This application is related to the following commonly-owned patent applications, each of which is hereby incorporated by reference herein:
1. Field of the Invention
The present invention relates to techniques for transmitting content over a communications network and, more particularly, to techniques for uploading content from a device to a remote network location.
2. Related Art
The Internet, and in particular the World Wide Web (the “Web”), is increasingly being used to store and exchange information and to perform commercial transactions. Although the Web was originally only capable of storing and displaying textual information, the Web may now be used to store, display, and exchange a wide variety of textual, graphical, and audio-visual information such as digital images and full-motion video.
Digital photography, for example, is becoming increasingly popular, spurred in large part by the advent of low-cost, high-quality digital cameras. An increasing number of web sites allow users to upload digital photographs and other digital images to the Web, whereby such images may subsequently be viewed, shared, edited, and printed on conventional printers using computers connected to the Web using conventional Internet connections.
To upload an image or other content to a web site from a mobile device (such as a digital camera), a user must typically use a conventional desktop or laptop computer to establish a Web connection using a conventional modem or other network connection device. The user then provides the content to the computer, such as by transferring the content from a floppy disk, CD, or the mobile device's memory to the computer. The user then selects a remote destination for the content. The user may, for examine, select a remote web site (such as the web site of an online photo album service) or another user as the remote destination.
The user then transmits the selected content to the selected remote destination. The transmission method that is used may vary depending on the kind of remote destination that is selected. If, for example, the remote destination is a web site, the user may transmit the content using conventional File Transfer Protocol (FTP) software or some other file transfer means. If the remote destination is an online photo album service or file storage service, the service may require the user to upload the content using the service's proprietary software or a web-based interface provided by the service. If the remote destination is another person, the user may need to use email software to transmit the content to the other person as an email attachment.
The content transmission process just described can be tedious, time-consuming, and error-prone for a variety of reasons. For example, the process described above may require the user to engage in many manual steps, use a variety of different software programs, and provide a variety of information to the computer. The process may also require the user to have a significant amount of technical knowledge and proficiency with using several different kinds of software and/or hardware. Assume, for example, that the content to be transmitted is a digital photograph stored in the memory of a digital camera. To provide the digital photograph to the computer, the user may need to physically connect the camera to the computer using a cable or other connection. Alternatively, the user may need to remove the camera's memory from the computer and insert the memory into a memory reader. To transfer the digital photograph to the computer, the user may need to initiate a “copy” operation using the computer's operating system or initiate a “transfer” operation using proprietary software associated with the user's particular digital camera.
To transmit the content to a desired remote destination, the user must typically identify the remote destination's online “address,” such as a web page address or an email address. To successfully transmit information to the desired remote destination, the user must therefore keep a record of and have access to the destination's address. It can be difficult and tedious for users, particularly novice and/or casual computer users, to keep track of large numbers of online addresses. Furthermore, the user may not have access to the necessary address at a particular time if, for example, the user is traveling. For these and other reasons it may be difficult or impossible for the user to provide the remote destination's address to the computer, thereby making it difficult or impossible to transmit the content to the remote destination. Furthermore, as described above, the particular transmission method that is required to transmit particular content may vary depending on the kind of content and/or the selected remote destination. The user may, for example, need to use multiple software programs to transmit different kinds of content and/or to transmit content to multiple destinations. For example, it may be necessary to use FTP software to transmit content to web sites and to use email software to transmit content to other users. As a result, the user may need to learn how to use each such software program to transmit content to particular kinds of destinations. This can be difficult and time-consuming, particularly for novice and/or casual computer users. These problems are further compounded in the situation where the user desires to transmit particular content to multiple remote destinations simultaneously. The user may, for example, desire to transmit a digital image simultaneously to several friends and to an online photo album service for storage. In such a situation, the user may need to initiate a separate manual transmission of the content for each desired destination. The problems described above are also further compounded in the increasingly common situation in which the user desires to permanently store content at a remote location (such as an online file storage service) rather than on the hard drive of the user's computer. In such a case, the user may transmit content (such as digital photographs) to an online service and then erase, overwrite, discard, or otherwise not retain an original copy of the content locally. If the user subsequently desires to transmit some or all of the content to another remote destination, it may be necessary for the user to engage in a significant amount of tedious and time-consuming activity. If, for example, the online service at which the content is remotely stored does not provide a feature for transmitting the content to another person by email, the user may need to download the content from the online service to the user's local computer and then transmit the content to the other person using email software, which can be tedious and time-consuming for all of the reasons described above. Furthermore, the requirement that the source of the content (e.g., a digital camera) be connected to a host computer has a variety of disadvantages. For example, a mobile computer user who desires the ability to transmit content from a variety of locations (such as at home and at the office) typically must have access to a Web-connected computer in each such location. Using the techniques described above, the content source must be connected to a computer to upload content to the Web and to transmit the content to services and other users. As a result, a user who wishes to transmit such content may be required to travel with both the content source and a laptop computer, or may be limited to uploading content from locations at which a Web-connected desktop computer is available. The requirement that the content source be connected to a computer therefore limits the mobility of the user and limits the range of locations from which content may be uploaded. This may be particularly problematic when the content source is a mobile device, such as a digital camera.
What is needed, therefore, are improved techniques for uploading content from a device to a remote location.
Techniques are disclosed for uploading content (such as a digital photograph) from a content upload device to a content server over a communications network, and for automatically forwarding the content from the content server to one or more remote destinations. A user of the content upload device may cause the content upload device to upload the content to the content server by initiating a single action, such as pressing a single button on the content upload device, and without providing information identifying the user to the content upload device. Upon receiving the content, the content server may add the content to a queue, referred to as a content outbox, associated with the user. The content server may automatically forward the content in the user's content outbox to one or more remote destinations specified by preferences associated with the user's content outbox. Additional aspects and embodiments of the present invention and advantages thereof will be described in more detail below.
Techniques are disclosed for uploading content (such as a digital photograph) from a content upload device to a content server over a communications network, and for automatically forwarding the content from the content server to one or more remote destinations. A user of the content upload device may cause the content upload device to upload the content to the content server by initiating a single action, such as pressing a single button on the content upload device, and without providing information identifying the user to the content upload device. Upon receiving the content, the content server may add the content to a queue, referred to as a content outbox, associated with the user. The content server may automatically forward the content in the user's content outbox to one or more remote destinations specified by preferences associated with the user's content outbox.
Referring to
A user 102 possesses content 104 stored on a content medium 103. The content 104 may be any kind of content, such as digital images (e.g., digital photographs captured using a digital camera), digital video (e.g., MPEG, AVI, or QuickTime® files), digital audio (e.g., MP3 files), digital text documents (e.g., word processing documents), analog text and/or images (such as printed text or conventional photographs), or any combination thereof. Although in particular examples the content 104 may be described as a single file containing information (such as a single digital photograph), it should be appreciated that the content 104 may include a plurality of files of the same or varying types. More generally, the content 104 may be any information that may be transferred to the content upload device 106.
Furthermore, the content 104 need not be generated externally to the content upload device 106. Rather, the content upload device 106 may itself generate the content 104, as in the case where the content upload device 106 is a digital camera. In such a case, it is not necessary for the user 102 to provide the content 104 to the content upload device 106.
The user 102 provides the content 104 to the content upload device 106 through a media reader 105 coupled to the content upload device 106. The media reader 105 reads the content 104 (or a portion thereof) from the content medium 103 and transfers the content 104 to the content upload device 106. The content upload device 106 may include a memory or other storage medium in which the content 104 is stored.
The content upload device 106 establishes a network connection with a content server 118 over a communications network 116. The content upload device 106 uploads the content 104, in a content upload message 114, to the content server 118. As illustrated in
Referring to
After identifying the user content account 120 associated with the user 102, the content server stores the content 104 in a content outbox 126 associated with the content account 120 (step 305). Additional information that is associated with the content account 120 will be described in more detail below with respect to
Advantages of various embodiments of the system 100 will now be described briefly. In one embodiment, the user 102 may initiate uploading of the content 104 to the content server 118 using a single action. For example, the content upload device 106 may include content upload initiation means 108, such as a single button (with an appropriate label, such as “Go,” “Transmit,” or “Upload”). To initiate uploading of the content 104 to the content server 118, the user 102 may activate the content upload initiation means 108 (e.g., the single button), in response to which the content upload device 106 may upload the content 104 to the content server 118 without requiring any additional action by the user 102. In another embodiment, in response to activation of the content upload transmission means 108, the content upload device 106 may both transfer the content 104 from the content medium 103 to the content upload device 106 (through the media reader 105) and upload the content 104 to the content server 118. As a result, the user 102 may initiate both the transfer of the content 104 to the content upload device 106 and the upload of the content 104 to the content server 118 using a single action. Furthermore, in yet another embodiment, the content server 118 may forward the content 104 to the content destination 128 automatically, i.e., without requiring any additional action by the user 102. As a result, a single action performed by the user 102 may initiate the transfer of the content 104 to the content upload device 106, the upload of the content 104 from the content upload device 106 to the content server 118, and the forwarding of the content 104 by the content server 118 to the content destination 128.
In another embodiment, the user 102 may initiate the transfer of the content 104 to the content upload device 106 and/or the uploading of the content 104 from the content upload device 106 to the content server 118 without providing information identifying the user (such as an account name or password) to the content upload device 106 and/or the content server 118. For example, as described above, the user 102 may initiate transfer/upload of the content 104 simply by activating the content upload initiation means 108 (e.g., a single button). As described in more detail below, the content server 118 may identify the user content account 120 associated with the user 102 automatically, i.e., without requiring the user 102 to provide any personal identifying information.
As used herein, the terms “information identifying the user” and “personal identifying information” refer to information that identifies the user 102 of the device 106 apart from the device 106 itself. In the case, for example, where the device ID 123 (described below) is a serial number or other unique identifier of the device 106, the device ID 123 does not constitute “information identifying the user,” even though the device ID 123 may identify the user 102 indirectly if the user 102 is the sole user of the device 106. Examples of “information identifying the user” include the user's name, address, telephone number, and social security number.
As a result of these and other features of various embodiments of the present invention, the user's experience of transferring content 104 to the content upload device 106, uploading content 104 from the content upload device 106 to the content server 118, and forwarding the content 104 to the content destination 128, is greatly simplified compared to the experience associated with conventional techniques for performing similar functions. For example, to upload the content 104 from the content upload device 106 to the content server 118, the user 102 may simply activate the content upload initiation means 108 (e.g., press a single button). The user 102 need not, in particular embodiments of the present invention, identify or input an address of the content server, input information identifying the user 102, or execute file-transfer software for transferring the content 104 to the content server 118. Rather, the content upload device 106 automatically establishes a network connection with the content server 118 and uploads the content 104 to the content server 118. As a result, the task of uploading content 104 to the content server 118 is greatly simplified and is particularly well-suited for use by novice and/or casual computer users. Similarly, in various embodiments of the present invention, forwarding of the content 104 from the content server 118 to the content destination 128 is automated, thereby relieving the user 102 of the responsibility for performing tasks that may be necessary to forward the content 104 to the content destination 128. As described in more detail below, the content server 118 may automatically select the content destination 128 based on preferences 125 previously specified by the user 102 and automatically forward the content 104 to the content destination 128 using an appropriate forwarding method.
A further advantage of various embodiments of the system 100 is that the user 102 may upload the content 104 to the content server 118 without connecting the content upload device 106 to a host computer, such as a conventional desktop or laptop computer. One advantage of this feature is that it may be possible for the user 102 to upload the content 104 from a wider variety of locations, since the user's choice of locations from which to upload the content 104 is constrained only by the mobility of the content upload device 106 and the availability of a network connection over which the content upload device 106 may connect to the content server 118. The lack of a requirement that the user 102 connect the content upload device 106 to a conventional computer may also simplify the process of uploading the content 104 to the content server 118, by eliminating the steps of physically connecting the content upload device 106 to the computer and transferring the content 104 from the content upload device 106 to the computer, and all of the potential difficulties that such steps entail.
Various embodiments of the system 100 will now be described in more detail.
The content medium 103 may be any medium that is suitable for storing the content 104. The content medium 103 may, for example, be any of a variety of kinds of input media, such as one or more PCMCIA cards, ZIP disks, compact flash cards, SmartMedia®, Memory Stick® memory, CDs, floppy disks, photographic negatives or prints, or a digital camera.
The media reader 105 may be any device that is capable of reading the content 104 from the content medium 103. The media reader 105 may, for example, be a PCMCIA interface, compact flash card reader, SmartMedia® reader, Memory Stick® memory reader, CD drive, floppy disk drive, scanner, or I/O port (such as a Universal Serial Bus (USB) port or a conventional serial or parallel port). The content medium 103 may be coupled to the media reader 105 in any manner, such as by a cable connection, network connection, or by inserting the content medium 103 into an appropriate interface on the media reader 105, as in the case of floppy disks and CDs.
The media reader 105 may be internal or external to the content upload device 106. Furthermore, the media reader 105 may be permanently or temporarily coupled to the content upload device 106 using any kind of connection. In one embodiment, for example, the content upload device 106 is itself a media reader (such as a digital camera memory reader) that has been modified to include means for uploading the content 104 to the content server 118 using the techniques described herein.
The content upload device 106 may be any kind of mobile device, such as a mobile printer, digital camera, Personal Digital Assistant (PDA), cellular telephone, or any combination thereof. The content upload device 106 need not, however, be a mobile device. The content upload device 106 may, for example, be a conventional computer, such as a conventional desktop or laptop computer. Although implementing the content upload device 106 as a conventional computer may limit the mobility of the content upload device 106, in such cases the content upload device 106 may still operate advantageously in conjunction with features of various embodiments of the present invention, such as the ability to upload content 104 which is automatically forwarded by the content server 118 to the remote content destination 118.
As shown in
Alternatively, the content upload device 106 may communication over the network 116 directly through the data port 112, without the use of the cellular telephone 115. In such a case, network communications device 110 may be any kind of communications device, such as a conventional analog modem, cable modem, Digital Subscriber Line (DSL) modem, or network interface card (NIC). The network communications device 110 may be either internal or external to the content upload device 106, so long as the content upload device 106 includes a controller suitable for using the network communications device 110 to communicate over the communications network 116.
The content upload device 106 may establish a connection to the content server 118 in any of a variety of ways. For example, consider one embodiment in which the communications network 116 is a cellular telephone network. The content upload device 106 may initiate a connection with the content server 118 over the network 116 by instructing the cellular telephone to dial a predetermined telephone number associated with the content server 118. The content server 118 may be equipped with a corresponding modem that answers the telephone call placed by the cellular telephone 115. The content server 118 and cellular telephone 115 may then negotiate and establish a connection over the network 116 in any of a variety of ways that are well-known to those of ordinary skill in the art. Alternatively, the content upload device 106 may instruct the cellular telephone 115 to call a predetermined toll-free telephone number to connect to a computer (not shown) that may provide the content upload device 106 with a telephone number or other address of the content server 118. Techniques for locating the content server 118 in this manner are described in more detail in the above-referenced patent application entitled “Method and Apparatus for Remote Processing and Sharing of Digital Images.”
The content upload device 106 may obtain the telephone number for the content server 118 in any of a variety of ways. For example, upon activation of the content upload initiation means 108, the content upload device 106 may prompt the user 102 for the content server's telephone number, which the user 102 may then enter through a keypad on the content upload device 106. Alternatively, for example, the content upload device 106 may allow the user 102 to pre-configure the content upload device 106 with the telephone number or Internet address of the content server 118 so that the content upload device 106 may automatically connect to the content server 118 without having to prompt the user for such information each time the content upload device 106 uploads content to the content server 118.
In any case, the content upload device 106 may store the telephone number or other addressing information for the content server 118 in a ROM, RAM, flash memory, or other storage medium.
As shown in
As shown in
As described above, some or all of the content 104 may be transferred from the content medium 103 to the content upload device 106. The content upload device 106 may, for example, include means (not shown) that allow the user to select particular portions of the content 104 (e.g., particular digital photographs) to transfer to the content upload device 106.
The content upload message 114, which contains some or all of the content 104 provided by the user, may be formatted and transmitted according to any appropriate network communications protocol, such as the File Transfer Protocol (FTP) or the Hypertext Transfer Protocol (HTTP). Examples of techniques that may be used to upload images to the content server 118 are described in more detail in above-referenced patent application entitled “Method and System for Remote Utilizing a Mobile Device to Share Data Objects.” The communications network 116 may be any network or combination of networks. For example, the communications network may be a POTS network, wireless network, Local Area Network (LAN), Wide Area Network (WAN), or an internet such as the public Internet. The content upload device 106, content server 118, and content destination 128 need not all communicate over the same network. The single communications network 116 is shown in
The content server 118 may be implemented in hardware, software, firmware, or any combination thereof. For example, the content server 118 may be implemented in software executing on a computer accessible over the communications network 116. The content server 118 need not be a “server” according to a client-server architecture. Rather, the content server 118 may be implemented using any means for performing the functions described herein.
Referring to
The user content account 120 includes information 122 identifying the user 102, such as the user's real name 212, postal address 214, telephone number 216 (e.g., the telephone number of the cellular telephone 115), email address 218, payment information 220 (such as a credit card number and expiration date), user name 222, and password 224. The particular identifying information 122 shown in
The user content account 120 also include the content upload device ID 123 of the content upload device 106. As described in more detail in the above-referenced patent application entitled “Product Registration System,” the content server 118 may associate one or more content upload device IDs with each user content account. The content upload device ID 123 may be obtained and recorded in the user content account 120 when the user content account 120 is created.
As described above, in one embodiment the content server 118 identifies the user 102 that is associated with the content upload device 106 when the content server 118 receives the content upload message 114 (
Alternatively, the content server 118 may use caller ID messages (not shown) to identify the telephone number 216 associated with the content upload device 106 and thereby identify the user 102, as described in more detail in the above-referenced patent application entitled “Method and Apparatus for Printing Remote Images Using a Mobile Device and Printer.” In such a case, the telephone number 216 acts as a unique identifier of the user 102.
Although in certain embodiments of the present invention the content upload device 106 does not transmit information identifying the user 102 to the content server 118, this is not a requirement of the present invention. Rather, the content upload device 106 may store and transmit information identifying the user 102, such as the user's username 222 and password 224, to the content server 118. The content server 118 may identify the user 102 based on such information. The content server 118 may also automatically log the user in to the user content account 120 using such information.
As shown in
As mentioned above, when the content server 118 receives the content 104 (in the content upload message 114), the content server 118 stores the content in the content outbox 126 (
As described above, the content server 118 forwards the content 104 to the content destination 128 (
The content server 118 may accumulate content in the content outbox 126 until the occurrence of a particular event. For example, the content server 118 may accumulate content that it receives until the user 102 instructs the content server 118 (using, for example, a web-based interface) to transmit some or all of the content 126a-n in the content outbox 126 to the content destination 128. Alternatively, the content server 118 may automatically forward any content that it receives (such as content 104) to the content destination 128 without waiting for any instruction from the user 102.
It should be appreciated that the content upload device 106 and/or the content server 118 may perform various kinds of processing on the content 104. Such processing may include, for example, compressing the content 104, encrypting the content 104, and performing image processing on the content 104, such as changing the spatial resolution and/or color depth of the content 104 to make it suitable for printing on a mobile printer. Examples of various kinds of processing that may be performed on the content 104 are described in more detail in the above-referenced patent application entitled “Method and Apparatus for Printing Remote Images Using a Mobile Device and Printer.”
As mentioned above, the content server 118 may automatically select one or more content destinations for the content 104 (
The content server 118 may, for example, select the content destination 128 based on the type of the content 104. For example, if the content 104 is a text document (such as a Microsoft Word® word processing file), the content server 118 may select an email recipient as the content destination 128. If, however, the content 104 is a digital image, the content server 118 may select a digital image storage service as the content destination 128. From these examples it should be appreciated that the content server 118 may also select a forwarding method (e.g., email or file transfer) based on the content type.
Techniques which the content server 118 may use to select the content destination 128 and/or content forwarding method will now be described in more detail. Referring again to
Referring to
The content server 118 searches through the rows 202a-m of the content destination preferences 125 to identify one or more records corresponding to the type of the content 104. More specifically, the content server 118 enters into a loop over each destination preference P in the content destination preferences 125 (step 406). The content server identifies the content type TP of preference P by reference to the content type 224 shown in
The content server 118 may also select a forwarding method to use to forward the content 104 to the destination(s) selected in step 308. For example, as shown in
For each destination D (step 502), the content server 118 determines whether the destination is a web site (step 504). The content server 118 may perform this step by, for example, examining the URL field 222 (
If the destination D is a web site, the content server 118 forwards the content 104 to the web site by logging in to the web site using the username 206 and password 208 associated with the destination D (step 510), if necessary, and transferring the content 104 to the web site using HTTP (step 512). The content destination 128 may, for example, be a web site of a service, such as an online digital photo album service, with which the user 102 has a separate account (i.e., an account that is distinct from the user's content account 120). If the destination D is not a web site (e.g., if the destination D is an email address), the content server 118 forwards the content 104 to the email address by logging in to the user's SMTP account using the username 206 and password 208 associated with the destination D, and by transmitting the content 104 to the email address as an email message or an email attachment using SMTP (step 516). The content server 118 by store an IP address (not shown) for the user's SMTP account for use in step 514.
Content server 118 repeats steps 504-516 for each destination D (step 518), thereby forwarding the content 104 to each of the destinations using an appropriate forwarding method.
It should be appreciated that each content type 224 may be associated with either a single content destination or with multiple content destinations. If the content type of the content 104 is associated with multiple content destinations, the content server 118 may forward the content 104 to each of the multiple content destinations. The user 102 may, for example, prefer that digital photographs be forwarded both to an online photo album service and to a preselected group of family members.
The content destination preferences 125 may be editable by the user 102. The service associated with the content server 118 may, for example, provide proprietary software and/or a web-based interface which allows the user to modify the content destination preferences 120. Such an interface may, for example, allow the user 102 to edit the URL 222, username 206, and password 208 that is associated with each content type.
The particular content destination preferences 125 shown in
One advantage of the system 100 described above is that the “intelligence” of the system 100 may be provided entirely or primarily in the content server 118, rather than in the user 102, the content upload device 106, and/or the content destination 128. For example, as described above, the content upload device 106 may automatically establish a network connection with the content server 118 and automatically upload the content 104 to the content server 118, thereby relieving the user 102 of the responsibility for providing a network address for the content server 118, establishing a network connection with the content server 118, providing a username and/or password to the content server 118, and performing other tasks typically associated with uploading content to remote locations over the Internet.
Similarly, as described above, the content server 118 may automatically select the content destination 128, select a forwarding method for forwarding the content 104 to the content destination 128, and performing the actual forwarding of the content 104 to the content destination. This relieves both the user 102 and the content upload device 106 of the responsibility for performing such tasks. In particular, placement of such functionality in the content server 118 may enable the content upload device 106 to be implemented as a small, mobile, and inexpensive device with relatively little hardware and/or software. In various embodiments of the present invention the content upload device 106 may include only simple network communications capabilities, such as the ability to serially transmit the content 104 to the cellular telephone 115, rather than the kinds of extensive networking and processing capabilities that are typically provided by conventional desktop and laptop computers.
A further advantage of various embodiments of the system 100 is that the user 102 may use the content upload device 106 to upload content from a variety of content sources, such as digital cameras, scanners, video cameras, and still photographs. The user 102 may use the content upload device 106 to upload content from such sources even if such sources are not themselves capable of communicating over the network, since the content upload device 106 provides the necessary network communication capabilities.
It is to be understood that although the invention has been described above in terms of particular embodiments, the foregoing embodiments are provided as illustrative only, and do not limit or define the scope of the invention. Various other embodiments, including but not limited to the following, are also within the scope of the claims.
The content upload device 106 is described herein as performing various functions, such as receiving the content 104 from the content medium 103 and uploading the content 104 to the content server 118. It should be appreciated that such functionality may be implemented within the content upload device 106 in any manner, such as by using hardware, software, firmware, or any combination thereof. In general, a device “controller” refers herein generally to any such subsystem(s) of the content upload device 106 that perform the functions described herein.
The content upload device 106 may also be configured to download content from the content server 118 and to print such content, as described in more detail in the above-referenced patent application entitled “Method and Apparatus for Printing Remote Images Using a Network-Enabled Printer.” The content upload device 106 may, for example, include a content download initiation means (not shown), such as a button labeled “Print” or “Download” in addition to the content upload initiation means. The single content upload device 106 may therefore be used both to upload and to download content.
The term “connection” as used herein (e.g., a connection between content upload device 106 and content server 118) refers to any kind of connection that enables communication between or among two or more devices. For example, a “connection” may be a physical and/or logical connection enabled by any combination of wired and/or wireless networks. Although examples are provided above in which content 104 is uploaded to the content server 118 in response to actions performed by the user 102, this is not a limitation of the present invention. Rather, content 104 may be automatically uploaded without any prompting by the user 102. For example, the content upload device 106 may automatically upload the content 104 to the content server 118 upon establishment of a network connection between the content upload device 106 and the content server 118. Such a connection may be established automatically when, for example, the content upload device 106 enters the range of a wireless network through which the content server 118 is accessible. In general, the techniques described above may be implemented, for example, in hardware, software, firmware, or any combination thereof. The techniques described above may be implemented in one or more computer programs executing on a programmable computer including a processor, a storage medium readable by the processor (including, for example, volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. Program code may be applied to data entered using the input device to perform the functions described and to generate output information. The output information may be applied to one or more output devices.
Elements and components described herein may be further divided into additional components or joined together to form fewer components for performing the same functions.
Each computer program within the scope of the claims below may be implemented in any programming language, such as assembly language, machine language, a high-level procedural programming language, or an object-oriented programming language. The programming language may be a compiled or interpreted programming language.
Each computer program may be implemented in a computer program product tangibly embodied in a machine-readable storage device for execution by a computer processor. Method steps of the invention may be performed by a computer processor executing a program tangibly embodied on a computer-readable medium to perform functions of the invention by operating on input and generating output.
It is to be understood that although the invention has been described above in terms of particular embodiments, the foregoing embodiments are provided as illustrative only, and do not limit or define the scope of the invention. Other embodiments are also within the scope of the present invention, which is defined by the scope of the claims below. Other embodiments that fall within the scope of the following claims includes include, but are not limited to, the following.
Number | Name | Date | Kind |
---|---|---|---|
661504 | Ehlman | Nov 1900 | A |
1251766 | Gindele | Jan 1918 | A |
1524508 | Cohen | Nov 1922 | A |
2590678 | Caim | Mar 1952 | A |
2854903 | Land et al. | Oct 1958 | A |
2930301 | Land et al. | Mar 1960 | A |
3047387 | Land | Jul 1962 | A |
3079849 | Wareham | Mar 1963 | A |
3183809 | Nerwin | May 1965 | A |
3270653 | Bachelder | Sep 1966 | A |
3283683 | Land | Nov 1966 | A |
3314792 | Land | Apr 1967 | A |
3405619 | Land | Oct 1968 | A |
3455692 | Bachelder et al. | Jul 1969 | A |
3631773 | Moodie et al. | Jan 1972 | A |
3636845 | Harvey | Jan 1972 | A |
3643570 | Reid et al. | Feb 1972 | A |
3673939 | Harvey | Jul 1972 | A |
3754917 | Harvey | Aug 1973 | A |
3767405 | Harvey | Oct 1973 | A |
3852781 | Erlichman | Dec 1974 | A |
3939781 | Adams | Feb 1976 | A |
4114166 | Driscoll et al. | Sep 1978 | A |
4129377 | Miyamoto et al. | Dec 1978 | A |
4132471 | Svatek et al. | Jan 1979 | A |
4172647 | Gold | Oct 1979 | A |
4200383 | Bendoni et al. | Apr 1980 | A |
4212528 | Mason | Jul 1980 | A |
4248510 | Baker et al. | Feb 1981 | A |
4291966 | Bendoni et al. | Sep 1981 | A |
4370045 | Holmes | Jan 1983 | A |
4488794 | Dolgow et al. | Dec 1984 | A |
4569578 | Stella et al. | Feb 1986 | A |
4605608 | Bullitt | Aug 1986 | A |
4660951 | Reed et al. | Apr 1987 | A |
4693576 | Chen | Sep 1987 | A |
4829524 | Yoshida | May 1989 | A |
4855769 | Slavitter et al. | Aug 1989 | A |
4884088 | Mauchan | Nov 1989 | A |
4951073 | Slavitter | Aug 1990 | A |
4962398 | Sorg et al. | Oct 1990 | A |
5001502 | Douglas | Mar 1991 | A |
5023636 | Douglas | Jun 1991 | A |
5040009 | Mizuno | Aug 1991 | A |
5049910 | Hsiung | Sep 1991 | A |
5073464 | Osawa et al. | Dec 1991 | A |
5103249 | Keene | Apr 1992 | A |
5176224 | Spector | Jan 1993 | A |
5285894 | Kamata et al. | Feb 1994 | A |
5292612 | Polizzotto et al. | Mar 1994 | A |
5440366 | Reiss et al. | Aug 1995 | A |
5453804 | Norris et al. | Sep 1995 | A |
5673190 | Kahleck et al. | Sep 1997 | A |
5694484 | Cottrell et al. | Dec 1997 | A |
5742905 | Pepe et al. | Apr 1998 | A |
5757976 | Shu | May 1998 | A |
5768583 | Orzol et al. | Jun 1998 | A |
5787237 | Reilly | Jul 1998 | A |
5799219 | Moghadam et al. | Aug 1998 | A |
5806005 | Hull et al. | Sep 1998 | A |
5838999 | Norris | Nov 1998 | A |
5854882 | Wang | Dec 1998 | A |
5855007 | Jovicic et al. | Dec 1998 | A |
5859628 | Ross et al. | Jan 1999 | A |
5870633 | Norris | Feb 1999 | A |
5894546 | Yoshida | Apr 1999 | A |
5973731 | Schwab | Oct 1999 | A |
5978559 | Quinion | Nov 1999 | A |
5991290 | Malik | Nov 1999 | A |
5995239 | Kagawa et al. | Nov 1999 | A |
6032180 | Nishikawa | Feb 2000 | A |
6043898 | Jacobs | Mar 2000 | A |
6067532 | Gebb | May 2000 | A |
6072595 | Yoshiura et al. | Jun 2000 | A |
6076068 | DeLapa et al. | Jun 2000 | A |
6128415 | Hultgren, III et al. | Oct 2000 | A |
6134450 | Nordeman | Oct 2000 | A |
6166729 | Acosta et al. | Dec 2000 | A |
6167469 | Safai et al. | Dec 2000 | A |
6202096 | Williams et al. | Mar 2001 | B1 |
6215561 | Kakutani | Apr 2001 | B1 |
6241673 | Williams | Jun 2001 | B1 |
6275104 | Holter | Aug 2001 | B1 |
6298164 | Susuki | Oct 2001 | B1 |
6314476 | Ohara | Nov 2001 | B1 |
6351776 | O'Brien et al. | Feb 2002 | B1 |
6356356 | Miller et al. | Mar 2002 | B1 |
6381660 | Ito | Apr 2002 | B1 |
6397261 | Eldridge et al. | May 2002 | B1 |
6445694 | Swartz | Sep 2002 | B1 |
6453127 | Wood et al. | Sep 2002 | B2 |
6473498 | Foth | Oct 2002 | B1 |
6526416 | Long | Feb 2003 | B1 |
6553240 | Dervarics | Apr 2003 | B1 |
6570640 | Garfinkle et al. | May 2003 | B1 |
6594032 | Hiroki et al. | Jul 2003 | B1 |
6623527 | Hamzy | Sep 2003 | B1 |
6633635 | Kung et al. | Oct 2003 | B2 |
6636259 | Anderson et al. | Oct 2003 | B1 |
6657702 | Chui et al. | Dec 2003 | B1 |
6662231 | Drosset et al. | Dec 2003 | B1 |
6671063 | Iida | Dec 2003 | B1 |
6674539 | Serra et al. | Jan 2004 | B1 |
6715003 | Safai | Mar 2004 | B1 |
6725051 | Fidler | Apr 2004 | B2 |
6744528 | Picoult et al. | Jun 2004 | B2 |
6748569 | Brooke et al. | Jun 2004 | B1 |
6757900 | Burd et al. | Jun 2004 | B1 |
6785022 | Todaka | Aug 2004 | B1 |
6785542 | Blight et al. | Aug 2004 | B1 |
6792577 | Kimoto | Sep 2004 | B1 |
6795205 | Gacek | Sep 2004 | B1 |
6795852 | Kleinrock et al. | Sep 2004 | B1 |
6804534 | Lai et al. | Oct 2004 | B2 |
6804789 | Shimizu | Oct 2004 | B2 |
6823457 | Berstis et al. | Nov 2004 | B1 |
6823526 | Howard et al. | Nov 2004 | B2 |
6831682 | Silverbrook et al. | Dec 2004 | B1 |
6847334 | Hayhurst et al. | Jan 2005 | B2 |
6856412 | Kaneko | Feb 2005 | B1 |
6892069 | Flynn | May 2005 | B1 |
6892199 | Hong et al. | May 2005 | B2 |
6906810 | Senay et al. | Jun 2005 | B2 |
6922258 | Pineau | Jul 2005 | B2 |
6931432 | Yoshida | Aug 2005 | B1 |
6931600 | Pittman | Aug 2005 | B1 |
6937365 | Gorian et al. | Aug 2005 | B2 |
6938079 | Anderson et al. | Aug 2005 | B1 |
6947995 | Chang et al. | Sep 2005 | B2 |
6976084 | Pineau et al. | Dec 2005 | B2 |
6980305 | Martinez | Dec 2005 | B2 |
6993662 | Rubin et al. | Jan 2006 | B2 |
7006242 | Smith, II et al. | Feb 2006 | B2 |
7010695 | Mizuguchi | Mar 2006 | B1 |
7016062 | Ishizuka | Mar 2006 | B2 |
7068846 | Yaguchi | Jun 2006 | B1 |
7073119 | Matsubayashi et al. | Jul 2006 | B2 |
7092119 | Hinds et al. | Aug 2006 | B1 |
7099042 | Yaguchi | Aug 2006 | B2 |
7103905 | Novak | Sep 2006 | B2 |
7142317 | Naito et al. | Nov 2006 | B2 |
7143141 | Morgan et al. | Nov 2006 | B1 |
7162518 | Takahashi | Jan 2007 | B2 |
7162691 | Chatterjee et al. | Jan 2007 | B1 |
7190481 | Hirabayashi | Mar 2007 | B2 |
7206806 | Pineau | Apr 2007 | B2 |
7210099 | Rohrabaugh et al. | Apr 2007 | B2 |
7233408 | Henderson et al. | Jun 2007 | B2 |
7260637 | Kato | Aug 2007 | B2 |
7272390 | Adachi et al. | Sep 2007 | B1 |
7272788 | Anderson et al. | Sep 2007 | B2 |
7281034 | Eyal | Oct 2007 | B1 |
7286251 | Tomida et al. | Oct 2007 | B2 |
7355732 | Yamaguchi | Apr 2008 | B2 |
7383321 | Moyer | Jun 2008 | B2 |
7464134 | Simpson et al. | Dec 2008 | B2 |
20010021664 | Kikinis | Sep 2001 | A1 |
20010042010 | Hassell | Nov 2001 | A1 |
20010052942 | MacCollum et al. | Dec 2001 | A1 |
20010054066 | Spitzer | Dec 2001 | A1 |
20010054106 | Anderson et al. | Dec 2001 | A1 |
20010056550 | Lee | Dec 2001 | A1 |
20020040332 | Maari et al. | Apr 2002 | A1 |
20020042884 | Wu et al. | Apr 2002 | A1 |
20020051197 | Minegishi | May 2002 | A1 |
20020062406 | Chang et al. | May 2002 | A1 |
20020075510 | Martinez | Jun 2002 | A1 |
20020077974 | Oritz | Jun 2002 | A1 |
20020078160 | Kemp et al. | Jun 2002 | A1 |
20020078352 | Angwin et al. | Jun 2002 | A1 |
20020091527 | Shiau | Jul 2002 | A1 |
20020100802 | Sehr | Aug 2002 | A1 |
20020104099 | Novak | Aug 2002 | A1 |
20020161856 | Strange | Oct 2002 | A1 |
20020163895 | Haller et al. | Nov 2002 | A1 |
20020169002 | Imbrie et al. | Nov 2002 | A1 |
20020169851 | Weathersby et al. | Nov 2002 | A1 |
20020171857 | Hisatomi et al. | Nov 2002 | A1 |
20020174205 | Nakashima | Nov 2002 | A1 |
20020184302 | Prueitt | Dec 2002 | A1 |
20020184378 | Pineau et al. | Dec 2002 | A1 |
20020186404 | Gragg | Dec 2002 | A1 |
20020188673 | Gimson | Dec 2002 | A1 |
20030002072 | Berkema et al. | Jan 2003 | A1 |
20030004859 | Shaw et al. | Jan 2003 | A1 |
20030005050 | Pineau et al. | Jan 2003 | A1 |
20030037076 | Bravery et al. | Feb 2003 | A1 |
20030069780 | Hailwood et al. | Apr 2003 | A1 |
20030081788 | Simpson et al. | May 2003 | A1 |
20030084016 | Norgaard et al. | May 2003 | A1 |
20030090707 | Simpson et al. | May 2003 | A1 |
20030093756 | Behzadi et al. | May 2003 | A1 |
20030105887 | Cox et al. | Jun 2003 | A1 |
20030107529 | Hayhurst et al. | Jun 2003 | A1 |
20030115250 | Bernier et al. | Jun 2003 | A1 |
20030149573 | Lynton | Aug 2003 | A1 |
20040010540 | Puri et al. | Jan 2004 | A1 |
20040019628 | Piuri | Jan 2004 | A1 |
20040201613 | Simpson et al. | Oct 2004 | A1 |
20040201709 | McIntyre et al. | Oct 2004 | A1 |
20050024499 | Luciano et al. | Feb 2005 | A1 |
20050231761 | Pineau | Oct 2005 | A1 |
20050235202 | Chen et al. | Oct 2005 | A1 |
20080278751 | Moyer | Nov 2008 | A1 |
Number | Date | Country |
---|---|---|
2657423 | Dec 1976 | DE |
0 598 513 | May 1994 | EP |
0 738 956 | Oct 1996 | EP |
0 745 924 | Dec 1996 | EP |
0 830 000 | Jul 1997 | EP |
0 862 104 | Sep 1998 | EP |
0 872 792 | Oct 1998 | EP |
0 586 903 | Apr 1999 | EP |
0 930 774 | Jul 1999 | EP |
1 063 597 | Dec 2000 | EP |
1 093 288 | Apr 2001 | EP |
1 100 003 | May 2001 | EP |
1 109 113 | Jun 2001 | EP |
1 117 271 | Jul 2001 | EP |
1 132 839 | Sep 2001 | EP |
1 176 500 | Jan 2002 | EP |
1 075 138 | Sep 2005 | EP |
0 855 835 | Mar 2006 | EP |
2 775 406 | Feb 1998 | FR |
2 287 623 | Sep 1995 | GB |
2 303 478 | Feb 1997 | GB |
2 347 766 | Sep 2000 | GB |
63103220 | May 1988 | JP |
64 86660 | Mar 1989 | JP |
1 200865 | Aug 1989 | JP |
5244629 | Sep 1993 | JP |
10-069553 | Mar 1998 | JP |
10191453 | Jul 1998 | JP |
11 066823 | Mar 1999 | JP |
11-313107 | Nov 1999 | JP |
2000 053276 | Feb 2000 | JP |
2000 066866 | Mar 2000 | JP |
2000 099079 | Apr 2000 | JP |
2000-207145 | Jul 2000 | JP |
2000 222160 | Aug 2000 | JP |
2000-312260 | Nov 2000 | JP |
2000 339237 | Dec 2000 | JP |
2001 076058 | Mar 2001 | JP |
2001 103233 | Apr 2001 | JP |
2001 118010 | Apr 2001 | JP |
2001-167024 | Jun 2001 | JP |
2001 236183 | Aug 2001 | JP |
2001 245028 | Sep 2001 | JP |
2001 249899 | Sep 2001 | JP |
2001-256161 | Sep 2001 | JP |
2001 285418 | Oct 2001 | JP |
2001 313913 | Nov 2001 | JP |
2001 344435 | Dec 2001 | JP |
2002-056023 | Feb 2002 | JP |
WO 9530199 | Nov 1995 | WO |
WO 9530199 | Nov 1995 | WO |
WO 9613814 | May 1996 | WO |
WO 9819478 | May 1998 | WO |
WO 0001138 | Jan 2000 | WO |
WO 0048384 | Aug 2000 | WO |
WO 0072499 | Nov 2000 | WO |
WO 0103040 | Jan 2001 | WO |
WO 0113307 | Feb 2001 | WO |
WO 0116853 | Mar 2001 | WO |
WO 0116853 | Mar 2001 | WO |
WO 0120509 | Mar 2001 | WO |
WO 0150446 | Jul 2001 | WO |
WO 0173644 | Oct 2001 | WO |
WO 0195267 | Dec 2001 | WO |
WO 0201451 | Jan 2002 | WO |
WO 0208926 | Jan 2002 | WO |
WO 0209435 | Jan 2002 | WO |
WO 02098107 | Dec 2002 | WO |
WO 02098124 | Dec 2002 | WO |
WO 03052580 | Jun 2003 | WO |
WO 03052581 | Jun 2003 | WO |
WO 03067496 | Aug 2003 | WO |
WO 03079279 | Sep 2003 | WO |
WO 2004006085 | Jan 2004 | WO |
WO 2004006155 | Jan 2004 | WO |
WO 2004006543 | Jan 2004 | WO |
Number | Date | Country | |
---|---|---|---|
20030184793 A1 | Oct 2003 | US |