METHODS, SYSTEMS, AND DEVICES FOR HANDLING CAPTURED IMAGE DATA THAT IS RECEIVED BY DEVICES

Computationally implemented methods and systems include acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, and procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device. In addition to the foregoing, other aspects are described in the claims, drawings, and text.

BACKGROUND

This application is related to the capture of images that may include personality rights.

SUMMARY

Recently, there has been an increased popularity in wearable computers, e.g., computers that are placed in articles of clothing or clothing accessories, e.g., watches, eyeglasses, shoes, jewelry, accessories, shirts, pants, headbands, and the like. As technology allows electronic devices to become smaller and smaller, more and more items may be “smart” items, e.g., may contain a computer.

In addition, image capturing technology has also improved, allowing for high quality digital cameras that can capture pictures, audio, video, or a combination thereof. These digital cameras may be small enough to fit onto wearable computers, e.g., inside of eyeglasses. In some instances, the digital camera may blend into the eyeglasses mold, and may not be immediately recognizable as a camera. Such eyeglasses may be indistinguishable or somewhat distinguishable from standard eyeglasses that do not contain a camera and/or a computer.

Further, the cost of data storage has decreased dramatically, and it is not uncommon for an average person in a developed nation to have access to enough digital storage to store months' and/or years' worth of video and pictures. As the cost of data storage has decreased dramatically, so too has the cost of processors to process that data, meaning that automation may be able to take an entire day's worth of surreptitious recording, and isolate those portions of the recording that captured persons, either specific persons or persons in general.

Accordingly, with technology, it is possible for a person to “wear” a computer, in the form of eyeglasses, watches, shirts, hats, or through a pocket-sized device carried by a person, e.g., a cellular telephone device. This wearable computer may be used to record people, e.g., to capture pictures, audio, video, or a combination thereof a person, without their knowledge. Thus, conversations that a person may assume to be private, may be recorded and widely distributed. Moreover, a person may be surreptitiously recorded while they are in a locker room, in a bathroom, or in a telephone booth. It may be difficult or impossible to tell when a person is being recorded. Further, once proliferation of these wearable computers with digital cameras becomes widespread, people must assume that they are under surveillance 100% of the time that they are not in their house.

Therefore, a need has arisen to provide systems that attempt to limit the capture and distribution of a person's personality rights. The present invention is directed to devices, methods, and systems that attempt to limit the capture and distribution of captured images of persons. Specifically, the present invention is directed to devices, methods, and systems that attempt to limit the capture and distribution of captured images of persons, implemented at a device that carries out the capturing of the image. In some embodiments, this device may be a wearable computer, but in other embodiments, any image capturing device or any device that has an image capturing device incorporated into its functionality may implement the devices, methods, and systems described herein.

The instant application is directed to devices, methods, and systems that have a capability to capture images, and in which the capture of those images may include capturing images of a person, persons, or portion(s) of a person for which a privacy beacon may be associated. The privacy beacon may be optical, digital, or other form (e.g., radio, electromagnetic, biomechanic, quantum-state, and the like), and may be detected through digital or optical operations, as discussed herein. The instant application describes devices, methods and systems that may interface with other parts of a larger system, which may be described in detail in this or other applications.

In one or more various aspects, a method includes but is not limited to acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, and decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may be implemented in machines, compositions of matter, or manufactures of systems, limited to patentable subject matter under 35 U.S.C. 101. The one or more related systems may include, but are not limited to, circuitry and/or programming for carrying out the herein-referenced method aspects. The circuitry and/or programming may be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer, and limited to patentable subject matter under 35 USC 101.

In one or more various aspects, a system includes, but is not limited to, means for acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, means for obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, means for procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, and means for decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, a system includes, but is not limited to, circuitry for acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, circuitry for obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, circuitry for procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, and decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, a computer program product, comprising a signal bearing medium, bearing one or more instructions including, but not limited to, one or more instructions for acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, one or more instructions for obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, one or more instructions for procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, and one or more instructions for decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, a device is defined by a computational language, such that the device comprises one or more interchained physical machines ordered for acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, one or more interchained physical machines ordered for obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, one or more interchained physical machines ordered for procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, and one or more interchained physical machines ordered for decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device.

In addition to the foregoing, various other method and/or system and/or program product aspects are set forth and described in the teachings such as text (e.g., claims and/or detailed description) and/or drawings of the present disclosure.

The foregoing is a summary and thus may contain simplifications, generalizations, inclusions, and/or omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is NOT intended to be in any way limiting. Other aspects, features, and advantages of the devices and/or processes and/or other subject matter described herein will become apparent by reference to the detailed description, the corresponding drawings, and/or in the teachings set forth herein.

DETAILED DESCRIPTION

Thus, in accordance with various embodiments, computationally implemented methods, systems, circuitry, articles of manufacture, ordered chains of matter, and computer program products are designed to, among other things, provide an interface for acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device, obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, and decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device.

The claims, description, and drawings of this application may describe one or more of the instant technologies in operational/functional language, for example as a set of operations to be performed by a computer. Such operational/functional description in most instances would be understood by one skilled the art as specifically-configured hardware (e.g., because a general purpose computer in effect becomes a special purpose computer once it is programmed to perform particular functions pursuant to instructions from program software (e.g., a high-level computer program serving as a hardware specification)).

Importantly, although the operational/functional descriptions described herein are understandable by the human mind, they are not abstract ideas of the operations/functions divorced from computational implementation of those operations/functions. Rather, the operations/functions represent a specification for massively complex computational machines or other means. As discussed in detail below, the operational/functional language must be read in its proper technological context, i.e., as concrete specifications for physical implementations.

The logical operations/functions described herein are a distillation of machine specifications or other physical mechanisms specified by the operations/functions such that the otherwise inscrutable machine specifications may be comprehensible to a human reader. The distillation also allows one of skill in the art to adapt the operational/functional description of the technology across many different specific vendors' hardware configurations or platforms, without being limited to specific vendors' hardware configurations or platforms.

Some of the present technical description (e.g., detailed description, drawings, claims, etc.) may be set forth in terms of logical operations/functions. As described in more detail herein, these logical operations/functions are not representations of abstract ideas, but rather are representative of static or sequenced specifications of various hardware elements. Differently stated, unless context dictates otherwise, the logical operations/functions will be understood by those of skill in the art to be representative of static or sequenced specifications of various hardware elements. This is true because tools available to one of skill in the art to implement technical disclosures set forth in operational/functional formats—tools in the form of a high-level programming language (e.g., C, java, visual basic), etc.), or tools in the form of Very high speed Hardware Description Language (“VHDL,” which is a language that uses text to describe logic circuits)—are generators of static or sequenced specifications of various hardware configurations. This fact is sometimes obscured by the broad term “software,” but, as shown by the following explanation, those skilled in the art understand that what is termed “software” is a shorthand for a massively complex interchaining/specification of ordered-matter elements. The term “ordered-matter elements” may refer to physical components of computation, such as assemblies of electronic logic gates, molecular computing logic constituents, quantum computing mechanisms, etc.

For example, a high-level programming language is a programming language with strong abstraction, e.g., multiple levels of abstraction, from the details of the sequential organizations, states, inputs, outputs, etc., of the machines that a high-level programming language actually specifies. See, e.g., Wikipedia, High-level programming language, http://en.wikipedia.org/wiki/High-level_programming_language (as of Jun. 5, 2012, 21:00 GMT). In order to facilitate human comprehension, in many instances, high-level programming languages resemble or even share symbols with natural languages. See, e.g., Wikipedia, Natural language, http://en.wikipedia.org/wiki/Natural_language (as of Jun. 5, 2012, 21:00 GMT).

It has been argued that because high-level programming languages use strong abstraction (e.g., that they may resemble or share symbols with natural languages), they are therefore a “purely mental construct” (e.g., that “software”—a computer program or computer programming—is somehow an ineffable mental construct, because at a high level of abstraction, it can be conceived and understood by a human reader). This argument has been used to characterize technical description in the form of functions/operations as somehow “abstract ideas.” In fact, in technological arts (e.g., the information and communication technologies) this is not true.

The fact that high-level programming languages use strong abstraction to facilitate human understanding should not be taken as an indication that what is expressed is an abstract idea. In fact, those skilled in the art understand that just the opposite is true. If a high-level programming language is the tool used to implement a technical disclosure in the form of functions/operations, those skilled in the art will recognize that, far from being abstract, imprecise, “fuzzy,” or “mental” in any significant semantic sense, such a tool is instead a near incomprehensibly precise sequential specification of specific computational machines—the parts of which are built up by activating/selecting such parts from typically more general computational machines over time (e.g., clocked time). This fact is sometimes obscured by the superficial similarities between high-level programming languages and natural languages. These superficial similarities also may cause a glossing over of the fact that high-level programming language implementations ultimately perform valuable work by creating/controlling many different computational machines.

The many different computational machines that a high-level programming language specifies are almost unimaginably complex. At base, the hardware used in the computational machines typically consists of some type of ordered matter (e.g., traditional electronic devices (e.g., transistors), deoxyribonucleic acid (DNA), quantum devices, mechanical switches, optics, fluidics, pneumatics, optical devices (e.g., optical interference devices), molecules, etc.) that are arranged to form logic gates. Logic gates are typically physical devices that may be electrically, mechanically, chemically, or otherwise driven to change physical state in order to create a physical reality of logic, such as Boolean logic.

Logic gates may be arranged to form logic circuits, which are typically physical devices that may be electrically, mechanically, chemically, or otherwise driven to create a physical reality of certain logical functions. Types of logic circuits include such devices as multiplexers, registers, arithmetic logic units (ALUs), computer memory, etc., each type of which may be combined to form yet other types of physical devices, such as a central processing unit (CPU)—the best known of which is the microprocessor. A modern microprocessor will often contain more than one hundred million logic gates in its many logic circuits (and often more than a billion transistors). See, e.g., Wikipedia, Logic gates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012, 21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide a microarchitecture that will carry out the instructions defined by that microprocessor's defined Instruction Set Architecture. The Instruction Set Architecture is the part of the microprocessor architecture related to programming, including the native data types, instructions, registers, addressing modes, memory architecture, interrupt and exception handling, and external Input/Output. See, e.g., Wikipedia, Computer architecture, http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012, 21:03 GMT).

The Instruction Set Architecture includes a specification of the machine language that can be used by programmers to use/control the microprocessor. Since the machine language instructions are such that they may be executed directly by the microprocessor, typically they consist of strings of binary digits, or bits. For example, a typical machine language instruction might be many bits long (e.g., 32, 64, or 128 bit strings are currently common). A typical machine language instruction might take the form “11110000101011110000111100111111” (a 32 bit instruction).

It is significant here that, although the machine language instructions are written as sequences of binary digits, in actuality those binary digits specify physical reality. For example, if certain semiconductors are used to make the operations of Boolean logic a physical reality, the apparently mathematical bits “1” and “0” in a machine language instruction actually constitute a shorthand that specifies the application of specific voltages to specific wires. For example, in some semiconductor technologies, the binary number “1” (e.g., logical “1”) in a machine language instruction specifies around +5 volts applied to a specific “wire” (e.g., metallic traces on a printed circuit board) and the binary number “0” (e.g., logical “0”) in a machine language instruction specifies around −5 volts applied to a specific “wire.” In addition to specifying voltages of the machines' configurations, such machine language instructions also select out and activate specific groupings of logic gates from the millions of logic gates of the more general machine. Thus, far from abstract mathematical expressions, machine language instruction programs, even though written as a string of zeros and ones, specify many, many constructed physical machines or physical machine states.

Machine language is typically incomprehensible by most humans (e.g., the above example was just ONE instruction, and some personal computers execute more than two billion instructions every second). See, e.g., Wikipedia, Instructions per second, http://en.wikipedia.org/wiki/Instructions_per_second (as of Jun. 5, 2012, 21:04 GMT). Thus, programs written in machine language—which may be tens of millions of machine language instructions long—are incomprehensible to most humans. In view of this, early assembly languages were developed that used mnemonic codes to refer to machine language instructions, rather than using the machine language instructions' numeric values directly (e.g., for performing a multiplication operation, programmers coded the abbreviation “mult,” which represents the binary number “011000” in MIPS machine code). While assembly languages were initially a great aid to humans controlling the microprocessors to perform work, in time the complexity of the work that needed to be done by the humans outstripped the ability of humans to control the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done over and over, and the machine language necessary to do those repetitive tasks was the same. In view of this, compilers were created. A compiler is a device that takes a statement that is more comprehensible to a human than either machine or assembly language, such as “add 2+2 and output the result,” and translates that human understandable statement into a complicated, tedious, and immense machine language code (e.g., millions of 32, 64, or 128 bit length strings). Compilers thus translate high-level programming language into machine language.

This compiled machine language, as described above, is then used as the technical specification which sequentially constructs and causes the interoperation of many different computational machines such that useful, tangible, and concrete work is done. For example, as indicated above, such machine language—the compiled version of the higher-level language—functions as a technical specification which selects out hardware logic gates, specifies voltage levels, voltage transition timings, etc., such that the useful work is accomplished by the hardware.

Thus, a functional/operational technical description, when viewed by one of skill in the art, is far from an abstract idea. Rather, such a functional/operational technical description, when understood through the tools available in the art such as those just described, is instead understood to be a humanly understandable representation of a hardware specification, the complexity and specificity of which far exceeds the comprehension of most any one human. With this in mind, those skilled in the art will understand that any such operational/functional technical descriptions—in view of the disclosures herein and the knowledge of those skilled in the art—may be understood as operations made into physical reality by (a) one or more interchained physical machines, (b) interchained logic gates configured to create one or more physical machine(s) representative of sequential/combinatorial logic(s), (c) interchained ordered matter making up logic gates (e.g., interchained electronic devices (e.g., transistors), DNA, quantum devices, mechanical switches, optics, fluidics, pneumatics, molecules, etc.) that create physical reality of logic(s), or (d) virtually any combination of the foregoing. Indeed, any physical object which has a stable, measurable, and changeable state may be used to construct a machine based on the above technical description. Charles Babbage, for example, constructed the first mechanized computational apparatus out of wood, with the apparatus powered by cranking a handle.

Thus, far from being understood as an abstract idea, those skilled in the art will recognize a functional/operational technical description as a humanly-understandable representation of one or more almost unimaginably complex and time sequenced hardware instantiations. The fact that functional/operational technical descriptions might lend themselves readily to high-level computing languages (or high-level block diagrams for that matter) that share some words, structures, phrases, etc. with natural language should not be taken as an indication that such functional/operational technical descriptions are abstract ideas, or mere expressions of abstract ideas. In fact, as outlined herein, in the technological arts this is simply not true. When viewed through the tools available to those of skill in the art, such functional/operational technical descriptions are seen as specifying hardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operational technical descriptions is at least twofold. First, the use of functional/operational technical descriptions allows near-infinitely complex machines and machine operations arising from interchained hardware elements to be described in a manner that the human mind can process (e.g., by mimicking natural language and logical narrative flow). Second, the use of functional/operational technical descriptions assists the person of skill in the art in understanding the described subject matter by providing a description that is more or less independent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists the person of skill in the art in understanding the described subject matter since, as is evident from the above discussion, one could easily, although not quickly, transcribe the technical descriptions set forth in this document as trillions of ones and zeroes, billions of single lines of assembly-level machine code, millions of logic gates, thousands of gate arrays, or any number of intermediate levels of abstractions. However, if any such low-level technical descriptions were to replace the present technical description, a person of skill in the art could encounter undue difficulty in implementing the disclosure, because such a low-level technical description would likely add complexity without a corresponding benefit (e.g., by describing the subject matter utilizing the conventions of one or more vendor-specific pieces of hardware). Thus, the use of functional/operational technical descriptions assists those of skill in the art by separating the technical descriptions from the conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth in the present technical description are representative of static or sequenced specifications of various ordered-matter elements, in order that such specifications may be comprehensible to the human mind and adaptable to create many various hardware configurations. The logical operations/functions disclosed herein should be treated as such, and should not be disparagingly characterized as abstract ideas merely because the specifications they represent are presented in a manner that one of skill in the art can readily understand and apply in a manner independent of a specific vendor's hardware implementation.

The term module, as used in the foregoing/following disclosure, may refer to a collection of one or more components that are arranged in a particular manner, or a collection of one or more general-purpose components that may be configured to operate in a particular manner at one or more particular points in time, and/or also configured to operate in one or more further manners at one or more further times. For example, the same hardware, or same portions of hardware, may be configured/reconfigured in sequential/parallel time(s) as a first type of module (e.g., at a first time), as a second type of module (e.g., at a second time, which may in some instances coincide with, overlap, or follow a first time), and/or as a third type of module (e.g., at a third time which may, in some instances, coincide with, overlap, or follow a first time and/or a second time), etc. Reconfigurable and/or controllable components (e.g., general purpose processors, digital signal processors, field programmable gate arrays, etc.) are capable of being configured as a first module that has a first purpose, then a second module that has a second purpose and then, a third module that has a third purpose, and so on. The transition of a reconfigurable and/or controllable component may occur in as little as a few nanoseconds, or may occur over a period of minutes, hours, or days.

In some such examples, at the time the component is configured to carry out the second purpose, the component may no longer be capable of carrying out that first purpose until it is reconfigured. A component may switch between configurations as different modules in as little as a few nanoseconds. A component may reconfigure on-the-fly, e.g., the reconfiguration of a component from a first module into a second module may occur just as the second module is needed. A component may reconfigure in stages, e.g., portions of a first module that are no longer needed may reconfigure into the second module even before the first module has finished its operation. Such reconfigurations may occur automatically, or may occur through prompting by an external source, whether that source is another component, an instruction, a signal, a condition, an external stimulus, or similar.

For example, a central processing unit of a personal computer may, at various times, operate as a module for displaying graphics on a screen, a module for writing data to a storage medium, a module for receiving user input, and a module for multiplying two large prime numbers, by configuring its logical gates in accordance with its instructions. Such reconfiguration may be invisible to the naked eye, and in some embodiments may include activation, deactivation, and/or re-routing of various portions of the component, e.g., switches, logic gates, inputs, and/or outputs. Thus, in the examples found in the foregoing/following disclosure, if an example includes or recites multiple modules, the example includes the possibility that the same hardware may implement more than one of the recited modules, either contemporaneously or at discrete times or timings. The implementation of multiple modules, whether using more components, fewer components, or the same number of components as the number of modules, is merely an implementation choice and does not generally affect the operation of the modules themselves. Accordingly, it should be understood that any recitation of multiple discrete modules in this disclosure includes implementations of those modules as any number of underlying components, including, but not limited to, a single component that reconfigures itself over time to carry out the functions of multiple modules, and/or multiple components that similarly reconfigure, and/or special purpose reconfigurable components.

Those skilled in the art will recognize that it is common within the art to implement devices and/or processes and/or systems, and thereafter use engineering and/or other practices to integrate such implemented devices and/or processes and/or systems into more comprehensive devices and/or processes and/or systems. That is, at least a portion of the devices and/or processes and/or systems described herein can be integrated into other devices and/or processes and/or systems via a reasonable amount of experimentation. Those having skill in the art will recognize that examples of such other devices and/or processes and/or systems might include—as appropriate to context and application—all or part of devices and/or processes and/or systems of (a) an air conveyance (e.g., an airplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., a car, truck, locomotive, tank, armored personnel carrier, etc.), (c) a building (e.g., a home, warehouse, office, etc.), (d) an appliance (e.g., a refrigerator, a washing machine, a dryer, etc.), (e) a communications system (e.g., a networked system, a telephone system, a Voice over IP system, etc.), (f) a business entity (e.g., an Internet Service Provider (ISP) entity such as Comcast Cable, Qwest, Southwestern Bell, etc.), or (g) a wired/wireless services entity (e.g., Sprint, Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territory even if components are located outside the territory. For example, in a distributed computing context, use of a distributed computing system may occur in a territory even though parts of the system may be located outside of the territory (e.g., relay, server, processor, signal-bearing medium, transmitting computer, receiving computer, etc. located outside the territory).

A sale of a system or method may likewise occur in a territory even if components of the system or method are located and/or used outside the territory. Further, implementation of at least part of a system for performing a method in one territory does not preclude use of the system in another territory

Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into an image processing system. Those having skill in the art will recognize that a typical image processing system generally includes one or more of a system unit housing, a video display device, memory such as volatile or non-volatile memory, processors such as microprocessors or digital signal processors, computational entities such as operating systems, drivers, applications programs, one or more interaction devices (e.g., a touch pad, a touch screen, an antenna, etc.), control systems including feedback loops and control motors (e.g., feedback for sensing lens position and/or velocity; control motors for moving/distorting lenses to give desired focuses). An image processing system may be implemented utilizing suitable commercially available components, such as those typically found in digital still systems and/or digital motion systems.

Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into a mote system. Those having skill in the art will recognize that a typical mote system generally includes one or more memories such as volatile or non-volatile memories, processors such as microprocessors or digital signal processors, computational entities such as operating systems, user interfaces, drivers, sensors, actuators, applications programs, one or more interaction devices (e.g., an antenna USB ports, acoustic ports, etc.), control systems including feedback loops and control motors (e.g., feedback for sensing or estimating position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A mote system may be implemented utilizing suitable components, such as those found in mote computing/communication systems. Specific examples of such components entail such as Intel Corporation's and/or Crossbow Corporation's mote components and supporting hardware, software, and/or firmware.

For the purposes of this application, “cloud” computing may be understood as described in the cloud computing literature. For example, cloud computing may be methods and/or systems for the delivery of computational capacity and/or storage capacity as a service. The “cloud” may refer to one or more hardware and/or software components that deliver or assist in the delivery of computational and/or storage capacity, including, but not limited to, one or more of a client, an application, a platform, an infrastructure, and/or a server The cloud may refer to any of the hardware and/or software associated with a client, an application, a platform, an infrastructure, and/or a server. For example, cloud and cloud computing may refer to one or more of a computer, a processor, a storage medium, a router, a switch, a modem, a virtual machine (e.g., a virtual server), a data center, an operating system, a middleware, a firmware, a hardware back-end, a software back-end, and/or a software application. A cloud may refer to a private cloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloud may be a shared pool of configurable computing resources, which may be public, private, semi-private, distributable, scaleable, flexible, temporary, virtual, and/or physical. A cloud or cloud service may be delivered over one or more types of network, e.g., a mobile communication network, and the Internet.

As used in this application, a cloud or a cloud service may include one or more of infrastructure-as-a-service (“IaaS”), platform-as-a-service (“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service (“DaaS”). As a non-exclusive example, IaaS may include, e.g., one or more virtual server instantiations that may start, stop, access, and/or configure virtual servers and/or storage centers (e.g., providing one or more processors, storage space, and/or network resources on-demand, e.g., EMC and Rackspace). PaaS may include, e.g., one or more software and/or development tools hosted on an infrastructure (e.g., a computing platform and/or a solution stack from which the client can create software interfaces and applications, e.g., Microsoft Azure). SaaS may include, e.g., software hosted by a service provider and accessible over a network (e.g., the software for the application and/or the data associated with that software application may be kept on the network, e.g., Google Apps, SalesForce). DaaS may include, e.g., providing desktop, applications, data, and/or services for the user over a network (e.g., providing a multi-application framework, the applications in the framework, the data associated with the applications, and/or services related to the applications and/or the data over the network, e.g., Citrix). The foregoing is intended to be exemplary of the types of systems and/or methods referred to in this application as “cloud” or “cloud computing” and should not be considered complete or exhaustive.

To the extent that formal outline headings are present in this application, it is to be understood that the outline headings are for presentation purposes, and that different types of subject matter may be discussed throughout the application (e.g., device(s)/structure(s) may be described under process(es)/operations heading(s) and/or process(es)/operations may be discussed under structure(s)/process(es) headings; and/or descriptions of single topics may span two or more topic headings). Hence, any use of formal outline headings in this application is for presentation purposes, and is not intended to be in any way limiting.

Throughout this application, examples and lists are given, with parentheses, the abbreviation “e.g.,” or both. Unless explicitly otherwise stated, these examples and lists are merely exemplary and are non-exhaustive. In most cases, it would be prohibitive to list every example and every combination. Thus, smaller, illustrative lists and examples are used, with focus on imparting understanding of the claim terms rather than limiting the scope of such terms.

Although one or more users maybe shown and/or described herein, e.g., inFIG. 1, and other places, as a single illustrated figure, those skilled in the art will appreciate that one or more users may be representative of one or more human users, robotic users (e.g., computational entity), and/or substantially any combination thereof (e.g., a user may be assisted by one or more robotic agents) unless context dictates otherwise. Those skilled in the art will appreciate that, in general, the same may be said of “sender” and/or other entity-oriented terms as such terms are used herein unless context dictates otherwise.

It is noted that “wearable computer” is used throughout this specification, and in the examples given, it is generally a wearable computer that captures images. However, this is merely for exemplary purposes. The same systems may apply to conventional digital cameras, and any other camera, including security cameras, surveillance cameras, motor vehicle mounted cameras, road/traffic cameras, cameras at automated teller machines, and the like.

Referring now toFIG. 1, in an embodiment, an entity, e.g., a user of a privacy beacon, e.g., user2105, e.g., a person, e.g., “Jules Caesar,” may be associated with a “Don't Capture Me” (hereinafter “DCM”) privacy beacon, e.g., DCM Beacon2110. In an embodiment, a DCM beacon may be active, e.g., may contain circuitry and be an active unit, e.g., something wearable, e.g., on a piece of clothing, or on a ring, or on a drone associated with the user. In an embodiment, the DCM beacon may be passive, e.g., it may be something that can be detected in the electromagnetic spectrum, or can be otherwise detected but does not contain any circuitry or advanced logic gates of its own. In an embodiment, the DCM beacon may be a combination of the two.

In an embodiment, a DCM beacon may be detectable by a machine or a human being (e.g., a stop sign painted on a user's forehead may be a DCM beacon). In an embodiment, a DCM beacon may be detectable by a particular type of machine, structure, or filter, and may be otherwise undetectable or difficult to detect through human senses. For example, in an embodiment, a DCM beacon may be seen using ultraviolet or infrared light, or a DCM beacon may emit light outside the visible spectrum. In an embodiment, a DCM beacon may be visible or detectable after a filter is applied, e.g., a DCM beacon may be visible after a red filter is applied, or after a transformation is applied to a captured image, e.g., a Fourier transformation.

In an embodiment, a DCM beacon may be detected optically. In another embodiment, a DCM beacon may be detected by sensing a different kind of wave emitted by a DCM beacon, e.g., a wave in the nonvisible electromagnetic spectrum, a sound wave, an electromagnetic wave, and the like. In an embodiment, a DCM beacon may use quantum entanglement (e.g., through use of an entanglement-based protocol, among others).

In an embodiment, a DCM beacon may transmit data, e.g., a terms of service for the user (e.g., user2105) for which the DCM beacon (e.g., DCM beacon2110) is associated or linked. In an embodiment, a DCM beacon may be encoded with a location of data, e.g., a web address of a server where terms of service for the user (e.g., user2105) for which the DCM beacon (e.g., DCM beacon2110) is associated.

In an embodiment, a DCM beacon may be provided by a drone, of any size, e.g., nanometers to full-sized aircraft, that is associated with the user.

In an embodiment, a DCM beacon may be provided by a piece of electronics that a user carries, e.g., a cellular telephone, tablet, watch, wearable computer, or otherwise.

In an embodiment, a DCM beacon may be embedded in the user, ingested by the user, implanted in the user, taped to the skin of the user, or may be engineered to grow organically in the user's body.

In an embodiment, a DCM beacon may be controlled by a magnetic field or other field emitted by a user, either through a user's regular electromagnetic field or through a field generated by a device, local or remote, associated with the user.

Referring again toFIG. 1, in an embodiment, a different user, e.g., a wearable computer user3105, may have a wearable computer3100. A wearable computer may be a pair of eyeglasses, a watch, jewelry, clothing, shoes, a piece of tape placed on the user's skin, it may be ingested by the user or otherwise embedded into the user's body. Wearable computer3100may be a piece of electronics carried by a user3105. Wearable computer3100may not be a “wearable” computer in a traditional sense, but may be a laptop computer, tablet device, or smartphone carried by a user. In an embodiment, wearable computer3100may not be associated with a user at all, but may simply be a part of a surveillance system, e.g., a security camera, or a camera at an Automated Teller Machine (“ATM”).

Wearable Computer That Captures the Image (FIGS. 1-I;1-J,1-N,1-O).

Referring now toFIG. 1, e.g.,FIG. 1-J, wearable computer3100may include a wearable computer image capturing device3110, e.g., a lens. Wearable computer image capturing device3110may include functionality to capture images, e.g., an image sensor, e.g., a charge-coupled device (“CCM”) or a complementary metal-oxide semiconductor (“CMOS”), an analog-to digital converter, and/or any other equipment used to convert light into electrons. Wearable computer image capturing device3110may capture the optical data, which may remain as light data, or may be converted into electrons through an image sensor, as raw data. This raw data, e.g., raw data2200may be captured by the optical image data acquiring module3120of wearable computer3100. Optical image data acquiring module3120may be configured to acquire an image, e.g., an image of user2105. As described above, a DCM beacon2110may be associated with user2105. In an embodiment, at this point in the operation of wearable computer3100, no processing has been performed on the raw image data2200.

Although not pictured here, wearable computer image capturing device3110may also include circuitry to detect audio (e.g., a microphone) and/or video (e.g., the ability to capture frames above a certain rate of frames per second). This circuitry and its related explanation have been omitted to maintain simplicity of the drawing, however, through this application, “raw image data2200” should be considered to also possibly include still pictures, video, and audio, in some embodiments.

Referring now toFIG. 1-I, in an embodiment, wearable computer3100then may transfer the raw/optical image data2200to an image path splitting module3130. This splitting path may be optical, e.g., a set of mirrors/lenses, for the case in which raw image data2200is still in optical form, or digital, e.g., through use of known electrical signal splitters. Image path splitting module3130may be implemented as hardware, software, or a combination thereof.

Referring again toFIG. 1, e.g.,FIG. 1-I, in an embodiment, the north (upper) branch, as illustrated inFIG. 1, transmits the raw image data2200to an image prior-to-processing encryption module3150. Image prior-to-processing encryption module3150may receive the raw image data2200. From there, image prior-to-processing encryption module3150may acquire an encryption key that is device-specific, e.g., wearable computer device specific encryption key3182. In an embodiment, wearable computer device-specific encryption key3182may be stored in wearable computer device memory3180, which also may include encrypted image storage3184, and a wearable computer user-specific encryption key3186. In another embodiment, device-specific encryption key3182may be retrieved from elsewhere, e.g., cloud storage. In another embodiment, device-specific encryption key3182may be generated in real time by the device. In another embodiment, device-specific encryption key3182may be generated in real time by the device based on random user input (e.g., the last five words spoken by the device and recorded).

In an embodiment, image prior-to-processing encryption module3150may generate encrypted image data2210. Encrypted image data2210may be stored in encrypted image storage3184of wearable computer device memory3180. In an embodiment, encrypted image data2210also may be transmitted to central server encrypted data and beacon metadata transmission module3170.

Referring again toFIG. 1-IandFIG. 1-N, in an embodiment, the south (lower) branch, as illustrated inFIG. 1, may transmit the raw image data2200to a DCM beacon detecting module3140. In an embodiment, DCM beacon detecting module3140may include one or more of optics-based DCM beacon detecting module3142, which may be configured to detect the DCM beacon in an optical signal (e.g., light). In an embodiment, DCM beacon detecting module3140may include digital image processing-based DCM beacon detecting module3144, which may be configured to detect the DCM beacon in a converted electron signal (e.g., data signal). In an embodiment, DCM beacon detecting module3140is configured to detect a presence or an absence of a DCM beacon, e.g., DCM beacon2110, associated with the entity (e.g., user2105, e.g., “Jules Caesar”), without performing any additional processing on the image, or releasing the image for other portions of wearable computer3100to use. In an embodiment, for example, raw image data2200is not stored in device memory of wearable computer3100in a form that is accessible to other applications and/or programs available to wearable computer3100or other computing devices that may communicate with wearable computer3100. For example, a user3105of wearable computer3100may not, at this stage in processing, capture the raw data2200and upload it to a social networking site, e.g., Facebook. In an embodiment, DCM beacon detecting module3140may be implemented in hardware, which may prevent users or third parties from bypassing the DCM beacon detecting module3140, without disassembling the device and physically altering the circuit/logic.

Referring now toFIG. 1-N, in an embodiment, the DCM beacon detecting module3140may detect the DCM beacon2110. For example, in the exemplary embodiment shown inFIG. 1, DCM beacon detecting module3140may detect the DCM beacon2110that is associated with user2105, e.g., Jules Caesar. Thus, DCM beacon detecting module3140now knows to lock the image data and prevent unencrypted image data from being accessed on the device. Although not shown in this example, if the DCM beacon had not been found, then in an embodiment, the image data2200would have been released for use by the device, e.g., for uploading to social network or cloud storage, for example.

In an embodiment, the detected DCM beacon2110associated with Jules Caesar may be transmitted to DCM beacon metadata generating module3160. DCM beacon metadata generating module3160may generate metadata based on the detection of the beacon. The metadata may be as simple as “the image data contains a privacy beacon,” e.g., Boolean data. In an embodiment, the metadata may be more complex, and may identify the user associated with the privacy beacon, e.g., the metadata may describe “A privacy beacon associated with Jules Caesar has been found in the image data.” In another embodiment, the metadata may include the terms of service associated with the personality rights of Jules Caesar, an example of which terms of service will be provided in more detail herein.

In an embodiment, the detected DCM beacon2110may be very simple (e.g., optically detectable), and to obtain/generate metadata associated with the detected DCM beacon2110, DCM beacon metadata generating module3160may include a DCM server contacting module3162, which may contact one or more entities to obtain more information regarding the DCM beacon2110. The DCM beacon metadata generating module3160may, in some embodiments, transmit the DCM beacon, or the image in which the DCM beacon was captured, to the external entity, in order to obtain more accurate data. For example, the DCM server contacting module3162may contact service term management server5000, which may have DCM beacon registry5010, which will be discussed in more detail further herein.

In an embodiment, DCM beacon metadata generating module3160may generate the DCM beacon metadata2230, and transfer DCM beacon metadata2230to central server encrypted data and beacon metadata transmission module3170.

Referring again toFIG. 1, e.g.,FIG. 1-I, central server encrypted data and beacon metadata transmission module3170may receive the encrypted image data2210and the DCM beacon metadata2230(e.g., seeFIG. 1-N). In an embodiment, central server encrypted data and beacon metadata transmission module3170may facilitate the transmission of encrypted image data2210and DCM beacon metadata2230to a server, e.g., wearable computer encrypted data receipt and determination server4000, which will be discussed in more detail herein. In an embodiment, central server encrypted data and beacon metadata transmission module3170may include one or more of DCM beacon metadata transmission module3172, which may be configured to transmit the DCM beacon metadata2230, and encrypted data transmission module3174, which may be configured to transmit the encrypted image data2210.

Referring again toFIG. 1, e.g.,FIG. 1-H, in an embodiment, a system may include a wearable computer server, e.g., wearable computer encrypted data receipt and determination server4000. In an embodiment, a wearable computer server may be provided by a manufacturer of the wearable device3100. In an embodiment, a wearable computer server may be provided by a developer of one or more software applications for the wearable device3100. In an embodiment, wearable computer server4000may not have a direct relationship with wearable device3100prior to receiving the encrypted image data and the DCM beacon metadata2230, as will be discussed in more detail herein. In an embodiment, a wearable computer server4000may be implemented at a home computer of a user, for example, and may communicate only with wearable devices that are associated with that user. In another embodiment, a wearable computer server4000may communicate with many wearable devices3100, which may or may not have some relationship. In an embodiment, wearable computer server4000may communicate with one or more wearable devices3100through use of a communication network, which may use any known form of device communication. In an embodiment, wearable computer server4000may be chosen by wearable device3100, either due to proximity or due to one or more properties or characteristics of wearable computer server4000. In an embodiment, wearable computer server4000may be free to agree or disagree to process DCM beacon and image data received from various wearable devices3100. In an embodiment, wearable computer server4000may be distributed across many computers and/or servers.

In an embodiment, wearable computer encrypted data receipt and determination server4000may include an encrypted data and beacon metadata reception module4100. Encrypted data and beacon metadata reception module4100may receive encrypted image data2210and DCM beacon metadata2230from wearable computer3100, e.g., central server encrypted data and beacon metadata transmission module3170. In an embodiment, encrypted data and beacon metadata reception module4100may include a DCM beacon metadata reception module4104. DCM beacon metadata reception module4104may be configured to acquire a privacy metadata, e.g., DCM beacon metadata2230, corresponding to a detection of a DCM beacon, e.g., DCM beacon2110, in the one or more images captured by the image capture device, e.g., wearable computer3100. In an embodiment, encrypted data and beacon metadata reception module4100may include encrypted data reception module4102. In an embodiment, encrypted data reception module4102may be configured to acquire one or more of a block of encrypted data corresponding to one or more images that previously have been encrypted, e.g., encrypted image data2210. In an embodiment, encrypted data module4102may transmit, or facilitate the transmission of, encrypted image data2210to an entity that will perform a secondary detection of the privacy beacon, e.g., DCM beacon detection test duplicating server4800, which will be discussed in more detail further herein.

Referring again toFIG. 1-H, in an embodiment, encrypted data and beacon metadata reception module4100may transmit the received DCM beacon metadata to DCM beacon metadata reading module4120. If the DCM beacon metadata2230indicates that a DCM beacon was not found, then, in an embodiment, processing may transfer to module4220, which will be discussed in more detail further herein. In the example shown inFIG. 1, the DCM beacon2110associated with Jules Caesar was found, and the DCM beacon metadata2230indicates this state to DCM beacon metadata reading module4120.

Referring now toFIG. 1-G, in an embodiment, when the presence of the DCM beacon2110is determined through the DCM beacon metadata, e.g., DCM beacon metadata2230, then a DCM beacon TOS retrieval module4122may retrieve term data from a location, which may be a remote location, e.g., a DCM beacon management server5100, which will be discussed in more detail further herein. In an embodiment, DCM beacon TOS retrieval module4122may retrieve term data that includes a terms of service that specifies one or more conditions in which the image containing the DCM beacon2110may be used. In an embodiment, the TOS may also specify one or more penalties for using the personality rights that may be associated with the image, without acquiring permission or paying a licensing fee prior to releasing or utilizing the image. In an embodiment, the TOS also may include language forcing the entity that viewed the privacy beacon to accept the TOS upon viewing of the beacon. The TOS will be described in more detail with respect to modules5000and5100.

Referring again toFIG. 1-G, in an embodiment, wearable computer encrypted data receipt and determination server4000also may include an encrypted data value calculation module4130. Encrypted data value calculation module4130may use one or more algorithms or other methods of inducing or deducing an estimate regarding how much advertising or other revenue may be garnered by using the images containing the entity associated with the privacy beacon. For example, in an embodiment, encrypted data value calculation module4130may include a facial recognition program to recognize the person or persons associated with the beacon. In another embodiment, however, this may not be necessary, because the DCM beacon metadata and/or the ToS may identify the person. In an embodiment, encrypted data value calculation module4130may use various heuristics to calculate ad revenue, e.g., based on models used by popular advertising methods, or based on prior releases of images of the person associated with the DCM beacon2110. In an embodiment, module4130may use social networking to acquire a focus group and test the image on the focus group, in order to assist in revenue determination. For example, in the example shown inFIG. 1, the image in question is of Jules Caesar, who is the reclusive leader of the Roman Empire, and so the ad revenue generated from having an actual picture of Jules Caesar, or a video of Jules Caesar drinking a mead-and-tonic, may have high net value.

Referring again toFIG. 1-G, in an embodiment, the ToS acquired from DCM beacon TOS retrieval module4122, and the encrypted data valuation calculated from encrypted data value calculation module4130may be sent to release of encrypted data determination module4140. Release of encrypted data determination module4140may make a determination, at least partly based on the acquired metadata, and at least partly based on a value calculation based on the representation of the feature of the person associated with the DCM beacon2110(e.g., Jules Caesar drinking a mead-and-tonic). That determination may be regarding whether to allow an action, e.g., processing, decryption, distribution, editing, releasing, sharing, saving, posting to a social network, and the like, of the image. In an embodiment, the decision may be based on whether the potential advertising revenue outweighs the potential damages retrieved from the terms of service. In an embodiment, this calculation may be a strict number comparison (e.g., is “revenue” greater than “damages”). In an embodiment, the calculation may include more complex factors, e.g., likelihood of success on a damages claim, likelihood that revenues will increase, secondary revenue factors from increased traffic and/or brand awareness, and the like. In addition, in an embodiment, the comparison may not be strictly less than/greater than, e.g., in a risk adverse algorithm, if the numbers are close, then the determination may be to not release the encrypted data, even if the potential ad revenue is calculated as larger than the potential damages by a small amount.

Referring again toFIG. 1-G, if the determination made by release of encrypted data determination module4140is “NO,” e.g., the potential revenue is less than the potential damages, then the encrypted data2210is moved to an encrypted data holding and/or quarantine module4150. In an embodiment, the data from encrypted data holding and/or quarantine module4150is deleted after a predetermined time period, e.g., seven days. In an embodiment, the data is simply stored, encrypted and locked away. In an embodiment, the encrypted image data2210may be transmitted to an ad replacement value determination server4400, shown inFIG. 1-F, which will be discussed in more detail herein.

Referring again toFIG. 1-G, if the determination made by release of encrypted data determination module4140is “YES,” e.g., the potential revenue is more than the potential damages, then the encrypted data2210is transferred to encrypted data decryption enabling module4152, shown inFIG. 1-H. In an embodiment, encrypted data decryption enabling module4152may be configured to determine whether to perform decryption of at least a portion of the encrypted data2210based on the result from module4140by transmitting the encrypted image data2210to wearable computer acquired encrypted data decryption and re-encryption server4200, which will be discussed in more detail.

Wearable Computer Acquired Encrypted Data Decryption and Re-Encryption Server4200(FIGS. 1-Land1-M)

Referring now toFIG. 1-M, in an embodiment, the system may include wearable computer acquired encrypted data decryption and re-encryption server4200. In an embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may be a portion of wearable computer server4000. In an embodiment, however, wearable computer acquired encrypted data decryption and re-encryption server4200may be a different server than wearable computer server4000, and may be controlled by a different entity. For example, in an embodiment, the owner of the wearable computer3100hardware may control wearable computer server4000. After the decision is made to decrypt the data at the wearable computer server4000, control may be handed off to a different server in control of software on the wearable computer, e.g., software that handles pictures taken by the wearable computer3100. In another embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may be controlled by a social networking/media site, e.g., Facebook, who may have an agreement to acquire the image data at the same time as the device.

Referring again toFIG. 1-M, in an embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may include encrypted data acquiring module4210, which may acquire the encrypted image data2210from the wearable computer server4000. In an embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may include a privacy metadata acquiring module4220, which may acquire privacy metadata from module4120, if the DCM beacon was never detected and the image is free to be used. For example, in an embodiment, image data with no DCM beacon may be treated similarly to image data with a DCM beacon, but that has been determined to have an advertising value greater than a potential damages value. For example, in an embodiment, image data with no DCM beacon may be treated as image data with potential damages value of zero.

Referring again toFIG. 1-M, in an embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may include data indicating profitability of image with DCM beacon acquiring module4230, which may receive data from module4150of wearable computer server4000indicating that the image should be decrypted regardless of the DCM beacon because of its potential profitability.

Referring again toFIG. 1-M, in an embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may include image data decryption preparation module4240, which may receive data from one or more of data indicating profitability of image with DCM beacon acquiring module4230, encrypted data acquiring module4210, and privacy metadata acquiring module4220. In an embodiment, module4240may prepare the image or images for decryption, e.g., perform pre-processing, check image integrity, reconfirm the privacy beacon calculations, and the like.

Referring now toFIG. 1-L, wearable computer acquired encrypted data decryption and re-encryption server4200may include device-specific key retrieving module4250which may retrieve the device-specific key used to encrypt/decrypt the encrypted image data2210. In an embodiment, device-specific key retrieving module4250may include a device-specific key retrieving from device module4252, which may be configured to retrieve the device-specific key directly from the device that encrypted the image, e.g., wearable computing device3100. In an embodiment, device-specific key retrieving module4250may include a device-specific key retrieving from server module4254, which may be configured to retrieve the device-specific key from a server, e.g., from wearable computer encrypted data receipt and determination server400, or from DCM beacon detection test duplicating server4800, or from another server not depicted inFIG. 1.

Referring again toFIG. 1-L, in an embodiment, image data decryption with device-specific key module4260may take the device-specific key retrieved from module4250, and apply it to the encrypted image data2210to generate decrypted image data2280, as shown by the icon with the unlocked lock inFIG. 1-L.

Referring again toFIG. 1-L, the image data has been decrypted. However, to protect security, in some embodiments, the data may be re-encrypted with a key that is not tied to a specific device, but may be tied to a specific user of the device, e.g., the key may be related to user3105, rather than wearable device3100. This embodiment will be described in more detail herein. This embodiment allows the re-encrypted data to be securely sent to a different device belonging to the user, e.g., a smart TV, a home computer, a video game system, or another portable electronic device, e.g., a cellular smartphone. In an embodiment, the re-encryption with a user specific key may be omitted.

In an embodiment, wearable computer acquired encrypted data decryption and re-encryption server4200may include a user-specific key retrieving module4270, that may be configured to obtain, through generation, acquisition, reception, or retrieval, of a user-specific encryption key. The user-specific encryption key may be delivered to image data encrypting with user-specific key module4280, which, in an embodiment, also may receive the decrypted image data2280.

Referring again toFIG. 1-L, in an embodiment, image data encrypting with user-specific key module4280may be configured to encrypt the block of decrypted data through use of a unique user code that is related to the user3105of the wearable device3100. The again-encrypted image data then may be transferred to encrypted image data transmitting module4290. In an embodiment, encrypted image data transmitting module4290may transmit the image data that has been encrypted with a user-specific key to one or more other devices, which will be discussed in more detail herein.

Computing Device that Receives the Image Data (FIGS. 1-Sand1-T).

Referring now toFIG. 1-S, in an embodiment, the system may include a computing device3200, which may be a wearable computer or other device. In an embodiment, computing device3200may be the same as wearable computer3100, but it does not necessarily have to be the same. In an embodiment, computing device3200receives the image data. In an embodiment, as described above, the received image data has been encrypted with a user-specific code. Thus, in such an embodiment, computing device3200may be associated with user3105of the wearable computing device3100. For example, a user3105may have a wearable computing device3100that captures images of people. After processing those images at the server4000, for example, the images, which, in some embodiments, now may be encrypted with a user-specific code, may be transmitted to computing device3200, which may be the user3105's home media center back at her house. In another embodiment, computing device3200may be user3105's laptop device, or user3105's smartphone or tablet device. And, as previously mentioned, in another embodiment, computing device3200may simply be the user3105's wearable computing device3100that captured the images originally.

In an embodiment, the computing device3200and the wearable computing device3100pictured inFIG. 1are the same device. In an embodiment, the encryption, transmission to a server, decryption, and transmission back, may occur invisibly to the user3105, e.g., to the user3105of the wearable computing device3100, the images are available to her after they are recorded and saved, with a delay that is not specified. In some embodiments, the user3105may not be informed of the path taken by the captured image data.

In an embodiment, wearable computing device3100may include an encrypted image data receiving module3210configured to acquire the data encrypted by the user-specific key code from encrypted image data transmitting module4290of wearable computer4200. In an embodiment, computing device3200may include image data release verification acquiring module3220, which may be configured to determine that the images received from the encrypted image data transmitting module4290of wearable computer4200have been approved for release and/or use. In an embodiment, the determination may be made based on the ground that the images are encrypted with a user-specific key rather than a device specific key, if it is possible to tell from the encrypted information (e.g., in some embodiments, different types of encryption that may leave a different “signature” may be used). In an embodiment, the determination may be made by again analyzing the image data. In an embodiment, image data release verification acquiring module3220may include encrypted image data analysis module3222which may perform analysis on the encrypted image data, including, but not limited to, reading metadata attached to the encrypted image data, to verify that the received encrypted image data is approved for release and/or processing. In an embodiment, image data release verification acquiring module3220may include release verification data retrieving module3224, which may be configured to obtain release verification data from the device that performed the verification, e.g., server4000, or from a different device.

Referring now toFIG. 1-T, in an embodiment, computing device3200may include device memory3280. Device memory3280may store the wearable computer user-specific encryption/decryption key3286, which may be used to decrypt the received encrypted image data. In an embodiment, device memory3280also may include encrypted image storage3284, which may include one or more image data, which may be encrypted.

Referring again toFIG. 1-S, in an embodiment, computing device3200may include user-specific decryption key obtaining module3230, which may obtain the user-specific encryption/decryption key. In an embodiment, user-specific decryption key obtaining module3230may include encryption/decryption key external source obtaining module3232, which may be configured to obtain the encryption/decryption key from an external source, e.g., server4000. In an embodiment, user-specific decryption key obtaining module may include encryption/decryption key memory retrieving module3234, which may be configured to retrieve the encryption/decryption key from device memory3280of computing device3200.

Referring again toFIG. 1-S, in an embodiment, computing device3200may include image decryption module3240, which may use the user-specific encryption/decryption key to decrypt the image data. In an embodiment, the decrypted image data then may be sent to decrypted image release module3250, where the clear image data may be accessed by the device, and transmitted to other locations, posted to social networking or cloud storage, be shared, manipulated, saved, edited, and otherwise have open access to the decrypted image data.

Ad Replacement Value Determination Server (FIG. 1-F).

Referring back toFIG. 1-G, as discussed briefly above, release of encrypted data determination module4140may determine not to release the encrypted data, which may be stored in an encrypted data holding and/or quarantine module4150. In an embodiment, the encrypted data and the DCM beacon may be transmitted to an ad replacement value determination server, as shown inFIG. 1-F.

Referring now toFIG. 1-F, in an embodiment, the system may include an ad replacement value determination server4400. Ad replacement value determination server4400may take the encrypted image data and determine if there is a way to monetize the images such that the monetization may outweigh the potential damages. For example, ad replacement value determination server4400may calculate potential earnings and limited damages liability, if, for example, an entity with the DCM beacon, e.g., Jules Caesar, is instead shown with an advertisement where his head would normally be. In an embodiment, ad replacement value server may be controlled by a different entity than server4000, and there may be an agreement in place for the ad replacement value determination server4400to receive encrypted data for which the server4000decides it does not want to allow distribution. For example, ad replacement value server4400may be run by a smaller social networking site that cares less about potential damages because they have fewer assets, or are less risk-averse. In another embodiment, ad replacement value determination server4400may be part of server4000, and it may be a practice of server4000to send an encrypted image for further analysis after the server4000determines that the image is not likely to be profitable without modification.

Referring again toFIG. 1-F, in an embodiment, ad replacement value determination server4400may include a DCM beacon metadata reception module4410configured to receive the DCM beacon metadata from the wearable computer encrypted data receipt and determination server4000. In an embodiment, ad replacement value determination server4400may include an encrypted data reception module4420that may be configured to receive the encrypted data from the wearable computer encrypted data receipt and determination server4000, e.g., from the encrypted data holding module4150.

Referring again toFIG. 1-F, in an embodiment, ad replacement value determination server4400may include a DCM beacon term acquiring module4430, which may acquire one or more terms of service from service term management server5000and/or DCM beacon management server5100, similarly to DCM beacon terms-of-service retrieval module4122of wearable computer encrypted data receipt and determination server4000. In an embodiment, DCM beacon term acquiring module may include DCM beacon remote retrieval module4432. In an embodiment, DCM beacon term acquiring module may be configured to retrieve term data from a remote location, e.g., service term management server5000, which term data may correspond to a term of service associated with a release of image data that includes the person with which the DCM beacon is associated, e.g., Jules Caesar.

Referring again toFIG. 1-F, in an embodiment, ad replacement value determination server4400may include an encrypted data value calculation with standard ad placement module4440. In an embodiment, standard ad placement module4440may perform a similar calculation as encrypted data value calculation module4130of wearable computer encrypted data receipt and determination server4000. In an embodiment, for example, encrypted data value calculation with standard ad placement module4440may calculate whether an estimated advertising revenue from one or more advertisement images placed in the encrypted image data will be greater than an estimated potential liability for distribution of the images. In an embodiment, the estimated potential liability is based at least in part on the terms of service which may be retrieved by the DCM beacon term acquiring module4430.

Referring again toFIG. 1-F, in an embodiment, ad replacement value determination server4400may include encrypted image data modification with intentionally obscuring ad placement module4450. In an embodiment, encrypted image data modification with intentionally obscuring ad placement module4450may be configured to modify the encrypted image data (e.g., which, in some embodiments, may require limited decryption and then re-encryption) by replacing one or more areas associated with the entity related to the DCM beacon, e.g., Jules Caesar's face (e.g., or in another embodiment, Jules Caesar's genitalia, if, e.g., it was a naked picture of Jules Caesar), with one or more advertisement images.

Referring again toFIG. 1-F, in an embodiment, ad replacement value determination server4400may include modified encrypted data value calculation with intentionally obscuring ad placement module4460. In an embodiment, modified encrypted data value calculation with intentionally obscuring ad placement module4460may be configured to calculate an estimated advertising revenue from the modified image data. In an embodiment, the modified image data then may be distributed through modified encrypted data distributing module4470.

Referring now toFIG. 1-E, in an embodiment, a system may include tracking server9000. Tracking server9000may be configured to log use of a “Don't Capture Me” (hereinafter “DCM”) beacon by one or multiple users. In an embodiment, tracking server9000may track active DCM beacons, e.g., beacon2110, through communication with said one or more beacons. In an embodiment, tracking server may track DCM beacons through other means, e.g., social networking and the like. The DCM beacon does not need to be an active DCM beacon in order to be tracked by tracking server9000.

In an embodiment, tracking server9000may include deployment of one or more active and/or passive DCM beacons monitoring module9010. Deployment of one or more active and/or passive DCM beacons monitoring module9010may include one or more of active DCM beacon monitoring module9012and passive DCM beacon monitoring/data gathering module9020. In an embodiment, passive DCM beacon monitoring/data gathering module9020may gather data about the passive DCM beacon by observing it, e.g., through satellite video capture, through other image capturing devices, e.g., phone cameras, security cameras, laptop webcams, and the like, or through other means. In an embodiment, passive DCM beacon monitoring/data gathering module9020may include user input module9022, which may receive an indication from a user, e.g., a switch flipped on a user's cell phone, indicating that the user is using the DCM beacon. In an embodiment, passive DCM beacon monitoring/data gathering module9020may include a device status module which tracks a device with which the passive DCM beacon is associated, e.g., a wearable computer that is a shirt, or a cellular phone device in the pocket. In an embodiment, passive DCM beacon monitoring/data gathering module9020may include a social media monitoring module that monitors posts on social networking sites to determine if the DCM beacon is being used, and a location of the user.

Referring again toFIG. 1-E, in an embodiment, tracking server9000may include a record of the deployment of the one or more active and/or passive DCM beacons storing module9030, which may be configured to store a record of usage and/or detection logs of the DCM beacons that are monitored. In an embodiment, record of the deployment of the one or more active and/or passive DCM beacons storing module9030may store a record of the deployment in deployment record storage9032. In an embodiment, record of the deployment of the one or more active and/or passive DCM beacons storing module9030may transmit all or portions of the recorded record through record of the deployment of one or more active and/or passive DCM beacons transmitting module9040.

Service Term Management Server5000(FIG. 1-A)

Referring now toFIG. 1-A, in an embodiment, the system may include service term management server5000, which may manage terms of service that are associated with a DCM beacon and/or a person. In an embodiment, service term management server5000may include a DCM beacon registry5010. In an embodiment, the DCM beacon registry5010may include one or more of a user's name, e.g., Jules Caesar, a terms of service associated with Jules Caesar, which may be custom to Jules Caesar, or may be a generic terms of service that is used for many persons, and various representations of portions of Jules Caesar, e.g., likeness, handprint, footprint, voiceprint, pictures of private areas, and the like.

Referring again toFIG. 1-A, in an embodiment, the system may include a terms of service generating module5020. Terms of service generating module5020may create a terms of service for the user Jules Caesar. A sample Terms of Service is shown in FIG.1-A and is reproduced here. It is noted that this is a condensed Terms of Service meant to illustrate an exemplary operation of the system in the environment, and accordingly, several necessary legal portions may be omitted. Accordingly, the example Terms of Service should not be considered as a binding, legal document, but rather a representation of what the binding, legal document would look like, that would enable one skilled in the art to create a full Terms of Service.

Exemplary Terms of Service for User2105(Jules Caesar)

1. By capturing an image of any part of the user Jules Caesar (hereinafter “Image”), or providing any automation, design, resource, assistance, or other facilitation in the capturing of the Image, you agree that you have captured these Terms of Service and that you acknowledge and agree to them. If you cannot agree to these Terms of Service, you should immediately delete the captured Image. Failure to do so will constitute acceptance of these Terms of Service.

2. The User Jules Caesar owns all of the rights associated with the Image and any representation of any part of Jules Caesar thereof;

3. By capturing the Image, you agree to provide the User Jules Caesar just compensation for any commercialization of the User's personality rights that may be captured in the Image.

4. By capturing the Image, you agree to take all reasonable actions to track the Image and to provide an accounting of all commercialization attempts related to the Image, whether successful or not.

5. By capturing the Image, you accept a Liquidated Damages agreement in which unauthorized use of the Image will result in mandatory damages of at least, but not limited to, $1,000,000.

In an embodiment, terms of service generating module may include one or more of a default terms of service storage module5022, a potential damage calculator5024, and an entity interviewing for terms of service generation module. In an embodiment, default terms of service storage module5022may store the default terms of service that are used as a template for a new user, e.g., when Jules Caesar signs up for the service, this is the terms of service that is available to him. In an embodiment, potential damage calculator5024may determine an estimate of how much in damages that Jules Caesar could collect for a breach of his personality rights. In an embodiment, for example, potential damage calculator may search the internet to determine how much Jules Caesar appears on social media, blogs, and microblog (e.g., Twitter) accounts. In an embodiment, entity interviewing for terms of service generation module5026may create an online questionnaire/interview for Jules Caesar to fill out, which will be used to calculate potential damages to Jules Caesar, e.g., through determining Jules Caesar's net worth, for example.

In an embodiment, service term management server5000may include terms of service maintenance module5030, which may maintain the terms of service and modify them if, for example, the user becomes more popular, or gains a larger online or other presence. In an embodiment, terms of service maintenance module5030may include one or more of a social media monitoring module5042, that may search social networking sites, and an entity net worth tracking module5034that may have access to the entity's online bank accounts, brokerage accounts, property indexes, etc., and monitor the entity's wealth.

In an embodiment, serviced term management server5000may include a use of representations of an entity detecting module5040. In an embodiment, use of representations of an entity detecting module5040may include one or more of a social media monitoring module5042, a public photo repository monitoring module5044, and a public blog monitoring module5046. In an embodiment, use of representations of an entity detecting module5040may track uses of representations, e.g., images, of the user Jules Caesar, to try to detect violations of the terms of service, in various forums.

Referring now toFIG. 1-C, in an embodiment, the system may include a DCM beacon management server5100, which may be configured to manage the DCM beacon associated with a user, e.g., DCM beacon2110for user2105, e.g., Jules Caesar. In an embodiment, DCM beacon management server5100and service term management server5000may be the same server. In another embodiment, DCM beacon management server5100and service term management server5000may be hosted by different entities. For example, a specialized entity may handle the terms of service generation, e.g., a valuation company that may be able to determine a net “social network” worth of a user, e.g., Jules Caesar, and use that to fashion the terms of service.

Referring again toFIG. 1-C, in an embodiment, DCM beacon management server5100may include DCM beacon communication with entity wanting to avoid having their image captured module5110. DCM beacon communication with entity wanting to avoid having their image captured module5110may be configured to communicate with a user, e.g., user2105, e.g., Jules Caesar, and may handle the creation, generation, maintenance, and providing of the DCM beacon2110to Jules Caesar, whether through electronic delivery or through conventional delivery systems (e.g., mail, pickup at a store, etc.). In an embodiment, DCM beacon communication with entity wanting to avoid having their image captured module5110may include one or more of DCM beacon transmission module5112, DCM beacon receiving module5114, and DCM beacon generating module5116.

In an embodiment, DCM beacon management server5100may include entity representation acquiring module5120. Entity representation acquiring module5100may be configured to receive data regarding one or more features of the user that will be associated with the DCM beacon. For example, the user might upload pictures of his body, face, private parts, footprint, handprint, voice recording, hairstyle, silhouette, or any other representation that may be captured and/or may be deemed relevant.

In an embodiment, DCM beacon management server5100may include DCM beacon association with one or more terms of service and one or more entity representations module5130. In an embodiment, DCM beacon association with one or more terms of service and one or more entity representations module5130may be configured to, after generation of a DCM beacon, obtain a terms of service to be associated with that DCM beacon. In an embodiment, the terms of service may be received from service term management server5000.

In an embodiment, DCM beacon management server5100may include a DCM beacon capture detecting module5140. DCM beacon capture detection module5140may detect when a DCM beacon is captured, e.g., if it is an active beacon, or it may receive a notification from various servers (e.g., server4000) and/or wearable devices (e.g., wearable device3100) that a beacon has been detected, if it is a passive DCM beacon.

In an embodiment, when a DCM beacon is detected, DCM beacon management server5100may include terms of service associated with DCM beacon distributing module, which may be configured to provide the terms of service associated with the DCM beacon to an entity that captured the image including the DCM beacon, e.g., to module4122of wearable computer encrypted data receipt and determination server4000, or DCM beacon remote retrieval module4430of ad replacement value determination server4400, for example.

Wearable Computer with Optional Paired Personal Device3300(FIGS. 1-Qand1-R)

Referring now toFIG. 1-R, in an embodiment, the system may include a wearable computer3300. Wearable computer3300may have additional functionality beyond capturing images, e.g., it may also store a user's contact list for emails, phone calls, and the like. In another embodiment, wearable computer3300may be paired with another device carried by a user, e.g., the user's smartphone device, which stores the user's contact list. As will be described in more detail herein, wearable computer3300operates similarly to wearable computer3100, except that entities with DCM beacons are obscured, unless they have a preexisting relationship with the user. It is noted that DCM beacon detection and encryption may operate similarly in wearable computer3300as in wearable computer3100, and so substantially duplicated parts have been omitted.

Referring again toFIG. 1-R, in an embodiment, wearable computer3300may include an image capturing module3310, which may capture an image of Jules Caesar, who has DCM beacon “A”, Beth Caesar, who has DCM beacon “B”, and Auggie Caesar, who has no DCM beacon. In an embodiment, wearable computer3300may include an image acquiring module3320, which may be part of image capturing module3310, to acquire one or more images captured by an image capture device, e.g., the image of Jules Caesar, Beth Caesar, and Auggie Caesar.

In an embodiment, wearable computer3300may include an entity identification module3330, which may perform one or more recognition algorithms on the image in order to identify persons in the image. Entity identification module may use known facial recognition algorithms, for example, or may ask the user for input, or may search the internet for similar images that have been identified, for example.

Referring again toFIG. 1-R, in an embodiment, wearable computer3300may include preexisting relationship data retrieval module3340, which may retrieve names of known persons, e.g., from a device contact list, e.g., device contact list3350. In the example shown inFIG. 1, Jules Caesar is in the contact list of the device3300. It is noted that the device contact list3350may be stored on a different device, e.g., the user's cellular telephone.

Referring now toFIG. 1-Q, in an embodiment, wearable computer3300may include data indicating an identified entity from the image data has a preexisting relationship obtaining module3360, which, in an embodiment, may obtain data indicating that one of the entities recorded in the image data (e.g., Jules Caesar) is in the user's contact list.

Referring again toFIG. 1-Q, in an embodiment, wearable computer3300may include entities with preexisting relationship marking to prevent obfuscation module3370. In an embodiment, entities with preexisting relationship marking to prevent obfuscation module3370may attach a marker to the image, e.g., a real marker on the image or a metadata attachment to the image, or another type of marker, that prevents obfuscation of that person, regardless of DCM beacon status, because they are in the user's contact list.

Referring again toFIG. 1-Q, in an embodiment, wearable computer3300may include unknown entities with DCM beacon obscuring module3380, which may obfuscate any of the entities in the image data that have a DCM beacon and are not in the contact list. For example, in the example shown inFIG. 1, Beth Caesar's image is obscured, e.g., blurred, blacked out, covered with advertisements, or the like, because she has a DCM beacon associated with her image, and because she is not in the user's contact list. Jules Caesar, on the other hand, is not obscured because a known entity marker was attached to his image at module3370, because Jules Caesar is in the contact list of an associated device of the user. Auggie Caesar is not obscured regardless of contact list status, because there is no DCM beacon associated with Auggie Caesar.

Referring again toFIG. 1-Q, after the image is obscured, obscured image3390of wearable computer3300may release the image to the rest of the device for processing, or to another device, the Internet, or cloud storage, for further operations on the image data.

Referring now toFIG. 1-P, in an embodiment, a user2107may be associated with an active DCM beacon2610, which will be discussed in more detail herein. The word “Active” in this context merely means that the DCM beacon has some form of circuitry or emitter.

Referring now toFIG. 1-K, in an embodiment, the system may include an active DCM beacon6000, which may show an active DCM beacon, e.g., active DCM beacon2610, in more detail. In an embodiment, beacon6000may include DCM beacon broadcasting module6010. In an embodiment, DCM beacon broadcasting module6010may broadcast a privacy beacon associated with at least one user, e.g., user2107, from at or near the location of user2107. The beacon may be detected by an image capturing device when the user is captured in an image.

Referring again toFIG. 1-K, in an embodiment, the beacon6000may include an indication of DCM beacon detection module6020, which may detect, be informed of, or otherwise acquire an indication that the active DCM beacon has been captured by an image capturing device. In an embodiment, indication of DCM beacon detection module6020may include one or more of DCM beacon scanning module6022, which may scan nearby devices to see if they have detected the beacon, and DCM beacon communications handshake module6024, which may establish communication with one or more nearby devices to determine if they have captured the beacon.

Referring again toFIG. 1-K, in an embodiment, beacon6000may include term data broadcasting module6030, which may broadcast, or which may order to be broadcasted, term data, which may include the terms of service. In an embodiment, term data broadcasting module6030may include one or more of a substantive term data broadcasting module6032, which may broadcast the actual terms of service, and pointer to term data broadcasting module6034, which may broadcast a pointer to the terms of service data that a capturing device may use to retrieve the terms of service from a particular location.

Referring now toFIG. 1-C, in an embodiment, the system may include a DCM beacon test duplicating server4800. In an embodiment, the DCM beacon test duplicating server4800may take the image data, and perform the test for capturing the beacon again, as a redundancy, as a verification, or as a protection for wearable computer server4000. In an embodiment, DCM beacon test duplicating server4800may be a part of wearable computer server4000. In another embodiment, DCM beacon test duplicating server4800may be separate from wearable computer server4000, and may be controlled by a different entity, e.g., a watchdog entity, or an independent auditing agency.

Referring again toFIG. 1-C, in an embodiment, DCM beacon test duplicating server4800may include encrypted data reception for secondary DCM beacon detection module4810, which may acquire the encrypted image data containing the user, e.g., user2105, e.g., Jules Caesar, and the associated DCM beacon, e.g., DCM beacon2110.

Referring again toFIG. 1-C, in an embodiment, DCM beacon test duplicating server4800may include a device-specific key retrieving module4820, which may retrieve the device-specific key, e.g., from wearable computer device3100, or from wearable computer server4000. In an embodiment, DCM beacon test duplicating server4800may include image data decryption with device-specific key module4830, which may apply the device-specific key obtained by device-specific key retrieving module4820, and apply it to the encrypted image data, to generate decrypted image data.

Referring again toFIG. 1-C, in an embodiment, the unencrypted image data may be sent to DCM beacon detecting module4840of DCM beacon test duplicating server4800. If the raw image data was optical in its original form, then it may be reconverted to optical (e.g., light) data. In an embodiment, DCM beacon detecting module4840may perform a detection for the DCM beacon, as previously described. In an embodiment, DCM beacon detecting module4840may include one or more of an optics-based DCM beacon detecting module4842and a digital image processing-based DCM beacon detecting module4844.

Referring now toFIG. 1-D, after the test for detecting the DCM beacon2220(which may be the same as the DCM beacon2210, but is detected at a different place, so a different number has been assigned), DCM beacon detection at duplicating sever result obtaining module4850may obtain the result of the detection performed at DCM beacon test duplicating server4800. Similarly, DCM beacon detection at device result obtaining module4860may obtain the result from the DCM beacon detection performed at wearable computer device3100. The results from module4850and4860may be stored at DCM beacon test result storage and logging module4870of DCM beacon test duplicating server4800.

Referring again toFIG. 1-D, the test results from DCM beacon test duplicating server4800and from wearable computer3100may be stored at DCM beacon test result storage and logging module4870, and such results may be kept for a predetermined length of time. In an embodiment, the results may be transmitted to a requesting party using DCM beacon test result transmitting module4880.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring an image, said image including at least one representation of a feature of at least one entity, detecting a presence of a privacy beacon associated with the at least one entity from the acquired image, without performance of a further process on the acquired image, encrypting the image using a unique device code prior to performance of one or more image processes other than privacy beacon detection, said unique device code unique to an image capture device and not transmitted from the image capture device, and facilitating transmission of the encrypted image and privacy beacon data associated with the privacy beacon to a location configured to perform processing on one or more of the encrypted image and the privacy beacon data.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring a block of encrypted data corresponding to one or more images that have previously been encrypted through use of a unique device code associated with an image capture device configured to capture the one or more images, wherein at least one of the one or more images includes at least one representation of a feature of at least one entity, acquiring a privacy metadata, said privacy metadata corresponding to a detection of a privacy beacon in the one or more images captured by the image capture device, said privacy beacon associated with the at least one entity, and determining, at least partly based on the acquired privacy metadata, and partly based on a value calculation based on the representation of the feature of the at least one entity for which the privacy beacon is associated, whether to allow processing, which may include distribution, decryption, etc., of the encrypted data block.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring a block of encrypted data corresponding to one or more images that have previously been encrypted through use of a unique device code associated with an image capture device configured to capture the one or more images, wherein at least one of the one or more images includes at least one representation of a feature of at least one entity, acquiring a privacy metadata indicating detection of a privacy beacon in the one or more images captured by the image capture device, said privacy beacon associated with the at least one entity, retrieving term data from a remote location, said term data corresponding to a term of service associated with a potential release of the block of encrypted data corresponding to the one or more images that have previously been encrypted through use of the unique device code associated with the image capture device configured to capture the one or more images, calculating an expected valuation corresponding to potential revenue associated with the release of at least a portion of the block of encrypted data corresponding to the one or more images that have previously been encrypted through use of the unique device code associated with the image capture device configured to capture the one or more images, and determining whether to perform decryption of at least a portion of the block of encrypted data at least partially based on the calculation of the expected valuation corresponding to the potential revenue associated with the release of the at least the portion of the block of encrypted data, and at least partially based on the retrieved term data corresponding to the term of service.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring a block of encrypted data corresponding to one or more images that have previously been encrypted through use of a unique device code associated with an image capture device configured to capture the one or more images, wherein at least one of the one or more images includes at least one representation of a feature of at least one entity, acquiring a privacy metadata indicating a lack of detection of a privacy beacon in the one or more images captured by the image capture device, decrypting the block of encrypted data corresponding to the one or more images that have previously been encrypted through use of a unique device code associated with the image capture device, and encrypting the block of decrypted data through use of a unique entity code that is related to an entity associated with the image capture device configured to capture the one or more images. Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring a block of encrypted data from a remote location, said block of encrypted data corresponding to one or more images captured by an image capture device, said block of encrypted data previously encrypted through use of a unique entity code that is related to an entity associated with the image capture device, receiving an indication that the one or more images captured by the image capture device were approved for decryption through a verification related to privacy metadata associated with the one or more images, obtaining the unique entity code related to the entity associated with the image capture device, and releasing the one or more images through decryption of the block of encrypted data acquired from the remote location using the obtained unique entity code related to the entity associated with the image capture device.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring a block of encrypted data corresponding to one or more images that have previously been encrypted through use of a unique device code associated with an image capture device configured to capture the one or more images, wherein at least one of the one or more images includes at least one representation of a feature of at least one entity, retrieving term data from a remote location, said term data corresponding to a term of service associated with a potential release of the one or more images that have previously been encrypted through use of the unique device code associated with the image capture device configured to capture the one or more images, calculating whether an estimated advertising revenue from one or more advertisement images placed in the one or more images of the block of encrypted data will be greater than an estimated potential liability for distribution of the one or more images of the block of encrypted data, said estimated potential liability at least partly based on the retrieved term data, modifying the one or more images of the block of encrypted data by replacing one or more areas associated with one or more entities at least partially depicted in the one or more images with the one or more advertisement images, and calculating a modified estimated advertising revenue from the modified one or more images of the block of encrypted data.

Referring again to the system, in an embodiment, a computationally-implemented method may include monitoring a deployment of a privacy beacon associated with a user, said privacy beacon configured to alert a wearable computer of one or more terms of service associated with said user in response to recordation of image data that includes said privacy beacon by said wearable computer, and said privacy beacon configured to instruct said wearable computer to execute one or more processes to impede transmission of the one or more images that include the user associated with said privacy beacon, and storing a record of the deployment of the privacy beacon associated with the user, said record configured to be retrieved upon request to confirm whether the privacy beacon associated with the user was active at a particular time.

Referring again to the system, in an embodiment, a computationally-implemented method may include receiving data regarding one or more features of one or more entities that are designated for protection by one or more terms of service, associating the one or more terms of service with a privacy beacon configured to be captured in an image when the one or more features of the one or more entities are captured in the image, and providing the terms of service to one or more media service providers associated with a device that captured an image that includes the privacy beacon, in response to receipt of an indication that an image that includes the privacy beacon has been captured.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring one or more images that have previously been captured by an image capture device, wherein at least one of the one or more images includes at least one representation of a feature of one or more entities, identifying a first entity for which at least one representation of a first entity feature is present in the one or more images, and a second entity for which at least one representation of a second entity feature is present in the one or more images, obtaining data indicating that the first entity has a preexisting relationship with an entity associated with the image capture device, e.g., in a contact list, preventing an obfuscation of the representation of the first entity for which the preexisting relationship with the entity associated with the image capture device has been indicated, and obfuscating the representation of the second entity for which at least one representation of the second entity feature is present in the one or more images.

Referring again to the system, in an embodiment, a computationally-implemented method may include broadcasting a privacy beacon associated with at least one entity from a location of the at least one entity, said privacy beacon configured to be detected by an image capturing device upon capture of an image of the at least one entity, acquiring an indication that the privacy beacon associated with the at least one entity has been captured by the image capturing device, and broadcasting term data including one or more conditions and/or consequences of distribution of one or more images that depict at least a portion of the at least one entity.

Referring again to the system, in an embodiment, a computationally-implemented method may include acquiring a block of encrypted data corresponding to one or more images that have previously been encrypted through use of a unique device code associated with an image capture device configured to capture the one or more images, wherein at least one of the one or more images includes at least one representation of a feature of at least one entity, decrypting the block of encrypted data corresponding to the one or more images that have previously been encrypted through use of the unique device code associated with the image capture device configured to capture the one or more images, performing an operation to detect a presence of a privacy beacon associated with the at least one entity from the one or more images, wherein the privacy beacon previously had been detected by the image capture device, and storing outcome data corresponding an outcome of the operation to detect the presence of the privacy beacon associated with the at least one entity of the one or more images, wherein said outcome data includes an indication of whether a result of the performed operation to detect the presence of the privacy beacon associated with the at least one entity from the one or more images matches the previous detection of the privacy beacon by the image capture device.

Referring now toFIG. 2, e.g.,FIG. 2A,FIG. 2Aillustrates an example environment200in which the methods, systems, circuitry, articles of manufacture, and computer program products and architecture, in accordance with various embodiments, may be implemented by one or more computing devices220. As shown inFIG. 2A, one or more computing devices220may capture images. For example, computing device220may capture an image of an entity105associated with a privacy beacon, e.g., a DCM (“Don't Capture Me”) beacon110. In this and some other examples, the captured entity is named “Jules Caesar.” In an embodiment in which computing device220is a wearable computer, computing device220may be worn by computing device user115. In another embodiment, computing device user115is not present (e.g., computing device220is a security camera, or an automated teller machine with a camera).

Referring again toFIG. 2A, computing device220may capture the image data as image data22, which may be optical data, e.g., light data, digital data, e.g., a digital signal, or data in another form. In a process that will be discussed in more detail herein according to various embodiments, image data22may be encrypted using a device-specific code, shown here as encrypted image data24. Encrypted image data24may be transmitted to a server device230, which may be an example of wearable computer server3000shown inFIG. 1. In an embodiment, computing device220may generate beacon metadata150from the detected DCM beacon110. In an embodiment, beacon metadata150may be binary beacon metadata that indicates whether a beacon has been detected, e.g., yes or no. In an embodiment, beacon metadata150may include a data string that identifies the beacon, the entity, the type of beacon, data about the beacon, or a combination of the foregoing. In an embodiment, such a beacon metadata150may be used by server device230to obtain additional information about the entity, e.g., terms of service data, which will be described in more detail herein. In an embodiment, beacon metadata150may include terms of service data associated with the entity, e.g., Jules Caesar. The types of beacon metadata150are not limited to those listed in this paragraph, and the foregoing types of beacon metadata150will be described in more detail further herein with respect toFIGS. 4A-4E, and with respect to the specific examples listed herein.

Referring again toFIG. 2A, in an embodiment, server device230may include a decryption determination module232, which may determine whether to decrypt the device-based encrypted image24, in a process described in more detail in this application and the related applications. In an embodiment, decryption determination module232may include valuation assessment module236. Valuation assessment module236may make one or more calculations and/or estimations to determine one or more of an estimated value of the captured image, and an estimated liability that may be incurred for the distribution of the image.

In an embodiment, if the decryption determination module232determines to decrypt the image, then the image may be decrypted into decrypted image26. In an embodiment, decrypted image26may be transmitted to server device235for further operation. In an embodiment, server device235may be part of server device230. In another embodiment, server device235may be separate from server device230, or may be under the control of a related or separate entity. In an embodiment, server device235may apply a client-based encryption key to decrypted image26to generate client-based encrypted image28. Upon encryption, client-based encrypted image28may be transmitted to another location, server, or social networking site, by client-based encrypted image distribution module239. In an embodiment, client-based encrypted image28may be transmitted to computing device220by client-based encrypted image distribution module239.

In an embodiment, computing device220may receive the client-based encrypted image at client-based encrypted image receiving module221. Client-based encrypted image receiving module221may then facilitate decryption of the client-based encrypted image through use of the client-based encryption key, which may be stored on the device, inputted by the user, or retrieved from a remote database or server. Client-based encrypted image28thus may be decrypted into decrypted image26A.

Referring again toFIG. 2A, computing device220may include other operation modules, e.g., a decrypted image operation module249. Decrypted image operation module249may include one or more of a social network distributing module249A, image manipulation module249B, image copying module249C, and image mailing module249D. In an embodiment, the portions of the computing device220that deal with the device-based encrypted image24, e.g., the image capturing components and the image encryption components, may be separated, either physically or virtually, from components that operate on the decrypted image, e.g., the client-based encrypted image receiving module221and the decrypted image operation module229. In this way, the computing device220may be prevented from transmitting or operating on the unencrypted image as it is captured, or the encrypted image after it is encrypted by the device.

Referring again toFIG. 2A, in some embodiments, one or more of the encrypted image data and the DCM beacon metadata are transmitted over one or more communication network(s)240. In various embodiments, the communication network240may include one or more of a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a personal area network (PAN), a Worldwide Interoperability for Microwave Access (WiMAX), public switched telephone network (PTSN), a general packet radio service (GPRS) network, a cellular network, and so forth. The communication networks240may be wired, wireless, or a combination of wired and wireless networks. It is noted that “communication network” as it is used in this application refers to one or more communication networks, which may or may not interact with each other.

Computing device220may be any electronic device, portable or not, that may be operated by or associated with one or more users. Computing device220is shown as interacting with a user115. As set forth above, user115may be a person, or a group of people, or another entity that mimics the operations of a user. In an embodiment, user115may be a computer or a computer-controlled device. Computing device220may be, but is not limited to, a wearable computer. Computing device220may be any device that is equipped with an image capturing component, including, but not limited to, a cellular phone, a network phone, a smartphone, a tablet, a music player, a walkie-talkie, a radio, an augmented reality device (e.g., augmented reality glasses and/or headphones), wearable electronics, e.g., watches, belts, earphones, or “smart” clothing, earphones, headphones, audio/visual equipment, media player, television, projection screen, flat screen, monitor, clock, appliance (e.g., microwave, convection oven, stove, refrigerator, freezer), a navigation system (e.g., a Global Positioning System (“GPS”) system), a medical alert device, a remote control, a peripheral, an electronic safe, an electronic lock, an electronic security system, a video camera, a personal video recorder, a personal audio recorder, and the like.

Referring now toFIG. 2B,FIG. 2Bshows a detailed description of a computing device220operating in environment200, in an embodiment. It is noted that the components shown inFIG. 2Brepresent merely one embodiment of computing device220, and any or all components other than processor222may be omitted, substituted, or modified, in various embodiments.

Referring again toFIG. 2B, computing device220may include a device memory224. In an embodiment, device memory224may include memory, random access memory (“RAM”), read only memory (“ROM”), flash memory, hard drives, disk-based media, disc-based media, magnetic storage, optical storage, volatile memory, nonvolatile memory, and any combination thereof. In an embodiment, device memory224may be separated from the device, e.g., available on a different device on a network, or over the air. For example, in a networked system, there may be many computing devices220whose device memory224is located at a central server that may be a few feet away or located across an ocean. In an embodiment, computing device220may include a device memory224. In an embodiment, memory224may comprise of one or more of one or more mass storage devices, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), cache memory such as random access memory (RAM), flash memory, synchronous random access memory (SRAM), dynamic random access memory (DRAM), and/or other types of memory devices. In an embodiment, memory224may be located at a single network site. In an embodiment, memory224may be located at multiple network sites, including sites that are distant from each other.

Referring again toFIG. 2B, in an embodiment, computing device220may include a client-based decryption key obtaining module223configured to obtain the client-based decryption key. In an embodiment, client-based decryption key obtaining module223may obtain the client-based decryption key by one or more of retrieving the key from a local memory, retrieving the key from a remote memory, and receiving an input from an operator of the device, e.g., a person that knows an access code for getting the client-based decryption key.

Referring again toFIG. 2B, in an embodiment, computing device220may include a client-based encrypted image receiving module221that may receive the client-based encrypted image, e.g., from server device230or server device235.

Referring again toFIG. 2B,FIG. 2Bshows a more detailed description of computing device220. In an embodiment, computing device220may include a processor222. Processor222may include one or more microprocessors, Central Processing Units (“CPU”), a Graphics Processing Units (“GPU”), Physics Processing Units, Digital Signal Processors, Network Processors, Floating Point Processors, and the like. In an embodiment, processor222may be a server. In an embodiment, processor222may be a distributed-core processor. Although processor222is as a single processor that is part of a single computing device220, processor222may be multiple processors distributed over one or many computing devices220, which may or may not be configured to operate together. In an embodiment, computing device220may be a wearable computer.

Processor222is illustrated as being configured to execute computer readable instructions in order to execute one or more operations described above, and as illustrated inFIGS. 10,11A-11D,12A-12D,13A-13D, and14A-14B. In an embodiment, processor222is designed to be configured to operate as processing module250, which may include one or more of client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module252, approval data configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module254, data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring module256, and application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image facilitating module258.

FIGS. 3A-3Erefer to an “image capture device,” which is defined as any device that is equipped with the ability to capture images, and not necessarily a wearable computer or a device designed specifically to capture images.

Referring now toFIG. 3A,FIG. 3Ashows an exemplary embodiment of a computing device220as image capture device302. In an embodiment, image capture device302may include an image capture component, e.g., a lens306A. Image capture component306A may capture an image including the user105and the DCM beacon110, and capture that image as raw (optical or digital) data120. In an embodiment, image capture device302may include beacon detection module310A that is configured to detect DCM beacon110, either optically, digitally, or other, depending on the embodiment. After detection of the beacon, the image data may be sent to an image data encryption module320A to encrypt the image. In an embodiment, if the beacon is not detected, the image data120is released past barrier340A and the other image capture device modules350A may operate on the image data120. In an embodiment, the encrypted data, and data associated with the DCM beacon110(although not necessarily the beacon itself) may be transmitted to encrypted data and beacon transmitting module330A, which may transmit the encrypted data and beacon data to an external source, e.g., server3000as described inFIG. 1. It is noted that beacon detection module310A, image data encryption module320A, and encrypted data and beacon transmitting module330A may be separated from other image capture device modules350A by barrier340A.

In an embodiment, barrier340A may be a physical barrier, e.g., beacon detection module310A, lens306A, image data encryption module320A, and encrypted data and beacon transmitting module330A may be hard-wired to each other and electrically excluded from other image capture device modules350A. In another embodiment, barrier340A may be implemented as a programmed barrier, e.g., the image data120is not transmitted to modules other than beacon detection module310A, lens306A, image data encryption module320A, and encrypted data and beacon transmitting module330A. In another embodiment, barrier340A may be implemented as a data access barrier, e.g., the captured image data120may be protected, e.g., with an access or clearance level, so that only beacon detection310A, lens306A, image data encryption module320A, and encrypted data and beacon transmitting module330A may read or operate on the image data120. In another embodiment, barrier340A may not be a complete barrier, e.g., barrier340A may allow “read” access to the image data, but not “copy” or “write” access. In another embodiment, barrier340A may be a barrier to transmission, e.g., the image may be viewed locally at the device, but may be barred from being saved to a removable memory, or uploaded to a cloud storage or social networking site/social media site.

Referring now toFIG. 3B,FIG. 3Bshows an embodiment of a computing device220as image capture device304. In an embodiment, image capture device304may include an image capture component, e.g., a lens and sensor306B. Image capture component306B may capture an image including the user105and the DCM beacon110, and capture that image as raw (optical or digital) data120. In an embodiment, image capture device304may include image path splitting module305B that may receive the raw data120as a signal, e.g., optical or digital, and split the signal into two branches. As shown inFIG. 4, one branch, e.g., the north branch, sends the raw signal to image data encryption module320B, which may encrypt the image. In an embodiment, the other branch, e.g., the south branch, may send the signal to a beacon detection module310B, which may detect the DCM beacon110. In an embodiment, if the DCM beacon110is detected, then the unencrypted image data that arrived at beacon detection module310B is destroyed. In an embodiment, if the DCM beacon110is not detected, then the encrypted image data from image data encryption module320B is destroyed, and the unencrypted image data at beacon detection module310B is allowed to pass to other image capture device modules350B. In an embodiment, the beacon detection result and the encrypted image data are transmitted to the encrypted data and beacon transmitting module330B. In an embodiment, barrier340B may separate image path splitting module305B, beacon detection module310B, image data encryption module320B, and encrypted data and beacon transmitting module330B from other image capture device modules350B.

In an embodiment, barrier340B may be a physical barrier, e.g., beacon detection module310B, lens306B, image data encryption module320B, and encrypted data and beacon transmitting module330B may be hard-wired to each other and electrically excluded from other image capture device modules350B. In another embodiment, barrier340B may be implemented as a programmed barrier, e.g., the image data120is not transmitted to modules other than image path splitting module305B, beacon detection310B, lens306B, image data encryption module320B, and encrypted data and beacon transmitting module330B. In another embodiment, barrier340B may be implemented as a data access barrier, e.g., the captured image data may be protected, e.g., with an access or clearance level, so that only beacon detection module310B, lens306B, image data encryption module320B, and encrypted data and beacon transmitting module330B may read or operate on the image data120. In another embodiment, barrier340B may not be a complete barrier, e.g., barrier340B may allow “read” access to the image data, but not “copy” or “write” access. In another embodiment, barrier340B may be a barrier to transmission, e.g., the image may be viewed locally at the device, but may be barred from being saved to a removable memory, or uploaded to a cloud storage or social networking site/social media site.

Referring now toFIG. 3C,FIG. 3Cshows an embodiment of a computing device220implemented as image capture device306. In an embodiment, image capture device306may include an image capture component306C that captures optical data120A. In an embodiment, optical data120A may be sent to optical splitting module305C, which may split the optical signal, e.g., the light, into two paths. Referring toFIG. 3C, the “south” path may transmit the light to an optical filter312, which may filter the light for a specific characteristic, e.g., a wavelength or an object, according to known optical filtration techniques. In an embodiment, the filtered optical signal may then be transmitted to a filtered optical signal beacon detection module310C, which may detect the beacon110in the optical data120A.

Referring again toFIG. 3C, the “north” path from optical splitting module305C may transmit the optical image data to an optical-to-digital converter314, e.g., a CMOS or CCD sensor. In an embodiment, the digital signal then may be transmitted to image data encryption module320C, and the encrypted data transmitted to encrypted data and beacon transmitting module330C, along with the beacon detection result, for transmission to an external source, e.g., server3000as shown inFIG. 1. In an embodiment, barrier340C may prevent access to the unencrypted image data by other image capture device modules350C. In an embodiment, barrier340C may function similarly to barriers340A and340B, and the descriptions of those barriers and their possible implementations also may apply to barrier340C. In an embodiment, image data encryption module320C, encrypted data beacon and transmitting module330C, and optical-to-digital converter314may be controlled by beacon detection control module325, which may be part of the processor of image capture device306, or may be a separate processor. In an embodiment, beacon detection control module325may form part or all of processor222of computing device220ofFIG. 2B.

Referring now toFIG. 3D,FIG. 3Dshows an exemplary implementation of a computing device220implemented as image capture device308, according to an embodiment. Image capture device308may include an optical image collector306D that may capture an image including the user105and the DCM beacon110, and capture that image as optical data120A. Optical data120A may then be sent to optical splitting module305D, which may split the optical signal, e.g., the light, into two paths. Referring toFIG. 3D, the “south” path may transmit the light to an optical transformation module332, which may apply a transformation, e.g., a Fourier transformation, to the optical image data. The transformed optical data from module332, as well as a reference image from optical beacon reference signal providing module334may be transmitted to optical beacon detection module310D. Optical beacon detection module310D may optically detect the beacon using Fourier transformation and an optical correlator. The basic operation of performing optical image object detection is described in the publically-available (at the University of Michigan Online Library) paper “Report of Project MICHIGAN, SIGNAL DETECTION BY COMPLEX SPATIAL FILTERING,” by A. B. Vander Lugt, printed in July 1963 at the Radar Laboratory at the Institute of Science and Technology, the University of Michigan, which is hereby incorporated by reference in its entirety. Applicant's representative is including a copy of this paper with the filing of this application, for the convenience of the Examiner.

Referring again toFIG. 3D, the “north” path from optical splitting module305D may transmit the optical image data to an optical-to-digital converter324, e.g., a CMOS or CCD sensor. In an embodiment, the digital signal then may be transmitted to image data encryption module320D, and the encrypted data transmitted to encrypted data and beacon transmitting module330D, along with the beacon detection result, for transmission to an external source, e.g., server3000as shown inFIG. 1. In an embodiment, barrier340D may prevent access to the unencrypted image data by other image capture device modules350D. In an embodiment, barrier340D may function similarly to barriers340A and340B, and the descriptions of those barriers and their possible implementations also may apply to barrier340D. In an embodiment, image data encryption module320D, encrypted data and beacon transmitting module330D, and optical-to-digital converter324may be controlled by beacon detection control module335, which may be part of the processor of image capture device308, or may be a separate processor. In an embodiment, beacon detection control module335may form part or all of processor222of computing device220ofFIG. 2B.

Referring now toFIG. 3E,FIG. 3Eshows an exemplary embodiment of an implementation of computing device220as image capture device309. In an embodiment, image capture device309may include an optical image collector306E, e.g., a lens, which may collect the optical data120A. Optical data120A may be emitted to an optical beacon detection module310E, which may detect the DCM beacon110using one of the above-described optical detection methods. After detection of the beacon using optical techniques, the optical signal may be captured by an optical-to-digital conversion module344, and converted to digital image data, which is transferred to image data encryption module320E for encryption. In an embodiment, modules306E,310E,344, and320E, are hard-wired to each other, and separated from encrypted data and beacon transmitting module330E and other image capture device modules350E by barrier340E (which, in this embodiment, is shown for exemplary purposes only, because the physical construction of modules306E,310E,344, and320E removes the need for a barrier340E, whether implemented as hardware, programming, security, or access. In this embodiment, the image data is encrypted prior to interaction with the “main” portions of image capture device309, and after the beacon data has been optically detected.

FIGS. 4A-4Eshow one or more embodiments of a server device230, according to one or more embodiments. Unless otherwise stated or contradictory toFIGS. 4A-4E, the server devices430A,430B,430C,430D, and430E may include the elements of server device230, as previously described. Similarly, unless otherwise stated or contradictory toFIGS. 4A-4E, the computing devices420A,420B,420C,420D, and420E may include the elements of computing device230, as previously described.

Referring now toFIG. 4A,FIG. 4Ashows an exemplary implementation of server device230as server device430A operating in exemplary environment400A. In an embodiment, computing device420A further includes a location and time log and transmission module422A. In an embodiment, location and time log and transmission module422A may record a location, e.g., through global positioning sensors, triangulation using radio signals, or other methods, of the computing device420A, and a time that the image is captured, at the time the image is captured. This data of location and time of the image capture, e.g., location and time of detection data162, may be transmitted to server device430A, as shown inFIG. 4A.

Referring again toFIG. 4A, server device430A may include a beacon metadata acquisition module433. Beacon metadata acquisition module433may include location and time of beacon detection data acquisition module433A. Location and time of beacon detection data acquisition module433A may receive the location and time of detection data162. In an embodiment in which the beacon metadata150is binary beacon metadata150A, additional data regarding the image may be obtained. For example, server device430A may transmit the location and time of detection data162to a remote location, e.g., to beacon support server490. Beacon support server may include, for example, a geotagged and timestamped list of detected beacons436, which may track a location and time when a beacon is detected. Beacon support server490may be associated with DCM beacon110, and may be configured to log each time DCM beacon110is detected, e.g., in an embodiment in which DCM beacon110is an active beacon that can determine when it is detected. In an embodiment, beacon support server490may use the location and time of detection data162to determine which DCM beacon110is detected, and transmit the beacon identification information back to server device430A, e.g., to beacon identification data acquisition module433B. In an embodiment, this beacon identification information may be used by server device430A. In an embodiment, the beacon identification information may be used to identify the entity in the image, without decrypting the image, for example.

Referring now toFIG. 4B,FIG. 4Bshows an exemplary implementation of server device230as server device430B operating in exemplary environment400B. In an embodiment, the computing device420B may generate beacon metadata150, which may be binary beacon metadata150A, and transmit the binary beacon metadata150A to server device430B. In an embodiment, server device430B receives the binary beacon metadata150A, e.g., through use of beacon metadata acquisition module443, which may describe whether a beacon was detected in the encrypted image data block160, but which may, in an embodiment, not provide additional data regarding the beacon. In an embodiment, server device430B may include encrypted image analysis and data extraction module442, which may perform analysis on the encrypted image24, if possible. Such analysis may include, for example, that the encrypted image data block160may have metadata that is not encrypted or that may be read through the encryption. In an embodiment, for example, the image22may be encrypted in such a manner that certain characteristics of the encrypted image24may be obtained without decrypting the image. In an embodiment, server device430B may use encrypted image analysis and data extraction module442to determine more information about the image, e.g., which may be used to perform valuation of the image and/or to retrieve term data regarding one or more terms of service associated with the DCM beacon110and the entity Jules Caesar105.

Referring now toFIG. 4C,FIG. 4Cshows an exemplary implementation of server device230as server device430C operating in exemplary environment400C. In an embodiment, computing device420C may transmit the beacon metadata150, which may be binary beacon metadata150A, to server device430C. Beacon metadata150may be obtained by beacon metadata acquisition module456. In an embodiment, beacon metadata acquisition module456may relay data regarding the received metadata to a decision-making portion of server device430C, e.g., a central processor. In an embodiment, server device430C may determine that it wants more data regarding the image22, in order to retrieve term data, or perform a valuation of the image data. Accordingly, in an embodiment, server device430C may include encrypted image analysis and data extraction module436, which may operate similarly to encrypted image analysis and data extraction module442, and also, in an embodiment, encrypted image analysis and data extraction module436may transmit the encrypted image data block to a “sandbox,” e.g., image decryption sandbox492. Image decryption sandbox492may place the image in a virtual or physical “sandbox” where other processes may be unable to access the data. Image decryption sandbox492may be part of server device430C, or may be a separate entity. In an embodiment, image decryption sandbox492may decrypt the encrypted image. Encrypted image decryption and beacon identification module493may perform analysis on the decrypted image, including identifying the beacon, or identifying the entity, or a combination thereof. The identification data then may be given to beacon identification data reception module438. In an embodiment, the decrypted image data is then trapped in the sandbox and/or destroyed.

Referring now toFIG. 4D,FIG. 4Dshows an exemplary implementation of server device230as server device430D operating in exemplary environment400D. In an embodiment, computing device420D may transmit beacon metadata150, e.g., beacon identifier metadata150B, to server device430D. In an embodiment, beacon identifier metadata150B may identify the beacon, e.g., the DCM beacon110. The identification may be a unique identification, e.g. “this beacon is associated with user #13606116, Jules Caesar,” or, in an embodiment, the identification may be a class of beacon, e.g., “this is a beacon with a $100,000 dollar liquidated damages clause associated with using a likeness of the entity associated with the beacon,” or “this is a beacon of a television celebrity,” or “this is a beacon provided by Image Protect Corporation.”

Referring again toFIG. 4D, server device430D receives the beacon identifier metadata150B, e.g., through use of beacon metadata acquisition module447. In an embodiment, server device430D may transmit the identifier to an external location, e.g., a terms of service transmission server485. Terms of service transmission server485may store terms of service associated with various beacons in its terms of service repository489. In an embodiment, each unique beacon may be associated with its own unique terms of service. In another embodiment, there may be common terms of service for various users. In another embodiment, there may be common terms of service for various classes of users. In an embodiment, the terms of service may vary depending on how much the entity, e.g., Jules Caesar, is paying to use the beacon service.

In an embodiment, terms of service transmission server485may include beacon identifier lookup table487. Beacon identifier lookup table487may receive the beacon identifier metadata150B, and use the beacon identifier metadata150B to obtain the terms of service associated with that beacon, e.g., terms of service data151. In an embodiment, terms of service data151then may be transmitted to server device430D.

Referring now toFIG. 4E,FIG. 4Eshows an exemplary implementation of server device230as server device430E operating in exemplary environment400E. In an embodiment, computing device420E may detect the DCM beacon110, and may obtain the terms of service from the detected beacon (e.g., the terms of service may be read from the beacon, e.g., in compressed binary). In an embodiment, the computing device420E may use the detected beacon data to obtain the terms of service data from another location, e.g., a terms of service data server (not pictured).

Referring again toFIG. 4E, in an embodiment, computing device420E may transmit beacon metadata150, e.g., beacon identifier and terms of service metadata150C, to server device430E. Beacon metadata acquisition module444may receive the beacon identifier and terms of service metadata150C, and detect that the terms of service are present in the beacon metadata150. In an embodiment, beacon metadata terms of service reading module454may read the terms of service from the beacon metadata150.

The foregoing examples are merely provided as examples of how beacon data may operate, and how identifying data and/or term of service data may be obtained by the various server devices, and should not be interpreted as limiting the scope of the invention, which is defined solely by the claims. Any and all components ofFIGS. 4A-4Emay be combined with each other, modified, or eliminated.

FIGS. 5A-5Dshow one or more embodiments of a computing device230, among other components, operating in an environment500(e.g.,500A-500D), according to one or more embodiments. Unless otherwise stated or contradictory toFIGS. 5A-5D, the server devices530A,530B,530C, and530D may include the elements of server device230, as previously described. Similarly, unless otherwise stated or contradictory toFIGS. 5A-5D, the computing devices520A,520B,520C, and520D may include the elements of computing device220, as previously described.

Referring now toFIG. 5A,FIG. 5Ashows an exemplary implementation of server device230as server device530A operating in exemplary environment500A. In an embodiment, as shown inFIG. 5A, computing device520A may capture an image that includes an entity105that may be associated with a privacy beacon, e.g., DCM beacon110. In an embodiment, the captured image, e.g., image22, may be encrypted into encrypted image24using a device-based encryption key. In an embodiment, encrypted image24may be combined with beacon metadata, e.g., beacon metadata150, in an encrypted image data block160. In another embodiment, beacon metadata150may be separate from encrypted image data block160. In an embodiment, the encrypted image24may be transmitted to a server device530A by encrypted image data transmitting module180. In an embodiment, a decryption determination module532A may determine to decrypt the image, e.g., in a process described in one or more of this and/or previous applications incorporated by reference. In an embodiment, server device530A may include decryption module534A, which may apply a device-based decryption key to the encrypted image24to generate decrypted image data. In an embodiment, client-based encryption module536A may apply a client-based encryption key to the decrypted image data, to generate a client-based encrypted image. In an embodiment, the client-based encrypted image then may be transmitted back to the computing device520A, which may be a wearable computer, e.g., to client-based encrypted data receiving module190. In an embodiment, upon receipt of the client-based encrypted image the client-based encrypted image decryption module195may decrypt the client-based encrypted image.

In an embodiment, one or more of the originally-captured image22, the decrypted image data in the decryption module534A of server device530A, and the decrypted image data in the client-based encryption module536A may be identical. In another embodiment, the substantive portion of the data (e.g., the color data) may be identical, and other data, e.g., header data or compression data, may be different. In another embodiment, the decrypted image data in the decryption module534A of server device530A, and the decrypted image data in the client-based encryption module536A may be slightly different.

Referring now toFIG. 5B,FIG. 5Bshows an exemplary implementation of server device230as server device530B operating in exemplary environment500B. In an embodiment, as shown inFIG. 5B, computing device520B may capture an image that includes an entity105that may be associated with a privacy beacon, e.g., DCM beacon110. In an embodiment, the captured image, e.g., image22, may be encrypted into encrypted image24using a device-based encryption key. In an embodiment, encrypted image24may be combined with beacon metadata, e.g., beacon metadata150, in an encrypted image data block160. In another embodiment, beacon metadata150may be separate from encrypted image data block160. In an embodiment, the encrypted image24may be transmitted to a server device530B by encrypted image data transmitting module180. In an embodiment, a decryption determination module532B may determine to decrypt the image, e.g., in a process described in one or more of this and/or previous applications incorporated by reference. In an embodiment, server device530B may include decryption module534B, which may apply a device-based decryption key to the encrypted image24to generate decrypted image data. In an embodiment, client-based encryption module536B may apply a client-based encryption key to the decrypted image data, to generate a client-based encrypted image.

Referring again toFIG. 5B, in an embodiment, the client-based encrypted image then may be transmitted to a device that is not the computing device520B, e.g., rather to other client-associated computer device550. Other client-associated computer device550may include client-based encrypted data receiving module191and/or client-based encrypted image decryption module194which may decrypt the client-based encrypted image, similarly to modules190and195ofFIG. 5A, but not part of computing device520B. In an embodiment, computer device550may also be worn or carried by the client, e.g., a smartphone carried by the client that was wearing the wearable computer520B. In an embodiment, computer device550may be remote from the client, e.g., the client's home computer. In another embodiment, computer device550may be a shared server, e.g., where the client stores images on the cloud. In an embodiment similar to the one described above, the computing device520B may not possess the decrypted image at any point during the process.

Referring again toFIG. 5B, similarly toFIG. 5A, in an embodiment, one or more of the originally-captured image22, the decrypted image data in the decryption module534B of server device530B, and the decrypted image data in the client-based encryption module536B may be identical. In another embodiment, the substantive portion of the data (e.g., the color data) may be identical, and other data, e.g., header data or compression data, may be different. In another embodiment, the decrypted image data in the decryption module534B of server device530B, and the decrypted image data in the client-based encryption module536B may be slightly different.

Referring now toFIG. 5C,FIG. 5Cshows an exemplary implementation of server device230as server device530C operating in exemplary environment500C. In an embodiment, as shown inFIG. 5A, computing device520C may capture an image that includes an entity105that may be associated with a privacy beacon, e.g., DCM beacon110. In an embodiment, the captured image, e.g., image22, may be encrypted into encrypted image24using a device-based encryption key. In an embodiment, encrypted image24may be combined with beacon metadata, e.g., beacon metadata150, in an encrypted image data block160. In another embodiment, beacon metadata150may be separate from encrypted image data block160. In an embodiment, the encrypted image24may be transmitted to a server device530C by encrypted image data transmitting module180. In an embodiment, a decryption determination module532C may determine to decrypt the image, e.g., in a process described in one or more of this and/or previous applications incorporated by reference.

Referring again toFIG. 5C, in an embodiment, one or more of the decision to decrypt the encrypted image24, and the encrypted image24may be transmitted to a client-based encryption handling device560. In an embodiment, client-based encryption handling device560may include decryption module562, which may apply a device-based decryption key to the encrypted image24to generate decrypted image data. In an embodiment, client-based encryption module564may apply a client-based encryption key to the decrypted image data, to generate a client-based encrypted image. In an embodiment, the client-based encrypted image, then may be transmitted back to the computing device520A, which may be a wearable computer, e.g., to client-based encrypted data receiving module190. In an embodiment, upon receipt of the client-based encrypted image the client-based encrypted image decryption module195may decrypt the client-based encrypted image.

Referring again toFIG. 5C, similarly toFIG. 5A, in an embodiment, one or more of the originally-captured image22, the decrypted image data in the decryption module562of client-based encryption handling device560, and the decrypted image data in the client-based encryption module564may be identical. In another embodiment, the substantive portion of the data (e.g., the color data) may be identical, and other data, e.g., header data or compression data, may be different. In another embodiment, the decrypted image data in the decryption module562of client-based encryption handling device560, and the decrypted image data in the client-based encryption module564may be slightly different.

Referring now toFIG. 5D,FIG. 5Dshows an exemplary implementation of server device230as server device530D operating in exemplary environment500D. In an embodiment, as shown inFIG. 5D, computing device520D may capture an image that includes an entity105that may be associated with a privacy beacon, e.g., DCM beacon110. In an embodiment, the captured image, e.g., image22, may be encrypted into encrypted image24using a device-based encryption key. In an embodiment, encrypted image24may be combined with beacon metadata, e.g., beacon metadata150, in an encrypted image data block160. In another embodiment, beacon metadata150may be separate from encrypted image data block160. In an embodiment, the encrypted image24may be transmitted to a server device530D by encrypted image data transmitting module180. In an embodiment, a decryption determination module532D may determine to decrypt the image, e.g., in a process described in one or more of this and/or previous applications incorporated by reference. In an embodiment, server device530D may include decryption module534D, which may apply a device-based decryption key to the encrypted image24to generate decrypted image data. In an embodiment, client-based encryption module536D may apply a client-based encryption key to the decrypted image data, to generate a client-based encrypted image.

Referring again toFIG. 5D, in an embodiment, the client-based encrypted image then may be transmitted to a device that is not the computing device520D, e.g., rather to a social networking server570or file repository570. In an embodiment, social networking server570may include client-based encrypted data receiving module192, similarly to client-based encrypted data receiving module190ofFIG. 5A. In an embodiment, social networking server570may include the client-based encrypted image decryption module197, which may be similar to the client-based encrypted image decryption module195ofFIG. 5A, and which may decrypt the client-based encrypted image. In an embodiment, social networking server may automatically decrypt the image, and/or take one or more actions, e.g., posting the image to a user's account, e.g., their “wall” on Facebook, or a similar structure. In another embodiment, the social networking server570may wait to decrypt the image, and/or to take one or more actions with the image, until the client that captured the image logs into the social networking service associated with the social networking server.

Referring again toFIG. 5D, similarly toFIG. 5A, in an embodiment, one or more of the originally-captured image22, the decrypted image data in the decryption module534D of server device530D, and the decrypted image data in the client-based encryption module536D may be identical. In another embodiment, the substantive portion of the data (e.g., the color data) may be identical, and other data, e.g., header data or compression data, may be different. In another embodiment, the decrypted image data in the decryption module534D of server device530D, and the decrypted image data in the client-based encryption module536D may be slightly different.

Referring now toFIG. 6,FIG. 6illustrates an exemplary implementation of the client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module252. As illustrated inFIG. 6, the client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module may include one or more sub-logic modules in various alternative implementations and embodiments. For example, as shown inFIG. 6, e.g.,FIG. 6A, in an embodiment, module252may include one or more of client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location configured to approve the client-based encrypted image for decryption module602, client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code as a seed value for generation of an encryption key and an asymmetric decryption key receiving module606, client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code as a nonsecret parameter of a key derivation function receiving module608, and client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code as a public key for an asymmetric cryptographic function receiving module610. In an embodiment, module602may include client-based encrypted image that is a captured image that includes a pixel-based representation of a person captured by a wearable computer image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location configured to approve the client-based encrypted image for decryption module604.

Referring again toFIG. 6, e.g.,FIG. 6B, in an embodiment, module252may include client-based encrypted image that is a captured image that depicts at least one feature of an entity captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module612. In an embodiment, module612may include one or more of client-based encrypted image that is a captured image that is a two-dimensional array of color values that correspond to a graphical representation of the at least one feature of an entity captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module614, client-based encrypted image that is a captured image that depicts at least one body part of a person captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module616, and client-based encrypted image that is a captured image that depicts at least one feature of an entity associated with a privacy beacon that has been captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module618. In an embodiment, module618may include client-based encrypted image that is a captured image that depicts at least one feature of an entity associated with a privacy beacon that has been captured by an image capture device that detected the privacy beacon and that has been previously encrypted through use of a particular client code receiving module620. In an embodiment, module620may include client-based encrypted image that is a captured image that depicts at least one feature of an entity associated with a privacy beacon that has been captured by an image capture device that optically detected the privacy beacon and that has been previously encrypted through use of a particular client code receiving module622.

Referring again toFIG. 6, e.g.,FIG. 6C, in an embodiment, module252may include client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location module624and client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code retrieving from a device memory module630. In an embodiment, module624may include client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location that approved the captured image for decryption module626. In an embodiment, module626may include client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a server that is operated by a developer of an image capturing application configured to be executed on one or more image capture devices and the server approved the captured image for decryption module628. In an embodiment, module630may include one or more of client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code retrieving from a device memory of the image capture device module632and client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code retrieving from a limited-access device memory module634.

Referring again toFIG. 6, e.g.,FIG. 6D, in an embodiment, module252may include client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code and that also has been previously encrypted through use of a particular device code receiving module636, client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular device, decrypted, and again encrypted through use of a particular client code receiving module638, client-based encrypted image that is a captured image captured by a wearable image capture device and that has been previously encrypted through use of a particular client code receiving module640, and client-based encrypted image that is a captured image captured by a stationary image capture device and that has been previously encrypted through use of a particular client code receiving module644. In an embodiment, module640may include client-based encrypted image that is a captured image captured by a covertly placed wearable image capture device and that has been previously encrypted through use of a particular client code receiving module642.

Referring now toFIG. 7,FIG. 7illustrates an exemplary implementation of approval data configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module254. As illustrated inFIG. 7, the approval data configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module254may include one or more sub-logic modules in various alternative implementations and embodiments. For example, as shown inFIG. 7, e.g.,FIG. 7A, in an embodiment, module254may include one or more of approval data configured to indicate a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module702and approval data configured to signify a decryption approval for the client-based encrypted image that is decrypted through application of a client-based decryption key obtaining module706. In an embodiment, module702may include binary approval data configured to indicate a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module704.

Referring again toFIG. 7, e.g.,FIG. 7B, in an embodiment, module254may include approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata and that is facilitated by a client-based decryption key obtaining module708. In an embodiment, module708may include one or more of approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata related to a privacy beacon obtaining module710and approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata related to a privacy beacon associated with an entity depicted in the captured image obtaining module716. In an embodiment, module710may include one or more of obtaining approval data that indicates that the client-based encrypted image was approved for decryption at least partly based on the privacy metadata that indicates that the captured image does not contain the privacy beacon associated with the entity represented in the captured image712and obtaining approval data that indicates that the client-based encrypted image was approved for decryption at least partly based on the privacy metadata that indicates the privacy beacon associated with the entity represented in the captured image was not detected714. In an embodiment, module716may include approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata that indicates detection of a privacy beacon associated with an entity depicted in the captured image obtaining module718. In an embodiment, module718may include approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a binary privacy metadata that indicates detection a privacy beacon associated with an entity depicted in the captured image obtaining module720.

Referring again toFIG. 7, e.g.,FIG. 7C, in an embodiment, module254may include one or more of approval data that is at least partly based on term data related to an entity depicted in the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module722and approval data that is at least partly based on term data retrieved through use of privacy metadata related to a privacy beacon linked to an entity depicted in the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module728. In an embodiment, module722may include approval data that is at least partly based on term data that includes one or more terms of service that govern use of the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module724. In an embodiment, module724may include approval data that is at least partly based on term data that includes one or more terms of service that specify liquidated damages for a public dissemination of the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module726.

Referring again toFIG. 7, e.g.,FIG. 7D, in an embodiment, module254may include approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a valuation of the captured image and that is facilitated by a client-based decryption key obtaining module730. In an embodiment, module730may include approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a valuation comparison of a potential revenue from distribution of the captured image and a potential damages incurred from the distribution of the captured image and that is facilitated by a client-based decryption key obtaining module732. In an embodiment, module732may include approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a valuation comparison of a potential revenue from distribution of the captured image and a potential damages determined by term data that includes one or more terms of service that govern distribution of the captured image and that is facilitated by a client-based decryption key obtaining module734.

Referring now toFIG. 8,FIG. 8illustrates an exemplary implementation of data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring module256. As illustrated inFIG. 8, the data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring module256may include one or more sub-logic modules in various alternative implementations and embodiments. For example, as shown inFIG. 8, e.g.,FIG. 8A, in an embodiment, module256may include one or more of data that includes the client-based decryption key that is generated through use of the particular client code that is related to a client that is associated with the image capture device as a seed value acquiring module802, data that includes the client-based decryption key that is generated through use of the particular client code that is related to a client that is associated with the image capture device as a parameter in a key generation function acquiring module804, data that includes the client-based decryption key that is a private key of an asymmetric key pair in which the particular client code is at least a portion of the public key acquiring module806, and data that includes the client-based decryption key that is generated through application of a transformation algorithm to the particular client code that is related to a client that is associated with the image capture device acquiring module808.

Referring again toFIG. 8, e.g.,FIG. 8B, in an embodiment, module256may include one or more of inputted particular client code receiving module810, generation of the client-based encrypted key from the inputted particular client code facilitating module812, data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring from a device that has authorization to distribute the client-based decryption key module816, and data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring from a memory of a particular device to which the client is logged into module820. In an embodiment, module810may include inputted particular client code receiving from the client module814. In an embodiment, module816may include data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring from a device that is configured to allow a login by the client module818.

Referring again toFIG. 8, e.g.,FIG. 8C, in an embodiment, module256may include data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device retrieving in response to a detection of input of the particular client code module822, data that includes the client-based decryption key that is at least partly based on the particular client code that is assigned to the client that is associated with the image capture device acquiring module826, and data that includes the client-based decryption key that is at least partly based on the particular client code that is generated through client input to the image capture device acquiring module830. In an embodiment, module822may include data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device retrieving in response to a detection of input of the particular client code as a login to a device module824. In an embodiment, module826may include data that includes the client-based decryption key that is at least partly based on the particular client code that is assigned to the client by the image capture device acquiring module828.

Referring again toFIG. 8, e.g.,FIG. 8D, in an embodiment, module256may include one or more of data that includes the client-based decryption key that is at least partly based on the particular client code that is a login code that is distributed to the client to facilitate access to an application configured to be loaded into a memory of the image capture device acquiring module832, data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client for which the image capture device is configured to store associated client data acquiring module834, data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that operated the image capture device acquiring module836, and data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device configured to be worn by the client acquiring module838.

Referring now toFIG. 9,FIG. 9illustrates an exemplary implementation of application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image facilitating module258. As illustrated inFIG. 9, the application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image facilitating module258may include one or more sub-logic modules in various alternative implementations and embodiments. For example, as shown inFIG. 9, e.g.,FIG. 9A, in an embodiment, module258may include one or more of application of the client-based decryption key that is at least partly based on the particular client code that is related to the image capture device that is a wearable computing device to the client-based encrypted image facilitating module902and application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image to remove encryption facilitating module904.

Referring again toFIG. 9, e.g.,FIG. 9B, in an embodiment, module258may include one or more of application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image to generate a decrypted image executing module906and decrypted image storing in a memory of a device module908. In an embodiment, module908may include one or more of decrypted image storing in a memory that is configured to be accessible to one or more image distribution applications module910and decrypted image storing in a memory of a device other than the image capture device module914. In an embodiment, module910may include decrypted image storing in a memory that is configured to be accessible to one or more social network site upload applications module912. In an embodiment, module914may include decrypted image storing in a memory of a home computer device linked to the client module916.

Referring now toFIG. 10,FIG. 10shows operation1000, e.g., an example operation of server device230operating in an environment200. In an embodiment, operation1000may include operation1002depicting acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device. For example,FIG. 2, e.g.,FIG. 2B, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module252acquiring (e.g., obtaining, receiving, calculating, selecting from a list or other data structure, receiving, retrieving, or receiving information regarding, performing calculations to find out, retrieving data that indicates, receiving notification, receiving information that leads to an inference, whether by human or automated process, or being party to any action or transaction that results in informing, inferring, or deducting, including but not limited to circumstances without absolute certainty, including more-likely-than-not and/or other thresholds) a client-based (e.g., the encryption is associated with the client (e.g., a user of the device), that is, the encryption is performed by the client, or uses an encryption key associated with the client, inputted by the client, or uses an encryption key that was derived from a client attribute, including but not limited to a client code, a client name, a client email address, a client identifier, e.g., a client social security number or drivers' license number) encrypted (e.g., one or more operations have been performed with the intention of preventing, delaying, or hindering unauthorized access) image (e.g., a description of a graphic picture that is a visual representation of something, regardless of whether that something is coherent, nonsensical, abstract, or otherwise) that is a captured (e.g., at least a portion of the image was collected from reflected light that was gathered by a lens and/or other components) image (e.g., a description of a graphic picture that is a visual representation of something, regardless of whether that something is coherent, nonsensical, abstract, or otherwise) that has been previously (e.g., prior to the “acquiring” step described here) encrypted (e.g., one or more operations have been performed with the intention of preventing, delaying, or hindering unauthorized access) through use of a particular client code (e.g., any set of data that is associated with the client or created by the client), wherein said captured (e.g., at least a portion of the image was collected from reflected light that was gathered by a lens and/or other components) image (e.g., a description of a graphic picture that is a visual representation of something, regardless of whether that something is coherent, nonsensical, abstract, or otherwise) was captured by an image capture device (e.g., a device that has the hardware and/or software to facilitate the gathering of one or more images).

Referring again toFIG. 10, operation1000may include operation1004depicting obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key. For example,FIG. 2, e.g.,FIG. 2B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module254obtaining (e.g., acquiring, receiving, calculating, selecting from a list or other data structure, receiving, retrieving, or receiving information regarding, performing calculations to find out, retrieving data that indicates, receiving notification, receiving information that leads to an inference, whether by human or automated process, or being party to any action or transaction that results in informing, inferring, or deducting, including but not limited to circumstances without absolute certainty, including more-likely-than-not and/or other thresholds) an indication (e.g., a data, signal, message, flag, binary encoding, state change, environment change, quantum state change) that the client-based (e.g., the encryption is associated with the client (e.g., a user of the device), that is, the encryption is performed by the client, or uses an encryption key associated with the client, inputted by the client, or uses an encryption key that was derived from a client attribute, including but not limited to a client code, a client name, a client email address, a client identifier, e.g., a client social security number or drivers' license number) encrypted (e.g., one or more operations have been performed with the intention of preventing, delaying, or hindering unauthorized access) image (e.g., a description of a graphic picture that is a visual representation of something, regardless of whether that something is coherent, nonsensical, abstract, or otherwise) was approved (e.g., cleared, granted, authorized, selected, allowed, or otherwise permission has been given or is implied or always present) for decryption (e.g., removal of the encryption, reversal of the encryption, or general modification into an intelligible form) through use of a client-based decryption key (e.g., a key that is related to the client, e.g., whose creation and/or application was related to data associated with the client, approved by the client, overseen by the client, in response to a client input or action, etc.).

Referring again toFIG. 13, operation1000may include operation1006depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device. For example,FIG. 2, e.g.,FIG. 2B, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring module256procuring (e.g., obtaining or acquiring through an action, including retrieving from memory or receiving from a remote source) the client-based decryption key (e.g., a key that is related to the client, e.g., whose creation and/or application was related to data associated with the client, approved by the client, overseen by the client, in response to a client input or action, etc., including a situation where the key is generated from a code or other set of data that is associated with the client) that is at least partly based on the particular client code (e.g., any set of data that is associated with the client or created by the client), wherein the particular client code (e.g., any set of data that is associated with the client or created by the client) that is related to (e.g., there is some relationship, regardless of how tenuous, including being assigned to, or including information about) a client (e.g., a user) that is associated with (e.g., has a relationship with, e.g., has previously used, purchased, logged into, viewed, received data from, etc.) the image capture device (e.g., a device that has the hardware and/or software to facilitate the gathering of one or more images).

Referring again toFIG. 10, operation1000may include operation1008depicting decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device. For example,FIG. 2, e.g.,FIG. 2B, shows application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image facilitating module258decrypting (e.g., removing the encryption from, reversing the encryption, or generally modifying into an intelligible form) the client-based (e.g., the encryption is associated with the client (e.g., a user of the device), that is, the encryption is performed by the client, or uses an encryption key associated with the client, inputted by the client, or uses an encryption key that was derived from a client attribute, including but not limited to a client code, a client name, a client email address, a client identifier, e.g., a client social security number or drivers' license number) encrypted (e.g., one or more operations have been performed with the intention of preventing, delaying, or hindering unauthorized access) image (e.g., a description of a graphic picture that is a visual representation of something, regardless of whether that something is coherent, nonsensical, abstract, or otherwise) through use of (e.g., was facilitated, at least in part, in the derivation of or carrying out of) the client-based decryption key (e.g., a key that is related to the client, e.g., whose creation and/or application was related to data associated with the client, approved by the client, overseen by the client, in response to a client input or action, etc., including a situation where the key is generated from a code or other set of data that is associated with the client) that is at least partly based on the particular client code (e.g., any set of data that is associated with the client or created by the client) that is related to (e.g., there is some relationship, regardless of how tenuous, including being assigned to, or including information about) the client (e.g., a user) associated with (e.g., has a relationship with, e.g., has previously used, purchased, logged into, viewed, received data from, etc.) the image capture device (e.g., a device that has the hardware and/or software to facilitate the gathering of one or more images).

An example terms of service is listed below with the numbered paragraphs 1-5. Many other variations of terms of service are known and used in click-through agreements that are common at the time of filing, and the herein example is intended to be exemplary only and not limiting in any way.

1. By capturing an image of any part of the user Jules Caesar (hereinafter “Image”), or providing any automation, design, resource, assistance, or other facilitation in the capturing of the Image, you agree that you have captured these Terms of Service and that you acknowledge and agree to them. If you cannot agree to these Terms of Service, you should immediately delete the captured Image. Failure to do so will constitute acceptance of these Terms of Service.

2. The User Jules Caesar owns all of the rights associated with the Image and any representation of any part of Jules Caesar thereof;

3. By capturing the Image, you agree to provide the User Jules Caesar just compensation for any commercialization of the User's personality rights that may be captured in the Image.

4. By capturing the Image, you agree to take all reasonable actions to track the Image and to provide an accounting of all commercialization attempts related to the Image, whether successful or not.

5. By capturing the Image, you accept a Liquidated Damages agreement in which unauthorized use of the Image will result in mandatory damages of at least, but not limited to, $1,000,000.

A privacy beacon may include, but is not limited to, one or more of a marker that reflects light in a visible spectrum, a marker that reflects light in a nonvisible spectrum, a marker that emits light in a visible spectrum, a marker that emits light in a nonvisible spectrum, a marker that emits a radio wave, a marker that, when a particular type of electromagnetic wave hits it, emits a particular electromagnetic wave, an RFID tag, a marker that uses near-field communication, a marker that is in the form of a bar code, a marker that is in the form of a bar code and painted on a user's head and that reflects light in a nonvisible spectrum, a marker that uses high frequency low penetration radio waves (e.g., 60 GHz radio waves), a marker that emits a particular thermal signature, a marker that is worn underneath clothing and is detectable by an x-ray-type detector, a marker that creates a magnetic field, a marker that emits a sonic wave, a marker that emits a sonic wave at a frequency that cannot be heard by humans, a marker that is tattooed to a person's bicep and is detectable through clothing, a marker that is a part of a user's cellular telephone device, a marker that is broadcast by a part of a user's cellular telephone device, a marker that is broadcast by a keychain carried by a person, a marker mounted on a drone that maintains a particular proximity to the person, a marker mounted in eyeglasses, a marker mounted in a hat. a marker mounted in an article of clothing, the shape of the person's face is registered as the beacon, a feature of a person registered as the beacon, a marker displayed on a screen, a marker in the form of an LED, a marker embedded on a page, or a book, a string of text or data that serves as a marker, a marker embedded or embossed onto a device, and the like.

FIGS. 11A-11Ddepict various implementations of operation1002, depicting acquiring a client-based encrypted image that is a captured image that has previously been encrypted through use of a particular client code, wherein said captured image was captured by an image capture device according to embodiments. Referring now toFIG. 11A, operation1002may include operation1102depicting acquiring the client-based encrypted image from a remote location configured to approve the client-based encrypted image for decryption, wherein said client-based encrypted image is the captured image that includes a representation of a feature of an entity and that was captured by a wearable computer, and wherein said client-based encrypted image was previously encrypted through use of an encryption key that was generated at least partly based on a particular client code. For example,FIG. 6, e.g.,FIG. 6Ashows client-based encrypted image that is a captured image and that has been previously encrypted through use of a particular client code receiving from a remote location configured to approve the client-based encrypted image for decryption module602acquiring the client-based encrypted image (e.g., a picture of three people in a fishing boat) from a remote location (e.g., a server owned by a component manufacturer of the wearable computer, e.g., the Google Glass) configured to approve the client-based encrypted image (e.g., the picture of three people in the fishing boat) for decryption, wherein said client-based encrypted image (e.g., the picture of three people in the fishing boat) is the captured image (e.g., the picture of three people in the fishing boat) that includes a representation of a feature of an entity (e.g., a face of one of the people in the fishing boat for which a privacy beacon was detected) and that was captured by a wearable computer (e.g., a Google Glass device), and wherein said client-based encrypted image (e.g., the picture of three people in the fishing boat) was previously encrypted through use of an encryption key that was generated at least partly based on a particular client code.

Referring again toFIG. 11A, operation1102may include operation1104depicting acquiring the client-based encrypted image from a remote location configured to approve the client-based encrypted image for decryption, wherein said client-based encrypted image is the captured image that includes a pixel-based representation of a face of a person and that was captured by a wearable computer, and wherein said client-based encrypted image was previously encrypted through use of an encryption key that was generated at least partly based on a particular client code. For example,FIG. 6, e.g.,FIG. 6A, shows client-based encrypted image that is a captured image that includes a pixel-based representation of a person captured by a wearable computer image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location configured to approve the client-based encrypted image for decryption module604acquiring the client-based encrypted image (e.g., a picture of a family having Sunday brunch at Golden Corral restaurant) from a remote location (e.g., a server controlled by a service that the device or the device user subscribes to that manages images) configured to approve the client-based encrypted image (e.g., the picture of a family having Sunday brunch at Golden Corral restaurant) for decryption, wherein said client-based encrypted image (e.g., the picture of a family having Sunday brunch at Golden Corral restaurant) is the captured image (e.g., the picture of a family having Sunday brunch at Golden Corral restaurant) that includes a pixel-based representation of a face of a person (e.g., the father of the family) and that was captured by a wearable computer (e.g., an EyeTap device), and wherein said client-based encrypted image (e.g., the picture of a family having Sunday brunch at Golden Corral restaurant) was previously encrypted through use of an encryption key that was generated at least partly based on a particular client code (e.g., the client login to the service that approved the image for decryption).

Referring again toFIG. 11A, operation1002may include operation1106depicting acquiring the client-based encrypted image that is the captured image that was captured by the image capture device that has been previously encrypted through use of the particular client code as a seed value to generate an asymmetric pair of encryption keys that are configured to be used to encrypt and decrypt the image. For example,FIG. 6, e.g.,FIG. 6A, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code as a seed value for generation of an encryption key and an asymmetric decryption key receiving module606acquiring the client-based encrypted image (e.g., an image of a person taking pictures of a landmark) that is the captured image (e.g., the image of a person taking pictures of a landmark) that was captured by the image capture device (e.g., a wearable computer, e.g., a hypothetical Microsoft “KinectVision”) that has been previously encrypted through use of the particular client code (e.g., a user login to a Microsoft-branded service that is available on the “KinectVision”) as a seed value to generate an asymmetric pair of encryption keys that are configured to be used to encrypt and decrypt the image (e.g., the image of a person taking pictures of a landmark).

Referring again toFIG. 11A, operation1002may include operation1108depicting acquiring the client-based encrypted image that is the captured image that was captured by the image capture device and that has been previously encrypted through use of the particular client code as a non-secret parameter in a key derivation function. For example,FIG. 6, e.g.,FIG. 6A, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code as a non-secret parameter of a key derivation function receiving module608acquiring the client-based encrypted image (e.g., an image of four friends in front of a Las Vegas casino) that is the captured image (e.g., the image of four friends in front of a Las Vegas casino) that was captured by the image capture device (e.g., a wearable computer, e.g., a hypothetical Samsung “Spectacles”) and that has previously been encrypted through use of the particular client code (e.g., a login name and password to the hypothetical Samsung “Spectacles”) as a non-secret parameter in a key derivation function.

Referring again toFIG. 11A, operation1002may include operation1110depicting acquiring the client-based encrypted image that is the captured image that was captured by the image capture device and that has been previously encrypted through use of the particular client code as a public key for an asymmetric cryptographic function. For example,FIG. 6, e.g.,FIG. 6B, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code as a public key for an asymmetric cryptographic function receiving module610acquiring the client-based encrypted image (e.g., a surreptitious image of two people at an amusement park) that is the captured image (e.g., the surreptitious image of the two people at the amusement park) that was captured by the image capture device (e.g., an Oculon Optoelectronics device) and that has been previously encrypted through use of the particular client code (e.g., a code stored in the image capture device once the user has logged in at least once to the device) as a public key for an asymmetric cryptographic function.

Referring now toFIG. 11B, operation1002may include operation1112depicting acquiring the client-based encrypted image that is the captured image that includes a representation of a feature of an entity and that has been previously encrypted through use of a particular client code, wherein said captured image was captured by the image capture device. For example,FIG. 6, e.g.,FIG. 6B, shows client-based encrypted image that is a captured image that depicts at least one feature of an entity captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module612acquiring the client-based encrypted image (e.g., an image of two people at a Matt & Kim concert) that is the captured image (e.g., the image of the two people at the concert) that includes a representation (e.g., pixel data) of a feature (e.g., a face) of an entity (e.g., a person) and that has been previously encrypted through use of a particular client code (e.g., the image capture device has a bank of codes, and each time someone operates the image capture device, the image capture device assigns a code to that person), wherein said captured image (e.g., the image of two people at a Matt & Kim concert) was captured by the image capture device (e.g., a hypothetical wearable computer, e.g., an Apple “iGlasses”).

Referring again toFIG. 11B, operation1112may include operation1114depicting acquiring the client-based encrypted image that is the captured image that includes a two-dimensional array of color values that represent a feature of an entity and that has been previously encrypted through use of a particular client code, wherein said captured image was captured by the image capture device. For example,FIG. 6, e.g.,FIG. 6B, shows client-based encrypted image that is a captured image that is a two-dimensional array of color values that correspond to a graphical representation of the at least one feature of an entity captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module614acquiring the client-based encrypted image (e.g., an image of three friends meeting at a bar for drinks, taken covertly by a person at a different table) that is the captured image (e.g., the image of three friends meeting at a bar for drinks, taken covertly by a person at a different table) that includes a two-dimensional array of color values that represent a feature (e.g., a full-body) of an entity (e.g., one of the three friends at the bar) and that has been previously encrypted through use of a particular client code (e.g., when a user uses an image capture device, a remote server transmits a code to the image capture device that is assigned to the user), wherein said captured image (e.g., the image of three friends meeting at a bar for drinks, taken covertly by a person at a different table) was captured by the image capture device (e.g., a wearable computer, e.g., an EyeTap device).

Referring again toFIG. 11B, operation1112may include operation1116depicting acquiring the client-based encrypted image that is the captured image that includes a representation of a body part of a person and that has been previously encrypted through use of a particular client code, wherein said captured image was captured by the image capture device. For example,FIG. 6, e.g.,FIG. 6B, shows client-based encrypted image that is a captured image that depicts at least one body part of a person captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module616acquiring the client-based encrypted image (e.g., an image of two people on a date at a beachside bar) that is the captured image (e.g., the image of two people on a date at a beachside bar) that includes a representation of a body part (e.g., a rear end) of a person (e.g., a celebrity) and that has been previously encrypted through use of a particular client code (e.g., a piece of data pulled from a client's profile when she registers the device), wherein said captured image (e.g., the image of two people on a date at a beachside bar) was captured by the image capture device (e.g., a hypothetical wearable computer, e.g., a Microsoft “KinectVision”).

Referring again toFIG. 11B, operation1112may include operation1118depicting acquiring the client-based encrypted image that is the captured image that includes the representation of the feature of the entity that is associated with a privacy beacon and that has been previously encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6B, shows client-based encrypted image that is a captured image that depicts at least one feature of an entity associated with a privacy beacon that has been captured by an image capture device and that has been previously encrypted through use of a particular client code receiving module618acquiring the client-based encrypted image (e.g., an image of a person sitting by themselves at a bus stop) that is the captured image (e.g., an image of a person sitting by themselves at a bus stop) that includes the representation (e.g., RGB color spectrum data) of the feature (e.g., a face) of the entity (e.g., the person at the bus stop) that is associated with a privacy beacon (e.g., a marker that reflects light in a visible spectrum) and that has been previously encrypted through use of the particular client code (e.g., the full name of the person operating the image capture device, as inputted by the person into the image capture device).

Referring again toFIG. 11B, operation1118may include operation1120depicting acquiring the client-based encrypted image that is the captured image that includes the representation of the feature of the entity that is associated with the privacy beacon that was detected in the image and that has been previously encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6B, shows client-based encrypted image that is a captured image that depicts at least one feature of an entity associated with a privacy beacon that has been captured by an image capture device that detected the privacy beacon and that has been previously encrypted through use of a particular client code receiving module620acquiring the client-based encrypted image (e.g., an image of three college kids out playing in the snow) that is the captured image (e.g., the image of three college kids out playing in the snow) that includes the representation (e.g., pixel data) of the feature (e.g., a full body) of the entity (e.g., one of the persons playing in the snow) that is associated with the privacy beacon (e.g., a marker that emits light in a visible spectrum) that was detected in the image (e.g., the image of three college kids out playing in the snow) and that has been previously encrypted through use of the particular client code (e.g., a 32-digit number assigned to the person using the image capture device to capture the image).

Referring again toFIG. 11B, operation1120may include operation1122depicting acquiring the client-based encrypted image that is the captured image that includes the representation of the feature of the entity that is associated with the privacy beacon that was optically detected in the image by the image capture device and that has previously been encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6B, shows device-based encrypted image that is an image that has previously been encrypted through use of a particular device code assigned to an image capture device configured to capture the image, wherein the image includes a representation of a feature of an entity acquiring from a server that determined that the device-based encrypted image has been cleared for decryption module622acquiring the client-based encrypted image (e.g., an image of a pickup basketball game) that is the captured image (e.g., the image of the pickup basketball game) that includes the representation of the feature (e.g., bare legs and arms) of the entity (e.g., one of the basketball players) that is associated with the privacy beacon (e.g., a marker that is tattooed to a person's bicep and is detectable through clothing) that was optically detected (e.g., detected at least partly through use of one or more optical components) in the image (e.g., the image of the pickup basketball game) by the image capture device (e.g., a wearable computer, e.g., Google Glass) and that has been previously encrypted through use of the particular client code (e.g., a Google “identity” that is required for the user to operate the Google Glass image capture device).

Referring now toFIG. 11C, operation1002may include operation1124depicting acquiring the client-based encrypted image from a remote location, wherein said client-based encrypted image is the captured image captured by the image capture device that has previously been encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6C, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location module624acquiring the client-based encrypted image (e.g., a photo of two people in a cigar shop) from a remote location (e.g., from a server that stores images that were captured by an image capture device), wherein said client-based encrypted image (e.g., the photo of two people in the cigar shop) is the captured image (e.g., the photo of two people in the cigar shop) captured by the image capture device (e.g., a wearable computer, e.g., a LifeLog device) that has previously been encrypted through use of the particular client code (e.g., a code that is assigned to the user by the image capture device when the user uses the image capture device, without informing the user of the code).

Referring again toFIG. 11C, operation1124may include operation1126depicting acquiring the client-based encrypted image from a remote location that approved the client-based encrypted image for decryption, wherein said client-based encrypted image is the captured image captured by the image capture device that has previously been encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6C, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a remote location that approved the captured image for decryption module626acquiring the client-based encrypted image (e.g., an image of two people drinking coffee at a Starbucks) from a remote location (e.g., a server to which the image was transmitted after capture and immediate encryption) that approved the client-based encrypted image (e.g., the image of two people drinking coffee at the Starbucks) for decryption, wherein said client-based encrypted image (e.g., the image of two people drinking coffee at the Starbucks) is the captured image (e.g., the image of two people drinking coffee at the Starbucks) captured by the image capture device (e.g., a wearable computer, e.g., a hypothetical Apple wearable computer, e.g., “iGlasses”) that has previously been encrypted through use of the particular client code (e.g., a 128-bit string that was generated at least partly using the Apple-branded identifier that the client uses to log in to various Apple products, including the hypothetical Apple-branded wearable computer).

Referring again toFIG. 11C, operation1126may include operation1128depicting acquiring the client-based encrypted image from the remote location that approved the client-based encrypted image for decryption and that is a server that is operated by a developer of an image capturing application configured to be executed on one or more image capture devices, wherein said client-based encrypted image is the captured image captured by the image capture device that has previously been encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6C, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code receiving from a server that is operated by a developer of an image capturing application configured to be executed on one or more image capture devices and the server approved the captured image for decryption module628acquiring the client-based encrypted image (e.g., an image of three friends with sideline passes for a professional football game) from the remote location that approved the client-based encrypted image (e.g., image of three friends with sideline passes for a professional football game) for decryption that is a server that is operated by a developer (e.g., Google, in this example, but could be a third party developer as well) of an image capturing application (e.g., a baseline camera application that is included in the device at manufacture to allow out-of-the-box operation of the image capture device) configured to be executed on one or more image capture devices (e.g., wearable computers, e.g., Google Glass, and it may be a generic application that is usable with other device that use Google's branded operating system, e.g., “Android”), wherein said client-based encrypted image (e.g., the image of three friends with sideline passes for a professional football game) is the captured image (e.g., the image of three friends with sideline passes for a professional football game) captured by the image capture device (e.g., a wearable computer, e.g., a Google Glass device) that has previously been encrypted through use of the particular client code (e.g., a unique block of data associated with the client that uses the wearable computer).

Referring again toFIG. 11C, operation1002may include operation1130depicting acquiring the client-based encrypted image from a device memory, wherein said client-based encrypted image is the captured image captured by the image capture device that has been previously encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6C, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code retrieving from a device memory module630acquiring the client-based encrypted image (e.g., an image of two people sitting at a bar) from a device memory (e.g., a memory of a device that received the encrypted image and is now storing it, which may be the device that captured the image, an associated device, or, in some embodiments, an unrelated device), wherein said client-based encrypted image (e.g., the image of two people sitting at a bar) is the captured image (e.g., the image of two people sitting at a bar) captured by the image capture device (e.g., a wearable computer, e.g., a DigiLens DL 40) that has been previously encrypted through use of the particular client code (e.g., a unique block of data associated with the client that uses the wearable computer that is assigned at the time that the image capture device is acquired by the client from a seller).

Referring again toFIG. 11C, operation1130may include operation1132depicting acquiring the client-based encrypted image from a memory of the image capture device that captured the image, wherein said client-based encrypted image is the captured image captured by the image capture device that has been previously encrypted through use of the particular client code. For example,FIG. 6, e.g.,FIG. 6C, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code retrieving from a device memory of the image capture device module632acquiring the client-based encrypted image (e.g., an image of three people on a smoke break outside an office building) from a memory of the image capture device (e.g., a wearable computer, e.g., a hypothetical Samsung “Spectacles”) that captured the image (e.g., the image of three people on a smoke break outside an office building), wherein said client based encrypted image (e.g., the image of three people on a smoke break outside an office building) is the captured image captured by the image capture device (e.g., the image was originally captured by the Samsung-branded hypothetical wearable computer, encrypted using a device-based code, transmitted to a remote server, approved for decryption, decrypted, re-encrypted using a client-based encryption code, and transmitted back to the same Samsung-branded hypothetical wearable computer) that has been previously encrypted through use of (e.g., the encryption key is at least partially derived from, e.g., as a seed value or algorithm parameter) the particular client code (e.g., a code associated with a user of the image capture device).

Referring again toFIG. 11C, operation1130may include operation1134depicting acquiring the client-based encrypted image from a limited-access memory of the image capture device that captured the image, wherein said client-based encrypted image is the captured image captured by the image capture device that has been previously encrypted through use of the particular client code, wherein said captured image was captured by the image capture device. For example,FIG. 6, e.g.,FIG. 6C, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code retrieving from a limited-access device memory module634acquiring the client-based encrypted image (e.g., an image of a person doing work on their laptop at an airport concourse) from a limited-access memory (e.g., a memory that is accessible only to a particular set of applications) of the image capture device (e.g., a wearable computer, e.g., a Nokia SMARTglasses device) that captured the image (e.g., the image of a person doing work on their laptop at an airport concourse), wherein said client-based encrypted image is the captured image captured by the image capture device (e.g., the image was originally captured by the previously-mentioned Nokia-branded wearable computer, encrypted using a device-based code, transmitted to a remote location, approved for decryption, decrypted, re-encrypted using a client-based encryption code, and transmitted back to the same Nokia-branded wearable computer) that has been previously encrypted through use of the particular client code (e.g., an encryption key that is derived at the device from a login used by the user of the image capture device), wherein said captured image (e.g., image of a person doing work on their laptop at an airport concourse) was captured by the image capture device).

Referring now toFIG. 11D, operation1002may include operation1136depicting acquiring the client-based encrypted image that is the captured image that has been previously encrypted through use of the particular client code, and that was previously encrypted at the image capture device using a particular device code, wherein said captured image was captured by the image capture device. For example,FIG. 6, e.g.,FIG. 6D, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular client code and that also has been previously encrypted through use of a particular device code receiving module636acquiring the client-based encrypted image (e.g., an image of a person sitting at their cubicle at work, taken surreptitiously by a co-worker) that is the captured image that has been previously encrypted through use of the particular client code (e.g., an encryption key that is derived at the device from a sampling of the last forty inputs into the image capture device), wherein said captured image (e.g., the image of a person sitting at their cubicle at work, taken surreptitiously by a co-worker) was captured by the image capture device (e.g., a wearable computer, e.g., an Oculon Optoelectronics device).

Referring again toFIG. 11D, operation1002may include operation1138depicting acquiring the client-based encrypted image that is the captured image that was encrypted at the image capture device through use of a particular device code, decrypted, and then previously encrypted again through use of the particular client code, wherein said captured image was captured by the image capture device. For example,FIG. 6, e.g.,FIG. 6D, shows client-based encrypted image that is a captured image captured by an image capture device and that has been previously encrypted through use of a particular device, decrypted, and again encrypted through use of a particular client code receiving module638acquiring the client-based encrypted image (e.g., a picture of a man at a urinal at a public bathroom that is taken clandestinely by a wearable computer) that is the captured image (e.g., the picture of a man at a urinal at a public bathroom that is taken clandestinely by a wearable computer) that was encrypted at the image capture device (e.g., a hypothetical wearable computer, e.g., a Microsoft “KinectVision”) through use of (e.g., an encryption key or algorithm was at least partially derived from) a particular device code (e.g., a code related to the device, e.g., a MAC address, or a sampling of the data stored at a particular memory address of the device), decrypted, and then previously encrypted again through use of the particular client code (e.g., a code associated with the user of the image capture device), wherein said captured image (e.g., the picture of a man at a urinal at a public bathroom that is taken clandestinely by a wearable computer) was captured by the image capture device (e.g., the hypothetical wearable computer, e.g., a Microsoft “KinectVision”).

Referring again toFIG. 11D, operation1002may include operation1140depicting acquiring the client-based encrypted image that is a captured image that has been previously encrypted through use of the particular client code, wherein said captured image was captured by a wearable computer device. For example,FIG. 6, e.g.,FIG. 6D, shows client-based encrypted image that is a captured image captured by a wearable image capture device and that has been previously encrypted through use of a particular client code receiving module640acquiring the client-based encrypted image (e.g., an image of a man playing with his dog at a dog park) that is a captured image (e.g., the image of a man playing with his dog at a dog park) that has been previously encrypted through use of the particular client code (e.g., a code associated with the user of the device), wherein said captured image (e.g., the image of a man playing with his dog at a dog park) was captured by a wearable computer device.

Referring again toFIG. 11D, operation1140may include operation1142depicting acquiring the client-based encrypted image that is a captured image that has been previously encrypted through use of the particular client code, wherein said captured image was captured by a covertly-operated wearable computer device. For example,FIG. 6, e.g.,FIG. 6D, shows client-based encrypted image that is a captured image captured by a covertly placed wearable image capture device and that has been previously encrypted through use of a particular client code receiving module642acquiring the client-based encrypted image (e.g., an image of three work associates eating lunch at a restaurant) that is a captured image (e.g., the image of three work associates eating lunch at a restaurant) that has been previously encrypted through use of the particular client code (e.g., a code associated with the user and selected by the user through prompting from the image capture device), wherein said captured image (e.g., image of three work associates eating lunch at a restaurant) was captured by a wearable computer device (e.g., a DigiLens DL40).

Referring again toFIG. 11D, operation1002may include operation1144depicting acquiring the client-based encrypted image that is a captured image that has been previously encrypted through use of the particular client code, wherein said captured image was captured by a stationary camera device. For example,FIG. 6, e.g.,FIG. 6D, shows client-based encrypted image that is a captured image captured by a stationary image capture device and that has been previously encrypted through use of a particular client code receiving module644acquiring the client-based encrypted image (e.g., an image of a person speaking on their cellular phone taken outside of a restaurant) that is a captured image that has been previously encrypted through use of the particular client code (e.g., here the particular client code is associated with an owner entity of the ATM, e.g., a bank), wherein said captured image was captured by a stationary camera device (e.g., a camera mounted on an automated teller machine (“ATM”) device).

FIGS. 12A-12Ddepict various implementations of operation1004, depicting obtaining an indication that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of a client-based decryption key, according to embodiments. Referring now toFIG. 12A, operation1004may include operation1202depicting obtaining data that indicates that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of the client-based decryption key. For example,FIG. 7, e.g.,FIG. 7A, shows approval data configured to indicate a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module702obtaining data that indicates that the client-based encrypted image (e.g., an image of a person praying inside a church) was approved for decryption through use of a client-based decryption key (e.g., a private key of an asymmetric pair).

Referring again toFIG. 12A, operation1202may include operation1204depicting obtaining binary data that indicates that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of the client-based decryption key. For example,FIG. 7, e.g.,FIG. 7A, shows binary approval data configured to indicate a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module704obtaining binary data (e.g., “yes or no” data) that indicates that the client-based encrypted image (e.g., an image of a politician at a fundraiser for a particular cause) was approved for decryption through use of the client-based decryption key (e.g., as part of a Digital Signature Standard (DSS) encryption).

Referring again toFIG. 12A, operation1004may include operation1206depicting obtaining a signal that indicates that the client-based encrypted image was approved for decryption, said decryption configured to be carried out through use of the client-based decryption key. For example,FIG. 7, e.g.,FIG. 7A, shows approval data configured to signify a decryption approval for the client-based encrypted image that is decrypted through application of a client-based decryption key obtaining module706obtaining a signal that indicates that the client-based encrypted image (e.g., an image of two people walking in the snow) was approved for decryption through use of the client-based decryption key (e.g., a decryption key from a Pretty Good Protection (PGP) scheme).

Referring now toFIG. 12B, operation1004may include operation1208depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on a privacy metadata associated with the captured image. For example,FIG. 7, e.g.,FIG. 7B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata and that is facilitated by a client-based decryption key obtaining module708obtaining approval data that indicates that the client-based encrypted image (e.g., an image of a child with a famous baseball player) was approved for decryption, said approval data at least partly based on a privacy metadata (e.g., data that includes a terms of service governing use of the image that contains a particular entity) associated with the captured image (e.g., the privacy metadata is based on a privacy beacon associated with the famous baseball player in the image).

Referring again toFIG. 12B, operation1208may include operation1210depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on a privacy metadata that regards a privacy beacon associated with an entity represented in the captured image. For example,FIG. 7, e.g.,FIG. 7B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata related to a privacy beacon obtaining module710obtaining approval data that indicates that the client-based encrypted image (e.g., an image of two people having dinner at a fancy restaurant) was approved for decryption, said approval data at least partly based on a privacy metadata (e.g., a metadata that indicates a terms of service that govern the image that was retrieved using an identification code of the privacy beacon) that regards a privacy beacon (e.g., a marker that reflects light in a nonvisible spectrum) associated with an entity (e.g., the privacy beacon is under the agency of the entity, e.g., one of the people in the picture) represented in the captured image (e.g., the image of two people having dinner at the fancy restaurant).

Referring again toFIG. 12B, operation1210may include operation1212depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on the privacy metadata that indicates that the captured image does not contain the privacy beacon associated with the entity represented in the captured image. For example,FIG. 7, e.g.,FIG. 7B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata that indicates an absence of the privacy beacon obtaining module712obtaining approval data that indicates that the client-based encrypted image (e.g., an image of a politician talking to a prominent donor that was recorded by a waiter wearing a wearable computer) was approved for decryption, said approval data at least partly based on the privacy metadata that indicates that the captured image (e.g., the image of a politician talking to a prominent donor that was recorded by a waiter wearing a wearable computer) does not contain the privacy beacon associated with the entity (e.g., the politician) represented in the captured image (e.g., the image of a politician talking to a prominent donor that was recorded by a waiter wearing a wearable computer).

Referring again toFIG. 12B, operation1210may include operation1214depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on the privacy metadata that indicates that the privacy beacon was not detected when the captured image was captured by the image capture device. For example,FIG. 7, e.g.,FIG. 7B, shows obtaining approval data that indicates that the client-based encrypted image was approved for decryption at least partly based on the privacy metadata that indicates the privacy beacon associated with the entity represented in the captured image was not detected714obtaining approval data that indicates that the client-based encrypted image (e.g., an image of two men sitting on a park bench) was approved for decryption (e.g., a decryption algorithm for use with the blowfish block cipher), said approval data at least partly based on the privacy metadata that indicates that the privacy beacon was not detected when the captured image (e.g., the image of two men sitting on a park bench) was captured by the image capture device (e.g., a wearable computer).

Referring again toFIG. 12B, operation1208may include operation1216depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on the privacy metadata that regards the privacy beacon associated with an entity represented in the captured image. For example,FIG. 7, e.g.,FIG. 7B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata related to a privacy beacon associated with an entity depicted in the captured image obtaining module716obtaining approval data that indicates that the client-based encrypted image (e.g., an image of three friends sitting courtside at a professional basketball game) was approved for decryption, said approval data at least partly based on the privacy metadata (e.g., data that includes an address for viewing a terms of service that govern use of the entity, which address was derived from data gathered from the privacy beacon) that regards the privacy beacon (e.g., a marker that is in the form of a bar code and painted on a user's head and that reflects light in a nonvisible spectrum) associated with an entity (e.g., one of the friends) represented in the captured image (e.g., the image of three friends sitting courtside at a professional basketball game).

Referring again toFIG. 12B, operation1216may include operation1218depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on the privacy metadata that indicates detection of the privacy beacon associated with the entity represented in the captured image. For example,FIG. 7, e.g.,FIG. 7B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a privacy metadata that indicates detection a privacy beacon associated with an entity depicted in the captured image obtaining module718obtaining approval data that indicates that the client-based encrypted image (e.g., an image of a man leaving a bar with a very drunk woman, surreptitiously taken by another patron) was approved for decryption, said approval data at least partly based on the privacy metadata (e.g., that indicates that a privacy beacon was detected and that a terms of service governing release of the image can be retrieved from a database using a particular key code) that indicates detection of the privacy beacon (e.g., a marker that emits light in a nonvisible spectrum) associated with the entity (e.g., the man leaving the bar) represented in the captured image (e.g., image of a man leaving a bar with a very drunk woman, taken by another patron).

Referring again toFIG. 12B, operation1218may include operation1220depicting obtaining approval data that indicates that the client-based encrypted image was approved for decryption, said approval data at least partly based on binary privacy metadata that indicates detection of the privacy beacon associated with the entity represented in the captured image. For example,FIG. 7, e.g.,FIG. 7B, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a binary privacy metadata that indicates detection a privacy beacon associated with an entity depicted in the captured image obtaining module720obtaining approval data that indicates that the client-based encrypted image (e.g., an image of two people sitting in a Ferrari at a car dealership) was approved for decryption, said approval data at least partly based on binary privacy metadata that indicates detection of the privacy beacon (e.g., a marker that uses high frequency low penetration radio waves (e.g., 60 GHz radio waves) associated with the entity (e.g., one of the persons in the Ferrari) represented in the captured image (e.g., the image of two people sitting in a Ferrari at a car dealership).

Referring now toFIG. 12C, operation1004may include operation1222depicting obtaining the indication that the client-based encrypted image was approved for decryption through use of the client based decryption key, wherein said indication is at least partly based on term data related to the captured image that contains a representation of an entity. For example,FIG. 7, e.g.,FIG. 7Cshows approval data that is at least partly based on term data related to an entity depicted in the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module708obtaining the indication that the client-based encrypted image (e.g., an image of a woman sunbathing topless at a private pool) was approved for decryption (e.g., a decryption key associated with the Diffie-Hellman encryption scheme) through use of the client-based decryption key, wherein said indication is at least partly based on term data (e.g., data that specifies one or more conditions and/or requirements and/or penalties) for release of the image) related to the captured image that contains a representation of an entity (e.g., a representation of the woman's breasts in the picture).

Referring again toFIG. 12C, operation1222may include operation1224depicting obtaining the indication that the client-based encrypted image was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on term data that includes one or more terms of service that specify one or more conditions for the use of the captured image that contains the representation of the entity. For example,FIG. 7, e.g.,FIG. 7C, shows approval data that is at least partly based on term data that includes one or more terms of service govern use of the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module724obtaining the indication that the client-based encrypted image (e.g., an image of three friends at a baseball game) was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on term data that includes one or more terms of service that specify one or more conditions (e.g., “pay me $1,000 to use this product”) for the use of the captured image that contains the representation of the entity (e.g., one of the three friends at the baseball game).

Referring again toFIG. 12C, operation1224may include operation1226depicting obtaining the indication that the client-based encrypted image was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on term data that includes one or more terms of service that specify an amount of damages for the distribution of the captured image that contains the representation of the entity. For example,FIG. 7, e.g.,FIG. 7C, shows approval data that is at least partly based on term data that includes one or more terms of service that specify liquidated damages for a public dissemination of the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module726obtaining the indication that the client-based encrypted image (e.g., an image of a group of people at a bowling alley) was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on term data that includes one or more terms of service that specify an amount of damages for the distribution of the captured image that contains the representation of the entity (e.g., one of the persons bowling at the bowling alley).

Referring again toFIG. 12C, operation1004may include operation1228depicting receiving the indication that the client-based encrypted image was approved for decryption through use of the client-based decryption key, wherein the indication is at least partly based on term data retrieved through use of privacy metadata related to a privacy beacon associated with an entity that is represented in the captured image. For example,FIG. 7, e.g.,FIG. 7C, shows approval data that is at least partly based on term data retrieved through use of privacy metadata related to a privacy beacon linked to an entity depicted in the captured image and that is configured to signify a decryption approval for the client-based encrypted image that is facilitated by a client-based decryption key obtaining module728receiving the indication that the client-based encrypted image (e.g., an image of two people having coffee in the morning at a diner) was approved for decryption through use of the client-based decryption key, wherein the indication is at least partly based on term data retrieved through use of privacy metadata (e.g., the term data was retrieved from a database using the privacy metadata as a key value) related to a privacy beacon (e.g., marker that uses near-field communication) associated with an entity (e.g., one of the people having coffee in the diner) that is represented in the captured image (e.g., the image of two people having coffee in the morning at the diner).

Referring now toFIG. 12D, operation1004may include operation1230depicting receiving the indication that the client-based encrypted image was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on a valuation of the captured image. For example,FIG. 7, e.g.,FIG. 7D, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a valuation of the captured image and that is facilitated by a client-based decryption key obtaining module730receiving the indication that the client-based encrypted image (e.g., an image of two people volunteering at a food bank) was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on a valuation of the captured image (e.g., if the valuation is large enough, the approval for decryption is given).

Referring again toFIG. 12D, operation1230may include operation1232depicting receiving the indication that the client-based encrypted image was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on a valuation comparison of a potential revenue from distribution of the captured image and a potential damages incurred from the distribution of the captured image. For example,FIG. 7, e.g.,FIG. 7D, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a valuation comparison of a potential revenue from distribution of the captured image and a potential damages incurred from the distribution of the captured image and that is facilitated by a client-based decryption key obtaining module732receiving the indication that the client-based encrypted image (e.g., an image of a man working on a laptop at a local coffee shop) was approved for decryption through use of the client-based decryption key (e.g., a key that is part of the International Data Encryption Algorithm (IDEA)), wherein said indication is at least partly based on a valuation comparison of a potential revenue from distribution (e.g., sale, or value of posting the image on a website with advertisements/subscription fees, e.g., if the person is famous or if the data is important, e.g., if the person was a known CEO of a large company) of the captured image (e.g., the image of a man working on a laptop at a local coffee shop) and a potential damages incurred (e.g., from legal liability, whether direct or indirect, e.g., protection from legal recovery) from the distribution of the captured image (e.g., the image of a man working on a laptop at a local coffee shop).

Referring again toFIG. 12D, operation1232may include operation1234depicting receiving the indication that the client-based encrypted image was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on the valuation comparison of the potential revenue from distribution of the captured image and a potential damages that is based on term data that includes one or more terms of service that govern distribution of the captured image. For example,FIG. 7, e.g.,FIG. 7D, shows approval data configured to signify a decryption approval for the client-based encrypted image that is at least partly based on a valuation comparison of a potential revenue from distribution of the captured image and a potential damages determined by term data that includes one or more terms of service that govern distribution of the captured image and that is facilitated by a client-based decryption key obtaining module734receiving the indication that the client-based encrypted image (e.g., an image of a man having lunch with a woman at a secluded restaurant) was approved for decryption through use of the client-based decryption key, wherein said indication is at least partly based on the valuation comparison of the potential revenue (e.g., from sale to a gossip website) from distribution of the captured image (e.g., an image of a man having lunch with a woman at a secluded restaurant) and a potential damages that is based on term data that includes one or more terms of service (e.g., a liquidated damages clause) that govern distribution of the captured image (e.g., an image of a man having lunch with a woman at a secluded restaurant).

FIGS. 13A-13Cdepict various implementations of operation1006, depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to a client that is associated with the image capture device, according to embodiments. Referring now toFIG. 13A, operation1006may include operation1302depicting procuring the client-based decryption key that is a decryption key of a client-based encryption key that was generated through use of the particular client code as a seed value, wherein the particular client code is related to the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8A, shows data that includes the client-based decryption key that is generated through use of the particular client code that is related to a client that is associated with the image capture device as a seed value acquiring module802procuring the client-based decryption key that is a decryption key of a client-based encryption key that was generated through use of the particular client code (e.g., a code associated with the user of the image capture device, e.g., a login to one or more services running on the image capture device) as a seed value, wherein the particular client code is related to the client (e.g., the user of) that is associated with the image capture device (e.g., a wearable computer, e.g., a Google Glass device).

Referring again toFIG. 13A, operation1006may include operation1304depicting procuring the client-based decryption key that was generated through use of the particular client code as input to a key generation algorithm, wherein the particular client code is related to the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8A, shows data that includes the client-based decryption key that is generated through use of the particular client code that is related to a client that is associated with the image capture device as a parameter in a key generation function acquiring module804procuring the client-based decryption key that was generated through use of the particular client code as input to a key generation algorithm (e.g., a Boneh-Franklin Identity-Based Encryption, e.g., described in IEEE 1363.3), wherein the particular client code is related to the client that is associated with the image capture device (e.g., a hypothetical wearable computer, e.g., a Microsoft KinectVision).

Referring again toFIG. 13A, operation1006may include operation1306depicting procuring the client-based decryption key that is a private key of an asymmetric key pair that includes a public key that is the particular client code, wherein the particular client code is related to the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8A, shows data that includes the client-based decryption key that is a private key of an asymmetric key pair in which the particular client code is at least a portion of the public key acquiring module806procuring the client-based decryption key that is a private key of an asymmetric key pair that includes a public key that is the particular client code (e.g., a 64-bit data string that was used from randomly selecting characters of the user's login name), wherein the particular client code is related to the client that is associated with the image capture device (e.g., a wearable computer, e.g., an EyeTap device).

Referring again toFIG. 13A, operation1006may include operation1308depicting generating the client-based decryption key through application of a transformation algorithm to the particular client code, wherein the particular client code is related to the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8A, shows data that includes the client-based decryption key that is generated through application of a transformation algorithm to the particular client code that is related to a client that is associated with the image capture device acquiring module808generating the client-based decryption key through application of a transformation algorithm to the particular client code (e.g., a 256-digit code), wherein the particular client code is related to the client that is associated with the image capture device (e.g., a wearable computer, e.g., a hypothetical Samsung “Spectacles”).

Referring now toFIG. 13B, operation1006may include operation1310depicting receiving an input of the particular client code. For example,FIG. 8, e.g.,FIG. 8A, shows inputted particular client code receiving module810receiving an input of the particular client code (e.g., it could be a login username, a password, a random input from a user into other applications, or a prompted input from a user).

Referring again toFIG. 13B, operation1006may include operation1312depicting obtaining the client-based decryption key from the inputted particular client code. For example,FIG. 8, e.g.,FIG. 8B, shows generation of the client-based encrypted key from the inputted particular client code facilitating module812obtaining (e.g., generating, using an algorithm, or retrieving, using the input as a lookup) the client-based decryption key from the inputted particular client code (e.g., could be a login username, a password, a random input from a user into other applications, or a prompted input from a user).

Referring again toFIG. 13B, operation1310may include operation1314depicting receiving the input of the particular client code from the client. For example,FIG. 8, e.g.,FIG. 8B, shows inputted particular client code receiving from the client module814receiving the input of the particular client code (e.g., a 64-character password) from the client (e.g., the user of an image capture device, e.g., a wearable computer).

Referring again toFIG. 13B, operation1006may include operation1316depicting retrieving the client-based decryption key that is at least partly based on the particular client code from a device that is authorized to have possession of the client-based decryption key. For example,FIG. 8, e.g.,FIG. 8B, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring from a device that has authorization to distribute the client-based decryption key module816retrieving the client-based decryption key that is at least partly based on the particular client code (e.g., a combination of a login string and a password string) from a device that is authorized to have possession of the client-based decryption key (e.g., a home computer that acts as a home base for roving devices, e.g., smartphones, wearable computers, etc., or a central server that is configured to store more than one client-based decryption key and to hand out the keys in response to receipt of the proper login plus password string, or through use of an additional factor to verify what device is receiving the key).

Referring again toFIG. 13B, operation1316may include operation1318depicting retrieving the client-based decryption key that is at least partly based on the particular client code from the image capture device that captured the image and that is authorized to have possession of the client-based decryption key. For example,FIG. 8, e.g.,FIG. 8B, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring from a device that is configured to allow a login by the client module818retrieving the client-based decryption key that is at least partly based on the particular client code (e.g., a 256-byte block of data associated with a user of the image capture device) from the image capture device (e.g., a wearable computer, e.g., a hypothetical Apple “iGlasses”) that captured the image and that is authorized to have possession of the client-based decryption key.

Referring again toFIG. 13B, operation1006may include operation1320depicting retrieving the client-based decryption key from a memory when it is determined that the client that is associated with the image capture device is logged into a particular device. For example,FIG. 8, e.g.,FIG. 8B, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device acquiring from a memory of a particular device to which the client is logged into module820retrieving the client-based decryption key from a memory (e.g., a memory of a device), when it is determined that the client that is associated with the image capture device (e.g., a wearable computer, e.g., a Nokia SMARTglasses device) is logged into a particular device (e.g., a home computer that is associated with the image capture device, e.g., a user takes the picture with her Nokia SMARTglasses, and if it is approved for decryption, it is transmitted to her home computer and then the key is retrieved and the image decrypted when she logs in to her home computer).

Referring now toFIG. 13C, operation1006may include operation1322depicting retrieving the client-based decryption key from a memory when it is determined that the particular client code has been inputted by the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8C, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device retrieving in response to a detection of input of the particular client code module822retrieving the client-based decryption key from a memory when it is determined that the particular client code (e.g., a code derived from a user's login to a third party application that runs on the device) has been inputted by the client that is associated with the image capture device (e.g., a wearable computer, e.g., a hypothetical Samsung “Spectacles” device).

Referring again toFIG. 13C, operation1322may include operation1324depicting retrieving the client-based decryption key from a memory when it is determined that the particular client code has been inputted by the client that is associated with the image capture device as a login. For example,FIG. 8, e.g.,FIG. 8C, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device retrieving in response to a detection of input of the particular client code as a login to a device module824retrieving the client-based decryption key from a memory when it is determined that the particular client code has been inputted by the client that is associated with the image capture device (e.g., a wearable computer, e.g., a hypothetical wearable computer, e.g., an Apple “iGlasses” device) as a login (e.g., a login to identify to the device who is using the image capture device).

Referring again toFIG. 13C, operation1006may include operation1326depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is assigned to the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8C, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is assigned to the client that is associated with the image capture device acquiring module826procuring the client-based decryption key that is at least partly based on the particular client code (e.g., a 64-bit code assigned to the user by a program that is part of the operating system of the image capture device), wherein the particular client code (e.g., the assigned 64-bit code) is assigned to the client (e.g., the user of the image capture device) that is associated with (e.g., has a login for, purchased, used, or has data about them stored on the device) the image capture device (e.g., a wearable computer, e.g., a Fujitsu Laser EyeWear device).

Referring again toFIG. 13C, operation1326may include operation1328depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is assigned to the client that is associated with the image capture device by the image capture device. For example,FIG. 8, e.g.,FIG. 8C, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is assigned to the client by the image capture device acquiring module828procuring the client-based decryption key that is at least partly based on the particular client code (e.g., a code derived from random user inputs), wherein the particular client code is assigned to the client (e.g., the user) that is associated with the image capture device (e.g., a wearable computer, e.g., a hypothetical Microsoft “KinectVision”) by the image capture device (e.g., the image capture device samples random user input at pseudorandom times, and then builds a particular client code from those inputs, and assigns that code to the user).

Referring again toFIG. 13C, operation1006may include operation1330depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is originally defined by the client that is associated with the image capture device. For example,FIG. 8, e.g.,FIG. 8C, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is generated through client input to the image capture device acquiring module830procuring the client-based decryption key that is at least partly based on the particular client code (e.g., an extra-long security phrase), wherein the particular client code is originally defined by the client (e.g., by typing in the extra-long security phrase) that is associated with the image capture device (e.g., with a wearable computer, e.g., a DigiLens DL40).

Referring now toFIG. 13D, operation1006may include operation1332depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is a login code that is distributed to the client to facilitate access to a service configured to operate on the image capture device. For example,FIG. 8, e.g.,FIG. 8D, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is a login code that is distributed to the client to facilitate access to an application configured to be loaded into a memory of the image capture device acquiring module832procuring the client-based decryption key that is at least partly based on the particular client code (e.g., a login for an image editing service that can run on the image capture device), wherein the particular client code (e.g., a login for an image editing service that can run on the image capture device) is a login code that is distributed to the client to facilitate access to a service (e.g., an image editing service) configured to operate on the image capture device (e.g., a wearable computer, e.g., a hypothetical Microsoft “KinectVision”).

Referring again toFIG. 13D, operation1006may include operation1334depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to the client for which data is stored on the image capture device. For example,FIG. 8, e.g.,FIG. 8D, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client for which the image capture device is configured to store associated client data acquiring module834procuring the client-based decryption key that is at least partly based on the particular client code (e.g., a code associated with a user), wherein the particular client code is related to the client for which data is stored on the image capture device (e.g., a wearable computer, e.g., a LifeLog device).

Referring again toFIG. 13D, operation1006may include operation1336depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to the client that operated the image capture device when the captured image was captured. For example,FIG. 8, e.g.,FIG. 8D, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that operated the image capture device acquiring module836procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code (e.g., a 64-bit code that is the user's login name, with random characters appended to it until 64 bits are reached) is related to the client that operated the image capture device (e.g., a wearable computer, e.g., an EyeTap device).

Referring again toFIG. 13D, operation1006may include operation1338depicting procuring the client-based decryption key that is at least partly based on the particular client code, wherein the particular client code is related to the client that is associated with the image capture device that is configured to be worn by the client. For example,FIG. 8, e.g.,FIG. 8D, shows data that includes the client-based decryption key that is at least partly based on the particular client code that is related to a client that is associated with the image capture device configured to be worn by the client acquiring module838procuring the client-based decryption key that is at last partly based on the particular client code (e.g., a code that uses the user's login to the device to seed a random number generator that generates a 2048 digit number), wherein the particular client code (e.g., the 2048 digit number) is related to the client (e.g., the client's login was used to generate the number, and the number is used to generate a set of encryption keys used to encrypt images that were captured at the command of the client) that is associated with the image capture device (e.g., a wearable computer, e.g., an Oculon Optoelectronics device) that is configured to be worn (e.g., has a shape that allows wearing, e.g., like eyeglasses or a headset) by the client (e.g., the user).

FIGS. 14A-14Bdepict various implementations of operation1008, depicting decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with the image capture device, according to embodiments. Referring now toFIG. 14A, operation1008may include operation1402depicting decrypting the client-based encrypted image through use of the client-based decryption key that is at least partly based on the particular client code that is related to the client associated with a wearable computing device. For example,FIG. 9, e.g.,FIG. 9A, shows application of the client-based decryption key that is at least partly based on the particular client code that is related to the image capture device that is a wearable computing device to the client-based encrypted image facilitating module902decrypting the client-based encrypted image (e.g., an image of four people shooting doubles pool at a bar) through use of the client-based decryption key that is at least partly based (e.g., is derived from) on the particular client code (e.g., a client login to a particular application that is loaded on the image capture device) that is related to the client (e.g., the wearer of the wearable computer) associated with a wearable computer device (e.g., a Google Glass device).

Referring again toFIG. 14A, operation1008may include operation1404depicting decrypting the client-based encrypted image through application of the client-based decryption key to remove encryption from the client-based encrypted image. For example,FIG. 9, e.g.,FIG. 9A, shows application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image to remove encryption facilitating module904decrypting the client-based encrypted image (e.g., an image of four friends on a camping trip, one of whom is a minor celebrity) through application of the client-based decryption key to remove encryption (e.g., RSA-based encryption) from the client-based encrypted image (e.g., the image of four friends on a camping trip, one of whom is a minor celebrity).

Referring now toFIG. 14B, operation1008may include operation1406depicting generating a decrypted image through decryption of the client-based encrypted image, wherein said decryption utilizes the client-based decryption key. For example,FIG. 9, e.g.,FIG. 9B, shows application of the client-based decryption key that is at least partly based on the particular client code to the client-based encrypted image to generate a decrypted image executing module906generating a decrypted image (through decryption (e.g., through use of a cryptographic hash algorithm) of the client-based encrypted image (e.g., the image of three people having a drink at the bar), wherein said decryption utilizes (e.g., uses) the client-based decryption key (e.g., the key that is configured to remove the client-based encryption.

Referring again toFIG. 14B, operation1008may include operation1408depicting storing the decrypted image in a memory. For example,FIG. 9, e.g.,FIG. 9B, shows decrypted image storing in a memory of a device module908storing the decrypted image (e.g., an image of three people having a drink at a bar) in a memory (e.g., a storage, e.g., removable storage, or fixed storage).

Referring again toFIG. 14B, operation1408may include operation1410depicting storing the decrypted image in the memory that is accessible to one or more image distribution applications. For example,FIG. 9, e.g.,FIG. 9B, shows decrypted image storing in a memory that is configured to be accessible to one or more image distribution applications module910storing the decrypted image (e.g., an image of two people kissing in public) in the memory (e.g., of the device) that is accessible to one or more image distribution applications (e.g., email, a blogging application, a social network posting application, a photo editing application, a share drive (e.g., DropBox or SkyDrive).

Referring again toFIG. 14B, operation1410may include operation1412depicting storing the decrypted image in the memory that is accessible to a social network site upload application. For example,FIG. 9, e.g.,FIG. 9B, shows decrypted image storing in a memory that is configured to be accessible to one or more social network site upload applications module912storing the decrypted image (e.g., an image of two people having dinner at a romantic restaurant) in the memory that is accessible to a social network site (e.g., Facebook) upload application (e.g., a Facebook “app” for a hypothetical wearable computer, e.g., an Apple “iGlasses”).

Referring again toFIG. 14B, operation1408may include operation1414depicting storing the decrypted image in a memory of a device other than the image capture device. For example,FIG. 9, e.g.,FIG. 9B, shows decrypted image storing in a memory of a device other than the image capture device module914storing the decrypted image (e.g., an image of three people at a Washington Capitals hockey game) in a memory of a device (e.g., a tablet device carried by the wearer of the wearable computer that captured the image) other than the image capture device (e.g., a wearable computer that captured the image, e.g., a hypothetical Samsung “Spectacles”).

Referring again toFIG. 14B, operation1414may include operation1416depicting storing the decrypted image in the memory of a home computer device linked to the client that is associated with the image capture device. For example,FIG. 9, e.g.,FIG. 9B, shows decrypted image storing in a memory of a home computer device linked to the client module916storing the decrypted image (e.g., an image of three friends doing shots at a bar) in the memory of a home computer device linked to the client (e.g., the client has a login at the home computer) that is associated with (e.g., owns, or was wearing when the image was captured) the image capture device (e.g., a wearable computer, e.g., a DigiLens DL40).

While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.).

This application may make reference to one or more trademarks, e.g., a word, letter, symbol, or device adopted by one manufacturer or merchant and used to identify and/or distinguish his or her product from those of others. Trademark names used herein are set forth in such language that makes clear their identity, that distinguishes them from common descriptive nouns, that have fixed and definite meanings, or, in many if not all cases, are accompanied by other specific identification using terms not covered by trademark. In addition, trademark names used herein have meanings that are well-known and defined in the literature, or do not refer to products or compounds for which knowledge of one or more trade secrets is required in order to divine their meaning. All trademarks referenced in this application are the property of their respective owners, and the appearance of one or more trademarks in this application does not diminish or otherwise adversely affect the validity of the one or more trademarks. All trademarks, registered or unregistered, that appear in this application are assumed to include a proper trademark symbol, e.g., the circle R or bracketed capitalization (e.g., [trademark name]), even when such trademark symbol does not explicitly appear next to the trademark. To the extent a trademark is used in a descriptive manner to refer to a product or process, that trademark should be interpreted to represent the corresponding product or process as of the date of the filing of this patent application.

Throughout this application, the terms “in an embodiment,” “in one embodiment,” “in an embodiment,” “in several embodiments,” “in at least one embodiment,” “in various embodiments,” and the like, may be used. Each of these terms, and all such similar terms should be construed as “in at least one embodiment, and possibly but not necessarily all embodiments,” unless explicitly stated otherwise. Specifically, unless explicitly stated otherwise, the intent of phrases like these is to provide non-exclusive and non-limiting examples of implementations of the invention. The mere statement that one, some, or may embodiments include one or more things or have one or more features, does not imply that all embodiments include one or more things or have one or more features, but also does not imply that such embodiments must exist. It is a mere indicator of an example and should not be interpreted otherwise, unless explicitly stated as such.