The present invention relates generally to the field of electronic commerce, and more specifically to a method and system to generate a listing in a network-based commerce system.
More and more Internet users are realizing the ease and convenience of buying and selling online via a network-based commerce system. Certain such commerce systems are focused on person-to-person trading, and collectors, hobbyists, small dealers, unique listing seekers, bargain hunters, and other consumers, are able to buy and sell millions of listings at various online shopping sites. Such systems also support business-to-person and business-to-business commerce.
The success of a networked-based commerce system may depend upon its ability to provide a user-friendly environment in which buyers and sellers can conduct business efficiently. Current network-based commerce systems have certain limitations in the manner in which a user can post a listing on such systems.
According to one aspect of the invention, there is provided a method and system of generating a listing in a network-based commerce system. The method includes receiving listing identification data from a user, and retrieving listing data associated with the listing based on the listing identification data. Thereafter, a listing is generated that is at least partially based on the listing data and posted on the network-based commerce system. In one embodiment, the user may edit the listing data prior to posting the listing. The network-based commerce system may include a database of listing data associated with at least one of movies, music, games, books and motor vehicles. In one embodiment, a plurality of check boxes is provided each of which are associated with an attribute of the listing and the method automatically, without human intervention, checks attributes based on the listing data.
Other features of the present invention will be apparent from the accompanying drawings and from the detailed description that follows.
The invention is now described, by way of example, with reference to the accompanying diagrammatic drawings in which like reference numerals are used to indicate the same or similar features, unless otherwise indicated.
A method and system automatically to generate listings in a network-based commerce system based on reference listing data is described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be evident, however, to one skilled in the art that the invention may be practiced without these specific details.
For the purposes of the present specification, the term “listing” or “item” may refer to any description, identifier, representation or information pertaining to a listing, service, offering or request that is stored within a network-based commerce system. As such, a listing may be an auction or fixed-price offering (e.g., products such as goods and/or services), an advertisement, or a request for a listing or service.
Transaction Facility
The network-based commerce system 10 includes one or more of a number of types of front-end servers that each includes at least one Dynamic Link Library (DLL) to provide selected functionality. The system 10 includes page servers 12 that deliver web pages (e.g., mark-up language documents), picture servers 14 that dynamically deliver images to be displayed within Web pages, listing servers 16 that facilitate category-based browsing of listings, search servers 18 that handle search requests to the system 10 and facilitate keyword-based browsing of listings, and ISAPI servers 20 that provide an intelligent interface to a back-end of the system 10. The system 10 also includes e-mail servers 22 that provide, inter alia, automated e-mail communications to users of the network-based commerce system 10. In one embodiment, one or more administrative application functions 24 facilitate monitoring, maintaining, and managing the system 10. One or more API servers 26 may provide a set of API functions for querying and writing to the network-based commerce system 10. APIs may be called through the HTTP transport protocol. In one embodiment, information is sent and received using a standard XML data format. Applications utilized to interact (e.g., upload transaction listings, review transaction listings, manage transaction listings, etc.) with the network-based commerce system 10 may be designed to use the APIs. Such applications may be in an HTML form or be a CGI program written in C++, Perl, Pascal, or any other programming language.
The page servers 12, API servers 26, picture servers 14, ISAPI servers 20, search servers 18, e-mail servers 22 and a database engine server 28 may individually, or in combination, act as a communication engine to facilitate communications between, for example, a client machine 30 and the network-based commerce system 10; act as a transaction engine to facilitate transactions between, for example, the client machine 30 and the network-based commerce system 10; and act as a display engine to facilitate the display of listings on, for example, the client machine 30.
The back-end servers may include the database engine server 28, a search index server 32 and a credit card database server 34, each of which maintains and facilitates access to a respective database.
In one embodiment, the network-based commerce system 10 is accessed by a client program, such as for example a browser 36 (e.g., the Internet Explorer distributed by Microsoft Corp. of Redmond, Wash.) that executes on the client machine 30 and accesses the network-based commerce system 10 via a network such as, for example, the Internet 38. Other examples of networks that a client may utilize to access the network-based commerce system 10 include a wide area network (WAN), a local area network (LAN), a wireless network (e.g., a cellular network), the Public Switched Telephone Network (PSTN) network, or the like. The client program that executes on the client machine 30 may also communicate with the network-based commerce system 10 via the API servers 26.
Database Structure
The database 40 may, in one embodiment, be implemented as a relational database, and includes a number of tables having entries, or records, that are linked by indices and keys. In an alternative embodiment, the database 40 may be implemented as collection of objects in an object-oriented database.
The database 40 (see
The database 40 also includes one or more divisions in the form of categories provided in category tables 50. Each record within the category table 50 may describe a respective category. In one embodiment, listings provided by the system 10 are arranged in the categories. These categories may be navigable by a user of the network-based commerce system 10 to locate listings in specific categories. Thus, categories provide a mechanism to locate listings that may be browsed. In addition or instead, an alphanumeric search mechanism may be provided by the search servers 20 to allow a user to search for specific listings using search terms or phrases. In one embodiment, the category table 50 describes multiple, hierarchical category data structures, and includes multiple category records, each of which describes the context of a particular category within the multiple hierarchical category structures. For example, the category table 50 may describe a number of real, or actual, categories to which listing records, within the listings tables 44, may be linked.
The database 40 also includes one or more attributes tables 52. Each record within the attributes table 52 describes a respective attribute associated with a listing. In one embodiment, the attributes table 52 describes multiple, hierarchical attribute data structures, and includes multiple attribute records, each of which describes the context of a particular attribute within the multiple hierarchical attribute structures. For example, the attributes table 52 may describe a number of real, or actual, attributes to which listing records, within the listings tables 44, may be linked. Also, the attributes table 52 may describe a number of real, or actual, attributes to which categories, within the category table 50, may be linked.
The database 40 may also include a note table 54 populated with note records that may be linked to one or more listing records within the listings tables 44 and/or to one or more user records within the user table 42. Each note record within the note table 54 may include, inter alia, a comment, description, history or other information pertaining to a listing being offered via the network-based commerce system 10, to a user of the network-based commerce system 10. The database 40 may also include a targeted site table 56 populated with targeted site records that may be linked to one or more listing records within the listings tables 44 and/or to one or more user records within the user table 42.
A number of other exemplary tables may also be linked to the user table 42, namely a user past aliases table 58, a feedback table 60, a feedback details table 62, a bids table 64, an accounts table 66, and an account balances table 68. In one embodiment, the database 40 also includes a batch table 70, a batch listings table 72, and a listings wait table 74.
It will be appreciated that the success of a seller in, for example, selling a listing may be dependent upon the listing information provided when the listing is posted to the network-based commerce system.
Generating a Listing
Referring in particular to
As shown at Block 102, the method 100, broadly, identifies reference data associated with the proposed listing and, thereafter, retrieves the reference listing data for the proposed listing from a reference data store and then, in an automated fashion, generates listing data for the proposed listing (see block 104) based on the reference listing data. As will be described in more detail below, the method 100 then presents the proposed listing to the user and allows the user to modify (e.g., edit) the data or information in the proposed listing (see block 106). In one embodiment, the method 100 pre-populates fields of a web page with appropriate data that has been retrieved and then allows the user to modify the data as required. Once the proposed listing has been finalized (and/or accepted) by the user, it may then be posted on the network-based commerce system 10 as shown at block 108.
When the method 100 is applied to listings in the form of motor vehicles (including motorcycles and the like) an identifier such as a Vehicle Identification Number (VIN) may be used to identify the appropriate reference data or information associated with the listing (see block 102). Thus, key data associated with the particular listing (e.g., the vehicle) is provided to the user wishing to list the vehicle in an automated fashion. Accordingly, in one embodiment, a user posting a listing is not confronted with the dilemma as to what information to enter when listing (e.g., selling a car) via the network-based commerce system 10. In one embodiment, the method 100 generates a template suitable for selling a motorcar and the template is then populated with the appropriate reference data identified using the VIN. Further, as reference listing data is retrieved from a reference data source (e.g., a catalogue of VIN data), the integrity of the data provided in the listing is thereby enhanced as the reference data source may be checked and user error is thereby reduced. In certain embodiments, the catalogue of reference listing data is sourced from an appropriate data provider to enhance its accuracy. Accordingly, the data used to populate the template may thus be sourced from an external system. The VIN catalogue data provider may include VIN data substantially similar to that used by dealers, manufacturers, distributors or the like to list vehicles for sale in a wholesale market.
Reference numeral 110 (see
Returning to
As mentioned above, in one embodiment the attributes (e.g., sound system, leather seats, custom paint, heated seats, hard top, etc.) of the listing are identified in the template using a plurality of check boxes. Accordingly, in this embodiment, the check boxes may be automatically checked based on the VIN using the VIN catalogue. However, as mentioned above, any listing identifier may be used to retrieve any attributes or information relating to a proposed listing. It will be appreciated that different templates may be populated dependent upon the nature of the listing and the category in which it is to be listed.
Reference numeral 130 (see
Referring in particular to
At block 148, the method provides the user with an option to select a standard or conventional listing procedure, or list using the method 100, in accordance to the invention. If the user selects to list using a conventional listing procedure, the user is then required to populate all fields for the listing manually without automated assistance. However, if the user selects to generate a new listing in an automated fashion using the method 100, then the user at block 148 enters identification data (e.g., the VIN of a vehicle which he or she wishes to list). In one embodiment, a user interface the form of an exemplary web page 150 (see
In certain embodiments when the user selects to list a motor vehicle, the network-based commerce system 10 may request a user to identify whether the listing is newer than a predetermined year (e.g., 1990) or older than a predetermined year (e.g., 1989), for example, to accommodate a VIN catalogue that does not include older listings. Further, the web page 150 provides a data entry field 152 for the user to enter the VIN of the vehicle that he or she is wishing to list. In one embodiment, the method 140 checks the validity of the VIN entered by the user.
Thereafter, the method 140 monitors activation or clicking of a “Continue” button 154 in order to proceed with the automated listing functionality. If, however, the user chooses to list a vehicle that is older than the predetermined date (e.g., 1989 or older), no VIN is entered and the user may then immediately activate a “Continue” button 156.
Once the network-based commerce system 10 has received the VIN, and in the event of only a single listing or motor vehicle being found that corresponds to the entered VIN, then the method 140 proceeds directly to a Title and Description operation or block 158. Likewise, if the user enters no VIN and the “Continue” button 156 is activated, then the method 140 also proceeds directly to the Title and Description block 158. If, however, the network-based commerce system 10 locates multiple vehicles associated with the VIN, the method 140 generates a user interface in the form of a web page 160 (see
Returning to
In one embodiment, the method 100 automatically generates a title for the listing based on the VIN. In particular, the VIN is used to determine a year, make and model, sub-model/style/trims specified, number of doors, and engine capacity (cylinders and output). Thus, as shown by a user interface in the form of a web page 192 (See
A vehicle description 200 (see
In certain embodiments of the invention, a user may edit or modify a listing or item after it has been posted on the network-based commerce system 10. For example, in one embodiment of the invention, the system 10 includes a “Revise Your Item” (RYI) function. For example, when the network-based commerce system 10 is a network-based auction system, if there are no bids and more than 12 hours remaining in the auction for the listing, the user or seller may be able to make selected changes. However, when there is either a bid or less than 12 hours remaining, the user or seller may be able to supplement the listings' previous description. If, for example, both a bid and less than 12 hours remain, the seller may in this case make changes not affecting the core description of the listing. Exemplary user interfaces for revising the listing in the form of exemplary web pages are provided in
The web page 210 (see
Returning to
As mentioned above, the methods 100, 110, 130 and 140 can be applied to any listing in any network-based commerce system. Further, the identification data that the user enters may differ from one listing to another. For example, when a listing is automatically generated for listing in an exemplary movies category, the listing identification data may be a title of the movie or its UPC code. In one embodiment, a help facility to assist a user in finding the UPC code of the movie may be provided. Further, for example when listing a music CD, the user may enter an artist name, title of the CD and so on. Thus, broadly, the invention allows assisted listing wherein an appropriate template is populated with relevant data pertaining to a proposed listing. In one embodiment, the template includes a plurality of check boxes that are checked in an automated fashion based on reference listing data. It is to be appreciated that the listing generated may include extensive information on the listing or any varying degree of information.
Referring in particular to
The system 250 includes a data retrieval module 264, a proposed listing generation module 266, a proposed listing editing module 268, and a proposed listing display module 270. The modules 264 to 270 either individually, or in combination execute the functionality of the above described methods 100, 110, 130 and 140.
The computer system 300 includes a processor 302, a main memory 304 and a static memory 306, which communicate with each other via a bus 308. The computer system 300 may further include a video display unit 310 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 300 also includes an alphanumeric input device 312 (e.g., a keyboard), a cursor control device 314 (e.g., a mouse), a disk drive unit 316, a signal generation device 318 (e.g., a speaker) and a network interface device 320 to interface the computer system to a network 322.
The disk drive unit 316 includes a machine-readable medium 324 on which is stored a set of instructions or software 326 embodying any one, or all, of the methodologies described herein. The software 326 is also shown to reside, completely or at least partially, within the main memory 304 and/or within the processor 302. The software 326 may further be transmitted or received via the network interface device 320. For the purposes of this specification, the term “machine-readable medium” shall be taken to include any medium which is capable of storing or encoding a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to included, but not be limited to, solid-state memories, optical and magnetic disks, and carrier wave signals. Further, while the software is shown in
Thus, a method and system to generate a listing in a network-based commerce system 10 have been described. Although the invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
This application is a continuation of U.S. patent application Ser. No. 15/643,874, filed Jul. 7, 2017, which is a continuation of U.S. patent application Ser. No. 14/318,525, filed Jun. 27, 2014, which is a continuation of U.S. patent application Ser. No. 10/648,125, filed Aug. 25, 2003, which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/437,199, filed Dec. 31, 2002, the benefit of priority of each of which is claimed hereby, and each are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5537586 | Amram et al. | Jul 1996 | A |
5664115 | Fraser | Sep 1997 | A |
5740425 | Povilus | Apr 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5822123 | Davis et al. | Oct 1998 | A |
5844554 | Geller | Dec 1998 | A |
5950173 | Perkowski | Sep 1999 | A |
5987610 | Franczek et al. | Nov 1999 | A |
6029141 | Bezos et al. | Feb 2000 | A |
6044363 | Mori et al. | Mar 2000 | A |
6073142 | Geiger et al. | Jun 2000 | A |
6078866 | Buck et al. | Jun 2000 | A |
6083276 | Davidson et al. | Jul 2000 | A |
6119101 | Peckover | Sep 2000 | A |
6122648 | Roderick | Sep 2000 | A |
6144958 | Ortega et al. | Nov 2000 | A |
6151601 | Papierniak et al. | Nov 2000 | A |
6216264 | Maze et al. | Apr 2001 | B1 |
6230156 | Hussey | May 2001 | B1 |
6266649 | Linden et al. | Jul 2001 | B1 |
6336105 | Conklin et al. | Jan 2002 | B1 |
6345315 | Mishra | Feb 2002 | B1 |
6351755 | Najork et al. | Feb 2002 | B1 |
6401084 | Ortega et al. | Jun 2002 | B1 |
6410084 | Klare et al. | Jun 2002 | B1 |
6415270 | Rackson et al. | Jul 2002 | B1 |
6453339 | Schultz et al. | Sep 2002 | B1 |
6460050 | Pace et al. | Oct 2002 | B1 |
6470383 | Leshem et al. | Oct 2002 | B1 |
6476833 | Moslifeghi | Nov 2002 | B1 |
6549935 | Lapstun et al. | Apr 2003 | B1 |
6598026 | Ojha et al. | Jul 2003 | B1 |
6631522 | Erdelyi | Oct 2003 | B1 |
6633316 | Maddalozzo et al. | Oct 2003 | B1 |
6641037 | Williams | Nov 2003 | B2 |
6667751 | Wynn et al. | Nov 2003 | B1 |
6697800 | Jannink et al. | Feb 2004 | B1 |
6697823 | Otsuka et al. | Feb 2004 | B2 |
6697824 | Bowman-Amuah | Feb 2004 | B1 |
6732088 | Glance | May 2004 | B1 |
6820111 | Rubin et al. | Nov 2004 | B1 |
6853982 | Smith et al. | Feb 2005 | B2 |
6892193 | Bolle et al. | May 2005 | B2 |
6904410 | Weiss et al. | Jun 2005 | B1 |
6907574 | Xu et al. | Jun 2005 | B2 |
6928425 | Grefenstette et al. | Aug 2005 | B2 |
6948120 | Delgobbo et al. | Sep 2005 | B1 |
6963850 | Bezos et al. | Nov 2005 | B1 |
6963867 | Ford et al. | Nov 2005 | B2 |
6976053 | Tripp et al. | Dec 2005 | B1 |
7013423 | Blaschke et al. | Mar 2006 | B2 |
7225199 | Green et al. | May 2007 | B1 |
7228298 | Raines | Jun 2007 | B1 |
7295995 | York et al. | Nov 2007 | B1 |
7315983 | Evans et al. | Jan 2008 | B2 |
7366721 | Bennett et al. | Apr 2008 | B1 |
7395502 | Gibbons et al. | Jul 2008 | B2 |
7447646 | Agarwal et al. | Nov 2008 | B1 |
7480627 | Van et al. | Jan 2009 | B1 |
7783520 | Zhang et al. | Aug 2010 | B2 |
7886156 | Franchi | Feb 2011 | B2 |
8050974 | Lopez et al. | Nov 2011 | B2 |
8086502 | Krishnamurthy et al. | Dec 2011 | B2 |
8194985 | Grigsby et al. | Jun 2012 | B2 |
8260656 | Harbick | Sep 2012 | B1 |
8301512 | Hamilton et al. | Oct 2012 | B2 |
8306872 | Inoue et al. | Nov 2012 | B2 |
8352334 | Ulinski | Jan 2013 | B2 |
8402068 | Clendinning et al. | Mar 2013 | B2 |
8489438 | Ibrahim | Jul 2013 | B1 |
8768937 | Clendinning et al. | Jul 2014 | B2 |
8819039 | Grove et al. | Aug 2014 | B2 |
8849693 | Koyfman et al. | Sep 2014 | B1 |
8977603 | Pate et al. | Mar 2015 | B2 |
9076173 | Hamilton et al. | Jul 2015 | B2 |
9171056 | Clendinning et al. | Oct 2015 | B2 |
9412128 | Clendinning et al. | Aug 2016 | B2 |
9558510 | Melcher et al. | Jan 2017 | B2 |
9704194 | Grove et al. | Jul 2017 | B2 |
10319018 | Hamilton et al. | Jun 2019 | B2 |
10332198 | Hamilton et al. | Jun 2019 | B2 |
20010032163 | Fertik et al. | Oct 2001 | A1 |
20010034694 | Elias | Oct 2001 | A1 |
20010037251 | Nojima et al. | Oct 2001 | A1 |
20020016839 | Smith et al. | Feb 2002 | A1 |
20020026353 | Porat et al. | Feb 2002 | A1 |
20020032638 | Arora et al. | Mar 2002 | A1 |
20020040359 | Green et al. | Apr 2002 | A1 |
20020049641 | Kopelman et al. | Apr 2002 | A1 |
20020049763 | Seamon | Apr 2002 | A1 |
20020052801 | Norton et al. | May 2002 | A1 |
20020082893 | Barts et al. | Jun 2002 | A1 |
20020082953 | Batham et al. | Jun 2002 | A1 |
20020083448 | Johnson | Jun 2002 | A1 |
20020095454 | Reed et al. | Jul 2002 | A1 |
20020103789 | Turnbull et al. | Aug 2002 | A1 |
20020107775 | Hawkins | Aug 2002 | A1 |
20020107861 | Clendinning et al. | Aug 2002 | A1 |
20020120554 | Vega | Aug 2002 | A1 |
20020120619 | Marso et al. | Aug 2002 | A1 |
20020123912 | Subramanian et al. | Sep 2002 | A1 |
20020154157 | Sherr et al. | Oct 2002 | A1 |
20020161697 | Stephens | Oct 2002 | A1 |
20020165799 | Jaffe et al. | Nov 2002 | A1 |
20020188555 | Lawrence | Dec 2002 | A1 |
20020194081 | Perkowski | Dec 2002 | A1 |
20030009495 | Adjaoute | Jan 2003 | A1 |
20030018652 | Heckerman et al. | Jan 2003 | A1 |
20030033216 | Benshemesh | Feb 2003 | A1 |
20030036964 | Boyden | Feb 2003 | A1 |
20030055806 | Wong et al. | Mar 2003 | A1 |
20030061147 | Fluhr et al. | Mar 2003 | A1 |
20030066031 | Laane | Apr 2003 | A1 |
20030083961 | Bezos et al. | May 2003 | A1 |
20030105682 | Dicker et al. | Jun 2003 | A1 |
20030110100 | Wirth, Jr. | Jun 2003 | A1 |
20030154044 | Lundstedt et al. | Aug 2003 | A1 |
20030167213 | Jammes et al. | Sep 2003 | A1 |
20030172357 | Kao et al. | Sep 2003 | A1 |
20030182310 | Charnock et al. | Sep 2003 | A1 |
20030200156 | Roseman et al. | Oct 2003 | A1 |
20030204449 | Kotas | Oct 2003 | A1 |
20030216971 | Sick et al. | Nov 2003 | A1 |
20030217052 | Rubenczyk et al. | Nov 2003 | A1 |
20030233350 | Dedhia et al. | Dec 2003 | A1 |
20040006602 | Bess et al. | Jan 2004 | A1 |
20040128320 | Grove et al. | Jul 2004 | A1 |
20040139059 | Conroy et al. | Jul 2004 | A1 |
20040148611 | Manion et al. | Jul 2004 | A1 |
20040153378 | Perkowski | Aug 2004 | A1 |
20040177319 | Horn | Sep 2004 | A1 |
20040205334 | Rennels | Oct 2004 | A1 |
20040210479 | Perkowski et al. | Oct 2004 | A1 |
20040243478 | Walker et al. | Dec 2004 | A1 |
20040243485 | Borenstein et al. | Dec 2004 | A1 |
20040249794 | Nelson et al. | Dec 2004 | A1 |
20040254950 | Musgrove et al. | Dec 2004 | A1 |
20040260621 | Foster et al. | Dec 2004 | A1 |
20050010871 | Ruthfield et al. | Jan 2005 | A1 |
20050028083 | Kircher et al. | Feb 2005 | A1 |
20050114682 | Zimmer et al. | May 2005 | A1 |
20050114782 | Klinger | May 2005 | A1 |
20050132297 | Milic-Frayling et al. | Jun 2005 | A1 |
20050171627 | Funk et al. | Aug 2005 | A1 |
20050197141 | Jiang et al. | Sep 2005 | A1 |
20050201562 | Becker et al. | Sep 2005 | A1 |
20050204292 | Kibilov et al. | Sep 2005 | A1 |
20050251409 | Johnson et al. | Nov 2005 | A1 |
20050257131 | Lim et al. | Nov 2005 | A1 |
20050289105 | Cosic | Dec 2005 | A1 |
20050289168 | Green et al. | Dec 2005 | A1 |
20060031216 | Semple et al. | Feb 2006 | A1 |
20060085477 | Phillips et al. | Apr 2006 | A1 |
20060106683 | Fisher et al. | May 2006 | A1 |
20060106859 | Eugene et al. | May 2006 | A1 |
20060143158 | Ruhl et al. | Jun 2006 | A1 |
20060190352 | Zeidman | Aug 2006 | A1 |
20060224406 | Leon et al. | Oct 2006 | A1 |
20060224571 | Leon et al. | Oct 2006 | A1 |
20060224954 | Chandler et al. | Oct 2006 | A1 |
20060224960 | Baird-Smith | Oct 2006 | A1 |
20060233326 | Erhart et al. | Oct 2006 | A1 |
20070112968 | Schwab | May 2007 | A1 |
20070118441 | Chatwani et al. | May 2007 | A1 |
20070130207 | Pate et al. | Jun 2007 | A1 |
20070150365 | Bolivar | Jun 2007 | A1 |
20070179848 | Jain et al. | Aug 2007 | A1 |
20070250403 | Altschuler | Oct 2007 | A1 |
20070260495 | Mace et al. | Nov 2007 | A1 |
20080059331 | Schwab | Mar 2008 | A1 |
20080077507 | McElhiney et al. | Mar 2008 | A1 |
20080097767 | Milman et al. | Apr 2008 | A1 |
20090089429 | Antani et al. | Apr 2009 | A1 |
20090113475 | Li | Apr 2009 | A1 |
20090240735 | Grandhi et al. | Sep 2009 | A1 |
20090304267 | Tapley et al. | Dec 2009 | A1 |
20100076867 | Inoue et al. | Mar 2010 | A1 |
20100086192 | Grigsby et al. | Apr 2010 | A1 |
20100214302 | Melcher et al. | Aug 2010 | A1 |
20100217684 | Melcher et al. | Aug 2010 | A1 |
20110099085 | Hamilton et al. | Apr 2011 | A1 |
20120265744 | Berkowitz et al. | Oct 2012 | A1 |
20130198183 | Clendinning et al. | Aug 2013 | A1 |
20130297437 | Hamilton et al. | Nov 2013 | A1 |
20140304220 | Clendinning et al. | Oct 2014 | A1 |
20140372244 | Grove et al. | Dec 2014 | A1 |
20150142601 | Pate et al. | May 2015 | A1 |
20150310525 | Hamilton et al. | Oct 2015 | A1 |
20160027086 | Clendinning et al. | Jan 2016 | A1 |
20170140446 | Melcher et al. | May 2017 | A1 |
20180033080 | Grove et al. | Feb 2018 | A1 |
20190139131 | Grove et al. | May 2019 | A9 |
20190244269 | Hamilton et al. | Aug 2019 | A1 |
Number | Date | Country |
---|---|---|
1841195 | Oct 2007 | EP |
2001057735 | Aug 2001 | WO |
2001077869 | Oct 2001 | WO |
2002054292 | Jul 2002 | WO |
2002054292 | Nov 2003 | WO |
2004061720 | Jul 2004 | WO |
2006107333 | Oct 2006 | WO |
2006107335 | Oct 2006 | WO |
2007061975 | May 2007 | WO |
2007078560 | Jul 2007 | WO |
2007061975 | Oct 2007 | WO |
2007078560 | Oct 2007 | WO |
Entry |
---|
Response to Notice of Non-Compliant Amendment filed Oct. 26, 2015 for U.S. Appl. No. 14/792,133, dated Oct. 20, 2015, 5 pages. |
Response to Final Office Action filed on Feb. 6, 2013, for U.S. Appl. No. 11/426,993, dated Nov. 7, 2012, 9 pages. |
Response to Final Office Action filed on Mar. 4, 2014, for U.S. Appl. No. 11/426,993, dated Sep. 4, 2013, 11 pages. |
International Search Report received for PCT Application No. PCT/US2006/044944, dated May 10, 2017, 2 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2006/044944, dated Jun. 5, 2008, 5 pages. |
International Written Opinion received for PCT Application No. PCT/US2006/044944, dated May 10, 2007, 3 pages. |
Response to Final Office Action filed on Oct. 15, 2010, for U.S. Appl. No. 11/426,993, dated Jul. 22, 2010, 43 pages. |
Response to Final Office Action filed on Oct. 30, 2015, for U.S. Appl. No. 11/426,993, dated Jun. 30, 2015, 16 pages. |
Response to Non-Final Office Action filed on Apr. 14, 2016, for U.S. Appl. No. 11/426,993, dated Jan. 14, 2016, 14 pages. |
Response to Non-Final Office Action filed on Apr. 15, 2015, for U.S. Appl. No. 11/426,993, dated Dec. 15, 2014, 21 pages. |
Response to Non-Final Office Action filed on Jun. 23, 2011, for U.S. Appl. No. 11/426,993, dated Dec. 23, 2010, 8 pages. |
Response to Non-Final Office Action filed on Apr. 28, 2010, for U.S. Appl. No. 11/426,993, dated Feb. 24, 2010 10 pages. |
Response to Non-Final Office Action filed on Jun. 27, 2013, for U.S. Appl. No. 11/426,993, dated Mar. 29, 2013, 8 pages. |
Response to Non-Final Office Action filed on Sep. 18, 2012, for U.S. Appl. No. 11/426,993, dated Jun. 21, 2012, 10 pages. |
Response to Non-Final Office Action filed on Sep. 23, 2014, for U.S. Appl. No. 11/426,993, dated May 23, 2014, 13 pages. |
Response to Restriction Requirement filed on Jan. 7, 2010, for U.S. Appl. No. 11/426,993, dated Dec. 7, 2009, 5 pages. |
Restriction Requirement received for U.S. Appl. No. 11/426,993, dated Dec. 7, 2009, 8 pages. |
Non Final office Action received for U.S. Appl. No. 12/605,212 dated Feb. 16, 2012, Feb. 16 2012, 11 pages. |
Notice of Allowance received for U.S. Appl. No. 12/605,212, dated Jun. 28, 2012, 12 pages. |
Response to Non-Final Office Action filed on May 16, 2012, for U.S. Appl. No. 12/605,212, dated Feb. 16, 2012, 8 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 13/663,178, dated Nov. 28, 2014, 3 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/663,178, dated Oct. 3, 2014, 18 pages. |
Notice of Allowance received for U.S. Appl. No. 13/663,178 dated Mar. 3, 2015, 10 pages. |
Response to Non-Final Office Action filed on May 1, 2015, for U.S. Appl. No. 13/663,178, dated Oct. 3, 2014, 14 pages. |
Advisory Action received for U.S. Appl. No. 14/318,525, dated Jun. 9, 2016, 4 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 14/318,525, dated Aug. 1, 2016, 1 Page. |
Final Office Action received for U.S. Appl. No. 14/318,525, dated Mar. 31, 2016, 28 pages. |
Final Office Action received for U.S. Appl. No. 14/318,525, dated May 28, 2015, 20 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/318,525, dated Feb. 12, 2015, 19 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/318,525, dated Sep. 24, 2015, 31 Pages. |
Notice of Allowance received for U.S. Appl. No. 14/318,525, dated Mar. 10, 2017, 13 pages. |
Preliminary Amendment for U.S. Appl. No. 14/318,525, filed Jun. 30, 2014, 8 pages. |
Response to Final Office Action filed on May 31, 2016, for U.S. Appl. No. 14/318,525, dated Mar. 31, 2016, 14 pages. |
Response to Non-Final Office Action filed on Jan. 25, 2016, for U.S. Appl. No. 14/318,525, dated Sep. 24, 2015, Jan. 25, 2016, 13 pages. |
Response to Non-Final Office Action filed on Aug. 28, 2015, for U.S. Appl. No. 14/318,525, dated May 28, 2015, 16 pages. |
Response to Non-Final Office Action filed on Jan. 3, 2017, for U.S. Appl. No. 14/318,525, dated Sep. 1, 2016, 20 pages. |
Response to Non-Final Office Action filed on May 12, 2015, for U.S. Appl. No. 14/318,525, dated Feb. 12, 2015, 14 pages. |
Supplemental Preliminary Amendment filed on Aug. 14, 2014, for U.S. Appl. No. 14/318,525, 3 pages. |
Notice of Non-Compliant Amendment received for U.S. Appl. No. 14/792,133, dated Oct. 20, 2015, 2 pages. |
Preliminary Amendment filed received for U.S. Appl. No. 14/792,133 dated Oct. 8, 2015, 1 pages. |
Irvine, “New Text and Social Messaging Features Expand Frucall's Voice-Based”, Primezone , Aug. 31, 2006, 1 page. |
Kotas, et al., “Use of Electronic Catalog to Facilitate User-to-User Sales”, U.S. Appl. No. 60/336,409, filed Oct. 31, 2001, 45 pages. |
My Comicshop. Com, “Mad Comic Books”, Retrieved from the Internet: URL:<https://www.mycomicshop.com/search?tid=353271&pgi=i151>, 1955, 22 pages. |
Demand for Preliminary Examination received for U.S. Patent Application No. PCT/US2003/41543 dated Jun. 10, 2004, 5 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2003/41543, dated Apr. 27, 2005, 6 pages. |
International Search Report received for PCT Patent Application No. PCT/US2003/41543, dated Apr. 14, 2004, 7 Pages. |
International Written Opinion received for PCT Patent Application No. PCT/US2003/41543, dated Aug. 26, 2004, 9 pages. |
Ukiva, “Machine Vision Handbook”, 2007, pp. 1-16. |
Final Office Action received for U.S. Appl. No. 11/426,993, dated Jun. 30, 2015, 8 pages. |
Appeal Brief filed on Oct. 22, 2018, for U.S. Appl. No. 14/792,133, 18 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 14/792,133, dated Feb. 9, 2018, 2 pages. |
Final Office Action received for U.S. Appl. No. 14/792,133, dated May 22, 2018, 21 pages. |
First Action Interview—Pre-Interview Communication received for U.S. Appl. No. 14/792,133, dated Nov. 30, 2017, 7 pages. |
First Action Interview—Office Action Summary received for U.S. Appl. No. 14/792,133, dated Feb. 9, 2018, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 14/792,133, dated Feb. 1, 2019, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 14/792,133, dated Dec. 12, 2018, 11 pages. |
Response to First Action Interview—Office Action Summary Filed on Apr. 4, 2018, For U.S. Appl. No. 14/792,133, dated Feb. 9, 2018, 18 pages. |
Amendment Under 37 CFR 1.312 filed on May 7, 2019 for U.S. Appl. No. 15/643,874, 8 pages. |
Examiner-Initiated Interview Summary received for U.S. Appl. No. 15/643,874, dated Oct. 18, 2018, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/643,874, dated Apr. 18, 2018, 34 pages. |
Notice of Allowance received for U.S. Appl. No. 15/643,874, dated Feb. 7, 2019, 18 pages. |
PTO Response to Rule 312 Communication received for U.S. Appl. No. 15/643,874, dated May 20, 2019, 2 pages. |
Response to Non-Final Office Action filed on Aug. 14, 2018, for U.S. Appl. No. 15/643,874, dated Apr. 18, 2018, 28 pages. |
“Screen Dumps for Windows Internet Explorer 6.0SP2”, Dec. 2004, 6 pages. |
U.S. Appl. No. 10/648,125 U.S. Pat. No. 8,819,039, Aug. 25, 2003, Method and System to Generate a Listing in a Network-Based Commerce System. |
U.S. Appl. No. 14/318,525 U.S. Pat. No. 9,704,194, Jun. 27, 2014, Method and System to Generate a Listing in a Network-Based Commerce System. |
U.S. Appl. No. 15/643,874 U.S. Pat. No. 10,332,198, Jul. 7, 2017, Method and System to Generate a Listing in a Network-Based Commerce System. |
U.S. Appl. No. 11/426,993, filed Jun. 28, 2006, Editable Electronic Catalogs. |
U.S. Appl. No. 13/663,178 U.S. Pat. No. 9,076,173, Oct. 29, 2012, Product Identification Using Multiple Services. |
U.S. Appl. No. 12/605,212 U.S. Pat. No. 8,301,512, Oct. 23, 2009, Product Identification Using Multiple Services. |
U.S. Appl. No. 14/792,133, filed Jul. 6, 2015, Product Identification Using Multiple Services. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated May 23, 2014, 19 pages. |
Response to Final Office Action filed on Nov. 4, 2013, for U.S. Appl. No. 11/426,993, dated Sep. 4, 2013, 10 pages. |
Preliminary Amendment filed on Aug. 23, 2019, for U.S. Appl. No. 16/384,010, 6 pages. |
Advisory Action received for U.S. Appl. No. 10/648,125, dated Jun. 9, 2005, 4 pages. |
Advisory Action received for U.S. Appl. No. 10/648,125, dated Feb. 11, 2009, 3 pages. |
Appeal Brief filed on Jul. 16, 2010, for U.S. Appl. No. 10/648,125, 35 pages. |
Appeal Decision received for U.S. Appl. No. 10/648,125, dated Jan. 30, 2014, 12 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 10/648,125, dated Jun. 12, 2014, 1 Page. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 10/648,125, dated Jan. 6, 2006, 3 pages. |
Decision on Pre-Appeal Brief Request received for U.S. Appl. No. 10/648,125, dated Apr. 16, 2010, 2 pages. |
Examiner Initiated Interview Summary received for U.S. Appl. No. 10/648,125, dated Mar. 28, 2014, 2 pages. |
Examiner Initiated Interview Summary received for U.S. Appl. No. 10/648,125, dated Oct. 16, 2008, 2 pages. |
Examiner's Answer to Appeal Brief for U.S. Appl. No. 10/648,125, dated Oct. 14, 2010, 47 pages. |
Final Office Action received for U.S. Appl. No. 10/648,125, dated Dec. 4, 2008, 33 pages. |
Final Office Action received for U.S. Appl. No. 10/648,125, dated Jan. 4, 2010, 39 pages. |
Final Office Action received for U.S. Appl. No. 10/648,125, dated Jan. 9, 2006, 29 pages. |
Final Office Action received for U.S. Appl. No. 10/648,125, dated Oct. 10, 2008, 56 pages. |
Final Office Action received for U.S. Appl. No. 10/648,125 dated Mar. 24, 2005, 19 pages. |
Final Office Action received for U.S. Appl. No. 10/648,125, dated Jul. 24, 2007, 27 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/648,125, dated Aug. 25, 2005, 14 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/648,125, dated Feb. 21, 2008, 53 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/648,125, dated May 13, 2009, 36 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/648,125, dated Dec. 7, 2006, 27 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/648,125, dated Sep. 1, 2004, 22 pages. |
Notice of Allowance received for U.S. Appl. No. 10/648,125, dated Apr. 21, 2014, 14 pages. |
Pre-Appeal Brief Request received for U.S. Appl. No. 10/648,125, dated Mar. 4, 2010, 5 pages. |
Reply Brief filed on Mar. 26, 2014, for U.S. Appl. No. 10/648,125, 65 pages. |
Reply Brief filed on Nov. 2, 2010, for U.S. Appl. No. 10/648,125, 10 pages. |
Response to Advisory Action filed on Jul. 25, 2005, for U.S. Appl. No. 10/648,125, dated Jun. 9, 2005, 9 pages. |
Response to Final Office Action filed on Feb. 4, 2009, for U.S. Appl. No. 10/648,125, dated Dec. 4, 2008, 13 pages. |
Response to Final Office Action filed on Jul. 12, 2006, for U.S. Appl. No. 10/648,125, dated Jan. 9, 2006, 14 pages. |
Response to Final Office Action filed on Mar. 4, 2009, for U.S. Appl. No. 10/648,125, dated Dec. 4, 2008, 14 pages. |
Response to Final Office Action filed on May 26, 2005, for U.S. Appl. No. 10/648,125, dated Mar. 24, 2005, 21 pages. |
Response to Final Office Action filed on Oct. 30, 2007, for U.S. Appl. No. 10/648,125, dated Jul. 24, 2007, 13 pages. |
Response to Non-Final Office Action filed on Dec. 16, 2005, for U.S. Appl. No. 10/648,125, dated Aug. 25, 2005, 9 pages. |
Response to Non Final Office Action filed on Jun. 23, 2008, for U.S. Appl. No. 10/648,125, dated Feb. 21, 2008, 19 pages. |
Response to Non-Final Office Action filed on Jan. 10, 2005, for U.S. Appl. No. 10/648,125, dated Sep. 1, 2004, 18 pages. |
Response to Non-Final Office Action filed on May 10, 2007, for U.S. Appl. No. 10/648,125, dated Dec. 7, 2006, 14 pages. |
Response to Non-Final Office Action filed on Sep. 14, 2009, for U.S. Appl. No. 10/648,125, dated May 13, 2009, 14 pages. |
Final Office Action received for U.S. Appl. No. 11/426,993, dated Sep. 16, 2011, 16 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated Dec. 23, 2010, 18 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated Jan. 14, 2016, 8 pages. |
Response to Final Office Action filed on Dec. 15, 2011, for U.S. Appl. No. 11/426,993, dated Sep. 16, 2011, 9 pages. |
Final Office Action received for U.S. Appl. No. 11/426,993, dated Jul. 22, 2010, 17 pages. |
Advisory Action received for U.S. Appl. No. 11/426,993 dated Feb. 12, 2014, 3 pages. |
Final Office Action received for U.S. Appl. No. 11/426,993, dated Nov. 7, 2012, 14 pages. |
Final Office Action received for U.S. Appl. No. 11/426,993, dated Sep. 4, 2013, 14 pages. |
Final Office Action received for U.S. Appl. No. 11/426,993, dated Aug. 11, 2016, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated Jun. 21, 2012, 17 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated Dec. 15, 2014, 6 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated Feb. 24, 2010, 22 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/426,993, dated Mar. 29, 2013, 15 pages. |
Non Final Office Action received for U.S. Appl. No. 16/384,010, dated Sep. 30, 2020, 22 pages. |
Preliminary Amendment filed on Aug. 5, 2020, for U.S. Appl. No. 16/384,010, 6 pages. |
Final Office Action Received for U.S. Appl. No. 16/384,010, dated Feb. 8, 2021, 23 pages. |
Non Final Office Action Received for U.S. Appl. No. 16/384,010, dated Jul. 7, 2021, 9 Pages. |
Number | Date | Country | |
---|---|---|---|
20200082468 A1 | Mar 2020 | US |
Number | Date | Country | |
---|---|---|---|
60437199 | Dec 2002 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15643874 | Jul 2017 | US |
Child | 16411577 | US | |
Parent | 14318525 | Jun 2014 | US |
Child | 15643874 | US | |
Parent | 10648125 | Aug 2003 | US |
Child | 14318525 | US |