Transmission bandwidth and memory requirements reduction in a portable image capture device

Information

  • Patent Grant
  • 8868778
  • Patent Number
    8,868,778
  • Date Filed
    Tuesday, October 25, 2011
    13 years ago
  • Date Issued
    Tuesday, October 21, 2014
    10 years ago
Abstract
Storage and network transmission bandwidth requirements of a portable image capture device are reduced. An online service using at least one hardware server on a network provides action information for an image capture device, the action information corresponding to an action that can be performed on images by the online service. A captured image is received uploaded from the image capture device to the online service. A request is received from the image capture device to perform the action for the uploaded image. The request includes an image identifier assigned by the online service.
Description
FIELD OF THE INVENTION

The present invention relates the storage and transmission of digital images, and more particularly to a method and system for reducing transmission bandwidth and storage requirements of an image capture device.


BACKGROUND

As the popularity of digital cameras continues grow, the use of on-line photo sharing websites for storing and sharing digital images is becoming more prevalent. The most common method for getting the digital images to the photo sharing websites is to load the images from the digital camera to a personal computer (PC) and use the Internet connection on the PC to upload images to the photo site.


Today, however, hand-held electronic devices are emerging, including digital cameras that have the capability to connect directly to the Internet without the use of the PC. For example, the assignee of the present application has developed an approach to uploading images to the Web. In this approach, an e-mail software application is loaded into a digital camera capable of running software applications that allows the user to e-mail images directly from the camera. The user simply connects his or her digital camera to a cell phone or a modem, runs the e-mail application, and selects the desired images and e-mail recipients. The selected images are then sent to the e-mail recipients as attachments.


A more advanced approach is to provide the digital camera with cell phone-like functionality in which the camera establishes an Internet connection with the photo sharing website by dialing an 800 number, for example, and automatically uploads the images.


One prohibitive factor to the widespread adoption of digital imaging is cost. Digital cameras are already relatively expensive to purchase, and providing digital cameras with Internet connectivity for uploading images to the Internet will only add to the expense. And ever increasing images sizes means that digital cameras will require larger memories, further adding to the expense. What's more, consumers will have to pay for the bandwidth consumed during transmission of images to the photo-sharing site. The cost for transmitting images will be a function of the size and number of the images, the speed of the modem or wireless medium, and the cost of calling the 800 number.


One reason why digital cameras require so much transmission bandwidth is because images stored on the digital camera are oftentimes transmitted over the Internet more than once. For example, consider the example where the user wants to send selected images to ten different work groups at work and selects the same image several times. The user may chose to send images 1, 2, and 8 to group 1, images 2, 5, 8 and 9 to group 2, images 3, 4, 8, and 10 to group, and so on. As can be seen, the same image (#8) must be transmitted over the Internet several times, consuming a large amount of bandwidth.


One way to reduce the bandwidth used transmitting images from the camera is to reduce the size of the image files by using higher compression rates and/or by capturing lower resolution images. However, the digital camera industry is attempting to meet to consumer demand for digital image quality that rivals film images, which may require image sizes of at least 4-10 MB. Using higher compression rates is not viable option because higher compression rates degrade image quality, and capturing lower resolution images is the antithesis of achieving film-quality.


Accordingly, what is needed is a method and system for reducing bandwidth and storage requirements of images transmitted from a digital camera. The present invention addresses such a need.


SUMMARY

Storage and network transmission bandwidth requirements of a portable image capture device are reduced. An online service using at least one hardware server on a network provides action information for an image capture device, the action information corresponding to an action that can be performed on images by the online service. A captured image is received uploaded from the image capture device to the online service. A request is received from the image capture device to perform the action for the uploaded image. The request includes an image identifier assigned by the online service.


According to the system and method disclosed herein, reducing the image files of each of the uploaded images after image uploading frees memory space for the capture of additional images and reduces storage requirements. And transmitting only the image identifier of the image after an image is uploaded the first time eliminates the need to retransmit the image, thereby reducing transmission bandwidth requirements.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram illustrating an online photo-sharing system in accordance with a preferred embodiment of the present invention.



FIG. 2 is a diagram showing a preferred embodiment of a digital camera for use in accordance with the present invention.



FIG. 3 is a block diagram illustrating a diagram of one embodiment for an image file.



FIG. 4 is a flow chart illustrating the process for reducing storage and bandwidth requirements of the digital camera in accordance with a preferred embodiment of the present invention.



FIG. 5 is a flow chart illustrating the process for reducing storage and bandwidth requirements of the digital camera in capture mode in a preferred embodiment of the present invention.



FIG. 6 is a block diagram illustrating an example action list displayed on the LCD screen of the camera.



FIGS. 7A and 7B is a flow chart illustrating the process for reducing storage and bandwidth requirements of the digital camera in play mode.





DETAILED DESCRIPTION

The present invention relates to reducing the transmission bandwidth and storage requirements of a portable image capture device. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.


The present invention provides a method and system for reducing storage and bandwidth requirements of a portable image capture device, such as the digital camera. Captured images, which are stored in image files, are transmitted to an online photo-sharing site for permanent storage, and the files of the uploaded images are reduced in size to reduce storage requirements. The uploaded images are thereafter only referred to an image identifier during subsequent server communication, thereby eliminating redundancy in image transmission.



FIG. 1 is a block diagram illustrating a system for reducing the transmission bandwidth and storage requirements of a portable image capture device in accordance with a preferred embodiment of the present invention. The system will be explained in terms of a preferred embodiment where the image capture device is represented as a digital camera. However, one of ordinary skill in the art will readily recognize that any portable device capable of capturing images could be used, such as a cellphone or PDA equipped with a lens attachment, for instance.


The system includes one or more digital cameras 14 and an online photo-sharing service 16. The digital cameras 14 capture digital images and store the images on an internal memory. Because the digital cameras 14 have limited storage capacity, the digital cameras 14 are provided with the capability of uploading the captured images to the online photo sharing service 16, which has practically unlimited storage capacity. In a preferred embodiment, the cameras 14 are provided with wireless connectivity for connecting to the Internet, and are therefore called “web-enabled” devices, although a wired connection method may also be used. In one embodiment, the cameras 14 may connect to the Internet via a service provider 26, which may include a wireless carrier and/or an Internet service provider (ISP) that is capable of servicing many devices simultaneously.


The online photo-sharing service 16 includes a gateway server 18 for receiving the images and an image database 20 for storing the images. Once uploaded, the images may be stored in the user's account and organized into online web albums. Once the images are stored at the photo-sharing site 16, the images may be viewed and managed over the Internet through a user's web browser 24.


Referring now to FIG. 2, a block diagram illustrating an example digital camera architecture is shown for use with the present invention. Preferably, the camera 14 includes a microprocessor-based architecture that runs an operating system 70 for controlling camera hardware 72 and overall functionality of the camera 14 (e.g., taking pictures, storing pictures, and the like). An example of such an operating system 70 is the Digita™ Operating Environment developed by the assignee of the present application. A memory 82, which may comprise flash memory or other type of non-volatile memory, is provided to store captured images as image files 80, explained further below.


The camera 14 also includes communication manager 74 software, and a TCP-IP protocol stack 76, that enables communication via the Internet, as is well-known in the art. The protocol stack 76, under direction of the communications manager interfaces with the communications hardware 78 of camera. The protocol stack 76 includes software APIs and protocol libraries that interface with the communication manager 74, and communication hardware interface drivers that interfaces directly with the various communications hardware 78 the camera 14 must function with (e.g., a Bluetooth transceiver, etc.).


The communications hardware 78 may provide wireless connectivity using anyone of a variety of methods. For example, a cellphone may be used to provide the digital camera 14 with wireless capability, where the camera 14 is connected to the cellphone via a cable or some short-range wireless communication, such as Bluetooth. Alternatively, the camera 14 could be provided with built-in cellphone-like wireless communication. In an alternative embodiment, the digital camera 14 is not wireless, but instead uses a modem for Internet connectivity. The modem could be external or internal. If external, the camera 14 could be coupled to modem via any of several communications means (e.g., USB, IEEE1394, infrared link, etc.). An internal modem could be implemented directly within the electronics of camera 14 (e.g., via a modem ASIC), or alternatively, as a software only modem executing on a processor within camera. As such, it should be appreciated that, at the hardware connectivity level, the Internet connection can take several forms. Hence, it should be appreciated that the present invention is not limited to any particular method of accessing the Internet.


The communication manager 74 communicates with operating system 70, the IP protocol stack 76, and the communications hardware 78 to establish an Internet connection and to transmit information and the image files 80 from the memory 82 to the photo-sharing service 16.



FIG. 3 is a block diagram illustrating a diagram of one embodiment for an image file 80. Image file 80 preferably includes a header 52, image data 54, a screennail 56, a thumbnail 58, image tags 60, and an audio tag 62. Header 52 preferably includes information that identifies and describes the various contents of image file 80. Image data 54 contains actual captured image data, the resolution of which depends on the settings of the camera 14. Image data 54 is typically stored in JPEG format, but may exist in whichever format is appropriate for the current location of image file 80 within the image processing chain of the camera 110. Screennail 56 and thumbnail 58 are each different versions of image data 54 that have varying degrees of reduced resolution for a number of special viewing applications. Image tags 60 include various types of metadata that correspond and relate to particular captured image data 54. Audio tag 62 stores any sound that has been recorded for the image.


The size of the image file 80 depends primarily on the size of the image data 54 and the audio tag 62, which are the largest components of the file 80. For a one-megapixel image, the image data 54 may be 200 k-1 M, the screennail 56 may be 20 k, the thumbnail 58 may be 10 k, the image tags 60 may be 1 k, and the audio tag 62 may be 250 k depending on the size of the sound clip.


As the resolution of digital cameras 14 continues to increase, the size of the image file 80 will also increase, requiring that the digital cameras 14 include higher capacity memories 80, which translates to higher camera cost. Besides the cost of the camera 14, the user 24 must also pay for the bandwidth required to transmit images to the photo-sharing site 16. Larger image sizes and the fact that the user may instruct the camera 14 to transmit a high-resolution image to multiple destinations translates to higher transmission bandwidth requirements and higher expense for the user.


Referring now to FIG. 4, a flow chart is shown illustrating the process for reducing storage and bandwidth requirements of the digital camera 14 in accordance with a preferred embodiment of the present invention. The process begins by assigning a respective image identifier (ID) 84 to each of the images uploaded to the server 18 in step 100. The image files 82 of each of the uploaded images are then optionally reduced in size on the digital camera in step 102. In response to a user request to apply an action to one of the uploaded images, the image ID 84 and the requested action are transmitted to the server 18 in step 104. According to the present invention, because each image is uploaded to the server 18 only once and is thereafter reduced in size to save storage space, and only the image ID 84 is sent to the server 18, both storage requirements and transmission bandwidth required to send the image to multiple destinations from the digital camera are significantly reduced. In addition, as image sizes increase, the amount of reduction in storage and bandwidth required will also increase, which will decrease digital imaging cost for the consumer.


The digital camera 14 operates in at least two operating modes: a capture mode for capturing images, and a play mode for displaying the previously captured images to the user. The captured images may be uploaded to the server 18 in any of the operating modes, preferably as a background process. In one preferred embodiment of the present invention, the camera 14 automatically uploads captured images to the server 18 in capture mode. In another preferred embodiment, the captured images are displayed on the camera 14 in play mode, and the user may choose which images to are to be uploaded. Also in a preferred embodiment, the user may also select actions to apply to the images, either before or after the images are uploaded.


The image ID's 84 may be assigned to the captured images by the camera 14 before uploading or by the server 18 after uploading. If the image ID's 84 are assigned by the camera 14, then the image ID's 84 are uploaded to the server 18 along with the images. If the image ID's 84 are assigned by the server 18, then the server 18 assigns the image IDs 84 to the images after image uploading and returns the assigned Ids 84 to the camera 14. Receipt of the image IDs 84 by the camera 14 acts as acknowledgement of a successful upload and may trigger the reduction of the corresponding image files in the camera 14.


In a preferred embodiment, the image files are reduced by deleting a portion of the file data. For example, the image data 54 may be replaced with the smaller screennail image 56, or the image data 54 may be made smaller through resizing and by then deleting the screennail image 56. By deleting or replacing the JPEG image data with screennail data, the size of the file is reduced dramatically, but sufficient image data exist to display the image to the user in play mode. In an alternative embodiment, the file may be deleted and replaced with just an alias, such as the file name. This results in the most space savings, but at the cost of not being able to show a representation of the image to the user.



FIG. 5 is a flow chart illustrating the process for reducing storage and bandwidth requirements of the digital camera in capture mode in a preferred embodiment of the present invention. The process begins by assigning an image identifier 84 (shown in FIG. 2) to each captured image in step 200. In a preferred embodiment, the digital camera names images using an incrementing count of the total number of images captured so that each captured image is provided with a unique name. The image identifier may then be created as a combination of the image name, and data identifying the camera 14, such as the camera serial number and/or the make and model of the camera 14. In a preferred embodiment, the image identifier (ID) 84 may be associated with the image by storing the image identifier 84 in the image file 80 as metadata, or in a separate file stored along with the image.


When an image upload is initiated, the digital camera 14 may display an action list to the user on the digital camera 14 in step 202 so the user may easily select what actions the gateway server 18 should take with respect to the images by selecting the displayed action list items. Examples of action list items include specifying where the images should be stored and/or sent from a particular user or camera, such as sending the images to a list of email addresses for instance, or even performing some type of analysis or calculation on the image data.



FIG. 6 is a block diagram illustrating an example action list 48 displayed on the LCD screen of the camera 14. The action list 48 is shown displaying three major options; printing the uploaded images, saving the uploaded images in the user's personal space called a shoebox, and sending the images to Mom. Under the printing option, the user may select from various size prints. Rather than nested menu categories as shown under the printing option, the action list 48 may be displayed with each action listed as a separate item (e.g., “Send 4×8 prints to Mom”, “Send 5×7 prints to me”).


Referring again to FIG. 5, after the user selects one or more actions from the action list 48, the camera 14 begins transmitting the images image files 80 to the server 18 along with the image IDs 84 (unless the server provides the image IDs) and any selected actions chosen by the user in step 204. Transmitting the images necessarily includes first establishing a network connection with the server 18, and may also include identifying the users' account information.


After the images files 80 are transmitted, the digital camera 14 also marks each of the uploaded image files 80 as “sent” in step 206, preferably using one of the metadata tags 60. Next, the digital camera 14 generates the reduced image files by replacing or the high resolution image 54 with lower resolution data, such as the screennail 56, and optionally deleting any audio tags 62 present in each of the of uploaded image files 80 in step 208. If the audio tag 62 has been deleted, then an “audio present” tag is marked in the reduced image file for later retrieval in step 212. The amount of image file reduction depends on the sizes of the data 54 and the audio tag 62. However, for a one mega pixel image, generating the reduced image files reduces the size of the image file 80 by 7-to-1. After the reduced image files have been generated, the camera 14 may check whether a maximum number of images files 80 are present on the camera 14 in step 214. If the maximum number of images has been reached, then the oldest images may be deleted to further increase storage capacity in step 216. If there are additional marked image files 80 in step 218, the process resumes at step 208. An additional, optional tag may also indicate that images are “protected”, and thus not included in the list of potentially images to delete. These “protected” images are those the use wants to keep in the camera, such as family pictures, etc.


Once the uploaded images files 80 are received by the server 18, the server 18 stores the images in the image database 20 and indexes them by their image IDs 84. The sever 18 also applies the requested action to the image files 80.



FIG. 7 is a flow chart illustrating the process for reducing storage and bandwidth requirements of the digital camera in play mode. The process begins by displaying the reduced images on the digital camera 14 for user selection in step 300. In a preferred embodiment, the images are displayed with an indication that the images are reduced and a muted sound icon is displayed if the audio has been deleted from the image file. After the user selects one or more images, the user may choose an action to apply to the image, as described above, in step 302. The image ID 84 for the selected image and the selected action are then transmitted to the sever 18 in step 304. If any of the selected images have not been previously uploaded, then they are appropriately ID'd and uploaded, as described above.


If the action selected by the user is to play the audio for the selected image in step 306, then the server 18 uses the image ID 84 to retrieve the audio tag 62 from the original image file 80 in step 308. The server 18 then downloads the retrieved audio tag 62 to the camera 14 in step 310, and the camera 18 plays the audio in step 312. The process of downloading the audio may take some time. Therefore, the user is preferably given the option of canceling the action at any time. In an alternative embodiment, the server re-encodes the audio into a higher compression format using an asymmetric system, such as MP3, which requires much more processing power to encode than to decode. This will make the audio tag much smaller for subsequent download, and can still be played in-camera with no noticeable loss of quality.


If the action selected by the user is to send the selected image from the camera 14 to another device in step 314, then the server 18 uses the image ID 84 to retrieve the original image data in step 316. The server 18 then downloads the retrieved image data to the camera 14 in step 318, and the camera 18 sends the image data to the device in step 320. In an alternative embodiment, the camera 14 may send the reduced image to the other device along with a password so that the device may download the original image data from the server 18. This feature may be very useful for Internet-enabled printers, where the reduced image is sent to the printer and the printer prints with full resolution even though the full resolution image was not actually sent from the camera. This feature can also be implemented via a “signature” key in the metadata, using public key encryption.


If the action selected by the user is to send the selected image from the server 18 to another destination in step 322, then the server 18 uses the image ID 84 to retrieve the original image file 80 in step 324, and sends the image file 80 to the specified destination in step 326.


If the user changes the image tags in the reduced image file in step 328, then the tags are transmitted to the server 18 in step 330 for synchronization. The server 18 then uses the image ID 84 to store the tags in the original image file 80 in step 332.


If the action selected by the user is a request to delete the selected image in step 334, then the user may be prompted in step 336 whether the user wants to delete the reduced image only or wants to delete both the reduced image and the original image file 80. If the user chooses to delete the reduced image, then the reduced image is deleted from the camera 14 in step 338. If the user chooses to delete both the reduced image and the original image file 80, then the reduced image is deleted from the camera 14 in step 340 and the server 18 uses the image ID 84 to delete the original image file 80 in step 342. Ideally, rather than use the same word “delete” for both types of actions, “delete” would only be used for eliminating the image entirely, and some other word, such as “purge” or “remove” would be used to delete the local reduced copy.


If the action selected by the user is to view the original image data in step 344, then the server 18 uses the image ID 84 to retrieve the original image data in step 346, and downloads the image data to the camera 14 in step 348. The camera then displays the image in step 350. Since the camera LCD or video output is typically significantly lower resolution than the image, the only possible use on the camera 14 is when the user wants to magnify the image significantly, such that the reduced image resolution is not sufficient (such as 4× magnification). Alternatively, a desired resolution can be requested, and the server can resize and download the requested reduced resolution—which is significantly smaller than the full resolution, but significantly larger than the in-camera version. This would also reduce bandwidth requirements.


In a preferred embodiment, the user may also want to view a group of images, which are specified by a date range and or by category which are no longer in-camera. The search criteria would then be sent to the server with the ID of the camera and/or user and the server would use the search criteria to search for matching images taken by the identified camera/user. To speed transmission, the server 18 could return the thumbnail images to the camera 14 as the search results for the user to browse. When the user finds the image(s) he is looking for, a reduced copy of the image can be then downloaded.


A method and system for reducing the storage and transmission bandwidth requirements of a digital camera has been disclosed. According to the present invention, captured images are automatically uploaded to a server and the large image files are reduced in size in the camera to reduce storage requirements. If the user wishes to apply further actions to a previously uploaded image, then the camera only sends the image ID of the image to the server, thereby reducing transmission bandwidth.


Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims
  • 1. A method, comprising: providing, by an online service using at least one server to an image capture device, action information corresponding to an action that the online service is configured to perform on images;receiving an image uploaded from the image capture device to the online service;storing the image in an image set corresponding to the image capture device;receiving, at the online service using the at least one server from the image capture device, a request to perform the action on the image; andtransmitting, to the image capture device, an image identifier assigned by the online service to the image in response to receiving the request;wherein the image identifier uniquely identifies the image in the image set.
  • 2. The method of claim 1, wherein the action comprises deleting the image.
  • 3. The method of claim 1, wherein the action comprises sending the image to a remote destination.
  • 4. The method of claim 1, wherein the action comprises associating a tag with the image.
  • 5. The method of claim 4, wherein the tag comprises a caption, a title, descriptive information, or user-entered information.
  • 6. The method of claim 1, wherein the action comprises performing an analysis of or a calculation on data associated with the image.
  • 7. A method, comprising: transmitting an image from a portable image capture device to an online service operating on a server coupled to a network;selecting, using the portable image capture device, an action to be performed on the image by the online service from a plurality of actions originated from the online service;in response to selecting the action, transmitting a request from the portable image capture device to the online service; andreceiving an image identifier assigned to the image by the online service in response to the request;wherein the image identifier uniquely identifies the image in an image set maintained by the online service; andwherein the request comprises the action to be performed on the image by the online service.
  • 8. The method of claim 7, wherein the action comprises deleting the image.
  • 9. The method of claim 7, wherein the action comprises sending the image to a remote destination.
  • 10. The method of claim 7, wherein the action comprises associating a tag with the image.
  • 11. The method of claim 10, wherein the tag comprises a caption, a title, descriptive information, or user-entered information.
  • 12. The method of claim 7, wherein the action comprises performing an analysis or a calculation on data associated with the image.
  • 13. A system, comprising: at least one server configured to operate an online service to: provide, to an image capture device, a plurality of actions that the online service is configured to perform on images;receive an image uploaded from the image capture device;store the image in an image set corresponding to the image capture device;receive, at the online service from the image capture device, a request to perform at least one of the plurality of actions for the image;assign an image identifier to the image; andtransmit the image identifier to the image capture device in response to the request;wherein the image identifier uniquely identifies the image in the image set.
  • 14. The system of claim 13, wherein the at least one of the plurality of actions comprises deleting the image.
  • 15. The system of claim 13, wherein the at least one of the plurality of actions comprises sending the image to a remote destination.
  • 16. The system of claim 13, wherein the at least one of the plurality of actions comprises associating a tag with the image.
  • 17. The system of claim 16, wherein the tag comprises a caption, a title, descriptive information, or other user-entered information.
  • 18. The system of claim 13, wherein the at least one of the plurality of actions comprises performing an analysis of or a calculation on data associated with the image.
  • 19. A system, comprising: an online service communication manager for a portable image capture device, the online service communication manager configured to: upload, via a network, an image from the portable image capture device to an online service operating on a server;receive a selection of an action configured to be performed on the image by the online service, the action corresponding to at least one of a plurality of actions originated from the online service;transmit a request from the portable image capture device to the online service to perform the action on the image; andreceive from the online service an image identifier assigned to the image by the online service in response to the request;wherein the image identifier uniquely identifies the image in an image set; andwherein the request comprises the action to be performed by the online service for the image.
  • 20. The system of claim 19, wherein the action comprises deleting the image.
  • 21. The system of claim 19, wherein the action comprises sending the image to a remote destination.
  • 22. The system of claim 19, wherein the action comprises associating a tag with the image.
  • 23. The system of claim 22, wherein the tag comprises a caption, a title, descriptive information, or user-entered information.
  • 24. The system of claim 19, wherein the action comprises performing an analysis of or a calculation on data associated with the image.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/534,909, titled “Transmission Bandwidth and Memory Requirements Reduction in a Portable Image Capture Device”, filed on Aug. 4, 2009, now issued as U.S. Pat. No. 8,073,965, which is a continuation of U.S. patent application Ser. No. 11/857,100, titled “Transmission Bandwidth and Memory Requirements Reduction in a Portable Image Capture Device”, filed on Sep. 18, 2007, now issued as U.S. Pat. No. 7,587,514, which is a continuation of U.S. patent application Ser. No. 09/680,612, titled “Transmission Bandwidth And Memory Requirements Reduction In A Portable Image Capture Device”, filed on Oct. 6, 2000, now issued as U.S. Pat. No. 7,287,088, all of which are assigned to the assignee of the present application and the entire contents of each of which are incorporated here by reference. The current application is related to U.S. Pat. Nos. 6,636,259, 7,443,419, 8,009,194, and U.S. patent application Ser. No. 13/183,566, each titled “Automatically Configuring A Web-Enabled Digital Camera To Access The Internet,” and to U.S. Pat. No. 7,117,519, titled “Method And System For Selecting Actions To Be Taken By A Server When Uploading Images,” all of which are assigned to the assignee of the present application the entire contents of each of which are incorporated here by reference.

US Referenced Citations (150)
Number Name Date Kind
4847694 Nishihara Jul 1989 A
5206915 Kern et al. Apr 1993 A
5249230 Mihm Sep 1993 A
5333133 Andrews et al. Jul 1994 A
5396546 Remillard Mar 1995 A
5430827 Rissanen Jul 1995 A
5432871 Novik Jul 1995 A
5442749 Northcutt et al. Aug 1995 A
5444483 Maeda Aug 1995 A
5446491 Shibata et al. Aug 1995 A
5469453 Glider et al. Nov 1995 A
5475441 Parulski et al. Dec 1995 A
5477264 Sarbadhikari et al. Dec 1995 A
5477542 Takahara et al. Dec 1995 A
5524194 Chida et al. Jun 1996 A
5532833 Hong et al. Jul 1996 A
5552776 Wade et al. Sep 1996 A
5558148 Uzaki et al. Sep 1996 A
5568192 Hannah Oct 1996 A
5577107 Inagaki Nov 1996 A
5594736 Tatsumi et al. Jan 1997 A
5606365 Maurinus et al. Feb 1997 A
5608874 Ogawa et al. Mar 1997 A
5625410 Washino et al. Apr 1997 A
5649185 Antognini et al. Jul 1997 A
5659742 Beattie et al. Aug 1997 A
5666159 Parulski et al. Sep 1997 A
5674003 Anderson et al. Oct 1997 A
5677909 Heide Oct 1997 A
5684918 Abecassis Nov 1997 A
5696850 Parulski et al. Dec 1997 A
5719786 Nelson et al. Feb 1998 A
5737491 Allen et al. Apr 1998 A
5739864 Copeland Apr 1998 A
5748780 Stolfo May 1998 A
5754227 Fukuoka May 1998 A
5768426 Rhoads Jun 1998 A
5771355 Kuzma Jun 1998 A
5784581 Hannah Jul 1998 A
5790789 Suarez Aug 1998 A
5790807 Fishler et al. Aug 1998 A
5793966 Amstein et al. Aug 1998 A
5799150 Hamilton et al. Aug 1998 A
5799322 Mosher, Jr. Aug 1998 A
5806005 Hull et al. Sep 1998 A
5812989 Witt et al. Sep 1998 A
5814798 Zancho Sep 1998 A
5821523 Bunte et al. Oct 1998 A
5822524 Chen et al. Oct 1998 A
5825408 Yuyama et al. Oct 1998 A
5832514 Norin et al. Nov 1998 A
5835140 Nakamura et al. Nov 1998 A
5845265 Woolston Dec 1998 A
5852472 Prasad et al. Dec 1998 A
5860068 Cook Jan 1999 A
5862217 Steinberg et al. Jan 1999 A
5862218 Steinberg Jan 1999 A
5862325 Reed et al. Jan 1999 A
5884042 Winter et al. Mar 1999 A
5896128 Boyer Apr 1999 A
5905528 Kodama May 1999 A
5905736 Ronen et al. May 1999 A
5917542 Moghadam et al. Jun 1999 A
5926623 Tsukakoshi et al. Jul 1999 A
5943046 Cave et al. Aug 1999 A
5973731 Schwab Oct 1999 A
5991842 Takayama Nov 1999 A
5999968 Tsuda Dec 1999 A
6002770 Tomko et al. Dec 1999 A
6006039 Steinberg et al. Dec 1999 A
6012088 Li et al. Jan 2000 A
6017157 Garfinkle et al. Jan 2000 A
6035323 Narayen et al. Mar 2000 A
6038295 Mattes Mar 2000 A
6046762 Sonesh et al. Apr 2000 A
6049621 Jain et al. Apr 2000 A
6052509 Abe Apr 2000 A
6064671 Killian May 2000 A
6067571 Igarashi et al. May 2000 A
6069648 Suso et al. May 2000 A
6073192 Clapp et al. Jun 2000 A
6073241 Rosenberg et al. Jun 2000 A
6076109 Kikinis Jun 2000 A
6147742 Bell et al. Nov 2000 A
6167469 Safai et al. Dec 2000 A
6185551 Birrell et al. Feb 2001 B1
6185611 Waldo et al. Feb 2001 B1
6204877 Kiyokawa Mar 2001 B1
6223190 Aihara et al. Apr 2001 B1
6226752 Gupta et al. May 2001 B1
6230187 Suzuki May 2001 B1
6266082 Yonezawa et al. Jul 2001 B1
6269481 Perlman et al. Jul 2001 B1
6281874 Sivan et al. Aug 2001 B1
6301586 Yang et al. Oct 2001 B1
6301607 Barraclough et al. Oct 2001 B2
6332146 Jebens Dec 2001 B1
6337712 Shiota et al. Jan 2002 B1
6430470 Nakajima et al. Aug 2002 B1
6445777 Clark Sep 2002 B1
6453361 Morris Sep 2002 B1
6480671 Takahashi et al. Nov 2002 B2
6502195 Colvin Dec 2002 B1
6529522 Ito et al. Mar 2003 B1
6538663 Kamei Mar 2003 B2
6567121 Kuno May 2003 B1
6567122 Anderson et al. May 2003 B1
6571271 Savitzky et al. May 2003 B1
6573927 Parulski et al. Jun 2003 B2
6581094 Gao Jun 2003 B1
6583799 Manolis et al. Jun 2003 B1
6591295 Diamond et al. Jul 2003 B1
6608973 Masera Aug 2003 B2
6623528 Squilla et al. Sep 2003 B1
6625812 Abrams et al. Sep 2003 B2
6628325 Steinberg et al. Sep 2003 B1
6636259 Anderson et al. Oct 2003 B1
6647409 Sherman et al. Nov 2003 B1
6650831 Thompson Nov 2003 B1
6657702 Chui et al. Dec 2003 B1
6701522 Rubin et al. Mar 2004 B1
6715003 Safai Mar 2004 B1
6762791 Schuetzle Jul 2004 B1
6784924 Ward et al. Aug 2004 B2
6832101 Kino Dec 2004 B1
6909889 Ishikawa Jun 2005 B2
6930709 Creamer et al. Aug 2005 B1
6950800 McIntyre Sep 2005 B1
7117519 Anderson et al. Oct 2006 B1
7287088 Anderson Oct 2007 B1
7443419 Anderson et al. Oct 2008 B2
7444373 Ludwig et al. Oct 2008 B2
7483964 Jackson et al. Jan 2009 B1
7587514 Anderson Sep 2009 B2
8009194 Anderson Aug 2011 B2
8073965 Anderson Dec 2011 B2
8219410 McIntyre Jul 2012 B2
8224776 Anderson et al. Jul 2012 B1
20010010543 Ward et al. Aug 2001 A1
20010043272 Sato et al. Nov 2001 A1
20020054224 Wasula et al. May 2002 A1
20020083171 Hoogenboom et al. Jun 2002 A1
20020087601 Anderson et al. Jul 2002 A1
20020101816 Braitberg et al. Aug 2002 A1
20030191756 Oh Oct 2003 A1
20040174440 Kojima et al. Sep 2004 A1
20050246752 Liwerant et al. Nov 2005 A1
20060062192 Payne Mar 2006 A1
20110271000 Anderson et al. Nov 2011 A1
20120254112 Anderson et al. Oct 2012 A1
Foreign Referenced Citations (9)
Number Date Country
0930770 Jul 1999 EP
1948883.2 Jul 2008 EP
2002-514560 May 2002 JP
9921336 Apr 1999 WO
WO 9921336 Apr 1999 WO
WO 9948276 Sep 1999 WO
208860 Jan 2002 WO
208926 Jan 2002 WO
0209435 Jan 2002 WO
Non-Patent Literature Citations (15)
Entry
United States Patent and Trademark Office ISA/IPEA; PCT/US2001/021488 International Preliminary Examination Report; Jun. 23, 2003; 3 pages.
United States Patent and Trademark Office ISA/IPEA; PCT/US2001/23112 International Preliminary Examination Report; May 17, 2002; 3 pages.
United States Patent and Trademark Office ISA/IPEA; PCT/US2001/041089 International Preliminary Examination Report; Sep. 9, 2004; 4 pages.
Stolowitz Ford Cowger LLP Related Case Listing; Mar. 12, 2012; 2 Page.
Digby Keane; “High Speed Communications for Robots” Department of Computer Science and Electrical Engineering University of Queensland; Oct. 15, 1999; 97 Pages.
Corcoran et al.; “Internet enabled digital photography”; Consumer Electronics, IEEE Transactions; Aug. 1999; vol. 45 Issue 3; pp. 577-583.
Recene, Ronald; Investigation into the use of the World Wide Web as an interface for distributing electronic documents to and from a remote digital color printing site; 1996.
Pan, L., “A Digital Camera With a Function of Picture Transmission,” Database EPODOC, European Patent Office, XP001091526 [TW 403853B (Inventec Corp) Sep. 1, 2000].
JP 2000047988 (Tozono) Jul. 28, 1998 (abstract) [online] Retrieved from the PAJ database.
JP 09233453 Canon Inc.) Sep. 5, 1997 (abstract) [online] Retrieved from the PAJ database.
JP 10105517 (Takasaki) Apr. 24, 1998 (abstract) [online] Retrieved from the PAJ database.
JP 11-265390 (Hoshina) Sep. 28, 1999 (abstract) (online) Retrieved from the PAJ database.
JP 2003-111008 (Satomi) Apr. 11, 2003 (abstract) (online) Retrieved from the PAJ database.
JP 2004-032129 (Fukuda) Jan. 29, 2004 (abstract) (online) Retrieved from the PAJ database.
Stolowitz Ford Cowger LLP Related Case Listing; Jul. 11, 2013; 1 Page.
Related Publications (1)
Number Date Country
20120044366 A1 Feb 2012 US
Continuations (3)
Number Date Country
Parent 12534909 Aug 2009 US
Child 13280757 US
Parent 11857100 Sep 2007 US
Child 12534909 US
Parent 09680612 Oct 2000 US
Child 11857100 US