US20120130908A1 - Voice recognition method and apparatus using model number lookup - Google Patents

Voice recognition method and apparatus using model number lookup Download PDF

Info

Publication number
US20120130908A1
US20120130908A1 US13/361,405 US201213361405A US2012130908A1 US 20120130908 A1 US20120130908 A1 US 20120130908A1 US 201213361405 A US201213361405 A US 201213361405A US 2012130908 A1 US2012130908 A1 US 2012130908A1
Authority
US
United States
Prior art keywords
product
consumer
identifier
information
vru
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/361,405
Inventor
Dean O'Connor
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
E2interactive Inc
Original Assignee
Nintendo of America Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nintendo of America Inc filed Critical Nintendo of America Inc
Priority to US13/361,405 priority Critical patent/US20120130908A1/en
Publication of US20120130908A1 publication Critical patent/US20120130908A1/en
Assigned to SIRAS.COM INC. reassignment SIRAS.COM INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NINTENDO OF AMERICA INC.
Assigned to E2INTERACTIVE, INC. D/B/A E2INTERACTIVE, INC. reassignment E2INTERACTIVE, INC. D/B/A E2INTERACTIVE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SIRAS.COM INC.
Assigned to JPMORGAN CHASE BANK, N.A. reassignment JPMORGAN CHASE BANK, N.A. PATENT SECURITY AGREEMENT Assignors: E2INTERACTIVE, INC.
Assigned to BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT reassignment BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT PATENT SECURITY AGREEMENT Assignors: E2INTERACTIVE, INC.
Assigned to E2INTERACTIVE, INC. reassignment E2INTERACTIVE, INC. RELEASE OF PATENT SECURITY INTEREST Assignors: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Assigned to NINTENDO OF AMERICA INC. reassignment NINTENDO OF AMERICA INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: O'CONNOR, DEAN
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/487Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083Shipping
    • G06Q10/0837Return transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/01Customer relationship services
    • G06Q30/012Providing warranty services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/487Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H04M3/4936Speech interaction details
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2201/00Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/40Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition

Definitions

  • the present invention relates to voice recognition units or systems (VRUs) for enabling users to remotely obtain information in an efficient and accurate manner from a database using voice commands and/or responses over a telephone system. More particularly, the invention relates to a VRU system that enables users to obtain information regarding return, warranty, replacement and/or repair of previously purchased products from an electronic product registration (ER) system, such as the type disclosed in U.S. Pat. Nos. 5,978,774 and 6,018,719, the disclosures of which are incorporated by reference herein in their entirety.
  • ER electronic product registration
  • Electronic registration (ER) systems rely on the use of a unique identifier, such as a serial number, for each product that is purchased.
  • the serial number is obtained at the point of sale for inclusion in a registration database, together with other information, such as a date of transaction.
  • This database can then be accessed in connection with an attempted product return/warranty transaction for the purpose of determining if the product qualifies for return/warranty under applicable return/warranty criteria (which is also stored in or made available to the system).
  • Such electronic systems may also be used in connection with repair and/or exchange transactions, in addition to returns, by enabling an accurate determination as to whether the product qualifies for any of these actions under the appropriate policies and criteria under which the product was originally sold.
  • the ER system uses pre-established return/repair policies and procedures that are programmed into the system so that the system can perform a check when a product is presented for return to determine if the product qualifies for return, replacement and/or warranty repair based on sales transaction information available in the ER system for the particular product at issue.
  • known ER systems include a database of return qualification information (or warranty/replacement criteria) for various manufacturer's which enables the system to make an accurate determination with respect to whether or not a particular product or item (that is uniquely identified by the system using a serial number or other unique identifier) actually qualifies for return (or warranty/replacement) based on the appropriate qualification criteria.
  • return qualification information or warranty/replacement criteria
  • ER systems have, in the past, used a unique identifier for each product that is registered, thereby enabling the system to provide return qualification information respect to the particular product being returned.
  • Voice recognition systems for accessing the ER database have also been based on unique identifiers.
  • products that do not include a unique identifier associated therewith have not been able to be incorporated into ER systems for access by VRU systems.
  • Voice recognition systems have been successfully used in the past in connection with electronic registration systems for purchased products for the purpose of enabling users to obtain information about return, warranty, replacement and/or repair of the purchased products.
  • Voice recognition (VRU) systems have been used in the connection with such electronic registration (ER) systems to enable remote access to the registration data that is collected by the ER system. Due to the fact that the ER systems have been based on serialized products (i.e., products each having a unique serial number), the VRU systems used therewith have also been based on the use of serial numbers.
  • An example of a VRU system that uses serial numbers is disclosed in PCT application No. PCT/US01/25296 filed Aug. 14, 2001 (Atty Docket No. 723-1159), and entitled “Voice Recognition Method and Apparatus Using Dynamic Link Library”, the disclosure of which is incorporated by reference herein.
  • the instant invention provides an improved VRU system that has increased functionality, by providing an enhancement to known VRU systems that enable information on non-serialized products (i.e., products that do not have a unique identifier) to be accessed by users in a manner that is similar to the serialized VRU systems.
  • non-serialized products i.e., products that do not have a unique identifier
  • the improved VRU system enables non-serialized data or identifiers to be used to access return/warranty qualification information that applies to a class or group of similar products.
  • model numbers or other non-serialized data such as UPC or SKU numbers
  • the invention enables information to be accessed through a VRU on products that may not have been originally intended for electronic registration, due to, for example, their price, nature or other characteristics.
  • the invention also enables products that have already been sold without collecting registration data at the point of sale to be added into the ER system for access by the VRU system.
  • the VRU system accesses a database that has been previously loaded with information on model numbers (or other non-unique identifiers) and applicable return and/or warranty criteria for products having these model numbers.
  • the database may also contain serialized information so that the VRU system can perform serial number (or other unique identifier) lookup operations and model number (or other non-unique identifier) lookup operations.
  • non-serialized information does not provide the same level of accuracy as a serialized system, in that specific sales information on a specific product is not available for the non-serialized products, the information is still useful in making logical decisions about whether or not the product qualifies for return or warranty based on information in the system about the entire class or group of products to which the product belongs.
  • a voice response system for use in obtaining return qualification information for a product using a non-unique product identifier.
  • the voice response system includes: a dial-in system operable to prompt a caller for the non-unique product identifier, wherein the non-unique product identifier identifies the product as a member of a defined product group; a product registration database including a plurality of different, non-unique product identifiers; a return policy storage that defines return policies for each of the non-unique product identifiers; and an arrangement that looks up a specific return policy for the non-unique product identifier entered by the caller and provides information to the caller regarding return qualification for the product identified by the non-unique product identifier.
  • a method for operating a voice response system. The method includes: storing different non-unique product identifiers into a system; storing a return policy in the system for each of the non-unique product identifiers, wherein the return policy defines criteria under which products having the non-unique product identifier associated with the policy can be returned; prompting a caller using a dial-in voice system for a non-unique identifier associated with a product for which a return is desired; Looking up the entered non-unique identifier to determine if it corresponds to one of the stored non-unique identifiers in the system; if the non-unique product identifier does correspond to a stored non-unique identifier, obtaining a stored return policy for that non-unique product identifier; and communicating return qualification information based on the stored return policy back to the caller through the voice system.
  • FIG. 1 is an exemplary high-level flow chart of the main features of the VRU system of the instant invention
  • FIG. 2 is an exemplary overall block diagram illustrating the operation of the instant VRU system in accordance with a preferred embodiment of the instant invention
  • FIG. 3 is an exemplary high-level flow chart illustrating the operation of the instant VRU system
  • FIG. 4 is a schematic diagram of the interaction between the VRU, DLL and database in accordance with a preferred embodiment of the instant invention.
  • FIG. 5 is a more detailed flow-chart illustrating a preferred embodiment of the operation of the instant VRU system
  • FIG. 6 is an exemplary block diagram illustrating the VRU watchdog feature of the instant invention.
  • FIG. 7 is an exemplary block diagram of the speech watchdog feature of the instant invention.
  • FIG. 1 shows a high-level flow chart of the main steps that are performed in accordance with the VRU model number lookup system of the instant invention.
  • non-unique product identifiers such as product model numbers or the like
  • the loaded model numbers define model numbers for which the system will be able to provide return qualification information to a requesting party.
  • a manufacturer, retailer or other party desires to utilize the system for the purpose of reducing the number of unauthorized returns, that party provides the models numbers of interest (or other non-unique product identifiers) so that they can be loaded into the system.
  • the party then also defines a return/warranty policy for each different model number that has been loaded into the system.
  • the policies are preferably based on some information that relates to the sale or shipment of products having the particular model numbers. For example, a policy may state that product having a particular model number cannot be returned X days after the last shipment of such products from the manufacturer to the retailer. Another example of a policy is one that states that products having a certain model number cannot be returned X days after the last sell-through date at the retailer or products having that model number. These are useful policies in reducing unauthorized returns, because they define a time period for return that logically relates to a legitimate return period.
  • the retailer can define a policy that states that no returns are allowed after X days (e.g., 90 days) from that date for products having that model number.
  • X days e.g. 90 days
  • this system may allow some improper returns, due to the fact that there is no way to know exactly when a particular product having the model number was purchased (or shipped).
  • the system at least can provide a logical cut-off date for returns based on the last sale (or shipment) date for all products having that model number, thereby still operating to reduce the number of unauthorized returns.
  • the system basically assumes that all products having that model number were purchased on the date the last one was purchased (even though this is likely not the case). This enables decisions to be made as to return qualification based on these last dates. Any policy can be used in accordance with the system with a group of products having the same non-unique product identifier depending on the particular desires of each retailer and/or manufacturer.
  • the invention has been described in the context of a VRU system. However, the invention has broader applications and can be used in a computerized look-up system as well as a VRU system.
  • the user would access the system through a web site or other computer communication and then be prompted for the model number or other non-unique identifier.
  • the computerized system would then look up the associated return/warranty policy for the product and provide return qualification information back to the user through the computer system (rather than through the VRU system).
  • a non-unique identifier such as a product model number
  • a product serial number is unique for each product, whereas more than one product (typically the same type of product) may have a non-unique identifier such as a product model number. While the description of the present invention will hereinafter refer to “model number”, those skilled in the art will understand that any non-unique identifier could be sent as at least part of a query to the database in accordance with the instant invention.
  • the caller will speak whether a serial number lookup or a model number lookup (or some other type of lookup) should be performed.
  • the VRU will then access the appropriate database based upon that spoken indication from the caller.
  • the VRU system is capable of automatically determining whether a spoken or keyed query provided by the caller is a product serial number query or a product model number query (or other type of informational query) just from the number itself and automatically accesses the appropriate database based upon that determination.
  • serial number lookup query is requested by the caller
  • serial number registration information is retrieved from the system, as described, for example, in the above-referenced PCT application.
  • the VRU then converts the information so that it is sent back to the caller.
  • policy information relating to products having that model number can be retrieved from the system.
  • the VRU can then convert this policy information so that it can be read back to the caller through the VRU system.
  • the VRU system of one embodiment of the instant invention enables users to obtain information regarding return, warranty, replacement and/or repair of previously purchased products using product model number information and without any type of information (e.g., serial number, purchase date/time and/or individual transaction information) being obtained at the time the product is purchased.
  • product model number information e.g., serial number, purchase date/time and/or individual transaction information
  • a retailer can effectively control the return, warranty, replacement and/or repair of purchased products even if the retailer did not collect any information at the time the products were purchased, or even have the ability of (or even contemplated) providing such control at the time the products were purchased, since no information at the point of sale is needed.
  • no information regarding the individual purchase transactions, particular purchase dates/times and/or serial numbers is needed to provide model number lookup in accordance with the instant invention.
  • policy or criteria information is needed that relates to the entire class or group of products that are covered by the model number or other non-unique identifier.
  • a policy may be defined for a particular product model number such that any purchased product having that model number cannot be returned X number of days after the last ship date from the manufacturer to the retailer of products having that model number.
  • This exemplary return policy can be instituted by the retailer and/or manufacturer without collecting any information at the time of sale and can thus be instituted after some or all of the sales of the products having that particular model number are completed.
  • the return policy for that particular model number has been defined before the caller provides the model number query to the database, the only additional information needed is the model number itself from the caller. Serial number, purchase date/time and/or other transactional data at the time of sale (or any time thereafter) is not required.
  • a VRU system using a model number lookup can operate at a lower cost since a registration system for obtaining information at the time of sale or any time thereafter is not needed.
  • the products do not have to be assigned unique identifiers.
  • a system which registers serial number, purchase date/time and/or other transactional information is not necessarily needed in order for the VRU system of the instant invention to operate effectively to reduce the number of improper or fraudulent returns and/or warranty repair or replacement.
  • less storage space for model number data and policy information is typically needed than for a time-of-sale registration system (e.g., a serial number registration system).
  • the caller is greeted with a welcome message.
  • the VRU prompts the caller for initial information, such as a manufacturer of a purchased product. This is preferably a speech recognition step and can recognize several manufacturers and product types associated with those manufacturers. If the manufacturer spoken by the caller is a registered client of the VRU system (such as a SiRAS client), the VRU prompts the caller to speak whether a serial number lookup or a model number lookup is to be performed. Alternatively, the VRU system is capable of automatically determining whether a spoken or keyed number provided by the caller is a serial number or a model number (or other type of information) just from the number itself.
  • the caller speaks that a serial number lookup is to be performed (or alternatively, if the VRU automatically determines that the number spoken or keyed by the caller is a serial number), that information is sent to, for example, an Oracle® table to query. After retrieving the serial number information, the system returns all of the applicable return and/or warranty dates that have been defined in the system. The VRU converts all of the information into sentences, which are then played back to the caller. This whole process preferably takes about 3-5 seconds to complete. The VRU will then ask the caller if they want the information repeated or give options to lookup a service center (based on the specific product they looked up), get the 800# for the manufacturer, or try another serial number.
  • the VRU could also ask the caller if he/she wants to enter a new serial number or a model number.
  • non-serialized (e.g., model number) lookup additional details about the serial number lookup features are omitted and can be further understood from review of the above-referenced U.S. patents and PCT application.
  • the VRU can send a query to a Microsoft Access® or an Oracle® data table which stores preloaded model information. If the model number information of the query sent to the data table fails to correspond to (e.g., fails to match) any of the preloaded model numbers in the data table, the VRU plays an error message that the model number doesn't exist or is incorrect and asks for a new model number to be provided by the caller.
  • the VRU retrieves the pre-loaded policy information (e.g., return, warranty, replacement and/or repair information) associated with that particular model number from the data table or other suitable database.
  • the VRU converts the policy information associated with the selected model number into sentences, which is then played back to the caller.
  • the VRU will then ask the caller if he/she wants the policy information repeated, and gives an, option to lookup a service center (based on the specific product he/she looked up), obtain the telephone number of the manufacturer, or try another model number.
  • the VRU can also ask the caller if he/she wants to enter a serial number to thereby initiate a serial number lookup as described above. After completing either the serial number lookup or the model number lookup, if the caller chooses to lookup a service center, the VRU prompts the caller to speak or key in their zip code to obtain the three (or other number of) closest service centers for the identified product. After the service center information is complete, the caller can repeat the information, try another zip code, or start over with another serial number. Additionally, the caller could start over with a model number.
  • the caller when someone calls the VRU, the caller is greeted and prompted for the manufacturer. After the caller speaks the manufacturer, the caller is prompted to speak whether a serial number lookup or a model number lookup is requested.
  • a number can be spoken or keyed (i.e., dialed) by the caller and the VRU will automatically determine whether the number is a serial number or a model number. If the caller requests that a serial number lookup is to be performed, the VRU performs a serial number lookup. If, however, the caller requests that a model number lookup is to be performed, the VRU performs a model number lookup.
  • model number lookup information relating to the model number from the caller is sent as a query to a Microsoft Access® or Oracle® data table (or any other suitable data table) which stores preloaded model information.
  • preloaded model information is stored at any time before the query is sent by the caller to the data table.
  • the model number information from the caller is compared with the preloaded model information stored by the data table to see if the model number exists in the data table. If model number information from the caller does not correspond to (e.g., match with) one of the preloaded model numbers of the data table, an error message will be played indicating that the model number from the caller does not exist or is incorrect.
  • the VRU will then prompt the caller to re-speak the model number. If the model number information originally provided by the caller does correspond to one of the preloaded model numbers, the VRU will select and retrieve policy information which is associated with that particular model number from the data table. The VRU will convert this retrieved information and play to the caller a policy information message that explains the return/warranty repair options that may be available to the caller. Alternatively, the policy information may be stored in a preloaded database different than the Microsoft Access® or Oracle® data table which stores the model number information.
  • the policy information can be defined by the retailer and/or manufacturer for each model number. Different retailers can thus have different policies for the same model number.
  • a non-exhaustive list of examples of the policies includes the following:
  • Policy A Policy A—Purchased product cannot be returned X days (e.g., 90 days) after the last ship date for products having the model number (e.g., the last date products were shipped from the manufacturer to the retailer having that model number).
  • Policy B Policy B—Purchased product cannot be returned X days after the last sell-through date at the retailer of products having that model number.
  • the last sell-through data can be determined, for example, through inventory records for the retailer.
  • Policy E Policy E—Purchased product can be returned only by a specific retailer(s) or authorized service center(s). Returns by other retailers or non-authorized service centers are not permitted.
  • the caller can repeat the playing of the policy message, initiate a service center lookup as described below, or enter a new model.
  • a new serial number can also be entered to thus begin a serial number lookup as described above.
  • a counter When a model number is requested by a caller, a counter may be activated to count the total number of times a specific model is requested. This count can be stored in a database and further increased for each model number as they are respectively requested. This count may, for example, provide an indication that a specific product model is being returned often by customers.
  • the voice recognition system of the instant invention may use a method known as “screen scraping” in order to obtain the desired data for use in the VRU process.
  • screen scraping methods rely on a computer screen (such as an AS/400 screen) to display information.
  • the VRU will send the query (such as a product serial number query) to the AS/400 screen and the VRU will copy the return information it sees on the screen. This information is converted and the appropriate information (such as date information relating to a previously purchased product) are read back to the caller.
  • the VRU system uses a custom dynamic link library (DLL) instead of screen scraping in order to improve the operation of the VRU system.
  • DLL dynamic link library
  • things can change in the background and these changes are seamless to the VRU.
  • the VRU system of the instant invention preferably does not use an AS/400 screen or other computer screen.
  • the product model number query (or other information query) is sent via a customized DLL to a database servlet application using, for example, HTTP protocol.
  • the application accesses a specified host system such as an Oracle database and retrieves the model number registration information.
  • the servlet returns the model number registration information (or other desired information) back to the DLL, which in turn returns it back to the VRU.
  • the VRU converts the information and the appropriate dates relating to the model number (or other non-unique identifier) are read back to the caller.
  • the preferred customized DLL embodiment of the instant invention is described in further detail below.
  • the high-level flow of the VRU system of the instant invention includes a first step 10 of greeting a caller who calls the VRU system.
  • the VRU uses voice prompts to prompt the user to enter information through the telephone or other communication device needed in connection with the particular application in which the VRU system is employed.
  • the VRU prompts the user to enter information regarding the product that the user is calling about, such as the product model number and manufacturer.
  • the VRU includes a predefined object for each of the pieces of information that is requested by the VRU.
  • the VRU then passes the information to a customized Dynamic Link Library (DLL) (Step 12 ).
  • the DLL includes predefined fields corresponding to the objects in the VRU.
  • the DLL also includes additional fields to be loaded with information from the database to be passed back to the caller, as will be described in greater detail below.
  • a database application program uses the information in the DLL to formulate a query to a database, such as an Oracle® database or the like.
  • the database is then queried (Step 14 ) to obtain information therefrom corresponding in some way to the information provided by the caller.
  • the result of the query is then passed back to the DLL and is loaded into predefined fields in the DLL.
  • the VRU then obtains the resulting information from the DLL and loads the information into corresponding objects in the VRU (Step 18 ).
  • the VRU then provides the information back to the waiting caller, thereby providing the caller with the information that was requested (Step 20 ).
  • FIG. 4 shows the interaction between the VRU 22 , DLL 24 and database 26 during an exemplary call from a user of the VRU system.
  • the VRU system is designed to work in conjunction with an ER system, wherein the caller requests return or warranty information on a previously purchased non-serialized product.
  • the VRU includes objects for Manufacturer, Model No. and Zip Code.
  • the DLL 24 includes predefined fields that correspond to these three VRU objects.
  • the object data from the VRU is loaded directly into the predefined fields in the DLL.
  • the Manufacturer and Model No. are used by the database application program to formulate a first query to the database.
  • the result of this first query is the last date for return and/or warranty repair for the product identified by the entered model number.
  • the database includes a product registration database that is established by importing the model numbers and the associated return/warranty criteria or policies with respect to each of the model numbers.
  • the result of the first database query is loaded into a corresponding field of the DLL (e.g., Return Date field).
  • the VRU 22 then obtains the return date information from the DLL and stores it as a predefined return date object.
  • the VRU uses the date object to provide a voice response back to the caller to communicate the date information back to the caller.
  • the VRU system of this example enables the caller to enter product information and get return date information back from the system, thereby informing the user whether or not the product qualifies for return and/or warranty repair.
  • the caller is given the option of obtaining information on service centers for the product by entering zip code information when prompted by the VRU.
  • the Zip information is passed to the DLL and is then used by the database application program to formulate a second query to the database.
  • the second query uses the zip code information to obtain information on the three closest service centers for the product.
  • This service center information is then passed back to the DLL and finally to the VRU in order to provide the service center information to the caller. This information is useful to the caller when, for example, the product no longer qualifies for return under qualification guidelines from the ER database.
  • FIG. 5 shows an overall flow chart of the exemplary VRU system of the instant invention and as described above in connection with FIGS. 1 and 2 .
  • the caller is greeted with the welcome message.
  • the VRU then prompts the caller for initial information, such as the manufacturer of a purchased product.
  • This step is preferably a speech recognition step and can recognize several manufacturers and product types associated with those manufacturers (i.e., NOA, SEGA, PHILIPS). If the manufacturer spoken is a registered client of the product registration system, the VRU prompts the caller to speak or key in the model number of the product.
  • the custom DLL 24 takes that information and sends it via, for example, HTTP to a servlet, which in turn sends it to the Oracle table to query. After retrieving the model number information, the DLL returns with the return and/or warranty dates. The VRU converts all of the DLL information into sentences, which is then played back to the caller. This whole process preferably takes about 3-5 seconds to complete. The VRU will then ask the caller if they want the information repeated or give options to lookup a service center (based on the product they looked up), get the 800# for the manufacturer, or try another model number (or serial number if the system also supports serialized product registrations).
  • the VRU prompts the caller to speak or key in their zip code.
  • the VRU uses another custom DLL, the VRU sends the product information and zip code to the servlet.
  • the servlet works with an application, which assigns latitude and longitude and then provides the three closest locations to the zip code provided.
  • the three closest service centers are sent back to the VRU and the VRU assigns the appropriate voice files to play according to the information given back by the DLL. This process preferably takes about 3-5 seconds to complete.
  • the results are then played back to the caller asking which service center they would like information on. After the service center information is complete, the caller can repeat the information, try another zip code, or start over with another model number.
  • Any known and suitable type of voice recognition system may be used to interact with the caller, and the details of such systems are well-known. Thus, additional details regarding the specific operation of the VRU itself are not provided herein.
  • the customized DLL acts as an interface between the VRU and the registration database.
  • the preferred embodiment includes a model number lookup portion and a service center lookup portion. Further details on the DLL are provided below with respect to each of these portions of this embodiment.
  • the caller when someone calls the VRU, the caller is prompted for the manufacturer of the product. This step is only optional in this embodiment. Depending on the desires of the designer of the system, the manufacturing information could be omitted, as this information may be obtained directly from the serial number.
  • the caller speaks the manufacturer, the caller is prompted for the model number.
  • the caller speaks the model number into the VRU.
  • the VRU loads the model number and the manufacturer into the DLL.
  • the DLL is sent to an application server and the information is given to a servlet.
  • the servlet gathers the registration information and then loads the DLL with all of the registration related dates and information.
  • the DLL returns to the VRU and the VRU converts the dates and information and then reads back the information to the caller. This completes the model number lookup portion of this embodiment.
  • the caller can choose to speak in their zip code to lookup the closest service center for that specific product.
  • the DLL loads the zip code and the model number (given by the first DLL).
  • the DLL is sent to an application server and the information is given to a servlet.
  • the servlet gathers the 3 closest service centers and loads them into the DLL.
  • the DLL returns to the VRU and the VRU reads back the 3 locations that were provided by the DLL. This completes the service center lookup portion.
  • a single customized DLL may be used or a plurality of customized DLLs may be used to implement the invention.
  • a single DLL can be used for both the model number lookup portion and the service center lookup portion.
  • the ER system application of the invention described above is only one example as to how the instant invention can be implemented.
  • the customized DLL can be used in connection with any suitable voice recognition and response system to improve the overall operation thereof.
  • FIGS. 6 and 7 show exemplary processes for testing the operation of the system.
  • FIG. 6 shows a VRU watchdog process that can be used in accordance with the instant invention to check the overall operation of the VRU system.
  • FIG. 7 shows a speech watchdog process that can be used in connection with the VRU watchdog of FIG. 6 to check the speech recognition server of the VRU system is operating properly.
  • the VRU watchdog process is used to check various parts of the system, including the model number lookup DLL, the service center lookup DLL, local access to the database, the speech recognition server, as well as any other VRUs running in parallel to support sufficient traffic through the VRU system.
  • a first check is made to determine if the model number lookup DLL is functional. If not, the system automatically pages or otherwise contacts the appropriate support personnel for the VRU system. If the model number DLL is functional, then the system checks to see if the service center lookup DLL is functional. If not, the system automatically pages the appropriate support person. If the service center DLL is functional, the system checks to see if the local access to the database is operating.
  • the system automatically contacts the support person. If the local access is fine, the system checks the speech recognition server by calling the watchdog application of FIG. 7 , which will be described in detail below in connection with FIG. 7 . If the speech server is not operating properly, the support person is contacted. Finally, any other VRU systems operating in parallel to support the anticipated traffic to the VRU system is checked in the same manner as described above. Any errors that are found are logged by the system with a time and date stamp in a local access database.
  • the VRU watchdog is preferably designed to run every 15 minutes and checks all of the DLL's, local databases, speech recognition server, and the other VRU(s), if any. In the preferred embodiment, there are at least two VRU's that have these watchdogs running. If there is a failure in any section of the testing, the VRU will page the VRU support team with the specific error that was encountered. The system will also create a log entry on the local database with the exact error, the date, and the time the error was encountered. Further details on the particular operation of this VRU watchdog are provided below.
  • the system checks all DLL's by sending a request to the servlet (to simulate a consumer calling on a specific model number) and the watchdog expects specific data to come back. If the data is not accurate or the DLL didn't send anything at all, the system sends out the page and creates the error log entry for the failed DLL. The watchdog then checks the local database by doing a quick query. If the database connection is not there, the system sends out the page to the support group. The next check for the watchdog is the speech recognition server. The watchdog places a call to the Speech Watchdog of FIG. 7 and speaks a sentence that has a high confidence. If the speech server is down, the speech watchdog handles the paging to the support group.
  • the final check for the watchdog is calling any other VRUs running in parallel to the first VRU system.
  • the watchdog places the call and if the other VRU doesn't answer it will page the support team and create an entry in the error log.
  • the watchdog resets itself and waits 15 minutes and launches again.
  • the watchdog process preferably only takes about 10 seconds to complete.
  • the speech watchdog waits for the VRU watchdog to call and then verifies the speech recognition server is up by recognizing prerecorded message that is guaranteed to be a certain confidence within the VRU system. In other words, the speech watchdog waits for the VRU Watchdog to call it. After receiving the call, the speech watchdog prompts for some speech. After the VRU watchdog speaks, the utterance is sent to the speech recognition server. If the speech wasn't recognized, the speech watchdog sends out a page to the support team and logs the error that the speech server is down. The speech watchdog then hangs up and waits for the watchdog to call back.

Abstract

A voice response system for use in obtaining return qualification information for a product using a non-unique product identifier, including: a dial-in voice system operable to prompt a caller for the non-unique product identifier, wherein the non-unique product identifies the product as a member of a defined product group: a product registration database including a plurality of different, non-unique product identifiers: a return policy storage that defines return policies for each of the non-unique product identifiers: and an arrangement that looks up a specific return policy for the non-unique product identified entered by the caller and provides information to the caller regarding return qualification for the product identified by the non-unique product identifier.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of application Ser. No. 12/659,856, filed Mar. 24, 2010, which is a continuation of application Ser. No. 10/398,556, filed Sep. 9, 2003, which is a National Phase of PCT Application No. PCT/US01/31589, filed Oct. 10, 2001, which claims the benefit of U.S. Provisional Application No. 60/238,452, filed Oct. 10, 2000, the entire contents of each of which are hereby incorporated by reference in this application.
  • BACKGROUND AND SUMMARY OF THE INVENTION
  • The present invention relates to voice recognition units or systems (VRUs) for enabling users to remotely obtain information in an efficient and accurate manner from a database using voice commands and/or responses over a telephone system. More particularly, the invention relates to a VRU system that enables users to obtain information regarding return, warranty, replacement and/or repair of previously purchased products from an electronic product registration (ER) system, such as the type disclosed in U.S. Pat. Nos. 5,978,774 and 6,018,719, the disclosures of which are incorporated by reference herein in their entirety.
  • Electronic registration (ER) systems rely on the use of a unique identifier, such as a serial number, for each product that is purchased. The serial number is obtained at the point of sale for inclusion in a registration database, together with other information, such as a date of transaction. This database can then be accessed in connection with an attempted product return/warranty transaction for the purpose of determining if the product qualifies for return/warranty under applicable return/warranty criteria (which is also stored in or made available to the system). Such electronic systems may also be used in connection with repair and/or exchange transactions, in addition to returns, by enabling an accurate determination as to whether the product qualifies for any of these actions under the appropriate policies and criteria under which the product was originally sold.
  • The ER system uses pre-established return/repair policies and procedures that are programmed into the system so that the system can perform a check when a product is presented for return to determine if the product qualifies for return, replacement and/or warranty repair based on sales transaction information available in the ER system for the particular product at issue. Thus, known ER systems include a database of return qualification information (or warranty/replacement criteria) for various manufacturer's which enables the system to make an accurate determination with respect to whether or not a particular product or item (that is uniquely identified by the system using a serial number or other unique identifier) actually qualifies for return (or warranty/replacement) based on the appropriate qualification criteria. Such ER systems have greatly reduced improper and fraudulent returns and warranty claims.
  • ER systems have, in the past, used a unique identifier for each product that is registered, thereby enabling the system to provide return qualification information respect to the particular product being returned. Voice recognition systems for accessing the ER database have also been based on unique identifiers. Thus, in the past, products that do not include a unique identifier associated therewith have not been able to be incorporated into ER systems for access by VRU systems.
  • Voice recognition systems have been successfully used in the past in connection with electronic registration systems for purchased products for the purpose of enabling users to obtain information about return, warranty, replacement and/or repair of the purchased products. Voice recognition (VRU) systems have been used in the connection with such electronic registration (ER) systems to enable remote access to the registration data that is collected by the ER system. Due to the fact that the ER systems have been based on serialized products (i.e., products each having a unique serial number), the VRU systems used therewith have also been based on the use of serial numbers. An example of a VRU system that uses serial numbers is disclosed in PCT application No. PCT/US01/25296 filed Aug. 14, 2001 (Atty Docket No. 723-1159), and entitled “Voice Recognition Method and Apparatus Using Dynamic Link Library”, the disclosure of which is incorporated by reference herein.
  • While such VRU systems have proven to be very useful in their current forms, additional improvements in such systems are still desired in order to provide additional functionality that will benefit customers, retailers and/or manufacturers. To this end, the instant invention provides an improved VRU system that has increased functionality, by providing an enhancement to known VRU systems that enable information on non-serialized products (i.e., products that do not have a unique identifier) to be accessed by users in a manner that is similar to the serialized VRU systems.
  • In accordance with the invention, the improved VRU system enables non-serialized data or identifiers to be used to access return/warranty qualification information that applies to a class or group of similar products. For example, in accordance with the invention, model numbers or other non-serialized data (such as UPC or SKU numbers) that do not uniquely identify a particular product can be entered into the VRU system for the purpose of obtaining return and/or warranty information for the product. The invention enables information to be accessed through a VRU on products that may not have been originally intended for electronic registration, due to, for example, their price, nature or other characteristics. The invention also enables products that have already been sold without collecting registration data at the point of sale to be added into the ER system for access by the VRU system.
  • In accordance with the invention, the VRU system accesses a database that has been previously loaded with information on model numbers (or other non-unique identifiers) and applicable return and/or warranty criteria for products having these model numbers. The database may also contain serialized information so that the VRU system can perform serial number (or other unique identifier) lookup operations and model number (or other non-unique identifier) lookup operations. Thus, the instant invention enables non-serialized products to benefit from electronic registration in substantially the same manner that serialized products have and are currently benefiting from electronic registration. While the non-serialized information does not provide the same level of accuracy as a serialized system, in that specific sales information on a specific product is not available for the non-serialized products, the information is still useful in making logical decisions about whether or not the product qualifies for return or warranty based on information in the system about the entire class or group of products to which the product belongs.
  • In accordance with one aspect of the invention, a voice response system is provided for use in obtaining return qualification information for a product using a non-unique product identifier. The voice response system includes: a dial-in system operable to prompt a caller for the non-unique product identifier, wherein the non-unique product identifier identifies the product as a member of a defined product group; a product registration database including a plurality of different, non-unique product identifiers; a return policy storage that defines return policies for each of the non-unique product identifiers; and an arrangement that looks up a specific return policy for the non-unique product identifier entered by the caller and provides information to the caller regarding return qualification for the product identified by the non-unique product identifier.
  • In accordance with another aspect of the invention, a method is provided for operating a voice response system. The method includes: storing different non-unique product identifiers into a system; storing a return policy in the system for each of the non-unique product identifiers, wherein the return policy defines criteria under which products having the non-unique product identifier associated with the policy can be returned; prompting a caller using a dial-in voice system for a non-unique identifier associated with a product for which a return is desired; Looking up the entered non-unique identifier to determine if it corresponds to one of the stored non-unique identifiers in the system; if the non-unique product identifier does correspond to a stored non-unique identifier, obtaining a stored return policy for that non-unique product identifier; and communicating return qualification information based on the stored return policy back to the caller through the voice system.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The invention will be further understood by review of the following detailed description of the invention when read in conjunction with the appended drawings, in which:
  • FIG. 1 is an exemplary high-level flow chart of the main features of the VRU system of the instant invention;
  • FIG. 2 is an exemplary overall block diagram illustrating the operation of the instant VRU system in accordance with a preferred embodiment of the instant invention;
  • FIG. 3 is an exemplary high-level flow chart illustrating the operation of the instant VRU system;
  • FIG. 4 is a schematic diagram of the interaction between the VRU, DLL and database in accordance with a preferred embodiment of the instant invention.
  • FIG. 5 is a more detailed flow-chart illustrating a preferred embodiment of the operation of the instant VRU system;
  • FIG. 6 is an exemplary block diagram illustrating the VRU watchdog feature of the instant invention; and
  • FIG. 7 is an exemplary block diagram of the speech watchdog feature of the instant invention.
  • DETAILED DESCRIPTION OF THE DRAWINGS
  • The preferred embodiment of the instant invention will now be described with reference to the drawings. It is noted that this description of the invention is only exemplary and is not meant to limit the invention beyond the express scope of the appended claims.
  • FIG. 1 shows a high-level flow chart of the main steps that are performed in accordance with the VRU model number lookup system of the instant invention. In accordance with the invention, non-unique product identifiers, such as product model numbers or the like, are preloaded into a database system, such as an electronic product registration system. The loaded model numbers define model numbers for which the system will be able to provide return qualification information to a requesting party. Thus, if a manufacturer, retailer or other party desires to utilize the system for the purpose of reducing the number of unauthorized returns, that party provides the models numbers of interest (or other non-unique product identifiers) so that they can be loaded into the system. The party then also defines a return/warranty policy for each different model number that has been loaded into the system. The policies are preferably based on some information that relates to the sale or shipment of products having the particular model numbers. For example, a policy may state that product having a particular model number cannot be returned X days after the last shipment of such products from the manufacturer to the retailer. Another example of a policy is one that states that products having a certain model number cannot be returned X days after the last sell-through date at the retailer or products having that model number. These are useful policies in reducing unauthorized returns, because they define a time period for return that logically relates to a legitimate return period. For example, if a retailer knows that the last product having a certain model number was sold on a certain date, then the retailer can define a policy that states that no returns are allowed after X days (e.g., 90 days) from that date for products having that model number. Of course, this system may allow some improper returns, due to the fact that there is no way to know exactly when a particular product having the model number was purchased (or shipped). However, the system at least can provide a logical cut-off date for returns based on the last sale (or shipment) date for all products having that model number, thereby still operating to reduce the number of unauthorized returns. In other words, in this example, the system basically assumes that all products having that model number were purchased on the date the last one was purchased (even though this is likely not the case). This enables decisions to be made as to return qualification based on these last dates. Any policy can be used in accordance with the system with a group of products having the same non-unique product identifier depending on the particular desires of each retailer and/or manufacturer.
  • It is noted that the invention has been described in the context of a VRU system. However, the invention has broader applications and can be used in a computerized look-up system as well as a VRU system. In the computerized system, the user would access the system through a web site or other computer communication and then be prompted for the model number or other non-unique identifier. The computerized system would then look up the associated return/warranty policy for the product and provide return qualification information back to the user through the computer system (rather than through the VRU system).
  • As explained above, rather than sending a product serial number query to a database, a non-unique identifier, such as a product model number, is accepted by the VRU and is sent to the database. As will be understood by those skilled in the art, a product serial number is unique for each product, whereas more than one product (typically the same type of product) may have a non-unique identifier such as a product model number. While the description of the present invention will hereinafter refer to “model number”, those skilled in the art will understand that any non-unique identifier could be sent as at least part of a query to the database in accordance with the instant invention.
  • In one embodiment of the instant invention, the caller will speak whether a serial number lookup or a model number lookup (or some other type of lookup) should be performed. The VRU will then access the appropriate database based upon that spoken indication from the caller. Alternatively, the VRU system is capable of automatically determining whether a spoken or keyed query provided by the caller is a product serial number query or a product model number query (or other type of informational query) just from the number itself and automatically accesses the appropriate database based upon that determination.
  • If a serial number lookup query is requested by the caller, serial number registration information is retrieved from the system, as described, for example, in the above-referenced PCT application. The VRU then converts the information so that it is sent back to the caller. On the other hand, if a product model number query is requested by the caller, then policy information relating to products having that model number can be retrieved from the system. The VRU can then convert this policy information so that it can be read back to the caller through the VRU system. The VRU system of one embodiment of the instant invention enables users to obtain information regarding return, warranty, replacement and/or repair of previously purchased products using product model number information and without any type of information (e.g., serial number, purchase date/time and/or individual transaction information) being obtained at the time the product is purchased.
  • By using a model number look-up rather than a serial number lookup, a retailer can effectively control the return, warranty, replacement and/or repair of purchased products even if the retailer did not collect any information at the time the products were purchased, or even have the ability of (or even contemplated) providing such control at the time the products were purchased, since no information at the point of sale is needed. Moreover, no information regarding the individual purchase transactions, particular purchase dates/times and/or serial numbers is needed to provide model number lookup in accordance with the instant invention. Instead, policy or criteria information is needed that relates to the entire class or group of products that are covered by the model number or other non-unique identifier. For example, a policy may be defined for a particular product model number such that any purchased product having that model number cannot be returned X number of days after the last ship date from the manufacturer to the retailer of products having that model number. This exemplary return policy can be instituted by the retailer and/or manufacturer without collecting any information at the time of sale and can thus be instituted after some or all of the sales of the products having that particular model number are completed. As long as the return policy for that particular model number has been defined before the caller provides the model number query to the database, the only additional information needed is the model number itself from the caller. Serial number, purchase date/time and/or other transactional data at the time of sale (or any time thereafter) is not required.
  • A VRU system using a model number lookup can operate at a lower cost since a registration system for obtaining information at the time of sale or any time thereafter is not needed. In addition, the products do not have to be assigned unique identifiers. Thus, a system which registers serial number, purchase date/time and/or other transactional information is not necessarily needed in order for the VRU system of the instant invention to operate effectively to reduce the number of improper or fraudulent returns and/or warranty repair or replacement. Moreover, less storage space for model number data and policy information is typically needed than for a time-of-sale registration system (e.g., a serial number registration system).
  • Referring now to FIG. 2, when a call accesses the VRU system of the present invention, the caller is greeted with a welcome message. The VRU prompts the caller for initial information, such as a manufacturer of a purchased product. This is preferably a speech recognition step and can recognize several manufacturers and product types associated with those manufacturers. If the manufacturer spoken by the caller is a registered client of the VRU system (such as a SiRAS client), the VRU prompts the caller to speak whether a serial number lookup or a model number lookup is to be performed. Alternatively, the VRU system is capable of automatically determining whether a spoken or keyed number provided by the caller is a serial number or a model number (or other type of information) just from the number itself.
  • If the caller speaks that a serial number lookup is to be performed (or alternatively, if the VRU automatically determines that the number spoken or keyed by the caller is a serial number), that information is sent to, for example, an Oracle® table to query. After retrieving the serial number information, the system returns all of the applicable return and/or warranty dates that have been defined in the system. The VRU converts all of the information into sentences, which are then played back to the caller. This whole process preferably takes about 3-5 seconds to complete. The VRU will then ask the caller if they want the information repeated or give options to lookup a service center (based on the specific product they looked up), get the 800# for the manufacturer, or try another serial number. Additionally, the VRU could also ask the caller if he/she wants to enter a new serial number or a model number. Inasmuch as the instant invention is primarily directed to non-serialized (e.g., model number) lookup, additional details about the serial number lookup features are omitted and can be further understood from review of the above-referenced U.S. patents and PCT application.
  • If the caller speaks that a model number lookup is to be performed (or alternatively, if the VRU automatically determines that the number spoken or keyed by the caller is a model number), the VRU can send a query to a Microsoft Access® or an Oracle® data table which stores preloaded model information. If the model number information of the query sent to the data table fails to correspond to (e.g., fails to match) any of the preloaded model numbers in the data table, the VRU plays an error message that the model number doesn't exist or is incorrect and asks for a new model number to be provided by the caller. If the model number information of the query sent to the data table does correspond to a preloaded model number in the data table, the VRU retrieves the pre-loaded policy information (e.g., return, warranty, replacement and/or repair information) associated with that particular model number from the data table or other suitable database. The VRU converts the policy information associated with the selected model number into sentences, which is then played back to the caller. The VRU will then ask the caller if he/she wants the policy information repeated, and gives an, option to lookup a service center (based on the specific product he/she looked up), obtain the telephone number of the manufacturer, or try another model number. Additionally, the VRU can also ask the caller if he/she wants to enter a serial number to thereby initiate a serial number lookup as described above. After completing either the serial number lookup or the model number lookup, if the caller chooses to lookup a service center, the VRU prompts the caller to speak or key in their zip code to obtain the three (or other number of) closest service centers for the identified product. After the service center information is complete, the caller can repeat the information, try another zip code, or start over with another serial number. Additionally, the caller could start over with a model number.
  • As explained above, when someone calls the VRU, the caller is greeted and prompted for the manufacturer. After the caller speaks the manufacturer, the caller is prompted to speak whether a serial number lookup or a model number lookup is requested. In accordance with an alternative embodiment of the instant invention, a number can be spoken or keyed (i.e., dialed) by the caller and the VRU will automatically determine whether the number is a serial number or a model number. If the caller requests that a serial number lookup is to be performed, the VRU performs a serial number lookup. If, however, the caller requests that a model number lookup is to be performed, the VRU performs a model number lookup.
  • To perform a model number lookup, information relating to the model number from the caller is sent as a query to a Microsoft Access® or Oracle® data table (or any other suitable data table) which stores preloaded model information. As will understood by those skilled in the art, “preloaded” model information is stored at any time before the query is sent by the caller to the data table. The model number information from the caller is compared with the preloaded model information stored by the data table to see if the model number exists in the data table. If model number information from the caller does not correspond to (e.g., match with) one of the preloaded model numbers of the data table, an error message will be played indicating that the model number from the caller does not exist or is incorrect. The VRU will then prompt the caller to re-speak the model number. If the model number information originally provided by the caller does correspond to one of the preloaded model numbers, the VRU will select and retrieve policy information which is associated with that particular model number from the data table. The VRU will convert this retrieved information and play to the caller a policy information message that explains the return/warranty repair options that may be available to the caller. Alternatively, the policy information may be stored in a preloaded database different than the Microsoft Access® or Oracle® data table which stores the model number information.
  • The policy information can be defined by the retailer and/or manufacturer for each model number. Different retailers can thus have different policies for the same model number. A non-exhaustive list of examples of the policies includes the following:
  • Policy A—Purchased product cannot be returned X days (e.g., 90 days) after the last ship date for products having the model number (e.g., the last date products were shipped from the manufacturer to the retailer having that model number).
  • Policy B—Purchased product cannot be returned X days after the last sell-through date at the retailer of products having that model number. The last sell-through data can be determined, for example, through inventory records for the retailer.
  • Policy C—Purchased product cannot be returned. Only warranty repair is available.
  • Policy D—Purchased product cannot be returned. No warranty repair.
  • Policy E—Purchased product can be returned only by a specific retailer(s) or authorized service center(s). Returns by other retailers or non-authorized service centers are not permitted.
  • After a policy message is complete, the caller can repeat the playing of the policy message, initiate a service center lookup as described below, or enter a new model. In accordance with a further embodiment of the instant invention, a new serial number can also be entered to thus begin a serial number lookup as described above.
  • When a model number is requested by a caller, a counter may be activated to count the total number of times a specific model is requested. This count can be stored in a database and further increased for each model number as they are respectively requested. This count may, for example, provide an indication that a specific product model is being returned often by customers.
  • The voice recognition system of the instant invention may use a method known as “screen scraping” in order to obtain the desired data for use in the VRU process. Such screen scraping methods rely on a computer screen (such as an AS/400 screen) to display information. The VRU will send the query (such as a product serial number query) to the AS/400 screen and the VRU will copy the return information it sees on the screen. This information is converted and the appropriate information (such as date information relating to a previously purchased product) are read back to the caller. Screen scraping is not always a reliable way to retrieve data because if any screen on the AS/400 is modified and/or fields are moved around, the VRU system needs to be retrained to know what the screens look like and what parts need to be scraped (i.e., what fields contain the desired data). Thus, the preferred embodiment of the instant VRU system uses a custom dynamic link library (DLL) instead of screen scraping in order to improve the operation of the VRU system. By using a custom DLL, things can change in the background and these changes are seamless to the VRU. In other words, the VRU system of the instant invention preferably does not use an AS/400 screen or other computer screen. Instead, the product model number query (or other information query) is sent via a customized DLL to a database servlet application using, for example, HTTP protocol. In the preferred embodiment, the application accesses a specified host system such as an Oracle database and retrieves the model number registration information. The servlet returns the model number registration information (or other desired information) back to the DLL, which in turn returns it back to the VRU. The VRU converts the information and the appropriate dates relating to the model number (or other non-unique identifier) are read back to the caller. The preferred customized DLL embodiment of the instant invention is described in further detail below.
  • Referring now to FIG. 3, the high-level flow of the VRU system of the instant invention includes a first step 10 of greeting a caller who calls the VRU system. In this step, the VRU uses voice prompts to prompt the user to enter information through the telephone or other communication device needed in connection with the particular application in which the VRU system is employed. For example, when used in an Electronic Product Registration (ER) system, such as described in the above-referenced patents, the VRU prompts the user to enter information regarding the product that the user is calling about, such as the product model number and manufacturer. The VRU includes a predefined object for each of the pieces of information that is requested by the VRU. The VRU then passes the information to a customized Dynamic Link Library (DLL) (Step 12). The DLL includes predefined fields corresponding to the objects in the VRU. The DLL also includes additional fields to be loaded with information from the database to be passed back to the caller, as will be described in greater detail below.
  • Once the DLL has data passed to it by the VRU, a database application program uses the information in the DLL to formulate a query to a database, such as an Oracle® database or the like. The database is then queried (Step 14) to obtain information therefrom corresponding in some way to the information provided by the caller. The result of the query is then passed back to the DLL and is loaded into predefined fields in the DLL. The VRU then obtains the resulting information from the DLL and loads the information into corresponding objects in the VRU (Step 18). The VRU then provides the information back to the waiting caller, thereby providing the caller with the information that was requested (Step 20).
  • FIG. 4 shows the interaction between the VRU 22, DLL 24 and database 26 during an exemplary call from a user of the VRU system. In this example, the VRU system is designed to work in conjunction with an ER system, wherein the caller requests return or warranty information on a previously purchased non-serialized product. As seen in FIG. 4, in this embodiment the VRU includes objects for Manufacturer, Model No. and Zip Code. Thus, this is the information that is requested from the caller by the VRU. The DLL 24 includes predefined fields that correspond to these three VRU objects. Thus, the object data from the VRU is loaded directly into the predefined fields in the DLL. In this example, the Manufacturer and Model No. are used by the database application program to formulate a first query to the database. In this example, the result of this first query is the last date for return and/or warranty repair for the product identified by the entered model number. The database includes a product registration database that is established by importing the model numbers and the associated return/warranty criteria or policies with respect to each of the model numbers.
  • The result of the first database query is loaded into a corresponding field of the DLL (e.g., Return Date field). The VRU 22 then obtains the return date information from the DLL and stores it as a predefined return date object. The VRU then uses the date object to provide a voice response back to the caller to communicate the date information back to the caller. In this manner, the VRU system of this example enables the caller to enter product information and get return date information back from the system, thereby informing the user whether or not the product qualifies for return and/or warranty repair.
  • In the example of FIG. 4, the caller is given the option of obtaining information on service centers for the product by entering zip code information when prompted by the VRU. As with the Manufacturer and Model No. information, the Zip information is passed to the DLL and is then used by the database application program to formulate a second query to the database. The second query uses the zip code information to obtain information on the three closest service centers for the product. This service center information is then passed back to the DLL and finally to the VRU in order to provide the service center information to the caller. This information is useful to the caller when, for example, the product no longer qualifies for return under qualification guidelines from the ER database.
  • FIG. 5 shows an overall flow chart of the exemplary VRU system of the instant invention and as described above in connection with FIGS. 1 and 2. As shown in FIG. 5, when a call comes in to the VRU, the caller is greeted with the welcome message. The VRU then prompts the caller for initial information, such as the manufacturer of a purchased product. This step is preferably a speech recognition step and can recognize several manufacturers and product types associated with those manufacturers (i.e., NOA, SEGA, PHILIPS). If the manufacturer spoken is a registered client of the product registration system, the VRU prompts the caller to speak or key in the model number of the product. After the caller provides the model number, the custom DLL 24 takes that information and sends it via, for example, HTTP to a servlet, which in turn sends it to the Oracle table to query. After retrieving the model number information, the DLL returns with the return and/or warranty dates. The VRU converts all of the DLL information into sentences, which is then played back to the caller. This whole process preferably takes about 3-5 seconds to complete. The VRU will then ask the caller if they want the information repeated or give options to lookup a service center (based on the product they looked up), get the 800# for the manufacturer, or try another model number (or serial number if the system also supports serialized product registrations). If the caller chooses to lookup a service center, the VRU prompts the caller to speak or key in their zip code. Using another custom DLL, the VRU sends the product information and zip code to the servlet. The servlet works with an application, which assigns latitude and longitude and then provides the three closest locations to the zip code provided. The three closest service centers are sent back to the VRU and the VRU assigns the appropriate voice files to play according to the information given back by the DLL. This process preferably takes about 3-5 seconds to complete. The results are then played back to the caller asking which service center they would like information on. After the service center information is complete, the caller can repeat the information, try another zip code, or start over with another model number.
  • Any known and suitable type of voice recognition system may be used to interact with the caller, and the details of such systems are well-known. Thus, additional details regarding the specific operation of the VRU itself are not provided herein.
  • As can be seen from the example above, the customized DLL acts as an interface between the VRU and the registration database. As can be seen in FIG. 5, the preferred embodiment includes a model number lookup portion and a service center lookup portion. Further details on the DLL are provided below with respect to each of these portions of this embodiment.
  • In accordance with the model number lookup portion, when someone calls the VRU, the caller is prompted for the manufacturer of the product. This step is only optional in this embodiment. Depending on the desires of the designer of the system, the manufacturing information could be omitted, as this information may be obtained directly from the serial number. After the caller speaks the manufacturer, the caller is prompted for the model number. The caller speaks the model number into the VRU. The VRU then loads the model number and the manufacturer into the DLL. The DLL is sent to an application server and the information is given to a servlet. The servlet gathers the registration information and then loads the DLL with all of the registration related dates and information. The DLL returns to the VRU and the VRU converts the dates and information and then reads back the information to the caller. This completes the model number lookup portion of this embodiment.
  • In accordance with the service center lookup, after a model number lookup is finished, the caller can choose to speak in their zip code to lookup the closest service center for that specific product. After a zip code is spoken, the DLL loads the zip code and the model number (given by the first DLL). The DLL is sent to an application server and the information is given to a servlet. The servlet gathers the 3 closest service centers and loads them into the DLL. The DLL returns to the VRU and the VRU reads back the 3 locations that were provided by the DLL. This completes the service center lookup portion.
  • It is noted that a single customized DLL may be used or a plurality of customized DLLs may be used to implement the invention. In the less complex applications, such as described above, a single DLL can be used for both the model number lookup portion and the service center lookup portion. It is further noted that the ER system application of the invention described above is only one example as to how the instant invention can be implemented. In accordance with the invention, the customized DLL can be used in connection with any suitable voice recognition and response system to improve the overall operation thereof.
  • In many VRU systems, it is important to assure that the system is operating properly by performing periodic tests of certain aspects of the VRU system. FIGS. 6 and 7 show exemplary processes for testing the operation of the system. FIG. 6 shows a VRU watchdog process that can be used in accordance with the instant invention to check the overall operation of the VRU system. FIG. 7 shows a speech watchdog process that can be used in connection with the VRU watchdog of FIG. 6 to check the speech recognition server of the VRU system is operating properly. Each of these watchdog processes of FIGS. 6 and 7 will be explained in greater detail below.
  • Referring now to FIG. 6, the VRU watchdog process is used to check various parts of the system, including the model number lookup DLL, the service center lookup DLL, local access to the database, the speech recognition server, as well as any other VRUs running in parallel to support sufficient traffic through the VRU system. As can be seen in FIG. 6, a first check is made to determine if the model number lookup DLL is functional. If not, the system automatically pages or otherwise contacts the appropriate support personnel for the VRU system. If the model number DLL is functional, then the system checks to see if the service center lookup DLL is functional. If not, the system automatically pages the appropriate support person. If the service center DLL is functional, the system checks to see if the local access to the database is operating. If not, the system automatically contacts the support person. If the local access is fine, the system checks the speech recognition server by calling the watchdog application of FIG. 7, which will be described in detail below in connection with FIG. 7. If the speech server is not operating properly, the support person is contacted. Finally, any other VRU systems operating in parallel to support the anticipated traffic to the VRU system is checked in the same manner as described above. Any errors that are found are logged by the system with a time and date stamp in a local access database.
  • The VRU watchdog is preferably designed to run every 15 minutes and checks all of the DLL's, local databases, speech recognition server, and the other VRU(s), if any. In the preferred embodiment, there are at least two VRU's that have these watchdogs running. If there is a failure in any section of the testing, the VRU will page the VRU support team with the specific error that was encountered. The system will also create a log entry on the local database with the exact error, the date, and the time the error was encountered. Further details on the particular operation of this VRU watchdog are provided below.
  • As indicated above, the system checks all DLL's by sending a request to the servlet (to simulate a consumer calling on a specific model number) and the watchdog expects specific data to come back. If the data is not accurate or the DLL didn't send anything at all, the system sends out the page and creates the error log entry for the failed DLL. The watchdog then checks the local database by doing a quick query. If the database connection is not there, the system sends out the page to the support group. The next check for the watchdog is the speech recognition server. The watchdog places a call to the Speech Watchdog of FIG. 7 and speaks a sentence that has a high confidence. If the speech server is down, the speech watchdog handles the paging to the support group. The final check for the watchdog is calling any other VRUs running in parallel to the first VRU system. The watchdog places the call and if the other VRU doesn't answer it will page the support team and create an entry in the error log. After the checks are completed, the watchdog resets itself and waits 15 minutes and launches again. The watchdog process preferably only takes about 10 seconds to complete.
  • The specific operation of the speech watchdog will now be described in connection with FIG. 7. The speech watchdog waits for the VRU watchdog to call and then verifies the speech recognition server is up by recognizing prerecorded message that is guaranteed to be a certain confidence within the VRU system. In other words, the speech watchdog waits for the VRU Watchdog to call it. After receiving the call, the speech watchdog prompts for some speech. After the VRU watchdog speaks, the utterance is sent to the speech recognition server. If the speech wasn't recognized, the speech watchdog sends out a page to the support team and logs the error that the speech server is down. The speech watchdog then hangs up and waits for the watchdog to call back.
  • While the preferred forms and embodiment of the instant invention have been illustrated and described, it will be apparent to those of ordinary skill in the art that various modification and/or changes may be made to the exemplary embodiment described above. Thus, the exemplary embodiment described above is not meant to limit the scope of the invention beyond the express scope of the appended claims.

Claims (20)

1. A method of obtaining return and/or warranty qualification information for a consumer-type product on behalf of a consumer, the method comprising:
prompting the consumer for at least one identifier of the product in connection in connection with a return and/or warranty eligibility inquiry;
receiving the at least one identifier of the product from the consumer;
causing a computer to search an electronic registration database for a relevant policy based on the at least one identifier of the product received from the consumer; and
communicating the relevant policy, if found, to the consumer,
wherein when the at least one identifier of the product uniquely identifies the product, the computer is caused to search the electronic registration database for an exact match to the at least one identifier received from the consumer, and the relevant policy that is communicated to the consumer is the policy associated with that exact match, and
wherein when the at least one identifier of the product does not uniquely identify the product:
the at least one identifier received from the consumer is considered a non-unique identifier of the product,
the computer is caused to search the electronic registration database for a related product having the same non-unique identifier as that received from the consumer, and
the relevant policy that is communicated to the consumer is the policy associated with that related product.
2. The method of claim 1, wherein the prompting, receiving, and communicating are practiced in connection with a telephone system.
3. The method of claim 1, wherein the at least one identifier of the product is received via keyed-in data from the consumer.
4. The method of claim 1, wherein the at least one identifier of the product is received from the consumer by recognizing spoken words.
5. The method of claim 1, wherein the communicating includes performing text- to-speech conversion on the relevant policy.
6. The method of claim 1, further comprising enabling the consumer to initiate a service center lookup operation following communication of a found relevant policy.
7. The method of claim 1, further comprising providing the consumer with manufacturer contact information in response to a corresponding request received from the consumer following communication of a found relevant policy.
8. The method of claim 1, further comprising, following communication of a found relevant policy, repeating the communicating and/or enabling the consumer to initiate a further return and/or warranty eligibility inquiry.
9. The method of claim 1, wherein the non-unique identifier is a model number of the product.
10. The method of claim 1, wherein the related product is the product in the electronic registration database that was shipped last.
11. The method of claim 1, wherein the related product is the product in the electronic registration database that has the most recent sell-through date.
12. A system for use in obtaining return and/or warranty qualification information for a consumer-type product on behalf of a consumer, comprising:
a telephone response system configured to prompt the consumer for, and receive from the consumer, at least one identifier of the product in connection in connection with a return and/or warranty eligibility inquiry; and
a computer system configured to search an electronic registration (ER) database for a relevant policy based on the at least one identifier of the product received from the consumer, the ER database storing information regarding a plurality of products and associated return and/or warranty information;
wherein the telephone response system is further configured to communicate the relevant policy, if found, to the consumer,
wherein when the at least one identifier of the product uniquely identifies the product, the computer system is caused to search the electronic registration database for an exact match to the at least one identifier received from the consumer, and the relevant policy that is to be communicated to the consumer is the policy associated with that exact match, and
wherein when the at least one identifier of the product does not uniquely identify the product:
the at least one identifier received from the consumer is considered a non- unique identifier of the product,
the computer system is caused to search the electronic registration database for a related product having the same non-unique identifier as that received from the consumer, and
the relevant policy that is to be communicated to the consumer is the policy associated with that related product.
13. The system of claim 12, wherein the at least one identifier of the product is received via keyed-in data from the consumer.
14. The system of claim 12, further comprising a voice recognition unit configured to recognize words spoken by the consumer.
15. The system of claim 12, wherein the telephone response system is further configured to receive one or more supplemental requests from the consumer including:
a first request to initiate a service center lookup operation,
a second request for manufacturer contact information,
a third request to repeat the found relevant policy, and
a fourth request to initiate a further return and/or warranty eligibility inquiry.
16. The system of claim 12, wherein the non-unique identifier is a model number of the product.
17. The system of claim 12, wherein the related product is the product in the electronic registration database that was shipped last.
18. The system of claim 12, wherein the related product is the product in the electronic registration database that has the most recent sell-through date.
19. The system of claim 12, wherein the telephone response system is further configured to indicate to the consumer that a relevant policy has not been found when the at least one identifier does not match any data in the ER database.
20. The system of claim 12, wherein serial numbers help to uniquely identify products in the ER database.
US13/361,405 2000-10-10 2012-01-30 Voice recognition method and apparatus using model number lookup Abandoned US20120130908A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/361,405 US20120130908A1 (en) 2000-10-10 2012-01-30 Voice recognition method and apparatus using model number lookup

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US23845200P 2000-10-10 2000-10-10
US10/398,556 US7729923B2 (en) 2000-10-10 2001-10-10 Voice recognition and apparatus using model number lookup
PCT/US2001/031589 WO2002031809A1 (en) 2000-10-10 2001-10-10 Voice recognition method and apparatus using model number lookup
US12/659,856 US8126724B2 (en) 2000-10-10 2010-03-24 Voice recognition method and apparatus using model number lookup
US13/361,405 US20120130908A1 (en) 2000-10-10 2012-01-30 Voice recognition method and apparatus using model number lookup

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/659,856 Continuation US8126724B2 (en) 2000-10-10 2010-03-24 Voice recognition method and apparatus using model number lookup

Publications (1)

Publication Number Publication Date
US20120130908A1 true US20120130908A1 (en) 2012-05-24

Family

ID=22897946

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/398,556 Expired - Lifetime US7729923B2 (en) 2000-10-10 2001-10-10 Voice recognition and apparatus using model number lookup
US12/659,856 Expired - Lifetime US8126724B2 (en) 2000-10-10 2010-03-24 Voice recognition method and apparatus using model number lookup
US13/361,405 Abandoned US20120130908A1 (en) 2000-10-10 2012-01-30 Voice recognition method and apparatus using model number lookup

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/398,556 Expired - Lifetime US7729923B2 (en) 2000-10-10 2001-10-10 Voice recognition and apparatus using model number lookup
US12/659,856 Expired - Lifetime US8126724B2 (en) 2000-10-10 2010-03-24 Voice recognition method and apparatus using model number lookup

Country Status (3)

Country Link
US (3) US7729923B2 (en)
AU (1) AU2002211572A1 (en)
WO (1) WO2002031809A1 (en)

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8788432B2 (en) 1996-10-02 2014-07-22 Nintendo Of America Inc. Method and apparatus for efficient handling of product return transactions
US7797164B2 (en) * 1996-10-02 2010-09-14 Nintendo Of America, Inc. Method and apparatus for enabling purchasers of products to obtain return information and to initiate product returns via an on-line network connection
US6757663B1 (en) 1996-10-02 2004-06-29 Nintendo Of America Electronic registration system for product transactions
US8156026B2 (en) 2000-05-12 2012-04-10 Nintendo of America Ltd. Method and apparatus for enabling purchasers of products to obtain return information and to initiate product returns via an on-line network connection
US6085172A (en) * 1996-10-02 2000-07-04 Nintendo Of America Inc. Method and apparatus for efficient handling of product return transactions
CA2350551A1 (en) * 1998-11-13 2000-05-25 Nintendo Of America Inc. Method and apparatus for verifying product sale transactions and processing product returns
US8510171B2 (en) * 2000-07-25 2013-08-13 Nintendo Of America Inc. Electronic product registration system with customizable return/warranty programs
AU2002211572A1 (en) * 2000-10-10 2002-04-22 Nintendo Of America Inc. Voice recognition method and apparatus using model number lookup
US8209226B2 (en) * 2001-11-15 2012-06-26 Nintendo Of America Inc. Non-serialized electronic product registration system and method of operating same
US7353178B2 (en) * 2002-04-30 2008-04-01 Microsoft Corporation Touch point and attribute tracking system and process
US7840439B2 (en) * 2003-11-10 2010-11-23 Nintendo Of America, Inc. RF-ID product tracking system with privacy enhancement
US7873149B2 (en) 2004-06-01 2011-01-18 Verizon Business Global Llc Systems and methods for gathering information
US8392193B2 (en) * 2004-06-01 2013-03-05 Verizon Business Global Llc Systems and methods for performing speech recognition using constraint based processing
US7455230B2 (en) * 2005-04-22 2008-11-25 Nintendo Of America Inc. UPC, EAN and JAN validation system and method for loss prevention at point of sale/return
WO2007022411A1 (en) * 2005-08-18 2007-02-22 Cappella Inc. Delivery system and method of use for positioning of a device in a bifurcation
US20080052184A1 (en) * 2006-08-22 2008-02-28 Nintendo Of America Inc. Systems and methods for product authentication and warranty verification for online auction houses
US20090150170A1 (en) * 2007-12-11 2009-06-11 Nintendo Of America Method and apparatus for fraud reduction and product recovery
US20100325020A1 (en) * 2008-12-04 2010-12-23 Nintendo Of America, Inc. Systems and/or methods for globally tracking items and generating active notifications regarding the same
US8302024B2 (en) * 2009-04-02 2012-10-30 Nintendo Of America Inc. Systems and/or methods for paging control including selective paging element display according to a binary subdivision and/or a serial progressive display approach
US20110016008A1 (en) * 2009-07-14 2011-01-20 Nintendo of America Inc., Electronic registration systems for processing variable or multiple return/warranty policies, and associated methods
US10296916B2 (en) 2009-09-11 2019-05-21 Maridee Joy Maraz System and/or method for handling recalled product purchases and/or return/warranty requests
US8239269B2 (en) * 2009-09-11 2012-08-07 Nintendo Of America Inc. System and/or method for handling returns involving products tied to post-paid subscriptions/services
US8712856B2 (en) 2010-04-12 2014-04-29 Nintendo Of America Inc. Systems and/or methods for determining item serial number structure and intelligence
US8595062B2 (en) 2010-11-15 2013-11-26 Nintendo Of America Inc. Systems and/or methods for fraud detection in award point programs
US20130238471A1 (en) * 2012-03-06 2013-09-12 Nintendo Of America Inc. Systems and/or methods involving linked manufacturer serial numbers and unique identifiers applied to products
US8799111B2 (en) 2012-05-04 2014-08-05 Nintendo Of America Inc. Systems and/or methods for selling non-inventory items at point-of-sale (POS) locations
US9697522B2 (en) * 2013-11-01 2017-07-04 Plantronics, Inc. Interactive device registration, setup and use
US20160019518A1 (en) * 2014-07-17 2016-01-21 Toshiba Tec Kabushiki Kaisha Handheld computing device and electronic receipt server

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010054064A1 (en) * 1997-07-02 2001-12-20 Pallipuram V. Kannan Method system and computer program product for providing customer service over the world-wide web
US20060235768A1 (en) * 2005-03-24 2006-10-19 Sabre Inc.And Travelocity.Com Lp. System, method, and computer program product for reducing the burden on inventory system by displaying product availability information for a range of parameters related to a product
US7379899B1 (en) * 1998-11-13 2008-05-27 Nintendo Of America Inc. Method and apparatus for verifying product sale transactions and processing product returns

Family Cites Families (183)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US789106A (en) 1904-10-29 1905-05-02 Howard Preston Tweed Combined cash-slip and refunding-voucher.
US1330368A (en) 1917-09-19 1920-02-10 August N E Boos Date and time service protective-perforation recording check and receipt
US1393489A (en) 1918-04-25 1921-10-11 August N E Boos Service check and receipt
US1476819A (en) 1921-04-14 1923-12-11 Thomas B Hope Stock-record and sales-accounting system
GB2041596B (en) 1978-12-18 1982-11-17 Casio Computer Co Ltd Electronic cash register
US4414467A (en) 1979-11-13 1983-11-08 Video Corporation Of America Vending ordering terminal
NZ199808A (en) 1981-03-03 1986-06-11 Maciver K J A & Sons Machine for renting video tape cassettes:individual compartment for each cassette
DE3315724A1 (en) 1983-04-29 1984-10-31 Günter Ing.(grad.) 8540 Schwabach Blech Device for lending out stackable image and/or sound carriers
CA1218439A (en) 1983-07-18 1987-02-24 Robert J. Spooner Self-contained cassette vending machine
US4563739A (en) 1983-07-18 1986-01-07 Impulse Computer Systems, Inc. Inventory and business management system which accounts for the contents of full and partially filled product containers
FR2559599B1 (en) 1984-02-13 1988-07-08 Gauer Bernard AUTOMATIC RECOVERY DISTRIBUTOR OF VIDEO CASSETTES, AUDIO CASSETTES, COMPUTER CASSETTES, COMPUTER SOFT DISCS
US4598810A (en) 1984-04-17 1986-07-08 Abm Industries, Inc. Apparatus and method for vending and accepting return of re-usable articles
US4792018A (en) 1984-07-09 1988-12-20 Checkrobot Inc. System for security processing of retailed articles
US4789054A (en) 1985-01-02 1988-12-06 Abm Industries, Inc. Vending machine for returnable cartridges
CA1260117A (en) 1985-02-14 1989-09-26 Nelson Vending Technology Limited Automatic vending machine
US4812629A (en) 1985-03-06 1989-03-14 Term-Tronics, Incorporated Method and apparatus for vending
US5133441A (en) 1985-06-17 1992-07-28 Keyosk Corporation Video cassette vending machine
US4734005A (en) 1985-07-19 1988-03-29 Marvin Blumberg Vending machine for video cassettes
US4668150A (en) 1985-07-19 1987-05-26 Blumberg Marvin R Vending machine for video cassettes
US4866661A (en) 1986-03-26 1989-09-12 Prins Maurits L De Computer controlled rental and sale system and method for a supermarket and the like
US5367148A (en) 1986-04-18 1994-11-22 Cias, Inc. Counterfeit detection using ID numbers with at least one random portion
US5675137A (en) 1986-04-18 1997-10-07 Cias, Inc. Bar code decoding using moving averages to break the (n,k) code barrier for UPC, EAN Code 128 and others
US4839505A (en) 1986-05-29 1989-06-13 Videomat Associates Apparatus and method for storing and retrieving articles
US4814592A (en) 1986-05-29 1989-03-21 Videomat Associates Apparatus and method for storing and retrieving articles
US4750119A (en) 1986-10-10 1988-06-07 Tradevest, Inc. Purchasing system with rebate feature
US5028766A (en) 1987-02-27 1991-07-02 Avs, Inc. Automated rental system
US4884212A (en) 1987-03-23 1989-11-28 Vertx Corporation Apparatus and method for using unique charge cards dispensed from a vending machine
EP0286130A3 (en) 1987-04-08 1989-09-27 Omron Tateisi Electronics Co. Automatic article renting machine
GB8709233D0 (en) 1987-04-16 1987-05-20 Sankey Vending Ltd Machine for renting re-usable articles
US4803348A (en) 1987-06-30 1989-02-07 Lohrey David W Automated customer interface for services involving drop-off and pickup
US4858743A (en) 1987-07-31 1989-08-22 Datavend, Inc. Vending machine and method for automatic vending and returning of merchandise, particularly video cassette tapes
GB8720298D0 (en) 1987-08-28 1987-10-07 Sankey Vending Ltd Vending machine
GB8720297D0 (en) 1987-08-28 1987-10-07 Sankey Vending Ltd Vending machine
US4967906A (en) 1987-10-19 1990-11-06 Diebold, Incorporated Apparatus for dispensing and accepting return of reusable articles
US4896024A (en) 1987-10-19 1990-01-23 Diebold, Incorporated Apparatus for dispensing and accepting return of reusable articles
US4893705A (en) 1987-12-04 1990-01-16 Brown Leonard C Vending machine having plural compartments which are independently selected and controlled
US4903815A (en) 1988-03-25 1990-02-27 I.V.D.M. Ltd. Automatic vending machine and system for dispensing articles
US4997076A (en) 1988-03-25 1991-03-05 I. V. D. M. Ltd. Merchandise transaction machine and system with emergency operational modes
US5143193A (en) 1988-06-30 1992-09-01 Ronald Geraci Automated library article terminal
EP0349284A3 (en) 1988-06-30 1990-03-07 Flixcorp Of America Ltd Automated library article terminal
US5042686A (en) 1988-07-23 1991-08-27 Andre Stucki Device for dispensing goods and use thereof
US4984155A (en) 1988-08-29 1991-01-08 Square D Company Order entry system having catalog assistance
US5007518A (en) 1989-02-13 1991-04-16 Sam Crivello Apparatus for renting articles
US5020958A (en) 1989-02-23 1991-06-04 Philip Tuttobene Article vending machine
US5139384A (en) 1989-02-23 1992-08-18 Philip Tuttobene Article vending machine
JPH07101427B2 (en) 1989-03-29 1995-11-01 富士通株式会社 Bar code reading method and apparatus
US5128520A (en) 1989-08-11 1992-07-07 Spectra-Physics, Inc. Scanner with coupon validation
US5231569A (en) 1990-06-12 1993-07-27 Sears Payment Systems, Inc. Account transaction system
US5159560A (en) 1990-06-25 1992-10-27 Newell William C Automated merchandise dispensing and retrieval system
US5216612A (en) 1990-07-16 1993-06-01 R. J. Reynolds Tobacco Company Intelligent computer integrated maintenance system and method
DE69231012T2 (en) 1991-02-08 2000-09-28 Fujitsu Ltd High-speed bar code reader that can read more than one type of bar code
US5311424A (en) 1991-06-28 1994-05-10 International Business Machines Corporation Method and system for product configuration definition and tracking
US5256863A (en) 1991-11-05 1993-10-26 Comark Technologies, Inc. In-store universal control system
US5521815A (en) 1992-01-31 1996-05-28 K.L.E. Irrevocable Trust Uniform system for verifying and tracking articles of value
US5273183A (en) 1992-02-18 1993-12-28 Philip Tuttobene Article vending machine
US5291598A (en) 1992-04-07 1994-03-01 Gregory Grundy Method and system for decentralized manufacture of copy-controlled software
US5528490A (en) 1992-04-10 1996-06-18 Charles E. Hill & Associates, Inc. Electronic catalog system and method
US5257741A (en) 1992-09-21 1993-11-02 Rode Jerry A Method and apparatus for container redemption and recycling
JPH06211323A (en) 1992-11-30 1994-08-02 Olympus Optical Co Ltd Physical distribution control system
US5712989A (en) 1993-04-02 1998-01-27 Fisher Scientific Company Just-in-time requisition and inventory management system
US6119099A (en) 1997-03-21 2000-09-12 Walker Asset Management Limited Partnership Method and system for processing supplementary product sales at a point-of-sale terminal
US5416306A (en) 1993-08-16 1995-05-16 Imahata; Takeo Method for comparing and verifying security codes at point of sale
US5478990A (en) 1993-10-14 1995-12-26 Coleman Environmental Systems, Inc. Method for tracking the production history of food products
US5372386A (en) 1993-11-26 1994-12-13 Mills; William B. Automated reconciliation system
US5537314A (en) 1994-04-18 1996-07-16 First Marketrust Intl. Referral recognition system for an incentive award program
US5918214A (en) 1996-10-25 1999-06-29 Ipf, Inc. System and method for finding product and service related information on the internet
US5950173A (en) 1996-10-25 1999-09-07 Ipf, Inc. System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents
US7143055B1 (en) 1996-10-25 2006-11-28 Ipf, Inc. Internet-based system for collecting, managing and serving consumer product-related information over the internet using trademarks and universal resource locators (urls) symbolically-linked by manufacturers of consumer products and/or their agents
US6064979A (en) 1996-10-25 2000-05-16 Ipf, Inc. Method of and system for finding and serving consumer product related information over the internet using manufacturer identification numbers
US5520990A (en) 1994-06-10 1996-05-28 Printing For Systems, Inc. Shipping label
US5581064A (en) 1994-11-01 1996-12-03 Pennsylvania Food Merchants Association Automated coupon processing system employing coupon with identifying code and chosen second identifying code uniquely identifying the coupon
US7165174B1 (en) 1995-02-13 2007-01-16 Intertrust Technologies Corp. Trusted infrastructure support systems, methods and techniques for secure electronic commerce transaction and rights management
US5602377A (en) 1995-03-01 1997-02-11 Metanetics Corporation Bar code dataform scanning and labeling apparatus and method
US5721832A (en) 1995-05-12 1998-02-24 Regal Greetings & Gifts Inc. Method and apparatus for an interactive computerized catalog system
US5857175A (en) 1995-08-11 1999-01-05 Micro Enhancement International System and method for offering targeted discounts to customers
US5671279A (en) 1995-11-13 1997-09-23 Netscape Communications Corporation Electronic commerce using a secure courier system
US5737726A (en) 1995-12-12 1998-04-07 Anderson Consulting Llp Customer contact mangement system
US5918213A (en) * 1995-12-22 1999-06-29 Mci Communications Corporation System and method for automated remote previewing and purchasing of music, video, software, and other multimedia products
US5804803A (en) 1996-04-02 1998-09-08 International Business Machines Corporation Mechanism for retrieving information using data encoded on an object
US5799285A (en) 1996-06-07 1998-08-25 Klingman; Edwin E. Secure system for electronic selling
US6125352A (en) 1996-06-28 2000-09-26 Microsoft Corporation System and method for conducting commerce over a distributed network
US5890138A (en) 1996-08-26 1999-03-30 Bid.Com International Inc. Computer auction system
GB9615057D0 (en) 1996-07-18 1996-09-04 Newman Paul B D Identification and tracking of carcasses and primal cuts of meat
US5966450A (en) 1996-08-13 1999-10-12 Lucent Technologies Variable mask for encryption generated independently at communications stations
US5895453A (en) 1996-08-27 1999-04-20 Sts Systems, Ltd. Method and system for the detection, management and prevention of losses in retail and other environments
US5745036A (en) 1996-09-12 1998-04-28 Checkpoint Systems, Inc. Electronic article security system for store which uses intelligent security tags and transaction data
WO2001088831A2 (en) 2000-05-12 2001-11-22 Nintendo Of America Inc. Method/apparatus for enabling purchasers to obtain return information to return products via on line transactions
US8156026B2 (en) 2000-05-12 2012-04-10 Nintendo of America Ltd. Method and apparatus for enabling purchasers of products to obtain return information and to initiate product returns via an on-line network connection
US6757663B1 (en) 1996-10-02 2004-06-29 Nintendo Of America Electronic registration system for product transactions
US6018719A (en) 1996-10-02 2000-01-25 Nintendo Of America Inc. Electronic registration system for product transactions
US6085172A (en) 1996-10-02 2000-07-04 Nintendo Of America Inc. Method and apparatus for efficient handling of product return transactions
US7797164B2 (en) * 1996-10-02 2010-09-14 Nintendo Of America, Inc. Method and apparatus for enabling purchasers of products to obtain return information and to initiate product returns via an on-line network connection
DE19641092A1 (en) 1996-10-04 1998-04-09 Martin Dr Finsterwald Method for setting up a database containing customer data
US7904333B1 (en) 1996-10-25 2011-03-08 Ipf, Inc. Web-based electronic commerce (EC) enabled shopping network configured to allow members of a consumer product management team and authorized parties to communicate directly with consumers shopping at EC-enabled websites along the world wide web (WWW), using multi-mode virtual kiosks (MMVKS) driven by server-side components and managed by product team members
US6134533A (en) 1996-11-25 2000-10-17 Shell; Allyn M. Multi-level marketing computer network server
JP3887854B2 (en) 1996-11-28 2007-02-28 株式会社日立製作所 Electronic trading support method
JPH10222754A (en) 1997-02-12 1998-08-21 Sharp Corp Electronic cash register
US6119164A (en) 1997-04-15 2000-09-12 Full Circle Software, Inc. Method and apparatus for distributing over a network unsolicited information to a targeted audience
US6016027A (en) * 1997-05-19 2000-01-18 The Board Of Trustees Of The University Of Illinois Microdischarge lamp
US5984508A (en) 1997-06-18 1999-11-16 Aveo, Inc. System, method and article of manufacture for product return of software and other information
US6029141A (en) 1997-06-27 2000-02-22 Amazon.Com, Inc. Internet-based customer referral system
JP3656149B2 (en) 1997-06-30 2005-06-08 松下電器産業株式会社 Electronic cash register
US6025780A (en) 1997-07-25 2000-02-15 Checkpoint Systems, Inc. RFID tags which are virtually activated and/or deactivated and apparatus and methods of using same in an electronic security system
US6105001A (en) 1997-08-15 2000-08-15 Larry A. Masi Non-cash transaction incentive and commission distribution system
US6049778A (en) 1997-10-31 2000-04-11 Walker Asset Management Limited Partnership Method and apparatus for administering a reward program
US6016480A (en) 1997-11-07 2000-01-18 Image Data, Llc Merchandise return fraud prevention system and method
US6014635A (en) 1997-12-08 2000-01-11 Shc Direct, Inc. System and method for providing a discount credit transaction network
US6115690A (en) 1997-12-22 2000-09-05 Wong; Charles Integrated business-to-business Web commerce and business automation system
US6029139A (en) 1998-01-28 2000-02-22 Ncr Corporation Method and apparatus for optimizing promotional sale of products based upon historical data
US6154738A (en) 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US5913210A (en) 1998-03-27 1999-06-15 Call; Charles G. Methods and apparatus for disseminating product information via the internet
US7117227B2 (en) 1998-03-27 2006-10-03 Call Charles G Methods and apparatus for using the internet domain name system to disseminate product information
US5949335A (en) 1998-04-14 1999-09-07 Sensormatic Electronics Corporation RFID tagging system for network assets
US6219652B1 (en) 1998-06-01 2001-04-17 Novell, Inc. Network license authentication
US6005476A (en) 1998-07-24 1999-12-21 Valiulis; Carl Electronic identification, control, and security system for consumer electronics and the like
US6222914B1 (en) 1998-09-02 2001-04-24 Mcmullin John L. System and method for administration of an incentive award system having a delayed award payment using a credit instrument
JP3221487B2 (en) 1998-10-19 2001-10-22 日本電気株式会社 Electronic device customer information management system, customer information management method, and recording medium for storing customer information management program
US6746053B1 (en) 1998-10-29 2004-06-08 International Business Machines Corporation Method and system for preventing parallel marketing of wholesale and retail items
CA2350551A1 (en) 1998-11-13 2000-05-25 Nintendo Of America Inc. Method and apparatus for verifying product sale transactions and processing product returns
US6055511A (en) 1998-11-30 2000-04-25 Breault Research Organization, Inc. Computerized incentive compensation
TW515971B (en) 1999-02-10 2003-01-01 Ibm Network-based product information server
WO2000060484A1 (en) 1999-04-05 2000-10-12 Neomedia Technologies, Inc. System and method of using machine-readable or human-readable linkage codes for accessing networked data resources
GT200000061A (en) 1999-05-03 2001-10-25 METHOD AND SYSTEM FOR THE PROCESSING OF PAYMENTS BY INTERNET, USING THE FUND TRANSFER NETWORK.
US6606608B1 (en) 1999-07-19 2003-08-12 Amazon.Com, Inc. Method and system for providing a discount at an auction
AU6760200A (en) 1999-08-04 2001-03-05 Rapidmoney Corporation System and method for rapidly and securely transferring funds electronically between two points
US6965866B2 (en) 2000-05-01 2005-11-15 Elliot Klein Product warranty registration system and method
US7693731B1 (en) 1999-09-30 2010-04-06 Computer Sciences Corporation Business process framework for reinsurance
US6947941B1 (en) 1999-10-14 2005-09-20 Nintendo Of America Inc. Serial number mask and check digit for electronic registration system (ERS)
US6697812B1 (en) 2000-01-18 2004-02-24 Peter Martin Method and system for eliminating error when packing or packaging sets of serialized products or otherwise identifiable products
US8036905B2 (en) 2000-02-29 2011-10-11 Newgistics, Inc. Method and system for processing the local return of remotely purchased products
EP1277148A1 (en) 2000-03-28 2003-01-22 Stamps.Com Inc. Apparatus, systems and methods for online, multi-parcel, multi-carrier, multi-service parcel returns shipping management
US20020010627A1 (en) 2000-05-17 2002-01-24 Gilles Lerat System and method for creation, distribution, exchange, redemption and tracking of digitally signed electronic coupons
CZ200324A3 (en) 2000-06-05 2007-01-31 Optaglio Limited Product verification, system for and method of product authentication
US8510171B2 (en) 2000-07-25 2013-08-13 Nintendo Of America Inc. Electronic product registration system with customizable return/warranty programs
JP2002109098A (en) 2000-10-04 2002-04-12 Fujitsu Ltd Merchandise information management method and repair request method
AU2002211572A1 (en) 2000-10-10 2002-04-22 Nintendo Of America Inc. Voice recognition method and apparatus using model number lookup
JP2002133080A (en) 2000-10-24 2002-05-10 Dainippon Printing Co Ltd System for managing purchaser information of product
US6550685B1 (en) 2000-11-14 2003-04-22 Hewlett-Packard Development Company Lp Methods and apparatus utilizing visually distinctive barcodes
US6536659B1 (en) 2000-11-15 2003-03-25 Returns Online, Inc. Facilitating returns of merchandise purchased from other sources
US7000834B2 (en) 2001-02-21 2006-02-21 International Business Machines Corporation Method to address security and privacy issue of the use of RFID systems to track consumer products
JP2002279090A (en) 2001-03-16 2002-09-27 Toshiba Corp System for judging guarantee range, server and on-line terminal
US6554187B2 (en) 2001-03-23 2003-04-29 Ncr Corporation Method of detecting and managing RFID labels on items brought into a store by a customer
US20020143668A1 (en) 2001-03-30 2002-10-03 Goodwin John C. System and method of managing product returns
US6933848B1 (en) 2001-05-31 2005-08-23 Alien Technology Corporation System and method for disabling data on radio frequency identification tags
US20030050891A1 (en) 2001-09-07 2003-03-13 James Cohen Method and system for registration and tracking of items
US7162440B2 (en) 2001-11-12 2007-01-09 National Notification Center Llc Product management system
US8209226B2 (en) 2001-11-15 2012-06-26 Nintendo Of America Inc. Non-serialized electronic product registration system and method of operating same
US6722568B2 (en) 2001-11-20 2004-04-20 Ncr Corporation Methods and apparatus for detection and processing of supplemental bar code labels
CN1177408C (en) 2001-12-10 2004-11-24 艾默生网络能源有限公司 Insulated gate bipolar transistor IGBT drive protection circuit
US6881527B2 (en) 2002-03-26 2005-04-19 Canon Kabushiki Kaisha Toner, and process cartridge
JP4136437B2 (en) 2002-04-24 2008-08-20 大日本印刷株式会社 Quality assurance system
GT200300100A (en) 2002-04-26 2006-03-29 METHOD AND APPARATUS FOR THE APPROVAL OF COLOR SAMPLES.
US6957333B2 (en) 2002-09-12 2005-10-18 Symbol Technologies, Inc. System and method for encrypted communications between electronic devices
US7118478B2 (en) 2002-09-25 2006-10-10 Harrah's Operating Company, Inc. Self-verifying gaming voucher having secondary machine readable indicia
US20040196489A1 (en) 2003-04-07 2004-10-07 Kia Silverbrook Coupon redemption
US20040153344A1 (en) 2003-04-15 2004-08-05 Tuan Bui System and method for creating and updating a mobile patient care plan in real-time
US7752137B2 (en) 2003-11-03 2010-07-06 Meyers Printing Company Authentication and tracking system
US8615470B2 (en) 2003-11-03 2013-12-24 Verify Brand Authentication and tracking system
JP2005141374A (en) 2003-11-05 2005-06-02 Toshiba Tec Corp Merchandise sales data processor
US7840439B2 (en) 2003-11-10 2010-11-23 Nintendo Of America, Inc. RF-ID product tracking system with privacy enhancement
US20050137882A1 (en) 2003-12-17 2005-06-23 Cameron Don T. Method for authenticating goods
JP2005234981A (en) 2004-02-20 2005-09-02 Nci Systems Integration Inc Guarantee information confirmation system
US7900151B2 (en) 2004-03-05 2011-03-01 Sap Ag Maintaining individual object data
US20060062734A1 (en) 2004-09-20 2006-03-23 Melker Richard J Methods and systems for preventing diversion of prescription drugs
EP1667018B1 (en) 2004-10-14 2016-04-20 Sap Se Using customized data to control transaction processing in a computer application
TW200619111A (en) 2004-12-02 2006-06-16 Murata Machinery Ltd Warehouse system
US7156305B2 (en) 2004-12-23 2007-01-02 T3C Inc. Apparatus and method for authenticating products
US7303123B2 (en) 2005-02-07 2007-12-04 Cryovac, Inc. Method of labeling an item for item-level identification
US7455230B2 (en) 2005-04-22 2008-11-25 Nintendo Of America Inc. UPC, EAN and JAN validation system and method for loss prevention at point of sale/return
US7925044B2 (en) 2006-02-01 2011-04-12 Markmonitor Inc. Detecting online abuse in images
JP2007226516A (en) 2006-02-23 2007-09-06 Japan Research Institute Ltd Method, program and device for managing warranty
JP2007257561A (en) 2006-03-27 2007-10-04 Mitsubishi Electric Information Systems Corp Product assurance management system and program
US20100235250A1 (en) 2006-06-08 2010-09-16 Planetech Inc. Tracking items in a distribution channel
CN101089871B (en) 2006-06-14 2010-04-14 中国科学院自动化研究所 System and method for antiforge of article with certificate based on radio frequency technology
US20080052184A1 (en) 2006-08-22 2008-02-28 Nintendo Of America Inc. Systems and methods for product authentication and warranty verification for online auction houses
JP2008197768A (en) 2007-02-09 2008-08-28 Nikon Corp Non-contact memory incorporating apparatus, and its sales management system
WO2008103274A2 (en) 2007-02-16 2008-08-28 Noblis, Inc. Alert distribution and management system and returns module
JP2009032171A (en) 2007-07-30 2009-02-12 Warranty Mart:Kk Extended guarantee system and method for controlling the same
US20090150170A1 (en) 2007-12-11 2009-06-11 Nintendo Of America Method and apparatus for fraud reduction and product recovery
US20100325020A1 (en) 2008-12-04 2010-12-23 Nintendo Of America, Inc. Systems and/or methods for globally tracking items and generating active notifications regarding the same
US8302024B2 (en) 2009-04-02 2012-10-30 Nintendo Of America Inc. Systems and/or methods for paging control including selective paging element display according to a binary subdivision and/or a serial progressive display approach
US20110016008A1 (en) 2009-07-14 2011-01-20 Nintendo of America Inc., Electronic registration systems for processing variable or multiple return/warranty policies, and associated methods
US8239269B2 (en) 2009-09-11 2012-08-07 Nintendo Of America Inc. System and/or method for handling returns involving products tied to post-paid subscriptions/services

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010054064A1 (en) * 1997-07-02 2001-12-20 Pallipuram V. Kannan Method system and computer program product for providing customer service over the world-wide web
US7379899B1 (en) * 1998-11-13 2008-05-27 Nintendo Of America Inc. Method and apparatus for verifying product sale transactions and processing product returns
US20060235768A1 (en) * 2005-03-24 2006-10-19 Sabre Inc.And Travelocity.Com Lp. System, method, and computer program product for reducing the burden on inventory system by displaying product availability information for a range of parameters related to a product

Also Published As

Publication number Publication date
US8126724B2 (en) 2012-02-28
WO2002031809A1 (en) 2002-04-18
US7729923B2 (en) 2010-06-01
AU2002211572A1 (en) 2002-04-22
US20050100144A1 (en) 2005-05-12
US20100185533A1 (en) 2010-07-22

Similar Documents

Publication Publication Date Title
US8126724B2 (en) Voice recognition method and apparatus using model number lookup
US8229861B1 (en) Methods and systems for online warranty management
EP1269732B1 (en) Interacting with a data network using a telephonic device
US8130929B2 (en) Methods for obtaining complex data in an interactive voice response system
US9171341B1 (en) Methods and systems for providing property data
US6510417B1 (en) System and method for voice access to internet-based information
CA2474600C (en) A user authentication system and methods thereof
US6529881B2 (en) System and method for identifying an unidentified customer at the point of sale
US6539386B1 (en) Methods and apparatus for modifying a customer order
US8874446B2 (en) System and method for funneling user responses in an internet voice portal system to determine a desired item or servicebackground of the invention
US20080313571A1 (en) Method and system for automating the creation of customer-centric interfaces
US20140149252A1 (en) Dynamic template selector and data integrity engine for inspection reports
US20120197632A1 (en) System and method for the transformation and canonicalization of semantically structured data
US20020169615A1 (en) Computerized voice-controlled system for compiling quality control data
US8811593B1 (en) Call center agent centric speech decoding system and method with quality assurance function
CA2550822A1 (en) Profiling item sellers to inform item purchasing decisions and build trust in a multiple-seller marketplace
IE20000080A1 (en) System and method for identification and streamlined access to online services
WO2009097179A1 (en) Method and system for authenticating customer identities
EP1459217A2 (en) Voice-enabled, consumer transaction system
US20020029159A1 (en) System and method for providing an automated interview
CA2639372A1 (en) Interactive voice response interface, system, methods, and program for correctional facility commissary
US20050222854A1 (en) Automatically processing an expense report using an expense report agent
US20020143767A1 (en) Methods and systems for generating and managing offerings
WO2009129080A1 (en) Software option selection and validation system
US7676435B1 (en) Method and system for triggering enhanced security verification in response to atypical selections at a service-oriented user interface terminal

Legal Events

Date Code Title Description
AS Assignment

Owner name: SIRAS.COM INC., WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NINTENDO OF AMERICA INC.;REEL/FRAME:033450/0042

Effective date: 20140729

AS Assignment

Owner name: E2INTERACTIVE, INC. D/B/A E2INTERACTIVE, INC., GEO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIRAS.COM INC.;REEL/FRAME:034027/0452

Effective date: 20140818

AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:E2INTERACTIVE, INC.;REEL/FRAME:034783/0446

Effective date: 20150109

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NO

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:E2INTERACTIVE, INC.;REEL/FRAME:048465/0464

Effective date: 20190228

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NORTH CAROLINA

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:E2INTERACTIVE, INC.;REEL/FRAME:048465/0464

Effective date: 20190228

AS Assignment

Owner name: E2INTERACTIVE, INC., GEORGIA

Free format text: RELEASE OF PATENT SECURITY INTEREST;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:048489/0742

Effective date: 20190228

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: NINTENDO OF AMERICA INC., WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:O'CONNOR, DEAN;REEL/FRAME:049682/0709

Effective date: 20030828