Media acquisition, processing and distribution system for the internet

- Summit 6 LLC

The present invention, generally speaking, provides a broad-based solution for acquisition, processing and distribution of media objects including pictures (images), movies, videos, graphics, sound clips, etc via the Internet or the like. And specifically, it is a solution to such systems for use in applications wherein there are multiple originators of media objects that will be viewed in multiple web sites having different viewing requirements. A browser-based Aprepare and post@ tool prepares and submits media objects from inside a standard browser to a remote server. A Media Acquisition, Processing and Distribution (MAPD) system receives these media objects, processes them to meet specific requirements, and delivers them for integration into remote databases. MAPD system services include media object submission, processing, hosting and mirroring. The hosting service delivers a media object URL to a remote database, allowing the media object to be requested and served by the media object server. The mirroring service delivers the actual media object to multi-point remote databases to be stored and served by the customer.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CLAIM OF PRIORITY

This application is a continuation of U.S. application Ser. No. 10/736,285, entitled “MEDIA ACQUISITION, PROCESSING AND DISTRIBUTION SYSTEM FOR THE INTERNET”, and filed on Dec. 15, 2003 now U.S. Pat. No. 7,313,604, and which is a continuation of Application No. 09/440,461 now U.S. Pat. No. 6,732,162 entitled “Method of Providing Preprocessed Images for a Plurality of Internet Web Sites,” filed Nov. 15, 1999. These applications are hereby incorporated by reference.

BACKGROUND

1. Field of the Invention

The present invention relates to the acquisition, processing and distribution of media objects on the Internet and, more particularly, to such systems for use in applications wherein there are multiple originators of media objects that will be viewed in multiple web sites having different viewing requirements.

2. State of the Art

Much of the phenomenal success of the Web is attributable to its graphical nature. Literally, a picture is worth a thousand words. The capture of digital images has become routine, using digital cameras (still and video) and scanners. Nevertheless, although the handling of images by Web site creators has achieved a high degree of automation, for the average user manipulating and sharing digital images over the Internet remains a cumbersome and daunting process. Piecemeal solutions that have been devised for handling digital images require a level of sophistication that is beyond that of the ordinary user. Additionally, where automated solutions do not exist, time consuming and error-prone human and manual intervention are required to manipulate or share images. Such manual intervention for transferring a digital image may include, for example, first downloading a FTP program, then installing it, then running it and connecting it to an FTP server by typing the server name in the connection dialog, then navigating to the proper subdirectory, selecting the files to be uploaded, making sure that the program is in binary transfer mode, then sending the files. For the average user, such an involved process is a disadvantage.

Additionally, as technologies advance and casual users begin to experiment with other image types, such as streaming video, 3D objects, slide shows, movies, and accompanying sound files, the processes required to share these rich media types on the Internet becomes exponentially more complicated and prohibitive. As the realization of the Internet as an interactive, content rich medium becomes more and more a reality, the need for enabling the acquisition and distribution of rich content and media on the Internet will become the gating factor to its long-term success.

Once specific application of handling media over the Internet is in the real-estate market. It has been reported that over 25% of prospective residential home-buyers use the Internet as a means for locating properties of potential interest. There are many web sites dedicated to this purpose, including major real estate portals (e.g., Realtor.com and HomeAdvisor), national and regional brokerages, and individual realtor or broker web sites, to name a few. To be effective, these sites must provide rich visual content in the form of images of the properties listed. The image content can take the form of a single still image, multiple still images, slide shows comprised of a sequence of still images, immersive images (360 degree views), and video tours. These images can also have audio associated with them. The term Amedia object@ is used generically herein to refer to all types of such images, including audio and graphic objects.

While anyone can access the Internet through a browser, getting images posted to the Internet is a complicated process generally requiring a high degree of technical proficiency and specialized software tools. It is even more difficult when the media objects are of multiple types (still images, immersive images, video, etc.) and are created by different originators. For example, a real estate listing might include an image captured by a multiple listing service photographer, an immersive image captured by a professional photographer, and multiple still images taken by the real estate agent herself Add to this the fact that all of these media objects need to be displayed on multiple web sites that will have different viewing requirements. For example, a national real estate portal may only accept still images of a certain size and quality, say 300.times.200 pixels at a jpeg compression setting of 60%, while an agent=s individual web site may require a 390.times.260 pixel representation of the images at a different quality setting. Additionally, different browser versions have different viewing requirements for certain media object types. It is apparent that the problems associated with acquiring media objects from multiple sources and distributing them in the required form to multiple destination web sites are complex.

There are web sites today that offer a subset of this functionality specifically in the on line photo sharing market. These sites allow users to store their personal photographs, display them in a thumbnail or larger view and invite family and friends to view the pictures. These photo sharing sites let users upload digital pictures directly or have film processed and then posted to the web site. The purpose of these sites is to accommodate image uploads from many users within a proprietary system and where the image destination is intended to stay within that system.

The present invention teaches a Media Acquisition, Processing and Distribution (MAPD) system that solves many of the problems of handling media over the internet such as encountered in the real-estate market and photo sharing market. The Media Acquisition, Processing and Distribution (MAPD) system of the present invention has three major components: (1) media acquisition, (2) media processing and (3) media distribution (via hosting or mirroring). The purpose of the MAPD system is to enable multiple users without computer expertise to easily submit media objects that, after appropriate processing in accordance with pre-defined requirements, are viewable on multiple web sites.

The MAPD system of the present invention specifically handles image upload within an open system and that system is designed to process and distribute media objects outside of itself to be viewed in multiple web sites having different viewing requirements such as desired in the real-estate market. Additionally, the system of the present invention is designed such that the proprietary systems used in the photo sharing sites are unique to each web site and are not designed to be deployed across several web sites, markets or partners. Finally, the MAPD system of the present invention is designed to be used by varying and different web sites across many markets and partners. One important aspect of the MAPD system is its API or abstraction layer that specifically allows multiple web sites to integrate the MAPD system functionality,

SUMMARY OF THE INVENTION

The present invention, generally speaking, provides a broad-based solution for the acquisition, processing and automatic distribution of media objects via the Internet in a manner that does not require a high degree of technical proficiency. Specifically, the present invention provides a media acquisition, processing and distribution system for media objects submitted by multiple users for viewing within a plurality of destination web sites that have different media object viewing requirements. The invention provides means for each of the originators to associate one or more local media objects with a media object interface within a browser. Means are provided for storing information that defines the media object viewing requirements for each of the destination web sites. A remote server or servers receives the media objects from each originator and, based on the information stored in the database, processes the media objects in accordance with the media object viewing requirements of the destination web sites. In a hosting configuration, the remote server(s) send a URL to each destination web site that links the site back to the processed media object for viewing. In a mirroring configuration, the remote server(s) distribute the processed media objects to the destination web site servers.

In accordance with a further aspect of the present invention, within the MAPD client/server architecture, means are provided for intelligently processing the media objects both on the client and server, thereby enabling a more efficient use of bandwidth.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may be further understood from the following description in conjunction with the appended drawings. In the drawing:

FIG. 1 is a diagram illustrating information flow in accordance with one aspect of the invention;

FIG. 2 is a more detailed block diagram corresponding to the diagram of FIG. 1;

FIG. 3 is a diagram illustrating information flow in accordance with another aspect of the invention;

FIG. 4 is a more detailed block diagram corresponding to the diagram of FIG. 3;

FIG. 5 is a diagram of an exemplary Web page providing image acquisition functions;

FIG. 6 is a conceptual block diagram of the MAPD system network imaging system work flow and media processing engine scalability;

FIG. 7 is a system block diagram of the hardware partition for MAPD system network imaging system mirroring service;

FIG. 8 is a diagram showing the relationship of certain areas of the mirroring service;

FIG. 9 is a diagram illustrating three-tier partitioning of the network imaging system;

FIG. 10 is an entity/relationship diagram of the database of FIG. 9;

FIG. 11 is a diagram illustrating relationships between account, service and storage entities;

FIG. 12 is a diagram illustrating relationships between mirror service entities; and

FIG. 13 is a method called when a new media object arrives at a client site.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description describes a system for MAPD that enables the acquisition, processing and distribution of media objects from multiple users to multiple viewing web sites on the Internet. The term Amedia object@ as used herein refers broadly to any form of digital image or graphical file, including still images, PDF files, video images, audio, slide shows, etc. Although in the following description the submission and processing of still images is described in greatest detail, the same principles apply equally to media objects of all descriptions and apply equally to groups of multiple images.

The MAPD system of the present invention is for use in those applications wherein multiple users of the system have a need to submit media objects for viewing on multiple destination web sites that, in general, have different viewing requirements. The term, Aviewing requirements@ refers broadly to the various and unique ways media objects are displayed by web sites. Each web site places different technical requirements and constraints on the way that site uniquely displays media objects and therefore allows for viewing of media objects by visitors to the site. In accordance with the present invention, means are provided in the form of a Aprepare and post@ tool for each of the originators of media objects to associate one or more media objects with a media object identifier on a locally viewable web page, and for uploading the media object or objects to at least one remote server. A database stores information that defines the media object viewing requirements for each of the destination web sites. Within the MAPD client/server architecture, either on the client or server, the MAPD system processes the input media objects to meet the viewing requirements that are specified for each of the destination web sites. Such processing may take the form of image resizing, reformatting (changing the file format), encoding in the case of video, specifying media object storage location and browser version support just to name a few. The MAPD system then either delivers a media object URL to the destination web sites (hosting service) or transfers the processed media objects to the destination web sites ready for viewing (mirroring service). Specifically, the hosting service delivers a media object URL to a web page, allowing the media object to be requested by a customer web site and served by the MAPD system. The mirroring service delivers the actual media object, or other related data such as a media object URL, to a remote database to be served by the host of the destination web site.

Using MAPD system, end users can submit media objects in an immediate and intuitive manner. No technical sophistication is required. In particular, understanding technical terms such as JPEG, resolution, pixel, kilobyte, transfer protocol, IP address, etc., is not required, since the MAPD system automatically and transparently handles all of these tasks for the end user.

For on-line commerce customers dealing with high transaction load web sites, hosting is appealing. The MAPD system hosting service allows these customers to incorporate rich media (where rich media can be generally defined as combinations of different media objects such as pictures, movies, sound clips, etc.) into interactive web sites. The MAPD system hosting service provides this rich media to web sites without requiring that they bear the overhead costs associated with hosting the media objects on their own servers or without the technical expertise required to process and create rich media. Referring to FIG. 1, the MAPD system hosting service entails the following step-by-step process:

1. A media object is submitted by an end user (originator) dragging content into a MAPD system customer's web page. Media object ID data is also collected.

2. The media object may be pre-processed, such as converted, reduced, enhanced, etc., on the client within the MAPD client/server architecture.

3. The media object is uploaded into the MAPD system with ID information.

4. The media object is processed by the MAPD system in accordance with a profile that represents the requirements of the destination web sites. The requirement data is stored in a database and the media object is stored on a file server.

5. The MAPD system transparently returns a URL (representing the media object location) to the customer's web page. The media object source URL is embedded in the HTML in the customer's web page and returned to the customer's web server.

6. A hit by an end user (requester) to the MAPD system customer's web page where the media object source URL is embedded causes the customer's server to request insertion of the media object hosted from the MAPD system.

7. The requested media object is served by the MAPD system and integrated into the customer's web page in real time as the web page draws.

8. The end user's (requestor's) browser presents the finished web page to the end user. Transaction flow for the host service may be further appreciated with reference to FIG. 2. Transaction flow begins with a MAPD system customers web page having embedded in it the Aprepare and post@ tool. The Aprepare and post@ tool is represented on the web page as a media object identifier into which the user drags and drops a selected media object. The media object identifier may take the form of a Java applet, an ActiveX control, etc. The function of the identifier is to receive a media object, display a thumbnail or visual representation of the media object, and (optionally) perform preprocessing of the media object. A separate component may be used to upload the media object in response to the user clicking on a Send button. In an exemplary embodiment, clicking on the Send button activates a COM component of the Aprepare and post@ tool, called the Media Sender, for uploading the media object to the MAPD system (step 1).

The MAPD system includes processing capabilities in the form of a “media processing engine” and media object storage including a database and a file system (e.g., file server). When media objects are received, they are “logged” into the database, processed if required, and stored in the file system. As shown in step 2, a media object source URL (IMG SRC URL) is returned to the end user (originator) machine that was used to view the customer's web page. The IMG SRC URL is in turn sent with accompanying form data to the destination web site (step 3).

At the destination web site, a web page is created having HTML that contains the IMG SRC reference. For example, the web page may describe a real estate listing and the media object may be an image of the property being listed. When an end user requests to view the web page (a hit to the web page occurs), HTML containing the IMG SRC URL is delivered to the end user's (requestor's) computer from the destination web site. The media object itself is delivered separately from the MAPD system but at the same time the destination web page is served (step 5).

Some customers may prefer to host media objects on their own servers. In this instance, a MAPD system mirroring service is used. Referring to FIG. 3, the media object mirroring service entails the following steps:

1. A media object is submitted by an end user (originator) dragging content into a MAPD system customer's web page. Media object ID data is also collected.

2. The media object may be pre-processed, such as converted, reduced, enhanced, etc.

3. The media object is uploaded to the MAPD system with ID information.

4. The media object and data are received by the MAPD system and the data is stored in a database while the media object is stored on a file server.

5. A request is placed in the distribution queue notifying the servers that additional processing and preparation may then be required prior to sending.

6. The media object is processed in accordance with a profile that represents the viewing requirements of the destination web sites and the processed media object is distributed to the customer's web server (second location) or to other web servers (e.g., customer affiliate locations) approved by the customer.

7. The media object and ID information are received by the second location and are processed by the customer's servers so that the ID information is automatically stored in a database and the media object is stored in accordance with pre-determined instructions per the second location.

8. When an end user (requestor) hits the customer's web sites that contain media objects from the MAPD system, the web sites and media objects are served from the customer's web server.

Transaction flow for the mirror service may be further appreciated with reference to FIG. 4. As in the case of the hosting service, transaction flow for the mirroring service begins with a MAPD system customer web page having embedded in it the Aprepare and post@ tool, represented as a media object identifier. The end user drops a selected media object into the media object identifier and clicks on the Send button, sending the media object to the MAPD system central server (step 1). A return code is returned (step 2) to the COM component indicating whether or not submission has been successful.

On central servers within MAPD system, the media object is processed in accordance with a stored customer profile. The media object is then sent directly (step 3) to the customer's web site servers, where it is stored. A return code is returned (step 4) to the MAPD system indicating success or failure of media object transfer to the destination web sites.

As in the case of the hosting service, at each destination web site, a web page is created having HTML containing the IMG SRC reference. However in most mirroring scenarios, different from the hosting service, when an end user (requester) hit to the web page occurs, the web page and the media object are delivered directly from the customer's servers (steps 5 and 6).

Another implementation of mirroring may not send the media object itself to the MAPD system customer or customer affiliate locations. Other data that references the media object, such as the IMG SRC URL, may be distributed directly to the customer's servers and automatically integrated with web page data. The URL in hosting is returned immediately to the web page where the submission originates. The URL in mirroring is forwarded to another server (second location) not related to the web page where the submission originates. In this instance, the media object will be served from the MAPD system.

Referring to the real estate industry example stated earlier, FIG. 5, is an example of a realty web page featuring the described Aprepare and post@ functionality of the MAPD system. The end user (originator) drags and drops photos into media object identifiers and selects appropriate captions for the media object, e.g., living room, family room, etc. The captions may be typed in or selected from menus. The end user also supplies identifying information, in this instance the multiple listing service number. When the end user clicks the Send Photos button, the media objects are processed and transported immediately according to the configuration of the tool and in accordance with the hosting service or the mirroring service previously described.

There are three ways media objects become associated with a media object identifier. The first is through a “drag and drop” behavior where the user clicks on a media object to select the one they want to submit. The media object is then dragged to the media object identifier Releasing the mouse button associates the media object with the media object identifier. This behavior is allowed in web browsers that support drag and drop functionality. The Aprepare and post@ tools enable these browsers to accept media objects via drag and drop by providing the media object identifier as an ActiveX component.

The second way to associate a media with the media object identifier is to click on the media object identifier to browse for media objects, then select the media object of choice. This method is made available for web browsers where the media object identifier needs to be a pure Java component. (Such as “signed applet browsers” like Netscape Navigator). In this instance, the user may be asked to choose a media object in a similar manner as when choosing a file to be opened, either by graphical navigation or by specifying a path name. For example, a prompt associated with the media object identifier may be displayed prompting the user to click within the media object identifier. Clicking within the media object identifier brings up a browse dialog. Using the browse dialog, the user selects the desired media object, which is then placed in the media object identifier. The Aprepare and post@ tools will generate a visual representation or thumbnail of the media object, a feature currently not available in signed applet browsers.

A variation of the second way to associate a media object with the media object identifier involves support for older browser versions, also referred to as minimal browsers. Browsers in this category include versions 2.X and 3.X. Also considered part of the minimal browser category are all browsers used on the Macintosh platform. To accommodate complex file sending requirements from within minimal web browsers, the MAPD system implements media object sending through the alternate HTTP channel using the HTML<FILE>element. Once the end user (originator) clicks to send the media object, it is converted to a multi-part mime format for sending to the MAPD system central servers.

The Aprepare and post@ tool also supports a batch interface, allowing a plurality of media objects to be Abatched@ and submitted simultaneously. Most users who are using media objects work with several media objects at the same time versus one media object at a time. Therefore, it is desirable to submit 5, 10 or 25 media objects for processing and distribution at one time for efficiency without having to repeat steps for each of the media objects. An example is a professional photographer who may need to submit several media objects at the same time to several destination web sites. Quickly clicking and dragging a plurality of media objects for submission with the MAPD system is as easy and efficient as submitting one media object.

The description of the present invention thus far has discussed that a media object can be obtained from a single source or from multiple origination sources and that a media object can be transmitted to a single destination and to multiple destinations. The point-to-multi-point distribution is a key advantage of the present invention. This multi-point distribution may be accomplished using distribution lists stored at MAPD system central servers. Distribution lists stored within the MAPD database provide a way for MAPD system customers to specify which of their affiliate web sites get mirrored copies of images submitted through the mirror service distributed directly to them. In technical terms, a distribution list is a named entity that binds a group of destination web sites with a customer via the mirror service. When a media object arrives from a customer on the mirror service, the MAPD system uses the customer's named distribution list to establish which web site servers (i.e., customer affiliate locations) receive copies of the media object. FIG. 12 shows this point-to-multi-point distribution relationship as it is managed by the service link and the distribution list, as will be described herein below.

Each entity in a distribution list has an associated client profile that identifies the remote servers for the destination web sites, the delivery method and any number of processing filters to apply to the media object before sending. Filters are used to control the attributes of media object content delivered to clients, which are tied to the customer profiles. Filters can also be employed to increase functionality within the MAPD system architecture. The attributes may include dimensions, quality and type of media object delivered (i.e., slide show, video) etc. Filters are applied to inbound media objects or outbound media objects or both and are used for both the MAPD system host and mirror service.

More particularly, filters may be associated with both services and clients. Service filters are applied as the media object is received. For mirror services, the service filter is applied as the media object arrives, before it is stored. As the mirror service distributes the media object to clients, the appropriate filter for each client is applied before the media object is sent. For example, a particular mirror service may convert all images to 320.times.200 jpeg before storing them, and then convert those to the specific requirements of each client on its distribution list prior to transporting the images. For the hosting service, the service filter is applied as the media object is received, and then the appropriate client filter is applied to the result before the media object is stored. Clients and services can share filters. If no filters associated with a given service or client handle a particular file type, then media objects with that file type are not converted for that service or client.

Depending on the particular service, image processing may be performed primarily at the client using the Aprepare and post@ tool, primarily at a MAPD system central server, or may be performed at both, some at the client and some at the MAPD system central server. In the case of the host service, for example, image requirements may be specified within a particular instance of the Aprepare and post@ tool as it is integrated into the web page of a particular customer. Processing the image within the Aprepare and post@ tool avoids unnecessary data transfer. In the case of the mirror service, for example, more than one processed image may be produced from the original image submission. Image processing may therefore be performed primarily at the central server. Nevertheless, basic sizing and resampling may be performed at the client, avoiding the circumstance in which a novice user attempts to upload a huge image file, causing their network connection to “choke.”

Although media processing will often involve sizing and formatting of images, any of various kinds of media processing may be performed by the MAPD system media processing engine, for example enhancements and effects, text and graphic layering, image stitching, streaming video encoding, producing zoomable images, cropping, rotating, etc.

For instance, in one embodiment, resizing and format conversion of still images may be performed on either the client or central server. In another embodiment video image encoding may be performed on either the client or central server. In still another embodiment, still images are resized by determining on the central server a maximum still image size for all destination web sites such that the still images are resized no larger than the maximum size on the central server. In this case, resizing of the image may also be performed on the client.

Furthermore, although the MAPD systems have been described as having a central server, any suitable server architecture may be used to support MAPD system services One type of architecture that is complementary to MAPD system services is a distributed server architecture and global content distribution service offered by Akamai Technologies, Inc. of Cambridge, Mass. under the name Freeflow.™. The Freeflow content distribution method allows content providers to ensure rapid access to their sites without needing to maintain burdensome and expensive content distribution infrastructure, using a global network of specialized servers and software that controls how content is distributed throughout the network. Rapid access is achieved by moving bandwidth-intensive content closer to the user. Web site performance is optimized by migrating content according to its popularity while taking into account changing network conditions and fluctuations in traffic. The MAPD system may optionally pass information to this distributed server environment or others, as needed, in order to optimize delivery of the media content the MAPD system creates.

Referring to FIG. 6 therefore, a block diagram of the MAPD system network imaging architecture is shown. A MAPD system Media Acquisition and Distribution layer (MAPD system central server) provides for media object processing in accordance with customer profiles, and for multi-point distribution as described. Above the MAPD system Media Acquisition and Distribution layer may be various service layers including zoomable images, streaming video encoding, image stitching, slide shows, text and graphic layering, enhancement and effects, sizing and formatting. The architecture is easily extended by added new services as needed. Below the MAPD system Media Acquisition and Distribution layer is the optional distributed server infrastructure, which may be a global hosting infrastructure such as that of Akamai or any other advantageous server infrastructure partner.

Recognizing that any of various server infrastructures may be used, the MAPD system central hardware architecture in accordance with an exemplary embodiment of the invention will be described. Referring to FIG. 7, an example of how the MAPD system mirroring system hardware could be partitioned is detailed. A cluster organization is followed that uses three clusters, an inbound cluster, a file server cluster and an outbound cluster. The file server cluster is attached to a MAPD system database, or repository. Web submissions from the MAPD system Aprepare and post@ tool are received by the inbound cluster. Within the inbound cluster, the MAPD system repository is consulted in order to form a distribution request, which is sent to a distribution queue at the outbound cluster through a remote interface. Within the outbound cluster, distribution requests are polled and processed by picking up items from the distribution queue and building a distribution list based on the corresponding customer's profile. For each destination in the distribution list, a distribution server within the outbound cluster makes a socket connection to the second location and delivers the media object.

Because of the ability to have a media object sent to multiple destinations, the number of outbound transactions is potentially far greater than the number of inbound transactions. To facilitate the transfer of media objects, inbound media processing is separated from outbound media processing. This separation is accomplished by the MAPD system distribution queue. In an exemplary embodiment, the MAPD system distribution queue is a runtime Remote Method Invocation (RMI) object shared between multiple MAPD systems and outbound distribution processors. Referring more particularly to FIG. 8, when a submission arrives for the mirror service, it is received by an inbound mirror processor. The inbound mirror processor stores the submission within the MAPD system repository and adds a distribution object to the distribution queue. The outbound media distributor constantly polls the distribution queue for available items and when one is available, removes it from the queue and carries out the distribution. A single inbound submission to the mirror service typically results in multiple distributions to customer affiliate locations, since the purpose of the mirror service is to allow MAPD system customers to distribute media to that customer's affiliates using a distribution list. Once the outbound media distributor pulls an item off the distribution queue, it is responsible to build a distribution list of all intended recipients and carry out the transfer of media.

A ClientHoldingQueue object may be provided as a holding area for transactions destined for a customer which is unreachable. These transactions are queued as distribution objects until the customer becomes reachable and they can be sent. A ClientHoldingQueue contains a queue of distribution objects similar to the primary queue. It has its own thread to process that queue and it contains the ability to ping its customer as a way of knowing when the customer comes back on line. ClientHoldingQueues are created whenever a normal transmission fails and they go out of existence as soon as they are able to deliver all of their queued objects.

The MAPD system may be realized in two tiers (traditional client/server), three tiers, or, more generally, N tiers. A three-tier implementation in accordance with an exemplary embodiment of the invention is illustrated in FIG. 9. The three-tier partitioning includes a client tier, an application tier and a database tier. Beside tier boundaries, also identified are IP (internet protocol) boundaries. Communication across IP boundaries occurs, for example, through the Internet using the Internet Protocol (IP). A vertical IP boundary separates client (sources) from consumers (destinations). A horizontal IP boundary separates (browser-based) client from servers.

In operation, submission tools (Aprepare and post@) are used to submit media to a central server where the media objects are processed as necessary, stored, and distributed, either by hosting or mirroring. In the case of mirroring, the outbound servers send the media object to a mirrored client repository, causing the media object to be stored within a mirrored database. The media object is accessed from the mirrored client repository using distribution tools and viewers, in particular web browsers. Such access may be accomplished, for example, through Active Server Pages (ASP) or Cold Fusion (CF) for server-side page generation. In the case of hosting, the media object is accessed directly from the MAPD system central servers, using the same or similar techniques, for example.

Referring to FIG. 10, the principal MAPD system database system entities (tables) and their relationships are shown in accordance with an exemplary embodiment. Appendix A details the associated database tables. The Account table contains primary account information for each MAPD system service customer. There is only one account record for each MAPD system customer. The ClientProfile table contains profile information used to control customer access to MAPD system services. A MAPD system customer will typically have a single client profile, but may in some instances have more than one customer profile, e.g., if a customer has multiple business units, one or more of which subscribes to MAPD system services. The user table defines users with access rights to account information for a given customer.

The Distribution Link table is used to identify a distribution list associated with the mirror service via a ServiceLink record. The ServiceLink.Distribution-Listname and the ServiceLink.ServiceLinklD are used to identify all the DistributionLink records that are targeted for a media distribution to a second location. Each DistributionLink record identifies a profile (DistributionLink.ProfileID) which identifies the second location for the distribution as well as media distribution characteristics (e.g., filter, applications, etc.).

The Server table identifies various MAPD systems used to process inbound traffic, outbound traffic and media storage. The ErrorLog table records errors in inbound and outbound traffic processing.

The StorageVolume table contains descriptions of MAPD system central server volumes used for media storage. A given service uses a StorageVolume record to identify the server and volume where media will be stored. The physical and virtual paths used to identify the folder location for media items are identified via a StorageLink record in the StorageLink table. The StorageLink table contains physical and virtual folder locations within a given StorageVolume. It is used for identifying the storage location of media items within the MAPD system central server.

The MediaMaster table contains one entry for each unique media element stored in the MAPD system repository. The MediaType table identifies classes of media associated with MAPD system services. The Industry table describes industries associated with MAPD system customers. It may be based on the NAICS industry codes standard.

The Service table describes all available MAPD system services. The ServiceLink table contains associative records which identify customer-specific service characteristics or properties associated with a given service. The Filter table contains filter records. Each filter record defines activities or constraints applied to media. The FilterLink table contains associative records which identify filters associated with a given customer.

Further details concerning MAPD system filters and their implementation is found in Appendix B.

As illustrated in FIG. 11, in general terms, ServiceLinks link an Account to one or more services and ultimately, through StorageLink and StorageVolume entities, to a physical media storage location.

In the case of the mirror service, DistributionLink and ClientProfile entities control the distribution process as illustrated in FIG. 12. When a submission arrives for the mirror service, it is stored within the MAPD system central repository and mirrored to a customer (second location) or customer affiliate locations. The second location and the affiliate locations use MAPD system software, particularly a MAPD system ClientReceiver, to process and store media objects and data. When the media object submission arrives the userID and password are used to lookup the associated Account (1) record. Once the account has been identified, the Accountld and service name (in this instance “MIRROR”) are used to find the ServiceLink (2) record associated with the account for the mirror service. The ServiceLink record identifies the distribution list to mirror the submission to. Given a ServiceLinkID and a DistributionName, the DistributionLink (3) table is used to identify the target ClientProfile (4) records used to mirror the submission. The ClientProfile (4) record contains the IP address and port of the mirror site (second location).

The MAPD system communicates with clients to send mirrored media objects through TCP/IP sockets. A MAPD system ClientReceiver is a software agent that sits at the customer site and waits (e.g., on a pre-defined port) for connections from the MAPD system. In an exemplary embodiment, the port is stored with the customer profile in the MAPD system repository and fetched by the media distributor to make the customer connection. Other delivery methods may be used instead of sockets, e.g., HTTP filesend, FTP push, e-mail etc.

In order to effectively use the media objects, to match media objects with customer's databases, customers need to be able to automatically integrate incoming media objects (received from MAPD system distribution servers) into their existing database structures. In an exemplary embodiment, a method shown in FIG. 13 is called when a new media object arrives at the customer site (remote destination web site) via the MAPD system ClientReceiver. The ClientReceiver automatically takes the media object that has been sent from MAPD system central and stores it to disk (i.e., line “String filename,” in FIG. 13). The storage location is specified in a properties file at the customer's receiving site. The ClientReceiver also passes the information about the media object (unique ID number, sequence number, description fields, etc.) to a function which can be modified at the customer's receiving location as well (i.e., lines “String mediaGroupID)”, “String media ExtID”, “int seqNum”, “int industry Code”, “String desc1”, “String desc2”, and “String desc3”, in FIG. 13). The MAPD system provides a function that can be modified to provide the customer's own database with the information the MAPD system passed to the function. Once the new media object has been integrated into the customer's database, it can be immediately used in server-side page generation as a page is requested by a web site visitor.

The function typically stores the media object information in a proprietary database (the MAPD system customer's database). The body of the function is commented out so the customer or the customer's affiliate locations can fill it out with specific instructions (source code to the Java class that contains this unction is provided by the MAPD system). The function parameters reflect what was provided during the media object submission using the image submission tool.

MAPD system customers who subscribe to the “mirror” service specify their own servers or affiliate server locations who are approved to receive mirrored copies of the media objects or information about the media objects, such as IMG SRC URL, from the MAPD system. To specify which affiliates receive mirrored information, a distribution list is set up and a small profile is entered for each affiliate in the database. The initial steps for setting up a customer for the mirror service are:

1. A registration form is completed that contains standard entries such as an ID, password, full name, address, phone, e-mail, fax, etc. MAPD system central server uses this information to establish a service record(s) for the customer account.

2. Distribution list forms are completed for each approved affiliate or customer server and appropriate information such as IP address to send images to, transformations to be performed on media objects etc. MAPD system central server uses this information to establish a profile for each affiliate,

The profile contains the preferred delivery method (ClientReceiver, e-mail or FTP for the mirror service.) For delivery by the ClientReceiver, the entry contains the IP address and Port for the ClientReceiver.

The MAPD system ClientReceiver is provided to the customer and, in an exemplary embodiment, is a Java application or process that runs on any platform supporting the generic JDK 1.1 or later versions. The ClientReceiver sits on one of the customer's remote web servers or one or more customer's affiliate locations per the customer's designation. When media objects are received by MAPD systems from the Aprepare and post@ media submission tools, they are processed according to the customer's specifications as described earlier and forwarded to any approved affiliate locations by making a socket connection to ClientReceivers installed on the customers behalf.

In the case where the affiliate locations intended for mirrored delivery cannot install the ClientReceiver or they prefer delivery by a different method, the media object submissions can alternatively be forwarded via other methods such as FTP or by e-mail. The MAPD system is set up to specify delivery instructions by any number of methods including but not limited to ClientReceiver, FTP or e-mail on an affiliate-by-affiliate basis. For example, if Customer #1 wants media objects to be sent to 3 affiliates in a distribution list called “PrimaryAffiliates” (and there can be more than one distribution list), tables at MAPD system central may be set up for delivery by ClientReceiver to the first affiliate, FTP to the second and e-mail to the third. The MAPD system can be configured to have unique and varied distribution lists per the customer's instructions.

The following Appendices C and D describe in greater detail the program architecture for the Image Container (media object identifier) and COM (media sender) components used in an exemplary embodiment of the invention. Appendix E is a general description of the ClientReceiver class used in an exemplary embodiment of the invention.

Account Table Description: This table contains accounting information for each MAPD service partner. There is only one account record for each MAPD partner. Field Name Data Type Length Description AccountID varchar2 20 Unique Account ID AccountName varchar2 50 Textual name of account Password varchar2 10 Used for log in Address1 varchar2 80 Address2 varchar2 80 City varchar2 50 State varchar2 25 Zip varchar2 10 Country varchar2 20 PrimaryContract varchar2 50 Phone varchar2 20 Email varchar2 50 Website varchar2 80 Fax varchar2 20 Industry Number 5 industry associated with this account. UserLifeSpan Number 11 Users of this account live this long by default

ClientProfile Table Description: This table contains profile information used to control client access to MAPD services. A MAPD partner may have more than one client profile (though there is only one typically). This would be the case if a partner has multiple business units, one or more of which subscribes to MAPD services. Field Name Data Type Length Description ProfileID Number 11 Auto-incremented Unique ID ClientAccount varchar2 20 AccountName link to Account Table (e.g., Pacific Union) ProfileName varchar2 20 Textual name for this profile (e.g., PacUnion1) ClientIndustry Number 5 Industry type for this client. Media that come in from this client and are (by default) associated with this industry. ReceiverHost varchar2 80 Client media receiver URL ReceiverPort Number 5 Port to receive on LocalPort varchar2 5 Use this port for outbound traffic - currently not in use (defaults to port 0) DeliveryMethod varchar2 80 Class file of primary delivery method AltDeliveryMethod varchar2 80 Class file of alternate delivery method DeliveryEmail varchar2 50 Email address for Delivery Method (email) EmailFormatTemplate varchar2 2048 Text template for mirroring images via email AutoLogID varchar2 50 server-to-server connection id AutoLogPassword varchar2 10 server-to-server connection password DefAccessRights Number 4 default access rights for this profile

This table is used to identify a distribution list associated with the MIRROR service via a ServiceLink record. The ServiceLink.DistributionListname and the ServiceLinkID are used to identify all the DistributionLink records that are targeted for a media distribution. Each DistributionLink record identifies a profile (DistributionLink.ProfileID)which identifies the target server for the distribution as well as the media distribution characteristics(e.g., filter application, etc.)

DistributionLink Description This table is used to identify a distribution list associated with the MIRROR service via a ServiceLink record. The ServiceLink.DistributionListname and the ServiceLink.ServiceLinkID are used to identify all the DistributionLink records that are targeted for a media distribution. Each DistributionLink record identifies a profile (DistributionLink.ProfileID) which identifies the target server for the distribution as well as media distribution characteristics (e.g., filter application, etc.) Field Name Data Type Length Description DistributionID Number 6 Auto-incremented Unique ID ServiceLinkID Number 4 Groups distribution items by ServiceLinkID ProfileID Number 11 Identifies the target ClientProfile record DistributionName varchar2 20 Distribution List name - groups distributions by name for a given account and service (via a ServiceLink record)

StorageLink

Description:

This table contains descriptions of MAPD Central server volumes used for media storage. A given service Uses a StorageLink record to identify the server and volume where media will be stored. The physical and virtual paths used to identify the folder location for media items are also identified.

StorageLink Description: This table contains descriptions of MAPD Central server volumes used for media storage. A given service uses a StorageLink record to identify the server and volume where media will be stored. The physical and virtual paths used to identify the folder location for media items are also identified. Field Name Data Type Length Description VolumeLinkID Number 11 Auto-incremented primary key ServerName varchar2 30 Server name (e.g., DELL) VolumeName varchar2 30 Name of Volume within MAPD (e.g., DriveC - \\DELL\DriveC) IPAddress varchar2 80 IP address of server associated with this volume PhysicalDir varchar2 255 Physical location within volume (e.g., \inetpub\wwwroot\ mywebserver) VirtualDir varchar2 255 Virtual directory (e.g., \PWIS\images\hostimages) Status Number 2 Status: 1 = active, 0 = inactive

MediaMaster Table Description: This table contains one entry for each unique media element stored in the MAPD repository. Field Name Data Type Length Description MediaID Number 11 Auto-incremented Unique key MediaGroupID varchar2 150 Industry-specifc ID (e.g., MLS number) MediaExtendedID varchar2 100 Media id qualifier such as zipcode MediaSequenceNum Number 4 Identifies media item within a set (e.g., MediaGroupID + ExtendedID + SequenceNum) MediaType Number 3 stored media format (1 = jpg image, 2 = fpx image, 3 = gif, 4 = panorama) OrigName varchar2 80 Original name of media item at point of submission (i.e., the physical file that was sent - even if a temp file) Does not include path. MediaName varchar2 80 Name of item stored on MAPD server. Does not include path. MediaLocation Number 4 foreign key to StorageLink. IMPORTANT NOTE: Do nor modify the locations inside a StorageLink record; since old media items will point to an invalid location. If new storage locations need to be assigned to a service, then create a new torageLink record and use that. ServiceID varchar2 20 Service requested which resulted in this item being created IndustryCode Number 5 Item is associated with this industry (NAICS code) - 0 means unspecified Description1 varchar2 255 arbitrary values (e.g., room name for a real estate image) Description2 varchar2 255 arbitrary values Description3 varchar2 255 arbitrary values DateCreated Date/Time date media item created ClientID varchar2 20 ID of partner who initiated media upload SubmittorID varchar2 50 ID of person who submitted media item SubmittorPassword varchar2 10 Password of person who submitted media item AccessRights Number 4 default 1 = Public (anyone subscribing to Mirroring has access). 0 = submittor and affilitates only HasThumb Number 1 1 if there is a thumbnail associated with this item ImageWidth Number 6 Width of media image ImageHeight Number 6 Height of media image

Service Table Description: This table describes all available MAPD services. Field Name Data Type Length Description ServiceID varchar2 20 Unique ID identifying the service ServiceType Number 4 Identifies service type for this industry group DefaultServerID varchar2 20 default MAPD server ID for this service DefaultPort varchar2 5 default MAPD port for service DefaultStorageFormat Number 5 default stored format (e.g., FPX) DefaultFilter Number 5 default filter for client delivery

Filter Table Description: This table contains filter records. Each filter record defines actives or constraints applied to media. Field Name Data Type Length Description FilterID Number 5 Media filter ID FilterClassName varchar2 80 Java class name of filter. MediaFileType varchar2 20 Type (file extension) of media to which this filter should be applied. Convert Number 1 if the media is to be converted to another type (file extension.) 0 otherwise. DestinationFileType varchar2 50 Output type if above is yes. DestinationQuality Number 11 Output quality (currently only applies to jpeg files.) Resize Number 1 if the media is to be resized. 0 otherwise. AllowExpand Number 1 if the media can be increased in size. 0 Otherwise DestinationWidth Number Output width of media. DestinationHeight Number Output height of media. Template varchar2 255 Fully-qualified path of conversion template (if used) TemplateClass varchar2 80 Class which implements positioning logic (obsolete?)

Industry Table Description: This table describes industries associated with MAPD partners. It is based on the NAICS industry codes standard. Field Name Data Type Length Description IndustryID Number Auto-incremented. Any client may be associated with multiple industries MajorIndustryCode Number Major Industry code - from US Dept of Labor (example 65 = Real Estate) MinorIndustryCode Number Minor code (eg. 653 = Real Estate Agents and Managers) IndustryName varchar2 50 Name or type of industry (e.g., Auto)

ServerControl Table Description: This table identifies the various MAPD servers used to process Inbound traffic, Outbound traffic and media storage. Field Name Data Type Length Description ServerControlID Number 4 Unique id ServerType varchar2 16 type of server IPAddress varchar2 80 IP address of this server ControlPort varchar2 50 server port address Status Number 2 status: 1 = active, 0 = inactive

ServiceLink Table Description: This table contains associative records which identify client-specific service characteristics or properties associated with a given service. Field Name Data Type Length Description ID Number 4 Unique ID for this association AccountID varchar2 20 account id associated with this linklink to ClientProfile table ServiceID varchar2 20 link to Service Table ProfileID Number link to ClientProflle table - contains the default profile associated with this account IndustryCode Number US Department of Labor Major industry code (NAICS) Priority Number 3 default = 1 (highest). this is used to decide how/when to forward media associated with this service to the linked client OriginatorSend Yes/No default = false, if true, media for this service sent by this originator end its affiliates is distributed only to the originator. Answers the question: Whom do you want to allow to receive this media item? ForeignSend Yes/No Default = true, if false, this client only wants media for this service which originated from this client and its affiliates. Answers the question: Whose media do you want to receive? DistributionList varchar2 2000 List of semi-column separated named distribution lists. Each item organizes a list of destinations, with each destination being associated with a client profile containing a delivery method, IP addresses, etc. SubmitSelList varchar2 2000 Image well default selection list for this client's service StorageLinkID Number Link to storage locator record StorageGenerator varchar2 50 class name of storage constructor class MaxMediaPerUser Number 10 maximum submissions for a single user of this service SecurityClass varchar2 50 class name of security class. Run on server at submission reception time. MediaLifeSpan Number Lifespan of media received on this service

FilterLink Table Description: This table contains associative records which identify filters associated with a given client. Field Name Data Type Length Description FilterLinkID Number Auto-incremented Unique ID ServiceLinkID Number 4 Appy filter to media inbound to this service ClientProfileID Number The filter below is associated with this client FilterID varchar2 64 comma-delimited list of filterids from filter table

ErrorLog Table Description: This table records errors in Inbound and Outbound traffic processing. Field Name Data Type Length Description ErrorLogID Number 11 Auto-incremented Unique ID TimeOfOccurrence Date Date & Time of occurrence Media Number 11 ID of media item processed Host varchar2 50 Host ID of inbound/outbound transaction Port Number 5 Port error occurred on ClassName varchar2 50 Java classname where error occurred FunctionName varchar2 50 Java function within class Severity varchar2 50 severity code Reason varchar2 128 reason for error Response varchar2 128 action taken in response to error Context varchar2 255 general description Exception varchar2 255 java exception

ServerControl Table Description: This table contains the location (IP Address) and execution status MAPD server processes. It is used to register servers so they may receive external communication commands (see External Commands for details.) Field Name Data Type Length Description ServerControlID AutoNumber Unique ID ServerType Number Apply filter to media inbound to this service IPAddress Number The filter below is associated with this client ControlPort Number Link to filter table Status Number 0 = not running, 1 if currently running

User_r Table Description: This table defines users with access rights to account information for a given partner. Note that the names User_r and Privileges_r are named as such because Oracle reserves the names User and Privileges within its namespace. Field Name Data Type Length Description UserID AutoNumber Unique ID FirstName varchar2 20 e.g., Fred MiddleInit varchar2 3 LastName varchar2 20 User_r varchar2 50 e.g., freds - up to 10 alpha numeric Password varchar2 10 up to 10 alphanumeric AccountID varchar2 20 link to account table OfficeID varchar2 20 Phone varchar2 20 contact phone number Email varchar2 50 email address Privileges_r Number 5 Administration SupportLevel Number 5 access rights CreateDate Date date user added to system MaxSubmissionsAllowed Number 50 This user can only have 50 active media items. if −1, then use default from servicelink LastAccessDate Date Last time logged on SendEmailUpdates Number 1 marketing stuff ShareContactInfo Number 1 marketing stuff

DistributionLink Table Description: This table defines members of a distribution list. A distribution list is a named entity (DistributionName). A list is a collection of DistributionLink all with the same DistributionName and same. Field Name Data Type Length Description DistributionID Number 6 Unique ID ServiceLinkID Number 4 Groups distribution items by ServiceLink ProfileID Number Identifies the target client profile DistributionName varchar2 20 Distrirbution List name - groups distributions by name for a given account and service (via ServiceLink)

Maintenance Table Description: This table is used to schedule database object and media retirement activities. Field Name Data Type Length Description RetireNextRun Date Date/time of next retire run RetireIntervalDays Number Number of days between retire runs RetireLongFileNumber Number Next log file number to write retire log to TempDate Date temporary date/time storage for runs

Transaction Table Description: The ‘Transaction’ database table contains one entry for each transaction that is in progress or has taken place. Field Name Data Type Length Description TransactionID Number Unique identifier generated by database State Number 5 Current transaction state - UNKNOWN, RECEIVED, QUEUED, HELD, SEND, FAILED MediaID Number Identifier of media item being received or sent Bytes Number Number of bytes received or sent in this transaction ServiceLinkID Number 4 ServiceLink under which this media was received ClientProfileID Number Destination (outgoing transactions only) TimeCreated Date Database time stamp when this transaction was created TimeCompleted Date Database time stamp when this transaction was

Database Considerations for Filters

Each service and each client has a set of 0 or more filters associated with it. Filters are represented as entries in a ‘Filter’ Table. Filters are associated with services or clients by entries in a ‘FilterLink’ table. Each FilterLink entry maps one filter to one clientservice and/or one client. Note that clients services and clients can share filters.

Filter table entries specify the name of a filter (a Java class, see Extensibility below) and other attributes required by the filter such as output dimensions for an image filter. They also indicate the file type (extension) to which they are to be applied. This is either a specific file extension, or ‘ALL.’ ALL means the filter is the default for any media with a file type which the filter handles, (see handlesType below).

For example, a filter class called ‘soundFilter’ handles .wav, and .riff extensions. An entry in the Filter Table defines filter 7 as class soundfilter and as applying to all .wav files. Filter 8 is also a soundFilter and defined to apply to ‘ALL’ files. Entries in the FilterLink Table associate both filter 8 and 9 with Client X. A wav file is destined for Client X. The system looks at the filter set for Client X, sees filter 8 which is a soundfilter, (handles wav files as well as others), and sees that filter 8 has wav listed as the type to which it is to be applied. Filter 8 will take precedence over filter 9 which is also a soundFilter, but is configured for ‘ALL.’ A specific type match will always take precedence over ‘ALL.’ Any riff files bound for Client X will be handled by filter 9. If no filters associated with a given service or client handle a particular file type, then media with that file type are not converted for that service or client.

Filter Extensibility

Filters are implemented as java classes. All filter classes provide a common interface, which includes the following functions:

    • Constructor—takes a database filter table entry id as a parameter and initializes an instance of this filter with the attributes specified in that entry.
    • handlesType—given a file extension this returns true if the filter handles media with that extension
    • convert—this performs the conversion.
    • Compare—returns a comparison value between two filters. This is used to sort media during distribution for efficiency. By ordering destination clients for a particular outbound media according to the filters associated with those clients, identical sets of filters will be adjacent in the order. This means that the media need only be converted once per set of identical filters.

Filters are loaded dynamically, which means new filters can be developed, shipped, and installed while the system is running.

EXAMPLE

Take the case where client X wants to receive all images as jpg files scaled to 320×240 with a quality of 90. To do this, we create the following filter in the filter table:

    • FilterClassName=ImageFilter
    • MediaFileType=ALL
    • DestinationWidth=320
    • DestinationHeight=240
    • DestinationQuality=90

Next, we create an entry in the FilterLink table as follows:

    • ClientProfileID=client X's Client Profile ID
    • FilterID=ID of filter created above

Note that the ImageFilter is implemented in ImageFilter.class. It handles jpg files among others. In the example above, it will be used to convert all file types that it handles to jpg files with specified dimensions and quality.

PWTImgCont.ocx - Activex Image Container Component Interface Name Type Definition Signature ScaleImage function Scales an ScaleImage( image in     destWidth As Integer, place or to a     destHeight As Integer, temporary     destQuality As Integer, file     ′0-100     generateOutputFilename     As Boolean ′create     tempfile) As String DelTempFile sub Deletes DelTempfile( ) temporary file created with ScaleImage fileName String Name of file fileName as String property shown in image well imageName String String value imageName as String property from image caption box

PWISFileSend.dll - COM component for sending media to server Interface Name Type Definition Signature SubmitMediaRequest sub Transfers image SubmitMediaRequest(     UserID As String, ′partner UID     Password As String, ′partner password     ServiceType As String, ′“HOST” or “MIRROR”     IndustryCode As Integer, ′e.g., 65 real estate     MediaType As Integer, ′1=image 2=video 3=sound     OpCode As Integer, ′1=Add, 2=Update, 3=Delete     IPAddr As String, ′Destination IP address     filename As String, ′File to send     MediaGroupID As String, ′Used to build unique key     MediaExtendedID As String, ′“”     MediaSequenceNum As Integer, ′“”     Desc1 As String, ′255 chars     Desc2 As String, ′255 chars     Desc3 As String) ′255 chars retCode read-only Return code from retCode as Integer integer SubmitMediaRequest property Scaled integer Indicates whether image Scaled as Integer property was pre-scaled before being sent ServerRetString String Return value from ServerRetString as String property SubmitMediaRequest. If call made on HOST service, this string contains the IMG SRC url

Usage Example (VB Script) tempFileName = ‘ scale the image object DragImage1.ScaleImage(320, 240, 89, 1) ‘DragImage1’ result = ‘ transmit to mad central UpIHandler.SubmitMediaRequest( UserID, Password, ServiceType, 0, 1, 1, ipAddress, tempFileName, mlsNum.Value, zipcode, imageCount, title, desc2, desc3) DragImage3.DelTempFile ‘delete the temp file

Client Receiver Name Type Description Location Constraints ClientMediaReceiver.java Java class Client Media Handler. Java Source: JDK 1.1 Handles incomming MAD MADS\ClientReceiver compatible. Runs media distributions. Media Classfile: under any arrive as a binary stream MADS/ClientReceiver/ operating with an encoded Classes environment descriptive property set. support that Invokes an instance of the version of the ClientDBBinder to enable JDK (e.g., NT, dats integration at client Windows 9x, site (see below). Solaris, Mac, etc.) ClientDBBinder.java Java class This is a reference Java Source: We cannot implementation (with MADS\ClientReceiver integrate directly source code) of a into the client's component which is used Classfile: database unless to integrate incomming MADS/ClientReceiver/ we understand it's media into the client's. Classes structure. Since database. The choice of a in many cases we Java Bean or COM won't understand component is made by the it, it's best to client at installation time. provide a reference implementation instructing how to integrate the media properties into a database table structure. ClientMediaReceiver.props Client Receiver This is a properties file MADS/ClientReceiver This file should Properties File installed at the client be extended by receiver site. It defines the client to operating parameters for identify client media reception such appropriate as default storage database entries locations, etc. (DSN, drivers, default storage tables, etc.). startclientreceiver.bat batch file starts the ClientReceiver MADS\ClientReceiver Specifies the service name of the controlling properties file on the command line.

Claims

1. A media acquisition, processing, and distribution method for transferring one or more media objects to a plurality of destination web sites, comprising the following computer implemented steps:

receiving, from a client device, one or more media objects that have been pre-processed at said client device in accordance with pre-processing parameters that have been provided to said client device from a device external to said client device;
storing said one or more received pre-processed media objects;
retrieving, in response to said receiving, a distribution list that identifies a plurality of remote destination servers;
transmitting, by a server device to said plurality of remote destination servers, one or more media objects based on said stored one or more received pre-processed media objects, said transmitting enabling inclusion of said transmitted one or more media objects in a plurality of destination web sites associated with said plurality of remote destination servers; and
processing said one or more received pre-processed media objects prior to said transmitting in accordance with a profile associated with a remote destination server.

2. The method of claim 1, wherein said media object includes one or more of image content, video content, and audio content.

3. The method of claim 1, wherein said pre-processing parameters are received by said client device over a network.

4. The method of claim 1, wherein said pre-processing parameters are received by said client device over the Internet.

5. The method of claim 1, wherein said pre-processing parameters are received by said client device from an entity associated with said server device.

6. The method of claim 1, wherein said processing comprises resizing, cropping or rotating a media object.

7. The method of claim 1, wherein said processing comprises reformatting a media object.

8. The method of claim 1, wherein said processing comprises encoding a media object.

9. The method of claim 1, wherein said processing comprises adding text and/or graphic layering to a media object.

10. The method of claim 1, wherein said processing comprises enhancing or adding an effect to a media object.

11. The method of claim 1, further comprising transmitting, by said server device, said pre-processing parameters to said client device.

12. A media acquisition, processing, and distribution method for transferring one or more media objects to a plurality of destination web sites, comprising the following computer implemented steps:

receiving, from a client device, one or more media objects that have been pre-processed at said client device in accordance with pre-processing parameters that have been provided to said client device from a device external to said client device;
storing said one or more received pre-processed media objects;
transmitting, by a server device to a plurality of remote destination servers identified by a distribution list, one or more media objects based on said stored one or more received pre-processed media objects, said transmitting enabling inclusion of said transmitted one or more media objects in a plurality of destination web sites associated with said plurality of remote destination servers; and
further comprising processing said one or more received pre-processed media objects prior to said transmitting in accordance with a profile associated with a remote destination server.

13. The method of claim 12, wherein said media object includes one or more of image content, video content, and audio content.

14. The method of claim 12, wherein said pre-processing parameters are received by said client device over a network.

15. The method of claim 12, wherein said pre-processing parameters are received by said client device over the Internet.

16. The method of claim 12, wherein said pre-processing parameters are received by said client device from an entity associated with said server device.

17. The method of claim 12, wherein said processing comprises resizing, cropping or rotating a media object.

18. The method of claim 12, wherein said processing comprises reformatting a media object.

19. The method of claim 12, wherein said processing comprises encoding a media object.

20. The method of claim 12, wherein said processing comprises adding text and/or graphic layering to a media object.

21. The method of claim 12, wherein said processing comprises enhancing or adding an effect to a media object.

22. The method of claim 12, further comprising transmitting, by said server device, said pre-processing parameters to said client device.

23. A media acquisition, processing, and distribution method for transferring one or more media objects to a plurality of remote distribution servers, comprising the following computer implemented steps:

receiving, from a client device, one or more media objects that have been pre-processed at said client device in accordance with pre-processing parameters that have been provided to said client device from a device external to said client device;
transmitting, by a server device to a plurality of distribution servers that are remote from said client device and said server device, one or more media objects based on said one or more received pre-processed media objects, said transmitting enabling said transmitted one or more media objects to be further distributed by said plurality of remote distribution servers; and
further comprising processing said one or more received pre-processed media objects prior to said transmitting in accordance with a profile associated with a remote distribution server.

24. The method of claim 23, wherein said media object includes one or more of image content, video content, and audio content.

25. The method of claim 23, wherein said pre-processing parameters are received by said client device over a network.

26. The method of claim 23, wherein said pre-processing parameters are received by said client device over the Internet.

27. The method of claim 23, wherein said pre-processing parameters are received by said client device from an entity associated with said server device.

28. The method of claim 23, wherein said processing comprises resizing, cropping or rotating a media object.

29. The method of claim 23, wherein said processing comprises reformatting a media object.

30. The method of claim 23, wherein said processing comprises encoding a media object.

31. The method of claim 23, wherein said processing comprises adding text and/or graphic layering to a media object.

32. The method of claim 23, wherein said processing comprises enhancing or adding an effect to a media object.

33. The method of claim 23, further comprising transmitting, by said server device, said pre-processing parameters to said client device.

Referenced Cited
U.S. Patent Documents
4802008 January 31, 1989 Walling
4862200 August 29, 1989 Hicks
5001628 March 19, 1991 Johnson et al.
5327265 July 5, 1994 McDonald
5477353 December 19, 1995 Yamasaki
5555388 September 10, 1996 Shaughnessy
5608542 March 4, 1997 Krahe et al.
5678046 October 14, 1997 Cahill et al.
5760917 June 2, 1998 Sheridan
5761404 June 2, 1998 Murakami et al.
5765152 June 9, 1998 Erickson
5778198 July 7, 1998 Kadota
5781725 July 14, 1998 Saito
5781773 July 14, 1998 Vanderpool et al.
5799063 August 25, 1998 Krane
5802314 September 1, 1998 Tullis et al.
5813009 September 22, 1998 Johnson et al.
5819032 October 6, 1998 De Vries et al.
5819092 October 6, 1998 Ferguson et al.
5844969 December 1, 1998 Goldman et al.
5845299 December 1, 1998 Arora et al.
5848415 December 8, 1998 Guck
5859956 January 12, 1999 Sugiyama et al.
5890170 March 30, 1999 Sidana
5897622 April 27, 1999 Binn et al.
6012068 January 4, 2000 Boezeman et al.
6017157 January 25, 2000 Garfinkle et al.
6018774 January 25, 2000 Mayle et al.
6028603 February 22, 2000 Wang et al.
6035323 March 7, 2000 Narayen et al.
6058417 May 2, 2000 Hess et al.
6084581 July 4, 2000 Hunt
6085195 July 4, 2000 Hoyt et al.
6088732 July 11, 2000 Smith et al.
6104468 August 15, 2000 Bryniarski et al.
6119101 September 12, 2000 Peckover
6125352 September 26, 2000 Franklin et al.
6128600 October 3, 2000 Imamura et al.
6128655 October 3, 2000 Fields et al.
6133985 October 17, 2000 Garfinkle et al.
6167382 December 26, 2000 Sparks et al.
6167568 December 2000 Gandel et al.
6182279 January 30, 2001 Buxton
6199082 March 6, 2001 Ferrel et al.
6202061 March 13, 2001 Khosla et al.
6237010 May 22, 2001 Hui et al.
6281874 August 28, 2001 Sivan et al.
6301586 October 9, 2001 Yang et al.
6301607 October 9, 2001 Barraclough et al.
6330572 December 11, 2001 Sitka
6381029 April 30, 2002 Tipirneni
6456591 September 24, 2002 Mishra
6489980 December 3, 2002 Scott et al.
6505160 January 7, 2003 Levy et al.
6510418 January 21, 2003 Case et al.
6516340 February 4, 2003 Boys
6522418 February 18, 2003 Yokommizo et al.
6535296 March 18, 2003 Oak
6539420 March 25, 2003 Fields et al.
6542936 April 1, 2003 Mayle et al.
6567983 May 20, 2003 Shiimori
6583799 June 24, 2003 Manolis et al.
6621938 September 16, 2003 Tanaka et al.
6628417 September 30, 2003 Naito et al.
6732162 May 4, 2004 Wood et al.
6799165 September 28, 2004 Boesjes
6853461 February 8, 2005 Shiimori
6871231 March 22, 2005 Morris
6895557 May 17, 2005 Wood et al.
6930709 August 16, 2005 Creamer et al.
7010587 March 7, 2006 Shiimori
7032030 April 18, 2006 Codignotto
7043527 May 9, 2006 Shiimori et al.
7146575 December 5, 2006 Manolis et al.
7158172 January 2, 2007 Kawaoka et al.
7246147 July 17, 2007 Kim et al.
7257158 August 14, 2007 Figueredo et al.
7313604 December 25, 2007 Wood et al.
7315386 January 1, 2008 Shiimori et al.
20020067500 June 6, 2002 Yokomizo et al.
20050239454 October 27, 2005 Kawashima et al.
20050262437 November 24, 2005 Patterson et al.
20080201236 August 21, 2008 Field et al.
Foreign Patent Documents
0930774 July 1999 EP
1076302 February 2001 EP
8-153183 June 1996 JP
11-69072 March 1999 JP
11-184943 July 1999 JP
WO 97/04353 February 1997 WO
WO 98/49631 November 1998 WO
WO 99/19811 April 1999 WO
Other references
  • Emily Cohen, “Set Your Sites High,” PC Magazine, May 26, 1998.
  • Plante et al., “The NCSA Astronomy Digital Image Library: From Data Archiving to Data Publishing,” Sep. 21, 1998.
  • Augot et al., “Secure Delivery of Images over Open Networks,” Proceedings of the IEEE, vol. 87, Issue 7, pp. 1251-1266, Jul. 1999.
  • Persits, Peter, “Browser-Based File Uploading Under the Microscope,” 15 Seconds, Nov. 21, 1998.
  • Dean, Doug, “Down and Dirty Browser Uploading with a VB ASP Component,” Mar. 11, 1999.
  • Horstmann et al., “Distributed Authoring on the Web with the BSCW Shared Workspace System,” StandardView, vol. 5, No. 1, Mar. 1997.
  • Netscape Communications Corporation, “Creating Web Pages,” Apr. 27, 1999.
  • Steinberg, Jill, “New Start-Up Releases Java Application and Enabling Software,” JavaWorld, Oct. 1, 1996.
  • Bilson, Rob, “Net-It Central 1.0,” IDM, Jul. 31, 1997.
  • Warp 10 Technologies Inc., Jul. 10, 1998.
  • Pictra Incorporated, Nov. 11, 1998.
  • Letter from Terry Anderson to Craig Hamway, Oct. 16, 1997.
  • PictureWorks ADP Demo, May 1, 1998.
  • Letter from Terry Anderson to Ken Karutz, May 1, 1998.
  • Email from Scott Lewis to Lisa Wood, Jul. 2, 1998.
  • Email from Robin Fried to Scott Lewis et al., Jul. 5, 1998.
  • Email from Scott Lewis to Robin Fried, Jul. 8, 1998.
  • Email from Robin Fried to Martha White, Jul. 9, 1998.
  • Email from Robin Fried to Scott Lewis et al., Jul. 9, 1998.
  • Email from Don Strickland to Lisa Wood et al., Jul. 14, 1998.
  • Emails from Scott Lewis to Lisa Wood et al., Jul. 17-18, 1998.
  • PictureWorks Technology, Inc. Board Update, Jun. 20, 1998.
  • Letter from Terry Anderson, Jul. 22, 1998.
  • Email from Don Strickland to Lisa Wood et al., Jul. 22, 1998.
  • Emails from Don Strickland, Jul. 27 and Aug. 7, 1998.
  • Email from Robin Fried to Scott Lewis et al., Jul. 28, 1998.
  • Email from Scott Lewis to Lisa Wood et al., Jul. 29, 1998.
  • Prioritized Activities for Enterprise Team, Jul. 31, 1998.
  • Email from Don Strickland to Craig Hamway, Aug. 2, 1998.
  • Board Update from Don Strickland, Aug. 7, 1998.
  • Email from Lisa Wood, Aug. 10, 1998.
  • Email from Scott Lewis to Terry Anderson, Aug. 13, 1998.
  • Letter from Terry Anderson to Randy Kau, Aug. 14, 1998.
  • Email from Kirby Lunger to Don Strickland et al., Aug. 14, 1998.
  • Email from Kirby Lunger to Lisa Wood, Aug. 26, 1998.
  • Email from Terry Anderson to Don Strickland, Aug. 25, 1998.
  • Email from Kirby Lunger to Lisa Wood, Aug. 31, 1998.
  • Email from Robin Fried to Scott Lewis et al., Sep. 1, 1998.
  • Email from Scott Lewis to Lisa Wood et al., Sep. 1, 1998.
  • Email from Don Strickland to Terry Anderson et al., Sep. 8, 1998.
  • Email from Scott Lewis to Jeff Paradise, Sep. 11, 1998.
  • Letter from Terry Anderson to Howard Latham, Sep. 15, 1998.
  • Email from Scott Lewis to Jim McCarthy, Sep. 17, 1998.
  • Email from Terry Anderson to Don Strickland et al., Sep. 18, 1998.
  • Email from Scott Lewis to Lisa Wood et al., Sep. 22, 1998.
  • Letter from Anthony Delli Colli to Wayne Mangold, Sep. 18, 1998.
  • Email from Scott Lewis to Lisa Wood et al., Sep. 23, 1998.
  • Email from Robin Fried to Stu Roberson, Sep. 21, 1998.
  • Letter from Terry Anderson to Sei-Wai Lee, Sep. 24, 1998.
  • Email from Scott Lewis to Lisa Wood, Sep. 25, 1998.
  • Email from Terry Anderson to Lisa Wood et al., Sep. 29, 1998.
  • Letter from Scott Lewis to Karim El-Fishaway, Oct. 2, 1998.
  • Email from Anthony Delli Colli to Stu Roberson et al., Oct. 2, 1998.
  • Picture Works presentation to eBay, Oct. 16, 1998.
  • Letter from Scott Lewis to Gary Dillabough, Oct. 20, 1998.
  • Email from Don Strickland to PWT Employees, Oct. 31, 1998.
  • Press Release, Moore Data Management Services and PictureWorks Technology Inc., Announce Partnership to Revolutionize Use of Real Estate Photos on the Internet, Nov. 6, 1998.
  • Press Release, PictureWorks Technology Inc., Streamlines Posting of Photos to the Internet, Nov. 6, 1998.
  • Email from Laurie Fleming to Andrew Hunter et al., Nov. 13, 1998.
  • Letter from Scott Lewis to Wayne Graves, Nov. 16, 1998.
  • Email from Scott Lewis to Terry Anderson et al., Nov. 20, 1998.
  • Screenshots from Prepare and Post Video, Nov. 20, 1998.
  • Laura Roe, “New Software Gives Real Estate a View of the Future,” National Real Estate Investor, Dec. 1, 1998.
  • PictureWorks Information, Dec. 9, 1998.
  • PictureWorks Prepare & Post, Fourth Quarter, 1998.
  • Prepare & Post Product Overview, Fourth Quarter, 1998.
  • Letter from Terry Anderson to Neil Shafran, Jan. 12, 1999.
  • Letter from Stu Roberson to James Rowley, Jan. 29, 1999.
  • Product Picks, Realtor Magazine, Feb. 1, 1999.
  • PictureWorks Kodak Presentation, Feb. 24, 1999.
  • Letter from Don Strickland to Phil Ashe, Mar. 2, 1999.
  • PictureWorks ADP Presentation, Mar. 11, 1999.
  • PictureWorks Press Release, “PictureWorks Releases New Free Digital Imaging Software; MediaCenter Offers Essential Tools for Web Imaging,” Mar. 31, 1999.
  • PictureWorks Press Release, “PictureBay.com to Give-Away 30 Digital Cameras in 30 Days,” Apr. 12, 1999.
  • PictureWorks Press Release, “PictureWorks Technology's PictureBay Solves #1 Frustration of eBay Members, Adding Pictures to Auctions,” Apr. 12, 1999.
  • PictureWorks Press Release, “PictureWorks Technology's Rimfire Empowers any Website to Easily Accept, Process, and Display Visitor Photos and Media,” Apr. 12, 1999.
  • Rimfire real-time integrated media brochure, Apr. 12, 1999.
  • Letter from Terry Anderson to Jonathan Graff, Apr. 26, 1999.
  • Sales Update, Apr. 30, 1999.
  • “PictureWorks Plans to Become Powerhouse in Internet Imaging—Exclusive Interview with CEO,” The Future Image Report, vol. 7, Issue 1, May 1, 1999.
  • Email from Laurie Fleming to Terry Anderson et al., May 7, 1999.
  • Roland Woerner et al., “eBay for Dummies,” Chapter 12, May 10, 1999.
  • Letter from Scott Lewis to Roland Woerner, May 10, 1999.
  • Letter from Stu Roberson to Jim Ferras, May 25, 1999.
  • Rimfire real-time integrated media, May 27, 1999.
  • Letter from Scott Lewis to Candace Gates, May 28, 1999.
  • Letter of Intent between PictureWorks Technology, Inc. and Auction Universe, May 31, 1999.
  • Letter from Scott Lewis to Matthew Lengfelder, Jun. 1, 1999.
  • “Casio and PictureWorks Announce Co-Branding and Distribution Agreement; MediaCenter Offers Essential Tools for Web Imaging,” Jun. 3, 1999.
  • Sales Update, Jun. 4, 1999.
  • Email from Laurie Fleming to Terry Anderson et al., Jun. 7, 1999.
  • PictureWorks pricing for prototype, Jun. 9, 1999.
  • PictureWorks proposal, Jun. 9, 1999.
  • PictureWorks scope of work, Jun. 9, 1999.
  • Letter from Terry Anderson to Amazon, Jun. 9, 1999.
  • “Picture Works Announces Co-Branding and Distribution Agreements with On-Line Photo Services Companies,” Jun. 14, 1999.
  • PictureWorks Polaroid presentation, Jun. 15, 1999.
  • PictureWorks Letter of Intent, Jun. 23, 1999.
  • Email from Lisa Wood to Don Strickland et al., Jun. 30, 1999.
  • East Bay Business Times, “Picture Works Founder Keeps True to Original Vision,” Jul. 2, 1999.
  • PictureWorks Technology Proposal, Jul. 9, 1999.
  • Press Release, “PictureWorks Releases New, Free Imaging Weblication; MediaCenter 1.1 Offers Essential Photo Tools for Internet Imaging and Web Publishing, Ideal for Digital Camera Users,” Jul. 19, 1999.
  • Email from Arlette Heule to Lisa wood et al., Jul. 22, 1999.
  • Email from Don Strickland to Terry Anderson et al., Jul. 23, 1999.
  • Email from Lisa Wood to Marty Frame et al., Jul. 23, 1999.
  • Email from Matt Chang to Lisa Wood et al., Jul. 28, 1999.
  • PictureWorks Statement of Work, Jul. 29, 1999.
  • Email from Laurie Fleming to Curt Hibbs et al., Jul. 29, 1999.
  • PictureWorks Sales Update, Aug. 2, 1999.
  • Press Release, “Picturebay is the Fastest and Easiest Way to Add Pictures to Auctions,” Aug. 3, 1999.
  • Email from Scott Lewis to Lisa Wood et al., Aug. 5, 1999.
  • Email from Don Strickland to Terry Anderson et al., Aug. 6, 1999.
  • Email from Kristy Holch to Lisa Wood et al., Aug. 8, 1999.
  • Email from Don Strickland to Lisa Wood et al., Aug. 9, 1999.
  • MakeoverStudio.com screenshots, Aug. 9, 1999.
  • PictureWorks Service Agreement, Aug. 9, 1999.
  • PictureWorks Preferred Partner Agreement, Aug. 9, 1999.
  • Email from Lori Von Rueden to Lisa Wood, Aug. 10, 1999.
  • Email from Laurie Fleming to Robin et al. Aug. 12, 1999.
  • Email from Matt Chang to Lisa Wood et al., Aug. 13, 1999.
  • Email from Laurie Fleming to Terry Anderson et al., Aug. 16, 1999.
  • Email from Don Strickland to Terry Anderson et al., Aug. 16, 1999.
  • Email from Laurie Fleming to Curt Hibbs et al., Aug. 16, 1999.
  • Email from Robin Fried to Chris Weiss et al., Aug. 17, 1999.
  • Letter from Lori Von Rueden to Don Strickland, Aug. 18, 1999.
  • Email from Laurie Fleming to Curt Hibbs et al., Aug. 27, 1999.
  • PictureWorks letter to AOL, Aug. 23, 1999.
  • Email from Anthony Delli Colli to Stu Roberson et al., Aug. 23, 1999.
  • Email from Robin Fried to Lisa Wood et al., Aug. 23, 1999.
  • Email from Anthony Delli Colli to Terry Anderson et al., Aug. 24, 1999.
  • Email from Robin Fried to Chris Weiss et al., Aug. 24, 1999.
  • Email from Phil Ashe to Lisa Wood et al., Aug. 24, 1999.
  • PictureWorks Integration Checklist Aug. 27, 1999.
  • Press Release, “Realtor.com and PictureWorks Technology, Inc. Up the Ante on Real Estate Content,” Aug. 30, 1999.
  • Email from Laurie Fleming to Mike Jaffe et al., Aug. 31, 1999.
  • Email from David Allen to Jon Barry et al., Sep. 2, 1999.
  • Email from Laurie Fleming to Terry Anderson et al., Sep. 2, 1999.
  • Rimfire 2.0 Submission API User Guide and Reference, Sep. 5, 1999.
  • Rimfire 2.0 Submission API (RSAPI) Step-by-Step Guide, Sep. 5, 1999.
  • MakeoverStudio Network Imaging Project Outline, Sep. 7, 1999.
  • Email from Scott Lewis to Lisa Wood et al., Sep. 7, 1999.
  • Realtor.com and PictureWorks, Sep. 7, 1999.
  • Functional System Summary for Rimfire 10.0 GM6, Sep. 7, 1999.
  • Email from Matt Chang to Lisa Wood et al., Sep. 8, 1999.
  • MakeoverStudio Architecture, Sep. 8, 1999.
  • Email from Robin Fried to Laurie Fleming et al., Sep. 8, 1999.
  • Email from Laurie Fleming to Curt Hibbs et al., Sep. 9, 1999.
  • Email from Chrissie Kremer to Lisa Wood et al., Sep. 12, 1999.
  • PictureWorks Rimfire Instant Photo Submission, Sep. 14, 1999.
  • Email from Laurie Von Rueden to Bob Puette et al., Sep. 15, 1999.
  • Email from Sarah Pate, Sep. 15, 1999.
  • Email from Don Strickland to Terry Anderson et al., Sep. 16, 1999.
  • Email from Lee Cannon to Don Strickland et al., Sep. 17, 1999.
  • Email from Anthony Delli Colli to Lisa Wood et al., Sep. 20, 1999.
  • Email from Lori Von Rueden to Lisa Wood et al., Sep. 21, 1999.
  • Email from Lori Von Rueden to Chrissie Kremer et al., Sep. 21, 1999.
  • Email from David Schappell to Terry Anderson, Sep. 22, 1999.
  • Functional System Summary for Rimfire 2.01, Sep. 23, 1999.
  • Functional System Summary for Rimfire 2.0, Sep. 23, 1999.
  • Email from Don Strickland to Terry Anderson et al., Sep. 24, 1999.
  • Email from Matt Chang to Lisa Wood, Sep. 24, 1999.
  • Email from Lori Von Rueden to Lisa Wood et al., Sep. 27, 1999.
  • Email from Laurie Fleming to Curt Hibbs et al., Sep. 27, 1999.
  • Email from Matt Chang to Lisa Wood, Sep. 27, 1999.
  • Email from Laurie Fleming to Lisa Wood et al., Sep. 28, 1999.
  • Email from Don Strickland to Lisa Wood, Sep. 28, 1999.
  • Email from Lori Von Rueden to Lisa Wood et al., Sep. 29, 1999.
  • Email from Lisa Wood to Don Strickland et al., Sep. 29, 1999.
  • Phatmouth Project, Sep. 30, 1999.
  • Email from Brad Brighton to Terry Anderson et al., Sep. 30, 1999.
  • Rimfire FAQ, Oct. 1, 1999.
  • Email from Don Strickland to Robert Dominy et al., Oct. 3, 1999.
  • Email from Don Strickland to Devin Granback et al., Oct. 5, 1999.
  • Email from Lori Von Rueden to Don Strickland et al., Oct. 5, 1999.
  • Letter from Lori Von Rueden to Paul Woods, Oct. 6, 1999.
  • Email from Norman Winarsky to Robert Dominy, Oct. 6, 1999.
  • Email from Don Strickland to Terry Anderson et al., Oct. 8, 1999.
  • Rimfire Integration, Oct. 18, 1999.
  • Rimfire Mirror Service, Oct. 8, 1999.
  • Rimfire 2.0 Presentation Output Reference Snipetts, Oct. 8, 1999.
  • Rimfire 2.0 Presentation Output Reference, Oct. 8, 1999.
  • PictureWorks Ebay Presentation, Oct. 8, 1999.
  • Email from Laurie Fleming to Mike Ryder et al., Oct. 8, 1999.
  • Email from Laurie Fleming to Marty Frame et al., Oct. 11, 1999.
  • Email from Laurie Fleming to Lisa Wood, Oct. 12, 1999.
  • Email from Laurie Fleming to Curt Hibbs et al., Oct. 13, 1999.
  • Picturebay Screenshot, Oct. 13, 1999.
  • MakeoverStudio.com screen shot, Oct. 16, 1999.
  • PictureWorks Technology, Inc. Propels Leadership Position in Internet Imaging with Rimfire 2.5, Oct. 16, 1999.
  • Email from Scott Lewis to Terry Anderson et al., Oct. 18, 1999.
  • PictureWorks Rimfire Instant Photo Submission White Paper, Oct. 18, 1999.
  • Email from Stu Robertson to Don Strickland et al., Oct. 19, 1999.
  • Email from Laurie Fleming to Sarah Pate et al., Oct. 21, 1999.
  • Email from Sarah Pate to Lisa Wood et al., Oct. 26, 1999.
  • Email from Chris Weiss to Lisa Wood, Oct. 27, 1999.
  • Email from Anthony Delli Colli to Stu Roberson et al., Oct. 27, 1999.
  • Email from Lee Cannon to Janice Jones et al., Oct. 28, 1999.
  • Polaroid's Technical Topic/Question List, Oct. 29, 1999.
  • Email from Don Strickland to Terry Anderson et al., Oct. 29, 1999.
  • Email from Don Strickland to Terry Anderson et al., Nov. 2, 1999.
  • Auction Universe Statement of Work, Nov. 3, 1999.
  • Polaroid Statement of Work, Nov. 3, 1999.
  • Email from Anthony Delli Colli to Stu Roberson et al., Nov. 4, 1999.
  • Email from Sarah Pate to Joe Byrd, Nov. 4, 1999.
  • Email from Sarah Pate to Brad Schafer et al., Nov. 5, 1999.
  • Email from Terry Anderson to Bill Phelan, Nov. 5, 1999.
  • PictureWorks Technology, Inc. Expands in Real Estate Market with Adoption of Rimfire on Realtor.com, Nov. 8, 1999.
  • PictureWorks Technology, Inc.'s Rimfire Makes PictureBay the Leading Provider of Auction Photo Services, Nov. 9, 1999.
  • Makeover NetWorks and Avon, Nov. 10, 1999.
  • PictureWorks Technology Inc. Builds Backbone for Internet Imaging, Significant Partners Integrate Rimfire, Nov. 10, 1999.
  • PictureWorks Technology, Inc. Shows Strong Revenue Growth in Internet Imaging Business, Nov. 10, 1999.
  • Email from Steve Saylor to Donald Strickland et al., Nov. 11, 1999.
  • PictureWorks Technology, Inc. Announces Equity Investment in Phatmouth.com, Nov. 11, 1999.
  • PictureWorks Technology, Inc. Provides Internet Imaging to Real Estate Village, Nov. 12, 1999.
  • Email from Laurie Fleming to Lisa Wood et al., Nov. 15, 1999.
  • Pictureworks Technology, Inc. Propels Leadership Position in Internet Imaging with Rimfire 2.5, Nov. 16, 1999.
  • Email from John Stevens to Terry Anderson et al., Nov. 17, 1999.
  • Email from Laurie Fleming to Lisa Wood, Nov. 17, 1999.
  • PictureWorks Technology, Inc. Leaps off the Desktop as a Six Year Old Internet Startup, Nov. 17, 1999.
  • Email from Don Strickland to Don Strickland et al., Nov. 18, 1999.
  • Rimfire Mirror Service, Nov. 19, 1999.
  • Rimfire 2.0 Submission API User Guide and Reference, Nov. 19, 1999.
  • Rimfire 2.0 Submission API (RSAPI) Step-by-Step Guide, Nov. 19, 1999.
  • Rimfire 2.6 Integration Checklist, Nov. 19, 1999.
  • Email from Lee Cannon to Don Strickland et al., Nov. 22, 1999.
  • PictureWorks Technology Files for Patent on Internet Media Submission Invention, Nov. 22, 1999.
  • PictureWorks eBay Technology Overview, Fourth Quarter, 1999.
Patent History
Patent number: 7761537
Type: Grant
Filed: Nov 5, 2007
Date of Patent: Jul 20, 2010
Patent Publication Number: 20080059608
Assignee: Summit 6 LLC (Dallas, TX)
Inventors: Lisa T. Wood (Danville, CA), Scott M. Lewis (Danville, CA), Robin T. Fried (Berkeley, CA)
Primary Examiner: Wen-Tai Lin
Attorney: Duane S. Kobayashi
Application Number: 11/935,340
Classifications
Current U.S. Class: Accessing A Remote Server (709/219); Cooperative Computer Processing (709/205); Remote Data Accessing (709/217); Access Augmentation Or Optimizing (707/2) (707/999.002)
International Classification: G06F 15/16 (20060101); G06F 7/00 (20060101);