Creation of drone-related content using swarm confirmation

Abstract

Content sink device comprising: a processor and a memory (116, 316, 930-932) comprising instructions which, when executed by the processor, cause the processor to: receive first encrypted data from a first device, read the first encrypted data to identify a first image and first metadata associated with the first image, receive second encrypted data from a second device, read the second encrypted data to identify a second image and second metadata associated with the second image, and process the first image, the first metadata, the second image and the second metadata to produce aggregated content (322).

Description

CROSS-REFERENCE TO RELATED REGISTRATIONS This application claims the benefit and priority of the previously filed United States patent application, serial number 14 / 863,918, filed on September 24, 2015, the subject matter of which is hereby incorporated in its entirety by reference. TECHNICAL AREA The embodiments described herein generally relate to drones and, in particular, to swarms of drones that capture content. GENERAL STATE OF THE ART Drones are increasingly being used to gather information. For example, information gathering devices (e.g., video, audio, etc.) can be mounted on a drone to collect data. Furthermore, multiple drones can be used to distribute the task of gathering information among a larger group. In particular, drones can be deployed in a swarm or group to collect information. When multiple drones participate in data collection, there can be an overlap in the captured samples. Therefore, overlapping data can be combined into a single copy. However, maintaining rights and assigning value to the captured information can be difficult when samples overlap. Drones can be operated by more than one entity, which complicates matters. Consequently, overlapping data can diminish the rights of each entity and / or the value assigned to the same entity. US 2009 / 0 327 739 A1 discloses a system and method for monitoring and controlling medical devices over a network. It specifically describes the remote monitoring, data acquisition, and control of infusion pumps by a central station. US 2010 / 0 293 580 A1 discloses a system for managing and monitoring medical devices in a hospital setting. It focuses on integrating various devices into a central network to improve patient safety and efficiency. US patent 2014 / 0 108 805 A1 discloses a system for wireless communication between medical devices and a central monitoring unit. It describes methods for secure data transmission and for improving interoperability between different types of devices. US patent 2012 / 0 059 826 A1 discloses a system for the automated monitoring and control of infusion systems. It places particular emphasis on the collection and analysis of operational data to optimize infusion management. US 2012 / 0 169 882 A1 discloses a system for the centralized control and monitoring of medical devices, particularly infusion pumps, in a clinical setting. It describes the use of networks for remote monitoring and control, as well as for improving patient safety. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 illustrates a block diagram of a system according to one embodiment. Fig. 2 illustrates a block diagram of a device of the system of Fig. 1 according to one embodiment. Fig. 3 illustrates a block diagram of aspects of the operation of the device of Fig. 2 according to one embodiment. Fig. 4 illustrates a block diagram of a device of the system of Fig. 1 according to one embodiment. Fig. 5 illustrates a block diagram of aspects of the operation of the device of Fig. 4 according to one embodiment. Fig. 6 illustrates a technique according to one embodiment. Figs. 7 to 8 each illustrate logic sequences according to different embodiments. Fig. 9 illustrates an embodiment of a computer-readable storage medium. Fig. 10 illustrates an embodiment of a processing architecture. DETAILED DESCRIPTION Various embodiments are generally aimed at providing information gathering by multiple drones, while preserving assigned rights and / or value to the content created by each drone or subsets of drones. In general, the present disclosure ensures that drones participating in content gathering can verify their credibility to establish trust between drones in the swarm. In some examples, verification can be facilitated by one-time programmable backups, non-cloning backups, or the like. Furthermore, positional information (e.g., a 3-dimensional (3D) positional relationship between the drone and a target, a 3D positional relationship between the drone and other drones in the swarm, etc.) can be recorded. Captured information can be encrypted and sent to a content sink device (e.g., a cloud storage device).The content is transmitted to a designated drone, a cloud service, etc. The content sink device can collect the content and generate a content capture history (e.g., based on 3D positional relationships, etc.) to assign value and rights to specific content-capturing drones or one or more entities operating the drones. With general reference to the terms and designations used herein, sections of the detailed description that follow can be represented as program procedures executed on a computer or a network of computers. These procedure descriptions and representations are used by those skilled in the art to communicate the substance of their work most effectively to other skilled in the art. A procedure is to be understood here and generally as being an independent sequence of operations that leads to a desired result. These operations are those that require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transmitted, combined, compared, and otherwise manipulated.It sometimes proves convenient, mainly for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, concepts, numbers, or the like. It should be noted, however, that all these and similar terms must be linked to the corresponding physical quantities and are merely convenient designations applied to those quantities. Furthermore, these manipulations are often described using terms such as adding or comparing, which are commonly associated with mental operations performed by a human operator. However, in most cases, for any of the operations described herein that form part of one or more embodiments, such human operator capability is neither necessary nor desirable. Instead, these operations are machine operations. Machines suitable for performing operations of various embodiments include general-purpose digital computers, such as those selectively activated or configured by an internally stored computer program written according to the teachings herein, and / or devices specially designed for the required purpose. Various embodiments also relate to devices or systems for performing these operations.These devices may be specifically designed for the required purpose or may include a general-purpose data processing device. The necessary structure for a large number of these machines will be evident from the given description. Reference is now made to the drawings, in which the same reference numerals are used throughout to denote identical elements. For illustrative purposes, numerous specific details are presented in the following description to ensure a thorough understanding. However, it may be obvious that the novel embodiments can be implemented in practice without these specific details. In other cases, known structures and devices are shown in block diagram form to facilitate their description. The intention is to provide a comprehensive description so that all modifications, equivalents, and alternatives within the scope of the claims are adequately described. Furthermore, variables such as "a", "b", and "c" can be used to describe components where more than one component can be implemented. It is important to note that there do not necessarily have to be multiple components, and furthermore, where multiple components are implemented, they do not have to be identical. Instead, the use of variables to denote components in the figures is done for the sake of convenience and clarity of representation. Figure 1 shows a block diagram of a drone-generated content creation system 1000. The system 100 can include any number of drones, 100-a, where "a" is a positive integer. It should be noted that, for illustrative purposes, this figure shows drones 100-1 to 100-6. However, the system 1000 can be implemented with any number of drones 100-a. Therefore, the examples shown here are not intended to be limiting. The drones 100-a can be any of a variety of drone types. The drones 100-a can be autonomously controlled, operator-controlled, or a combination of both. The drones 100-a can include or be effectively connected to information acquisition devices. For example, the drones 100-a can include various input acquisition devices, such as a microphone, a camera, an infrared detector, or the like. The drones 100-a can be configured to collect information related to a target 200. Generally, the target 200 can be any object or location to which the drones are tasked with gathering information. For example, the target 200 could be a person or group of people, a vehicle or group of vehicles, a place, a geographical region, an event, or the like. Generally, the drones 100-a can be configured to collect information (e.g., images, videos, audio, thermal images, or the like) related to the target 200. As a specific example, the target 200 could be a sporting event, and the drones could be configured to capture video content related to the sporting event (e.g., content related to the participants in the event, the audience, etc.). As noted, the drones 100-a can be configured to operate in a swarm 1001. In other words, the drones 100-a can be configured to coordinate their operations and / or information gathering with respect to the target 200. Accordingly, the drones 100-a can be communicatively connected to each other via one or more wireless communication standards and / or channels. For example, the drones 100-a can communicate via Bluetooth, WiFi Direct, ZigBee, or similar technologies. It should be noted that in this figure, for clarity, only some of the drones 100-a are depicted as wirelessly connected. However, any number or combination of drones 100-a can be communicatively connected during operation. In some examples, the communication can be based on various security protocols. For example, the drones 100-a can be configured to acknowledge each other to establish trust.A Drone 100-a can limit communication with another Drone 100-a based on the success or failure of the confirmation process. Furthermore, the drones 100-a can be configured to designate a lead drone. Drone 100-1 is depicted as the lead drone. However, in practice, any of the drones 100-a can be selected as the lead drone. Additionally, the determination of the lead drone can be dynamic during operation. For example, drone 100-1 might initially be designated as the lead drone, and subsequently, drone 100-3 (or another drone) might be designated as the lead drone. In some examples, the drone 100-a with the greatest amount of remaining energy (e.g., the largest battery capacity, the longest predicted flight time, or similar) might be designated as the lead drone. As another example, the drone 100-a with the greatest amount of data processing resources might be designated as the lead drone. In general, the lead drone 100-a can be configured to coordinate the gathering of information regarding target 200 between the drones 100-a. In some examples, the lead drone 100-a can be configured to send signals to the other drones that include a specification of an aspect of the target to be gathered. Continuing the example above, where target 200 is a sporting event, the lead drone 110-1 can be configured to send a signal to one of the other drones (e.g., drone 100-2 or similar) that includes a specification to gather information regarding a specific part of the sporting event (e.g., a section of a playing field or similar). Furthermore, the lead drone 100-1 can be configured to send a signal to one of the other drones (e.g., drone 100-3 or similar) that includes a specification to gather information regarding another part of the sporting event (e.g.,to capture another section of the playing field, part of the audience, or the like. The lead drone 100-1 can be configured to receive signals from each of the drones, including information about the drone's position relative to target 200. For example, the lead drone 100-1 can receive signals (such as wireless signals or the like) from drone 100-6, including information about the 3D positional relationship of drone 100-6 to target 200 and / or other drones 100-a. The lead drone 100-1 can then coordinate the acquisition of information about target 200 based on the positional information received from the drones 100-a. The drones 100-a can communicate with a content sink 300 via a network 999. Generally, the content sink 300 can receive captured content from the drones 100-a (e.g., via network 999 or similar) and recorded position information. The content sink 300 can aggregate the captured content into a single stream and generate a content capture history based on the recorded position information. Furthermore, the content sink 300 can assign rights and / or value to the captured content to the drones 100-a based on the recorded position information. For example, a single content stream (which may have multiple perspectives) can be generated from the captured content, and the contribution to this single stream, or to parts of the stream, can be determined for each drone based on the generated content capture history. In some examples, each of the drones 100-a sends signals to the lead drone 100-1, including details of captured content and metadata (described in more detail below) associated with the captured content, and the lead drone 100-1 sends signals to the content sink 300, including details of the content captured by each of the drones 100-a and associated metadata. Figures 2 to 3 illustrate examples of a drone 100-a, Figures 4 to 5 illustrate examples of the content sink 300. Figure 6 illustrates an example of a technique for creating drone-related content that can be implemented by the system 1000, and Figures 7 to 8 illustrate examples of logic sequences that can be implemented by a drone and a content sink, respectively. These examples are described in more detail below. It is important to note that these examples are discussed in relation to the system 1000 shown in Figure 1, but examples in this context are not limited. Furthermore, for the sake of clarity, Figures 2 to 3 refer to drone 100; however, it can be seen that a drone 100 can correspond to any drone in a system that is implemented according to the present disclosure, such as drone 100-1, 100-2, 100-3, 100-4, 100-5, 100-6 or the like. Turning closer to Fig. 2, the exemplary drone 100 is illustrated. The drone 100 can be implemented according to various examples of the present disclosure. In particular, the drone 100 shown in this figure can be implemented as one of the drones 100-a shown in Fig. 1. However, it should be noted that the drones 100-a can include more or different components than those illustrated in this figure. The drone 100 can include a processor element 112, a graphics processing unit (GPU) 114, memory 116, a sensing device 120, a sensor array 130, a global positioning sensor (GPS) 140, secure memory 150, a one-time programmable fuse (OTPF) 162, an interface 170, and an antenna 172.Furthermore, as shown, the acquisition device 120, the sensor grouping 130, the GPS 140, the secure storage 150 and the OTPF 162 can operate within a trusted execution environment (TEE) 160. Sensor grouping 130 can include one or more sensors 132-b, where "b" is a positive integer. For clarity, sensor grouping 130 is shown to include sensors 132-1, 132-2, and 132-3. However, grouping 130 can include any number of sensors. For example, sensor grouping 130 can include a proximity sensor, an accelerometer, a barometer, a gyroscope, a magnetometer, an ambient light sensor, or the like. Memory stores one or more of a drone control routine 118. Secure memory stores one or more of a content creation control routine 152, captured content 154, content metadata 156, content creation guidelines 157, a swarm information element (IE) 158, and a flight plan 159.It is important to note that although the term "flight plan" is used, it is not intended to mean that the drone(s) in question are aerial drones. Instead, the drone(s) in question can be any combination of air-, land-, water-, or otherwise supported drones. In general, the drone control routine 118 contains a sequence of instructions that are effective on the components of the device 100 (e.g. the processor element 112, the GPU 114 or the like) to implement logic for operating the drone. Content creation control routine 152 contains a sequence of instructions effective at the TEE 160 to implement logic for confirming the setup or connection of the drone swarm (e.g., which drones 100-a or the like the swarm may include), for example, using OTPF 162, or the like. Furthermore, content creation control routine 152 contains a sequence of instructions effective at the TEE 160 to generate captured content 154 from the capture device 120, to generate content metadata 156 from the sensor grouping 130 and / or the GPS 140, and to communicate the swarm IE 158 and / or the flight plan 159 to the drone operator (e.g., drone 100-1 or the like). Turning closer to Fig. 3, a block diagram of an example of a part of the drone 100 is shown. Specifically, exemplary aspects of the drone 100's operation are depicted. In various embodiments, the drone control routine 118 and / or the content authoring control routine (CACR) 152 can include one or more operating system components, device drivers, and / or application-level routines (e.g., so-called "software packages" provided on disk media, "applets" obtained from a remote server, etc.). If an operating system is included, it can be any of the many available operating systems suitable for the corresponding processor component 112.If one or more device drivers are included, these device drivers can provide support for any of a variety of other components, whether hardware or software components of Device 100. In general, the CACR 152 is configured to acknowledge the joining and / or formation of a drone swarm (e.g., the drone grouping mapped by the System 1000, or the like) and to coordinate content capture as described herein, while the drone control routine 118 is configured to operate the drone based on the flight plan according to the coordinated content capture. The CACR 152 can include an acknowledgment machine 1521, a flight planner 1522, a content recording device 1523, a metadata recording device 1524, and a content transmitter 1525. The drone control routine 118 can include a drone controller 119. The confirmation machine 1521 broadcasts one or more signals that include information about the communication capabilities of the drone 100. Specifically, the confirmation machine 1521 can broadcast the swarm information element 158, which includes information about the communication capabilities of the drone 100. In some examples, the confirmation machine 1521 can broadcast the swarm information element 158 ​​via all available communication channels (e.g., using interface 170, antenna 174, and / or the like). Furthermore, the acknowledgment machine 1521 can receive one or more signals that include information on the communication capabilities of cooperating content capture devices, such as other drones (e.g., the drones 100-a shown in Fig. 1 or the like). Specifically, the acknowledgment machine 1521 can receive the swarm information element 158, which includes information on the communication capabilities of other drones (e.g., cooperating content capture devices or the like). In some examples, the acknowledgment machine 1521 can receive the swarm information element 158 ​​via one or more available communication channels (e.g., using the interface 170, the antenna 174, and / or the like). The acknowledgment machine 1521 can determine the capabilities of neighboring drones (e.g., drones that are intended to jointly collect content in a swarm configuration, or the like) and can acknowledge the neighboring drones. For example, the acknowledgment machine can acknowledge the neighboring drones via one or more acknowledgment procedures (e.g., ...) to form a drone swarm (e.g., the swarm shown in Fig. 1). In some examples, drones can be partially acknowledged. Specifically, content can be obtained from certain drones, but the content is either verified or treated as less reliable compared to content obtained from fully acknowledged drones. The confirmation machine 1521 can identify a lead drone (e.g., drone 100-1 or similar) from the drone swarm. In some examples, the confirmation machine 1521 can identify the drone with the highest amount of remaining energy as the lead drone from among the drones in the swarm. In other examples, the confirmation machine 1521 can identify the drone with the highest amount of processing power, storage, memory, or similar as the lead drone from among the drones in the swarm. In general, the Flight Planner 1522 can provide and / or load drivers and / or guidelines related to content creation that are necessary for drones in the swarm to cooperate. Furthermore, the Flight Planner 1522 can coordinate the flight path and areas where content is to be captured. For example, the Flight Planner 1522 can load the content creation guidelines 157 from secure storage and can receive the flight plan 159 from a lead drone (e.g., drone 100-1) or similar device, which includes a specification of aspects, geographical regions, targets, or the like from which content is to be captured. Furthermore, the flight planner 1522 can determine the orientation of drone 100 (e.g., its 3D orientation in space or similar) and the context-dependent position of the drone relative to the target (e.g., target 200) and other drones in the swarm (e.g., other drones 100-a or similar). For example, the flight planner 1522 can determine the context-dependent orientation of drone 100 relative to the target and the other drones based on the swarm IE 158. Based on the determined position and orientation of the drone, the flight planner 1522 can update the flight plan. For example, the flight plan can be updated based on the content creation guidelines. Furthermore, the flight planner can send control signals to the drone controller 119 to instruct the drone controller 119 to navigate according to the flight plan 159. For example, the drone controller 119 can instruct the drone 100 to remain stationary, turn to a different orientation, move to a different geographical location, or the like. In general, the content recording device 1523 encrypts captured content in order to securely transmit the content to a content sink device (e.g., the content sink 300 or the like). In some examples, the content recording device 1523 receives signals from the capture device 120, which include an indication of the captured content 154, and encrypts the captured content. For example, the content recording device 1523 can encrypt the captured content using credentials based on OTPF 162. In general, the metadata recording device 1524 encrypts captured metadata to securely transmit the metadata to a content sink device (e.g., the content sink 300 or the like). In some examples, the metadata recording device 1524 receives signals from the sensor grouping 130 and / or the GPS 140, which include metadata information 156 relating to the captured content 154, and encrypts the metadata. For example, the metadata recording device 1524 can encrypt the metadata using credentials based on OTPF 162. In general, the content sender 1525 causes the interface 170 to send signals that include information about the encrypted captured content 154 and the encrypted content metadata 156. For example, the content sender 1525 can transmit signals that include information about the content 154 and the metadata 156 to a drone operator (e.g., drone operator 100-1 or the like). In some examples, the content sender 1525 can transmit signals that include information about the content 154 and the metadata 156 to a content sink (e.g., content sink 300 or the like). In some examples (e.g., when drone 100 acts as a drone pilot), content sender 1525 can receive signals, including information about content and metadata, from other drones in the swarm and can forward or transmit a signal, including information about the received content and metadata, to a content sink. Figure 4 illustrates a portion of the drone sink 300. The drone sink 300 can be implemented according to various examples in the present disclosure. The drone sink 300 can include a processor element 312, a graphics processing unit (GPU) 314, memory 316, an interface 170, and an antenna 172. The memory 316 stores one or more of the following: content 154-1 to 154-N captured by a control routine 318, content metadata 156-1 to 156-N, content creation guidelines 157, a rights log 320, and collected content 322. In general, the control routine 318 includes a sequence of instructions that are effective on the components of the device 300 (e.g., the processor element 312, the GPU 314, or the like) to implement logic for decrypting and verifying the authenticity of the received content and to assign or track ownership based on the content based on the metadata. Turning closer to Fig. 5, a block diagram of an example of a part of the sink 300 is shown. Specifically, exemplary aspects of the sink 300's operation are illustrated. In various embodiments, the control routine 318 can include one or more operating system components, device drivers, and / or application-level routines (e.g., so-called "software packages" provided on disk media, "applets" received from a remote server, etc.). If an operating system is included, it can be any of the many available operating systems suitable for any corresponding processor component 312. If one or more device drivers are included, these device drivers can provide support for any of the many other components, whether hardware or software components, of the sink 300. In general, the control routine 318 is configured to receive encrypted content and metadata from drones in the system 1000 (e.g., from each drone directly and / or via a drone operator or the like), to acknowledge the received content, and to assign ownership to portions of the received content. In some examples, the control routine 318 may include a receiver 332, an authenticator 334, an aggregator 336, and an ownership assigner 338. In general, the receiver 332 receives signals (e.g., via interface 370 or the like) that include information about the captured content 154 and content metadata 156, corresponding to different drones in the system 1000. For example, the receiver 332 can receive signals that include information about the content 154 and metadata 156 from a drone operator (e.g., drone operator 100-1 or the like). It can be seen that the sink 300, and in particular the receiver 332, can receive a number (e.g., N) of different content samples. Accordingly, received content 154-1, 154-2 to 154-N and content metadata 156-1, 156-2 to 156-N are mapped. The content 154-1 may not necessarily correspond to drone 100-1, but instead represents a single sample of received content that may have been obtained by drone 100-1 or another drone in swarm 1000. Authenticator 334 can verify the received content. Specifically, authenticator 334 can determine whether the received content was obtained by a verified drone in swarm 1000. For example, authenticator 334 can determine whether the received content is encrypted based on trusted credentials (e.g., one of the OTPFs from a verified drone or similar). In general, the aggregator 336 can collect the content from the multiple drones in the swarm into a single stream of aggregated content 322. For example, the aggregator 336 can merge the content, remove overlapping samples, and perform various content processing operations (e.g., amplification, clarification, etc.) on the content to form the aggregated content 322. In general, the ownership assigner 338 can generate the rights logs that include ownership information for parts of the aggregated content 322. Specifically, the assigner 338 can determine ownership assignments for parts of the aggregated content 322 based on the captured content 154-n, the content metadata 156-n, and the content creation guidelines 157. In various embodiments, the processor elements 112 and / or 312 can include any of a wide variety of commercially available processors, without limitation including an AMD® Athlon®, Duron® or Opteron® processor, an ARM® application, embedded or secure processor, an IBM® and / or Motorola® DragonBall® or PowerPC® processor, an IBM and / or Sony® Cell processor, or an Intel® Celeron®, Core (2) Duo®, Core (2) Quad®, Core i3®, Core i5®, Core i7®, Atom®, Itanium®, Pentium®, Xeon® or XScale® processor. Furthermore, one or more of these processor elements may include a multi-core processor (whether the multiple cores are located together on the same or separate chips) and / or a multi-processor architecture of another type, through which multiple physically separate processors are linked in some way.Furthermore, in various embodiments, any number of the processor elements 110, 210, and / or 410 can include a trusted execution environment (e.g., Intel CSE®, Intel ME®, Intel VT®, Intel SGX®, ARM TrustedZone®, or similar) to ensure the processing and / or storage of sensitive information. The trusted execution environment can be accessed using the geolocation techniques described herein. In various embodiments, the GPUs can include 114 and / or 314 of any number of commercially available graphics processing units. Furthermore, one or more of these graphics processing units can have dedicated memory, multi-stranded processing, and / or other parallel processing capabilities. In various embodiments, the memory 11, 316 and / or the secure memory 150 can be based on any of a wide variety of information storage technologies, which may include volatile technologies requiring a continuous supply of electrical power and may include technologies involving the use of machine-readable media, which may or may not be removable. Consequently, each of these memories can include a wide variety of types (or combinations of types) of storage devices, without limitation including solid-state memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), dual-rate DRAM (DDR-DRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory (e.g.,, ferroelectric polymer memory), ovonic memory, phase-transition or ferroelectric memory, silicon oxide nitride oxide silicon (SONOS) memory, magnetic or optical cards, one or more single ferromagnetic disk drives, or multiple storage devices organized into one or more groupings (e.g., multiple ferromagnetic disk drives organized into a redundant array of independent disks or RAID grouping). It should be noted that, although each of these storage devices is depicted as a single block, one or more of them may include multiple storage devices that may be based on different storage technologies.Consequently, one or more of these depicted storage devices could, for example, represent a combination of an optical drive or a flash memory card reader, through which programs and / or data can be stored and transported on some type of machine-readable storage media; a ferromagnetic disk drive for the local storage of programs and / or data for a relatively extended period; and one or more volatile solid-state storage devices that allow relatively fast access to programs and / or data (e.g., SRAM or DRAM). It should also be noted that each of these storage devices could consist of several storage components based on identical storage technology, but which, as a result of specialization in use, could be maintained separately (e.g.,Some DRAM devices are used as main memory, while other DRAM devices are used as a dedicated image buffer for a graphics controller. In various embodiments, the TEE 160 may include logic, functions, features, and / or memory to implement the functions described herein. It is important to note that the TEE 160 may be enclosed within the processor element 112 and / or the secure memory 150. However, for clarity, the TEE 160 is shown separately from the processor element 112. In some examples, the TEE 160 may be implemented as a secure enclave, a secure coprocessor, or the like. In various embodiments, the capture device 120 can be any of a variety of content capture devices, such as a camera, a video recorder, an audio recorder, an infrared capture device, a radar capture device, or the like. In various embodiments, the interfaces 170 and / or 370 can employ any of a wide variety of signaling technologies, enabling the components to be connected via the antennas 72 and / or 372 to the network 999 and / or other drones 100-a in the system 1000. In general, the drone 100 and / or the sink 300 can communicate (e.g., ad hoc, directly, or via network 999) with other devices (e.g., devices in system 1000). Generally, the drone 100 and / or the sink 300 can exchange data and / or information relating to content acquired from a drone swarm, such as captured content 154, content metadata 156, content creation guidelines 157, swarm IE 158, and / or flight plan 159. In some examples, devices 100 and / or 300 can exchange data (even unrelated data) with other devices not shown. Furthermore, devices 100 and / or 300 can effectively connect to an additional network (such as the internet or similar) via network 999 or another network not shown. In various embodiments, the Network 999 can be a single network, possibly limited to extending within a single building or other relatively confined area, a combination of interconnected networks, possibly extending over a considerable distance, and / or it can include the Internet. Consequently, the Network 999 can be based on any of a multitude (or combination) of communication technologies capable of exchanging signals, without limitation including wired technologies employing electrically and / or optically conductive cabling, and wireless technologies employing infrared, radio frequency, or other forms of wireless transmission. Accordingly, the Interfaces 170 and / or 370 can include circuits providing at least some of the necessary functionality to enable such a connection.However, interfaces 170 and / or 370 may also be implemented, at least partially, with sequences of instructions executed by the processor elements (e.g., to implement a protocol stack or other features). If one or more segments of the network 999 employ electrically and / or optically conductive cabling, the interface may employ signaling and / or protocols conforming to any of a wide variety of industry standards, including, but not limited to, RS-232C, RS-422, USB, Ethernet (IEEE 802.3), or IEEE 1394. Alternatively or additionally, if one or more segments of the network 999 involve the use of wireless signaling, corresponding interfaces may employ signaling and / or protocols conforming to any of a wide variety of industry standards, including, but not limited to, IEEE 802.11a, 802.11b, 802.11g, 802.16, 802.17, and 802.18.20 (commonly referred to as "Mobile Broadband Wireless Access"), Bluetooth, ZigBee, or a cellular radio service such as GSM with General Packet Radio Service (GSM / GPRS), CDMA / 1xRTT, Enhanced Data Rates for Global Evolution (EDGE), Evolution Data Only / Optimized (EV-DO), Evolution For Data and Voice (EV-DV), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), 4G LTE, etc. It should be noted that although the interface is depicted as a single block, it could include multiple interfaces that may be based on different signaling technologies. This can be particularly true if one or more of these interfaces connect the components to more than one network, each employing different communication technologies. Turning more closely to Fig. 6, aspects of the operation of System 100 are illustrated in greater detail. Specifically, an acknowledgment technique 110 for content obtained from a swarm is depicted. As shown, the technique 1100 includes operations or blocks 6.X, where X is a positive integer. Furthermore, the technique 1100 is described with reference to System 1000 of Fig. 1, the drone 100 of Figs. 2 to 3, and the content sink 300 of Figs. 4 to 5. Specifically, the technique 1100 is described with respect to drones 100-1, 100-2, and 100-3, as well as the content sink 300. However, this is not intended as a limitation. Specifically, the technique 1100 can be implemented with any number of drones 100-a. Starting at block 6.1, drones 100-1, 100-2, and 100-3 can confirm each other. Specifically, drones 100-1, 100-2, and 100-3 can transmit information elements 158, which include details of authorization credentials and / or the drones' position (e.g., in 3D space). Furthermore, at block 6.1, drones 100-1, 100-2, and 100-3 can receive information elements 1000 transmitted by other drones in the system. For example, the drones' confirmation machine (e.g., confirmation machine 1521 or similar) can transmit and / or receive information elements 158. Continuing from section 6.2, drones 100-1 can authenticate one or more of the other drones to form drone swarm 1001 and determine a lead drone from among the drones in swarm 1001. For example, the drone with the largest remaining battery charge (e.g., drone 100-1 or similar) can be selected as the lead drone. Continuing from Block 6.3, the lead drone 100-1 can send an information element to the other drones in the swarm, where the information element includes a flight plan for the drones. Specifically, the information element can include details of aspects of a target to be captured and / or information regarding the capture of information. For example, the flight planner of the lead drone 100-1 can arrange for an information element to be transmitted (e.g., via the internet, the 999 network, peer-to-peer communication, or the like) to the flight planner of the other drones in the swarm. In some examples, the lead drone (e.g., as described) can coordinate the capture of information regarding the target based on Content Creation Guidelines 157.Furthermore, the lead drone can coordinate the collection of information based on the positional relationships of the drones in the swarm to each other and / or to the target. In some examples, Block 6.3 allows each drone to determine a flight plan based on Content Creation Guideline 157. Furthermore, each drone can coordinate information gathering based on the positional relationships of the drones within the swarm to each other and / or to the target. For example, in Block 6.3, the lead drone cannot necessarily determine a flight plan for the other drones and transmit the flight plan to them. Instead, each drone can determine its own flight plan based on its positional relationships to the other drones, determined, for example, by Information Element 158 ​​or similar. Continuing from Block 6.4, each of the drones in the swarm can capture content and metadata related to the captured content. For example, drones 100-1, 100-2, and 100-3 can capture content (e.g., video, audio, images, heat signatures, or the like) related to the target. Furthermore, drones 100-1, 100-2, and 100-3 can capture metadata related to the captured content. For example, the content recorder and the metadata recorder (e.g., content recorder 1523 and metadata recorder 1524, or the like) can capture content metadata as described herein. Continuing from Block 6.5, some of the drones can transmit the captured content and metadata to the lead drone. Specifically, in some examples in Block 6.5, drones 6.2 and 6.3 can send signals containing information about the captured content and metadata to the lead drone 100-1. In some examples, drones 100-2 and 100-3 can encrypt the captured content and metadata before sending it to the lead drone 100-1. In some examples, the captured content and metadata can be encrypted by the content sender (e.g., content sender 1525 or similar) using OTP 162. Continuing from Block 6.6, the lead drone can transmit the content received by drones (e.g., content captured by drones 100-1, 100-2, and 100-3, or similar) to the content sink 300. Specifically, the lead drone 100-1 can initiate the transmission of signals to the content sink (e.g., via the internet, network 999, a peer-to-peer connection, or similar), with the signal including information about the content and metadata captured by the swarm of drones. Furthermore, in Block 6.6, the content sink can receive signals (e.g., from the lead drone 100-1, or similar) that include information about the content captured by drones in swarm 1001 and metadata relating to that captured content. Following on from Block 6.7, Content Sink 300 can decode the content and metadata received from Lead Drone 100-1. Specifically, Content Sink 300 can decode the content and metadata captured by each of the drones 100-1, 100-2, and 100-3. Furthermore, Content Sink 300 can authenticate the content in Block 6.7 to determine whether it was generated and / or captured by an authenticated drone. Continuing from Block 6.8, the content sink 300 can aggregate the content received by the drones in the swarm into a single content stream. Specifically, the aggregator 336 can generate aggregated content 322 from the captured content. Continuing from Block 6.9, the content sink 300 can assign rights and / or ownership to sections of the aggregated content based on the captured content, the metadata associated with the captured content, and the content creation guidelines 157. Specifically, the ownership assignor 338 can determine ownership interests (e.g., full, partial, fractional, or the like) in sections of the aggregated content 322. In some examples, the lead drone 100-1 can log all transactions completed by the swarm 1001. For instance, the lead drone 100-1 can log activity (e.g., information element, content, metadata, or the like) from each drone in the swarm 1001. Such activity logs can be used to identify malicious and / or defective drones within the swarm. Figures 7 to 8 illustrate embodiments of logic sequences for ensuring information acquisition by multiple drones operating in a swarm, while maintaining the rights and / or value assigned to the content created by each drone or by subsets of drones. In general, the logic sequences can be implemented by parts of the System 1000 described herein. Specifically, one or more of the drones can implement the logic sequence shown in Figure 7, while the content sink can implement the logic sequence shown in Figure 8. It should be noted that the logic sequences are described with reference to Figures 1, 2, 3, 4, 5 to 6, and in particular to the drone 100 and the content sink 300. However, examples are not limited in this context, and in particular, systems and / or devices with similar or different components to those shown in Figures 1, 2, 3, 4, 5 to 6, and 8, can be used.4 , Fig. 5 to Fig. 6 include the logic sequences shown. Turning closer to Fig. 7, a logic sequence 1200 can begin at block 1210. At block 1210, "Receiving a first signal from a capture device, wherein the first signal includes information about captured content," the CACR 152 can receive signals from the capture device 120, wherein the signals include information about the captured content 154. For example, the CACR can receive video, audio, infrared, or similar signals from the capture device 120. Continuing from block 1220, “Receiving a second signal from a number of sensors, wherein the second signal includes information on metadata that indicates a relationship between the captured content and a cooperating capture device,” the CACR 152 can receive signals from the sensor group 130 and / or the GPS 140. The received signals include information on the content metadata 156. Continuing from Block 1230, "Arrange for an information element to be sent to a content sink, the information element including a specification of the captured content and content metadata," CACR 152 can arrange for an information element to be sent to content sink 300. For example, CACR 152 can arrange for the captured content 154 and the content metadata 156 to be sent to content sink 300. In some examples, the information element can be encrypted (e.g., via OTPF 162 or similar). In some examples, CACR 152 can encrypt the information element and send it directly to content sink 300. In some examples, CACR 152 can encrypt the information element and send it to content sink 300 via a guide drone (e.g., guide drone 100-1 or similar). Turning closer to Fig. 8, the logic sequence 1300 is depicted. The logic sequence 1300 can begin at block 1310. At block 1310, "Receiving signals from a drone operating in a drone swarm, wherein the drone swarm includes a number of drones, wherein the signals include information about content captured by a number of drones and content metadata," the control routine 318 can receive the captured content 154-1, 154-2 to 154-N and the content metadata 156-1, 156-2 to 156-N. Continuing from Block 1320, “Authenticating Captured Content,” the control routine 318 can authenticate the captured content 154-1, 154-2 to 154-N and the content metadata 156-1, 156-2 to 156-N. For example, the control routine 318 can determine whether the content was generated, encrypted, and / or transmitted by an authorized drone within the swarm. Continuing from Block 1330, “Assigning ownership rights to the captured content to one or more of the drones based on the content metadata,” the control routine 318 can assign ownership interests in the captured content (e.g., for licensing, micropayments, or the like) to one or more of the drones within the swarm based on the content metadata. In some examples, the control routine 318 can generate aggregated content from the captured content and assign ownership rights to portions of the aggregated content to one or more drones within the drone swarm based on the captured content and the content metadata. Fig. 9 illustrates an embodiment of a storage medium 2000. The storage medium 2000 can comprise a manufactured article. In some examples, the storage medium 2000 can include any computer-readable or machine-readable medium, such as optical, magnetic, or semiconductor memory. The storage medium 2000 can store various types of computer-executable instructions (e.g., 2002). For example, the storage medium 2000 can store various types of computer-executable instructions for implementing logic sequence 1100. In some examples, the storage medium 2000 can store various types of computer-executable instructions for implementing logic sequence 1200. In some examples, the storage medium 2000 can store various types of computer-executable instructions for implementing logic sequence 1300. Examples of computer-readable or machine-readable storage media can be any physical media capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and so on. Examples of computer-executable instructions can include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The examples are not limited in this context. Fig. 10 illustrates an embodiment of an exemplary processing architecture 3000, which is suitable for implementing various embodiments as described above. Specifically, the processing architecture 3000 (or variants thereof) can be implemented as part of the system 1000 of Fig. 1, the drone 100 of Figs. 2 to 3, and / or the contents sink 300 of Figs. 4 to 5. The Processing Architecture 3000 includes various elements commonly used in digital processing, without limitation including one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, power supplies, etc. As used in this description, the terms "system" and "component" are meant to denote an instance of a data processing device in which digital processing is performed, wherein the instance is hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by this exemplary processing architecture depicted. For example, a component could be a process running on a processor element, the processor element itself, a storage device (e.g., a storage drive), or a storage device.A component can be, but is not limited to, a hard disk drive, multiple storage devices in a group, etc., which may employ an optical and / or magnetic storage medium; a software object; an executable sequence of instructions; an execution thread; a program; and / or an entire data processing device (e.g., an entire computer). For illustration, both an application running on a server and the server itself can be a component. One or more components can reside within a process and / or an execution thread, and a component can reside on a data processing device and / or be distributed between two or more data processing devices. Communication can involve the one-way or two-way exchange of information. For example, components can communicate information in the form of signals transmitted via communication media.The information can be implemented as signals assigned to one or more signal lines. Each message can be a single signal or multiple signals transmitted either serially or essentially in parallel. As shown, when implementing the processing architecture 3000, a data processing device includes at least one processor element 910, one memory 930, one interface 990 to other devices, and one coupling 915. Depending on various aspects of a data processing device implementing the processing architecture 3000, including its intended use and / or conditions of use, such a data processing device may further include additional components, such as, without limitation, a counter element 915. The coupling 915 contains one or more buses, point-to-point connections, transceivers, buffers, coupling point switches, and / or other conductors and / or logic that communicatively connects at least the processor element 910 to the memory 930. The coupling 915 can further connect the processor element 910 to one or more of the interface 990 and the display interface 955 (depending on which of these and / or other components are also present). When the processor element 910 is thus connected by couplings 915, it is capable of performing the various tasks described in detail above, regardless of which of the data processing devices 100, 300, and 600 implement the processing architecture 3000. The coupling 915 can be implemented using any number of technologies or combinations of technologies by which signals are transmitted optically and / or electrically.Furthermore, at least parts of the coupling 915 can employ timings and / or protocols that conform to any of a wide variety of industry standards, without limitation including Accelerated Graphics Port (AGP), CardBus, Extended Industry Standard Architecture (E-ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI-X), PCI Express (PCI-E), Personal Computer Memory Card International Association (PCMCIA) Bus, HyperTransport™, QuickPath and the like. As previously discussed, the processor element 910 can include any of a wide variety of commercially available processors, employing any of a wide variety of technologies and implemented with one or more cores physically combined in any number of ways. As previously discussed, the Memory 930 can include one or more independent storage devices based on any wide variety of technologies or combinations of technologies. Specifically, as shown, the Memory 930 can include one or more volatile Memory 931 (e.g., solid-state memory based on one or more forms of RAM technology), Non-volatile Memory 932 (e.g., solid-state, ferromagnetic, or other memory that does not require a constant supply of electrical energy to retain its contents), and Removable Media Memory 933 (e.g., removable disk or solid-state memory card storage, enabling the transfer of information between data processing devices).This depiction of Memory 930 as possibly encompassing several distinct types of memory is made in recognition of the common use of more than one type of memory device in data processing equipment, where one type provides relatively fast read and write capabilities that enable faster manipulation of data by the Processor Element 910 (but may use a “volatile” technology that requires constant electrical energy), while another type provides relatively high density of non-volatile memory (but may provide relatively slow read and write capabilities). Given the often differing characteristics of various storage devices employing different technologies, it is also common for such diverse storage devices to be connected to other parts of a data processing device via different memory controllers, which are connected to their respective storage devices through different interfaces. For example, if volatile memory 931 is present and based on RAM technology, the volatile memory 931 may be communicatively connected to coupling 915 by a memory controller 935a, which provides a suitable interface to the volatile memory 931, perhaps providing row and column addressing, and where the memory controller 935a can perform row updates and / or other maintenance tasks to help retain the information stored within the volatile memory 931.As another example, if the non-volatile memory 932 is present and includes one or more ferromagnetic and / or solid-state disk drives, the non-volatile memory 932 can be communicatively connected to the coupling 915 by a memory controller 935b, which provides a suitable interface to the non-volatile memory 932, perhaps employing addressing of information blocks and / or of cylinders and sectors.As yet another example, if the removable media storage 933 is present and includes one or more optical and / or solid-state disk drives employing one or more pieces of removable machine-readable storage media 939, the removable media storage 933 can be communicatively connected to the coupling 915 by a storage controller 935c, which provides a suitable interface to the removable media storage 933, perhaps employing addressing of information blocks, and wherein the storage controller 935c can coordinate read, erase, and write operations in a manner specifically designed to extend the lifetime of the machine-readable storage media 939. Either the volatile memory 931 or the non-volatile memory 932 includes a manufactured article in the form of a machine-readable storage medium on which a routine may be stored comprising a sequence of instructions executable by the processor element 910, depending on the technologies on which each is based. For example, if the non-volatile memory 932 uses ferromagnetic disk drives (e.g., so-called "hard disks"), each such disk drive typically employs one or more rotating disks on which a coating of magnetically responsive particles is deposited and magnetically aligned in various patterns to store information, such as a sequence of instructions, in a manner similar to removable storage media, such as a floppy disk.As another example, non-volatile memory 932 can consist of banks of solid-state storage devices to store information, such as a sequence of instructions, in a manner similar to a compact flash card. Again, it is common to employ different types of storage devices in a data processing device at different times to store executable routines and / or data.Consequently, a routine comprising a sequence of instructions to be executed by the processor element 910 may initially be stored on the machine-readable storage media 939, and the removable media memory 933 may subsequently be used for long-term storage when copying this routine to the non-volatile memory 932, which does not require the continued presence of the machine-readable storage media 939 and / or the volatile memory 931 to allow faster access by the processor element 910 when this routine is executed. As previously discussed, the 990 interface can employ any of a variety of signaling technologies corresponding to any of a variety of communication technologies that can be used to connect a data processing device to one or more other devices. Again, one or both of various forms of wired or wireless signaling can be employed to enable the 910 processor element to interact with input / output devices (e.g., the illustrated exemplary keyboard 940 or a printer 945) and / or other data processing devices, possibly through a network (e.g., the 999 network) or an interconnected set of networks.Recognizing the often highly diverse nature of the various types of signaling and / or protocols that any given data processing device may need to support, the 990 interface is comprehensively represented as several distinct interface controllers: 995a, 995b, and 995c. The 995a interface controller can employ any of a variety of wired digital serial or wireless radio frequency interfaces to receive serially transmitted messages from user input devices, such as the illustrated 940 keyboard. The 995b interface controller can employ any of a variety of wired or wireless signaling, timing, and / or protocols to access other data processing devices through the 999 network (perhaps a network comprising one or more links, smaller networks, or perhaps the Internet).The 995c interface controller can use any of a variety of electrically conductive wiring, enabling the use of either serial or parallel signal transmission to carry data to the illustrated 945 printer. Other examples of devices that can be communicatively connected through one or more 990 interface controllers include, but are not limited to, microphones, remote controls, stylus pens, card readers, fingerprint readers, virtual reality interaction gloves, graphical input tablets, joysticks, other keyboards, retinal scanners, the touch component of touchscreens, rollerballs, various sensors, laser printers, inkjet printers, mechanical robots, milling machines, and so on. If a data processing device is communicatively connected to (or perhaps even contains) a display (e.g., the exemplary display 950 shown), such a data processing device implementing the 3000 processing architecture can also include the 955 display interface. Although more general types of interfaces can be used for communicative connection to a display, the somewhat specialized additional processing often required when visually displaying various forms of content on a display, as well as the somewhat specialized nature of the wired interfaces used, often makes providing a dedicated display interface desirable.Wired and / or wireless signaling technologies that can be used through the Display Interface 955 when communicating with the Display 950 make use of signaling and / or protocols that speak to any of a variety of industry standards, without limitation including any of a variety of analog video interfaces, Digital Video Interface (DVI), DisplayPort, etc. More generally, the various elements of data processing equipment can include 100, 200, and 400 different hardware elements, software elements, or a combination of both. Examples of hardware elements can include chips, logic devices, components, processors, microprocessors, circuits, processor elements, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so on), integrated circuits, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), memory units, logic gates, registers, semiconductor devices, chips, microchips, chipsets, and so on.Examples of software elements can include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, data processing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof.However, the determination of whether an embodiment is implemented using hardware elements and / or software elements can vary according to any number of factors, such as the desired data processing rate, energy levels, thermal tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints, as desired for a given implementation. Some embodiments may be described using the terms "an embodiment" or "an embodiment" together with their derivatives. These terms mean that a particular feature, structure, or property described in connection with the embodiment is included in at least one embodiment. The appearance of the phrase "in an embodiment" at different points in the description does not necessarily all refer to the same embodiment. Furthermore, some embodiments may be described using the terms "coupled" or "associated" together with their derivatives. These terms are not necessarily intended to be synonymous.For example, some embodiments can be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" can also mean that two or more elements are not in direct contact with each other, but nevertheless cooperate or interact with each other. It should be emphasized that the summary of disclosure is provided to enable a reader to quickly ascertain the nature of the technical disclosure. It is presented with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, it is evident from the preceding detailed description that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly stated in each claim. Instead, as reflected in the following claims, the inventive step lies in fewer than all the features of a single disclosed embodiment.Consequently, the following claims are hereby incorporated into the detailed description, each claim constituting a separate embodiment. In the appended claims, the terms "including" and "in which" are understood as the equivalents of the respective terms "comprising" and "whereby" in plain language. Furthermore, the terms "first," "second," "third," etc., are used only as distinguishing features and are not intended to impose any numerical requirements on their subject matter. What has been described above includes examples of the disclosed architecture. It is obviously not possible to describe every conceivable combination of components and / or methodologies, but an average person can see that many more combinations and substitutions are possible. Accordingly, the novel architecture is intended to encompass all such changes, modifications, and variations that fall within the spirit and scope of the attached claims. The disclosure now turns to providing several exemplary implementations. Example 1. Device comprising: logic, part of which is implemented in hardware, the logic comprising: a content recording device, wherein the content recording device receives a first signal from a capture device, the first signal including an indication of captured content; a metadata recording device, which receives a second signal from one or more sensors, the second signal including an indication of content metadata, the content metadata indicating a relationship between the captured content and a cooperating capture device; and a content sender, wherein the content sender causes an information element to be sent to a content sink device, the information element including an indication of the captured content and the content metadata. Example 2. Device of Example 1, wherein the content recording device, the metadata recording device and the content transmitter are executed in a trusted execution environment of a drone. Example 3. Device of one of Examples 1 to 2, wherein the content sender encrypts the information element. Example 4. Device of Example 3 comprising a one-time programmable fuse (OTPF), wherein the content sender encrypts the information element based on the OTPF. Example 5. Device of one of Examples 1 to 2, wherein the logic comprises an acknowledgment machine, the acknowledgment machine serving to: emit a first acknowledgment signal which includes an indication of a communication capability of the device, receive one or more secondary acknowledgment signals which include an indication of a communication capability of one or more cooperating content capture devices, and identify a content capture leader from the device and the one or more cooperating content capture devices. Example 6. Device of Example 5, wherein the logic identifies the content capture guide as one of the device or one or more cooperating content capture devices based on an amount of residual energy available to the device or one or more cooperating content capture devices. Example 7. Device of one of Examples 1 to 2, wherein the content sender causes an information element to be sent to a content sink device, wherein the information element includes a specification of the captured content and content metadata, comprising: sending a first information element to a content capture guide, wherein the first information element includes a specification of the captured content and content metadata, wherein the content capture guide sends a second information element to the content sink, wherein the second information element includes a specification of the captured content and content metadata. Example 8. Device of one of Examples 1 to 2 comprising an antenna and a radio device effectively connected to the antenna, wherein the content transmitter sends a control signal to the radio device to cause the radio device to transmit the information element via the antenna. Example 9. Device comprising: logic, part of which is implemented in hardware, the logic comprising: a receiver, wherein the receiver receives one or more signals from a drone operating in a drone swarm, the drone swarm including multiple drones, wherein the one or more signals include an indication of captured content and content metadata, the captured content being captured by one or more of the multiple drones, an authenticator to authenticate the captured content, and an ownership assigner to assign ownership rights to the captured content to one or more of the multiple drones. Example 10. Device of Example 9 comprising an aggregator to generate an aggregated content stream based on the captured content. Example 11. Device of Example 10, wherein the ownership assigner assigns ownership of a portion of the aggregated content stream to one of the multiple drones based on the captured content and content metadata. Example 12. Device of Example 10, wherein the ownership assignor determines a license for the aggregated content based on the assigned ownership rights. Example 13. Device of Example 10, wherein the ownership assignor determines a license fee payment for the aggregated content based on the assigned ownership rights. Example 14. Device comprising: a trusted execution environment (TEE), an acknowledgment machine executable by the TEE, wherein the acknowledgment machine emits a first acknowledgment signal which includes an indication of a communication capability of the device, receives one or more secondary acknowledgment signals which include an indication of a communication capability of one or more cooperating content capture devices, and identifies a content capture guide from the device and the one or more cooperating content capture devices, a content recording device executable by the TEE, wherein the content recording device receives a first signal from a capture device, the first signal including an indication of captured content, a metadata recording device executable by the TEE,wherein the metadata recording device receives a second signal from one or more sensors, the second signal including a specification of content metadata, and a content sender executable by the TEE, the content sender encrypting the captured content and content metadata and sending a signal including a specification of the encrypted captured content and encrypted content metadata to the content capture guide. Example 15. Device of Example 14 comprising a one-time programmable fuse (OTPF), wherein the content sender encrypts the captured content and content metadata based on the OTPF. Example 16. Device of Example 14 comprising a flight planner executable by the TEE, wherein the flight planner determines an orientation of the device in three-dimensional (3D) space relative to both the one or more cooperating content capture devices and a target, and determines a flight plan from which content is to be captured on the basis of the determined orientations. Example 17. Device of Example 14 comprising a flight planner executable by the TEE, wherein the flight planner receives a specification of a flight plan, the content of which is to be ascertained on the basis of the specified orientation. Example 18. System comprising: a drone control system, a trusted execution environment (TEE), a flight planner executable by the TEE, wherein the flight planner sends a control signal to the drone control system which includes an instruction to follow a flight path by which content is to be captured in relation to a target in conjunction with one or more cooperating content capture drones. Example 19. System of Example 18 comprising a TEE-executable content recording device, wherein the content recording device receives a first signal from a capture device, the first signal including an indication of captured content. Example 20. System of Example 19 comprising a TEE-executable metadata recording device, wherein the metadata recording device receives a second signal from one or more sensors, wherein the second signal includes a specification of content metadata, wherein the content metadata indicates a relationship between the captured content and the one or more cooperating capture devices. Example 21. System of Example 20 comprising a TEE-executable acknowledgment machine, wherein the acknowledgment machine emits a first acknowledgment signal including an indication of a communication capability of the device, receives one or more secondary acknowledgment signals including an indication of a communication capability of the one or more cooperating content capture devices, and identifies a content capture guide from the device and the one or more cooperating content capture devices. Example 22. System of Example 21 comprising a TEE-executable content sender, wherein the content sender encrypts the captured content and content metadata and sends a signal, including an indication of the encrypted captured content and encrypted content metadata, to a content capture guide. Example 23. System of Example 22, comprising a one-time programmable backup (OTPF), wherein the content sender encrypts the captured content and content metadata based on the OTPF. Example 24. System of Example 21, wherein the flight planner receives information about the flight path from the content capture guide. Example 25. System of Example 18 comprising a housing and a propulsion system, wherein the TEE is arranged in the housing and the drone control system is effectively connected to the propulsion system, wherein the drone control system causes the propulsion system to navigate a course substantially along the flight path. Example 26. System of Example 25, comprising a battery effectively connected to the propulsion system. Example 27. At least one machine-readable storage medium comprising instructions which, when executed by a trusted execution environment (TEE), cause the TEE to: receive a first signal from a capture device, wherein the first signal includes an indication of captured content; receive a second signal from one or more sensors, wherein the second signal includes an indication of content metadata, wherein the content metadata indicates a relationship between the captured content and a cooperating capture device; and cause an information element to be sent to a content sink device, wherein the information element includes an indication of the captured content and the content metadata. Example 28. The at least one machine-readable storage medium of Example 27, which includes instructions that further cause the TEE to encrypt the information element. Example 29. The at least one machine-readable storage medium of Example 27, which includes instructions that further cause the TEE to encrypt the information element at least partially on the basis of a one-time programmable password (OTPF). Example 30. The at least one machine-readable storage medium of Example 27 comprising instructions that further cause the TEE to: transmit a first acknowledgment signal including an indication of the device's communicative capability, receive one or more secondary acknowledgment signals including an indication of the communicative capability of one or more cooperating content capture devices, and identify a content capture leader from the device and the one or more cooperating content capture devices. Example 31. The at least one machine-readable storage medium of Example 27 comprising instructions which further cause the TEE to identify the content capture guide as the one from the device or the one or more cooperating content capture devices on the basis of an amount of residual energy available to the device or the one or more cooperating content capture devices. Example 32. The at least one machine-readable storage medium of Example 27, comprising instructions which further cause the TEE to send a first information element to a content capture guide, wherein the first information element includes a specification of the captured content and content metadata, wherein the content capture guide sends a second information element to the content sink, wherein the second information element includes a specification of the captured content and content metadata. Example 33. At least one machine-readable storage medium comprising instructions which, when executed by a data processing device, cause the data processing device to: receive one or more signals from a drone operating in a drone swarm, wherein the drone swarm includes multiple drones, wherein the one or more signals include an indication of captured content and content metadata, wherein the captured content is captured by one or more of the multiple drones, authenticate the captured content, and assign ownership rights to the captured content to one or more of the multiple drones. Example 34. The at least one machine-readable storage medium of Example 33, comprising instructions which further cause the data processing device to generate an aggregated content stream based on the captured content. Example 35. The at least one machine-readable storage medium of Example 33, comprising instructions which further cause the data processing device to assign ownership of a portion of the aggregated content stream to one of the multiple drones on the basis of the captured content and content metadata. Example 36. The at least one machine-readable storage medium of Example 33, which includes instructions that further cause the data processing device to determine a license for the aggregated content on the basis of the assigned ownership rights. Example 37. The at least one machine-readable storage medium of Example 33, which includes instructions that further cause the data processing device to determine a license fee payment for the aggregated content on the basis of the allocated ownership rights. Example 38. Computer-implemented method comprising: receiving a first signal from a capture device, wherein the first signal includes an indication of captured content; receiving a second signal from one or more sensors, wherein the second signal includes an indication of content metadata, the content metadata indicating a relationship between the captured content and a cooperating capture device; and causing an information element to be sent to a content sink device, wherein the information element includes an indication of the captured content and the content metadata. Example 39. Computer-implemented method of Example 38, which includes encrypting the information element. Example 40. Computer-implemented method of Example 38, which includes encrypting the information element at least partially on the basis of a one-time programmable password (OTPF). Example 41. Computer-implemented method of Example 38, comprising: transmitting a first acknowledgment signal including an indication of the device's communication capability, receiving one or more secondary acknowledgment signals including an indication of the communication capability of one or more cooperating content capture devices, and identifying a content capture leader from the device and the one or more cooperating content capture devices. Example 42. Computer-implemented method of Example 38, comprising identifying the content capture leader as the one belonging to the device or the one or more cooperating content capture devices based on an amount of residual energy available to the device or the one or more cooperating content capture devices. Example 43. Computer-implemented method of Example 38, which includes sending a first information element to a content capture guide, wherein the first information element includes a specification of the captured content and the content metadata, wherein the content capture guide sends a second information element to the content sink, wherein the second information element includes a specification of the captured content and the content metadata. Example 44. Computer-implemented method comprising: receiving one or more signals from a drone operating in a drone swarm, wherein the drone swarm includes multiple drones, wherein the one or more signals include an indication of captured content and content metadata, wherein the captured content is captured by one or more of the multiple drones, authenticating the captured content, and assigning ownership rights to the captured content to one or more of the multiple drones. Example 45. Computer-implemented method of Example 44, which includes generating an aggregated content stream based on the captured content. Example 46. Computer-implemented method of Example 44, which includes assigning ownership of a portion of the aggregated content stream to one of the multiple drones based on the captured content and content metadata. Example 47. Computer-implemented method of Example 44, which includes determining a license for the aggregated content based on the assigned ownership rights. Example 48. Computer-implemented method of Example 44, which includes determining a license fee payment for the aggregated content based on the assigned ownership rights. Example 49. Device for an apparatus, wherein the device comprises means for carrying out the method of one of Examples 38 to 48. Example 50. Device comprising: logic, part of which is implemented in hardware, the logic comprising: a content recording device, wherein the content recording device receives a first signal from a capture device, the first signal including an indication of captured content; a metadata recording device, which receives a second signal from one or more sensors, the second signal including an indication of content metadata, the content metadata indicating a relationship between the captured content and a cooperating capture device; and a content sender, wherein the content sender causes an information element to be sent to a content sink device, the information element including an indication of the captured content and the content metadata. Example 51. Device according to Example 50, wherein the content recording device, the metadata recording device and the content transmitter are executed in a trusted execution environment of a drone. Example 52. Device according to one of Examples 50 to 51, wherein the content sender encrypts the information element. Example 53. Device according to Example 52 comprising a one-time programmable fuse (OTPF), wherein the content sender encrypts the information element on the basis of the OTPF. Example 54. Device according to any of Examples 50 to 51, wherein the logic comprises an acknowledgment machine, the acknowledgment machine serving to: emit a first acknowledgment signal which includes an indication of a communication capability of the device, receive one or more secondary acknowledgment signals which include an indication of a communication capability of one or more cooperating content capture devices, and identify a content capture leader from the device and the one or more cooperating content capture devices. Example 55. Device according to Example 54, wherein the logic identifies the content capture leader as one of the devices or one or more cooperating content capture devices based on an amount of residual energy available to the device or one or more cooperating content capture devices. Example 56. Device according to any of Examples 50 to 51, wherein the content sender causes an information element to be sent to a content sink device, the information element including a specification of the captured content and content metadata, comprising: sending a first information element to a content capture guide, the first information element including a specification of the captured content and content metadata, the content capture guide sending a second information element to the content sink, the second information element including a specification of the captured content and content metadata. Example 57. Device according to any of Examples 50 to 51, comprising an antenna and a radio device effectively connected to the antenna, wherein the content transmitter sends a control signal to the radio device to cause the radio device to transmit the information element via the antenna Example 58. Device comprising: logic, part of which is implemented in hardware, the logic comprising: a receiver, wherein the receiver receives one or more signals from a drone operating in a drone swarm, the drone swarm including multiple drones, wherein the one or more signals include an indication of captured content and content metadata, the captured content being captured by one or more of the multiple drones; an authenticator to authenticate the captured content; and an ownership assigner to assign ownership rights to the captured content to one or more of the multiple drones. Example 59. Device according to Example 58 comprising an aggregator to generate an aggregated content stream based on the captured content. Example 60. Device according to Example 59, wherein the ownership assigner assigns ownership of a portion of the aggregated content stream to one of the multiple drones based on the captured content and content metadata. Example 61. Device according to Example 59, wherein the ownership assignor determines a license for the aggregated content on the basis of the assigned ownership rights. Example 62. Device according to Example 59, wherein the ownership assignor determines a license fee payment for the aggregated content based on the assigned ownership rights. Example 63. Device comprising: a trusted execution environment (TEE), an acknowledgment machine executable by the TEE, wherein the acknowledgment machine emits a first acknowledgment signal which includes an indication of a communication capability of the device, receives one or more secondary acknowledgment signals which include an indication of a communication capability of one or more cooperating content capture devices, and Identifying a content capture guide identified by the device and the one or more cooperating content capture devices, a content recording device executable by the TEE, wherein the content recording device receives a first signal from a capture device, the first signal including an indication of captured content, a metadata recording device executable by the TEE, wherein the metadata recording device receives a second signal from one or more sensors, the second signal including an indication of content metadata, and a content sender executable by the TEE, wherein the content sender encrypts the captured content and content metadata and sends a signal including an indication of the encrypted captured content and the encrypted content metadata to the content capture guide. Example 64. Device according to Example 63 comprising a one-time programmable fuse (OTPF), wherein the content sender encrypts the captured content and content metadata on the basis of the OTPF. Example 65. Device according to Example 63 comprising a flight planner executable by the TEE, wherein the flight planner determines an orientation of the device in three-dimensional (3D) space relative to both the one or more cooperating content capture devices and a target, and determines a flight plan, the content of which is to be captured on the basis of the determined orientations. Example 66. Device according to Example 63 comprising a flight planner executable by the TEE, wherein the flight planner receives a specification of a flight plan, the content of which is to be ascertained on the basis of the specified orientation. Example 67. System comprising: a drone control system, a trusted execution environment (TEE), a flight planner executable by the TEE, wherein the flight planner sends a control signal to the drone control system which includes an instruction to follow a flight path by which content is to be captured in relation to a target in conjunction with one or more cooperating content capture drones. Example 68. System according to Example 67 comprising a TEE-executable content recording device, wherein the content recording device receives a first signal from a capture device, the first signal including an indication of captured content. Example 69. System according to Example 68 comprising a TEE-executable metadata recording device, wherein the metadata recording device receives a second signal from one or more sensors, wherein the second signal includes a specification of content metadata, wherein the content metadata indicates a relationship between the captured content and the one or more cooperating recording devices. Example 70. System according to Example 69 comprising a TEE-executable acknowledgment machine, wherein the acknowledgment machine emits a first acknowledgment signal including an indication of a communication capability of the device, receives one or more secondary acknowledgment signals including an indication of a communication capability of the one or more cooperating content capture devices, and identifies a content capture guide from the device and the one or more cooperating content capture devices. Example 71. System according to Example 70 comprising a TEE-executable content sender, wherein the content sender encrypts the captured content and content metadata and sends a signal, including an indication of the encrypted captured content and encrypted content metadata, to a content capture guide. Example 72. System according to Example 71, comprising a one-time programmable backup (OTPF), wherein the content sender encrypts the captured content and content metadata based on the OTPF. Example 73. System according to Example 70, wherein the flight planner receives information about the flight path from the content capture guide. Example 74. System according to Example 67 comprising a housing and a propulsion system, wherein the TEE is arranged in the housing and the drone control system is effectively connected to the propulsion system, wherein the drone control system causes the propulsion system to navigate a course substantially along the flight path. Example 75. System according to Example 74, comprising a battery effectively connected to the propulsion system. Reference symbol list: 200 Target 116, 316, 930-932 Storage[s] 322 aggregated content[s]

Claims

Content sink device comprising: a processor and a memory (116, 316, 930-932) comprising instructions which, when executed by the processor, cause the processor to: receive first encrypted data from a first device, read the first encrypted data to identify a first image and first metadata associated with the first image, receive second encrypted data from a second device, read the second encrypted data to identify a second image and second metadata associated with the second image, and process the first image, the first metadata, the second image and the second metadata to produce aggregated content (322). Content sinking device according to claim 1, wherein the first image is contained in a first video and the second image is contained in a second video. Content sink device according to claim 1, wherein the first metadata includes first position data and the second metadata includes second position data. Content sinking device according to claim 1, wherein the first and second images are linked to a target (200) comprising a group of vehicles. Content sinking device according to one of claims 1 to 4, wherein the first device comprises a first drone and the second device comprises a second drone. Content sink device according to claim 5, wherein the first metadata comprises first position data corresponding to the first drone, and the second metadata comprises second position data corresponding to the second drone. Content sink device according to one of claims 1 to 6, wherein the processor and the memory (116, 316, 930-932) are contained in a cloud service. A computer-implemented procedure comprising: receiving first encrypted data from a first device, reading the first encrypted data to identify a first image and first metadata associated with the first image, receiving second encrypted data from a second device, reading the second encrypted data to identify a second image and second metadata associated with the second image, and processing the first image, first metadata, second image and second metadata to produce aggregated content (322). Computer-implemented method according to claim 8, wherein the first image is contained in a first video and the second image is contained in a second video. Computer-implemented method according to claim 8, wherein the first metadata includes first position data and the second metadata includes second position data. Computer-implemented method according to claim 8, wherein the first and second images are linked to a target (200) comprising a group of vehicles. Computer-implemented method according to one of claims 8 to 11, wherein the first device comprises a first drone and the second device comprises a second drone. Computer-implemented method according to claim 12, wherein the first metadata comprises first position data corresponding to the first drone, and the second metadata comprises second position data corresponding to the second drone. A computer-implemented method according to any one of claims 8 to 13, comprising processing the first image, the first metadata, the second image and the second metadata in a cloud service to generate the aggregated content (322). Non-volatile machine-readable medium(s) comprising a set of instructions which, in response to being executed by a processor circuit, cause the processor circuit to: receive first encrypted data from a first device, read the first encrypted data to identify a first image and first metadata associated with the first image, receive second encrypted data from a second device, read the second encrypted data to identify a second image and second metadata associated with the second image, and process the first image, the first metadata, the second image and the second metadata to produce aggregated content (322). Non-volatile computer-readable medium or non-volatile computer-readable media according to claim 15, wherein the first image is contained in a first video and the second image is contained in a second video. Non-volatile computer-readable medium or non-volatile computer-readable media according to claim 15, wherein the first metadata comprises first position data and the second metadata comprises second position data. Non-volatile computer-readable medium or non-volatile computer-readable media according to any one of claims 15 to 17, wherein the first and second images are linked to a target (200) comprising a group of vehicles. Non-volatile computer-readable medium or non-volatile computer-readable media according to any one of claims 15 to 18, wherein the first device comprises a first drone and the second device comprises a second drone. Non-volatile computer-readable medium or non-volatile computer-readable media according to claim 19, wherein the first metadata comprises first position data corresponding to the first drone, and the second metadata comprises second position data corresponding to the second drone. Device comprising: means for receiving first encrypted data from a first device, means for reading the first encrypted data to identify a first image and first metadata associated with the first image, means for receiving second encrypted data from a second device, means for reading the second encrypted data to identify a second image and second metadata associated with the second image, and means for processing the first image, the first metadata, the second image and the second metadata to produce aggregated content (322). Device according to claim 21, wherein the first image is contained in a first video and the second image is contained in a second video. Device according to claim 21, wherein the first and second images are linked to a target (200) comprising a group of vehicles. Device according to one of claims 21 to 23, wherein the first metadata includes first position data and the second metadata includes second position data. Device according to one of claims 21 to 24, wherein the first device comprises a first drone and the second device comprises a second drone.

Images