Patent Grant
9967424
Various computerized system embodiments for managing data received from a transmitting device are disclosed herein. A possible computerized system implementation for managing data received from a remote device may provide data storage files including one or more saved versions of selected captured data received from a transmitting capture device; computer apparatus operably coupled with said data storage files; and one or more program applications configured to enable future back and forth transferability of the selected captured data between the separate data storage facility and an external unit. Additional program application features may provide for such transferability to be dependent upon confirmation that transferability occurs with an authorized party or approved device or authorized recipient party, and wherein an operational attribute of a destination storage facility or destination device is matched with a corresponding aspect of the transferred captured data.
Some exemplary process embodiments disclosed herein provide a data storage protocol technique that includes providing a separate storage facility that receives selected captured data via a communication link from at least one transmitting capture device, which capture device includes local memory capacity; maintaining some or all of the selected captured data at the separate storage facility as an inventory data version that is stored in accordance with a safekeeping arrangement; and providing different status categories to identify the inventory data version of the selected captured data. Additional possible process features may include establishing future accessibility guidelines in accordance with the safekeeping arrangement to control back and forth data transferability between the separate storage facility and an external unit, and implementing the future accessibility guidelines based on an applicable attribute associated with the external unit.
Exemplary computer program product embodiments having one or more computer programs may be provided for executing a process that includes receiving selected captured data at a separate storage facility via a communication link from a transmitting capture device, providing status categories to identify an inventory data version of the selected captured data, and implementing a safekeeping arrangement for restricted back and forth transferability between the separate storage facility and an approved external unit. An additional aspect may include evaluating one or more applicable attributes associated with the external unit as a basis for downloading a particular inventory data version of the selected captured data to the approved external unit.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
A user may enter commands and information into the computing device 20 through user input devices, such as a number of switches and buttons, illustrated as hardware buttons 44, which may be associated with the electronic device and connected via a suitable interface 45. Input devices may further include a touch-sensitive display screen 32 with suitable input detection circuitry 33. The output circuitry of the touch-sensitive display screen is connected to the system bus 23 via a video driver 37. Other input devices may include a microphone 34 connected through a suitable audio interface 35, and a physical hardware keyboard (not shown). In addition to the display 32, the computing device 20 may include other peripheral output devices, such as at least one speaker 38.
Other external input or output devices 39, such as a joystick, game pad, satellite dish, scanner, an external computer readable medium, or the like may be connected to the processing unit 21 through a USB port 40 and USB port interface 41, to the system bus 23. Alternatively, the other external input and output devices 39 may be connected by other interfaces, such as a parallel port, game port or other port. The computing device 20 may further include or be capable of connecting to a flash card memory (not shown) through an appropriate connection port (not shown). The computing device may further include or be capable of a connection with a network through a network port 42 and network interface 43, and/or through wireless port 46 and corresponding wireless interface 47. Such a connection may be provided to facilitate communication with other peripheral devices, including other computers, printers, and so on (not shown). It will be appreciated that the various components and connections shown are exemplary and other components and means of establishing communications links may be used.
The computing device 20 may be designed to include a user interface having a character, key-based, other user data input via the touch sensitive display 32 using a stylus (not shown). Moreover, the user interface is not limited to an actual touch-sensitive panel arranged for directly receiving input, but may alternatively or in addition respond to another input device, such as the microphone 34. For example, spoken words may be received at the microphone 34 and recognized. Alternatively, the computing device may be designed to include a user interface having a physical keyboard (not shown).
The device functional elements 51 are typically application specific and related to a function of the electronic device. The device functional elements are driven by a device functional element(s) interface 50, which coupled with the system bus 23. A functional element may typically perform a single well-defined task with little or no user configuration or setup, such as a refrigerator keeping food cold, a cell phone connecting with an appropriate tower and transceiving voice or data information, and/or a camera capturing and saving an image.
In the description that follows, certain embodiments may be described with reference to acts and symbolic representations of operations that are performed by one or more computing devices, such as the thin computing device 20 of
Embodiments may be described in a general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. An embodiment may also be practiced in a distributed computing environment where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
Embodiments may be implemented with numerous other general-purpose or special-purpose computing devices, computing system environments, and/or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with an embodiment include, but are not limited to, personal computers, handheld or laptop devices, personal digital assistants, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network, minicomputers, server computers, game server computers, web server computers, mainframe computers, and distributed computing environments that include any of the above systems or devices.
In addition, the digital camera 210 includes a lens (not shown) and an image acquisition module (not shown). The image acquisition module controls the lens, a shutter, an aperture, and/or other elements as necessary to capture an image through the lens. In an embodiment, capturing images using digital cameras or camcorders may be equated with photography as performed by conventional film cameras. A captured image may be processed, stored, viewed, and/or distributed by the digital camera. The digital camera also includes a system memory (not shown), such as the system memory 22 of the thin computing device 20 of
The digital camera 210 includes operability to receive a user input through an interface of the plurality of interfaces 220. For example, in an embodiment, detecting a user touch to the button 244D may be received as an instruction and/or a selection. Another detected user touch to another user interface of the plurality of user interfaces 220 may be received as another instruction and/or a selection. The user touch may be detected by a user interface physically incorporated in the aspect of the digital camera 210 or proximate thereto. In an alternative embodiment, a user input may be received by detecting a signal responsive to a sound or voice received by the microphone 234. For example, a detection and recognition of a signal responsive to a spoken command to the microphone 234 may be received as an instruction to activate a program associated with the digital camera. Further, a detection of a signal responsive to a sound or voice may be received by the microphone 234.
In an embodiment, the digital camera 310 may include a computing device (not expressly shown) that handles any required processing. For example, the computing device may include at least a part of the system described in conjunction with
The image management module 330 includes an operability to save a captured image at a resolution in the computer readable medium 340 and in a user-accessible form. In an embodiment, the operability to save the captured image at a resolution in the computer readable medium and in a user-accessible form includes an operability to save a captured image in a format at least substantially suitable for presentation by a visual display of the digital camera 310, such as a display screen. For example, the operability to save a captured image at a resolution in the computer readable medium and in a user-accessible form may include an operability to save a captured image at a resolution in a JPEG format, a GIF format, a TIFF format, or a PDF format. In another embodiment, the operability to save the captured image at a resolution in the computer readable medium and in a user-accessible form includes an operability to save the captured image at a resolution in the computer readable medium after data representative of the captured image has been decoded and processed from a raw format. Typically, the raw data is decoded and/or processed from a raw format, i.e., raw image data, into a JPEG format, a GIF format, a TIFF format, or a PDF format. In a further embodiment, the operability to save the captured image at a resolution in the computer readable medium and in a user-accessible form includes an operability to save the captured image in a form accessible to a user of the digital camera in the computer readable medium. For example, the form accessible to a user of the digital camera may include a JPEG format, a GIF format, a TIFF format, a PDF format, or a raw format where the digital camera allows a user access to a saved captured image in a raw format.
In an embodiment, an “image” may include a full image. In another embodiment, an “image” may include a portion of an image, a segment of a full image, a thumbnail of an image, and/or an icon that pertains to an image. Another embodiment of an “image” may include a photograph and/or a digital image that can be captured by an image capture device such as, for example, the digital camera 310. Certain embodiments of a streaming image may include a video that may be captured by the digital camera, such as, for example, a digital camcorder camera.
The term “resolution” may include an indication of a measurement of image detail, such as may be expressed as pixels per inch, dots per inch, or samples per inch, etc. In certain embodiments, a file size of an image is a function of its resolution, and in certain embodiments of relatively limited storage-capability cameras, relatively few high-resolution images can be saved.
In another embodiment, a “user-accessible form” may include at least one of a location in the computer readable medium that allows a user to access a file saved therein, a file formatted to allow a user of the digital camera 310 to view and/or manipulate the captured image, a property of the captured image written to the computer readable medium, and/or an organization of the computer readable medium that allows a user to access a file saved therein. For example, data indicative of the captured image written to a hard drive in a JPEG format generally allows a user to view and/or manipulate the captured image. In an embodiment, a user-accessible storage medium may include all or any portion of any computer readable storage medium that allows a user, typically through a user interface, to act with respect to and/or interact with the image, such as viewing the image, manipulating the image, and/or directing the image to another location.
The image management module 330 also includes an operability to decrease the resolution of the saved captured image in the computer readable medium if a condition is met. In an embodiment, the condition may include a condition corresponding in part or whole to a state of the computer readable medium, a presence and/or absence of a predetermined content of the saved captured image, a characteristic of the saved image, an image storage administrative criterion, and/or a temporal criterion. In a further embodiment, a condition does not include an automatic or standing condition that normally occurs upon completion of a processing, for example, completion of decoding raw image data into a more machine usable and/or user viewable format.
Examples of decreasing a resolution of a saved captured image include, but are not limited to, changing a resolution of a saved captured image, resampling a saved captured image, adjusting an exposure of a saved captured image, adjusting some image content of a saved captured image, and/or adjusting image composition of a saved captured image. As described within this document, certain embodiments of the decreasing a resolution of a saved captured image are configurable to decrease the resolution of the image such as by utilizing pixel-combination and/or combination of multiple images. The decreasing a resolution of a saved captured image may include altering image intensity and/or color values. The decreasing a resolution of a saved captured image may in certain embodiments, but not others, be equated to sizing the resolution of an image downward, and may other embodiments be implemented by removing pixels from the saved captured image. The decreasing a resolution of a saved captured image may pertain in certain embodiments, but not others, to altering the color values and/or the color intensities of a particular image. The decreasing a resolution of a saved captured image may pertain to decreasing the density of the pixels forming the image. During a resolution decreasing process, in certain embodiments of a display or projector, a footprint of pixels may be suitably altered to effectively change the resolution of the at least one image.
In an embodiment, the computer readable media 340 may include a variety of computer readable media products. The computer readable media may include any storage media accessible by a computing device, and includes both removable and non-removable media. By way of example, and not of limitation, computer-readable media may include any computer storage media. Computer storage media includes removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media may include, but are not limited to, magnetic devices, such as magnetic disk storage, magnetic cassettes, magnetic tape, or other magnetic storage devices; optical devices, such as CD-ROM, digital versatile disks (DVD), or other optical disk storage; memory cards, such a flash memory card; and/or any other medium which may be used to store the captured information and which can be accessed by a computing device. Combinations of any of the above may also be included within the scope of a computer-readable medium.
In an embodiment, the computer readable medium 340 includes a non-volatile computer storage device. In another embodiment, the computer readable medium includes a non-volatile computer readable medium. In a further embodiment, the computer readable medium includes a removable non-volatile computer readable medium.
In an embodiment, the image acquisition module 320 operable to capture an image includes an image acquisition module operable to capture a still image, an image stream, and/or a combination of a still image and an image stream. In another embodiment, the image acquisition module operable to capture an image includes an image acquisition module operable to capture at least one of a visual image, an audio image, and/or a combination of a visual image and an audio image. In a further embodiment, the image acquisition module operable to capture an image includes an image acquisition module operable to capture an image in response to a received instruction from another digital device. The received instruction from another digital device may include an instruction received from another digital camera. The received instruction may direct capture of the image, or may include data responsive to which the image acquisition module captures the image.
In an embodiment, the image management module 330 operable to save a captured image at a resolution in a computer readable medium and in a user-accessible form includes an image management module operable to save a captured image at a resolution in the computer readable medium and in a user-accessible album of images stored in a computer readable medium. In another embodiment, the image management module operable to save a captured image at a resolution in a computer readable medium includes an image management module operable to save a captured image at a resolution in the computer readable medium and in a user-accessible collection of images stored in a computer readable medium. In a further embodiment, the image management module operable to save a captured image at a resolution in the computer readable medium and in a user-accessible form includes an image management module operable to save a captured image at a resolution in a user-accessible data structure.
In an embodiment, the image management module 330 operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met includes an image management module operable to decrease the resolution of the saved captured image in the computer readable medium using a lossy compression algorithm if a condition is met. In another embodiment, the image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met includes an image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a time exceeds a preselected time threshold. The preselected time threshold may exceed five seconds. The preselected time threshold may exceed at least a selected one of ten seconds, thirty seconds, one minute, thirty minutes, ninety minutes, five hours, twelve hours, one day, one week, one month, or one year.
In a further embodiment, the image management module 330 operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met includes an image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a time value is inside a preselected time window. In an embodiment, the image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met includes an image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met where the condition corresponds to at least one of a storage space availability in the computer readable medium, a user established parameter, a preselected content of the image, and/or a parameter established by a storage management algorithm. In another embodiment, the image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met includes an image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition independent of the operation to save a captured image at a resolution in the computer readable medium is met. In a further embodiment, the image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition is met includes an image management module operable to decrease the resolution of the saved captured image in the computer readable medium if a condition responsive to an examination of at least one other captured image saved in the computer readable medium is met. For example, a condition responsive to an examination of at least one other captured image saved in the computer readable medium may include examining a content and/or context of the at least one or more other saved captured images for a repetition and/or duplication. If at least one other saved captured image is examined and found to be repetitive and/or duplicative of the saved captured image, the condition would be met and the image management module would operate to reduce the resolution of the saved captured image. In an alternative embodiment, the image management module may include an operability to reduce the resolution of the at least one other saved image in response to the condition being met.
In an embodiment, the image management module 330 may further include an image management module operable to further decrease the resolution of the captured image saved in the computer readable medium if another condition is met.
If a condition is met, the image management module 330 decreases the resolution of the saved captured image in the computer readable medium 340 from the initial resolution 410 to a decreased resolution 415. For example, a condition may include whether a user has not caused the digital camera 310 to display the captured saved image at the initial resolution 410 for more than ten seconds in the 30 days immediately after the image was captured. The image management module monitors for the condition being met. If the condition is met, i.e., a user has not caused the digital camera to display the saved captured image at the initial resolution for more than 10 seconds during the 30 days after the image was captured, the image management module decreases the resolution of the saved captured image in the computer readable medium. The resolution of the saved captured image is decreased from the initial resolution 410 to a lesser or decreased resolution, illustrated as the decreased resolution 415.
If another condition is met, the image management module 330 may further decrease the decreased resolution 415 of the saved captured image in the computer readable medium 340. For example, a condition may include whether a user has not caused the digital camera 310 to display the captured saved image at its decreased resolution 415 for more than ninety seconds during the 90 days after the resolution was reduced from the file 410. If the condition is met, i.e., a user has not caused the digital camera to display the saved captured image for more than ninety seconds during the 90 days after the saved captured image was reduced, the image management module further decreases the resolution of the written captured image in the computer readable medium. The resolution is decreased from the decreased resolution 415 to a further decreased resolution, illustrated as a further decreased resolution 420. In an embodiment, each decreased resolution is selected to use less file storage space in the computer readable medium than its predecessor does. In an embodiment, less viewed or lower user-valued files have their resolution degraded over time to maximize available storage capacity for newly captured images and/or frequently viewed images.
In an embodiment, the image administration circuit 730 for saving a captured image in the computer readable medium at a first resolution includes an image administration circuit for saving a captured image at a first resolution in at least one of a nonvolatile, a removable, and/or non-removable media implemented in any method and/or technology for storage of digital information. In another embodiment, the image acquisition module 720 operable to capture an image includes an image acquisition module operable to capture at least one of a still image, an image stream, and/or a combination of a still image and an image stream. In a further embodiment, the image acquisition module operable to capture an image includes an image acquisition module operable to capture at least one of visual image, an audio image, and/or a combination of a visual image and an audio image.
In an embodiment, the image acquisition module 720 operable to capture an image includes an image acquisition module operable to capture a real-world image. In another embodiment, the image administration circuit 730 for saving a captured image at a first resolution in the computer readable medium includes an image administration circuit for saving a captured real-world image at a first resolution in the computer readable medium. In a further embodiment, the image acquisition module operable to capture an image includes an image acquisition module operable to capture a virtual-world image. In another embodiment, the image administration circuit for saving a captured image at a first resolution in the computer readable medium includes an image administration circuit for saving a captured virtual-world image at a first resolution in the computer readable medium.
In another embodiment, the image administration circuit 730 for saving a captured image at a first resolution in the computer readable medium includes an image administration circuit for saving a captured image at a first resolution in the computer readable medium and in a user-accessible form. In a further embodiment, the image administration circuit for saving a captured image at a first resolution in the computer readable medium and in a user-accessible form includes an image administration circuit for saving a captured image at a first resolution in the computer readable medium and in a user-accessible location. In an embodiment, the image administration circuit for saving a captured image at a first resolution in the computer readable medium and in a user-accessible form includes an image administration circuit for saving a captured image at a first resolution in a computer readable medium that allows user access to the saved captured image. In a further embodiment, the image administration circuit for saving a captured image at a first resolution in the computer readable medium and in a user-accessible form includes an image administration circuit for saving a captured image at a first resolution in a computer readable medium configured for user access to the saved captured image.
In an embodiment, the image administration circuit 730 for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution includes an image administration circuit for saving the captured image in the computer readable medium at a resolution reduced from the first resolution. In another embodiment, the image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution where at least a portion of the saved captured image has a resolution less than the first resolution. In a further embodiment, the image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution includes an image administration circuit for reducing the resolution of the captured image from the first resolution into the second resolution and for saving the captured image in the computer readable medium at the second resolution. In an embodiment, the image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution includes an image administration circuit for reducing the resolution of at least one selected frame of a streaming captured image from the first resolution into the second resolution and not reducing at least one other selected frame of the streaming captured image.
In an embodiment, the image administration circuit 730 for removing the captured image saved at the first resolution from the computer readable medium includes an image administration circuit for deleting the captured image saved at the first resolution from the computer readable medium. In another embodiment, the image administration circuit for removing the captured image saved at the first resolution from the computer readable medium includes an image administration circuit for communicating the captured image saved at the first resolution to another computer readable medium. In an embodiment, the another computer readable medium may be physically associated with the device. In further embodiment, the another computer readable medium may not physically associated with the device.
In an embodiment, the image administration circuit 730 for communicating the captured image saved at the first resolution to another computer readable medium includes an image administration circuit for communicating the captured image saved at the first resolution to another computer readable medium and acquiring a track-back link to the communicated captured image. In another embodiment, the image administration circuit for removing the captured image saved at the first resolution from the computer readable medium includes an image administration circuit for communicating the captured image saved at the first resolution to at least one of another computer readable medium that is a less accessible computer readable medium, a slower computer readable medium, a cheaper computer readable medium, a temporarily available computer readable medium, an intermittently available computer readable medium, a more secure computer readable medium, a less secure computer readable medium, a public computer readable medium, a private computer readable medium, and/or a computer readable medium that is less accessible in terms of a location and/or a rate and/or a format.
In an embodiment, the image administration circuit 730 for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a preselected time has elapsed since the captured image at a first resolution was saved in the computer readable medium. In a further embodiment, the image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if available storage space in the computer readable medium is less than a preselected threshold. For example, the available storage space in the computer readable medium may include a presently available storage in the computer readable medium that is less than a preselected threshold, and/or predicted availability of storage in the computer readable medium that is less than a preselected threshold.
In another embodiment, the image administration circuit 730 for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition established by a user is met. The condition established by a user may include a user-selected condition, a user-created condition, and/or a user-determined condition. In a further embodiment, the image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if an image resolution changing criterion established by a storage administration criterion is met. In an embodiment, the storage administration criterion may correspond to image content, image content attributes, time, storage space, presence and/or absence of a selected subject, a frequent presence of a selected subject in other saved captured images, an at least substantial similarity to other saved captured images, and/or an at least substantial similarity to other saved captured images having a commonality; such as recently captured, captured in a time frame, and/or captured in temporal or spatial proximity. For example, a storage administration criterion may include keeping only one high resolution saved captured image of my son from all those captured during the month of December. In another example, a storage administration criterion may include keeping, i.e., not deceasing the resolution of sufficient images to enable some task or goal, such as keeping just enough images to construct a panorama, to create a high dynamic range composite, and/or an infinite depth of field image.
In an embodiment, the image administration circuit 730 for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition corresponding to data received from another digital device is met. In another embodiment, the image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition is met includes an image administration circuit for saving the captured image in the computer readable medium at a second resolution that is less than the first resolution if a condition responsive to an examination of at least one other captured image saved in the computer readable medium is met. In a further embodiment, the another digital device includes an image acquisition module operable to capture an image. In another embodiment, the device includes a digital camera. In a further embodiment, the device includes a handheld digital camera.
In an embodiment, the an image administration circuit 730 further includes an image administration circuit for saving the captured image in the computer readable medium at a third resolution that is less than the second resolution and removing from the computer readable medium the captured image saved at the second resolution, if another condition is met.
In an embodiment, a photograph may include a single picture of a scene, a stream of pictures of a scene that may be static or dynamic, and/or a combination thereof. In another embodiment, the image acquisition module operable to capture an image includes an image acquisition module operable to capture at least one of a visual picture, a sound, and/or a combination thereof.
For a second image, the user may compose a second picture/image by orientating the lens 360 toward a subject in a second scene as above. The image management module 330 saves the second image 974 at a first resolution of the second image in the computer readable medium 980.
For a third image, the user may compose a third picture/image by orientating the lens 360 toward a subject in a third scene as above. The image management module 330 saves the third image 976 at a first resolution of the third image in the computer readable medium 980.
In an embodiment, the first image 972, the second image 974, and/or the third image 976 may be saved in a digital photo album of images and/or a collection of digital images 985 in the user-accessible data structure. In another embodiment, the first image 972, the second image 974, and/or the third image 976 may be received from a source that may or may not have captured the images. These received images may be saved and managed as described in conjunction with
The storage medium manager module 1230 is operable to save a digital image in a form in the user-accessible digital storage medium 1240. The storage medium manager module is also operable to alter the form of the saved digital image if a condition is met. The condition may include at least one of clarifying condition, a user-defined condition, an informed condition, an evaluated condition, and/or a computed condition. An informed condition may include a condition that employs obtained information, in contrast to a condition running autonomously or an uninformed condition. An evaluated condition may include a condition evaluated in response to an internal condition, an external condition, and/or both conditions. A computed condition may include any computed condition, in contrast with a standing condition and/or a normal or native condition related to the digital image and/or the storage medium.
In an embodiment, the storage medium manager module 1230 operable to save a digital image in a form in the user-accessible digital storage medium 1240 includes a storage medium manager module operable to save a digital image of a real-world event in a form in the user-accessible digital storage medium. In another embodiment, the user-accessible digital storage medium includes a user-accessible digital storage medium associated with a digital camera operable to capture the digital image. In a further embodiment, the device 1210 further includes the processing unit 350. In another embodiment, the storage medium manager module further includes a storage medium manager module operable to provide the altered form of the saved digital image.
An embodiment provides a computer program product. The computer program product includes a computer-readable signal-bearing medium bearing program instructions. The program instructions include instructions operable to perform a process in a computing device. The process includes saving a digital image in a form in a user-accessible storage medium, and altering the form of the saved digital image if a condition is met. The computer-readable signal-bearing medium bearing the program instructions may include a computer-storage medium bearing the program instructions. The computer-readable signal-bearing medium bearing the program instructions may include a communications medium bearing the program instructions.
Another embodiment provides a device. The device includes means for saving a digital image in a form in the digital storage medium. The device also includes means for altering the form of the saved digital image if a condition is met.
A further embodiment provides a method. The method includes saving a captured image in a user-accessible memory. The method also includes deallocating at least a portion of the user-accessible memory associated with the saved captured image if a condition is met. In an embodiment, the saving a captured image into a user-accessible memory includes saving a captured image at a resolution into a user-accessible memory. In another embodiment, the deallocating at least a portion of the user-accessible memory associated with the saved captured image if a condition is met includes deallocating at least a portion of the user-accessible memory associated with the saved captured image if a condition is met. In a further embodiment, the deallocating at least a portion of the user-accessible memory associated with the saved captured image if a condition is met includes deallocating at least a portion of the user-accessible memory associated with the saved captured image if a condition is met that includes at least one of a clarifying condition, a user-defined condition, an informed condition, an evaluated condition, and/or a computed condition.
An embodiment provides a device. The device includes a memory and a memory manager. The memory manager includes operability to save a captured image into a user-accessible memory. The memory manager also includes operability to deallocate at least a portion of the memory associated with the resolution if a condition is met.
Another embodiment provides a device. The device includes first means for a holding user-accessible digital data representative of an image. The device also includes second means for saving user-accessible digital data representative of an image in the first means. The device further includes third means for altering the saved user-accessible digital data representative of the saved digital image if a condition is met.
A further embodiment provides a computer program product. The computer program product includes a computer-readable signal-bearing medium bearing program instructions. The program instructions are operable to perform a process in a computing device. The process includes saving a captured image in a memory and in a user-accessible form. The process also includes deallocating at least a portion of the memory associated with the saved captured image if a condition is met. The computer-readable signal-bearing medium bearing the program instructions may include a computer-storage medium bearing the program instructions. The computer-readable signal-bearing medium bearing the program instructions may include a communications medium bearing the program instructions.
An embodiment provides a method. The method includes directing digital data representative of an image to a managed means for holding the digital data representative of an image. The method also includes accepting modified digital data representative of the image, the digital data representative of the image having been modified by deallocating at least a portion of the digital data representative of the image by the managed means for holding digital data upon occurrence of a condition.
Referring to an exemplary high level embodiment 1220 shown in
The flow chart of
Additional features may include providing the future accessibility via a communication link with an approved device (block 1228), and providing the future accessibility via a communication link with an authorized party (block 1229). Further features may include providing restricted accessibility to the saved version of the selected captured data based on a fee schedule (block 1231) and providing a fee schedule that includes a fee allocation paid to an entity responsible for the separate storage location (block 1232).
Some implementations may provide a storage protocol that allows access to the saved version of the selected captured data by an authorized third party (block 1233). Other possible features may include providing a storage management task that allows usage or retrieval or distribution or replication or modification or reorganization of the saved version of the selected captured data (block 1236), providing for further retention of the saved version of the selected captured data by the separate storage location subsequent to executing the storage management task (block 1237), and providing a fee schedule that includes a fee allocation paid by or on behalf of an authorized user or an authorized third party (block 1238).
Referring to detailed embodiments 1240 shown in
Additional aspects may include approving a storage format for the saved version of the selected captured data based on accessibility to substantially non-altered data components (block 1241), and in some instances accessibility to regenerated or transformed data components (block 1242).
Further possible aspects shown in
Another feature may include implementing a transfer to one or more of the following types of storage schemes: backup, archive, removable, rewritable, permanent, server, base station, network storage, web site, central, integrated, distributed, dispersed, fragmented, non-altered, transformed, encoded, bitmap, compression, volatile, replicated, third party, storefront, mobile, vehicle, residence, office, shared, proprietary, and rights-managed (block 1247).
The embodiments 1250 of
Another process features may include implementing a transfer via a wireless link to the separate storage location (block 1252). Further aspects may include providing the different storage organization categories based at least in part on a parameter established by a storage management algorithm (block 1256). Related possible aspects may establish the storage management algorithm that retains in a device memory some captured data having a quality parameter that is within an output capability range of the device (block 1258), and in some instance may establish the storage management algorithm that transfers to the separate storage location some captured data having a quality parameter that exceeds an output capability of the device (block 1257).
Another possible feature includes establishing the storage management algorithm based at least in part on one or more of the following parameters: creator, participant, originator, source, owner, proprietary, public domain, goal, subject matter, event, established policy, selected policy, custom policy, redundancy, variety, resolution, reproduction, replication, captured quality, device quality, captured fidelity, device fidelity, commercial value, personal value, expected future use, recipient, required access frequency, expected access frequency, potential distribution, taxonomy, common theme, tag, classification, device capability, device attribute, device parameter, storage capability, storage attribute, storage parameter, device setting, user task, device context, user context, device history, and user history (block 1259).
Referring to
Some implementations may further provide for maintaining the identifier record to facilitate a storage management task concerning the saved version of the selected captured data via a communication link with the designated device or with an authorized party (block 1264). Further aspects may include providing an exemplar or abbreviation or indicia that is recognizable by the authorized party and that is operably coupled to the identifier record to facilitate a storage management task concerning the saved version of the selected captured data (block 1266).
Another possible feature disclosed in
Some implementations may include processing the selected captured data to accomplish an allocation of the selected captured data among the one or more storage organization categories, which allocation is established automatically by the device prior to the transferring to the separate storage location (block 1269).
Referring to
As further illustrated in
The exemplary embodiments 1280 disclosed in
Other possible features may include maintaining the identifier record that enables an authorized user or an authorized third party to use a different device to obtain future accessibility to the saved version of the selected captured data (block 1283).
Additional implementations may include obtaining one or more of the following types of captured data: text, image, graphics, voice, music, sound, audio, video, audio/visual, monochrome, color, data log, measurement, instruction, biomedical, financial, sensor, environmental, personal, public, transactional, shopping, commercial, security, automotive, device-diagnostic, game, and virtual world (block 1286). Another possible aspect may include obtaining one or more of the following types of captured data: still image, image stream, and combination of still image and image stream (block 1287).
Further illustrated aspects may include obtaining one or more of the following types of captured data: real-time, time-delayed, original, copied, scanned, faxed, sensed, detected, derived, computed, modified, composite, enhanced, reduced, filtered, edited, condensed, compressed, compiled, retransmitted, forwarded, stored, cached, prefetched, processed, raw, live, batched, and uploaded (block 1288).
The detailed flow chart of
Further possible features may include making a selection of the captured data to be saved on storage media at the storage location based at least in part on a set of rules configured by an owner or operator of the separate storage location (block 1293).
Other illustrated process components shown in
A further possible aspect may include allowing an authorized user associated with the device to make a determination or modification of an applicable storage organization category after the selected captured data has been transferred from the device (block 1298).
Referring to the various embodiments 1300 of
A further related aspect may include employing one or more of the following features for making the captured data available to an authorized user associated with the device: printout, screen display, viewfinder display, display monitor, thumbnail display, removable memory, device memory, audio, tactile, alert, notification, transmittal to other device, and instructional (block 1302).
Another possible feature may include making a selection of the captured data to be saved on storage media at the separate storage location based at least in part on a set of rules configured by an authorized user associated with the device (block 1303).
The flow chart of
Additional implementations may include making a transfer of the selected captured data to storage media owned or controlled by an authorized user associated with the device (block 1314), and making a transfer of the selected captured data to a storage media owned or controlled by a third party (block 1313).
Referring to the exemplary embodiments 1315 of
Additional possible features may include obtaining captured data on a portable device (block 1317), and obtaining captured data on the portable device having one or more of the following storage capabilities: dedicated wireless link to remote storage, non-dedicated wireless link to remote storage, wireless link to multiple remote storage units, volatile memory, permanent memory, rewritable memory, internal memory, removable memory, backup memory, distributed memory, flash memory, and memory card (block 1318).
Further aspects may include obtaining captured data on a device owned or controlled by a third party, wherein the storage media at the storage location is also owned or controlled by the same third party (block 1316).
The high level flow chart of
Additional process features may include implementing a storage protocol for keeping a saved version of selected captured data at the separate storage location, which storage protocol includes different organization categories (block 1328). A further process feature may include maintaining an identifier record to enable future accessibility to the selected captured data by an authorized party or by a designated device (block 1329). The exemplary computer program product may include storage media or communication media for encoding the process instructions (block 1331).
The schematic block diagram of
The intermediate source capture device 1345 associated with user 1346 is shown receiving data inputs 1347, 1348 and may have capability for transferring selected captured data via communication link 1349 to separate storage location 1335. The hybrid capture/access device 1350 associated with one or more users 1351 may have capability for both transferring selected captured data to separate storage location 1335 as well as accessing saved versions of the selected captured data available at the separate storage location (see bidirectional communication link 1352).
In some instances a designated device may be approved for implementing a transfer and/or access to the separate storage location 1335. In other instances an authorized party (e.g., user associated with the capture device or with access device, authorized third party, etc.) may be authorized for implementing a transfer and/or access from many types of designated devices to the separate storage location 1335.
The schematic diagram of
Possible aspects may include an authorized party 1356 associated with access device 1355 having a communication link 1357 via cable to separate storage location 1335. Another possible aspect may include a third party 1361 associated with approved access device 1360 having a communication link 1362 via dial-up line to separate storage location 1335. A further possible aspect may include the approved automated access device 1365 having a wireless communication link 1366 to separate storage location 1335.
Another possible aspect may include multiple entities such as authorized party 1371, authorized party 1372, and third party 1373 associated with approved access device 1370 having a communication link 1374 (e.g., radio signal, television signal, etc.) via satellite 1375 to separate storage location 1335.
Referring to the schematic block diagram of
An exemplary data storage module 1390 may include one or more saved data versions 1392, non-altered data components 1393, modified data components 1394, transformed data 1396, and regenerated data 1397. An illustrated possible feature may include centralized storage media 1400, and in some instances active data storage files 1402 and archived data storage files 1404. Further aspects in some implementations may include distributed storage media 1406 and removable storage media 1408.
Processing of data may be accomplished by an exemplary computerized storage system 1410 incorporated as an integral part of the separate storage location 1380 or remotely linked to the separate storage location 1380. The computerized storage system 1410 may include processor 1412, controller 1414, one or more applications 1416, and memory 1418.
Additional types of storage-related modules may include identifier records 1420, storage protocol 1422, storage organization categories 1424, storage management algorithm 1426, and storage management tasks 1428.
Referring to the schematic block diagram of
Other communication links to the capture device 1430 may include an input channel for original captured data 1442, and another input channel for transmitted captured data 1444.
It will be understood that various functional aspects may be incorporated with the capture device and/or with the separate storage location. Accordingly the illustrated embodiment features of
Of course it will be understood that the various exemplary type of records and data files are disclosed herein for purposes of illustration only and are not intended to be limiting. Some of the specified file parameters and records may not be included in certain implementations, and additional types of file parameters and records may be desirable additions in other implementations.
A computer apparatus 1450 incorporated in the capture device 1430, or in some instances remotely linked to the capture device 1430, may include processor 1452, controller 1454, one or more applications 1456, and memory 1458. Additional aspects operably coupled with the capture device 1430 may include integrated storage media 1460, temporary storage 1466, distributed storage media 1462, and removable storage media 1464.
Further types of data storage files may include actual captured data 1467, modified captured data 1468, one or more data exemplars 1472, one or more data samples 1474, and in some instances various transformed data excerpts 1476. Depending on the circumstances additional aspects may include data selection rules 1478, and a data selection program 1479 to process the captured data and facilitate a determination of which captured data will be immediately or ultimately transferred to the separate storage location. It will be understood that various records may be maintained at the transmitting device and/or at a destination storage facility to identify which individual or groups of captured data have been transferred, and in some instances providing addition details regarding the nature (e.g., resolution, future access limitations, etc.) of the selected captured data that has been transferred.
It will be further understood that aspects of such data selection rules 1478 or data selection program 1479 may be incorporated at the destination storage facility or at the transmitting device in order to achieve efficient and desirable transfer results. Some embodiments may provide somewhat sophisticated rules, including an ability to detect redundancies and carry out selection policies and goals. For example, a storage algorithm regarding soccer match data may seek to transfer at least one high resolution shot of each goal attempted or made, as well as limiting transferred spectator images to not more than ten per match and limiting transferred action player images to not more than fifty per match. Similarly a policy guideline may provide predetermined limits regarding transferred audiovisual data for each soccer match. Of course, availability of local storage capacity associated with the transmitting device may result in temporary (or perhaps long term) retention policies regarding certain types of captured data (current topical interest, additional time for pre-transfer review, etc.).
As disclosed herein, some exemplary system embodiments and computer program implementations may provide one or more program applications that include encoded process instructions for implementing a storage management algorithm that allows accessibility by a particular device to selected captured data having a quality parameter that is within an operational capability range of the particular device. Another possible implementation may provide one or more program applications that include encoded process instructions for implementing a storage management algorithm that retains for future accessibility the selected captured data having a quality parameter that exceeds an operational capability of a transmitting device.
Additional exemplary system embodiments and computer program implementations may provide one or more program applications that include encoded process instructions for implementing a storage management algorithm that facilitates accessibility to the different storage organization categories based on one or more of the following parameters: creator, participant, originator, source, owner, proprietary, public domain, goal, subject matter, event, established policy, selected policy, custom policy, redundancy, variety, resolution, reproduction, replication, captured quality, device quality, captured fidelity, device fidelity, commercial value, personal value, expected future use, recipient, required access frequency, expected access frequency, potential distribution, taxonomy, common theme, tag, classification, device capability, device attribute, device parameter, storage capability, storage attribute, storage parameter, device setting, user task, device context, user context, device history, and user history.
Other exemplary system embodiments may provide data storage files that include a saved version of selected captured data received from one or more of the following type of transmitting devices: still camera, audio recorder, digital audio recorder, audio-visual recorder, video recorder, digital video recorder, video camera, video/still camera, data recorder, telephone, cell phone, transceiver, PDA, computer, server, printer, fax, multi-function device, scanner, copier, surveillance camera, data sensor, mote, distributed imaging element, ingested sensor, medical sensor, medical imaging, health-monitoring device, traffic management device, media library, media player, vehicle sensor, vehicular device, environmental sensor, implanted device, mobile unit, fixed unit, integral, applied device, worn device, remote, radio, communication unit, scheduler, private, public, shared , residential, business, and office.
Additional possible system features may provide one or more transmitting devices for transferring the selected captured data via a communication link to the data storage files at a separate storage facility. Further possible system aspects may include one or more transmitting devices configured to implement transferring of the selected captured data based on one or more of the following criteria: rule, user input, user state, configuration, commercial, personal, context, space, device memory, device capability, bandwidth, separate storage memory, separate storage capability, separate storage accessibility, cost, task, preference, storage protocol, security, privacy, affiliation, and membership.
In some instances an exemplary implementation may include one or more transmitting devices that are owned or controlled by an entity that is an owner or operator of the separate storage facility.
Further exemplary system embodiments may provide one or more transmitting devices that include a portable transmitting device having one or more of the following storage capabilities: dedicated wireless link to remote storage, non-dedicated wireless link to remote storage, wireless link to multiple remote storage units, volatile memory, permanent memory, rewritable memory, internal memory, removable memory, backup memory, distributed memory, flash memory, and memory card.
Additional process components incorporated in a computer program product may include retaining at a separate storage facility for future availability some selected captured data having a given quality characteristic, which selected captured data is received via a communication link with a capturing device. A related incorporated process component may include retaining for future availability one or more of the following types of selected captured data: real-time, time-delayed, original, copied, scanned, faxed, sensed, detected, derived, computed, modified, composite, enhanced, reduced, filtered, edited, condensed, compressed, compiled, retransmitted, forwarded, stored, cached, prefetched, processed, raw, live, batched, and uploaded.
Other process components incorporated in a computer program product may include enabling future accessibility by an authorized user or approved device or recipient party to the selected captured data pursuant to the storage protocol. A related incorporated process component may include providing one or more of the following parameters associated with or incorporated in an identity record to facilitate the future accessibility: exemplar, abbreviation, indicia, symbol, code, name, title, icon, date, excerpt, characteristic, form, alternate format, listing, reorganization, aggregation, summary, reduction, representation, sample, thumbnail, image, preview, group specimen, sub-group element, unique, non-unique, arbitrary, global, semantic, public, private, and encoded.
A further process component incorporated in a computer program product may include providing an identifier record that is operably coupled to one or more of the different organization categories. In some implementations an incorporated process feature related to the identifier record may include providing the identifier record at the separate storage facility. Another possible incorporated process feature related to the identifier record may include providing the identifier record at the capturing device or other approved device.
Referring to the high level flow chart of
Additional exemplary process embodiments 1505 are shown in
It will be understood that some implementations may provide an authentication relationship between a collection of identifier records and an approved device (e.g., capture device, transmitting device, personal mobile device, etc.). Data security may then be accomplished by providing limited logon rights, lockout schemes, or other restricted device usage techniques. The pertinent identifier record(s) can be activated pursuant to specified device interaction with the separate storage facility.
Some implementations may include providing the future access via a communication channel with an authorized user associated with a transmitting device or other device (block 1509). Another possible feature may include providing the future access via a communication channel with an authorized third party (block 1511).
It will be understood that some embodiments may provide an authentication relationship between a collection of identifier records and an authorized user or authorized third party. This results in future access to the separate storage facility becoming potentially more global. For example, such an authorized user or authorized third party who moves to any appropriate convenient device can generate or acquire the pertinent identifier record(s) necessary for activating a management task (e.g., retrieval, reorganization, status change, distribution authorization, etc.). In other words, such an appropriate convenient device temporarily becomes an “approved device” so long as its user qualifies as an “authorized user” or authorized third party.
Additional possible aspects illustrated in
The exemplary embodiments 1515 shown in
Additional process components may include receiving selected captured data having a given quality characteristic (block 1519), maintaining some or all of the selected captured data without a significant loss of the given quality characteristic (block 1521), and receiving selected captured data having a modified quality characteristic that was changed from a previous given quality characteristic (block 1522).
Further illustrated exemplary features in
Other possible aspects may include maintaining the captured data at the separate storage facility in a format that enables distribution of the saved version to one or more third party recipients pursuant to the storage access protocol (block 1528), and providing restricted availability to the selected captured data based on a fee schedule that includes a fee allocation paid by a third party recipient (block 1529).
The detailed flow chart of
Additional process components may include providing an exemplar or abbreviation or indicia that is recognized by an authorized party and that is operably coupled to the identifier record to facilitate a storage management task concerning the saved version of the selected captured data (block 1533). A related aspect may include processing a storage management task initiated by one or more of the following: owner of separate storage facility, operator of separate storage facility, transmitting device user, transmitting device, authorized party, approved device, and recipient party (block 1534). Further related aspects may include providing one or more of the following type of exemplar or abbreviation or indicia: symbol, code, name, title, icon, date, excerpt, characteristic, form, alternate format, listing, reorganization, aggregation, summary, reduction, representation, sample, thumbnail, image, preview, group specimen, sub-group element, unique, non-unique, arbitrary, global, semantic, public, private, and encoded (block 1536).
Other possible aspects illustrated in
Referring to the exemplary embodiment features 1540 shown
Additional possible aspects may include implementing one or more of the following types of storage organization guidelines to facilitate future access by an authorized party or approved device or recipient party: original high resolution, permanent high resolution, temporary high resolution, lower resolution, temporary lower resolution, permanent lower resolution, deleted high resolution, deleted lower resolution, deleted content, included content, excluded content, subject matter, event, author, creator, participant, redundancy, repetition, quality, size, resolution, fidelity, tagged, preview, sample, group, sub-group, composite group, individual, personage, entity, item, content, composition, summary, augmentation, attribute, content category, frequency, and inventory (block 1542).
Another exemplary feature may include providing the different storage organization categories based at least in part on one or more of the following type of parameters: temporal, available device memory, available storage location memory, user selected, device limitation, storage location requirement, and recipient choice (block 1543).
The exemplary detailed embodiments 1545 shown in
Another possible aspect relating to an identifier record may include enabling an authorized party or approved device or recipient party to locate the saved version and/or execute a storage management task concerning the saved version of the selected captured data by reference to the identifier record (block 1547). It will be understood that in some embodiments the identifier record is operably coupled with a recognizable element that an authorized user can “look at” or authorized device can detect (e.g., identify) in order to locate selected captured data and/or execute a storage management task. However in other embodiments such a recognizable element (e.g., representative sample, thumbnail, exemplar, topical pointer, etc.) may directly function as the identifier record that is operably coupled to the separate storage facility.
Further possible features may include receiving one or more of the following types of selected captured data at the separate storage location: text, image, graphics, voice, music, sound, audio, video, audio/visual, monochrome, color, data log, measurement, instruction, biomedical, financial, sensor, environmental, personal, public, transactional, shopping, commercial, security, automotive, device-diagnostic, game, and virtual world (block 1551).
The exemplary embodiment 1555 shown in
Further possible programmed process components may include providing an identifier record that is operably coupled to one or more of the different organization categories (block 1559), and enabling future accessibility by an authorized user or approved device or recipient party to the selected captured data pursuant to the storage protocol (block 1561).
Referring to the schematic block diagram of
As disclosed herein, a particular process for choosing selected captured data to be transferred to a separate storage facility 1567 may be accomplished by a program control module 1575 and/or by manual control 1577. Various types of transferability communication channels 1569 may be used that incorporate short and long distance communication media connections (e.g., Internet, wireless, cable, LAN, WAN, etc.) in order to provide periodic back and forth transfers between an approved external unit such as capture device 1565 and one or more separate storage facilities such as 1567.
In some exemplary implementations, various storage management functions may be performed at the separate storage facility 1567 under control of an owner/operator 1568 or in some instances under remote control by an approved device or authorized user 1566. Accordingly the illustrated separate storage facility embodiment 1567 includes data storage files 1580 with long term memory 1581 and temporary memory 1582 that store inventory data versions of the selected captured data received from a transmitting capture device 1565.
An exemplary data management technique at the separate storage facility 1567 may include representative thumbnails 1583 and other exemplars 1584 that serve as an identifier link (e.g., directly and/or through an identifier record) to different categories of stored inventory data versions (e.g., replicated, enhanced quality, downgraded quality, transformed, regenerated, etc.). Visual access to the inventory data versions as well as to thumbnails 1583 and exemplars 1584 may be provided in various ways such as by monitor 1586. Transferability management is shown to be subject to instructions from program control module 1585 as well as by manual control 1587.
Referring to the schematic block diagram of
Exemplary informational file records that may be included in data storage records 1595 provided at or in connection with the separate storage facility 1590 may include status category records 1596, and authorization lists 1597 with respect to users, third parties, data recipients, approved capture/transmitting devices, approved access devices, etc. Another possible file record may specify obligated parties and applicable provisions related to safekeeping arrangements 1598. Of course such file records are for purposes of illustration only, and may be augmented or simplified depending on the circumstances.
Data storage records 1595 may include audio/visual inventory data 1601, still images inventory data 1602, audio inventory data 1603, and textual inventory data 1604. Each type of data files may be categorized in various ways, such as for example between high quality 1606, standard quality 1607 and low quality 1608. Such examples are for purposes of illustration only and are not intended to be limiting. It will be understood that such categorization of stored data files may be updated or modified as access availability needs change over time.
As further shown in the exemplary embodiments of
It will be understood that some exemplary transferability schemes may provide transfers of captured or stored data that does not identically match a destination device or destination storage capability. However such type of matching may in some circumstances provide additional advantages and benefits.
Referring to the schematic diagram of
The various exemplary storage categories of
Another possible broad category includes soccer match data 1620 with sub-categories for Rudy's final match 1621, goal attempts 1622, and high quality team color pictures 1623. A further possible broad category includes audio/visual student concert excerpts data 1625 with overlapping related sub-categories for complete student concert audio data 1626 and for still color images of performers 1627.
Yet a further possible broad category includes Wednesday business negotiation data 1630 with a sub-category for audio transcript 1634. A related sub-category may be provided for textual documents 1631 that includes a working draft segment 1632 and a high quality original signed contracts segment 1633.
Some or all of these same captured data components may collectively and individually also be incorporated in a different categorization scheme. For example, exemplary categories may include text 1636, voice audio 1637, music audio 1638, and audio/visual 1639. Other possible categories for this scheme may include personal multi-media 1640, commercial multi-media 1641, high quality image 1642, and standard quality image 1643.
Some or all of these same captured data components may collectively and individually also be incorporated in yet another different categorization scheme. For example, exemplary categories may include public domain data 1645, proprietary data 1646, restricted access data 1647, data for distribution 1648 and third party accessible data 1649.
It will be understood that a particular separate data storage facility may have numerous authorized users and designated devices providing selected captured data under different safekeeping arrangements and related fee schedules. These same authorized users and designated devices as well as other patrons may be subject to additional accessibility guidelines and related fee schedules. Accordingly the illustrated examples are not intended to be limiting, and it is understood that changes may be made to accommodate the needs and desires of all different types of users and patrons.
The high level flow chart of
Additional exemplary embodiment features 1660 are disclosed in
Further possible implementations may include establishing flexible guidelines that allow user intervention for determining whether to transfer certain selected captured data from the at least one transmitting capture device to the separate storage facility (block 1666), establishing flexible guidelines that allow user intervention for determining whether to transfer certain selected inventory data versions from the separate storage facility to an external unit (block 1667), and establishing flexible guidelines that allow user intervention for determining whether to redirect certain selected inventory data versions from the separate storage facility to an authorized recipient party (block 1668).
The more detailed flow chart of
Other exemplary implementation features may include transferring an inventory data version having a particular quality characteristic from the separate storage facility to an external unit based on a matching operational quality capability of the external unit (block 1673), and transferring selected captured data having a particular quality characteristic from an external unit to the separate storage facility based on a deficient operational quality capability of the external unit (block 1674).
Additional aspects may include transferring an inventory data version from the separate storage facility to an external unit based on an identity confirmation of an authorized user at the approved external unit (block 1676), transferring selected captured data from an external unit to the separate storage facility based on a failure to obtain confirmation of an authorized user at the external unit (block 1677).
The illustrative features 1680 shown in
Further exemplary features may include preventing transfer of an inventory data version from the separate storage facility to an external unit based on confirmation of the external unit's location in a restricted area (block 1683), establishing a guideline for redirecting certain inventory data versions to an authorized recipient party (block 1684), and establishing a guideline for redirecting certain inventory data versions to an approved device (block 1686).
Referring to the detailed exemplary embodiments 1690 shown in
Another possible aspect may include providing an identifier record operably coupled to one or more status categories of inventory data versions (block 1695). A further related aspect may include enabling access to the identifier record by an authorized user or approved device or recipient party to accomplish a storage management task regarding the selected captured data (block 1696). Other possible implementation features may include enabling a storage management task initiated from an external unit to cause selected captured data to be off-loaded to the separate storage facility, or to cause inventory data versions to be down-loaded to an external unit, or to cause certain inventory data versions to be redirected to an authorized recipient party (block 1697).
The detailed exemplary embodiment features 1700 shown in
The various exemplary embodiment features 1710 of
Further possible implementation features may include making a selection of the captured data to be saved on storage media at the storage location based at least in part on a set of rules configured by an owner or operator of the separate storage location (block 1717). Other possible features may include employing one or more of the following features for making the captured data available to an authorized party prior to the transferring: printout, screen display, viewfinder display, display monitor, thumbnail display, removable memory, device memory, audio, tactile, alert, notification, transmittal to other device, and instructional (block 1718).
Referring to
Examples of back and forth transferability may involve replacing a thumbnail representation on a capture/access device with high resolution quality photographs retrieved from the separate storage facility. Another example may involve replacing an entire collection of recent photographs held in local memory of a user's capture/access device that are organized by a “date categorization” scheme with topical thumbnails organized by topics that are pertinent to a currently active project. As part of the replacement, the remaining non-topical recent photos may be transferred to the remote storage location for safekeeping and future accessibility.
Another possible example may involve prefetching from the separate storage facility previously archived high quality resolution images in anticipation of an upcoming event. A further example may involve using an external unit such as a mobile telephone to select certain individual or collective archived image data in remote archived storage, and initiate a redirection (e.g., distribution) of an enhanced transformed high quality resolution version that is matched to a high quality capability external unit of an approved recipient.
It will be understood by those skilled in the art that the various components and elements disclosed in the block diagrams herein as well as the various steps and sub-steps disclosed in the flow charts herein may be incorporated together in different claimed combinations in order to enhance possible benefits and advantages.
The exemplary system, apparatus, and computer program product embodiments disclosed herein including
Those skilled in the art will also recognize that the various aspects of the embodiments for methods, processes, apparatus and systems as described herein can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof.
It will be understood that variations may be incorporated in the methods, systems and program products disclosed herein for determining what data to transfer to the separate storage location, and what data to be retained by the capture device. Some predetermined guidelines or real-time decisions may be employed to determine how and whether to organize and reorganize the transferred data as well as how and whether to organize and reorganize the retained data. Possible factors may include rule guidelines, user input, context at the capture (e.g., transferring) device and/or at the separate storage location. Other types of factors may include space, bandwidth, device capabilities, accessibility of remote storage, cost task, preferences, etc.
It will be further understood that a possible return transfer (e.g., retrieval, etc.) from the separate storage location back to the capture device or other designated device (e.g., another device being used by an authorized user or other authorized third party) may depend on various factors such as freed-up or added device storage, bandwidth opportunities, tasks, context, etc.
Various computer program product embodiments and process components may include allowing accessibility to the selected captured data by an authorized party, as well as accessibility to the selected captured data by a designated device. Other possible features may include storage media or communication media for encoding process instructions.
It will be understood from the illustrative examples herein that a technique as disclosed herein processes captured data on a device, wherein selected captured data of a given quality resolution is transferred via a communication link to a separate storage location for future availability. A storage protocol may include different storage organization categories. A possible aspect includes an identifier record to enable future accessibility to selected captured data by one or more authorized parties or approved devices or authorized recipients.
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 versus 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 may 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 a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly 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 may be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of implementations will require optically-oriented hardware, software, and or firmware.
The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flow diagrams, operation diagrams, flowcharts, illustrations, and/or examples. Insofar as such block diagrams, operation diagrams, flowcharts, illustrations, 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, operation diagrams, flowcharts, illustrations, 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).
It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). 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 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 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.).
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,” or “operably coupled,” to each other to achieve the desired functionality. 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.
As a further definition of “open” terms in the present specification and claims, it will be understood that usage of a language construction “A or B” is generally interpreted as a non-exclusive “open term” meaning: A alone, B alone, A and B together.
While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
The present application is related to and claims the benefit of the earliest available effective filing date(s) from the following listed application(s) (the “Related Applications”) (e.g., claims earliest available priority dates for other than provisional patent applications or claims benefits under 35 USC § 119(e) for provisional patent applications, for any and all parent, grandparent, great-grandparent, etc. applications of the Related Application(s)). For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled ESTIMATING SHARED IMAGE DEVICE OPERATIONAL CAPABILITIES OR RESOURCES, naming Edward K. Y. Jung, Royce A. Levien, Robert W. Lord, Mark A. Malamud, and John D. Rinaldo, Jr. as inventors, filed Jun. 2, 2005, Ser. No. 11/143,970, which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date; For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled SHARED IMAGE DEVICE DESIGNATION, naming Edward K. Y. Jung, Royce A. Levien, Robert W. Lord, Mark A. Malamud, and John D. Rinaldo, Jr. as inventors, filed Jul. 26, 2005, Ser. No. 11/190,516, which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date; For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled SAVED-IMAGE MANAGEMENT, naming Royce A. Levien, Robert W. Lord, and Mark A. Malamud, as inventors, filed Oct. 31, 2005, Ser. No. 11/263,587, which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled CONDITIONAL ALTERATION OF A SAVED IMAGE, naming Royce A. Levien, Robert W. Lord, and Mark A. Malamud, as inventors, filed Nov. 1, 2005, Ser. No. 11/264,701 which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled DATA MANAGEMENT OF A DATA STREAM, naming Edward K.Y. Jung, Royce A. Levien, Robert W. Lord, Mark A. Malamud, and John D. Rinaldo, Jr. as inventors, filed Mar. 15, 2006, Ser. No. 11/376,627 which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled STORAGE ACCESS TECHNIQUE FOR CAPTURED DATA, naming Royce A. Levien, Robert W. Lord, and Mark A. Malamud as inventors, filed Apr. 3, 2006, Ser. No. 11/397,357 which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of United States patent application entitled THIRD PARTY STORAGE OF CAPTURED DATA, naming Royce A. Levien, Robert W. Lord, and Mark A. Malamud as inventors, filed Apr. 13, 2006, Ser. No. 11/404,104, which is currently co-pending, or is an application of which a currently co-pending application listed as a Related Application is entitled to the benefit of the filing date. All subject matter of the Related Applications and of any and all parent, grandparent, great-grandparent, etc. applications of the Related Applications is incorporated herein by reference to the extent such subject matter is not inconsistent herewith.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4124871 | Morrin, II | Nov 1978 | A |
| 4249218 | Davis et al. | Feb 1981 | A |
| 4763146 | Niikura | Aug 1988 | A |
| 4788565 | Masuda et al. | Nov 1988 | A |
| 4829384 | Iida et al. | May 1989 | A |
| 4862280 | Iida et al. | Aug 1989 | A |
| 5001504 | Okada | Mar 1991 | A |
| 5034759 | Watson | Jul 1991 | A |
| 5150215 | Shi | Sep 1992 | 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 |
| 5444476 | Conway | Aug 1995 | A |
| 5467288 | Fasciano et al. | Nov 1995 | A |
| 5485553 | Kovalick et al. | Jan 1996 | A |
| 5485554 | Lowitz et al. | Jan 1996 | A |
| 5493353 | Chen | Feb 1996 | 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 |
| 5738522 | Sussholz et al. | Apr 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 |
| 5809161 | Auty et al. | Sep 1998 | A |
| 5825506 | Bednar et al. | Oct 1998 | A |
| 5852753 | Lo et al. | Dec 1998 | A |
| 5867614 | Ito | Feb 1999 | A |
| 5889895 | Wong et al. | Mar 1999 | A |
| 5892509 | Jakobs et al. | Apr 1999 | A |
| 5915135 | Fiorentini | Jun 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 |
| 6011901 | Kirsten | Jan 2000 | A |
| 6021403 | Horvitz et al. | Feb 2000 | A |
| 6028585 | Ishii et al. | Feb 2000 | A |
| 6034786 | Kwon | Mar 2000 | A |
| 6046762 | Sonesh et al. | Apr 2000 | A |
| 6107918 | Klein et al. | Aug 2000 | A |
| 6115341 | Hirai | Sep 2000 | A |
| 6122003 | Anderson | Sep 2000 | A |
| 6122411 | Shen et al. | Sep 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 |
| 6198526 | Ohtsuka | Mar 2001 | B1 |
| 6222465 | Kumar et al. | Apr 2001 | B1 |
| 6229565 | Bobry | May 2001 | B1 |
| 6229850 | Linzer et al. | May 2001 | B1 |
| 6275260 | Anderson | Aug 2001 | B1 |
| 6282377 | Lawther et al. | Aug 2001 | B1 |
| 6285794 | Georgiev et al. | Sep 2001 | B1 |
| 6332666 | Ikeda | Dec 2001 | B1 |
| 6333792 | Kimura | Dec 2001 | B1 |
| 6351762 | Ludwig et al. | Feb 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 |
| 6411742 | Peterson | Jun 2002 | B1 |
| 6434398 | Inselberg | Aug 2002 | B1 |
| 6437797 | Ota | Aug 2002 | B1 |
| 6445822 | Crill et al. | Sep 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 |
| 6476858 | Ramirez Diaz et al. | Nov 2002 | B1 |
| 6493028 | Anderson et al. | Dec 2002 | B1 |
| 6499016 | Anderson | Dec 2002 | B1 |
| 6509931 | Mizosoe et al. | Jan 2003 | B1 |
| 6512541 | Dunton et al. | Jan 2003 | B2 |
| 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 |
| 6539169 | Tsubaki et al. | Mar 2003 | B1 |
| 6542183 | DeAngelis et al. | Apr 2003 | B1 |
| 6546189 | Koda | Apr 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 |
| 6587602 | Wakisawa et al. | Jul 2003 | B2 |
| 6611293 | Tarnoff et al. | Aug 2003 | B2 |
| 6629104 | Parulski et al. | Sep 2003 | B1 |
| 6633309 | Lau et al. | Oct 2003 | B2 |
| 6646676 | DaGraca et al. | Nov 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 |
| 6701845 | Ohmura | Mar 2004 | B2 |
| 6710809 | Niikawa | Mar 2004 | B1 |
| 6714192 | Torres | Mar 2004 | B1 |
| 6734911 | Lyons | May 2004 | B1 |
| 6735253 | Chang et al. | May 2004 | B1 |
| 6738155 | Rosenlund 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 |
| 6757480 | Moon et al. | Jun 2004 | B1 |
| 6757684 | Svendsen et al. | Jun 2004 | B2 |
| 6762791 | Schuetzle | Jul 2004 | B1 |
| 6766036 | Pryor | Jul 2004 | B1 |
| 6775406 | Watson | Aug 2004 | B1 |
| 6801717 | Hofer | Oct 2004 | B1 |
| 6801719 | Szajewski et al. | 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 |
| 6871010 | Taguchi et al. | Mar 2005 | B1 |
| 6879731 | Kang et al. | Apr 2005 | B2 |
| 6885395 | Rabbani et al. | Apr 2005 | B1 |
| 6898173 | McPherson et al. | May 2005 | B2 |
| 6903763 | Noguchi et al. | Jun 2005 | B1 |
| 6928230 | Squibbs | Aug 2005 | B2 |
| 6930707 | Bates et al. | Aug 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 |
| 6967780 | Hillis et al. | Nov 2005 | B2 |
| 6978047 | Montgomery | Dec 2005 | B2 |
| 6987528 | Nagahisa et al. | Jan 2006 | B1 |
| 6999626 | Andrew | Feb 2006 | B2 |
| 7015949 | Sah | Mar 2006 | B1 |
| 7015954 | Foote et al. | Mar 2006 | B1 |
| 7023469 | Olson | Apr 2006 | B1 |
| 7031700 | Weaver et al. | Apr 2006 | B1 |
| 7046273 | Suzuki | May 2006 | B2 |
| 7046292 | Ziemkowski | May 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 |
| 7163151 | Kiiskinen | Jan 2007 | B2 |
| 7196317 | Meissner, II et al. | Mar 2007 | B1 |
| 7203648 | Ostermann et al. | Apr 2007 | B1 |
| 7218792 | Raskar et al. | May 2007 | B2 |
| 7219365 | Sato et al. | May 2007 | B2 |
| 7221863 | Kondo et al. | May 2007 | B2 |
| 7227569 | Maruya | Jun 2007 | B2 |
| 7236690 | Matsukawa | Jun 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 |
| 7383508 | Toyama et al. | Jun 2008 | B2 |
| 7411623 | Shibutani | Aug 2008 | B2 |
| 7417667 | Shibutani | Aug 2008 | B2 |
| 7444593 | Reid | Oct 2008 | B1 |
| 7448063 | Freeman et al. | Nov 2008 | B2 |
| 7460495 | Li | Dec 2008 | B2 |
| 7460781 | Kanai et al. | Dec 2008 | B2 |
| 7504942 | Marman | Mar 2009 | B2 |
| 7525568 | Raghunath | Apr 2009 | B2 |
| 7529411 | Haupt et al. | May 2009 | B2 |
| 7535491 | Kumagai et al. | May 2009 | B1 |
| 7551787 | Marks | Jun 2009 | B2 |
| 7576770 | Metzger et al. | Aug 2009 | B2 |
| 7587674 | Broeksteeg | Sep 2009 | B2 |
| 7612804 | Marcu et al. | Nov 2009 | B1 |
| 7612806 | Kazami et al. | Nov 2009 | B2 |
| 7626614 | Marcu | Dec 2009 | B1 |
| 7626733 | Kodama et al. | Dec 2009 | B2 |
| 7647614 | Krikorian et al. | Jan 2010 | B2 |
| 7650058 | Garoutte | Jan 2010 | B1 |
| 7733371 | Monroe | Jun 2010 | B1 |
| 7751628 | Reisman | Jul 2010 | B1 |
| 7782365 | Levien et al. | Aug 2010 | B2 |
| 7860319 | Obrador et al. | Dec 2010 | B2 |
| 7872675 | Levien et al. | Jan 2011 | B2 |
| 7904814 | Errico et al. | Mar 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 |
| 8528019 | Dimitrova et al. | Sep 2013 | B1 |
| 8593555 | Chun et al. | Nov 2013 | B1 |
| 20010015756 | Wilcock et al. | 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 |
| 20010033333 | Suzuki et al. | Oct 2001 | A1 |
| 20010042043 | Shear et al. | Nov 2001 | A1 |
| 20010046199 | McPherson et al. | Nov 2001 | A1 |
| 20010050875 | Kahn et al. | Dec 2001 | A1 |
| 20020012071 | Sun | Jan 2002 | A1 |
| 20020015094 | Kuwano et al. | Feb 2002 | A1 |
| 20020028026 | Chen et al. | Mar 2002 | A1 |
| 20020028060 | Murata et al. | Mar 2002 | A1 |
| 20020030749 | Nakamura et al. | Mar 2002 | A1 |
| 20020054232 | Inagaki | May 2002 | A1 |
| 20020069036 | Mizokawa | Jun 2002 | A1 |
| 20020090217 | Limor et al. | Jul 2002 | A1 |
| 20020145622 | Kauffman et al. | Oct 2002 | A1 |
| 20020149677 | Wright | 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 |
| 20020191952 | Fiore et al. | Dec 2002 | A1 |
| 20020196344 | McIntyre et al. | Dec 2002 | A1 |
| 20020197067 | Ohnishi | Dec 2002 | A1 |
| 20030007078 | Feldis, III | Jan 2003 | A1 |
| 20030018802 | Romanik et al. | Jan 2003 | A1 |
| 20030020814 | Ono | Jan 2003 | A1 |
| 20030021455 | Dixon et al. | Jan 2003 | A1 |
| 20030021591 | Grosvenor et al. | Jan 2003 | A1 |
| 20030026596 | Betti et al. | Feb 2003 | A1 |
| 20030037111 | Yoshioka | Feb 2003 | A1 |
| 20030058265 | Robinson et al. | Mar 2003 | A1 |
| 20030063114 | Nishida | Apr 2003 | A1 |
| 20030063211 | Watanabe et al. | Apr 2003 | A1 |
| 20030069898 | Christodoulou et al. | Apr 2003 | A1 |
| 20030070174 | Solomon | Apr 2003 | A1 |
| 20030072491 | Sirivara et al. | Apr 2003 | A1 |
| 20030080878 | Kirmuss | May 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 |
| 20030103670 | Schoelkopf et al. | Jun 2003 | A1 |
| 20030112261 | Zhang | Jun 2003 | A1 |
| 20030112354 | Ortiz et al. | Jun 2003 | A1 |
| 20030113014 | Katoh | Jun 2003 | A1 |
| 20030117505 | Sasaki et al. | Jun 2003 | A1 |
| 20030117642 | Haraguchi | Jun 2003 | A1 |
| 20030131002 | Gennetten et al. | 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 |
| 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 |
| 20030227560 | Mattsson et al. | Dec 2003 | A1 |
| 20030229894 | Okada et al. | Dec 2003 | A1 |
| 20030234953 | Dawson et al. | Dec 2003 | A1 |
| 20030236674 | Henry, Jr. | Dec 2003 | A1 |
| 20030236831 | Ortiz et al. | Dec 2003 | A1 |
| 20030236832 | McIntyre et al. | Dec 2003 | A1 |
| 20040001145 | Abbate | Jan 2004 | A1 |
| 20040001161 | Herley | Jan 2004 | A1 |
| 20040017333 | Cooper et al. | Jan 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 |
| 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 |
| 20040080537 | Adler | Apr 2004 | A1 |
| 20040085456 | Kwag et al. | May 2004 | A1 |
| 20040095474 | Matsufune | May 2004 | A1 |
| 20040108995 | Hoshino et al. | 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 |
| 20040160453 | Horton et al. | Aug 2004 | A1 |
| 20040166930 | Beaulieu et al. | Aug 2004 | A1 |
| 20040172440 | Nakajima et al. | Sep 2004 | A1 |
| 20040174434 | Walker et al. | Sep 2004 | A1 |
| 20040174454 | Okamura | Sep 2004 | A1 |
| 20040179121 | Silverstein | Sep 2004 | A1 |
| 20040179545 | Erola et al. | Sep 2004 | A1 |
| 20040183903 | Pedersen | Sep 2004 | A1 |
| 20040183915 | Gotohda | Sep 2004 | A1 |
| 20040187583 | Ogawa | Sep 2004 | A1 |
| 20040189856 | Tanaka | Sep 2004 | A1 |
| 20040196399 | Stavely | Oct 2004 | A1 |
| 20040201683 | Murashita et al. | Oct 2004 | A1 |
| 20040201690 | Bryant et al. | Oct 2004 | A1 |
| 20040201709 | McIntyre et al. | Oct 2004 | A1 |
| 20040201748 | Goldstein et al. | Oct 2004 | A1 |
| 20040216173 | Horoszowski et al. | Oct 2004 | A1 |
| 20040218894 | Harville et al. | Nov 2004 | A1 |
| 20040221063 | Mogul | 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 |
| 20040257462 | Goris et al. | Dec 2004 | A1 |
| 20040263609 | Otsuki et al. | Dec 2004 | A1 |
| 20040263658 | Cozier et al. | Dec 2004 | A1 |
| 20050005308 | Logan et al. | Jan 2005 | A1 |
| 20050007471 | Walmsley et al. | Jan 2005 | A1 |
| 20050010531 | Kushalnagar et al. | Jan 2005 | A1 |
| 20050013602 | Ogawa | Jan 2005 | A1 |
| 20050017947 | Shahoian et al. | Jan 2005 | A1 |
| 20050018053 | Suga et al. | Jan 2005 | A1 |
| 20050028221 | Liu et al. | Feb 2005 | A1 |
| 20050033991 | Crane | Feb 2005 | A1 |
| 20050036033 | Imai | Feb 2005 | A1 |
| 20050046707 | Takane | Mar 2005 | A1 |
| 20050047676 | Kang et al. | Mar 2005 | A1 |
| 20050050043 | Pyhalammi et al. | Mar 2005 | A1 |
| 20050057687 | Irani et al. | Mar 2005 | A1 |
| 20050058321 | Buehler | Mar 2005 | A1 |
| 20050084037 | Liang | 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 |
| 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 |
| 20050140803 | Ohtsuka et al. | Jun 2005 | A1 |
| 20050150362 | Uehara | Jul 2005 | A1 |
| 20050158015 | Nakayama et al. | Jul 2005 | A1 |
| 20050162533 | Noguchi et al. | Jul 2005 | A1 |
| 20050162965 | Fukuda et al. | Jul 2005 | A1 |
| 20050169367 | Venetianer et al. | Aug 2005 | A1 |
| 20050185062 | Hillis et al. | Aug 2005 | A1 |
| 20050187901 | Maritzen et al. | Aug 2005 | A1 |
| 20050193421 | Cragun | Sep 2005 | A1 |
| 20050195285 | Ide | Sep 2005 | A1 |
| 20050203930 | Bukowski et al. | Sep 2005 | A1 |
| 20050207487 | Monroe | 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 |
| 20050243176 | Wu et al. | Nov 2005 | A1 |
| 20050262097 | Sim-Tang et al. | Nov 2005 | A1 |
| 20050271251 | Russell et al. | Dec 2005 | A1 |
| 20050275747 | Nayar et al. | Dec 2005 | A1 |
| 20060008254 | Seo | Jan 2006 | A1 |
| 20060023066 | Li et al. | Feb 2006 | A1 |
| 20060034533 | Batchvarov | Feb 2006 | A1 |
| 20060044398 | Foong et al. | Mar 2006 | A1 |
| 20060044416 | Miyazaki et al. | Mar 2006 | A1 |
| 20060048057 | Herberger et al. | Mar 2006 | A1 |
| 20060050785 | Watanabe et al. | Mar 2006 | A1 |
| 20060055788 | Kawabe | Mar 2006 | A1 |
| 20060056326 | Croome | Mar 2006 | A1 |
| 20060068824 | Inselberg | Mar 2006 | A1 |
| 20060072028 | Hong | Apr 2006 | A1 |
| 20060072837 | Ralston et al. | Apr 2006 | A1 |
| 20060083298 | Wang et al. | Apr 2006 | A1 |
| 20060083440 | Chen | Apr 2006 | A1 |
| 20060085534 | Ralston et al. | Apr 2006 | A1 |
| 20060087559 | Huberman et al. | 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 |
| 20060119711 | Ejima et al. | Jun 2006 | A1 |
| 20060125922 | Albert et al. | Jun 2006 | A1 |
| 20060136998 | Oowaki et al. | Jun 2006 | A1 |
| 20060143665 | Meek et al. | Jun 2006 | A1 |
| 20060173756 | Benight | Aug 2006 | A1 |
| 20060173972 | 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 |
| 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 |
| 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 |
| 20070100860 | Jung et al. | May 2007 | A1 |
| 20070113250 | Logan et al. | May 2007 | A1 |
| 20070120980 | Jung et al. | May 2007 | A1 |
| 20070217761 | Chen et al. | Sep 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 |
| 20080162668 | Miller | Jul 2008 | A1 |
| 20080192129 | Walker et al. | Aug 2008 | A1 |
| 20080228296 | Eilam et al. | Sep 2008 | A1 |
| 20080298796 | Kuberka et al. | Dec 2008 | A1 |
| 20080303909 | Watanabe et al. | Dec 2008 | A1 |
| 20090215388 | Karaoguz et al. | Aug 2009 | A1 |
| 20100017289 | Sah et al. | Jan 2010 | A1 |
| 20110270916 | Shih et al. | Nov 2011 | A1 |
| 20120105716 | Jung et al. | May 2012 | A1 |
| 20130176341 | Jung et al. | Jul 2013 | A1 |
| 20140146205 | Xu et al. | May 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 0940711 | Nov 2003 | EP |
| 5064225 | Mar 1993 | JP |
| H09-018762 | Jan 1997 | JP |
| 10023303 | Jan 1998 | 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 |
| WO 2005045807 | May 2005 | WO |
| WO 2005078597 | Aug 2005 | WO |
| WO 2005112437 | Nov 2005 | WO |
| Entry |
|---|
| U.S. Appl. No. 11/703,063, Jung et al. |
| U.S. Appl. No. 11/702,034, Jung et al. |
| U.S. Appl. No. 11/655,734, Jung et al. |
| U.S. Appl. No. 11/640,836, Levien et al. |
| U.S. Appl. No. 11/594,695, Levien et al. |
| U.S. Appl. No. 11/591,435, Jung et al. |
| U.S. Appl. No. 11/541,382, Jung et al. |
| U.S. Appl. No. 11/526,886, Jung et al. |
| U.S. Appl. No. 11/510,319, Jung et al. |
| U.S. Appl. No. 11/508,554, Jung et al. |
| U.S. Appl. No. 11/506,760, Jung et al. |
| U.S. Appl. No. 11/475,516, Levien et al. |
| U.S. Appl. No. 11/455,001, Jung et al. |
| U.S. Appl. No. 11/441,785, Jung et al. |
| U.S. Appl. No. 11/440,409, Levien et al. |
| U.S. Appl. No. 11/437,284, Levien et al. |
| U.S. Appl. No. 11/434,568, Jung et al. |
| U.S. Appl. No. 11/413,271, Jung et al. |
| U.S. Appl. No. 11/404,104, Levien et al. |
| U.S. Appl. No. 11/396,279, Jung et al. |
| U.S. Appl. No. 11/364,496, 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/173,166, Jung et al. |
| U.S. Appl. No. 11/153,868, 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/095,768, Jung et al. |
| U.S. Appl. No. 11/089,530, Jung et al. |
| U.S. Appl. No. 11/069,909, Jung et al. |
| U.S. Appl. No. 11/064,787, Jung et al. |
| U.S. Appl. No. 11/048,644, Jung et al. |
| U.S. Appl. No. 11/048,629, Jung et al. |
| Colbert, Martin; Voglimacci, Catherine; Finkelstein, Anthony; “Live, Audio-Visual Communication Systems for Distance Learning: Experience, Heuristics and ISDN”; pp. 1-40. |
| Cummins, Fred; “Synchronization Among Speakers Reduces Macroscopic Temporal Variability”; pp. 1-6. |
| Dodd, George; “Music Performance Venues-keeping them in tune with modern requirements”; pp. 1-11. |
| El Saddik, Abdulmotaleb DR.; “Multimedia Communications: Multimedia Technologies & Applications”; Multimedia Communications Research Laboratory, School of Information Technology and Engineering, University of Ottawa, Ottawa, Ontario, Canada; 22 slides; pp. 1-8. |
| 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. |
| Seifert, Eric; Eligator, Ron; “Acoustical Design Considerations at Universal Studios CityWalk™, Orlando, Florida”; Acoustics at CityWalk; pp. 1-5; located at http://www.acousticdimensions.com/tech_CityWalk.htm; bearing dates of Apr. 23, 1999 and Apr. 24, 1999; printed on Jul. 20, 2005. |
| “SOUNDaround: Get cinema quality surround sound through two speakers”; RAM: SOUNDaround by Xitel; pp. 1-7; located at http://www.ramelectronics.net/html/soundaround.html; printed on Jul. 20, 2005. |
| “Yamaha Internet ‘MidLive vol. 3’: An Open Experiment: The First MidLive to Feature Synchronized Streaming of MIDI and Audio Data”; Yamaha News Release: wMid Live vol. 3x; pp. 1-5; located at http://www.yamaha.co.jp/english/news/97121101.html; bearing a date of Dec. 1997; printed on Jul. 19, 2005. |
| 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. 17, 2005. |
| Cisco Systems, Inc.; “Cisco Catalyst 6500 Series Switches—High Availability for the Cisco Catalyst 6500 Series Switches”; pp. 1-9; located at http://www.cisco.com/en/US/products/hw/switches/ps708/products_white_paper09186a0080088874.shtml; bearing a date of 1992-2005; printed on May 3, 2005. |
| co-array.org; “A Brief Overview of Co-Array Fortran”; pp. 1-3; located at http://www.co-array.org/caf_intro.htm; printed on May 3, 2005. |
| Dave; “How Many Pixels? A reasoned approach to digicam specifications”; pp. 1-5; located at http://www.imaging-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/olytest/resample.html; printed on Feb. 16, 2005. |
| gizmodo.com; “FlashPoint ShareDrives”; pp. 1-2 located at http://www.gizmodo.com/gadgets/peripherals/storage/flashpoint-sharedrives-110083.php; bearing a date of Mon Jun. 27; printed on Jun. 29, 2005; Published by Gawker Media. |
| Har-Peled, Sariel; Koltun, Vladlen; Song; Dezhen; Goldberg, Ken; CiteSeer.1st:; “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. |
| Hernandez, J.R.; Perez-Gonzalez, F.; Rodriguez, J.M.; “Coding and Synchronization: A Boost and a Bottleneck for the Development of Image Watermarking”; pp. 1-7; Dept. Tecnologias de las Communicaciones, ETSI Telecom., Universidad de Vigo, 36200 Vigo, Spain. |
| Hewlett-Packard Development Company, L.P.; “Presenting the big picture”; pp. 1-7; located at http://www.matrixdisplay.com/pdf/HP_Big_Picture_Main_Brochure.pdf; bearing a date of 2003. |
| 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-4l 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/170A.HTM; bearing a date of 2001; printed on Feb. 16, 2005. |
| Intel.com; “Instantly Capture and Share your World with an Intel® PC Camera”; pp. 1-2; located at http://www.intel.com/pccamera/; printed on Jan. 27, 2005. |
| Jain, Anil K.; “Fundamentals of Digital Image Processing”; 1989; pp. 1-569; Prentice-Hall, Inc.; Englewood Cliffs, NJ U.S.A. |
| 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. 3, 2005. |
| LTL Imagery; “About Resolution Understanding Digital Image Resolution”; pp. 1-10; located at http://www.itlimagery.com/resolution.html; bearing a date of 2000-2004; printed on Feb. 16, 2005. |
| Mahmoud, Qusay H.; “Getting Started with Data Synchronization Using SyncML”; pp. 1-6; located at http://developers.sun.com/techtopics/mobility/midp/articles/syncm1/; bearing dates of Sep. 2004 and 1994-2005; printed on May 3, 2005. |
| Mobilemag; “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. |
| Cnnmoney; “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. |
| National Instruments Corporation; “Advanced Analog Triggering and Synchronization Techniques”; pp. 1-2; located at http://zone.ni.com/devzone/conceptd.nsf/webmain/A387B5C0AC6F6F4E86256C87005FCDDF?opendocument&node=dz00000_us; bearing a date of 2005; printed on May 3, 2005. |
| National Instruments Corporation; “Genlocking Multiple JAI CV-MI Cameras”; pp. 1-5; located at http://zone.ni.com/devzone/conceptd.nsf/webmain/7a6b5853548850e886256c21005b1413; bearing a date of 2005; printed on May 3, 2005. |
| National Instruments Corporation; “Multi-Camera Acquisition”; pp. 1-3; located at http://zone.ni.com/devzone/conceptd.nsf/webmain/D91BAC1317F9D0A686256C9300769A0D; bearing a date of 2005; printed on May 3, 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. |
| roadcasting.org; “A new type of radio”; “Final Design”; “Process”; “Conclusions”; “Recognition”; “How Roadcasting Works”; “Download”; pp. 1-15; located at www.roadcasting.org; printed on Jun. 2, 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.weblogsinc.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?tvpe=technical+report&id=823 bearing a date of Nov. 2004; printed on Jan. 25, 2005. |
| starbursthomepage.com; “Life is all about Sharing”; p. 1; located at http://www.starbursthomepage.com/flashpointx.htm; printed on Jun. 29, 2005. |
| starbursthomepage.com; “Sharing-On-The-Go Technology”; pp. 1-3; located at http://www.starbursthomepage.com/fsotg.htm; printed on Jun. 29, 2005. |
| starbursthomepage.com; “Specifications and Data Transfer Information”; pp. 1-5; located at http://www.starbursthomepage.com/fspec.htm; printed on Jun. 29, 2005. |
| starbursthomepage.com; “What are FlashPoint ShareDrives”; pp. 1-4; located at http://www.starbursthomepage.com/fproducts.htm; printed on Jun. 29, 2005. |
| Sutherland, Ed; “CSR Intros Low-Cost, Single-Chip WiFi”; pp. 1-3; located at http://www.wi-fiplante.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/290,538, Jung et al. |
| U.S. Appl. No. 12/284,202, Jung et al. |
| U.S. Appl. No. 12/283,420, Jung et al. |
| “About Flickr”; bearing a date of 2006; pp. 1-2; located at http://www.flickr.com/about/. |
| “About the SD Memory Card”; bearing a date of 2004; pp. 1-3; located at http://www.sdcard.org/sd_memorycard/index.html; SD Card Association; printed on Mar. 7, 2006. |
| “Auto Exposure Bracketing (AEB Mode)”; PowerShot G3 Digital Camera; bearing a date of 2004; pp. 1-4; located at http://web.canon.jp/Imaging/PSG3/PSG3_129-3.html; Canon Inc., printed on Sep. 7, 2006. |
| Darlin, Damon; “Why Do-It-Yourself Photo Printing Doesn't Add Up”; bearing a date of Oct. 8, 2005; pp. 1-3; located at http://www.nytimes.com/2005/10/08/technology08photo.ready.html; The New York Times; printed on Aug. 28, 2006. |
| “Digital Cameras Glossary”, pp. 1-3; located at http://www.crutchfieldadvisor.com/ISEO-rgbtcspd/learningcenter/home/digitalcameras_glossary.html; printed on Mar. 8, 2006. |
| “Digital Cameras: How to Choose”, pp. 1-3; located at http://www.crutchfieldadvisor.com/ISEO-rgbtcspd/learningcenter/home/digitalcameras.html; printed on Mar. 8, 2006. |
| “Fujifilm Summus Collaborate to Provide Wireless Photo Services”; bearing a date of Feb. 18, 2004; pp. 1-2; located at http://phx.corporate-ir.net/phoenix.zhtml?c=131111&p=irol-newsArticle&ID=807972&highlight=; Oasys Mobile, Inc.; printed on Mar. 17, 2006. |
| “JVC Everio GZMG77 2.0MP CCD 30GB HDD Camcorder with 10x Optical Zoom”; bearing a date of 1996-2006; pp. 1-8; located at http://www.amazon.com/gp/product/B000E1332W/ref=pd_cp_title/103-4351641-1963832; Amazon.com; printed on Apr. 25, 2006. |
| Kim, Jeong; Zimmerman, John; “Cherish: Smart Digital Photo Frames for Sharing Social Narratives at Home”; bearing a date of Apr. 22-28, 2006; pp. 1-6; located at http://www.cs.cmu.edu/˜johnz/pubs/2006_CHI_cherish.pdf#search=%22cherish%3B%20smart%20digital%20photo%20frames%20for%20sharing%20social%20narratives%20at%20home%22. |
| “Kodak's dual-lens camera”; bearing a date of Jan. 2, 2006; pp. 1; located at http://news.com/2300.com/2300-1041_3-6014914-2.htnl?ne.gall.pg; c/net news.com; printed on Mar. 7, 2006. |
| “Kodak Unveils Worlds First Dual-Lens Digital Camera; Combines Ultra-Wide Angle and Zoom Lenses in Compact Body”; bearing a date of Jan. 2, 2006; pp. 1-2; Kodak; located at: http://www.kodak.com/cknee/PageQuerierjhtml?pg-path=2709&pg-locale=en_US&gpcid=0900688a80465805; printed on Mar. 7, 2006. |
| “Leading Edge Eyecam Extreme High Resolution Wireless Color Video Camera System”; pp. 1-2; located at: http://parts.rctoys.com/rc-toys-hobbies/Items/329769%20-%20(S); Draganfly Parts Warehouse; printed on Mar. 9, 2006. |
| Lyons, Max; “Max Lyons Digital Image Gallery”; bearing a date of 2000-2005; pp. 1-3; located at http://www.tawbaware.com/maxlyons/; printed on Apr. 18, 2006. |
| Mills, Elinor; “HD camera, new monitor attract crowds”; bearing a date of 1995-2006; pp. 1; located at http://news.com.com/2102-7353_3-6023300.html?tag=st.util.print; c/net news.com; printed on Mar. 7, 2006. |
| “Multiple Camera Acquisition”; bearing a date of 2006; pp. 1; located at http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E80B56A4E034080020E74861&p_node=DZ52489&p_source=external; National Instruments Corporation; printed on Aug. 29, 2006. |
| “New High Capacity SD Memory Card Specification Under Final Review by SD Card Association”; bearing a date of Jan. 4, 2006; pp. 1-2; SD Card Association News Release. |
| Ng et al.; “Light Field Photography with a Hand-Held Plenoptic Camera”; bearing dates of 2004-2005; pp. 1-3; located at http://graphics.stanford.edu/papers/Ifcamera/; printed on Sep. 7, 2006. |
| Nicholls, Kyle; “Non-photorealistic Camera—Depth Edge Detection and Rendering using Muli-Flash Imaging”; bearing dates of 2000-2006; pp. 1-3; located at http://photo.net/learn/technology/mflash/merl-non-photo.html; printed on Apr. 18, 2006. |
| “OkIP Video. . . Anywhere Solar Powered! Protecting Critical Government Infrastructure Military and Homeland Surveillance”; pp. 1-8; located at http://www.oksolar.com/ip_anywhere/; printed on Mar. 9, 2006. |
| Raymond, Emily; “Kodak Digital Cameras: Kodak EasyShare V570 Digital Camera Review”; pp. 1-2; bearing a date of Jan. 22, 2006; located at http://www.digitalcamerainfo.com/content/Kodak-EasyShare-V570; printed on Apr. 19, 2006. |
| Reichmann, Mchael; “Understanding Raw Files”; Luminous-landscape.com; pp. 1-9; located at http://www.luminous-landscape.com/tutorials/understanding-series/u-raw-files.shtml; printed on Oct. 25, 2005. |
| “Sanyo Xacti VPC-HDI 5.1MP MPEG4 High Definition Camcorder x/10x Optical Zoom: Product Description”; bearing dates of 1996-2006; pp. 1-5; located at: http://www.amazon.com/gp/product/product-description/B000E0E6YC/ref=dp_nav_2/002-0210595-1654445?%5Fencoding=UTF8&n=502394&s=photo; Amazon.com; printed on Mar. 7, 2006. |
| “Secure Digital Card”; Wikipedia, pp. 1-6; located at http://en.wikipedia.org/wiki/Secure_Digital; Wikipedia; printed on Mar. 7, 2006. |
| Skillings, Jonathan; “Kodak packs two lenses in latest camera”; bearing a date of Feb. 7, 2006; pp. 1; located at http://news.com.com/2102-1041_3-6014939.html?tag=st.util.print; c/net news.com; printed on Mar. 7, 2006. |
| “Sony DCR-DVD405 3MP DVD Handycam Camcorder with 10x Optical Zoom”; pp. 1-12; Amazon.com; located at: http://www.amazon.com/gp/product/B000E0DU7G/ref=pd_cp_title/103-4351641-196383; printed on Apr. 25, 2006. |
| “storage device-A Word Definition From the Webopedia Computer Dictionary”; bearing dates of Oct. 30, 2001 and 2005; pp. 1-4; located at http://www.webopedia.com/TERMS/storage_device.htm; Webopedia.com; printed on Oct. 25, 2005. |
| “VisualStream: Digital Multimedia USB 1.1 High Resolution PC Camera”; bearing a date of 2002; pp. 1-4; D-Link Systems, Inc.; Irvine, CA. |
| “What is Flickr?”; bearing a date of 2006; pp. 1-6; located at http://www.flickr.com/learn_more.gne; printed on Aug. 28, 2006. |
| Woodrow, E.; Heinzelman, W.; “SPIN-IT: a data centric routing protocol for image retrieval in wireless networks”; bearing dates of Jun. 24-28, 2002; pp. 1-5; Image Processing 2002, Proceedings. 2002 International Conference; vol. 3; pp. 913-916; located at http://ieeexplore.ieee.org/xpl/absprintf.jsp?arnumber=1039121 %pag; printed Mar. 19, 2006. |
| “Editing & Organizing Photos” Snapfish Website; bearing a date of: Jan. 20, 2005; located at: http://web.archive.org/web/20050405222248/www.snapfish.com/helpediting; pp. 1-8; printed on Apr. 22, 2010. |
| “Snapfish Privacy Policy”; Snapfish Website; bearing a date of: Jan. 20, 2005; located at: http://web.arch ive.org/web/20050403221640/www.snapfish.com/privacy/t_0; pp. 1-5; printed on Apr. 22, 2010. |
| U.S. Appl. No. 12/806,060, Royce A. Levien 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. |
| Number | Date | Country | |
|---|---|---|---|
| 20060274154 A1 | Dec 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11143970 | Jun 2005 | US |
| Child | 11404381 | US | |
| Parent | 11190516 | Jul 2005 | US |
| Child | 11143970 | US | |
| Parent | 11263587 | Oct 2005 | US |
| Child | 11190516 | US | |
| Parent | 11264701 | Nov 2005 | US |
| Child | 11263587 | US | |
| Parent | 11376627 | Mar 2006 | US |
| Child | 11264701 | US | |
| Parent | 11397357 | Apr 2006 | US |
| Child | 11376627 | US | |
| Parent | 11404104 | Apr 2006 | US |
| Child | 11397357 | US |
