JP5129194B2 - Product search device - Google Patents

Product search device Download PDF

Info

Publication number
JP5129194B2
JP5129194B2 JP2009122388A JP2009122388A JP5129194B2 JP 5129194 B2 JP5129194 B2 JP 5129194B2 JP 2009122388 A JP2009122388 A JP 2009122388A JP 2009122388 A JP2009122388 A JP 2009122388A JP 5129194 B2 JP5129194 B2 JP 5129194B2
Authority
JP
Japan
Prior art keywords
search
product
plurality
product name
names
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.)
Active
Application number
JP2009122388A
Other languages
Japanese (ja)
Other versions
JP2010271869A (en
Inventor
繭 泉
Original Assignee
ヤフー株式会社
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 ヤフー株式会社 filed Critical ヤフー株式会社
Priority to JP2009122388A priority Critical patent/JP5129194B2/en
Publication of JP2010271869A publication Critical patent/JP2010271869A/en
Application granted granted Critical
Publication of JP5129194B2 publication Critical patent/JP5129194B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to a technology for searching for products via a network such as the Internet.

  Recently, buying and selling of products using the Internet has been actively performed, and such online shopping has become an indispensable existence in daily life.

  By the way, in order to search for a desired product, it is common to search for a product from a product name, a model number, or the like, using a search function provided by an internet shopping server. When the specific model number is not known, the product name is often the decisive factor for the search.

  Therefore, an effort is made to artificially register words that may be used as the product name (call name) of the product as keywords of the product database for determining a match with the search term input by the user. ing. Patent Document 1 discloses a technique for reducing the labor of inputting the product name, improving the reliability of the product master, and reducing the human cost.

JP 2007-264773 A

  As described above, conventionally, the search of the user has been supported by artificially maintaining the keywords of the product database.

  However, even products that exist in the past may become popular due to the occurrence of new product names, and maintenance of keywords in the product database may not be in time, and there is a possibility that a search will not hit. In this case, the user does not hit the search even though the desired product is actually sold, so the user often gives up the purchase because the desired product is not sold. Losing sales opportunities.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to automatically collect and manage a plurality of fluid product names for the same product, and input by the user. It is an object of the present invention to provide a product search apparatus that can perform a complete search for a search term.

In order to solve the above-described problem, in the present invention, as described in claim 1, it is specified by a search request receiving unit that receives a search request for a product from a user terminal, and a search condition included in the search request. Other product name acquisition means for acquiring other product names corresponding to the selected product name from the multiple product name database, search condition correction means for adding the acquired other product names to the search conditions with OR conditions, and after correction Search execution means for performing a search from the product database according to the search conditions, and a plurality of product name database registration means for extracting a plurality of product names for the same product from a search query log and registering the product names in the multiple product name database , The multiple product name database registration means uses the OR operator or the NOT operator when the query log data search expression is an OR search or a NOT search. Search terms of identifying a plurality of product names later if the query within a certain time period by the same user is present, and the product search device for identifying the search term for each query as a plurality of product name and summary.

In addition, as described in claim 2 , the product search device receives a search request for a product from a user terminal , and the product search device is a product specified by a search condition included in the search request. a plurality trade name acquisition step of acquiring the other trade names corresponding to the names of a plurality trade name database, the product search device, the search condition correcting step of adding by the OR condition to other trade name search conditions acquired A search execution step in which the product search device searches from the product database according to the corrected search condition, and the product search device extracts a plurality of product names for the same product from a search query log. and a plurality trade name database updating step of registering the name database, the plurality tradename database registration process, the search expression is OR search der query log data If the search term before or after the OR operator or the NOT operator is specified as a plurality of product names and there is a query within a certain time by the same user, the search term of each query is It can comprise as a goods search method specified as a some goods name .

  In the product search device of the present invention, it is possible to automatically collect and manage a plurality of fluid product names for the same product, and perform a complete search for a search term input by the user. .

It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the data structure example of a query log. It is a figure which shows the data structure example of multiple goods name database. It is a figure which shows the data structure example of a goods database. It is a figure which shows the hardware structural example of a goods search server. It is a sequence diagram which shows the process example of embodiment. It is a flowchart which shows the process example of a several goods name extraction part. It is a figure which shows the example of a screen of a search page. It is a figure which shows the example of the suggestion in a search screen. It is a figure which shows the example of a screen of a search result page.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 1, a network 1 such as the Internet is connected with a plurality of user terminals 2 such as PCs (Personal Computers), mobile phones, PDAs (Personal Digital Assistants) operated by users of internet shopping. The user terminal 2 includes a general browser (Web browser) 21. The browser 21 performs request / acquisition / display of page data described in a language such as HTML (Hyper Text Markup Language), transmission of form data, and the like according to HTTP (Hyper Text Transfer Protocol) which is a standard protocol of the Internet. It has a function.

  On the other hand, the network 1 is connected to a product search server 3 that searches for products in response to access from the browser 21 of the user terminal 2 operated by the user.

  The product search server 3 includes a product search processing unit 31 and a multiple product name database registration unit 32 as functional units. These functional units are realized by a computer program executed on hardware resources such as a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory) of a computer constituting the product search server 3. Is. These functional units do not need to be arranged on a single computer, and may be distributed as necessary.

  The product search processing unit 31 includes a search request receiving unit 311, another product name acquisition unit 312, a search condition correction unit 313, a search execution unit 314, a search result page generation unit 315, and a search result page transmission unit 316.

  The multiple product name database registration unit 32 includes a query log acquisition unit 321, a multiple product name extraction unit 322, and a database registration unit 323.

  A query log 301, a multiple product name database 302, and a product database 303 are provided as databases and the like that are referenced by the product search server 3. These databases and the like systematically hold predetermined data on a storage medium such as an HDD (Hard Disk Drive) in a computer that holds the database and the like.

  FIG. 2 is a diagram illustrating an example of the data structure of the query log 301, and includes items such as “acceptance date / time”, “session ID”, and “search formula”. “Reception date and time” is information indicating the date and time when the search request (query) is received. “Session ID” is information that roughly identifies the user or user terminal that has made a search request. When a registered user logs in in advance, the user can be specified accurately by using a session ID by login. Even when the user is not logged in, the identity of the user terminal can be identified within a short time by using a value based on the IP address of the user terminal. “Search expression” is a character string of the search expression included in the search request. The search expression may be a single search term or may include a plurality of search terms and operators such as AND, OR, NOT.

  FIG. 3 is a diagram showing an example of the data structure of the multiple product name database 302, and has items such as “product name”. In “Product Name”, a plurality of product names corresponding to the same product are listed. For example, “Jeans, Denim”, “Jewelry, Accessories”, “Heating, Heater, Stove”. The product name here includes not only an official product name used by a manufacturer or the like, but also a user's normal name.

  FIG. 4 is a diagram showing an example of the data structure of the product database 303, and includes items such as “product ID”, “title”, “description”, “image”, and “keyword”. “Product ID” is information for identifying a product to be sold. “Title” is a headline on the display of the product. “Description” is a simple description of the product. “Image” is an appearance image of the product. The “keyword” is a list of phrases used for searching for the product.

  Returning to FIG. 1, the product search processing unit 31 has a function of receiving a search request from the browser 21 of the user terminal 2 and returning a search result to the browser 21 of the user terminal 2.

  The search request receiving unit 311 has a function of providing a search page to the browser 21 of the user terminal 2 and receiving a search request.

  The other product name acquisition unit 312 searches a plurality of product names including the search term from the plurality of product name database 302 based on the search terms included in the search condition of the search request, and registers them together with the search terms. It has a function to acquire other product name (s).

  The search condition correction unit 313 has a function of correcting the search condition based on the other product name acquired by the other product name acquisition unit 312. The correction of the search condition may be performed automatically or after confirmation from the user.

  The search execution unit 314 has a function of searching the product database 303 based on the search condition.

  The search result page generation unit 315 has a function of generating a search result page based on the search result.

  The search result page transmission unit 316 has a function of transmitting the search result page to the browser 21 of the user terminal 2 that is a request source.

  The multiple product name database registration unit 32 is activated at a predetermined timing (such as a time zone when the load on the product search server 3 is light), extracts a plurality of product names from the query log 301, and registers them in the multiple product name database 302. Have.

  The query log acquisition unit 321 has a function of acquiring query log data from the query log 301.

  The multiple product name extraction unit 322 has a function of extracting and specifying multiple product names from the acquired query log data.

  The database registration unit 323 has a function of registering the multiple product names specified by the multiple product name extraction unit 322 in the multiple product name database 302.

  FIG. 5 is a diagram illustrating a hardware configuration example of the product search server 3.

  In FIG. 5, the product search server 3 is connected to a CPU 3002, ROM 3003, RAM 3004, NVRAM (Non-Volatile Random Access Memory) 3005, I / F (Interface) 3006, and I / F 3006 connected to a system bus 3001. A keyboard, mouse, monitor, CD / DVD (Compact Disk / Digital Versatile Disk) drive I / O (Input / Output Device) 3007, HDD 3008, NIC (Network Interface Card) 3009, and the like. M is a medium (recording medium) such as a CD / DVD in which a program or data is stored.

<Operation>
FIG. 6 is a sequence diagram showing a processing example of the above embodiment.

  In FIG. 6, when starting the process, the multiple product name database registration unit 32 of the product search server 3 acquires query log data from the query log 301 by the query log acquisition unit 321 (step S101).

  Next, the multiple product name database registration unit 32 extracts and specifies multiple product names from the acquired query log data by the multiple product name extraction unit 322 (step S102). Details of processing in the multiple product name extraction unit 322 will be described later.

  Next, the multiple product name database registration unit 32 registers the specified multiple product names in the multiple product name database 302 by the database registration unit 323 (step S103).

  FIG. 7 is a flowchart illustrating a processing example of the multiple product name extraction unit 322.

  In FIG. 7, the multiple product name extraction unit 322 performs the following processing for each acquired query log data.

  First, when the process starts (step S201), the multiple product name extraction unit 322 determines whether the query log data search expression is an OR search or a NOT search (step S202). If an OR operator is included in the search expression, an OR search is performed, and if a NOT operator is included, a NOT search is performed.

  If the query log data search expression is an OR search or a NOT search (Yes in step S202), the multiple product name extraction unit 322 specifies the search terms before and after the OR operator or the NOT operator as multiple product names ( Step S203), the process is terminated (Step S206). In order to improve the accuracy of multiple product names, the multiple product names may be specified only when it is confirmed by a synonym dictionary (not shown) that multiple search terms are included in the synonyms. . Furthermore, the number of times specified as a plurality of product names may be counted, and only when a predetermined number of times has been reached, may be formally specified as a plurality of product names.

  When the query log data search expression is an OR search or not a NOT search (No in step S202), the multiple product name extraction unit 322 further determines whether there is a query within a predetermined time with the same session ID (step S204). ).

  When there is a query within a certain time with the same session ID (Yes in step S204), the search term of each query is specified as a plurality of product names (step S205), and the process is terminated (step S206). In order to improve the accuracy of multiple product names, the multiple product names may be specified only when it is confirmed by a synonym dictionary (not shown) that multiple search terms are included in the synonyms. . Furthermore, the number of times specified as a plurality of product names may be counted, and only when a predetermined number of times has been reached, may be formally specified as a plurality of product names.

  If there is no query within the predetermined time with the same session ID (No in step S204), the processing is terminated as it is (step S206).

  By the above processing, for example, when query log data “heating OR heater” exists, “heating” and “heater” are registered in the multiple product name database 302 as multiple product names “heating, heater”. This is because the user who has issued the search request can determine that both “heating” and “heater” are aware of the product names in the same row.

  For example, when query log data “heating NOT stove” exists, “heating” and “stove” are registered in the multiple product name database 302 as multiple product names “heating, stove”. This is because the user who has issued the search request can determine that “heating” and “stove” are conscious of the product names in the same row by excluding “stove”.

  Also, for example, when query log data of “jewelry” and “accessories” exist within a certain time with the same session ID, these “jewelry” and “accessories” are multiple product name databases as multiple product names “jewelry and accessories”. 302 is registered. This is because the user who issued the search request can determine that both “jewelry” and “accessory” have been input continuously in order to search for the same product, and can be determined to be aware of the same product name. It is.

  Returning to FIG. 6, when the user of the user terminal 2 searches for a product for purchasing a product, the browser 21 of the user terminal 2 accesses the product search processing unit 31 of the product search server 3 to make a search page request (step) S111). For the page request, a message including a GET method according to HTTP, which is an Internet standard protocol, a request URI (Uniform Resource Indicator), and the like is transmitted from the browser 21 of the user terminal 2 to the product search processing unit 31 of the product search server 3. This is done.

  In response to this, the product search processing unit 31 of the product search server 3 returns the page data of the search page stored or dynamically generated by the search request receiving unit 311 to the browser 21 of the user terminal 2 (step S112). ). The page data is described in HTML or the like, and is transmitted from the product search processing unit 31 of the product search server 3 to the browser 21 of the user terminal 2 according to an HTTP response or the like.

  The browser 21 of the user terminal 2 displays a search page (step S113), and the user inputs search conditions (step S114). FIG. 8 is a diagram showing a screen example of a search page, which is provided with a search condition input field and a “search” button. The user inputs characters and numbers in the input field by keyboard operation or the like and presses the “search” button to complete the input.

  Returning to FIG. 6, when the input to the search page is completed, the input content (search request) of the search condition is transmitted from the browser 21 of the user terminal 2 to the product search processing unit 31 of the product search server 3 (step S115). The input content is transmitted from the browser 21 of the user terminal 2 to the product search processing unit 31 of the product search server 3 as data such as HTML added to the HTTP POST method or PUT method, or as a parameter added to the GET method. .

  The product search processing unit 31 of the product search server 3 that has received the search request records the search condition included in the search request by the search request receiving unit 311 in the query log 301 in association with the received date and session ID (step S116). ).

  Next, the product search processing unit 31 of the product search server 3 uses the other product name acquisition unit 312 to search the multiple product name database 302 for multiple product names including the search term based on the search terms included in the received search condition. Then, other product name (s) registered as a pair with the search term are acquired (step S117).

  Next, the product search processing unit 31 of the product search server 3 corrects the search condition by the search condition correction unit 313 (step S118).

  There are two methods for correcting the search condition by the search condition correction unit 313. One is to automatically add another product name acquired by the other product name acquisition unit 312 to the search condition designated by the user as an OR search without asking the user for confirmation. The other is to display a suggestion to the user that the search condition should be corrected, and add another product name as an OR search when the user confirms. FIG. 9 is a diagram showing an example of a suggestion on the search screen. “Since there is another product name △△△△ in the product name XXXXX included in the search expression you entered, It is recommended that you search. The message “The search condition is corrected by pressing the confirmation button.” Is displayed, and the search condition is corrected by pressing the “Confirm” button. When the “ignore” button is pressed, the search condition is not corrected.

  Returning to FIG. 6, after correcting the search conditions, the product search processing unit 31 of the product search server 3 searches the product database 303 based on the search conditions by the search execution unit 314 (step S <b> 119). That is, a record that matches (including a partial match) is obtained by comparing a character / numeric string other than the search condition operator and an item such as “keyword” in the product database 303 (FIG. 4), and the operator is taken into consideration. Then, a logical operation is performed to obtain a search result.

  Next, the product search processing unit 31 of the product search server 3 uses the search result page generation unit 315 to generate a search result page (step S120). That is, a list page of products hit by the search is generated.

  Next, the product search processing unit 31 of the product search server 3 transmits the search result page to the browser 21 of the user terminal 2 through the search result page transmission unit 316 (step S121). The page data is transmitted from the product search processing unit 31 of the product search server 3 to the browser 21 of the user terminal 2 according to an HTTP response or the like.

  The browser 21 of the user terminal 2 displays the received search result page (step S122). FIG. 10 is a diagram showing a screen example of the search result page, in which titles, descriptions, images, and the like of a plurality of products hit by the search are displayed.

<Summary>
As described above, according to the present embodiment, a plurality of fluid product names for the same product are automatically extracted from the query log 301 and registered in the multiple product name database 302, and a search request from a user is received. On the other hand, other product names are corrected (supplemented) from the multiple product name database 302. Therefore, even when a search request is made with a product name that is not set as a keyword in the product database 303, it is more likely that a desired product will be searched for by supplementing the product name, and the search entered by the user It is possible to perform a complete search for words.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

DESCRIPTION OF SYMBOLS 1 Network 2 User terminal 21 Browser 3 Goods search server 31 Goods search processing part 311 Search request reception part 312 Other goods name acquisition part 313 Search condition correction | amendment part 314 Search execution part 315 Search result page generation part 316 Search result page transmission part 32 Multiple Product name database registration unit 321 Query log acquisition unit 322 Multiple product name extraction unit 323 Database registration unit 301 Query log 302 Multiple product name database 303 Product database

Claims (2)

  1. Search request accepting means for accepting a product search request from a user terminal;
    Other product name acquisition means for acquiring another product name corresponding to the product name specified in the search condition included in the search request from the multiple product name database,
    Search condition correction means for adding other acquired product names to the search condition by OR condition;
    Search execution means for searching from the product database according to the corrected search conditions;
    A plurality of product name database registration means for extracting a plurality of product names for the same product from a search query log and registering them in the plurality of product name databases ;
    The plurality of product name database registration means,
    When the query log data search expression is OR search or NOT search, the search terms before and after the OR operator or NOT operator are specified as a plurality of product names,
    A product search apparatus characterized by specifying a search term of each query as a plurality of product names when there is a query within a predetermined time by the same user .
  2. A search request receiving step in which the product search device receives a search request for a product from the user terminal;
    The product search device acquires a plurality of product name acquisition steps for acquiring other product names corresponding to the product name specified by the search condition included in the search request from a plurality of product name databases,
    A search condition correction step in which the product search device adds another acquired product name to the search condition using an OR condition;
    The product search device performs a search execution step of searching from a product database according to the corrected search condition,
    The product search device includes a plurality of product name database update steps for extracting a plurality of product names for the same product from a search query log and registering the product names in the multiple product name database .
    The multiple product name database registration step includes:
    When the query log data search expression is OR search or NOT search, the search terms before and after the OR operator or NOT operator are specified as a plurality of product names,
    A product search method characterized by specifying a search term of each query as a plurality of product names when there are queries within a certain time by the same user .
JP2009122388A 2009-05-20 2009-05-20 Product search device Active JP5129194B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2009122388A JP5129194B2 (en) 2009-05-20 2009-05-20 Product search device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2009122388A JP5129194B2 (en) 2009-05-20 2009-05-20 Product search device

Publications (2)

Publication Number Publication Date
JP2010271869A JP2010271869A (en) 2010-12-02
JP5129194B2 true JP5129194B2 (en) 2013-01-23

Family

ID=43419854

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2009122388A Active JP5129194B2 (en) 2009-05-20 2009-05-20 Product search device

Country Status (1)

Country Link
JP (1) JP5129194B2 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012124604A (en) 2010-12-06 2012-06-28 Sony Corp Apparatus control device, apparatus control method, and program
KR101707652B1 (en) * 2015-01-26 2017-02-16 주식회사 포워드벤처스 Apparatus, method and computer program for providing shopping service

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6144958A (en) * 1998-07-15 2000-11-07 Amazon.Com, Inc. System and method for correcting spelling errors in search queries
JP2003091552A (en) * 2001-09-17 2003-03-28 Hitachi Ltd Retrieval requested information extraction method, its operating system and processing program of the same
US20060190447A1 (en) * 2005-02-22 2006-08-24 Microsoft Corporation Query spelling correction method and system
US8438142B2 (en) * 2005-05-04 2013-05-07 Google Inc. Suggesting and refining user input based on original user input

Also Published As

Publication number Publication date
JP2010271869A (en) 2010-12-02

Similar Documents

Publication Publication Date Title
US8275666B2 (en) User supplied and refined tags
US8838438B2 (en) System and method for determining sentiment from text content
US9152722B2 (en) Augmenting online content with additional content relevant to user interest
US7885863B2 (en) Methods and computer readable media for enhancing product reviews
CN101071424B (en) Personalized information push system and method
CN1278263C (en) System for carrying out universal search management in one or more networks
US20120239497A1 (en) Method and process of using a social network to retarget a personal advertisement
US9319479B2 (en) Suggesting a discussion group based on indexing of the posts within that discussion group
US8676829B2 (en) Methods and apparatus for generating a data dictionary
CN102760172B (en) Network searching method and network searching system
US8600979B2 (en) Infinite browse
US20110320423A1 (en) Integrating social network data with search results
US20050261962A1 (en) Anonymous page recognition
CN102317936B (en) Identifying comments to show in connection with a document
US20130311875A1 (en) Web browser embedded button for structured data extraction and sharing via a social network
KR20140034180A (en) Priority dimensional data conversion path reporting
US20110208513A1 (en) Splitting a character string into keyword strings
US8712996B2 (en) Information repository search system
CN102567475B (en) User interface for interactive query reformulation
KR20070005873A (en) Categorization of locations and documents in a computer network
JP5480389B2 (en) Specialized for dynamic search suggestions and classification
CN101414307A (en) Method and server for providing picture searching
CN101490677A (en) Presenting search results information
US20120290910A1 (en) Ranking sentiment-related content using sentiment and factor-based analysis of contextually-relevant user-generated data
US10235681B2 (en) Text extraction module for contextual analysis engine

Legal Events

Date Code Title Description
A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20120322

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20120327

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20120524

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20121002

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20121101

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

Ref document number: 5129194

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20151109

Year of fee payment: 3

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

S531 Written request for registration of change of domicile

Free format text: JAPANESE INTERMEDIATE CODE: R313531

R350 Written notification of registration of transfer

Free format text: JAPANESE INTERMEDIATE CODE: R350

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

S533 Written request for registration of change of name

Free format text: JAPANESE INTERMEDIATE CODE: R313533