eMediaCarts

• US 20020129002A1
• Filed: 10/22/2001
• Published: 09/12/2002
• Est. Priority Date: 10/27/2000
• Status: Abandoned Application

• Current Assignee: Douglas David Iii Fairchild, Douglas Wesley Alberts
• Original Assignee: Douglas David Iii Fairchild, Douglas Wesley Alberts
• Inventors: Alberts, Douglas Wesley, Fairchild, Douglas David III
• Application Number:
  US10/032,589
• Publication Number:
  US 20020129002A1
• Time in Patent Office: Days
• US Class Current: 707/1
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

eMediaCarts are interactive, portable shopping carts, which allow for e-commerce purchasing directly from personal computers, CDs, DVDs, interactive TV systems, or other stand alone or web connected media devices. eMediaCarts can include or access, dynamic databases reproducing functionalities and capabilities of dynamic server web sites, without needing to connect to a server, and can contain the same content as printed versions of catalogs by converting or exporting digital files from print design programs such as Adobe inDesign, Pagemaker, Quark Xpress, Canvas, Freehand et al. to any digital format or document that will support the BuyObjects, such as HTML, Adobe Acrobat, Flash, SVG (Scalable Vector Format), Quicktime, MPEG, PowerPoint, and other documents which can contain interactive URLs including remote server videos (which can be delivered as locally stored portable videos alleviating the concerns of Internet access and security and slowness of inadequate bandwidths). eMediaCarts transform and provide the ability for static data and data received from remote servers to become portable, interactive, purchasing media. eMediaCarts usages include direct mail using file formats such as: HTML, DHTML, XML, PDF, PowerPoint, Word, MPEG and other portable file formats, which can be used within or attached to email or instant messages.

Claims

1. eMediacarts are non-server, local device shopping carts with their own software engines for assembling orders, placing orders and purchasing, and do not require a web server, as shown in FIG. 1.

2. Emediacarts are hosted on any electronic storage device or hard drive that supports the file formats they are in, including portable devices such as removable hard disks, compact disks, digital video disks, television media and other media devices or electronic messaging systems that can support them, as shown in FIG. 2.

3. EmediaCarts are implemented as either small applications such as java applets or executable win32 modules incorporating activex controls.

4. Current emediacarts offered by ecatalogbuilders'"'"' are catalogbuilder cart, mx-cart, x-rom and x-rom lite cart with items, quantities, prices and other data pertinent to the transaction in either a floating window as in FIG. 3, or embedded as a static or dynamic area within a browser or messaging window as in FIG. 4.

5. Definitions:

Mx-messages are commerce enabled electronic messages.

Ecatalog pages are commerce enabled product pages.

Emedia is the collective term used to describe both mx-messages and ecatalogs.

PDF Engine is a sub application for portable document format ordering, which is based on our proprietary method of using a winsock control bound to a custom transmission control protocol port that is dedicated to accept requests issued by portable document format web links, which are then further processed by the emediacarts custom activex dII.

Buyobjects are code snippets or packages that contain the exact code necessary to make a purchase, complete with identifying icons and the ability to be dragged and dropped from palettes or windows in visual page or document layout and design programs or web authoring programs that support drag and drop technology and can be cut and pasted or dragged and dropped from template pages or documents in layout or design programs that do not support palette drag and drop.

Itransfer is the optional server side component which converts incoming emediacarts orders into either fax format, and faxes them securely to the merchant, or converts them into electronic formats compatible with merchant services gateway providers, for authentication and processing of electronic transactions such as credit cards and echecks.

6. The memory storage techniques used are long term cookies and databases which create a suspended memory system to hold and store order data during ordering sessions and to store complete orders which have been saved for later retrieval, for additional ordering modifications at future dates, or to be submitted for back-end processing at a future date as in FIG. 5.

7. Emediacarts have databases and cookie methods that contain entire unprocessed orders/carts on local hosts with unique customer assigned order names or numbers as identification tags, and the dates of the saved carts.

8. Data resources used as product information for emediacarts can be hard-coded or embedded into product pages in various formats, such as HTML, e-mail, text documents that support the coding, and graphical file types such as portable document format pages, scalable vector graphics, shockwave, and flash, or any pages or documents that will support the features and such product pages can be either static files or dynamically generated pages that are produced on the fly from local database contents, and pricing and other product information can be updated from a remote location through optional web-connect methods or through included update files.

9. The submitting of ordering data from the product pages to the emediacarts is done through buyobjects as shown in FIG. 6, which contain the web links, non-server forms or the forms and link format specific to the file type, such as the forms data format used in portable document format documents, universal resource locator strings, hypertext markup language forms, extensible markup language tags, portable document format web links, and all other available querystring and form field variations available in programming languages, and these buyobjects can either be single product submissions or group product submissions, and the data they contain can be parameters and values, containing numbers, descriptions, styles, colors, quantities, quality, tax info, shipping data, and any qualitative or quantitative options or information pertaining to the purchase.

10. Coded applications in hidden frame browser windows provide persistence between linked pages but are not required for single product page catalogs, where the use of the word persistence is in reference to the reloading of the existing cart versus the opening of a new cart during the linking to any additional product pages as shown in FIGS. 7 and 8.

11. Emediacarts'"'"' proprietary pdf engine for portable document format ordering is based on our proprietary method of using a winsock control bound to a custom transmission control protocol port that is dedicated to accept requests, issued by portable document format web links, which are further processed by the emediacarts custom activex dII, and is illustrated in FIG. 9.

12. Emediacarts in some cases require liveconnect or other technology that is capable of processing incoming messages from javascript, contained within the product pages.

13. All emediacarts can be web connected to back end merchant services and merchant administration services, including customer information, product updating, product pricing and updating, order history for both customers and the vendors, accounting interfaces, shipping management, taxations management, order faxing through our proprietary fax server, and interfaces to the credit card processor'"'"'s gateways for credit card authentication and processing through our proprietary itransfer intermediate gateway, and they can be customized to process orders through existing web site shopping carts and back-end services.