Product identification using multiple services

Information

  • Patent Grant
  • 11263679
  • Patent Number
    11,263,679
  • Date Filed
    Monday, April 15, 2019
    5 years ago
  • Date Issued
    Tuesday, March 1, 2022
    2 years ago
Abstract
A method and a system to determine a product identification of an item for sale in an online publication system is shown and described. For example, the method may be initiated when an input identifying an item is received from a user. An input type (e.g., image, text, audio recording, etc.) may be determined and one or more identification services may be selected based on the input type. At least a portion of the input is transmit to the selected one or more identification services. A product identification is received from each of the one or more identification services. Based on the received product identifications, a recommended product identification is determined. The recommended product identification is transmitted to the user.
Description
TECHNICAL FIELD

The present application relates generally to the technical field of computer technology and data processing and, in one specific example, to product identification using multiple services.


BACKGROUND

In an online publication system, users may submit data such as images, voice recordings, and text for publication. The data may be augmented by a description or other information that is provided by the user. In systems where one or more users may repeatedly submit the same or similar data, the submission of the data may be redundant and cumbersome to the user.





BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:



FIG. 1 is a network diagram of an example computing environment according to various embodiments.



FIG. 2 is a block diagram of an example publication system according to various embodiments.



FIG. 3 is a flowchart of a process for generating a listing as performed in some embodiments.



FIG. 4 is a flowchart of an example process for selecting a product identification.



FIG. 5 is a block diagram of an exemplary computer system according to some embodiments.





DETAILED DESCRIPTION

Example methods and systems to identify products using multiple product identification services are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of example embodiments. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details.


In an online publication system such as in an online shopping environment or online registry where users can post listings of items or services for sale, it may be desirable to provide an abbreviated posting process for users who regularly post to the online publication system. These users may have preferences regarding how the postings are presented to other users or have preferences regarding content that is repeated in each posting. Some of these users make few changes to a new posting relative to a previous posting. This is especially true if the new posting is for an item or service similar to an item or server in the previous posting.


For example, in online publication systems that are associated with an online shopping environment, the users may comprise sellers who sell goods on the online shopping environment. The sellers may have regular policies such as return policies, shipping policies, payment policies, and the like that apply to at least a portion of the seller's postings.


Some online shopping environments may have a catalog of products that describe identical or nearly identical items for sale. A product may be, in one example, a particular make and model of a computer printer. When a seller decides to sell a printer of that particular make and model, the seller may associate the printer for sale to the product in the catalog that describes the make and model of the printer. The catalog may be divided by domains or types of products. The products in the catalog may include a description, one or more images, reviews of the products, or the like. Some sellers find it desirable to associate their postings and items for sale with a product in the catalog to help potential buyers identify their items for sale.


According to various embodiments, an input is received from a seller that identifies an item for sale. The input may be a barcode (or image of a barcode), an image of the item for sale, a voice recording, a text string, etc. The input is analyzed and transmitted to one or more identification services which identify the item for sale as a particular product. Upon receipt of possible product identifications from the identification services, a recommended product identification to associate with the item for sale is selected. The product identification that is ultimately associated with the item for sale may depend on various factors such as, but not limited to, a proportion of identification services identifying the item for sale as the product, seller history, demand information, etc.


Some sellers may wish to more easily associate their item with a product in a catalog without taking the time to browse through a catalog, input a long text string, or perform other time-consuming tasks. The products and the catalog may be used to generate a posting from a remote location or from a device such as a handheld device.


The systems and methods described herein generally provide a fast and easy way to identify an item for sale, associate the item for sale with a product in a catalog, and generate a listing that includes one or more seller preferences to be posted in an online publication system such as an online shopping environment.


Architecture



FIG. 1 is a network diagram of an example computing environment according to various embodiments. A networked system 100, in the example forms of a network-based marketplace or publication system, provides server-side functionality, via a network 108 (e.g., the Internet or Wide Area Network (WAN)) to one or more clients. FIG. 1 illustrates, for example, a web client 110 (e.g., a browser, such as the Internet Explorer® browser developed by Microsoft Corporation of Redmond, Wash. State), and a programmatic client 112 executing on respective client machines 102 and 104.


One or more application servers 106 host one or more marketplace systems 114, payment systems 116, and publication systems 118. The application servers 106 are, in turn, shown to be coupled to one or more databases servers 120 that facilitate access to one or more databases 122.


The marketplace systems 114 may provide a number of marketplace functions and services to users that access the networked system 100. The payment systems 116 may likewise provide a number of payment services and functions to users. The payment systems 116 may allow users to accumulate value (e.g., in a commercial currency, such as the U.S. dollar, or a proprietary currency, such as “points”) in accounts, and then later to redeem the accumulated value for products (e.g., goods or services) that are made available via the marketplace systems 114. While the marketplace and payment systems 114 and 116 are shown in FIG. 1 to both form part of the networked system 100, it will be appreciated that, in alternative embodiments, the payment systems 116 may form part of a payment service that is separate and distinct from the networked system 100.


The publication systems 118 within the application servers 106 may provide publication functions and services to users that access the networked system 100. Additionally or alternatively, the publication systems 118 provide one or more user interfaces for users to generate, transmit, and review products and items for sale within the network-based marketplace. In some instances, the publication systems 118 may form a part of the marketplace systems 114 or be separate from marketplace systems 114.


Further, while the networked system 100 shown in FIG. 1 employs a client-server architecture, the present embodiments are of course not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system, for example. The various marketplace, payment, and publication systems 114, 116, and 118 could also be implemented as standalone software programs, which do not necessarily have networking capabilities.


The web client 110 accesses the various marketplace, payment, and publication systems 114, 116, and 118 via a web interface. Similarly, the programmatic client 112 accesses the various services and functions provided by the marketplace, payment, and publication systems 114, 116, and 118 via a programmatic interface provided by an API server. The programmatic client 112 may, for example, be a seller application (e.g., the TurboLister application developed by eBay Inc., of San Jose, Calif.) to enable sellers to author and manage listings on the networked system 100 in an off-line manner, and to perform batch-mode communications between the programmatic client 112 and the networked system 100.



FIG. 1 also illustrates a number of identification services such as identification service A 124, identification service B 126, and identification service N 128. The identification services 124, 126, and/or 128 may be a part of the application servers 106 or may be separate from the application servers 106. The identification services 124, 126, and/or 128 may receive an input from a client machine 102 or 104 or the application servers 106, and, in particular, the publication systems 118. Based on the input, the identification services 124, 126, and/or 128 provide a product identification of the item for sale as a particular product. For example, an input to an identification service may comprise an image of an item that a user wishes to offer to sell in the online market place. The identification service may compare the image to one or more images of known products to determine a closest match to the item in the image. In some instances, the various identification services may be categorized according to the input that each may receive and analyze. For example, identification service A 124 may identify a product based on an image, identification service B 126 may identify a product based on a barcode, and identification service N 128 may identify a product based on an audio recording.



FIG. 2 is a block diagram of an example publication system 200 according to various embodiments. In some instances, the publication system 200 may be the publication system 118 of FIG. 1. The publication system 200 may comprise a communication module 202 configured to communicate with the marketplace system 114 and the payment system 116. The communication module 202 may also communicate with the identification services 124, 126, and 128, and with the client machines 102 and 104 via the network 108. In some instances, where an external database is accessed during the course of operation, the communication module 202 may communicate with the database server(s) 120 and the database(s) 122.


A type identifier 204, upon receiving an input from a user via the network 108, determines an input type. The input type may be an image, a text string, an audio file, a video, etc. In some instances, the type identifier 204 may identify words, bar codes, and/or symbols from an image file.


Based on the input type identified, a service selector 206 selects one or more identification services 124, 126, and/or 128 to identify the item for sale. The selection may be based on the input received from the seller, a cost charged by the identification service, or on capabilities of the identification service. The service selector 206 may be modified by an administrator based on, for example, one or more preferences for identification services such as past performance of the respective identification services and relative costs for using the identification service. For example, the service selector 206 may, if a barcode has been scraped from a image of an item for sale by the type identifier 204, send only the bar code portion of the input to an identification service that is limited to identifying bar codes rather than a more expensive identification service able to recognize a product from a image.


In some instances, the service selector 206 may include and/or access a contracts database (not shown). The contracts database stores information related to one or more contracts with each of the identification services 124, 126, and 128. For example, the information may include a threshold number of identifications the identification service is contracted for over a specified period of time (e.g., 10,000 identifications per month), a graduated rate (e.g., first 2,000 identifications for a first rate, the next 2,000 identifications for a second rate, and so on), a per-identification cost of the service, and the like. In some instances, the service selector 206 may record the number of identifications sent to a particular identification service and/or track compliance to the service contract. In some instances, the service selector 206 may include one or more heuristics or artificial intelligence modules (e.g., a neural network) for selecting an identification service based on the contractual requirements, the cost per identification, or the like.


An identification selector 208 receives one or more product identifications from each of the identification services 124, 126, and 128 that the input or a portion of the input was sent to by the service selector 206. Based on the product identifications, the identification selector 208 selects the most relevant product identification from the received product identifications. In some instances, the identification selector 208 may provide a display of an organized list of the received product identifications for display to a user so that the user may select a product identification to associate with the item for sale. In other instances, the identification selector 208 may automatically select a single product identification from more than one product identifications as described, for example in connection with FIG. 4.


If the identification selector 208 does not receive a product identification from the identification services (e.g., no matches are found), the identification selector 208 transmits a user interface to the user at the client machine 102 or 104. The user interface may be used to manually select or identify a product identification corresponding to the item for sale.


The identification selector 208 may access a product database 210. The product database 210 may be a part of the database(s) 122 shown in FIG. 1 or may be a separate database specific to the publication system 200. The product database 210 stores descriptions of the products. In some instance, the product database 210 additionally stores a location of the product in a catalog, sales history of the product, and one or more items for sale corresponding to the product.


When the item is identified with a product identification, a category selector 212 selects a category for the item for sale from one or more potential categories. The category selector 212 may rely on factors such as a category where the product sold for a highest price, past user queries for the product, or pre-defined category preferences of the user providing the posting for publication. In some instances, the category information may be stored in a catalog database (not shown). The category selector 212 may provide a user interface if the item for sale corresponds to a product that is categorized in more than one way. The user may then manually provide the category using the user interface. For example, a particular make and model of a printer may be categorized as a “computer peripheral,” a “home electronic device,” and/or an “office supply.”


The category selector 212 may, in some embodiments, provide an interface to the user to select a category based on factors such as highest price, fastest selling time, highest visibility, categories where the seller has other active listings or routinely posts listings, or the like. In other instances, the category selector 212 may automatically select a category based on the product identification of the item for sale.


A listing generator 214 generates a listing for the item for sale to be published within the publication systems 200. The listing generally includes the product information of the item for sale, a condition of the item for sale, seller information, sale format (e.g., auction, fixed price, etc.), price, shipping information, etc. The listing generator 214 may provide an interface for the user to provide information not included in the product information or may populate a listing using one or more databases and/or modules.


To illustrate, to provide shipping information in a listing, a shipping selector 216 may determine a location of the user (e.g., seller) when the user provides the input. The location of the user is based on, for example, an IP address, a GPS location received via a GPS module on a handheld device, a cell triangulation technique, or the like. Based on the location of the user, one or more shipping options are identified. The shipping selector 216 may provide an interface for the user to select at least one of the shipping options available, or the shipping selector 216 may automatically select the at least one shipping option available based on, for example, a stored seller preference.


To populate the listing, a seller database 218 is accessed by the listing generator 214. The seller database 218 stores seller preferences such as, seller information, whether seller accepts returns, return policies, a number of days to return an item, how to return an item, who bears the cost of a returned item, payment policies, sale format, a minimum price if sale format is an auction, fixed price if sale format is fixed price, quantity, shipping cost, shipping carrier, condition, etc. In some instances, the seller database 218 may include more than one set of preferences for the seller. In these instances, the listing generator 214 may provide an interface for the seller to select a set of preferences to associate with that particular listing.


If a set of seller preferences is incomplete or if the seller has not set a default for a particular preference, the listing generator 214 may provide a user interface to be displayed to the user at the client machine where the user can select an option from a menu. The menu may be generated based on selections previously made by the user. In some embodiments, the user interface may allow the user to manually enter a preference.


The listing generator 214 may provide the generated listing to the client machine for display to the user. The user may, in turn, accept or reject all or part of the generated listing. Upon the user accepting the generated listing, the listing is published. If the user rejects some or all of the generated listing, an interface may be provided to the user where the user can manually input changes and/or select changes from a menu. In some instances, the system may save the unapproved listings and allow the user to modify the listing at a later time.



FIG. 3 is a flowchart of a process 300 for generating a listing as performed in some embodiments. The process 300 may be performed by the publication systems 118 or 200. The process 300 permits the seller of an item for sale to post a listing in an online publication system based on an input such as an image of the item for sale.


In an operation 302, the input is received from the seller via a client machine and a network. The input may comprise an image, a bar code, a text string, a voice recording, a video recording, or the like. In some instances, the input is captured by a handheld device (e.g., a mobile telephone or smart phone) having a camera, microphone, text input (e.g., keypad), and/or barcode reader.


In an operation 304, an input type is determined. The input may be an image, a bar code, a text portion of the image, a symbol or logo within an image, an audio file, a video file, a text string, etc. Examples of input types include, but are not limited to: whole image, partial image of text, partial image of barcode, barcode, ISBN, video, audio, and text.


In an operation 306, one or more identification services are determined. The identification services may be determined based on the input type determined in operation 304, relative cost of identification services, relative accuracy of the identification services, and the like. Once the identification services are determined, the input (or a portion of the input) is sent to the identification services. For example, a bar code parsed from an image of the entire item may be sent as a portion of the input to a bar code identification service.


The input may be sent to the one or more identification services sequentially or simultaneously. The determination of the identification services and/or whether the input is sent to each at the same time or at different times may be based on a pre-defined policy and/or as determined by the service selector 206 (FIG. 2). In some instances, the policy may identify more than one identification service if a determination is made that receiving an accurate product identification is more likely using a combination of identification services. To illustrate, an image identification service may be used, in part, to identify a barcode in a larger image. That barcode may, in turn, be sent to a bar code identification service.


In an operation 308, the product identifications are received from the identifications services to which the input was sent in operation 306. The product identifications may be alphanumerical based on SKU numbers, bar codes, ISBN numbers, etc. In some embodiments, the product identification may be based on a product catalog.


In an operation 310, a recommended product identification is determined. The recommended product identification may be based on one or more product identifications received from the product identification services. Generally, at least two product identifications are received, although any number of product identifications are contemplated. In some instances, a first portion of the product identifications may be received from product identification services outside of the online publication system and a second portion may be determined by an internal identification service (not shown) with the publication systems 118. The two or more product identifications are compared, and, if matching, used as the recommended product identification.


If, however, the product identifications do not match, other recommended product identifications are determined in a variety of ways. For example, a recommended product recommendation may be selected by the identification selector 208 from the received product identifications, the input may be sent to at least one additional product identification service to receive additional product identifications, the input may be further analyzed, and/or the user may be prompted to re-capture and/or re-submit the input of operation 302.


In an operation 312, a recommended price is determined. The recommended price may be based on past sale prices (e.g., stored in the product database) of the product corresponding to the recommended product identification. In some embodiments, a price recommendation may be modified based on an amount of time another item for sale corresponding to the same product has been posted without selling, a number of searches by potential buyers for the product, or the like. In some instances, pricing information may be collected from other merchants or publication systems via the network 108 (FIG. 1) using, for example, a web bot or a web crawler.


In an operation 314, a recommended category is determined. For some products, there may be only one category based on the catalog. However, for a significant portion of products, the same product may be listed in more than one category or in more than one location in a catalog. In some instances, a plurality of distinct product catalogs may be available based, for example, on product domains. Product domains are types of products such as, for example, autos, jewelry, toys, collectibles, house wares, electronics, etc.


A recommended category may be based on, for example, relative sale price of the product within each potential categorization, a time to sell within each categorization, a relative visibility of each categorization, or similar concerns. A recommended price may be independently determined for each possible category. The recommended category may also be based on seller preferences or seller history. In some instances, more than one category may be ultimately recommended to a seller. The recommended category may, additionally or alternatively, be based on categorizations developed by publication systems other than publication system 200. These categorizations may be collected via, for example, a web bot, web crawler, or information provided by manufacturers, resellers, distributors, other merchants and marketplaces, or the like.


In an operation 316, shipping options are determined based on a location of the seller or the item. The origin is determined by way of a geographical location of the client machine from which the input is received. In some instances, the client machine may be a mobile, portable, or handheld device having GPS or cellular capabilities. In some instances, a seller may have predefined shipping preferences stored in a seller profile on which the shipping options may be based.


In an operation 318, the seller policies are determined. Seller policies may include handling time (i.e., an amount of time to process a completed transaction), return policy, and/or accepted payment methods. Each seller policy may be aggregated with other policies of the same seller in a seller profile corresponding to the seller. The seller profile is accessible by the seller when generating a listing.


In some instances, a single seller may have more than one seller profile. Each profile includes an aggregate of seller policies that the seller may, in turn, define separately. The profiles of a single seller may be more or less complete relative to the other profiles. For example, a first profile may include a return policy, a handling time, and payment methods while a second seller policy may only include payment methods. The payment methods policy in the first seller profile may be the same as or different from the payment methods policy in the second seller profile.


If the seller has more than one seller profile, the seller may have the option of applying different seller profiles based on the listings themselves or on the categories associated with those listings. For example, a first profile comprising a return policy and a handling time policy may be directed to media goods like compact discs. The seller may also be associated with a second profile for listings in a clothing category that may, in turn, include an exchange policy or a longer handling time to fulfill custom orders. The seller may manually select the seller profile for each listing. Alternatively, a seller profile may be selected based on a recommended category of the listing.


In some instances, the publication system 200 may provide or recommend seller policies or changes to a seller profile based on past behavior of the seller or the seller profiles of other sellers offering the same or similar items for sale. In response to a determination that certain seller polices are popular or unpopular with buyers, the more popular seller policies may be recommended to sellers having less popular seller policies. This determination based, for example, on buyer surveys, buyer complaints, and/or a determination that a buyer chose to buy the same (or similar) good from one seller over another based on a seller policy.


In an operation 320, the listing is generated by aggregating the recommended product identification, price recommendation, categorization, shipping options, and seller policies according to a predetermined template or format. In some instances, the format of the listing may be seller-specific. For example, some sellers may use a template to format listings and/or prefer a particular font, text size, background graphic, or layout.


In an operation 322, the generated listing is transmitted to the client machine. The user may view the generated listing and confirm that the information in the listing is accurate and desirable. In some instances, a user interface may be provided for the user to add, delete, or modify portions of the listing. Menus or separate user interfaces may allow the user to select potential modifications from a menu. For example, if the user identifies that the product identification is incorrect, the user interface may include a menu having one or more alternative product identifications distinct from the recommended product identification. A similar user interface may be provided to modify a categorization or a seller policy, for example. Other portions, such as price, may be modified via a text field.


In instances where a recommended product identification is incorrect and the alternate product identifications (if provided) are also incorrect, a user interface for manually selecting a product from a catalog to associate with the item for sale is provided. A categorization may be additionally or alternatively selected in this fashion. When a correct product identification or categorization is identified by a user, the other portions of the listing (e.g., price, shipping, seller polices) may be determined by the publication system as described above.


When the seller confirms that the listing is correct, the listing is published in the online publication system for potential buyers to view and purchase. It is noted that throughout process 300, a seller may be prompted to provide additional input regarding any portion of the listing to be generated. For example, in the operation 314, a prompt may be provided to the seller to confirm the recommended product category. The prompt may include information about each category such as, for example, recommended price, expected time to sell, or visibility of the category.



FIG. 4 is a flowchart of an example process 400 for selecting a recommended product identification from more than one received product identification. Generally, the recommended product identification may be selected using a variety of algorithms and techniques such as heuristics, thresholds, artificial intelligence such as neural networks, etc. The process 400 is provided for the purposes of illustration and is not intended to be limiting. It is noted that alternatives are readily apparent to those skilled in the art.


In an operation 402, the product identifications are received from the product identification services. The received product identifications may be supplemented by one or more product identifications determined by product identification services internal to the publication system itself. Each of the product identifications may be associated with an initial product score that can be incremented and/or decremented based on a set of heuristics. The product score may be used to ultimately select the recommended product identification.


In an operation 404, a determination is made as to whether product identifications based on a bar code match one another. If at least two product identifications match, the product score is incremented in an operation 406. It is noted that more than one product score may be incremented. For example, if four product identifications are received and two match a first product while the other two match a second product, both product scores may be incremented. Each item corresponding to a product identification may be associated with a product score. In instances where more than two product identifications identify the same item (e.g., using a bar code or other feature), the product score may be incremented based on the number of matching product identifications.


In an operation 408, a determination is made as to whether product identifications based on a text string match. The text string may be input by the user directly or indirectly. To indirectly input a text string, the user may, for example, capture on image of text, such as a title of a book, and the text may be captured using an optical character recognition (OCR) technique. If at least two of the product identifications match, the product scores may be incremented in the operation 410.


In an operation 412, a determination is made as to whether product identifications based on an image match. Based on the determination of operation 412, the product score may be incremented in operation 414. Similarly, in an operation 416, a determination is made as to whether product identifications based on a voice recording match, and, in an operation 418, a product score may be incremented accordingly.


In an operation 420, a determination is made as to whether a particular product identification matches an item previously sold by the seller. In some instances, a seller has more than one item for sale corresponding to a particular product. As such, if a seller has previously sold a particular item, it is more likely that the present item for sale matches the previous item for sale. In an operation 422, the product score may be incremented based on the determination of operation 422.


In an operation 424, a determination is made based on a demand for a particular product. The demand may be determined based on a number of searches or user queries for the product by a potential buyer, an average or median amount of time elapsed before sale of the product, a change in price associated with the product, and/or other factors. Based on the demand for the product being higher than the demand for another product and/or meeting a predefined threshold (e.g., number of queries), the product score may be incremented in an operation 426.


In an operation 428, a determination is made based on supply of the product. The supply is indicative of the number of items currently for sale that correspond to the product. The supply may be based solely on the seller, a portion of sellers, or all sellers. In operation 430, the product score may be incremented based on the determination that the supply is high. The determination that the supply is high may be measured relative to the other product identifications and/or be based on a threshold (e.g., a number of items currently for sale).


In operations 406, 410, 414, 418, 422, 426, and 430, the product score may be incremented in a variety of ways. For example, the amount that each product score is incremented may be weighted based on the determination(s) preceding the increment. The determinations may include a determination of an amount by which to increment the product score.


In an operation 432, the product score associated with each unique product identification is compared to each other product score or to a threshold. The greatest product score that meets or exceeds the threshold may be identified as the recommended product identification.



FIG. 5 is a block diagram of an exemplary computer system 500, according to some embodiments, within which may be executed a set of instructions for causing the computer system 500 to perform any one or more of the methodologies discussed herein. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a server computer, a client computer, a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.


The example computer system 500 includes a processor 502 (e.g., a central processing unit (CPU) a graphics processing unit (GPU) or both), a main memory 504 and a static memory 506, which communicate with each other via a bus 508. The computer system 500 may further include a video display unit 510 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 500 also includes an alphanumeric input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), a disk drive unit 516, a signal generation device 518 (e.g., a speaker) and a network interface device 520.


The disk drive unit 516 includes a machine-readable medium 522 on which is stored one or more sets of instructions (e.g., software) 524 embodying any one or more of the methodologies or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504 and/or within the processor 502 during execution thereof by the computer system 500, the main memory 504 and the processor 502 also constituting machine-readable media.


The instructions 524 may further be transmitted or received over a network 526 via the network interface device 520.


While the machine-readable medium 522 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present embodiments. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.


Example embodiments described herein may provide technical benefits such as, but not limited to, efficient input of data into an online publication system, ease of locating a desired product within the online publication system by buyer, more efficient use of seller data to populate listings, and data collection by the user.


Thus, a method and system to automatically generate a listing using multiple identification services have been described. Although the present invention has been described with reference to specific example 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.


The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims
  • 1. A method comprising: receiving, at a network-based publication system, input from a client computing device communicating with the network-based publication system over a communications network, wherein the input comprises an identifier for an item; selecting, using a service selector, at least one identification service from a plurality of identification services, wherein selecting the identification service comprises:determining a data type of the input; andbased on the determined data type of the input, selecting the at least one identification service from the plurality of identification services;determining a product identification for the item using the at least one identification service selected by the service selector;providing a recommendation for a listing of the item; andcausing display of the recommendation for the listing on the client computing device.
  • 2. The method of claim 1, wherein the input comprises data relating to at least one of: an image, a bar code, a text string, a voice recording, or a video recording.
  • 3. The method of claim 1, further comprising determining an input type for the input, wherein the input type includes at least one of: text, image, video, audio, bar code, or ISBN.
  • 4. The method of claim 3, wherein selecting the at least one identification service is further based on at least one of: a cost of the plurality of identification services, or accuracy of the plurality of identification services.
  • 5. The method of claim 1, wherein selecting the at least one identification service is further based on a pre-defined policy specifying a priority of use for the plurality of identification services.
  • 6. The method of claim 1, wherein determining the product identification comprises identifying the product identification in a product catalog.
  • 7. The method of claim 1, further comprising determining a recommended price for the item, wherein the recommended price is based on existing sales prices of the item.
  • 8. The method of claim 1, further comprising determining a recommended category for the item, wherein the recommended category is determined using a product catalog.
  • 9. The method of claim 1, further comprising determining shipping options for the item based on a location of a seller of the item.
  • 10. The method of claim 1, further comprising determining one or more seller policies for the item, wherein the one or more seller policies comprise at least one of: handling time for the item, a return policy, or a payment method.
  • 11. The method of claim 1, wherein the listing of the item comprises the product identification and at least one of: a price recommendation for the item, a recommended category for the item, shipping options, or a seller policy.
  • 12. The method of claim 1, further comprising receiving, from a seller, confirmation that the listing of the item is correct.
  • 13. A system comprising: at least one processor; andmemory encoding computer executable instructions that, when executed by the at least one processor, perform a method comprising: receiving, at a network-based publication system, input from a client computing device communicating with the network-based publication system over a communications network, wherein the input comprises an identifier for an item;selecting, using a service selector, at least one identification service from a plurality of identification services based at least upon the input, wherein the service selector selects an identification service based upon a type of the input for the item;providing the input to the selected identification service;receiving, from the selected identification service, one or more product identifications corresponding to the input;determining a recommended product identification from the one or more product identifications;providing the recommended product identification; andcausing display of the recommendation for the listing on the client computing device.
  • 14. The system of claim 13, wherein the text-based identifier is a product name of the item or a product description for the item.
  • 15. The system of claim 13, wherein the one or more product identifications are determined using at least one of: heuristics, thresholds, artificial intelligence, or a neural network.
  • 16. The system of claim 13, wherein the one or more product identifications are each associated with a respective product score indicating a similarity between a respective product identification and the input.
  • 17. The system of claim 16, wherein the recommended product identification is a product identification having a highest product score of the respective product scores for the one or more product identifications.
  • 18. The system of claim 17, wherein the list of one or more items is sorted based on the respective product scores for the one or more product identifications.
  • 19. The system of claim 13, wherein providing for display the list of one or more items comprises: generating an item listing for the item, wherein the item listing comprises the one or more product identifications; andproviding the item listing to a seller of the item.
  • 20. A method comprising: receiving, at a network-based publication system, input from a client computing device communicating with the network-based publication system over a communication network, wherein the input comprises an identifier for an item;selecting an identification service from a plurality of identification services based on the input for the item, wherein selecting the identification service comprises: determining a data type of the input; andbased on the determined data type of the input, selecting at least one identification service from the plurality of identification services;providing the input to the at least one identification services;receiving, from the at least one identification services, one or more product identifications corresponding to the input;determining a recommended product identification from the one or more product identifications;providing an item listing of the item based on the recommended product identification; andcausing display of the recommendation for the listing on the client computing device.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/792,133 filed Jul. 6, 2015, entitled “PRODUCT IDENTIFICATION USING MULTIPLE SERVICES,” now U.S. Pat. No. 10,319,018, which is a continuation of U.S. application Ser. No. 13/663,178 filed on Oct. 29, 2012, entitled “PRODUCT IDENTIFICATION USING MULTIPLE SERVICES,” now U.S. Pat. No. 9,076,173, which application is a continuation of U.S. application Ser. No. 12/605,212 filed on Oct. 23, 2009, entitled “PRODUCT IDENTIFICATION USING MULTIPLE SERVICES”, now U.S. Pat. No. 8,301,512, the entirety of each of which is incorporated herein by reference thereto.

US Referenced Citations (196)
Number Name Date Kind
5537586 Amram et al. Jul 1996 A
5664115 Fraser Sep 1997 A
5710578 Beauregard et al. Jan 1998 A
5740425 Povilus Apr 1998 A
5758257 Herz et al. May 1998 A
5822123 Davis et al. Oct 1998 A
5844554 Geller et al. 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 Papiemiak 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. Dec 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 Fork 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 Horn Jan 2009 B1
7631065 Schweitzer et al. Dec 2009 B2
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 et al. Sep 2012 B1
8301512 Hamilton et al. Oct 2012 B2
8306872 Inoue et al. Nov 2012 B2
8352334 Ulinski Jan 2013 B2
8401710 Budhraja et al. Mar 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 Grove et al. Jun 2019 B2
20010032163 Fertik et al. Oct 2001 A1
20010034694 Elias Oct 2001 A1
20010037251 Nojima et al. Nov 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 et al. 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 et al. 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 et al. 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 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 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 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 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
20200082468 Grove et al. Mar 2020 A1
Foreign Referenced Citations (12)
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
2007078560 Oct 2007 WO
2007061975 Oct 2007 WO
Non-Patent Literature Citations (94)
Entry
Response to Non-Final Office Action filed on Jan. 3, 2005 for U.S. Appl. No. 10/648,125, dated Sep. 1, 2004, 18 pages. (Year: 2005).
“New Test and Social Messaging Features Expand Frucall's Voice-Based”, Primezone (Aug. 31, 2006), 1 page. (Year: 2012).
“MyComicShop.com”, Search for Mad (Magazine #24) on #158, [Online], Retrieved from the Internet: http://www.mycomicshop.com/search?tid=35327&pgi = 151, (Accessed Feb. 10, 2012), 22 pages. (Year: 2012).
Response to Non-Final Office Action filed on Jan. 5, 2015, for U.S. Appl. No. 13/663,178, dated Oct. 3, 2014, 14 pages. (Year: 2015).
Final Office Action received for U.S. Appl. No. 14/318,525, dated Feb. 12, 2015, 19 pages. (Year: 2015).
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.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2006/044944, dated Jun. 5, 2008, 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.
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, 5 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.
Response to Notice of Non-Compliant Amendment filed on Oct. 26, 2015, for U.S. Appl. No. 14/792,133, 5 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.
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.
Ukiva, “Machine Vision Handbook”, 2007, 16 pages.
International Written Opinion received for PCT Application No. PCT/US2006/044944, dated May 10, 2007, 3 pages.
International Search Report received for PCT Application No. PCT/US2006/044944, dated May 10, 2017, 2 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, mailed on 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, mailed on 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, mailed on 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, mailed on 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 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.
Non Final Office Action received for U.S. Appl. No. 12/605,212 dated 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.
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 Sep. 24, 2015, 31 pages.
Non-Final Office Action received for U.S. Appl. No. 14/318,525, dated Sep. 1, 2016, 43 pages.
Non-Final Office Action received for U.S. Appl. No. 15/643,874, dated Apr. 18, 2018, 34 pages.
Preliminary Amendment received for U.S. Appl. No. 14/318,525, dated 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, 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.
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.
Kotas, et al., “Use of Electronic Catalog to Facilitate User-to-User Sales”, U.S. Appl. No. 60/336,409, filed Oct. 31, 2001, Oct. 31, 2001, 45 pages.
Demand for Preliminary Examination received for U.S. Patent Application No. PCT/US2003/041543 dated Jun. 10 2004, 5 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2003/041543, dated Apr. 27, 2005, 6 pages.
International Search Report received for PCT Patent Application No. PCT/US2003/041543, dated Apr. 14, 2004, 7 pages.
International Written Opinion received for PCT Patent Application No. PCT/US2003/041543, dated Aug. 26, 2004, 9 pages.
First Action Interview-Office Action Summary received for U.S. Appl. No. 14/792,133, dated Feb. 9, 2018, 5 pages.
Non Final Office Action Received for U.S. Appl. No. 16/411,577 dated Sep. 2, 2020, 16 pages.
Preliminary Amendment filed on Oct. 17, 2019 U.S. Appl. No. 16/411,577, 7 pages.
Notice of Allowance received for U.S. Appl. No. 14/318,525, dated Mar. 10, 2017, 14 pages.
Applicant Initiated Interview summary received for U.S. Appl. No. 16/411,577 dated Oct. 30, 2020, 3 pages.
Response to Non-Final Office Action filed on Dec. 2, 2020 for U.S. Appl. No. 16/411,577, dated Sep. 2, 2020, 12 pages.
Final Office Action received for U.S. Appl. No. 16/411,577 dated Feb. 16, 2021, 25 pages.
Advisory Action Received for U.S. Appl. No. 16/411,577, dated May 27, 2021, 3 Pages.
Notice of Allowance received for U.S. Appl. No. 16/411,577, dated Aug. 12, 2021, 15 pages.
Corrected Notice of Allowability Received for U.S. Appl. No. 16/411,577, dated Oct. 13, 2021, 2 Pages.
Related Publications (1)
Number Date Country
20190244269 A1 Aug 2019 US
Continuations (3)
Number Date Country
Parent 14792133 Jul 2015 US
Child 16384010 US
Parent 13663178 Oct 2012 US
Child 14792133 US
Parent 12605212 Oct 2009 US
Child 13663178 US