Patent Grant
9819490
The present application is related to, and claims the earliest available effective filing date(s) from (e.g., claims earliest available priority dates for other than provisional patent applications; claims benefits under 35 USC §119(e) for provisional patent applications), and incorporates by reference in its entirety all subject matter of the following listed application(s) (the “Related Applications”) to the extent such subject matter is not inconsistent herewith; the present application also claims the earliest available effective filing date(s) from, and also incorporates by reference in its entirety all subject matter of any and all parent, grandparent, great-grandparent, etc. applications of the Related Application(s) to the extent such subject matter is not inconsistent herewith. The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation or continuation in part. (see CITATION). The present applicant entity has provided below a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant entity understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization such as “continuation” or “continuation-in-part.” Notwithstanding the foregoing, applicant entity understands that the USPTO's computer programs have certain data entry requirements, and hence applicant entity is designating the present application as a continuation in part of its parent applications, but expressly points out that such designations are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).
The present application relates, in general, to sharing mechanisms that allows sharing images between multiple devices at least partially based on a regional proximity of the devices.
One aspect includes but is not limited to: transmitting at least one portion of at least one image representation from a shared image device in a manner at least partially relying on a positioning of the shared image device within a sharing region. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present application.
Another aspect includes but is not limited to: receiving at a shared image device at least one portion of at least one image representation at least partially in response to a positioning of the shared image device within a sharing region. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present application.
Yet another aspect includes but is not limited to: establishing a sharing region in which at least one first shared image device can share at least one image representation with at least one second shared image device. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present application.
Another aspect includes but is not limited to: a shared image device configurable to receive at least a portion of at least one image representation to at least one other shared image device at least partially in response to a positioning of the shared image device within a sharing region.
Another aspect includes but is not limited to: a shared image device configurable to transmit at least a portion of at least one image representation to at least one other shared image device at least partially in response to a positioning of the shared image device within a sharing region. In addition to the foregoing, other apparatus aspects are described in the claims, drawings, and text forming a part of the present application.
Another aspect includes but is not limited to: means for receiving at least one portion of at least one image representation at a shared image device at least partially in response to a positioning of the shared image device within a sharing region. In addition to the foregoing, other apparatus aspects are described in the claims, drawings, and text forming a part of the present application.
Another aspect includes but is not limited to: means for transmitting at least one portion of at least one image representation at a shared image device at least partially in response to a positioning of the shared image device within a sharing region. In addition to the foregoing, other apparatus aspects are described in the claims, drawings, and text forming a part of the present application.
In addition to the foregoing, various other method and/or system aspects are set forth and described in the text (e.g., claims and/or detailed description) and/or drawings of the present application.
The foregoing contains, by necessity, simplifications, generalizations and 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 in the text set forth herein.
The use of the same symbols in different drawings typically indicates similar or identical items.
This disclosure describes a number of embodiments of sharing mechanisms 102 that can each be integrated in, and/or utilized by, at least one shared image device 101, as described for example with respect to
A variety of embodiments of the shared image network 100 are described herein such that a number of shared image devices 101 are contained within a sharing region 103. Within this disclosure, the sharing region 103 can represent two-dimensional or three-dimensional geographic area or volume in which the shared image devices are intended to operate. The sharing region can be set differently in a variety of embodiments such as, for example, for a fixed time duration, or for as long as a shared image device, or another device, is positioned proximately of the sharing region. In certain embodiments, a particular user can set up a sharing region as desired based on, for example, global positioning system (GPS) coordinates, field of view of one or more shared image devices, defined locating relative to a particular building or structure, etc. A variety of configurations of sharing regions 103 are described herein, including those sharing regions that are established with respect to a shared image device, those sharing regions that are established with respect to a fixed area, and/or those sharing regions that are established with respect to a combination of a shared image device and a fixed area. If in certain embodiments, positional information such as provided by a global positioning system (GPS), Loran, etc., can be utilized to determine positional coordinates of the sharing region.
In certain embodiments, any shared image device of the type being utilized by the sharing session that is within the sharing region may be allowed to join the sharing session. In other embodiments, the user of the shared image device may have to provide a password to join the sharing session. In still other embodiments, the user of shared image device can provide a sharing password in addition to being within the sharing region to join the sharing session. As such, there are a variety of permissible techniques that can be utilized to join the sharing session, that are within the intended scope of the present disclosure.
In certain instances, but not others, a particular sharing region 103 may be temporarily and/or geographically defined to correspond to a particular sharing session. As such, a sharing session may be established relative to a particular geographic location for a particular duration, such as within a child's house for a duration of a birthday party, or within a reception area for a duration of a wedding. In certain instances but not others, the sharing region in the sharing session can thereby be geographically related to the particular area for the duration of the session, such as a particular person's house, park, building, commercial setting, sports event, business event, etc.
This disclosure provides a number of embodiments of mechanisms by which one or more shared images, that may or may not correspond to a particular sharing region, can be transferred either: from a capturing shared image device to a peripheral shared image device, from a peripheral shared image device to a capturing shared image device, between one or more peripheral shared image devices, or between one or more capturing shared image devices. Such transferring of shared images between multiple shared image devices can occur either directly or indirectly (using an intermediate device) to another one or more peripheral shared image devices or capturing shared image devices. Such an indirect communication can occur via either one or more peripheral shared image devices or a capturing shared image device, or alternatively can occur via at least one other device that is not a capturing shared image device or a peripheral shared image device.
This disclosure also describes a variety of the communication links 104 that can rely at least partially upon a regional proximity of at least one shared image device within a sharing region. Regional proximity can relate to the type of communication link being utilized between the shared image devices and/or the sharing regions. For example, certain embodiments of communication links may work well when the multiple shared image devices are within the same home, building, campus, or other geographically-definable areas. As such, the regional proximity of one or more shared image devices (which may include one or more shared image devices that can capture images as well as one or more shared image devices that cannot capture images) provide a mechanism to transfer shared images therebetween. In different embodiments, the sharing region 103 may be established with respect to a transmitting shared image device, a receiving shared image device, another device that can provide positioning information, etc., or some other source of geographic information.
Different embodiments of the shared image devices 101 can each perform one or more processes including, but not limited to capturing, creating, processing, storing, printing, transferring, obtaining, retaining, displaying, and/or receiving the shared images. Different embodiments of the shared images can be configurable as still images (e.g. photographs) and/or motion images (e.g., moving pictures). Many embodiments of the sharing mechanism 102 can be integrated between one or more shared image devices 101. Within the disclosure, certain embodiments of the shared image devices 101, such as digital cameras, camcorders, etc. that can capture shared image information are referred to as “capturing shared image devices”, which can be considered as distinct from those shared image devices 101 that cannot capture shared image information. The capturing shared image devices such as digital cameras, still-picture cameras, motion picture cameras, or camcorders can be utilized within photography. Many shared image devices that cannot capture images can be referred to within this disclosure as “peripheral shared image devices”, which can perform such peripheral operations to images and/or other data as storing, saving, store and forwarding, displaying, projecting and/or otherwise processing.
Within the disclosure, the terms shared image(s), image(s), image representation(s), image(s), or image information each pertain to full images, portions of images, segments of full images, magnified images, reduced resolution images, thumbnails of images, information that describes particular images such as metadata. Metadata can contain such information as the subject of the image, identifying who took the image, image location, the reference number of the image, etc. Within this disclosure, the terms “image representation” or “image” can pertain (among other things) to images, thumbnails of images, icons that pertain to images, portions of images, images having altered resolution, information pertaining to images such as metadata, etc. The term “obtain” applies to obtaining shared images either by capturing or by data transfer from another shared image device. The term “retain” applies to storing shared images for some duration regardless how temporary or permanent the storage.
In this disclosure, the term “broadcast” can apply but is not limited to: transmitting one or more shared images from one shared image device(s) in a manner such that the signal can be received by at least one (and usually multiple) other shared image device(s), transmitting to all other shared image devices, transmitting to all other shared image devices enrolled in a sharing session, and/or transmitting to only certain selected shared image devices. Broadcasting can be utilized in general networks, master-satellite networks, server-satellite networks, peer-to-peer or point-to-point (alternatively, P2P) networks, or any of variety of other applicable network configurations, certain ones of which are as described in this disclosure.
A variety of processing techniques may be utilized by different ones of the shared image devices. These processing techniques include, but are not limited to, combining multiple images into single images, and/or transforming a particular image. Examples of transforming include, but not limited to, image transforming, format-sharing of images, and watermark-transforming. Watermark-transforming includes providing additional textual, or other, image information to an image that can be used to identify the source, location, identity, and/or other information about an image. For example, if multiple shared image devices are sharing images, or portions thereof, it may be desirable to indicate using a watermark-transforming and original identity of each particular image. Transforming of an image can include, but is not limited to, such imaging aspects as image compression, resolution changing, addition of one or more audio streams, etc. Within this disclosure, the term “ancillary information” can include information that is attached to, appended to, alters, or otherwise associated with image information. Examples of ancillary information include, but are not limited to, format-shared information, associated information, textual information, audio, annotation information, image map information, executable code, data overlay information, or a transmitted license. Format-sharing can be used to apply general information that can be used to format the image at the receiving device, and is intended to include, but is not limited to, at least one from a group of formats including ancillary information, associated information, textual information, audio, annotation information, image map information, executable code, data overlay information, transmitted license, etc. In certain embodiments, by utilizing transforming, including ancillary information, etc., a shared image that is being received at a receiving shared image device can appear largely as intended by transmitting shared image device, regardless of differences in format, etc. between the transmitting shared image device in the receiving shared image device.
In this disclosure, the terms “shared image devices” “cameras”, etc. apply to such dissimilar devices as digital cameras, video cameras, and/or camcorders. The shared image device can capture certain embodiments of still images including, but not limited to, photographs or digital images. Certain embodiments of shared image devices such as a camcorder or motion picture video camera can capture motion images such as videos. The imaging devices can integrate a sharing mechanism to either capture, obtain, retain, store, or transfer such shared images. A variety of embodiments of the sharing mechanism can therefore capture or otherwise process, retain, or obtain such exemplary shared images as digital still images or digital motion images that are provided either alone or in combination with video, audio, music, etc.
Examples of shared image devices 101 that are not configurable to capture shared image information can include certain laptop computers, desktop computers, portable image store and display devices, digital video disk (DVD) devices, personal display assistants (PDA), printers, compact disk (CD) drives, Pods (a trademark of Apple Computers), etc. Certain embodiments of portable image store and display devices can be configurable to utilize peer-to-peer communications, and may be capable of transferring shared images there between. Certain embodiments of the shared image devices that cannot capture shared image information operate largely to retain, obtain, store, process, and/or display shared images.
To provide a sharing session utilizing a number of shared image devices, it is important that each device be allowed to establish a permission to join the sharing session, and additionally that each device be provided an ability to join the sharing session. The establishing the permission to share, and the providing the ability to share, by each shared image device may be combined in some manner, or may be maintained as distinct operations.
In different embodiments, sharing mechanisms can provide a largely automated publishing function between multiple shared image devices. Certain shared image(s) that are captured by a shared image device can be distributed or transmitted to, and/or received by, other shared image devices, and thereby be “published” and made public (and therefore can be considered to be no longer private). One embodiment of the sharing mechanism 102 allows the shared image device 101 to toggle on/off publishing of the shared images to switch between the images being public and private. In certain embodiments, such publishing can be automatically set for a prescribed duration such as temporally or more permanently defined by a “sharing session”, after which duration the shared image devices each can return to their non-sharing configuration, or other configuration before they joined the sharing session. In other embodiments, the sharing session can be permanent or have a lengthy duration.
Certain embodiments of the shared image device 101 that include at least a portion of the sharing mechanism 102 can be modifiable to provide a variety of functions. Many embodiments of shared image devices, such as cameras or camcorders, that can capture shared images can also function as storage devices to store some data pertaining to shared images. Certain capturing embodiments of shared image devices can also act as a memory acquisition device that obtains or retains pictures from other shared image devices. Other embodiments of the shared image device 101 such as portable image storage and display devices can be configurable as storage devices, in which shared images can be stored, accessed, and/or displayed.
The very structure, nature, or operation of certain embodiments of such imaging devices such as cameras, digital cameras, or camcorders are likely to change as the associated technology improves. For example, it is likely that many digital cameras and/or camcorders will develop greater memory storage capabilities as the associated memory storage technologies improve. In this disclosure, multiple capturing shared image devices and/or multiple peripheral shared image devices could be “networked” in such a manner that a large number of images can be transferred between multiple capturing shared image devices. Certain capturing shared image devices can be optimized for their data storage or processing capabilities, and as such may act somewhat like computer servers. Other capturing shared image devices can be designed for their photographic or zooming abilities, and as such may be considered as true capturing or imaging devices. As the characteristics and abilities of different shared image devices vary more, the benefits of networking the shared image devices increases as well. Certain sharing concepts, as described herein, enhance the networking aspects of the capturing shared image devices.
In this disclosure, “subscribing” pertains to a user joining their shared image device (which, in different embodiments, can be configured either as a capturing shared image device or as a peripheral shared image device) in a session to provide shared images to and/or receive shared images from other shared image devices. In certain embodiments of the shared image device, it can be desired to subscribe to different functions using different mechanisms. While any combination of particular functions may be described with respect to this disclosure, this disclosure is intended to describe other shared image devices that can perform varied or alternative functions.
Certain embodiments of shared image devices 101 provide a mechanism by which certain shared image devices that are enrolled in a sharing session may not share every image that is being captured. For example, certain images captured by a particular shared image device may be considered as private, and therefore are not for general distribution during a sharing session with other member shared image devices. Certain communication links 104 that connect between pairs of shared image devices can thereby be temporarily and/or permanently configured to be private in one direction while public in another direction, public in both directions, or private in both directions. For example, it may be desired to configure a communication link from a capturing shared image device to a peripheral shared image device to be either public or private; while the communication link from the peripheral shared image device to the capturing shared image device can be the reverse or the same.
Certain embodiments of the shared image devices 101 can provide such operations as, but are not limited to: performing active sharing between multiple shared image devices, temporarily pausing or muting the active sharing, resuming the active sharing after temporarily pausing or muting, connecting with other devices and/or people, or temporarily performing or delaying a variety of operations. Such temporary pausing or muting of sharing operations may be equated to temporarily halting a subscription for a particular shared image device; and in many embodiments the shared images that were shared during this pausing or muting period can be transmitted or collected after the pausing or muting. Other aspects and concerns of sharing the shared images can relate to managing the shared image devices. Examples of these tasks include controlling and selecting image resolution, allowing shared images to exit a particular shared image device but not enter the same shared image device, or vice versa.
It is to be understood that certain embodiments of the shared image device 101 can be configurable in a variety of network configurations, for example as described in this disclosure with respect to
Certain embodiments of shared image devices 101, as described with respect to
In another embodiment, a share mechanism 102 can be included in a computer/controller based program to control the sharing process between multiple shared image devices. As such, certain embodiments of share mechanisms 102 can integrate a plurality of shared image devices, since more than one shared image device are involved in sharing images. Such a share mechanism can include an actuating portion that can actuate the sharing mechanism between a number of shared image devices, a graphical user interface (GUI) or computer display that can display copies of the shared images to the users across multiple shared image devices, and an authentication or authorization portion that can provide authentication or authorization between multiple shared image devices.
A number of other embodiments of the actuating portion of the sharing mechanism can differ considerably from a manually-actuated shared mechanism (such as a share button or share menu) to more automatic type devices. Certain embodiments of such shared image devices can rely on a regional proximity between at least one shared image device and the sharing region 103. Certain embodiments of the sharing mechanism 102 can utilize near-field shared image devices that are within a prescribed range that can be automatically actuated to copy and/or share the shared image information. In certain embodiments, the actuating portion of the share mechanism can even be remotely positioned from the associated shared image device 101, such as in a remote-control of the type that is in common usage for television, etc.
In another embodiment as described with respect to
Examples of Shared Image Devices Relying on Regional Proximity
In certain embodiments, various users can thereby transfer video, images, or some other type of information based on the regional proximity of one or more of the shared image devices 101 to a particular sharing region (the sharing region may last for the duration of a sharing session as described herein). Any combination of a plurality of capturing shared image device(s) and/or peripheral shared image device(s) can utilize regional proximity therebetween to establish the sharing mechanism 102. A variety of embodiments of the shared image device 101 can thereby rely on a variety of types of regional proximity between certain shared image devices and their sharing region to allow their sharing. The embodiment of geographic regional proximity between pairs of shared image devices, geographic regional proximity between a shared image device and the sharing region 103, examples of which are described with respect to
In certain embodiments, the term “proximity” or “regional proximity” indicates that the shared image device is positioned relative to a geographic region outlined by the sharing region 103. The sharing region 103 can be established in a variety of techniques either with respect to either of the shared image devices, or with respect to some geographic location (e.g., as determined by a global positioning system (GPS), or other positional determining device). In many embodiments, the term “regional proximity” indicates that the shared image device(s) 101 are sufficiently close to the sharing region to operably couple to each other, such as to allow establishing of a communication link 104 therebetween means. In certain embodiments, a wireless link can provide the geographic proximity that allows data transfer of the shared images or portions thereof. The particular dimensions of a sharing region will likely vary depending upon the particular sharing region. For example, a sharing region associated with the child's birthday party will likely include the geographic sharing regions of the child's house, and perhaps around the house. By comparison, the sharing regions associated with a large sporting event may utilize at least portions of the stadium, a concert hall, etc., and perhaps around the stadium, etc.
To establish a sharing region, it may be necessary to establish communication links between at least certain ones of the shared image devices 101 and/or other devices within, or relative to, the sharing region 103. In one embodiment, the multiple shared image devices 101 can operably couple within the shared image network 100 using a series of communication links 104; different embodiments of the communication links are described with respect to
Certain embodiments of the wireless communication link can utilize a variety of electromagnetic radiation to transmit data. The electromagnetic radiation that provides one embodiment of the wireless communication link 104 can include, but is not limited to, infrared, ultraviolet, near infrared, and/or optical signals. In one embodiment, a devoted optical communication link can cause data corresponding to the images to be transmitted between respective shared image devices. The communication link 104 can be configurable, in one embodiment, to operably couple a transmitting shared image device to a receiving shared image device. The transmitter, receiver, and/or transceiver portions of the communication link are to be configurable to carry sufficient data over the communication link considering the current task and/or network configuration.
In another embodiment, a camera flash or other optical signaling device can act as a communication link, that can be used to transmit image information. The intensity of the optical device (e.g., camera flash) can be modulated between different levels (including, but not limited to, turning the optical device on and off) to transfer a variety of shared image data. Such directing of the optical device in a suitable direction should act such that reflected light does not interfere with the modulated incident light produced by the optical device.
One aspect of using certain embodiments of the camera device, other such wireless link, etc. is that multiple receiving shared image devices can simultaneously obtain shared images from a single transmitting shared image device (e.g., by the multiple receiving shared image devices receiving the same camera flash or other optical-link that is configured to transmit data substantially simultaneously).
In many embodiments of the interrelated shared image devices 101 as described with respect to
Different embodiments of geographic-based regional proximity can range to a variety of dimensions including from within inches, to in the same room, to within the same building, to capable of accessing the same wireless LAN, to in the same stadium or part of a city, or beyond depending upon the technologies associated with the particular application or the communication link. In considering the application of certain commercially available transmitter/receiver device capabilities, Bluetooth (a trademark of the Bluetooth Special Interest Group, a trade association) can have an effective range of approximately 10 meters. Wireless Fidelity (WiFi, refers in this disclosure generically to any type of 802.11 network) can be located in a house or building, and can have an arbitrarily large range (especially by locating replicators or repeaters in each communication link 104 between multiple pairs of shared image devices 101). As such, shared image devices 101 can effectively communicate to each other through relatively extensive communication links 104 of variable dimensions depending upon the particular technology being utilized. If a particular shared image device 101 has WiFi capabilities, the shared image device can be considered to have access to the Internet.
If the shared image network 100 is established as a close regional-proximity shared image network, each user can be provided with their individual “shared image device” 101 that can each be somehow proximally located with respect to the sharing image network during its sharing session. Each shared image device can be configurable to join the sharing session, and thereby (e.g., using personal display assistant (PDA) terminology) sync their shared image device 101 to the current shared image devices.
In certain embodiments but not others, one shared image device 101 can continuously have its sharing mechanism actuated as to be in a sharing state. For example, a user can walk into a room with three friends that are currently enrolled in the sharing session, position the new shared image device 101 within the regional proximity of at least one of their shared image devices, and the shared images can be transferred utilizing such a technique such as being quick-synched to the new shared image device 101 over the communications link.
Certain commercially-available cellular phones include embedded cameras (therefore providing photographic capabilities) that can be configurable such that the images are transferred from that camera cellular phone to at least one other camera cellular phone, at least one land-phone, or at least one other receiving device using either a wireless, or some other suitable, connection. Many of the commercially-available camera cellular phones can thereby be considered to “push” one or more images to another device (such as a cellular phone, a computer, a PDA, etc.) with a display. Such transfer mechanisms that “push” these pictures utilize the Internet, e-mail, or a similar file-transfer addressing mechanism (e.g., e-mail address or some associated addressing scheme). In certain embodiments, addressing the data associated with photographs can take some time, while in other embodiments such addressing is simplified. Addressing can be challenging in situations where the address of the recipient shared image device 101 is unknown or inaccessible. Certain embodiments of shared image devices can utilize addressing mechanisms.
Many embodiments of shared image devices 101, as described in this disclosure with respect to
Within this disclosure, many embodiments of capturing shared image devices can be considered as similarly configured while others are not. Similarly, any embodiments of peripheral shared image devices can be considered as similarly configured while others are not. In this disclosure, the terms “similarly configured”, “similarly configurable”, or alternatively “similar” as applied to many embodiments of the shared image devices 101, can pertain to how each shared image device 101 processes or relates to its respective shared images. For example, certain embodiments of digital cameras, camcorders, video cameras, etc. can be configurable as capturing shared image devices that are capable of capturing, transferring, retaining, or obtaining such shared images as still images or motion images. In the embodiment as described with respect to
In many imaging situations, the resolution, imaging quality, and imaging characteristics of shared images are dependent on that particular shared image device that is performing the imaging. As such, even though shared image information may be shared between multiple shared image devices (in different embodiments within an, or even external of, a sharing region), the imaging quality of that shared image depends on the particular shared image device that images or captures, e.g., photographs, the shared information. As such, it may be desirable to capture many of the images with a high-quality shared image device, e.g., a relatively expensive high resolution, by using a number of shared image devices of the types as described in this disclosure.
Under certain circumstances, certain users of the shared image devices may desire to store a relatively large number of captured images within their shared image device. As such, it may be desirable to utilize lower-resolution shared image devices to capture lower-resolution versions of certain images.
In certain instances, an optimal resolution of the images that may be captured by the different shared image device(s) may not be a deciding factor for a potential user selecting to share images with a particular shared image device. Perhaps a particularly good photographer is using a particular shared image device. Alternately, perhaps a shared image device is capturing a particularly desirable subject. Perhaps a particular shared image device can take excellent pictures under certain circumstances, for some known or unknown reason. Certain capturing shared image devices may rely upon an optical or a software-base zooming technique. As such, many participants in the sharing session may be interested in obtaining such shared images based on their inherent quality or value.
The combination of the shared image devices for a particular sharing session, as described in this disclosure, provides a technique by which one or more particular shared image devices can be selected to capture a particular shared image of a type such that shared image device may be the most appropriate.
Many embodiments of digital cameras can capture, process, display, generate, or receive digital images. Certain peripheral shared image devices 101 (e.g., certain printers, fax machines, PDAs, copiers, etc.) may generally be considered as a peripheral device, and not a similar device to digital cameras since such peripheral shared image devices cannot capture shared images, and can only perform such peripheral functions as printing, retaining, or displaying shared images. A sharing mechanism may be configurable to convey shared image information either alone, or in combination with, audio, data, or a variety of other types of information as described herein.
Many of the embodiments of the sharing image network 100 can utilize a regional proximity between certain shared image devices 101 and their shared region(s) 103 to allow for a transfer of shared image information, shared images, etc. between multiple shared image devices. The embodiment of the sharing image network 100, described with respect to
In the embodiments of the sharing image network 100 that is described with respect to
Each communication link 104 should provide sufficient bandwidth to ensure effective transfer of the shared images (e.g., images, portions of the images, metadata, video segments, and/or video stills) between the appropriate shared image devices 101. Providing such effective shared image transfer can ensure satisfactory operation of the sharing image network 100 as described in this disclosure.
The embodiment of the shared image network 100, as described with respect to
In certain embodiments of the sharing image network 100, each shared image device 101 can be configurable to be capable of accessing the shared images captured by other ones of shared image devices 101 during the sharing session.
As described with respect to
Certain computers acting as servers might be named based on the data that they can store or produce (e.g., file servers, data servers, web page servers, etc.). As such, certain embodiments of the computer 302 as described with respect to
As such, certain ones of the satellite shared image devices 101b can be configurable as the computer 302 to be capable of handling queries relatively quickly and accurately. In certain embodiments, the users of certain shared image devices 101 can therefore include queries directed to the particulars of the sought shared images. Another advantage of certain computers 302 is that the storage capability of certain embodiments of the computers can substantially match a value of the number of captured shared images during a sharing session.
Example of Regional Proximity-Based Sharing Technique
This disclosure described a number of embodiments of a regional proximity-based sharing technique. One embodiment of the regional proximity-based sharing technique utilizes a computer or controller of the type described herein with respect to
Since multiple shared image devices can share data (at least one that sends the shared image information and at least one that receives the shared image information), each shared image device can form a portion of the sharing mechanism. In certain embodiments, actuating the actuating mechanism of a sharing mechanism can cause a particular shared image device to share or publish to other similar shared image devices. Such sharing or publishing can occur even if there is not another shared image device in sufficiently close geographic regional proximity, based largely on inclusions of additional shared image devices (each of which includes a store-and-forward mechanism). The additional shared image devices can be configurable to allow serial data transmission through a sequence of such intermediate located shared image devices that operatively couple the terminal shared image devices. The store-and-forward mechanism can temporarily store data in one of these shared image devices, and can generate copies of stored shared images in the form of data from that shared image device following a desired prescribed duration.
Under certain circumstances, only one shared image device may be a member of a session. For example, if a user of a particular shared image device 101 is the first one to join a sharing session (e.g., get to an event), then that first user may capture pertinent images, and the sharing mechanism allows others to access the pictures captured by the first user of a shared image device 101 at that sharing session. As such, at one particular time, only a single shared image device may join the sharing session, and effect sharing or copying of the shared images. Prior to a wedding or child's birthday, for example, a professional photographer may capture a number of images that pertain to preliminary events of that sharing session, and which would perhaps be desirable to other session members who would join that sharing session. In another instance, a leader of a business meeting may prepare a set of shared images prior to the meeting that relate to the meeting, and which would subsequently be accessible by other members of the meeting.
In other embodiments, at least two shared image devices 101 might establish a particular sharing session. For example, assume in certain embodiments that multiple shared image devices can be configurable as disposable cameras whose session shared images can be shared, processed, and/or made accessible. In certain embodiments, but not others, multiple shared image devices (such as those of the disposable variety) can be sold together to be associated with a prescribed sharing session, such as a birthday, wedding, business event, etc.
Other embodiments of shared image devices are likely to be associated with a single owner for a longer duration, and can be provided with a controllable sharing mechanism to allow multiple shared image devices to be controllably configurable to interface with each other for a distinct duration of, e.g., a distinct sharing session. Many embodiments of the shared image devices can be controllably adjustably configurable to allow the shared image device to join another session. In certain embodiments a single shared image device can perhaps even join multiple simultaneous sharing sessions.
In considering certain embodiments of the master-satellite configuration as described with respect to
The particular configuration of shared image devices and the shared images can largely represent a design choice based on intended usage, and networking or device configurations and operating characteristics. These particular configurations can be selected depending upon the particular sharing session, event type, shared image device 101 type or other operational characteristic, and can be selected by the “owner” or other participants of each particular sharing session. In some embodiments where a satellite shared image device has insufficient memory storage to store the full versions of the shared images that have been captured for a particular sharing session, the master shared image device can be provided with sufficient data storage to contain the full versions of the shared images that are being captured during the sharing session.
In certain embodiments but not others, at least some of the shared images that are being stored at the master shared image device will have the highest resolution available so that when the full images are requested from the at least certain other ones of the shared image devices, the full images can be provided.
In certain embodiments of the shared image networks of shared image devices 101 (while not with other embodiments), one purpose is to ensure those shared images captured by each one of shared image devices have been accessed, captured, stored, printed out, or has undergone some desired action. As such, in certain embodiments, each shared image device 101 may not obtain all the copies of each shared image generated by every shared image device for that sharing session. As such, in certain embodiments, it may be useful for a user of at least one shared image device 101 to provide a peripheral device (such as a printer or portable image storage device such as a CD drive) at a sharing session. The peripheral device may thereupon print and/or obtain and/or retain the desired shared images for each user of the member shared image devices 101 that are associated with the sharing session who wish to have the images in printed or stored form.
In one embodiment, a shared image device 101 can include a timeout mechanism. As such, if a user of a shared image device 101 leaves the sharing session, and they forget to deactivate the sharing mechanism, then the timeout mechanism can deactivate the shared image device with respect to the sharing session, after a prescribed amount of time. Certain embodiments of the sharing session can include multiple shared image devices 101 that each includes a timeout mechanism such that the sharing session terminates soon after the last member of the sharing session (and their shared image device) leaves the regional proximity that is associated with the session.
For example, it may be desired to couple a capturing shared image device such as a digital camera or camcorder with one or more peripheral shared image devices such as a printer, a projector, a computer, and/or a CD burner. Such a combination of dissimilar shared image devices might, or might not, be associated with a similar combination of shared image devices. For example, one or more shared image devices such as a digital camera can be associated with a dissimilar shared image device such as a printer, computer, or projector either for a particular sharing session or permanently.
Alternatively, one or more capturing shared image devices such as a digital camera or camcorder can be associated with a dissimilar shared image device such as a printer, computer, or projector. Each of these dissimilar shared image devices may be capable of utilizing the shared images in a distinct manner. However, each of the shared image devices 550 could also share similar shared images relating to a single group sharing session (such as digital images) in its own distinct manner.
In certain embodiments, the printer, or other peripheral shared image device, can be configured as a peer in a peer-to-peer configuration, or alternately as a master or satellite in a master-satellite configuration, during the sharing session. For example, one shared image device can be configurable as a capturing shared image device such as a digital camera or camcorder at the session to capture shared images from other capturing shared image devices as described with respect to
From a high-level aspect and embodiment, a variety of distinct types of shared image devices can therefore utilize the sharing mechanism. As such, a single user might actuate a single sharing mechanism to cause a sharing of images between the printer and the digital camera (or other examples of commonly-controlled peripheral or capturing shared image devices). In certain embodiments, peripheral shared image device(s) can be networked with one or more capturing shared image devices that are owned by multiple users at a given sharing session. Consider that in some embodiments but not others, both the peripheral shared image device (e.g., printer) and at least some of the capturing shared image devices (e.g., digital cameras) rely upon the same sharing mechanism for the sharing session. In certain embodiments but not others, a peripheral shared image device that can be configurable as a shared image-server, that could function to transfer stored image data back to another computer, could include a sharing mechanism with the other computer.
A variety of peripheral shared image device(s) 101 can store or display shared images that are produced by the capturing shared image device. In certain embodiments, a peripheral device such as a projector or television shared image device 101 can be associated with a digital camera or camcorder capturing shared image device to provide a slide show or movie including the shared images provided by the latter. In other embodiments, a digital video disk (DVD) recorder can burn a CD containing shared images provided by a digital camera or camcorder shared image device. These different embodiments of shared image devices that can be configurable as capturing and/or peripheral shared image devices can still be considered as dissimilar in certain aspects but perhaps not in other aspects.
Examples of the Computer/Controller
As described within this disclosure, multiple ones of the different embodiments of the shared image devices 101 are able to transfer image information, one or more portions of images, etc. to each other via the communication link 104. One embodiment of the computer/controller 1000 includes a processor 1002, a memory 1004, a circuit portion 1006, and an input output interface (I/O) 1008 that may include a bus (not shown). Different embodiments of the computer/controller 1000 can be a general-purpose computer, a specific-purpose computer, a microprocessor, a microcontroller, a personal display assistant (PDA), and/or any other known suitable type of computer or controller that can be implemented in hardware, software, electromechanical devices, and/or firmware. Certain portions of the computer/controller 1000 can be physically or operably configurable in each shared image device as described with respect to
Certain embodiments of the memory 1004 include random access memory (RAM) and read only memory (ROM) that together store the computer programs, operands, and other parameters that control the operation of the shared image device. The memory 1004 can be configurable to contain the shared image information obtained, retained, or captured by that particular shared image device 101 (that may be configurable in different embodiments as the peripheral shared image device of the capturing shared image device).
The bus is configurable to provide for digital information transmissions between processor 1002, circuit portion 1006, memory 1004, I/O 1008, and/or the image storage device 1020. While each of the portions 1002, 1004, 1006, 1008, or 1020 are described as distinct elements, it is to be understood that by using network concepts, as well understood by those skilled in the art, multiple computers, networked-devices, processing devices, control devices, or portions thereof may be combined to provide a functionality similar to a single device while utilizing multiple devices. In this disclosure, the memory 1004 can be configurable as RAM, flash memory, semiconductor-based memory, of any other type of memory that is configurable to store data pertaining to images. The bus also connects I/O 1008 to the portions of the shared image devices that either receive digital information from, or transmit digital information to other portions of the communication system 100.
The computer/controller 1000 can perform a variety of processing tasks that are described with respect to this disclosure. These processing tasks include, but are not limited to, combining multiple images, transforming images, watermark-transforming images, format-sharing, etc. Examples of format-sharing include, but are not limited to, sharing of ancillary information, associated information, textual information, audio, annotated information, image map information, executable code, data overlay information, or transmitted license information between different shared image devices. As such, format-sharing, and other image transformation in image combining techniques can be used to largely determined how an image will appear at a receiving shared image device that has been transmitted by a transmitting shared image device.
Certain embodiments of the shared image device 101 as described with respect to
Certain embodiments of the shared image device 101 as described with respect to
The memory 1004 can provide one example of a memory storage portion. In certain embodiments, the monitored value includes, but is not limited to: a percentage of the memory 1004, a number of images that are stored in the memory 1004, or for motion images a recording interval (audio or video recording intervals).
To provide for overflow ability for the memory 1004 of certain embodiments of the shared image device 101, an image storage device 1020 can operably couple to the memory 1004 to allow a controllable transmitting of memory data from the shared image device 101 to the image storage device when the monitored value of data within the memory 1004 (e.g., the memory storage portion) exceeds a prescribed value. The prescribed value can include, e.g., some percentage amount or some actual amount of the value. In different embodiments, the image storage device 1020 can be included as a portion of the shared image device 101, as external to the shared image device, or as electrically connected (such as by an electrical coupling) to the shared image device. Different embodiments of the image storage device 1020 can be configurable as a mobile random access memory (RAM) device, a flash memory device, a semiconductor memory device, or any other memory device (that may or may not be distinct from the memory 1004) that can store images, image information, and/or any other data that can be stored within the memory 1004.
In certain embodiments, a secondary communication link 1030 can be established between the shared image device 101 (for example, the memory 1004) and the image storage device 1020. The secondary communication link 1030 can be structured similar to as the communication link 104, as described with respect to
In certain embodiments of the shared image device 101, the particular elements of the computer/controller 1000 (e.g., the processor 1002, the memory 1004, the circuits 1006, and/or the I/O 1008) can provide a monitoring function to monitor the amount of images and/or image information contained therewithin. Such a monitoring function by the shared image device can be compared to a prescribed limit, such as whether the number of images contained in the memory 1004, the amount of data contained within the memory 1004, or some other measure relating to the memory is approaching some value. In different embodiments, the limits to the value can be controlled by the user and/or the manufacturer. In certain embodiments, the memory 1004 stores motion images, video images, and/or audio images relating to, e.g., a motion picture, camcorder, video, or audio embodiment of the shared image device. In certain embodiments the measure relating to the memory approaching some value may pertain to some recording duration, such as video recording duration or audio recording duration. Using the recoding duration, certain embodiments of motion picture shared image devices can thereby quantify how many shared images, or other images, have been captured.
In certain embodiments, the I/O 1008 provides an interface to control the transmissions of digital information between each of the components in the computer/controller 1000. The I/O 1008 also provides an interface between the components of the computer/controller 1000 and different portions of the shared image device. The circuit portion 1006 can include such other user interface devices as a display and/or a keyboard.
In other embodiments, the computer/controller 1000 can be constructed as a specific-purpose computer such as an application-specific integrated circuit (ASIC), a microprocessor, a microcomputer, or other similar devices. A distinct computer/controller 1000 can be integrated into certain embodiments of the shared image device 101, the share mechanism 102, and/or the communication link 104, as described with respect to
In certain embodiments, the shared image device 101 including the computer/controller 1000 can be configured as a peripheral shared image device. Such peripheral shared image devices can be configured to include sufficient image storage in the memory 1004 to allow storage of the images for a session. Additionally, in certain embodiments the peripheral shared image device can transmit operational instructions (either computer based or manual) to instruct either a user at the capturing shared image device how to operate the capturing shared image device; or ultimately can automatically operate the capturing shared image device(s) according to the operating information or instructions. The operating information or instructions can include, but is not limited to, how many images to capture, where to capture (take a picture toward a specified direction), the subject of the desired image, zoom level, etc. In this manner, certain embodiments of peripheral shared image devices can effectively control the operation of an associated capturing shared image device by effective use of operating information.
Examples of Device Capacity
The different embodiments of the shared image devices 101, operating as described with respect to
This section includes a description of certain embodiments of indicators that allow the shared image device to operate within their memory capacity, battery capacity, or processor capacity. When the particular capacity for a particular shared image device is reached, a particular shared image device typically does not operate as intended or designed. Different embodiments of the device capacity include, but are not limited to, memory storage capacity, processor capacity, and/or battery life capacity. One example of a device capacity indicator is described in this disclosure relative to
In many embodiments, the users of each shared image device can be provided with the option of obtaining or retaining particular shared images obtained from a particular shared image device, associated with a particular user, or relating to a particular subject. In one embodiment, such filtering techniques can filter based upon the metadata that is associated with each shared image.
In certain embodiments, the shared image device 101 can include a record that indicates the shared image device that actually captured the shared images. The record can also include the identities of other shared image devices with which the user has agreed, by joining the sharing session, to be willing to share images. The user of the shared image device with such a record can select those other shared image devices with which they wish to access certain, or at least some of their, shared images for the particular sharing session. In one embodiment, this can be considered as a back-end synchronization to provide sharing of shared images, and the synchronized data can be returned to the capturing shared image device.
This can be because there is an association between the different shared image devices (e.g., a user's camera and the user's computer or printer). In one embodiment, there can be a sharing session identifier that is available to the members of the sharing session by which the shared images, portions thereof, associated information, metadata, etc. that in certain instances allows transferring the shared images through the network or the Internet.
The synchronization for a session of multiple shared image devices can allow a member shared image device that has left a session to return to the session. In addition, a member that has entered a session later than other members can receive the prior images relating to the session by synchronizing with other members of the session that have the prior shared images. In certain embodiments, it is envisioned that different members of the same session can have different sessions, so to provide a complete synchronization for a member joining (or rejoining) an existing session, the joining shared image device may obtain a number of images from multiple shared image device sources. In the master-satellite embodiments as described with respect to
Synchronization may be more complex in certain embodiments than certain shared image devices providing the images to other shared image devices. For example, certain shared image devices may have limited resources compared with other shared image devices due to different memory dimensions, different battery lives, different imaging resolutions, etc. As such, to transmit image data between different shared image devices, it may be important that the sending shared image device configure the image data in a format as desired by the receiving shared image device. For example, the shared images could be selected to be thumbnail images, full images, portion of images, metadata relating to images, etc.
In many embodiments of shared image devices, a mechanism can be provided such that a receiving shared image device that has obtained one version of a shared image can obtain another. For example, if a receiving shared image device that has already received a thumbnail shared image from a transmitting shared image device, and the receiving shared image device thereupon provides a request to obtain a full-resolution image version or a reduced-resolution image version of certain shared images, then the transmitting shared image device could provide such full-resolution images. In certain embodiments, such synchronization (to provide certain versions of many images, or alternate versions of certain images) could be allowed even after the session is complete such as by using such a transfer mechanism such as email, or even a reestablished communication link.
In certain embodiments, a memory capacity warning such as the status indicator 1504 exists on capturing shared image devices such as a camera or camcorder. This memory capacity warning can function in a similar manner to a battery indicator, to indicate an amount of time remaining considering past-flows for the particular sharing session. As such, if the past image storage has taken up a prescribed percentage of the memory storage, the indicator will indicate the number of images used compared to those remaining, the percentage of image storage space used, or the amount of time remaining. The users of the shared image devices can use such indicators based on past-flows to judiciously apply further image capturing, obtaining, retaining, or other activities.
Certain ones of the device capacities may be related. For example, one capturing shared image device may be configurable to be able to only store a certain number of shared full-sized images. The status monitor insert 1504 therefore may indicate the number of remaining full-sized images, reduced-resolution images, as well as the number of thumbnail images or metadata (as desired by the user of the shared image device, or as designed by the designer of the shared image device). To obtain or retain more full-sized images or even reduced-resolution images may require a considerable amount of battery life that represents another embodiment of device capacity. As such, a particular user considering obtaining or retaining more shared images may depend partially on the battery life state as well as the amount of energy necessary to obtain the current state of stored full-sized images, thumbnail images, or metadata.
In one embodiment, the data associated with the captured shared images can be initially stored in an image storage location within the shared image device. The percentage of data (or number of images) that is stored in the image storage location can be monitored, and when the percentage of data (or number of images) exceeds a predetermined amount, some data that is to be stored and/or data that has been stored can be obtained or retained to a remote storage location.
In one embodiment, the remote storage location can be remotely located from the device image storage location such that the image, or portions thereof, can be obtained or retained over a wireless communication link and/or other link such as over the Internet or another shared image network or network. In another embodiment, the remote storage location can include, for example, an image storage device that is operably coupled, such as by a short connection link, to the shared image device. The physical memory dimensions of the image storage location, and as well as the remote storage location, can be selected based on the volumes and type of images, portions of images, or other image information that is likely to be obtained with a particular shared image device for a particular sharing session. As such, this allows the sharing by shared image devices 101 to be accomplished in a substantially real-time basis.
A data storage capacity situation can occur when a user overuses the storage capability of the shared image device, such as by capturing too many images using a digital camera or camcorder. This may be connected to the shared-percentage concept described presenting, wherein if a certain percentage of the image capacity in a camera has been captured, either the images relating to that sharing session, or the images from a particular user, can be rejected (or selectively considered by using, e.g., a browsing mechanism).
Certain embodiments of the sharing mechanism can also operate as a subscription mechanism. For example, if a user of a shared image device captures an image, it may be sent to the other shared image devices that are participating in the sharing session. Such a subscription to a sharing session may be equated with subscribing with another service. Each subscribing shared image device may thereupon elect to join a particular session. In certain embodiments of a session, each user of a shared image device can select which images are to be obtained or retained, and can reject certain images. There are a variety of embodiments that can be provided between sessions and subscriptions thereto.
In certain embodiments, if a user of a shared image device agrees to publish a particular image for a number of other shared image devices including, in particular, a second shared image device, then the user at the second shared image device can, in certain embodiments but not others, agree to accept the pictures. It is also possible to envision relatively simple or complex cases relating to receiving and/or transmitting images, or portions thereof, pertaining to shared image devices within a particular sharing region. For example, shared image devices configurable as digital cameras can have the capability of browsing through their shared images. Such a browser could be applied to incoming subscribed-to images. Consider an instance that provides for “stop subscribing” to any particular user, from any particular sharing session, and/or the like. As such, the images can be either permanently blocked, temporarily blocked, allowed access to add further time, selectively cultured, or a wide variety of other permutations. At a live event, a user may for example be more concerned with capturing the images than managing them.
Examples of Regional Proximity Shared Image Device Concepts
A number of different embodiments of regional proximity shared image device concepts are described with respect to
In
In
Each high-level flowchart can also represent structural aspects of an apparatus or a system, such as can be performed by a general-purpose computer, a specific-purpose computer, hardware, software, firmware, or some electromechanical controlling of computing device performing those portions or process steps. Both apparatus, method, system, and other claim types as attached herein find support using the high-level flowcharts such as included in
One embodiment of a shared image network 100 that can be utilized to perform a variety of regional shared image device concepts is described with respect to
A high-level flowchart of one embodiment of the regional shared image device concept 600 is described with respect to
A high-level flowchart of another embodiment of the regional proximity shared image device concept 700 is described with respect to
A high-level flowchart of one embodiment of the regional proximity shared image device concept 800 is described with respect to
The embodiment of the shared image networks 100 of
A high-level flowchart of another embodiment of the regional proximity shared image device concept 1900 is described with respect to
A high-level flowchart of another embodiment of the regional proximity shared image device concept 2000 is described with respect to
In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, electro-mechanical system, and/or firmware configurable to effect the herein-referenced method aspects depending upon the design choices of the system designer.
Examples of Sharing Mechanisms
To provide improved consumer electronics, it may be desirable to provide a simplified sharing mechanism to accomplish the desired task for the shared image device 101. The image-based products produced by such large-scale electronics/computer manufacturers such as Hewlett-Packard, IBM, Xerox, Sony, and a variety of other companies (all registered trademarks of their respective companies) determine those consumer-electronic devices that could have sharing capacity. To appreciate the large variety of shared image devices 101 that could benefit from sharing capability and thereby become either a capturing or peripheral shared image device of, one can walk-through a large consumer-electronics store, or alternatively consider the variety of consumer device patents in the USPTO.
Certain shared image devices 101 might have a prescribed design behavior when associated with a group of shared image devices. Consider that each shared image device has a traditional function such as photography, printing, computing, etc. It is also possible that some shared image devices can perform a function that differs from their traditional function for a particular sharing session.
Theoretically, the share mechanism can be configurable to operate relatively simply to cause sharing between multiple shared image devices; similar to the ease that has become generally accepted by, e.g., depressing a shutter button that triggers a camera to capture an image. Additional complexity may be provided, as desired, in certain embodiments of shared mechanisms to provide additional functionality such as to select those shared image devices that may join a particular sharing session. One embodiment of such additional complexity to select member shared image devices may relate to establishing a “buddy list” between multiple shared image devices, as described later in this disclosure. Certain embodiments of shared image devices, but not others, are configured as a packaged item that allows sharing functionality to other shared image devices in the package. Such member selection may be afforded to peripheral shared image devices such as device printers, DVD burners, etc.
In certain embodiments, shared image devices select certain shared images that may have been captured by at least one other shared image device, and can obtain other versions of the selected shared images. In one embodiment, it may be desired to provide a near-real-time data-transfer between certain shared image devices 101 (but perhaps not others) that are participating in certain sharing sessions. In other embodiments, the rate of data transfer may not be critical based on the particular application, and the rate of data transfer can be reduced. The particular share mechanism should be adaptable to the uses, designs, operations, and other considerations of the shared image devices.
Examples of Shared Image Devices Having Password Regional Proximity
It has been described above how to integrate a number of shared image devices 101 into the shared image network 100 based upon the regional proximity of the shared image devices 101 and their respective shared regions 103 (either geographic or based on the communication link 104), and also based on the actuations of, and the operations of, the respective shared mechanisms. In the geographic regional proximity-based embodiments, the shared image devices can be located relatively closely to each other depending upon the particular technology utilized.
In other embodiments, shared image devices can be operably connected to each other (e.g., operably coupled) to allow authentication for operation such as by a password such as a spoken word or phrase, a captured picture, etc. Certain embodiments can use password-regional-proximity in combination with, or in addition to, geographic regional proximity. The different types of regional proximity are therefore not necessarily mutually exclusive. As such, an authorizing password, a pass image, or a variety of similar pass mechanisms can replace the herein-described regional proximity requirements.
This portion of the disclosure thereby describes how a number of shared image devices 101 can join the sharing session based on passwords or a similar mechanism, instead of based upon the physical regional proximity. Certain embodiments of the shared image network 100 can create group passwords to protect against use of shared image devices by non-participants. The shared image devices 101 within that particular sharing session can be configurable to respond or operate pursuant to the password, pass image, etc. using suitable image recognition, speech recognition, pattern recognition, or other recognition programs. Consider, for example, one of the participants at a birthday party or other event creates a temporary community password for the session group.
Participants can enter the appropriate password, and thereby actuate the shared image device 101 using the sharing mechanism. In one embodiment, only those shared image devices 101 with the correct password may be provided access to a community of shared images for that sharing session.
A variety of password mechanisms thereby can provide password functionality to shared image devices 101. Password mechanisms represent one relatively easy technique to provide password functionality. In one embodiment, the users of shared image devices 101 can follow instructions to type in a specific password, pass phrase, something the user says, something the user types, or some picture that can be possessed by the users in the sharing session (e.g., handed out at the door for a sharing event). Such password, etc. that passes the appropriate recognition program can thereupon be used for authentication, etc.
One embodiment of a recognizable password for a recognition program includes a photographic-password. For example, a user who wants to join a certain session can do so by submitting a captured image of an arm, a captured image of a thumb, a captured image of a shoe, a captured image of a prescribed number of fingers or some letter or number (or group thereof), or a captured image of some other physical characteristic whose shape or appearance would be recognizable using computer-based image recognition programs, etc. In another embodiment, at least some of the cameras are provided (e.g., by a leader of a session or a producer of a shared image device) with a similar appearing card or piece of paper having some shape or pattern printed on them that represents a picture that can thereupon act as a password.
In another embodiment, the printed pattern could even include, e.g., a page or portion of a newspaper, or magazine, or a portion thereof The pattern of text, or a photograph, or a physical shape can represent a pattern that is recognizable by a hardware, firmware, or software-based pattern recognition mechanism such as may be used in certain embodiments of shared image devices 101. In yet another embodiment, the pattern recognition software can even be applied to remote shared image devices, such that the members of the sharing session hold up some predetermined number of fingers (e.g., 5, 4, etc.), or a printed number, to join the sharing session. These examples of pattern recognition, speech recognition, etc. are illustrative in nature and not limiting in scope. In certain embodiments, the users of the shared image devices 101 can even be remotely located as in different cities or countries while allowing suitable operation of the shared image network 100.
The patterns discussed in this disclosure are recognizable by an optical, audio, or video pattern recognition system or device (such as a pattern or shape recognition program that runs on at least one general-purpose computer or at least one specialized-purpose or specific-purpose computer, or a networked combination thereof, as described herein). It is also to be understood that many shared image devices, such as digital cameras or camcorders, could include voice input that could thereupon be compared against a speech pattern, an audio pattern, and/or a password or pass-phrase pattern using vocal recognition patterns. As such, a vocal or audio pattern search of a particular individual using a vocal or audio recognition program, or using a particular spoken password, is within the intended scope of the present disclosure. Additionally, a spoken password can be compared to a voice recognition program for that password.
There are a wide variety of graphic, photographic, image-based, local, or audio type passwords, and/or pass-phrases that are within the intended scope of the present disclosure. As such, those described herein are not intended to be limiting in scope. The variety of recognition programs for speech, voice, image, audio, video, etc. provide an indication of the large variety of recognition programs that are within the intended scope of the applicable pattern recognition programs of the present disclosure. The general operation of recognition programs as run on captures and/or controllers are generally well known by those skilled in the art and will not be further detailed within this disclosure.
The sophistication, quality, expense, and functionality of shared image devices 101 included in different embodiments of the shared image network can therefore vary widely. In one embodiment, the satellite shared image devices 101b that are associated with the master shared image device 101a can be a relatively inexpensive device, such as cameras or camcorders that can each hold a prescribed amount of data at any given time. As such, the satellite shared image devices 101b can thereupon obtain or retain the data to the imaging computer-camera associated with that sharing session. In other embodiments, some of shared image devices 101 in the shared image network 100 can be relatively expensive and sophisticated, such that each shared image devices 101 can be configurable to perform a specific function and/or specific operability.
A certain master shared image device 101a can alternatively be configurable as a satellite shared image device 101b in a different sharing session or time. In one embodiment, the person giving the party, moderating an event, etc. can logically configure their digital image device to be the master. As such, certain digital image devices (e.g., digital cameras or camcorders) can be configurable as the master or satellite depending upon the particular sharing session, and who is establishing or running the sharing session.
If a particular shared image is deleted, the deletion of the shared image can propagate through other shared image devices and/or users in certain embodiments. Although in certain relatively simplified embodiments, the deletion will not propagate through to other shared image devices. It may, also be desirable to apply an undo function to certain embodiments of shared image devices to remove bad pictures (images) so that they may not be shared.
In the peer-configuration, it may be desired to provide some “remembering” function such that the shared image network 100 remembers the contents of those particular shared images that were not shared before shared image devices lost regional proximity. An option may be to allow those shared images to be shared between shared image devices.
Examples of Sharing Sessions
As described in this disclosure, it may be useful in certain embodiments (while not in other embodiments) to incorporate some type of a sharing session that extends for the duration of a session to associate, on a sharing basis, those member shared image devices to the sharing session. As such, the sharing session can be the duration over which certain embodiments of shared image devices 101 may share their shareable resources, such as still pictures or motion pictures.
There can be many embodiments of types of sharing sessions, as described within this disclosure. For example, in some sessions, the shared images that have been captured can be shared or copied between some of the other shared image devices 101. As such, if a number of shared image devices each captured an image (or portions thereof) for a particular sharing session, then some of the shared image devices can be expected to have a large number of shared images to capture, process, manage, consider, store, and/or view. In other embodiments of the sharing sessions, only a certain number of the images are shared or copied with certain shared image devices.
One embodiment of the sharing session may involve a group of users for a session (e.g., parents for a particular child's birthday party or sporting event), each of which have a shared image device that may be configurable (authenticated or authorized) to gain access to the shared images at that event. In one embodiment, certain shared image devices 101 could obtain or retain shared images (e.g., pictures) even after they had left, but before the event has ended. It is likely that the shared image network 100 would utilize one or more wireless links to provide the flexibility between the shared image devices such as is provided with certain local area networks. Alternatively, the images could be accessed later over e.g., wide area networks to obtain or retain large volumes of the data associated with a number of pictures.
For certain embodiments, it may be desired to allow a certain shared image device 101 to join a plurality of concurrent sharing sessions. A user would then be able to determine which one of multiple sharing sessions they wished to be a member. As such, such a shared image device 101 could obtain or retain information from at least certain other shared image devices from both/all of the concurrent sharing sessions. Access to the multiple sharing sessions can be covered by providing multiple passwords or pass-phrases that each relate to the different concurrent sharing sessions. In certain embodiments, it is therefore possible for certain shared image devices 101 to subscribe to multiple sharing sessions simultaneously. Logically, this sharing of one shared image device into multiple sharing sessions can be envisioned as, e.g., a Venn diagram in which each shape represents one of multiple potentially-overlapping concurrent sharing sessions. In these embodiments, the sharing sessions that each shared image relates to can be identified; or in certain embodiments, a particular shared image device pertains to both/all of the concurrent sharing sessions.
With many embodiments of sharing sessions that are established on peer-to-peer shared image networks similar to as described above with respect to
Replication of lost, or never obtained, data may be successfully performed in many peer-to-peer shared image networks as well as other networks. Such data replication represents an advantage of certain peer-to-peer shared image networks. This replication may not apply to sharing sessions that have already both started and ended, even for peer-to-peer shared image networks. As such, in many embodiments, users of shared image devices 101 that might have joined the sharing session after the sharing session has ended may not be able to obtain those shared images substantially directly (but perhaps can obtain the sharing session pictures from a friend or a family member). Certain embodiments of the shared image network 100 may include a concept of a synchronized master shared image device from which a latecomer can obtain the shared images.
Though dissimilarities exist between different types of sharing sessions between shared image devices 101, there can also be a great deal of commonality. For example, many embodiments of the sharing sessions can be identified by a unique session identifier. With certain embodiments of the sharing sessions, those who are attending should be able to access the shared images captured by some of the shared image devices 101 associated with that sharing session (while this may not be true in other embodiments of the sharing session). Many embodiments of sharing sessions rely on a broadcast by which images (or portions thereof or information relating thereto) are transmitted to other members of the session, in many instances without an addressing mechanism.
A user can get access to sharing sessions in certain embodiments after they have left that sharing session, such as a party. For example, the sharing session may be configurable such that the members can access images relating to any portion of the shared session following the shared session from one of the session members (perhaps after providing a suitable password to rejoin and/or access images from the session). In certain embodiments, such sharing session members may be able to access the shared images after they leave the sharing session using a different mechanism, such as the Internet or another embodiment of network (e.g., or other shared image network). The particular configuration of the shared image network largely determines how current members, as well as past members, of the sharing session may access shared images from the shared image network.
Consider that for certain embodiments, when a user actuates a sharing mechanism 102 to join a particular sharing session, that they establish a sharing session identity (ID). For certain embodiments of shared image devices 101, they should be able to use the sharing session ID to later retrieve pictures even after they have left the event. For example, the password can be used as a host-name or sharing session ID for the event. Sharing session names can also default to easily remembered things such as date, name of the sharing session, etc. Shared image devices can be associated with one or more from a set of shared default keywords such as “party”, “anniversary”, “Christmas”, “sports event”, “business meeting”, etc. For a number of embodiments, the information associated with each particular sharing session should be retrievable later from a central computer, a server, etc.
For a particular sharing session member who shows up late to the sharing session or meeting, it may be important that different session attendees have the capability of “pulling in” new members, and providing them the shared images going back to the beginning of the sharing session. For example, assume that there are four currently-joined shared image devices 101 in a session, and a new shared image device is being joined using the shared image device to establish a new grouping of five shared image devices. Such joining techniques may, for example, rely on point-to-point communication, master-satellite communication, client-server communication, or other shared communication techniques. In one embodiment, for example, the user of the shared image device 101 actuates the sharing mechanism that publishes the shared images to allow the joining shared image device to become part of the sharing session, and thereby gain access to the images already taken by other session devices. A number of different sharing session configurations for the sharing mechanisms can thereby be provided depending on the application or as a design choice. One embodiment involves a first person actuating the sharing mechanism 102, at which point other shared image devices within range may be able to access those. This embodiment could be considered as simply opening up some of the session information contained in one shared image device 101 to other shared image devices.
Another embodiment can be considered as a “published with synchronized timestamp”, such that each user actuates the sharing mechanism at the same time to get synchronized, and therefore is able to somewhat control the dispersal of the shared images. Another embodiment can be referred to as a “shared plus password.”
Examples of Ancillary Aspects for Sharing Mechanisms
Certain shared image device 101 concepts can also be applicable to business meetings, telephone calls, etc. As such, some participants in a meeting can copy, share, and/or distribute all, or selected shared images, or shared camcorder output, etc. relating to the meeting, event, etc. This even applies to those members who arrived late.
Some embodiments of the sharing mechanism can also include a stop-publishing aspect of the sharing mechanism. In certain session embodiments, a stop-sharing mechanism or temporary halt publishing mechanism performs an inverse operation to the sharing mechanism as described herein. Suppose, for example, that a user in a shared image device 101 wishes to capture at least one private picture, and thereby temporarily disconnects from the shared image network to keep from sharing that image from the other members of the sharing session.
This can be the same or a different feature as a temporary-private mechanism such as a mute-image device. In this manner, a person in the party can temporarily disconnect their device from the shared image network 100 and/or certain shared images or portions thereof for a portion of the sharing session.
In one embodiment, a unique time-stamp can be provided to synchronize at least some of the digital devices in the sharing session, and the time can be measured with respect to the beginning of the sharing session. Each shared image device such as a digital camera or camcorder can thereupon utilize a universal sharing time. In one embodiment, at least some of the clocks for the different shared image devices 101 slave to a time corresponding to one of the devices for that sharing session. In another embodiment, at least certain shared image devices 101 slave to a sharing session time for that session. The selected sharing session time can rely on a distinct time-keeping mechanism.
In another embodiment, a “buddy list” can be integrated into a number of shared image devices that form a subset from within a larger group of shared image devices (e.g., the smaller group is identified to share or copy their shared images using the buddy list). Those shared image devices may elect to share or copy their images with other shared image devices sharing the same buddy list, but not share their “buddy-list” images with the group of shared image devices at large.
In one practical example, assume that one user of the shared image device 101 goes to a sports event with a group of friends. When that user actuates the sharing mechanism using their buddy list, the shared image device synchronizes with other shared image devices on that buddy list, but not necessarily with the shared image devices at large. In one embodiment, the “buddy-list” group can be associated with a prescribed password, for example. There can be a variety of such embodiments of shared image devices that range from relatively simple to more complex. The use of the buddy list to actuate the share mechanism in certain embodiments of shared image devices can utilize certain passwords, such that those shared image devices that produce the passwords can join the buddy-list session.
A number of rules can be applied to the shared image devices that pertain to general concepts of time, space, and/or locations for capturing the shared images. Such aspects as buddy lists, the numbers of pictures that can be shared, stop-halt, temporary-halt, percentage of storage that can be shared, and the types of pictures that can be shared (e.g., private or public shared images) are exemplary aspects with respect to shared image devices.
Additionally, in one embodiment, photographers could prioritize their shared images. For example, certain shared images can vary in quality based on, e.g., content, interest, or quality of the shared image in a manner that can be either objectively or subjectively rated, or other such factors. Other users may select a shared image device to access only those shared images that are above a certain quality level (e.g. good, excellent, fair, etc.). Filtering of the lower quality images, measured by some objective and/or subjective standard, provides a technique to reduce the amount of data that has to be obtained or retained for each sharing session.
Certain embodiments of shared image devices can be configurable to handle multiple sharing sessions. For example, suppose a user has a printer that can handle both a first sharing session and a second sharing session for a particular digital camera or camcorder. Different applications for the shared image devices could thereupon be useful in business, educational, sporting, governmental, police, or applications in which an individual obtains shared images for several concurrent events (or only one event that an individual is not attending). It might be desirable to allow a user to subscribe to the multiple sharing sessions substantially simultaneously. The personal computer (PC) can be configurable as a peer (of a peer-to-peer shared image network configuration) that monitors the shared images that are being captured as to select a variety of shared images from multiple shared image devices.
In certain embodiments, a status indicator can be provided, either on the shared image device or separately, and which indicates to others that a particular shared image device is in its share mode. One example of a status indicator may be an indicator light, or an “active” indicator on the display of the shared image device. Other status indicators may display some information pertaining to the particular sharing session.
Examples of Viewfinders for Shared Image Devices
In certain embodiments, but not others, a sharing mechanism might be considered to function as a virtual picture frame or viewfinder that allows remotely-located shared image devices such as digital cameras or camcorders to capture shared images. Viewfinders therefore provide a mechanism for one shared image device (which may be configurable as either a peripheral shared image device, a capturing shared image device, and/or another shared image device) to observe an image that has been, or is being, captured by another shared image device (which may be configurable as either a peripheral shared image device, a capturing shared image device, and/or another shared image device). As such, certain embodiments of viewfinders may be considered as operating to “share another shared image device's viewfinder”. In one embodiment, a viewfinder at a shared image device can display at least one image, or a portion thereof, that is being imaged at a second shared image device. The second shared image device acts by displaying at least a portion of the at least one image that is displayed by the shared image device as it could appear at the shared image device. Those embodiments of shared image devices 101 that are provided with viewfinders can be used by users to perform a variety of processing related to the shared images including, but not limited to, viewing the shared images, selecting those shared images to keep and those to discard, determine those shared images that will undergo further processing, and determine those shared images to select an increased resolution version of (e.g., when provided with thumbnails, image information or portions thereof, or metadata describing the image). For example, certain embodiments of viewfinders may display thumbnails of shared images. From the thumbnails, the user determines those shared images that are to be accessed in more detail (e.g., having a greater resolution).
Certain embodiments of a sharing menu (not shown) that is integrated within a shared image device 101. The sharing menu can be integrated as a portion of the viewfinder of certain embodiments of the shared image device 101 (e.g., such as being located on the display of the shared image device). The shared image device can allow a user to join a particular session, for which they are proximately located using one of the above-described mechanisms such as geographic regional proximity, regional proximity by communications link, and/or regional proximity by password. Certain components of a sharing menu may be selected using, for example, touch from a finger or stylus, clicking using inputs from a mouse, keyboard, trackball, or other device, etc.
The sharing menu can include a variety of questions, such as including input for the name and/or identity of the user, the user password, indicating whether this shared image device is the master device for a particular session, and indicating whether the particular session has a prescribed duration, and if so, when is the timeout. The embodiment of the sharing menu as described is illustrative in nature, and not limiting in scope. In actuality, the sharing menu can have a variety of appearances, shapes, and/or questions.
As described with respect to
The selection of a relative display of the remote capturing portion 910 relative to the local capturing portion 908 over the viewfinder 900 is a design choice, and the present description is not intended to be limiting in scope. For example, the remote capturing portion 910 of the viewfinder 900 can be provided relative to the local capturing portion 908 as an overlying window, an underlying window, a top or bottom window, an additional box, overlying text that is physically typed above the local capturing portion 908, or a variety of other configurations that are known to those skilled in graphical user interfaces (GUIs) such as Windows (as designed and made commercially available by Microsoft) and Mac (as designed and made commercially available by Apple Computer).
Also described with respect to
In one embodiment, the feedback line 906 includes an audio transmission line, by which one user can indicate to another user at the capturing shared image device 101c to, perhaps, move the particular remote capturing shared image device 101 to another location, detect a different field of view, zoomed in or out, otherwise adjust the settings of the capturing shared image device, provide a shared image, do not provide a shared image, capture another shared image, to not capture another shared image, or perform a variety of other task(s) with the remote capturing shared image device 101c.
Non-verbal instructions, similar in nature to those described as being transmitted over the audio version of the feedback line 906, can also be transmitted over a text-based or other graphical version of the feedback line. For example, a user in one shared image device can indicate to a user and another shared image device to scan in another direction by using a series of the arrows or other recognizable indicators that are transmitted utilizing GUI nomenclature via the feedback line 906. One user can also type to a remote user to zoom in or out.
The different embodiments of the feedback line 906 can be added, in addition to those feedback lines that are integral with each communication link 104, as described in this disclosure. Increasing the types and amount of communications that can be transmitted utilizing the feedback line 906 can thereby provide more interaction between the users and remotely-located shared image devices, thereby potentially improving an overall image sharing experience.
As described in this disclosure, certain embodiments of the viewfinder 900 thereby can be configurable in a variety of configurations to display the images in a variety of formats depending upon the type of the shared image device, the volume of data that is available to store therein, the amount of shared images that actually are stored therein, and the user input.
The viewfinder 900 may be utilized in a variety of shared image devices 101 to display certain shared images. As such, a shared image device can capture or copy a shared image, or a portion thereof, from a second shared image device at a remote location from the shared image device. Under these circumstances, the shared image device can actually utilize the imaging aspects or equipment of the second shared image device. Instead of photographing a vision or scene with multiple shared image devices, the scene can be photographed by only one device, and the distributed images can be combined to be copied or shared with other shared image devices.
It is thereby possible in certain embodiments to utilize another shared image devices' viewfinder 900 including the local capturing portion 908 and the remote capturing portion 910; such that one user can see what's on somebody else's shared image device. Suppose, for example, one shared image device that is at a child's birthday party is positioned at a swing while a second is at a swimming pool. It may be desirable to switch between the images that appear in the viewfinder 900 of the multiple shared image devices. Such viewfinders can exist in many embodiments of the at least one other shared image device 101d that is providing some operation information over the communication link 104b to the shared image device 101e (see e.g.
This use of switching viewfinders 900 for the shared image devices can also be applied to business, educational, personal, or other applications. For example, there might be multiple blackboards or whiteboards in a classroom that can be captured by multiple shared image devices. Alternatively, a user may wish to view what is going on in one class while attending another. Certain embodiments of the shared image device as described in this disclosure can thereby, essentially, bookmark activities at another shared image device.
In certain applications, it may therefore be worthwhile to view somebody else's viewfinder 900 as opposed to just obtaining or retaining shared images that might have been captured. This also provides a technique to view the viewfinder 900 of another shared image device. For example, one shared image device can be used to indicate to a second shared image device that the subject of the shared image device; as such, please capture an image at the second shared image device for the shared image device.
Sharing or copying images between multiple shared image devices can thereby be considered as copying a captured image from the capturing shared image device to the other shared image devices (such other shared image devices can be configurable either as a capturing and/or peripheral shared image device). The quality, resolution, and other characteristics of each shared image are initially determined by the image in properties of the capturing shared image device that captured that shared image.
Consider that, in one embodiment, a shared image device has a higher resolution compared to other shared image device(s), such that relatively high quality shared images can be copied and distributed with other shared image devices (that are only capable of capturing lower resolution shared images). In certain sharing sessions, the best, or highest resolution, shared image device, or those used by the best photographer, can be used to capture shared images or portions thereof for other sharing devices in the sharing session. Each image or photograph can be captured by the particular desired capturing shared image device (highest resolution, least memory used, flash capability, demonstrated ability to take good shared images, etc.). The shared images captured by multiple shared image devices can then be copied or shared into each desired shared image device.
As such, a particular user may have a number of capturing shared image devices, each shared image device is considered optimal to capture a particular type of image. The sharing mechanism as described in this disclosure thereby allows the shared image that is being captured by each of these capturing shared image devices to be transferred between these multiple shared image devices to one or more selected shared image devices. Those images received by the selected shared image device from each of these “optimized” shared image devices are thereby identical to those images captured by the capturing shared image device.
Certain embodiments of the viewfinder 900 provide a mechanism by which the shared image device displays those images which, in time, can be copied to at least one other shared image device.
In one embodiment, the viewfinder 900 is used to subscribe to data from other shared image devices. New functionality might be provided to one shared image device based on the images, data, and/or information being shared or copied from other shared image devices. For example, the viewfinder 900 might annotate its display to show which geographic areas have been sufficiently captured or covered by previous shared images. In the case where the shared image device 101 is a digital camera or camcorder, that new functionality may include an enhanced resolution, an occlusion removal, etc.
The viewfinder 900 can be utilized to publish the presence of its information to users. For example, the viewfinder might annotate its display to show those areas of a shared image that are most desired by other users. The user looking through the viewfinder 900 might alter the subject of the current shared image (such as by changing direction or zooming) based on what it detects as the most valuable people, places, or other subjects to photograph. Within this disclosure, the term “valuable” is highly subjective, and can refer to, e.g., an area that has not already been captured by other cameras (for example a particular child at a birthday party who has not been frequently imaged, a remote corner of a park at a particular time of day, a publicly-known individual, a group of individuals, or a person involved in an activity specifically requested by someone). Such determination of a particularly valuable individual or image can be input manually, or somewhat automatically using a recognition program or positioning program.
In certain embodiments, the viewfinder 900 can also indicate what has already been shared. Using image processing techniques, prior shared images can be considered. For example, children at a birthday party whose images have been captured (photographed) frequently might, in certain embodiments, appear differently within the viewfinder 900 compared to those having few captured images. In one embodiment, a user of a shared image device such as a digital camera or camcorder visually scans around a room during a sharing session such as a birthday party, and those kids who have been photographed often might get some indication on the viewfinder 900. As an example, less captured subjects may “sparkle” compared with more captured subjects. In one embodiment, such functionality can be provided depending largely on the real-time recognizers that can analyze or store the identity of particular individuals. Areas in the viewfinder 900 that are more valuable to photograph might sparkle or display an outline or be color-coded in certain embodiments of the viewfinders for the shared image devices. An explicit monetary value indicator might also be associated with these valuable areas.
In certain embodiments, positional information such as those from global positioning system (GPS), metadata, or those including reference to some geographic location, particular individual, or setting can be used to indicate where certain pictures have been captured. For example, if outdoors, then GPS derived positional information can be used to indicate the physical location, and therefore information about the subject, of a particular photograph.
Consider that the viewfinder 900 display indicates that a large number of pictures have been captured of the same birthday cake, etc. In certain embodiments, this similar-composition shared image can be applied to devices lacking a sharing mechanism, as well as a shared image device 101. For example, if a particular user has captured a large number of images of one particular object, they would likely want to have an indication of it so that they can change the subject of further images. In another embodiment, perhaps a birds-eye view can be provided on at least some of the shared image devices to indicate where prior shared images in the sharing session have been captured. The recognition algorithm can vary widely in scope. For example, in one embodiment, positional information relating to where shared images have been captured could be indicated and searched, based on derived GPS coordinates and/or other positional information. In one embodiment, those shared images that the current shared image device (or any particular shared image device) has captured can be highlighted in some manner along the bottom, side, top, etc. of the viewfinder 900.
In certain embodiments, pictures can be sorted based on color schemes, or color map queries. An example might be considering N shared images that appear most similar to M shared images (where M and N identify particular shared images) from a computational perspective. In those instances, images that have been stored in memory can be quickly accessed and returned to one or more of shared image devices. This type of task can be configured to, for example, view images chronologically, based on their subject, based on their location, or based on their value, etc. can be achieved using commercially available pattern recognition programs that are configured to recognize such patterns. Instead of viewing the shared images based on their time sequences, the images are sorted based at least partially on composition in certain embodiments of shared image devices. Image processing or signal processing techniques can be applied to the shared image devices to determine certain characteristics of the shared images.
As technology improves, more memory storing-capabilities will likely be provided to many individual shared image devices such as digital cameras, camcorders, printers, and other such capturing and peripheral devices. The cost of individual digital shared images will likely continue to decrease as the associated technology improves. The sharing or copying of a considerable number of shared images from one capturing shared image device to another will become more affordable, especially as memory storage cost drops.
Other types of shared image sorting, shared image querying, or shared image storing techniques may be provided by a computer after the shared images could have been obtained or retained from a digital camera, camcorder, or web site. However, this feature will also likely be useful for the sharing mechanism between multiple shared image devices.
In one embodiment, the most recently input information (e.g., one or few shared images) of the sessions shared image devices 101, such as digital cameras, can also be shown on the viewfinder 900 such as shown with respect to
In certain above-described embodiments of the viewfinders 900 as described for example with respect to
A variety of viewfinder displays can be provided, such as illustrated in
The user of each shared image device might thereupon be prompted as to the specific room, region, or other locational area in which a particular shared image can be captured. Alternately, additional positioning equipment such as a GPS unit can be installed in each shared image device, and the locations of the photographs and thereupon be applied to the particular rooms depending upon the derived GPS positions (e.g., as described by metadata).
Another embodiment of the viewfinder 900 is described with respect to the inset 1502 of
Certain embodiments of a status insert 1504, as included in the viewfinder 900 as described with respect to
As such, metadata can be associated with a particular shared image. For example, metadata can indicate a camera in a sharing session that took the shared image, the owner of the camera that took the shared image, the geographic location that the shared image was captured, the identity of an individual being imaged, subject of the shared image, the identity of the particular sharing session, etc.
Another embodiment of the viewfinder 900 displays the local capturing portion 908 within the remote capturing portion 910 as described with respect to
In one embodiment, the local shared image device can be provided with a panoramic vision. The panoramic view formed partially by including other shared images can be configured to appear in the viewfinder 900 as a ghosted feature as displayed in
A variety of graphical user interface (GUI) techniques can be applied where the local capturing portion 908 is integrated within the remote capturing portion 910, as described with respect to
It might be desirable in certain applications, for example, to combine multiple ones of these shared images using a similar ghosted feature to provide a single shared image. Similarly, embodiment involves providing a three-dimensional shared image using multiple photographs (e.g., two, three, or more) of the same shared object from different angles. A variety of imaging applications, such as providing a driving or aircraft simulator, may be accomplished in which a variety of shared images are overlaying other shared images, at which certain of the overlaying shared images can include motion images to our present, for example, motion of instruments associated with such simulators. Such interlaying of images may provide a particularly realistic image.
From another aspect, such overlaying of static and/or motion images as associated with many embodiments of a share mechanism described within this disclosure relative to some description of where to place a particular shared room image device to achieve some multi-image effect with other shared image devices utilizing windowing or similar GUI techniques. Some software can be utilized to achieve the panoramic/3-dimensional/or other effects as desired. Certain embodiments of viewfinders for shared image devices involves using other people's shared image devices such as cameras, to insert old bookmarks at locations in where their cameras could have been located.
One viewfinder 900 embodiment involves using other people's shared image devices such as cameras, and put old bookmarks at locations in where their cameras could have been located.
In yet another embodiment, the viewfinder 900 of the shared image device can be provided with an indicator that provides positional information as to where the images have been taken. Such positional information can range from, but not be limited to, metadata that contains the latitude/longitude, GPS waypoint, within a known commercial location (e.g., at Sears®), at some residential location (within the living room at the Jones'), etc.
Examples of Variable Resolution
Different embodiments of the shared image devices can provide images with different resolutions. In fact, certain shared image devices can alter the resolution of their images. Certain embodiments of shared image devices can increase the number of images that can be shared or imaged by adjusting the resolution of one or more of the images. In certain embodiments of shared image devices, the entirety of, portions of, or information relating to, the images captured during a sharing session can be viewed on the viewfinder of the shared image device. Conceivably, the ones that a user has captured, or that satisfy some other criteria, will be accepted at the highest resolution. Varying the image resolution therefore partially pertains to the capacity of the shared image device, as described above. Other images will be accepted at low resolutions. In certain embodiments, the lower resolution images can be kept, rejected, or selected having a corresponding higher resolution image obtained or retained in the future.
Commercially available technology can provide always-on video, for certain embodiments of shared image devices. Such always-on technology can likely be applied to shared image devices. As such, actuating the sharing mechanism may be one technique for determining interest of a particular shared image, wherein another user of a shared image device can provide feedback via audio as to how a shared image can be altered (e.g., modify the subject, vary the resolution or zoom of the image, etc.). If the current image appears interesting, one user of a shared image device can turn on an audio microphone to communicate with another shared image device, and either capture a current image and/or a current sound. Additionally, if there is one image of particular interest, it may be desirable to obtain or retain five images chronologically on either side of that image that had been taken by that particular shared image device.
Consider a shared image device application such as a friend providing live pictures of a ski resort, a beach area, and/or a snowy pass that have been captured using a share mechanism, wherein the current weather conditions make a difference. The sharing mechanism 102 can be used to access such information on a near-real-time basis. The images that can be accessed on a near-real-time basis may have reduced highest resolution. As such, it may be desirable to reduce the resolution for certain imaging applications.
The variable resolution control represents another embodiment of a capacity-control device. Consider that lower-resolution images (e.g., thumbnails and/or metadata) generally require less memory storage than higher-resolution images. As such, for a given memory, a larger number of lower-resolution images can be stored than higher-resolution images. In addition, capturing higher-resolution images often utilizes more battery life than with lower-resolution images. All of these factor into the type of image that is to be stored.
In many embodiments of shared image devices, converting the resolution of images may utilize considerable device energy, such as battery life. As such, to reduce the drain on the energy expended by certain battery-powered devices during resolution conversion processes; it may be desired to transfer images to another shared image device(s) so that the other shared image device (that presumably has greater energy, such as a printer or computer that may be plugged in) can vary the resolution of the images.
Further consider those instances where a user of a shared image device has filled their device with high-resolution images. This user will be able to utilize capacity control by storing further images as thumbnails and/or metadata that in certain embodiments can be accessed later when the user obtains or retains their current image, or otherwise obtains more memory. In certain embodiments, the user will be able to access the high-resolution versions of all of the desired images from home, or some other location, via a network.
Naming Aspects
Other embodiments of shared image devices 101 involve “naming”. A unique name for a particular session can be associated with each of the shared image devices that captured at least one shared image such as a digital camera or camcorder. Another simpler sharing embodiment involves shared image devices 101 that can be pre-configurable when being built or distributed. For example, multiple cameras can be associated with each other such that at least some of those cameras will be able to share and/or copy images. For example, the metadata contained in the embodiment of the local capturing portion 908, as described with respect to
In one embodiment, the shared image device 101 identifies where a particular shared image was captured or imaged, the subject of the particular shared image, and/or when the shared image was captured. In one embodiment, these types of shared image information can be contained as metadata relative to the shared image device 101. As such, the metadata can be used to answer queries that may be applied to the shared images in the sharing session.
Naming allows a shared image device 101 to be identified to its owner, or with its user. In one embodiment, a name stored as metadata or other information can include a filename and a timestamp, and an identification of the individual shared image device (e.g., the identity name can be added as the filename). The metadata can therefore be provided within the desired format on the shared images.
Certain new embodiments involve providing multiple shared image devices 101 at a given session being provided with a synchronized timestamp. As such, the shared images that pertain to a particular event such as a wedding can be sorted depending upon the chronology of when they occurred. For example, shared images that are associated with a wedding can be chronologically categorized and separated as shared images that occurred prior to the wedding, during the wedding, after the wedding, during the reception, or at the bar afterwards, etc. This therefore can allow the sharing mechanism to provide an offset time, for the distinct shared image devices 101. This can act similarly to synchronizing watches between multiple photographers, and indicating the time of each photograph that can be sequentially arranged.
Conclusion
This disclosure provides a number of embodiments of the sharing mechanisms that can allow images that are located on one device to be transferred to another shared image device relying at least partially on the regional proximity between the shared image devices and the sharing region. Different configurations of peripheral shared image devices and/or capturing shared image devices may be combined using networking techniques. Different embodiments of the sharing mechanisms can be included in such embodiments of the shared image network 100 as telecommunication systems, computer systems, audio systems, video systems, teleconferencing systems, and/or hybrid combinations of certain ones of these systems. The embodiments of the shared image devices as described with respect to this disclosure are intended to be illustrative in nature, and are not limiting its scope.
Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems and/or other technologies described herein can be effected (e.g., hardware, software, and/or firmware), and that the preferred vehicle will vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for mainly a hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for mainly a software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. Hence, there are several possible vehicles by which the processes and/or devices and/or other technologies described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary.
The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of a signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory; and transmission type media such as digital and analog communication links using TDM or IP based communication links (e.g., packet links).
All of the above U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in any Application Data Sheet, are incorporated herein by reference, in their entireties.
The herein described aspects depict different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, “operably linked”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
It is to be understood by those skilled in the art that, in general, that the terms used in the disclosure, including the drawings and the appended claims (and especially as used in the bodies of the appended claims), are generally intended as “open” terms. For example, the term “including” should be interpreted as “including but not limited to”; the term “having” should be interpreted as “having at least”; and the term “includes” should be interpreted as “includes, but is not limited to”; etc. In this disclosure and the appended claims, the terms “a”, “the”, and “at least one” located prior to one or more items are intended to apply inclusively to either one or a plurality of those items.
Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “ a system having at least one of A, B, and C” would include but not be limited to systems that could have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “ a system having at least one of A, B, or C” would include but not be limited to systems that could have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).
Those skilled in the art will appreciate that the herein-described specific exemplary processes and/or devices and/or technologies are representative of more general processes and/or devices and/or technologies taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.
Within this disclosure, elements that perform similar functions in a similar way in different embodiments may be provided with the same or similar numerical reference characters in the figures.
For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation of U.S. patent application Ser. No. 11/122,274, entitled REGIONAL PROXIMITY FOR SHARED IMAGE DEVICE(S), naming EDWARD K. Y. JUNG, ROYCE A. LEVIEN, ROBERT W. LORD, MARK A. MALAMUD, JOHN D. RINALDO, JR. as inventors, filed 4 May 2005, now abandoned, or is an application of which a currently co-pending application is entitled to the benefit of the filing date.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4124871 | Morrin, II | Nov 1978 | A |
| 4249218 | Davis et al. | Feb 1981 | A |
| RE32662 | Pennington | May 1988 | E |
| 4747143 | Kroeger et al. | May 1988 | A |
| 5164831 | Kuchta et al. | Nov 1992 | A |
| 5341192 | Wally, Jr. et al. | Aug 1994 | A |
| 5388197 | Rayner | Feb 1995 | A |
| 5410343 | Coddington et al. | Apr 1995 | A |
| 5418565 | Smith | May 1995 | A |
| 5444476 | Conway | Aug 1995 | A |
| 5467288 | Fasciano et al. | Nov 1995 | A |
| 5477546 | Shibata et al. | Dec 1995 | A |
| 5546145 | Bernardi et al. | Aug 1996 | A |
| 5561883 | Landry et al. | Oct 1996 | A |
| 5588029 | Maturi et al. | Dec 1996 | A |
| 5612715 | Karaki et al. | Mar 1997 | A |
| 5629778 | Reuman | May 1997 | A |
| 5633678 | Parulski et al. | May 1997 | A |
| 5655144 | Milne et al. | Aug 1997 | A |
| 5659662 | Wilcox et al. | Aug 1997 | A |
| 5675789 | Ishii et al. | Oct 1997 | A |
| 5689343 | Loce et al. | Nov 1997 | A |
| 5689442 | Swanson et al. | Nov 1997 | A |
| 5701163 | Richards et al. | Dec 1997 | A |
| 5715487 | McIntyre et al. | Feb 1998 | A |
| 5751338 | Ludwig, Jr. | May 1998 | A |
| 5764800 | Yamagata | Jun 1998 | A |
| 5793630 | Theimer et al. | Aug 1998 | A |
| 5796879 | Wong et al. | Aug 1998 | A |
| 5806005 | Hull et al. | Sep 1998 | A |
| 5809161 | Auty et al. | Sep 1998 | A |
| 5822440 | Oltman et al. | Oct 1998 | A |
| 5825506 | Bednar et al. | Oct 1998 | A |
| 5828793 | Mann | Oct 1998 | A |
| 5845166 | Fellegara et al. | Dec 1998 | A |
| 5867614 | Ito | Feb 1999 | A |
| 5884039 | Ludwig et al. | Mar 1999 | A |
| 5889895 | Wong et al. | Mar 1999 | A |
| 5892509 | Jakobs et al. | Apr 1999 | A |
| 5917958 | Nunally et al. | Jun 1999 | A |
| 5917962 | Chen et al. | Jun 1999 | A |
| 5926605 | Ichimura | Jul 1999 | A |
| 5949484 | Nakaya et al. | Sep 1999 | A |
| 5956081 | Katz et al. | Sep 1999 | A |
| 5959622 | Greer et al. | Sep 1999 | A |
| 5977867 | Blouin | Nov 1999 | A |
| 5991799 | Yen et al. | Nov 1999 | A |
| 5995095 | Ratakonda | Nov 1999 | A |
| 5999214 | Inagaki | Dec 1999 | A |
| 6021403 | Horvitz et al. | Feb 2000 | A |
| 6028585 | Ishii et al. | Feb 2000 | A |
| 6034786 | Kwon | Mar 2000 | A |
| 6035323 | Narayen et al. | Mar 2000 | A |
| 6046762 | Sonesh et al. | Apr 2000 | A |
| 6052125 | Gardiner et al. | Apr 2000 | A |
| 6092670 | Marriott | Jul 2000 | A |
| 6115341 | Hirai | Sep 2000 | A |
| 6122003 | Anderson | Sep 2000 | A |
| 6128446 | Schrock et al. | Oct 2000 | A |
| 6134345 | Berman et al. | Oct 2000 | A |
| 6154771 | Rangan et al. | Nov 2000 | A |
| 6157406 | Iura et al. | Dec 2000 | A |
| 6157935 | Tran et al. | Dec 2000 | A |
| 6167350 | Hiramatsu et al. | Dec 2000 | A |
| 6167469 | Safai et al. | Dec 2000 | A |
| 6188383 | Tamura | Feb 2001 | B1 |
| 6188431 | Oie | Feb 2001 | B1 |
| 6198526 | Ohtsuka | Mar 2001 | B1 |
| 6204877 | Kiyokawa | Mar 2001 | B1 |
| 6222465 | Kumar et al. | Apr 2001 | B1 |
| 6226672 | DeMartin et al. | May 2001 | B1 |
| 6229565 | Bobry | May 2001 | B1 |
| 6285794 | Georgiev et al. | Sep 2001 | B1 |
| 6332139 | Kaneko et al. | Dec 2001 | B1 |
| 6332666 | Ikeda | Dec 2001 | B1 |
| 6333792 | Kimura | Dec 2001 | B1 |
| 6342887 | Munroe | Jan 2002 | B1 |
| 6351762 | Ludwig et al. | Feb 2002 | B1 |
| 6356868 | Yuschik et al. | Mar 2002 | B1 |
| 6359649 | Suzuki | Mar 2002 | B1 |
| 6366577 | Donovan | Apr 2002 | B1 |
| 6380972 | Suga et al. | Apr 2002 | B1 |
| 6384862 | Brusewitz et al. | May 2002 | B1 |
| 6400848 | Gallagher | Jun 2002 | B1 |
| 6433818 | Steinberg et al. | Aug 2002 | B1 |
| 6434398 | Inselberg | Aug 2002 | B1 |
| 6437797 | Ota | Aug 2002 | B1 |
| 6446095 | Mukai | Sep 2002 | B1 |
| 6452974 | Menon et al. | Sep 2002 | B1 |
| 6453336 | Beyda et al. | Sep 2002 | B1 |
| 6456339 | Surati et al. | Sep 2002 | B1 |
| 6459823 | Altunbasak et al. | Oct 2002 | B2 |
| 6466253 | Honjoh | Oct 2002 | B1 |
| 6466264 | Shioji | Oct 2002 | B1 |
| 6493028 | Anderson et al. | Dec 2002 | B1 |
| 6509931 | Mizosoe et al. | Jan 2003 | B1 |
| 6512541 | Dunton et al. | Jan 2003 | B2 |
| 6515704 | Sato | Feb 2003 | B1 |
| 6516154 | Parulski et al. | Feb 2003 | B1 |
| 6519612 | Howard et al. | Feb 2003 | B1 |
| 6522418 | Yokomizo et al. | Feb 2003 | B2 |
| 6535228 | Bandaru et al. | Mar 2003 | B1 |
| 6538692 | Niwa | Mar 2003 | B2 |
| 6539169 | Tsubaki et al. | Mar 2003 | B1 |
| 6542183 | DeAngelis et al. | Apr 2003 | B1 |
| 6546189 | Koda | Apr 2003 | B1 |
| 6549307 | Makishima et al. | Apr 2003 | B1 |
| 6564380 | Murphy | May 2003 | B1 |
| 6567122 | Anderson et al. | May 2003 | B1 |
| 6573927 | Parulski et al. | Jun 2003 | B2 |
| 6577311 | Crosby et al. | Jun 2003 | B1 |
| 6577336 | Safai | Jun 2003 | B2 |
| 6583813 | Enright et al. | Jun 2003 | B1 |
| 6587602 | Wakisawa et al. | Jul 2003 | B2 |
| 6611293 | Tarnoff et al. | Aug 2003 | B2 |
| 6628899 | Kito | Sep 2003 | B1 |
| 6629104 | Parulski et al. | Sep 2003 | B1 |
| 6650366 | Parulski et al. | Nov 2003 | B2 |
| 6650704 | Carlson et al. | Nov 2003 | B1 |
| 6654543 | Ando et al. | Nov 2003 | B2 |
| 6657667 | Anderson | Dec 2003 | B1 |
| 6678413 | Liang et al. | Jan 2004 | B1 |
| 6680748 | Monti | Jan 2004 | B1 |
| 6687877 | Sastry et al. | Feb 2004 | B1 |
| 6698021 | Amini et al. | Feb 2004 | B1 |
| 6701058 | Tsubaki | Mar 2004 | B1 |
| 6701845 | Ohmura | Mar 2004 | B2 |
| 6710809 | Niikawa | Mar 2004 | B1 |
| 6728729 | Jawa et al. | Apr 2004 | B1 |
| 6734911 | Lyons | May 2004 | B1 |
| 6735253 | Chang et al. | May 2004 | B1 |
| 6738155 | Rosenlund et al. | May 2004 | B1 |
| 6741271 | McConica et al. | May 2004 | B1 |
| 6741864 | Wilcock et al. | May 2004 | B2 |
| 6750902 | Steinberg et al. | Jun 2004 | B1 |
| 6757008 | Smith | Jun 2004 | B1 |
| 6757431 | Loce et al. | Jun 2004 | B2 |
| 6757684 | Svendsen | Jun 2004 | B2 |
| 6762791 | Schuetzle | Jul 2004 | B1 |
| 6766036 | Pryor | Jul 2004 | B1 |
| 6774935 | Morimoto et al. | Aug 2004 | B1 |
| 6775406 | Watson | Aug 2004 | B1 |
| 6801717 | Hofer | Oct 2004 | B1 |
| 6801719 | Szajewski et al. | Oct 2004 | B1 |
| 6809759 | Chiang | Oct 2004 | B1 |
| 6813312 | Tullberg et al. | Nov 2004 | B2 |
| 6816071 | Conti | Nov 2004 | B2 |
| 6816468 | Cruickshank | Nov 2004 | B1 |
| 6822660 | Kim | Nov 2004 | B2 |
| 6823092 | Sato | Nov 2004 | B1 |
| 6832009 | Shezaf et al. | Dec 2004 | B1 |
| 6856353 | Misawa | Feb 2005 | B1 |
| 6864911 | Zhang | Mar 2005 | B1 |
| 6871010 | Taguchi et al. | Mar 2005 | B1 |
| 6876393 | Yokonuma | Apr 2005 | B1 |
| 6885395 | Rabbani et al. | Apr 2005 | B1 |
| 6903763 | Noguchi et al. | Jun 2005 | B1 |
| 6922258 | Pineau | Jul 2005 | B2 |
| 6928230 | Squibbs | Aug 2005 | B2 |
| 6930707 | Bates et al. | Aug 2005 | B2 |
| 6940543 | Perotti et al. | Sep 2005 | B2 |
| 6940545 | Ray et al. | Sep 2005 | B1 |
| 6947075 | Niikawa | Sep 2005 | B1 |
| 6954224 | Okada et al. | Oct 2005 | B1 |
| 6961083 | Obrador et al. | Nov 2005 | B2 |
| 6961087 | Yoshida | Nov 2005 | B1 |
| 6967675 | Ito et al. | Nov 2005 | B1 |
| 6978047 | Montgomery | Dec 2005 | B2 |
| 6978311 | Netzer et al. | Dec 2005 | B1 |
| 6987528 | Nagahisa et al. | Jan 2006 | B1 |
| 6992711 | Kubo | Jan 2006 | B2 |
| 6999626 | Andrew | Feb 2006 | B2 |
| 7015949 | Sah | Mar 2006 | B1 |
| 7015954 | Foote et al. | Mar 2006 | B1 |
| 7023469 | Olson | Apr 2006 | B1 |
| 7027084 | Watanabe | Apr 2006 | B1 |
| 7031700 | Weaver et al. | Apr 2006 | B1 |
| 7046273 | Suzuki | May 2006 | B2 |
| 7046292 | Ziemkowski | May 2006 | B2 |
| 7065418 | Standard et al. | Jun 2006 | B2 |
| 7068316 | Pine | Jun 2006 | B1 |
| 7075567 | Hunter et al. | Jul 2006 | B2 |
| 7079176 | Freeman et al. | Jul 2006 | B1 |
| 7084910 | Amerson et al. | Aug 2006 | B2 |
| 7110025 | Loui et al. | Sep 2006 | B1 |
| 7110027 | Wyman | Sep 2006 | B2 |
| 7123292 | Seeger et al. | Oct 2006 | B1 |
| 7123935 | Takahashi | Oct 2006 | B2 |
| 7136094 | Ziemkowski | Nov 2006 | B2 |
| 7139018 | Grosvenor et al. | Nov 2006 | B2 |
| 7154535 | Yamasaki | Dec 2006 | B2 |
| 7158175 | Belz et al. | Jan 2007 | B2 |
| 7161619 | Niida et al. | Jan 2007 | B1 |
| 7163151 | Kiiskinen | Jan 2007 | B2 |
| 7196317 | Meissner, II et al. | Mar 2007 | B1 |
| 7203648 | Ostermann et al. | Apr 2007 | B1 |
| 7219365 | Sato et al. | May 2007 | B2 |
| 7221863 | Kondo et al. | May 2007 | B2 |
| 7227569 | Maruya | Jun 2007 | B2 |
| 7248924 | Casavant et al. | Jul 2007 | B2 |
| 7257317 | Ohnishi | Aug 2007 | B2 |
| 7287088 | Anderson | Oct 2007 | B1 |
| 7292229 | Morag et al. | Nov 2007 | B2 |
| 7327385 | Yamaguchi | Feb 2008 | B2 |
| 7327387 | Tanaka et al. | Feb 2008 | B2 |
| 7333134 | Miyamoto | Feb 2008 | B2 |
| 7339623 | Kawai | Mar 2008 | B2 |
| 7340766 | Nagao et al. | Mar 2008 | B2 |
| 7362968 | Kim | Apr 2008 | B2 |
| 7366979 | Spielberg et al. | Apr 2008 | B2 |
| 7379116 | Okamura | May 2008 | B2 |
| 7411623 | Shibutani | Aug 2008 | B2 |
| 7417667 | Shibutani | Aug 2008 | B2 |
| 7448063 | Freeman et al. | Nov 2008 | B2 |
| 7460495 | Li | Dec 2008 | B2 |
| 7460781 | Kanai et al. | Dec 2008 | B2 |
| 7463216 | Yamazaki et al. | Dec 2008 | B2 |
| 7474338 | Sato | Jan 2009 | B2 |
| 7477296 | Okumura | Jan 2009 | B2 |
| 7499084 | Kurakata | Mar 2009 | B2 |
| 7511737 | Singh | Mar 2009 | B2 |
| 7525568 | Raghunath | Apr 2009 | B2 |
| 7529411 | Haupt et al. | May 2009 | B2 |
| 7535491 | Kumagai et al. | May 2009 | B1 |
| 7542183 | Satoh et al. | Jun 2009 | B2 |
| 7602419 | Kiuchi | Oct 2009 | B2 |
| 7602421 | Hunter | Oct 2009 | B2 |
| 7612806 | Kazami et al. | Nov 2009 | B2 |
| 7636754 | Zhu et al. | Dec 2009 | B2 |
| 7647614 | Krikorian | Jan 2010 | B2 |
| 7650058 | Garoutte | Jan 2010 | B1 |
| 7711443 | Sanders et al. | May 2010 | B1 |
| 7782365 | Levien et al. | Aug 2010 | B2 |
| 7840892 | Pyhälammi et al. | Nov 2010 | B2 |
| 7860319 | Obrador et al. | Dec 2010 | B2 |
| 7872675 | Levien et al. | Jan 2011 | B2 |
| 7924324 | Fujita | Apr 2011 | B2 |
| 7945935 | Stonedahl | May 2011 | B2 |
| 8026944 | Sah | Sep 2011 | B1 |
| 8098287 | Misawa et al. | Jan 2012 | B2 |
| 8350946 | Jung et al. | Jan 2013 | B2 |
| 8429223 | Gilley et al. | Apr 2013 | B2 |
| 8528019 | Dimitrova et al. | Sep 2013 | B1 |
| 8593555 | Chun et al. | Nov 2013 | B1 |
| 8606383 | Jung et al. | Dec 2013 | B2 |
| 20010015756 | Wilcock et al. | Aug 2001 | A1 |
| 20010015759 | Squibbs | Aug 2001 | A1 |
| 20010028398 | Takahashi | Oct 2001 | A1 |
| 20010029521 | Matsuda et al. | Oct 2001 | A1 |
| 20010030709 | Tarnoff et al. | Oct 2001 | A1 |
| 20010031005 | Nister et al. | Oct 2001 | A1 |
| 20010032335 | Jones | Oct 2001 | A1 |
| 20010033333 | Suzuki et al. | Oct 2001 | A1 |
| 20010042043 | Shear et al. | Nov 2001 | A1 |
| 20010044858 | Rekimoto | Nov 2001 | A1 |
| 20010050875 | Kahn et al. | Dec 2001 | A1 |
| 20010052083 | Willins et al. | Dec 2001 | A1 |
| 20020006786 | Mine | Jan 2002 | A1 |
| 20020014954 | Fitzgibbon et al. | Feb 2002 | A1 |
| 20020015094 | Kuwano et al. | Feb 2002 | A1 |
| 20020018137 | Tsuda | Feb 2002 | A1 |
| 20020021359 | Okamoto | Feb 2002 | A1 |
| 20020024607 | Suga et al. | Feb 2002 | A1 |
| 20020028060 | Murata et al. | Mar 2002 | A1 |
| 20020030749 | Nakamura et al. | Mar 2002 | A1 |
| 20020054232 | Inagaki | May 2002 | A1 |
| 20020055955 | Lloyd-Jones et al. | May 2002 | A1 |
| 20020069036 | Mizokawa | Jun 2002 | A1 |
| 20020090217 | Limor et al. | Jul 2002 | A1 |
| 20020093575 | Kusaka | Jul 2002 | A1 |
| 20020103813 | Frigon | Aug 2002 | A1 |
| 20020118958 | Ishikawa et al. | Aug 2002 | A1 |
| 20020122194 | Kuwata et al. | Sep 2002 | A1 |
| 20020137529 | Takahashi | Sep 2002 | A1 |
| 20020141005 | Okisu et al. | Oct 2002 | A1 |
| 20020141586 | Margalit | Oct 2002 | A1 |
| 20020149677 | Wright | Oct 2002 | A1 |
| 20020154221 | Ishimaru | Oct 2002 | A1 |
| 20020171737 | Tullis | Nov 2002 | A1 |
| 20020171747 | Niikawa et al. | Nov 2002 | A1 |
| 20020176016 | Misawa et al. | Nov 2002 | A1 |
| 20020176508 | Boyce et al. | Nov 2002 | A1 |
| 20020186668 | Thomason | Dec 2002 | A1 |
| 20020191079 | Kobayashi et al. | Dec 2002 | A1 |
| 20020191952 | Fiore et al. | Dec 2002 | A1 |
| 20020196329 | Dudkowski | Dec 2002 | A1 |
| 20020196344 | McIntyre et al. | Dec 2002 | A1 |
| 20020197067 | Ohnishi | Dec 2002 | A1 |
| 20030005066 | Lazaridis et al. | Jan 2003 | A1 |
| 20030007078 | Feldis, III | Jan 2003 | A1 |
| 20030016289 | Motomura | Jan 2003 | A1 |
| 20030018802 | Romanik et al. | Jan 2003 | A1 |
| 20030020811 | Hunter et al. | Jan 2003 | A1 |
| 20030020814 | Ono | Jan 2003 | A1 |
| 20030021455 | Dixon et al. | Jan 2003 | A1 |
| 20030021591 | Grosvenor et al. | Jan 2003 | A1 |
| 20030025800 | Hunter et al. | Feb 2003 | A1 |
| 20030030731 | Colby | Feb 2003 | A1 |
| 20030037111 | Yoshioka | Feb 2003 | A1 |
| 20030039380 | Sukegawa et al. | Feb 2003 | A1 |
| 20030058265 | Robinson et al. | Mar 2003 | A1 |
| 20030063114 | Nishida | Apr 2003 | A1 |
| 20030063211 | Watanabe et al. | Apr 2003 | A1 |
| 20030069898 | Christodoulou | Apr 2003 | A1 |
| 20030072491 | Sirivara et al. | Apr 2003 | A1 |
| 20030081140 | Furukawa | May 2003 | A1 |
| 20030090690 | Katayama et al. | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030095191 | Saito | May 2003 | A1 |
| 20030103144 | Sesek et al. | Jun 2003 | A1 |
| 20030112354 | Ortiz et al. | Jun 2003 | A1 |
| 20030113014 | Katoh | Jun 2003 | A1 |
| 20030117642 | Haraguchi | Jun 2003 | A1 |
| 20030122940 | Myojo | Jul 2003 | A1 |
| 20030123078 | Kazami | Jul 2003 | A1 |
| 20030128272 | Clough et al. | Jul 2003 | A1 |
| 20030131002 | Gennetten et al. | Jul 2003 | A1 |
| 20030133018 | Ziemkowski | Jul 2003 | A1 |
| 20030151679 | Amerson et al. | Aug 2003 | A1 |
| 20030152263 | Kawano et al. | Aug 2003 | A1 |
| 20030160870 | Ziemkowski | Aug 2003 | A1 |
| 20030162556 | Libes | Aug 2003 | A1 |
| 20030180037 | Sommers | Sep 2003 | A1 |
| 20030182000 | Muesch et al. | Sep 2003 | A1 |
| 20030185302 | Abrams, Jr. | Oct 2003 | A1 |
| 20030189654 | Kage et al. | Oct 2003 | A1 |
| 20030197794 | Sakata | Oct 2003 | A1 |
| 20030206232 | Suzuki et al. | Nov 2003 | A1 |
| 20030222998 | Yamauchi et al. | Dec 2003 | A1 |
| 20030226023 | Peters | Dec 2003 | A1 |
| 20030229894 | Okada et al. | Dec 2003 | A1 |
| 20030234953 | Dawson et al. | Dec 2003 | A1 |
| 20030236831 | Ortiz et al. | Dec 2003 | A1 |
| 20030236832 | McIntyre et al. | Dec 2003 | A1 |
| 20040001145 | Abbate | Jan 2004 | A1 |
| 20040008258 | Aas et al. | Jan 2004 | A1 |
| 20040012686 | Ono et al. | Jan 2004 | A1 |
| 20040013319 | Wenstrand et al. | Jan 2004 | A1 |
| 20040017333 | Cooper et al. | Jan 2004 | A1 |
| 20040032394 | Ayatsuka | Feb 2004 | A1 |
| 20040032517 | Walmsley et al. | Feb 2004 | A1 |
| 20040037540 | Frohlich et al. | Feb 2004 | A1 |
| 20040042679 | Yamada | Mar 2004 | A1 |
| 20040046885 | Regan et al. | Mar 2004 | A1 |
| 20040056960 | Hayashi | Mar 2004 | A1 |
| 20040061782 | Kinjo | Apr 2004 | A1 |
| 20040061797 | Takahashi et al. | Apr 2004 | A1 |
| 20040062439 | Cahill et al. | Apr 2004 | A1 |
| 20040066968 | Glickman | Apr 2004 | A1 |
| 20040070586 | Taubin | Apr 2004 | A1 |
| 20040070678 | Toyama et al. | Apr 2004 | A1 |
| 20040071445 | Tarnoff et al. | Apr 2004 | A1 |
| 20040075750 | Bateman | Apr 2004 | A1 |
| 20040080653 | Tanaka et al. | Apr 2004 | A1 |
| 20040080661 | Afsenius et al. | Apr 2004 | A1 |
| 20040085456 | Kwag et al. | May 2004 | A1 |
| 20040088326 | Lin | May 2004 | A1 |
| 20040090525 | Eichmann | May 2004 | A1 |
| 20040090526 | Watanabe et al. | May 2004 | A1 |
| 20040095480 | Battles et al. | May 2004 | A1 |
| 20040105015 | Tsukioka | Jun 2004 | A1 |
| 20040119733 | Morimoto et al. | Jun 2004 | A1 |
| 20040119841 | Shimizu | Jun 2004 | A1 |
| 20040120562 | Hays et al. | Jun 2004 | A1 |
| 20040123131 | Zacks et al. | Jun 2004 | A1 |
| 20040130634 | Delaney et al. | Jul 2004 | A1 |
| 20040131282 | Yoshida et al. | Jul 2004 | A1 |
| 20040141056 | Izumi et al. | Jul 2004 | A1 |
| 20040145501 | Hung | Jul 2004 | A1 |
| 20040145657 | Yamamoto et al. | Jul 2004 | A1 |
| 20040150641 | Duiker | Aug 2004 | A1 |
| 20040150724 | Nozaki et al. | Aug 2004 | A1 |
| 20040156535 | Goldberg et al. | Aug 2004 | A1 |
| 20040160453 | Horton et al. | Aug 2004 | A1 |
| 20040166930 | Beaulieu et al. | Aug 2004 | A1 |
| 20040171381 | Inselberg | Sep 2004 | A1 |
| 20040172440 | Nakajima | Sep 2004 | A1 |
| 20040174434 | Walker | Sep 2004 | A1 |
| 20040174454 | Okamura | Sep 2004 | A1 |
| 20040179121 | Silverstein | Sep 2004 | A1 |
| 20040183903 | Pedersen | Sep 2004 | A1 |
| 20040183915 | Gotohda et al. | Sep 2004 | A1 |
| 20040187583 | Ogawa | Sep 2004 | A1 |
| 20040196388 | Kaku | Oct 2004 | A1 |
| 20040196399 | Stavely | Oct 2004 | A1 |
| 20040201683 | Murashita et al. | Oct 2004 | A1 |
| 20040201687 | Perotti et al. | Oct 2004 | A1 |
| 20040201690 | Bryant et al. | Oct 2004 | A1 |
| 20040201709 | McIntyre et al. | Oct 2004 | A1 |
| 20040218916 | Yamaguchi et al. | Nov 2004 | A1 |
| 20040221063 | Mogul | Nov 2004 | A1 |
| 20040223060 | Yasuda | Nov 2004 | A1 |
| 20040230420 | Kadambe et al. | Nov 2004 | A1 |
| 20040233308 | Elliott et al. | Nov 2004 | A1 |
| 20040233621 | Maeoka et al. | Nov 2004 | A1 |
| 20040239958 | Nagata et al. | Dec 2004 | A1 |
| 20040243419 | Wang | Dec 2004 | A1 |
| 20040252193 | Higgins | Dec 2004 | A1 |
| 20040252230 | Winder | Dec 2004 | A1 |
| 20040253990 | McCoog et al. | Dec 2004 | A1 |
| 20040257462 | Goris et al. | Dec 2004 | A1 |
| 20040263609 | Otsuki et al. | Dec 2004 | A1 |
| 20040263634 | Kiuchi | Dec 2004 | A1 |
| 20040263658 | Cozier et al. | Dec 2004 | A1 |
| 20050005308 | Logan et al. | Jan 2005 | A1 |
| 20050007456 | Lee et al. | Jan 2005 | A1 |
| 20050007471 | Walmsley et al. | Jan 2005 | A1 |
| 20050010407 | Jaroker | Jan 2005 | A1 |
| 20050010531 | Kushalnagar et al. | Jan 2005 | A1 |
| 20050013602 | Ogawa | Jan 2005 | A1 |
| 20050013604 | Ogawa | Jan 2005 | A1 |
| 20050018053 | Suga et al. | Jan 2005 | A1 |
| 20050021369 | Cohen et al. | Jan 2005 | A1 |
| 20050028221 | Liu et al. | Feb 2005 | A1 |
| 20050033760 | Fuller et al. | Feb 2005 | A1 |
| 20050033991 | Crane | Feb 2005 | A1 |
| 20050036033 | Imai | Feb 2005 | A1 |
| 20050036044 | Funakura | Feb 2005 | A1 |
| 20050046707 | Takane | Mar 2005 | A1 |
| 20050050043 | Pyhalammi et al. | Mar 2005 | A1 |
| 20050052685 | Herf et al. | Mar 2005 | A1 |
| 20050057687 | Irani et al. | Mar 2005 | A1 |
| 20050058321 | Buehler | Mar 2005 | A1 |
| 20050080894 | Apostolopoulos et al. | Apr 2005 | A1 |
| 20050084113 | Simpson et al. | Apr 2005 | A1 |
| 20050086391 | Chu et al. | Apr 2005 | A1 |
| 20050088417 | Mulligan | Apr 2005 | A1 |
| 20050093980 | Nonaka et al. | May 2005 | A1 |
| 20050099519 | Creamer et al. | May 2005 | A1 |
| 20050103863 | Zhu et al. | May 2005 | A1 |
| 20050105806 | Nagaoka et al. | May 2005 | A1 |
| 20050111036 | Takasaki | May 2005 | A1 |
| 20050113136 | Gosieski, Jr. | May 2005 | A1 |
| 20050125843 | Okezie et al. | Jun 2005 | A1 |
| 20050130717 | Gosieski, Jr. et al. | Jun 2005 | A1 |
| 20050131905 | Margolus et al. | Jun 2005 | A1 |
| 20050132414 | Bentley et al. | Jun 2005 | A1 |
| 20050134696 | Nath et al. | Jun 2005 | A1 |
| 20050140803 | Ohtsuka et al. | Jun 2005 | A1 |
| 20050144632 | Mears et al. | Jun 2005 | A1 |
| 20050150362 | Uehara | Jul 2005 | A1 |
| 20050152619 | Motomura et al. | Jul 2005 | A1 |
| 20050158015 | Nakayama et al. | Jul 2005 | A1 |
| 20050162533 | Noguchi et al. | Jul 2005 | A1 |
| 20050162699 | Fukunaga | Jul 2005 | A1 |
| 20050162965 | Fukuda et al. | Jul 2005 | A1 |
| 20050168965 | Yoshida | Aug 2005 | A1 |
| 20050169367 | Venetianer et al. | Aug 2005 | A1 |
| 20050180341 | Nelson et al. | Aug 2005 | A1 |
| 20050187901 | Maritzen et al. | Aug 2005 | A1 |
| 20050188399 | Tischer | Aug 2005 | A1 |
| 20050192685 | Puckette | Sep 2005 | A1 |
| 20050193421 | Cragun | Sep 2005 | A1 |
| 20050195285 | Ide | Sep 2005 | A1 |
| 20050195291 | Kubo | Sep 2005 | A1 |
| 20050203930 | Bukowski et al. | Sep 2005 | A1 |
| 20050206721 | Bushmitch et al. | Sep 2005 | A1 |
| 20050210267 | Sugano et al. | Sep 2005 | A1 |
| 20050210516 | Pettinato | Sep 2005 | A1 |
| 20050212912 | Huster | Sep 2005 | A1 |
| 20050212950 | Kanai | Sep 2005 | A1 |
| 20050231625 | Parulski et al. | Oct 2005 | A1 |
| 20050237388 | Tani | Oct 2005 | A1 |
| 20050237422 | Kido | Oct 2005 | A1 |
| 20050248776 | Ogino | Nov 2005 | A1 |
| 20050262097 | Sim-Tang et al. | Nov 2005 | A1 |
| 20050271251 | Russell et al. | Dec 2005 | A1 |
| 20050278461 | Ohta | Dec 2005 | A1 |
| 20060004712 | Hakala et al. | Jan 2006 | A1 |
| 20060010400 | Dehlin et al. | Jan 2006 | A1 |
| 20060023066 | Li et al. | Feb 2006 | A1 |
| 20060028553 | Mori et al. | Feb 2006 | A1 |
| 20060044394 | Read | Mar 2006 | A1 |
| 20060044398 | Foong et al. | Mar 2006 | A1 |
| 20060044416 | Miyazaki et al. | Mar 2006 | A1 |
| 20060055788 | Kawabe | Mar 2006 | A1 |
| 20060056056 | Ahiska et al. | Mar 2006 | A1 |
| 20060061451 | Chen | Mar 2006 | A1 |
| 20060068824 | Inselberg | Mar 2006 | A1 |
| 20060072028 | Hong | Apr 2006 | A1 |
| 20060083298 | Wang et al. | Apr 2006 | A1 |
| 20060083440 | Chen | Apr 2006 | A1 |
| 20060087559 | Huberman et al. | Apr 2006 | A1 |
| 20060087941 | Obradovich | Apr 2006 | A1 |
| 20060088276 | Cho et al. | Apr 2006 | A1 |
| 20060092291 | Bodie | May 2006 | A1 |
| 20060098112 | Kelly | May 2006 | A1 |
| 20060104483 | Harel et al. | May 2006 | A1 |
| 20060104600 | Abrams | May 2006 | A1 |
| 20060109349 | Takashima | May 2006 | A1 |
| 20060112413 | Ando et al. | May 2006 | A1 |
| 20060119711 | Ejima et al. | Jun 2006 | A1 |
| 20060125922 | Albert et al. | Jun 2006 | A1 |
| 20060125928 | Wolcott et al. | Jun 2006 | A1 |
| 20060125930 | Mindrum et al. | Jun 2006 | A1 |
| 20060125937 | LeGall et al. | Jun 2006 | A1 |
| 20060126861 | Saliterman | Jun 2006 | A1 |
| 20060136998 | Oowaki et al. | Jun 2006 | A1 |
| 20060143665 | Meek et al. | Jun 2006 | A1 |
| 20060150109 | Schultz | Jul 2006 | A1 |
| 20060173972 | Jung et al. | Aug 2006 | A1 |
| 20060174203 | Jung et al. | Aug 2006 | A1 |
| 20060174204 | Jung et al. | Aug 2006 | A1 |
| 20060174206 | Jung et al. | Aug 2006 | A1 |
| 20060176392 | Rainier et al. | Aug 2006 | A1 |
| 20060177132 | Jackson et al. | Aug 2006 | A1 |
| 20060177150 | Uyttendaele et al. | Aug 2006 | A1 |
| 20060187860 | Li | Aug 2006 | A1 |
| 20060192887 | Miyamaki et al. | Aug 2006 | A1 |
| 20060195322 | Broussard et al. | Aug 2006 | A1 |
| 20060197839 | Senior et al. | Sep 2006 | A1 |
| 20060203099 | Omata | Sep 2006 | A1 |
| 20060209089 | Date | Sep 2006 | A1 |
| 20060216021 | Touchard et al. | Sep 2006 | A1 |
| 20060226298 | Pierson | Oct 2006 | A1 |
| 20060230123 | Simmons et al. | Oct 2006 | A1 |
| 20060242164 | Evans et al. | Oct 2006 | A1 |
| 20060268117 | Loui et al. | Nov 2006 | A1 |
| 20060274165 | Levien et al. | Dec 2006 | A1 |
| 20060288273 | Erol et al. | Dec 2006 | A1 |
| 20060288374 | Ferris et al. | Dec 2006 | A1 |
| 20070013776 | Venetianer et al. | Jan 2007 | A1 |
| 20070097214 | Jung et al. | May 2007 | A1 |
| 20070100533 | Jung et al. | May 2007 | A1 |
| 20070100606 | Rogers | May 2007 | A1 |
| 20070100621 | Jung et al. | May 2007 | A1 |
| 20070113250 | Logan et al. | May 2007 | A1 |
| 20070120980 | Jung et al. | May 2007 | A1 |
| 20070195373 | Singh | Aug 2007 | A1 |
| 20070217761 | Chen et al. | Sep 2007 | A1 |
| 20070252901 | Yokonuma et al. | Nov 2007 | A1 |
| 20070274705 | Kashiwa et al. | Nov 2007 | A1 |
| 20080023232 | Morag et al. | Jan 2008 | A1 |
| 20080037749 | Metzger et al. | Feb 2008 | A1 |
| 20080120325 | Davis | May 2008 | A1 |
| 20080161948 | Bodin et al. | Jul 2008 | A1 |
| 20080162668 | Miller | Jul 2008 | A1 |
| 20080192129 | Walker | Aug 2008 | A1 |
| 20080228296 | Eilam et al. | Sep 2008 | A1 |
| 20080298796 | Kuberka et al. | Dec 2008 | A1 |
| 20080303909 | Watanabe et al. | Dec 2008 | A1 |
| 20090033752 | Bodnar et al. | Feb 2009 | A1 |
| 20090215388 | Karaoguz et al. | Aug 2009 | A1 |
| 20090281644 | Okamoto et al. | Nov 2009 | A1 |
| 20090305677 | Ellison et al. | Dec 2009 | A1 |
| 20100017289 | Sah et al. | Jan 2010 | A1 |
| 20110270916 | Shih et al. | Nov 2011 | A1 |
| 20120105716 | Jung et al. | May 2012 | A1 |
| 20120323349 | Khedouri et al. | Dec 2012 | A9 |
| 20130176341 | Jung et al. | Jul 2013 | A1 |
| 20140146205 | Xu et al. | May 2014 | A1 |
| 20140195011 | Sakuta et al. | Jul 2014 | A1 |
| 20140282923 | Narayan et al. | Sep 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 5064225 | Mar 1993 | JP |
| H09-018762 | Jan 1997 | JP |
| 10023303 | Jan 1998 | JP |
| 2001045452 | Feb 2001 | JP |
| 2001086383 | Mar 2001 | JP |
| 2001-309236 | Nov 2001 | JP |
| 2002-083280 | Mar 2002 | JP |
| 2002-094862 | Mar 2002 | JP |
| 2003-009044 | Jan 2003 | JP |
| 2004274625 | Sep 2004 | JP |
| WO 2005045807 | May 2005 | WO |
| WO 2005112437 | Nov 2005 | WO |
| Entry |
|---|
| cg.its.tudelft.nl, Delft University of Technology; “Shared cameras”; 1 page; located at http://www.cg.its.tudelft.nl/˜spiff/descSC.html; printed on Mar. 21, 2011. |
| Jain, Anil K.; “Fundamentals of Digital Image Processing”; 1989; pp. 1-569; Prentice-Hall, Inc.; Englewood Cliffs, NJ. |
| U.S. Appl. No. 12/283,420, Jung et al. |
| U.S. Appl. No. 11/998,824, Jung et al. |
| U.S. Appl. No. 11/998,819, Jung et al. |
| U.S. Appl. No. 11/998,447, Jung et al. |
| U.S. Appl. No. 11/975,352, Jung et al. |
| U.S. Appl. No. 11/703,063, Jung et al. |
| 2tiff.com; “Introduction to 2TIFF”; pp. 1-3; located at http://www.2tiff.com/help/; bearing a date of 2004; printed on Feb. 16, 2005. |
| about.com; “Image Size and Resolution”; pp. 1-3; located at http://graphicssoft.about.com/od/resolution/; bearing a date of 2005; printed on Feb. 16, 2005. |
| adobe.com, “Share images with Photo Mail (Win only)”, pp. 1-4, located at http://www.adobe.com/tips/phsel3photomail/main.html, printed on Jan. 26, 2005. |
| Bockaert, Vincent; “Interpolation”; pp. 1-4; located at http://www.dpreview.com/learn/?/Glossary/Digital—Imaging/Interpolation—01.htm; bearing a date of 1998-2005; printed on Feb. 16, 2005. |
| canon.ca, “Print/Share Button”, pp. 1-2, located at http://www.canon.ca/digitalphotography/english/ctech—article.asp?id=174&tid=6, bearing a date of Jan. 26, 2005, printed on Jan. 26, 2005. |
| cg.its.tudelft.nl, Delft University of Technology, “Shared cameras”, pp. 1, located at http://www.cg.its.tudelft.nl/˜spiff/descSC.html, printed on Jan. 27, 2005. |
| chainstyle.com; “Resolution and Image Size”; pp. 1-9; located at http://www.chainstyle.com/photoshop/webhelp/tutorials/basics/resolution—and—image—size.htm; printed on Feb. 16, 2005. |
| Chastain, Sue; “Q. is it better to use in-camera digital zoom or crop and resample with software?”; pp. 1-2; located at http://graphicssoft.about.com/cs/digitalimaging/f/digitalzoom.htm; bearing a date of 2005; printed on Feb. 16, 2005. |
| Dave; “How Many Pixels? A reasoned approach to digicam specifications”; pp. 1-5; located at http://www.imagine-resource.com/ARTS/HOWBIG/HOWBIG.HTM; bearing a date of 1999; printed on Feb. 16, 2005. |
| debian.org, “GNUstep application for digital still cameras”, pp. 1-2, located at http://packages.debian.org/unstable/graphics/camera.app, bearing a date of Jan. 26, 2005, printed on Jan. 27, 2005. |
| Digital Photography Review, “Kodak EasyShare One”, pp. 1-5, located at http://www.dpreview.com/news/0501/05010605kodakeasyshareone.asp, bearing a date of Jan. 6, 2005, printed on Jan. 26, 2005. |
| Ekdahl, Lars; “Image Size and resolution”; pp. 1-5; located at http://www.ekdahl.org/kurs/resolution/resolution2—eng.htm; bearing a date of 2002; printed on Feb. 16, 2005. |
| geocities.com; “Which is better? Resample the image in a photo editor, print at a low resolution, use Genuine Fractals, or resample in many small steps?”; pp. 1-4; located at http://www.geocities.com/roberthaus/olvtest/resample.html; printed on Feb. 16, 2005. |
| Har-Peled, Sariel; Koltun, Vladlen; Song, Dezhen; Goldberg, Ken; CiteSeer.Ist:, “Efficient Algorithms for Shared Camera Control”, pp. 1-2, located at http://citeseer.ist.psu.edu/har-peled02efficient.html, bearing a date of 2002, printed on Jan. 26, 2005. |
| home.iprimus.com.au; “Digital Cameras and Resampling”; pp. 1-2; located at http://home.iprimus.com.au/painless/resample.htm; printed on Feb. 16, 2005. |
| hp.com, “HP Image Zone Express step-by-step: HP Instant Share”, pp. 1-4, located at http://www.hp.com/united-states/ize/steps—instant—share.html, printed on Jan. 26, 2005. |
| Hua, Zhigang; Xie, Xing; Lu, Hanqing; Ma, Wei-Ying; Research.Microsoft.com, “COBO: Building Cooperative Environment for Cross-Device Image Sharing”, pp. 1, located at http://research.microsoft.com/research/pubs/view.aspx?type=technical+report&id=823, bearing a date of Nov. 2004, printed on Jan. 25, 2005. |
| imaging resource.com; “The Imaging Resource Quick Review”; pp. 1-22; located at http://www.imaging-resource.com/PRODS/1700/l70A.HTM; bearing a date of 2001; printed on Feb. 16, 2005. |
| intel.com, “Intel® PC Cameras”, pp. 1-2, located at http://www.intel.com/pccamera/, printed on Jan. 27, 2005. |
| kodak.com, “Frequently Asked Questions”, pp. 1, located at http://www.kodak.com/global/en/service/knowledgebase/digital-camera-faqs.jhtml?pq-path=1396/5759, bearing a date of Jan. 6, 2005, printed on Jan. 26, 2005. |
| Koren, Norman, “Understanding image sharpness: Digital cameras vs. film, part 2”, pp. 1-16, located at http://www.normankoren.com/Tutorials/MTF7A.html, bearing a date of 2000-2004, printed on Feb. 4, 2005. |
| ltlimagery.com; “About Resolution Understanding Digital Image Resolution”; pp. 1-10; located at http://www.ltlimagery.com/resolution.html; bearing a date of 2000-2004; printed on Feb. 16, 2005. |
| Mobileman, “Nikon D2H WiFi Digital Camera”, pp. 1-2, located at http://www.mobilemag.com/content/100/336/C2502/, bearing a date of Feb. 20, 2004, printed on Jan. 25, 2005. |
| money.cnn.com, “Playboy coming to iPod”, pp. 1-2, located at http://money.cnn.com/2005/01/05/technology/personaltech/playboy—ipod/index.htm, bearing a date of Jan. 5, 2005, printed on Jan. 26, 2005. |
| physorg.com; “World's First Built-In Wi-Fi-Enabled Digital Cameras”; pp. 1-3; located at http://www.physorg.com/news6183.html; bearing a date of Sep. 2, 2005; printed on Sep. 7, 2005. |
| Rains, Nick, “Vietnam Travel Photography the Digital Way”, pp. 1-7, located at http://www.luminous-landscape.com/locations/vietnam.shtml, bearing a date of 2003, printed on Feb. 3, 2005. |
| ritzcamera.com, “Canon—Powershot A85 Digital Camera”, pp. 1-8, located at http://www.ritzcamera.com/webapp/wcs/stores/servlet/ProductDisplay?storeId=10001&catalogId=10001&langId=-1&productId=13176854, printed on Jan. 26, 2005. |
| Ross, Suzanne, Research.Microsoft.com, “The Life of a Digital Photo”, pp. 1-5, located at http://research.microsoft.com/displayArticle.aspx?id=605, printed on Jan. 25, 2005. |
| Sciannamea, Michael, “WiFi-Enabled Digital Cameras About to Tap a Growing Marketplace”, pp. 1-5, located at http://wifi.webloesinc.com/entry/7312187118786387/, bearing a date of Oct. 12, 2004, printed on Jan. 25, 2004. |
| Sellen, Abigail; Fleck, Rowanne; Kindberg, Tim; Spasojevic, Mirjana; Research.Microsoft.com, “How and Why People Use Camera Phones”, pp. 1-16, located at http://research.microsoft.com/research/pubs/view.aspx?type=technical+report&id=823 bearing a date of Nov. 2004, printed on Jan. 25, 2005. |
| Sutherland, Ed; “CSR Intros Low-Cost, Single-Chip WiFi”, pp. 1-3, located at http://www.wi-fiplanet.com/news/article.php/3434131, bearing a date of Nov. 10, 2004, printed on Jan. 25, 2005. |
| swgc.mun.ca; “About image size and resolution”; pp. 1-7; located at http://www.swgc.mun.ca/vart2600/resolution.html; printed on Feb. 16, 2005. |
| U.S. Appl. No. 12/799,398, Jung et al. |
| Adobe Photoshop User Guide 5.0;bearing a date of 1998; pp. 1,2,22,31-35,41,46,48,55-58,101,108,128,167-1-7,259-284, and 311-316; Adobe Systems Inc. |
| Grant, Andrew; “Open vs. Closed Source Software”; Science in Africa—Africa's First On-Line Science Magazine; bearing a date of Jan. 2004; Science in Africa, Science magazine for Africa, © 2002; pp. 1-4; located at http://www.scienceinafrica.co.za/2004/january/software.htm. |
| Palmer, James M.; “Radiometry and Photometry FAQ, Version 1.01”; bearing a date of Jun. 1999; pp. 1-14; located at: http://employeepages.scad.edu/˜kwitte/clocuments/Photometry—FAQ.PDF. |
| U.S. Appl. No. 12/290,538, Jung et al. |
| U.S. Appl. No. 11/901,240, Jung et al. |
| U.S. Appl. No. 11/213,324, Jung et al. |
| U.S. Appl. No. 11/210,284, Jung et al. |
| U.S. Appl. No. 11/190,516, Jung et al. |
| U.S. Appl. No. 11/173,166, Jung et al. |
| U.S. Appl. No. 11/153,868, Jung et al. |
| U.S. Appl. No. 11/143,970, Jung et al. |
| U.S. Appl. No. 11/129,045, Jung et al. |
| U.S. Appl. No. 11/122,274, Jung et al. |
| U.S. Appl. No. 11/115,078, Jung et al. |
| U.S. Appl. No. 11/089,530, Jung et al. |
| Newell, Chris.; “ID3v2 Chapter Frame Addendum”; Dec. 2, 2005; pp. 1-5; BBC Research and Development; located at: http://id3.org/id3v2-chapters-1.0?action=print. |
| Nilsson et al.; “ID3v2 Draft Specification”; Mar. 26, 1998; pp. 1-28; located at: http://www.unixgods.org/˜tilo/ID3/docs/id3v2-00.html. |
| Number | Date | Country | |
|---|---|---|---|
| 20100271490 A1 | Oct 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11122274 | May 2005 | US |
| Child | 12799367 | US |
