Information processing device, server, information processing method, and program
The information processing device and server system address the lack of advertisement and product information for hash tags by providing a system for integrating and billing advertising on web pages based on hash tags, enabling effective advertising and product information delivery.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- ZETA株式会社
- Filing Date
- 2025-06-16
- Publication Date
- 2026-04-17
AI Technical Summary
Existing technologies fail to provide pages with advertisement and product information related to hash tags, and do not allow for the association of advertisement information with hash tags.
An information processing device that includes a selection receiving unit, advertising information acquisition unit, product information acquisition unit, page configuration unit, and page output unit, which enables the provision of pages containing advertising and product information related to hash tags, and further supports user-generated content and hashtag acquisition, along with a server system for advertiser recruitment and billing.
Enables the provision of pages with advertising and product information related to hash tags, allows advertisers to bid on desired hashtags, and facilitates automatic billing for advertising fees, thereby enhancing the integration of advertising and product information on web pages.
Smart Images

Figure 2026066950000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an information processing apparatus and the like that perform processing related to hash tags.
Background Art
[0002] Conventionally, there has been a technique for providing a page including advertisement information and product information based on the activities or inactivity of a user corresponding to search results (see Patent Document 1).
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] However, in the prior art, it was not possible to provide a page including advertisement information and product information for hash tags of a web page.
[0005] Also, in the prior art, advertisement information for hash tags could not be associated.
Means for Solving the Problems
[0006] The first information processing device of this invention comprises: a selection receiving unit that accepts the selection of a hashtag; an advertising information acquisition unit that acquires advertising information paired with the hashtag corresponding to the selection received by the selection receiving unit from an advertising management unit that stores one or more pieces of advertising information corresponding to one or more hashtags; a product information acquisition unit that acquires product information paired with the hashtag corresponding to the selection received by the selection receiving unit from a product management unit that stores two or more pieces of product information corresponding to one or more hashtags; a page configuration unit that constitutes a page having the advertising information acquired by the advertising information acquisition unit and the product information acquired by the product information acquisition unit; and a page output unit that outputs the page configured by the page configuration unit.
[0007] This configuration allows for the provision of pages containing advertising information and product information related to the page's hashtags.
[0008] Furthermore, the information processing device of the second invention, compared to the first invention, further comprises a tag acquisition unit that acquires one or more tags using tag source information that is the source for acquiring tags in a page stored in a page storage unit, adds "#" to each of the one or more tags, and acquires one or more hashtags with "#" added, and the hashtag corresponding to the selection received by the selection receiver is the hashtag acquired by the tag acquisition unit.
[0009] This configuration makes it possible to provide a page that includes advertising information and product information related to hashtags obtained from UGC (User-Generated Content), etc.
[0010] Furthermore, the information processing device of this third invention, in contrast to the second invention, is an information processing device in which the tag source information is user-generated content (UGC) entered by a user for a page stored in the page storage unit, or provided information provided to the user by the provider of the page stored in the page storage unit.
[0011] This configuration makes it possible to provide a page that includes advertising information and product information related to hashtags obtained from UGC (User-Generated Content), etc.
[0012] Furthermore, the information processing device of this fourth invention is an information processing device in which a hashtag is a phrase having two or more words, in relation to any one of the first to third inventions.
[0013] This configuration allows for the provision of a page containing advertising information and product information for hashtags, which are phrases consisting of two or more words.
[0014] Furthermore, the information processing device of the fifth invention is an information processing device that, in addition to any one of the first to fourth inventions, has an advertising management unit that stores one or more pieces of advertising information associated with advertiser identifiers and advertising fee information, associated with one or more hashtags, and a billing processing unit that performs billing processing for billing advertisers identified by advertiser identifiers paired with hashtags used to compose the page when the page output unit outputs a page composed by the page composition unit.
[0015] This configuration allows advertisers to be charged for advertising on the page's hashtags.
[0016] Furthermore, the server of this sixth invention comprises: a hashtag management unit that stores one or more hashtags obtained by adding "#" to one or more tags acquired from tag source information on a page; an advertiser recruitment unit that transmits recruitment screen information, which is screen information for recruiting advertisers for one or more hashtags in the hashtag management unit, to one or more terminal devices; an application receiving unit that receives application information having advertiser information about advertisers from terminal devices in association with hashtags in response to the transmission of recruitment screen information; and an advertiser information storage unit that stores the advertiser information received by the application receiving unit in association with hashtags.
[0017] This configuration allows advertisers to bid on the hashtags they want to advertise.
[0018] In addition, the server of the seventh invention includes a hash tag management unit that stores one or more hash tags each with a "#" added to each of the one or more tags obtained from the tag source information in a page, an advertiser management unit that stores two or more pieces of advertiser information regarding advertisers, a corresponding unit that associates at least one piece of advertiser information from the two or more pieces of advertiser information in the advertiser management unit with each of the one or more hash tags in the hash tag management unit, and an advertiser information storage unit that stores and accumulates one piece of advertiser information associated by the corresponding unit in association with the hash tag.
[0019] With such a configuration, an advertiser can be automatically determined for a hash tag.
[0020] Furthermore, the information processing apparatus of the eighth invention further includes a billing processing unit that performs a billing process for billing an advertiser for an advertising fee indicated by the advertising fee information associated with a hash tag, with respect to the advertiser corresponding to one piece of advertiser information accumulated by the advertiser information storage unit, where the hash tag management unit stores advertising fee information associated with each of the one or more hash tags, for the sixth or seventh invention.
[0021] With such a configuration, an advertising fee can be billed to an advertiser for a hash tag determined by the advertiser.
Advantages of the Invention
[0022] According to the information processing apparatus of the present invention, a page including advertising information and product information for hash tags of a web page can be provided.
Brief Description of the Drawings
[0023] [Figure 1] Conceptual diagram of information system A in Embodiment 1 <0000A flowchart illustrating the first example of the tag acquisition process. [Figure 6] A flowchart illustrating a second example of the tag acquisition process. [Figure 7] A flowchart illustrating an example of the process for retrieving a set of tags. [Figure 8] A flowchart illustrating an example of the same page structure processing. [Figure 9] This figure illustrates an example of processing by the tag acquisition unit 131. [Figure 10] Figure showing an example of the same output. [Figure 11] Figure showing an example of the same output. [Figure 12] A diagram showing an example of the same facet. [Figure 13] Conceptual diagram of information system B in Embodiment 2 [Figure 14] Block diagram of the same information system B [Figure 15] Block diagram of the information processing device 4. [Figure 16] A flowchart illustrating an example of the operation of the information processing device 4. [Figure 17] A flowchart illustrating an example of the product information storage process. [Figure 18] A flowchart illustrating an example of the billing process. [Figure 19] A flowchart illustrating an example of the advertiser decision-making process. [Figure 20] A flowchart illustrating an example of the application process. [Figure 21] A flowchart illustrating an example of the same tag selection process. [Figure 22] A flowchart illustrating an example of server 5's operation. [Figure 23] A diagram showing an example of the product management sheet. [Figure 24] A diagram showing an example of the advertising management table. [Figure 25] A diagram showing an example of the advertiser management sheet. [Figure 26] A diagram showing an example of the application page. [Figure 27]Figure showing an example of the same screen. [Figure 28] A diagram showing an example of a page with the same structure. [Figure 29] A diagram showing an example of a page with the same structure. [Figure 30] Block diagram of the computer system in the above embodiment [Modes for carrying out the invention]
[0024] The following describes embodiments of the information processing device and the like with reference to the drawings. Note that components denoted by the same reference numerals in the embodiments perform similar operations, and therefore, further explanation may be omitted.
[0025] (Embodiment 1) This embodiment describes a page generation device that automatically retrieves one or more hashtags from tag source information corresponding to a product, and from these one or more hashtags, constructs a web page that contains product-related information, which corresponds to one or more hashtags, and stores it in association with address information. The tag source information includes, for example, user-generated content (UGC) such as reviews, and provided information such as facets and product information.
[0026] In this embodiment, the association of information X with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not limited. Information X and information Y may be linked, may exist in the same buffer, may information X be contained in information Y, or information Y may be contained in information X, and so on.
[0027] Figure 1 is a conceptual diagram of information system A in this embodiment. Information system A comprises a page generation device 1, one or more terminal devices 2, and one or more websites 3.
[0028] Page generator 1 is a device that creates and stores one or more web pages. Page generator 1 is typically a so-called server. Page generator 1 may be a cloud server or an ASP server, but the type is not limited. Page generator 1 may also operate as a standalone device.
[0029] Terminal device 2 is a terminal used by the user. Terminal device 2 is, for example, a device for searching and retrieving web pages stored by page generation device 1. Terminal device 2 is, for example, a device for inputting reviews for product information sold on website 3. Terminal device 2 is, for example, a terminal for faceted search using the facets of website 3. Terminal device 2 is, for example, a terminal for searching web pages created by page generation device 1.
[0030] Terminal device 2 can be a personal computer, smartphone, or tablet device, but the type is not limited.
[0031] Website 3 could be, for example, an e-commerce site selling products, but it could also be a website for a company or organization, regardless of its type. Website 3 could also be, for example, a cloud server or an ASP server, regardless of its type. Products are usually items that can be transferred or leased. Products are, for example, items for sale or advertising. The term "product" here can also include services and is interpreted broadly. Products can also include, for example, companies or organizations that want to improve their image.
[0032] Figure 2 is a block diagram of information system A in this embodiment. Figure 3 is a block diagram of page generation device 1.
[0033] The page generation device 1 comprises a storage unit 11, a receiving unit 12, a processing unit 13, and an output unit 14. The processing unit 13 comprises a tag acquisition unit 131, a collection acquisition unit 132, a page configuration unit 133, an address acquisition unit 134, and a storage unit 135.
[0034] The terminal device 2 includes a terminal storage unit 21, a terminal receiving unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal receiving unit 25, and a terminal output unit 26.
[0035] The storage unit 11, which constitutes the page generation device 1, stores various types of information. These types of information include, for example, one or more web pages, information on one or more websites, tag source information, and UGC (User Generated Content).
[0036] Website information refers to information about a website. For example, website information could be the address information for website 3. Address information is the information needed to access website 3 or a webpage. For example, address information could be a URL or URI.
[0037] Tag source information refers to the information from which tags are obtained. Examples of tag source information include user-generated content (UGC) and user-generated content.
[0038] User-generated content (UGC) refers to content created by users, such as word-of-mouth or similar information. Word-of-mouth can also be called reviews or user reviews; the terminology is not restricted. Word-of-mouth can also be written as "reviews" or "user comments," and the notation is not restricted. The data in word-of-mouth is typically text, but may also include scores or other metrics.
[0039] The information provided refers to the information provided by the operators (or providers) of website 3. Examples of this information include facets and product information.
[0040] A facet is an interface provided on Website 3, used for searching for information on Website 3. A facet is, for example, a set of one or more terms. A facet is, for example, one or more search criteria. A facet is the information used in so-called faceted searches. A facet constitutes, for example, a menu for searching. Search criteria typically include a set of one or more terms.
[0041] Product information refers to information about a product. This includes, for example, product images, product descriptions, product names, and type information that identifies the type of product.
[0042] The reception unit 12 receives various instructions and information. These instructions and information include, for example, UGC, start instructions, access instructions, URIs, and URLs.
[0043] A start instruction is an instruction to begin the process of generating a web page. A start instruction may consist only of instructions to begin creating the web page, or it may include search criteria. Search criteria may include, for example, conditions for searching for product information corresponding to product-related information included in the web page being created. These search criteria may include, for example, type information.
[0044] An access instruction is an instruction for accessing a web page. An access instruction includes, for example, a URL.
[0045] Here, "reception" typically refers to the reception of information transmitted via wired or wireless communication lines, but it may also be a concept that includes the reception of information input from input devices such as keyboards, mice, and touch panels, as well as the reception of information read from recording media such as optical discs, magnetic discs, and semiconductor memory.
[0046] The processing unit 13 performs various processes. These various processes include, for example, the processes performed by the tag acquisition unit 131, the collection acquisition unit 132, the page composition unit 133, the address acquisition unit 134, and the storage unit 135.
[0047] The processing unit 13 obtains the web page corresponding to the access instruction received by the reception unit 12.
[0048] The tag acquisition unit 131 acquires one or more tags using tag source information corresponding to one or more product information items on the website 3. It is preferable for the tag acquisition unit 131 to acquire tags in association with product information.
[0049] Tags are, for example, the information that forms the basis of a hashtag. Tags are, for example, the string of characters in a hashtag without the "#". Tags are, for example, words.
[0050] The tag acquisition unit 131 preferably acquires one or more tags from tag source information corresponding to one or more product information on each of two or more websites 3.
[0051] The following describes how the tag acquisition unit 131 acquires tags from customer reviews (an example of tag source information), from facets (an example of tag source information), and from product information (an example of tag source information). It is preferable for the tag acquisition unit 131 to acquire tags from two or more types of tag source information among customer reviews, facets, and product information. (1) When obtaining tags from reviews
[0052] The tag acquisition unit 131 acquires, for example, one or more tags from reviews on one or more websites 3. The tag acquisition unit 131 acquires, for example, one or more tags from reviews associated with product information on website 3. The tag acquisition unit 131 acquires, for example, one or more words contained in reviews on one or more websites 3 as tags.
[0053] Furthermore, it is preferable that the words acquired by the tag acquisition unit 131 are of a specific part of speech. A specific part of speech is, for example, a noun or an adjective.
[0054] The tag acquisition unit 131, for example, performs morphological analysis on the reviews, obtains one or more morphemes, and then obtains one or more specific morphemes from those morphemes as tags. The tag acquisition unit 131 preferably obtains characteristic words from among one or more words in the reviews. Characteristic words are words that have characteristics related to the product information corresponding to the reviews. Characteristic words can be said to be words that represent the characteristics of the product corresponding to the reviews. The tag acquisition unit 131, for example, performs morphological analysis on the reviews, obtains one or more morphemes, and then obtains specific morphemes from those morphemes that have an importance equal to or greater than a threshold as tags. The importance is, for example, the tf-idf value, but other indicators such as Okapi BM25 may also be used.
[0055] It is preferable that the tags acquired by the tag acquisition unit 131 from customer reviews are associated with one or more product information items corresponding to those customer reviews. (2) When obtaining tags from facets
[0056] The tag acquisition unit 131 acquires, for example, one or more terms that constitute a facet of one or more websites 3.
[0057] It is preferable that the tags acquired by the tag acquisition unit 131 from the facets are associated with one or more product information items that are searched based on the conditions that gave rise to the tags. (3) When obtaining tags from product information
[0058] The tag acquisition unit 131 acquires tags, for example, from the product information of one or more products on one or more websites 3.
[0059] The tag acquisition unit 131 acquires, for example, one or more words that constitute the descriptive information included in the product information as tags. The descriptive information is a string of characters that describes the product. The descriptive information may also include product type information, product specifications, etc.
[0060] The tag acquisition unit 131, for example, performs morphological analysis on the descriptive information contained in the product information, obtains one or more morphemes, and acquires one or more specific morphemes from those one or more morphemes as tags. The tag acquisition unit 131 preferably acquires a characteristic word from among one or more words in the descriptive information. A characteristic word is a word that has characteristics related to the product information. A characteristic word can be said to be a word that represents the characteristics of the product corresponding to the descriptive information. The tag acquisition unit 131, for example, performs morphological analysis on the descriptive information, obtains one or more morphemes, and acquires a specific morpheme from those one or more morphemes that has an importance equal to or greater than a threshold as a tag.
[0061] The tag acquisition unit 131 performs image recognition processing on product images included in product information, obtains one or more recognition results, and acquires each of these one or more recognition results as a tag. The recognition results may be, for example, product type information or one or more attribute values of the product (for example, color, shape, etc.).
[0062] Performing image recognition processing on a product image to obtain the product name, product type, and one or more attribute values of the product within the image is possible using known image processing techniques, so a detailed explanation will be omitted. The tag acquisition unit 131, for example, performs machine learning prediction processing on a product image using a learning model to obtain the product name or product type within the image. The learning model is data obtained by performing machine learning training processing using two or more training data sets having an image and a product name or product type. The learning model may also be called a learner, prediction model, or predictor. The machine learning algorithm can be deep learning, random forest, decision tree, etc. Furthermore, various machine learning functions such as the TensorFlow library and the R language's random forest module, as well as various existing libraries, can be used for machine learning.
[0063] The set acquisition unit 132 acquires one or more tag sets, which are combinations of one or more tags, from the one or more tags acquired by the tag acquisition unit 131.
[0064] If the three tags acquired by the tag acquisition unit 131 are "word A, word B, word C", the set acquisition unit 132 will acquire, for example, the tag sets "word A, word B", "word A, word C", "word B, word C", and "word A, word B, word C". The tag acquisition unit 131 may also acquire a single tag, "word A", "word B", and "word C". A single tag can also be called a tag set.
[0065] The page structure section 133 is a web page in which each of the one or more tag sets acquired by the set acquisition section 132 is a hashtag, and it contains information corresponding to each of the one or more tags, and thus constitutes a web page containing product-related information. Note that hashtags may be replaced with search terms. In other words, hashtags can be broadly understood as information used for searching web pages.
[0066] The page structuring unit 133 preferably constructs a web page for each tag set acquired by the set acquisition unit 132. However, the page structuring unit 133 may also construct a web page corresponding to only one or more tag sets from the tag sets acquired by the set acquisition unit 132 that meet specific conditions. Specific conditions include, for example, conditions regarding the number of tags in a tag set, and conditions regarding the co-occurrence of tags within a tag set. Conditions regarding tag co-occurrence include, for example, that two or more tags in a tag set co-occur in reviews, that the proportion or number of two or more tags in a tag set co-occurring in reviews is above or above a threshold, that two or more tags in a tag set co-occur in reviews and product information, and that the proportion or number of two or more tags in a tag set co-occurring in reviews and product information is above or above a threshold.
[0067] Product-related information refers to information related to a product. Examples of product-related information include product images, product descriptions, links to product information, and hashtags that link to product information. Links to product information are typically links to specific web pages on websites where the product information is posted. For example, links to product information might be links to pages where the product can be purchased.
[0068] It is preferable that the product-related information within the configured web pages corresponds to anchors, and that, according to the instructions in the product-related information, users jump to website 3 containing the product information.
[0069] The address acquisition unit 134 acquires address information for storing web pages constructed by the page construction unit 133. Address information is information for accessing web pages. Address information includes, for example, URLs, URIs, and file names.
[0070] The address acquisition unit 134 generates, for example, unique address information. The address acquisition unit 134 acquires unused address information from, for example, a database (not shown) that stores two or more pieces of address information.
[0071] The storage unit 135 stores the web pages constructed by the page construction unit 133. Typically, the storage unit 135 stores the web pages constructed by the page construction unit 133 in relation to the address information acquired by the address acquisition unit 134.
[0072] The output unit 14 outputs various types of information. These types of information include, for example, information indicating that a web page has been created and stored, the address information of the stored web page, and the web page acquired by the processing unit 13.
[0073] Here, output usually refers to transmission to an external device (e.g., terminal device 2, administrator device not shown), but it may also be a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, storage on a recording medium, and transfer of processing results to other processing devices or other programs.
[0074] The terminal storage unit 21, which constitutes the terminal device 2, stores various types of information. These types of information include, for example, a user identifier.
[0075] The terminal reception unit 22 receives various types of information and instructions. These types of information and instructions include, for example, start instructions and access instructions.
[0076] Here, "reception" is a concept that includes receiving information input from input devices such as keyboards, mice, and touch panels; receiving information transmitted via wired or wireless communication lines; and receiving information read from recording media such as optical discs, magnetic discs, and semiconductor memory.
[0077] The means of inputting various information and instructions can be anything, such as a touch panel, keyboard, mouse, or menu screen.
[0078] The terminal processing unit 23 performs various processes. These processes include, for example, converting received information and instructions into information and instructions to be transmitted. Other processes include, for example, converting received information into output information.
[0079] The terminal transmission unit 24 transmits various information and instructions to the page generation device 1. These various information and instructions include, for example, a start instruction.
[0080] The terminal receiving unit 25 receives various types of information from the page generation device 1. These types of information include, for example, the web page corresponding to the access instruction, the created web page, and access information for the created web page.
[0081] The terminal output unit 26 outputs various types of information. These types of information include, for example, web pages and access information for created web pages.
[0082] Here, "output" is a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, transmission to an external device, storage on a recording medium, and transfer of processing results to other processing devices or other programs.
[0083] The storage unit 11 and the terminal storage unit 21 are preferably made of non-volatile recording media, but can also be made of volatile recording media.
[0084] The process by which information is stored in the storage unit 11, etc. is not relevant. For example, information may be stored in the storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 11, etc., or information input via an input device may be stored in the storage unit 11, etc.
[0085] The reception unit 12 and the terminal receiving unit 25 are usually implemented by wireless or wired communication means, but they may also be implemented by means of receiving broadcasts.
[0086] The reception unit 12 may also be implemented using device drivers for input means such as touch panels or keyboards, or control software for menu screens.
[0087] The processing unit 13, tag acquisition unit 131, set acquisition unit 132, page configuration unit 133, address acquisition unit 134, storage unit 135, and terminal processing unit 23 can typically be implemented using a processor, memory, etc. The processing procedures of the processing unit 13, etc., are usually implemented in software, and this software is recorded on a recording medium such as ROM. However, it may also be implemented in hardware (dedicated circuitry). The processor can be a CPU, MPU, GPU, etc., and the type is not limited.
[0088] The output unit 14 and the terminal transmission unit 24 are usually implemented by wireless or wired communication means, but may also be implemented by broadcasting means.
[0089] The output unit 14 may be implemented using driver software for an output device, or by using driver software for an output device and an output device, etc.
[0090] The terminal reception unit 22 can be implemented using device drivers for input means such as touch panels and keyboards, or control software for menu screens, etc.
[0091] The terminal output unit 26 may or may not be considered to include output devices such as a display or speakers. The terminal output unit 26 can be implemented using driver software for an output device, or a driver software for an output device and an output device.
[0092] Next, we will explain an example of the operation of information system A. First, we will explain an example of the operation of page generation device 1 using the flowchart in Figure 4.
[0093] (Step S401) The reception unit 12 determines whether or not it has received a start instruction. If it has received a start instruction, it proceeds to step S402; otherwise, it proceeds to step S410.
[0094] The reception unit 12 receives a start command from, for example, the terminal device 2. However, the reception unit 12 may also automatically receive the start command at a predetermined time.
[0095] (Step S402) The tag acquisition unit 131 performs the tag acquisition process. An example of the tag acquisition process will be explained using the flowcharts in Figures 5 and 6.
[0096] (Step S403) The set acquisition unit 132 performs tag set acquisition processing. An example of tag set acquisition processing will be explained using the flowchart in Figure 7.
[0097] (Step S404) The page component 133 assigns 1 to counter i.
[0098] (Step S405) The page composition unit 133 determines whether or not the i-th tag set exists among the tag sets obtained in step S403. If the i-th tag set exists, the process proceeds to step S406; otherwise, the process returns to step S401.
[0099] (Step S406) The page composition unit 133 performs page composition processing. An example of page composition processing will be explained using the flowchart in Figure 8.
[0100] (Step S407) The address acquisition unit 134 acquires unique address information (e.g., a URL) that identifies the location where the web pages will be stored.
[0101] (Step S408) The storage unit 135 stores the web page configured in step S406 at the location indicated by the address information obtained in step S407.
[0102] The output unit 14 may also send such address information to, for example, an administrator. Sending to an administrator means, for example, sending it to the administrator's email address or to the administrator's terminal device 2. An administrator is, for example, the person who sent the start command, the administrator of website 3, or the administrator of page generation device 1.
[0103] (Step S409) The page component 133 increments counter i by 1. Return to step S405.
[0104] (Step S410) The reception unit 12 determines whether or not it has received an access instruction. If an access instruction has been received, it proceeds to step S411; otherwise, it returns to step S401.
[0105] (Step S411) The processing unit 13 obtains the web page corresponding to the access instruction.
[0106] (Step S412) The output unit 14 sends the web page obtained in step S411 to the terminal device 2 that sent the access instruction. Return to step S401.
[0107] In the flowchart shown in Figure 4, processing is terminated by power-off or processing termination interrupts.
[0108] Next, we will explain the first example of the tag acquisition process in step S402 using the flowchart in Figure 5.
[0109] (Step S501) The tag acquisition unit 131 assigns 1 to counter i.
[0110] (Step S502) The tag acquisition unit 131 determines whether the i-th website 3, which is the source of the tag information, exists. If the i-th website 3 exists, the process proceeds to step S503; otherwise, it returns to the higher-level process.
[0111] The source of the tag information is usually predetermined for each website 3. The address information for accessing the i-th website 3 is stored in the storage unit 11.
[0112] (Step S503) The tag acquisition unit 131 acquires one or more web pages from the i-th website 3.
[0113] (Step S504) The tag acquisition unit 131 assigns 1 to counter j.
[0114] (Step S505) The tag acquisition unit 131 determines whether the j-th product information exists in the one or more web pages acquired in step S503. If the j-th product information exists, the unit proceeds to step S506; otherwise, it proceeds to step S512.
[0115] (Step S506) The tag acquisition unit 131 assigns 1 to the counter k.
[0116] (Step S507) The tag acquisition unit 131 determines whether or not there is a k-th UGC (e.g., a review) corresponding to the j-th product information of the i-th website 3. If a k-th UGC exists, the unit proceeds to step S508; otherwise, it proceeds to step S510.
[0117] (Step S508) The tag acquisition unit 131 acquires the k-th UGC corresponding to the j-th product information of the i-th website 3. Next, the tag acquisition unit 131 acquires one or more terms from the UGC. Next, the tag acquisition unit 131 stores the acquired one or more terms in association with the i-th website 3 and the j-th product information. The tag acquisition unit 131 also associates the acquired one or more terms with the k-th UGC, for example. The tag acquisition unit 131 stores the acquired one or more terms in a buffer (not shown) in association with, for example, the site identifier of the i-th website, the product identifier of the j-th product information, and the identifier of the k-th UGC.
[0118] (Step S509) The tag acquisition unit 131 increments the counter k by 1. Return to step S507.
[0119] (Step S510) The tag acquisition unit 131 acquires one or more terms from the j-th product information (e.g., product description information, product image) of the i-th website 3. Next, the tag acquisition unit 131 stores the acquired one or more terms in association with the i-th website 3 and the j-th product information.
[0120] (Step S511) The tag acquisition unit 131 increments the counter j by 1. Return to step S505.
[0121] (Step S512) The tag acquisition unit 131 acquires the facets of the i-th website 3.
[0122] (Step S513) The tag acquisition unit 131 assigns 1 to counter l.
[0123] (Step S514) The tag acquisition unit 131 determines whether the l-th term exists among the facets acquired in step S512. If the l-th term exists, the unit proceeds to step S515; otherwise, it proceeds to step S518.
[0124] (Step S515) The tag acquisition unit 131 acquires the product identifier for each of the one or more product information items searched for using the l-th term.
[0125] (Step S516) The tag acquisition unit 131 associates the l-th term with the product identifier acquired in step S515 and the i-th website 3, and stores it in a buffer (not shown).
[0126] (Step S517) The tag acquisition unit 131 increments the counter l by 1. Return to step S514.
[0127] (Step S518) The tag acquisition unit 131 increments the counter i by 1. Return to step S502.
[0128] In the flowchart in Figure 5, tags were obtained from UGC, product information, and facets. However, in the flowchart in Figure 5, tags may be obtained from only one or two of the following types of information: UGC, product information, and facets.
[0129] Furthermore, in the flowchart of Figure 5, the tag acquisition unit 131 may acquire a set of two or more terms within a facet, associate the product identifier of one or more product information retrieved using the AND condition of the set of two or more terms with the set of two or more terms, and store them in a buffer (not shown).
[0130] Next, a second example of the tag acquisition process in step S402 will be explained using the flowchart in Figure 6. In the flowchart in Figure 6, the explanation of the steps that are the same as those in the flowchart in Figure 5 will be omitted.
[0131] (Step S601) The tag acquisition unit 131 acquires the search conditions from the received start instruction.
[0132] (Step S602) The tag acquisition unit 131 acquires one or more tags that constitute the search conditions.
[0133] (Step S603) The tag acquisition unit 131 searches for product information, etc., on the i-th website using the search criteria. Product information, etc., usually consists of product information and customer reviews.
[0134] Next, an example of the tag set acquisition process in step S403 will be explained using the flowchart in Figure 7.
[0135] (Step S701) The set acquisition unit 132 sorts the acquired tag-site identifier-product identifier pairs using the tag as the key and performs a unique operation on the tags. However, the set acquisition unit 132 does not perform a unique operation on the site identifier-product identifier pairs. As a result, it is possible that one tag may correspond to two or more site identifier-product identifier pairs.
[0136] (Step S702) The set acquisition unit 132 assigns 1 to counter i. Note that counter i may start from 2. In this case, the tag set will be a set of 2 or more tags.
[0137] (Step S703) The set acquisition unit 132 determines whether or not to create a web page for the combination of i hashtags. If a web page for the combination of i hashtags is to be created, the process proceeds to step S704; otherwise, it returns to the higher-level process.
[0138] Let's assume, for example, that the number of hashtag combinations to be created is predetermined.
[0139] (Step S704) The set acquisition unit 132 assigns 1 to counter j.
[0140] (Step S705) The set acquisition unit 132 determines whether the j-th combination of i tags can be obtained from the set of tags obtained in step S402. If the j-th combination of i tags can be obtained, the unit proceeds to step S706; otherwise, the unit proceeds to step S710.
[0141] (Step S706) The set acquisition unit 132 acquires the j-th combination of i tags from the set of tags acquired in step S402.
[0142] (Step S707) The set acquisition unit 132 acquires one or more pairs of product identifiers and site identifiers corresponding to the j-th combination of i tags.
[0143] Furthermore, the pair of product identifiers and site identifiers corresponding to the j-th combination of i tags may be any pair of product identifiers and site identifiers corresponding to all tags included in the j-th combination of i tags, any pair of product identifiers and site identifiers corresponding to one tag included in the j-th combination of i tags, or any pair of product identifiers and site identifiers corresponding to a number or proportion of tags among the j-th combination of i tags that are equal to or greater than a threshold.
[0144] (Step S708) The set acquisition unit 132 associates the j-th combination of i tags with the one or more sets of product identifiers and site identifiers acquired in step S707 and stores it in a buffer (not shown).
[0145] (Step S709) The set acquisition unit 132 increments counter j by 1. Return to step S705.
[0146] (Step S710) The set acquisition unit 132 increments counter i by 1. Return to step S703.
[0147] Next, an example of the page composition process in step S406 will be explained using the flowchart in Figure 8.
[0148] (Step S801) The page constructor 133 obtains the set of tags of interest from a buffer (not shown). The set of tags of interest is the i-th set of tags in S405.
[0149] (Step S802) The page composition unit 133 obtains one or more hashtags using one or more tags from the tag set obtained in step S801, and places the one or more hashtags on the web page to be created.
[0150] (Step S803) The page component 133 assigns 1 to counter i.
[0151] (Step S804) The page constructor 133 determines whether or not there is an i-th product identifier that is paired with the set of tags of interest. If an i-th product identifier exists, the process proceeds to step S805; otherwise, it returns to the higher-level process.
[0152] (Step S805) The page constructor 133 obtains the i-th product identifier that is paired with the tag set of interest, and the site identifier that is paired with the i-th product identifier.
[0153] (Step S806) The page structuring unit 133 retrieves product-related information related to the product identified by the i-th product identifier within the website 3 identified by the site identifier obtained in step S805. The page structuring unit 133 places the retrieved product-related information on the web page.
[0154] (Step S807) The page component 133 increments counter i by 1. Return to step S804.
[0155] The following describes specific operational examples of information system A in this embodiment. Three specific examples are described below. Specific example 1 describes a case where one or more hashtags are obtained from product description information and user reviews (word-of-mouth) of products corresponding to the product information from one or more e-commerce sites (website 3), and a web page is generated and stored that is accessed using the one or more hashtags, and that allows easy access to one or more product information pages. Specific example 2 describes a case where hashtags are obtained from product information of a type specified by search conditions and terms obtained from reviews, and a web page is generated and stored that uses two or more hashtags. Specific example 3 describes a case where hashtags are obtained using facets, and a web page is generated and stored that uses those hashtags.
[0156] (Specific example 1) The reception unit 12 of the page generation device 1 assumes that it has received a start instruction from the terminal device 2.
[0157] Next, the tag acquisition unit 131 acquires web pages from one or more e-commerce sites (websites 3) that sell clothing, bags, etc., and each website 3 contains information on multiple products.
[0158] Next, the tag acquisition unit 131 performs morphological analysis on the descriptive information 902 in the product information (for example, 901 in Figure 9) and acquires terms that are specific parts of speech such as nouns or sets of two or more terms (for example, "short length", "casual", "coordinate", "simple").
[0159] Next, the tag acquisition unit 131 performs morphological analysis on the review 903 associated with the product information and acquires terms that are specific parts of speech such as nouns, or sets of two or more terms (for example, "during commuting," "style," "doesn't cause shoulder pain," "various scenes").
[0160] Next, the tag acquisition unit 131 acquires hashtags (for example, "#shortlength", "#casual", "#coordinate", "#simple", "#commuting", "#style", "#shoulderspainfree", "#variousscenes") from each acquired term or term set (904 in Figure 9).
[0161] Next, the tag acquisition unit 131 temporarily stores the acquired hashtags, associating them with the source tag information, which consists of product information and reviews, from which the hashtags were acquired.
[0162] Next, the set acquisition unit 132 constructs a set of one or more tags which is a set of one or more acquired hashtags (for example, "#shortlength,#casual", "#shortlength,#coordinate", "#shortlength,#simple", "#shortlength,#commuting", "#shortlength,#style", "#shortlength,#doesnothurttheshoulders", "#shortlength,#variousscenes", ..., "#shortlength,#casual,#coordinate,#simple,#commuting,#style,#doesnothurttheshoulders", ..., "#shortlength,#casual,#coordinate,#simple,#commuting,#style,#doesnothurttheshoulders,#variousscenes").
[0163] Next, the page structure unit 133 constitutes a web page corresponding to each of the two or more tag sets. Such a web page has a tag set and, for example, product information 905 and product information 906. Note that each of the two or more tag sets corresponding to a web page may also have a review 903.
[0164] Next, the address acquisition unit 134 acquires unique address information (in this case, a URL) for each of the two or more tag sets, which identifies the destination where the web pages will be stored.
[0165] Next, the storage unit 135 stores the web pages for each of the two or more tag sets at the location indicated by the acquired address information.
[0166] Based on the above, we were able to generate one or more web pages that allow easy access to product information 901.
[0167] (Specific example 2) The reception unit 12 of the page generation device 1 receives a start command from the terminal device 2 that includes the search condition "One Piece".
[0168] Next, the tag acquisition unit 131 acquires one or more web pages from each of the predetermined e-commerce sites (websites 3) that contain information on multiple products.
[0169] Next, the tag acquisition unit 131 retrieves product information and reviews that match the search condition "One Piece" from the one or more web pages it has acquired. Then, the tag acquisition unit 131 performs morphological analysis on the acquired reviews and retrieves terms of specific parts of speech (in this case, nouns) such as "private," "wedding," "date," and "business."
[0170] Next, the set acquisition unit 132 acquires one or more tag sets, which are sets of one or more hashtags corresponding to the term "One Piece" included in the search conditions and one or more terms obtained from the reviews (for example, "private," "wedding," "date," "business").
[0171] Next, the page structure unit 133 retrieves product information for each of the one or more tag sets that matches the search condition "One Piece" and corresponds to the review that was the source of the hashtag. The page structure unit 133 also retrieves at least one review that is paired with the retrieved product information.
[0172] Next, the page configuration unit 133 constructs a web page for each of the one or more tag sets that includes the acquired one or more product information and the reviews associated with that product information.
[0173] Next, the address acquisition unit 134 acquires unique address information (in this case, a URL) for each of the two or more tag sets, which identifies the destination where the web pages will be stored.
[0174] Next, the storage unit 135 stores the web pages for each of the two or more tag sets at the location indicated by the acquired address information.
[0175] Based on the above, we were able to generate one or more web pages that allow easy access to product information 801.
[0176] Next, let's assume the user enters an access instruction into terminal device 2 that includes "wedding" and "dress" in order to purchase a dress to wear to a wedding.
[0177] Next, terminal device 2 receives the access instruction "wedding, dress" and transmits the access instruction to page generation device 1.
[0178] Next, the reception unit 12 of the page generation device 1 receives the access instruction "wedding, dress". Next, the processing unit 13 retrieves the web page that was matched by the access instruction "wedding, dress". Next, the output unit 14 sends the retrieved web page to the terminal device 2 that sent the access instruction.
[0179] Next, terminal device 2 receives and outputs the web page. An example of such output is shown in Figure 10.
[0180] Next, suppose the user directs the user to product information 1001 on the screen shown in Figure 10. The terminal device 2 then retrieves and outputs the webpage to which product information 1001 is linked. An example of such output is shown in Figure 11. The product information in Figure 11 is, for example, product information included in one or more predetermined e-commerce sites (website 3).
[0181] (Specific example 3) Let's assume there is a restaurant website 3 with the facets shown in Figure 12. Here, the "product" is the service of providing food at the restaurant. The facets include prefecture and type of cuisine. In other words, on this website 3, users can specify the prefecture and type of cuisine to obtain information about the restaurant's products.
[0182] The page generator 1 generates and stores one or more web pages in the following manner, so that the restaurant information on the website 3 is easily searchable.
[0183] First, the tag acquisition unit 131 performs the tag acquisition process from the facet as follows: In other words, the tag acquisition unit 131 acquires the terms that constitute the facet from the facet in Figure 11: "Hokkaido, Aomori Prefecture, ...Fukushima Prefecture, ...Western food, French cuisine, Italian cuisine, ...Japanese food, Kaiseki / Kaiseki cuisine, Kappo / Small dishes, ...Sushi, ...".
[0184] Here, the tag acquisition unit 131 acquires terms for each type of term that constitutes a facet (in this case, prefecture and type of cuisine).
[0185] Next, the tag acquisition unit 131 acquires hashtags such as "#Hokkaido, #Aomori Prefecture, ... #Fukushima Prefecture, ..." and "#Western food, #French cuisine, #Italian cuisine, ... #Japanese food, #Kaiseki cuisine, #Kappo cuisine, ... #Sushi, ..." from the acquired terms, for each type of term.
[0186] Next, the set acquisition unit 132 performs the tag set acquisition process as follows: The set acquisition unit 132 acquires a tag set consisting of one hashtag "Hokkaido", "Aomori Prefecture", "Western food", "French cuisine", "Sushi", etc., and for each type of term, it acquires two hashtags such as "#Hokkaido,#Western food", "#Hokkaido,#French cuisine", "#Aomori Prefecture,#Western food", "#Fukushima Prefecture,#Sushi", etc.
[0187] Next, the page composition unit 133 retrieves product information (in this case, restaurant information) that can be searched using the terms that constitute the hashtags in each acquired tag set.
[0188] Next, the page composition unit 133 places the tag set and product-related information, which is the acquired one or more product information or information for accessing each of the acquired one or more product information (for example, anchor information), on the web page for each acquired tag set.
[0189] Next, the address acquisition unit 134 acquires unique address information (in this case, a URL) for each of the two or more configured web pages, which identifies the location where the web page will be stored.
[0190] Next, the storage unit 135 stores the web pages for each acquired tag set at the location indicated by the acquired URL.
[0191] In the above specific examples, it is preferable to obtain tags from two or three types of tag source information, such as reviews, product information, and facets, and then use those tags to construct and store web pages.
[0192] In summary, this embodiment makes it possible to create a webpage that allows easy access to product information. This constitutes a form of SEO (Search Engine Optimization).
[0193] Furthermore, according to this embodiment, it is possible to create a web page that allows easy access to product information from one or more websites 3.
[0194] Furthermore, according to this embodiment, it is possible to create a web page that allows easy access to product information using UGC (User-Generated Content) or hashtags obtained from provided information for website 3.
[0195] The processing in this embodiment may be implemented by software. This software may be distributed by software download or the like. Alternatively, this software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that implements the page generation device 1 in this embodiment is the following program. In other words, this program causes a computer to function as a tag acquisition unit that acquires one or more tags using tag source information corresponding to one or more product information in a website containing one or more product information; a set acquisition unit that acquires one or more tag sets, which are combinations of one or more tags, from the one or more tags acquired by the tag acquisition unit; a page configuration unit that configures a web page for each of the one or more tag sets acquired by the set acquisition unit, where each of the one or more tags in the tag set is a hashtag, and the web page contains product-related information that corresponds to each of the one or more tags and relates to a product; an address acquisition unit that acquires address information for storing the web pages configured by the page configuration unit; and a storage unit that stores the web pages configured by the page configuration unit for the address information acquired by the address acquisition unit.
[0196] (Embodiment 2) In this embodiment, in a situation where advertising information corresponding to one or more hashtags and two or more product information corresponding to one or more hashtags are managed, when a user selects a hashtag on a page, an information processing device is described that constructs and outputs a new page using the advertising information corresponding to the hashtag and the product information to which the hashtag is attached. The hashtag is, for example, information automatically obtained from the tag source information (reviews, etc.) mentioned above. It is also preferable that the hashtag is a phrase containing two or more words. The page is usually a web page, but it may also be an app screen, window, etc. The page can also be broadly interpreted as any information that is displayed.
[0197] This embodiment describes an information processing device that manages advertising fees corresponding to hashtags and bills advertisers for these advertising fees.
[0198] In this embodiment, we will describe a server that recruits advertisers and accepts advertising applications for each of the one or more hashtags obtained from the tag source information.
[0199] In this embodiment, we will describe a server that automatically associates advertisers with one or more hashtags obtained from the tag source information.
[0200] In this embodiment, advertising fees corresponding to hashtags are managed, and a server that bills advertisers for these advertising fees will be described.
[0201] In this specification, selecting or determining information Z means obtaining information Z, obtaining a pointer to information Z, obtaining the ID of information Z, setting a flag on information Z, etc., and it is sufficient to be able to access information Z.
[0202] Figure 13 is a conceptual diagram of information system B in this embodiment. Information system B comprises an information processing device 4, a server 5, and one or more terminal devices 6.
[0203] The information processing device 4 is typically a device that receives a hashtag selection from the terminal device 6, constructs a page containing product information and advertising information associated with the hashtag, and transmits it to the terminal device 6. The information processing device 4 is typically a so-called server. The information processing device 4 may be, for example, a cloud server or an ASP server, but the type is not limited. The information processing device 4 may also be a terminal. If the information processing device 4 is a terminal, it may be a so-called personal computer, smartphone, or tablet device, but the type is not limited.
[0204] Server 5 is the server that determines advertisers for each of the one or more hashtags obtained from the tag source information. The process of determining advertisers can be done manually or automatically. Manual processing involves soliciting advertisers for hashtags, receiving applications from advertisers, and managing them. Server 5 can be, for example, a cloud server or an ASP server, but the type is not limited.
[0205] Terminal device 6 is a device used by a user. For example, terminal device 6 is a device used by a user who specifies hashtags on a page or by an advertiser who submits a request for a hashtag. Terminal device 2 is a so-called personal computer, smartphone, or tablet device, but the type is not limited.
[0206] The information processing device 4 and one or more terminal devices 6, and the server 5 and one or more terminal devices 6 can communicate with each other via a network such as the Internet.
[0207] Figure 14 is a block diagram of information system B in this embodiment. Figure 15 is a block diagram of information processing device 4.
[0208] The information processing device 4 comprises a storage unit 41, a reception unit 42, a processing unit 43, and an output unit 44. The storage unit 41 comprises a page storage unit 411, a product management unit 412, and an advertising management unit 413. The reception unit 42 comprises a selection reception unit 421. The processing unit 43 comprises a tag acquisition unit 431, an advertising information acquisition unit 432, a product information acquisition unit 433, a page configuration unit 434, and a billing processing unit 435. The output unit 44 comprises a page output unit 441.
[0209] Server 5 comprises a server storage unit 51, a server receiving unit 52, a server processing unit 53, and a server transmission unit 54. Server storage unit 51 comprises a hashtag management unit 511 and an advertiser management unit 512. Server receiving unit 52 comprises an application receiving unit 521. Server processing unit 53 comprises an advertising fee determination unit 530, an advertiser recruitment unit 531, a response unit 532, an advertiser information storage unit 533, and a billing processing unit 534. Note that the information processing device 4 and server 5 may be a single device.
[0210] The terminal device 6 includes a terminal storage unit 61, a terminal receiving unit 62, a terminal processing unit 63, a terminal transmission unit 64, a terminal receiving unit 65, and a terminal output unit 66.
[0211] The storage unit 41, which constitutes the information processing device 4, stores various types of information. These types of information include, for example, one or more pages, website information, product information (described later), advertising information (described later), and hashtags.
[0212] The page storage unit 411 stores one or more pages. The pages in the page storage unit 411 are, for example, one or more web pages received from one or more websites 3.
[0213] The product management unit 412 stores information on two or more products. Each of the two or more product information entries is associated with one or more hashtags. Preferably, each of the two or more product information entries is product information contained in a page of the storage unit 41 or a page obtained using the website information of the storage unit 41.
[0214] Hashtags are preferably phrases or sentences containing two or more words. However, hashtags can also be single words. Examples of hashtags include "#goodtotouch" and "#gentleontheskin".
[0215] The advertising management unit 413 stores one or more advertising information. Each of the one or more advertising information items is associated with one or more hashtags.
[0216] It is preferable that the advertising management unit 413 stores one or more pieces of advertising information and advertising fee information, associated with one or more hashtags.
[0217] Advertising information refers to information about an advertisement. Advertising information can include, for example, the advertisement itself. It can also include, for example, still images, videos, text, audio, or a combination thereof, regardless of its data type. Advertising information can be associated with, for example, an advertiser identifier. Advertising information can also be associated with, for example, one or more advertising attribute values. These attribute values can include, for example, advertising fee information, the data type of the advertisement (e.g., "still image," "video," "text," "audio"), the frequency of the advertisement (e.g., once per user per month), and the size of the advertisement. Advertising fee information refers to information that identifies the advertising fee.
[0218] The reception unit 42 receives various types of information and instructions. For example, the reception unit 42 receives various types of information and instructions from the terminal device 6. These types of information and instructions include, for example, instructions for creating a product management table and selecting hashtags.
[0219] The instruction to create a product management table is an instruction to create a product management table and store it in the product management department 412. A product management table is a table that manages one or more pairs of product information and hashtags.
[0220] The selection receiving unit 421 accepts hashtag selections. The selection receiving unit 421 receives hashtag selections from, for example, the terminal device 6. Note that the hashtag selection is, for example, the selection of one hashtag from one or more hashtags displayed on the page on the screen. The hashtag selection can be the hashtag itself, a link to the hashtag, the hashtag ID, etc. Any information that identifies the selected hashtag is acceptable for the hashtag selection.
[0221] The processing unit 43 performs various processes. These processes include, for example, those performed by the tag acquisition unit 431, the advertising information acquisition unit 432, the product information acquisition unit 433, the page composition unit 434, and the billing processing unit 435.
[0222] The tag acquisition unit 431 uses the tag source information stored in the page storage unit 411 to acquire one or more tags, adds "#" to each of the one or more tags, and acquires one or more hashtags with "#" added. It is preferable that the tag acquisition unit 431 performs the same processing as the tag acquisition unit 131. Tags are preferably phrases or sentences, but may also be words.
[0223] It is preferable that each of the one or more hashtags acquired by the tag acquisition unit 431 corresponds to product information on the page.
[0224] The processing unit 43 or storage unit (not shown) preferably stores in the product management unit 412 pairs of one or more hashtags acquired by the tag acquisition unit 431 with product information corresponding to the source information from which the hashtags were acquired. The pairs of one or more hashtags and product information in the product management unit 412 may be, for example, information accumulated manually. The product information corresponding to the source information preferably is product information on the page.
[0225] The advertising information acquisition unit 432 acquires one or more advertising information items from the advertising management unit 413 that are paired with hashtags corresponding to the selection received by the selection reception unit 421.
[0226] The product information acquisition unit 433 acquires one or more product information items from the product management unit 412 that are paired with hashtags corresponding to the selection received by the selection reception unit 421. It is preferable for the product information acquisition unit 433 to acquire two or more product information items from the product management unit 412 that are paired with hashtags corresponding to the selection received by the selection reception unit 421.
[0227] The page configuration unit 434 comprises a page containing hashtags corresponding to selections received by the selection reception unit 421, advertising information acquired by the advertising information acquisition unit 432, and product information acquired by the product information acquisition unit 433.
[0228] When the page output unit 441 outputs a page constructed by the page construction unit 434, the billing processing unit 435 performs billing processing to invoice the advertiser identified by the advertiser identifier paired with the hashtag used to construct the page for the advertising fee specified by the advertising fee information paired with the hashtag. For example, when the page output unit 441 transmits a page constructed by the page construction unit 434 to the terminal device 6, the billing processing unit 435 performs billing processing to invoice the advertiser identified by the advertiser identifier paired with the hashtag used to construct the page for the advertising fee specified by the advertising fee information paired with the hashtag.
[0229] The billing process includes, for example, the process of charging advertising fees identified by advertising fee information paired with a hashtag using the credit card number paired with the advertiser identifier, the process of charging advertising fees identified by advertising fee information paired with a hashtag using the bank account information paired with the advertiser identifier, and the process of counting up the number of times a hashtag has been used.
[0230] The output unit 44 outputs various types of information. These types of information include, for example, the pages constructed by the page composition unit 434.
[0231] Here, output usually refers to transmission to terminal device 2, but it may also be a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, transmission to external devices other than terminal device 2, storage on a recording medium, and delivery of processing results to other processing devices or other programs.
[0232] The page output unit 441 outputs the page constructed by the page composition unit 434. For example, the page output unit 441 transmits the page constructed by the page composition unit 434 to the terminal device 6. This terminal device 6 is the same terminal device 6 that transmitted the hashtag selection.
[0233] The server storage unit 51, which constitutes server 5, stores various types of information. These types of information include, for example, one or more hashtags, advertising fee information, and one or more advertiser information.
[0234] The hashtag management unit 511 stores one or more hashtags. Preferably, hashtags are information obtained by adding "#" to tags acquired from tag source information on the page. However, the hashtags in the hashtag management unit 511 may also be manually created hashtags. Preferably, the hashtag management unit 511 stores advertising fee information corresponding to one or more hashtags.
[0235] Advertising fee information refers to information that identifies the advertising fee for a hashtag. Advertising fee information is determined, for example, by the server operator. Advertising fee information is determined, for example, by the advertising fee determination unit 530 based on the hashtag. Advertising fee information is determined, for example, by the operator of the information processing device 4.
[0236] The advertiser management unit 512 stores one or more advertiser information. Advertiser information refers to information about an advertiser. Advertiser information is associated with an advertiser identifier. Advertiser information has one or more advertiser attribute values. Advertiser attribute values include, for example, advertising budget (e.g., "30,000 yen / month"), business genre or type of product handled (e.g., cosmetics, clothing), and account information. Account information refers to information about the account the advertiser uses to pay advertising fees.
[0237] The server receiving unit 52 receives various types of information and instructions from the terminal device 6. These types of information and instructions include, for example, application information, advertiser information, and instructions to submit the application page.
[0238] The application receiving unit 521 receives application information from the terminal device 6. For example, the application receiving unit 521 receives application information from the terminal device 6 in response to the transmission of recruitment screen information.
[0239] Recruitment screen information refers to the information on a screen that solicits the purchase of advertising space for a hashtag. Recruitment screen information includes one or more hashtags or tags that constitute a hashtag, targeting advertisers. While recruitment screen information can be written in HTML, XML, etc., the method of implementation is not restricted.
[0240] Application information refers to information indicating an application to purchase the rights to advertise a hashtag. Application information is associated with a hashtag. Application information usually contains advertiser information. The advertiser information contained in the application information may be only a part of the advertiser information in the advertiser management department 512 (for example, only the advertiser identifier).
[0241] The server processing unit 53 performs various processes. These processes include, for example, those performed by the advertiser recruitment unit 531, the response unit 532, the advertiser information storage unit 533, or the billing processing unit 534.
[0242] The advertiser recruitment unit 531 performs the process of recruiting advertisers for the advertisements that are displayed when a hashtag is selected. This process is called the advertiser recruitment process.
[0243] The advertiser recruitment unit 531 transmits recruitment screen information, which is screen information for recruiting advertisers for each of the one or more hashtags in the hashtag management unit 511, to one or more terminal devices. The advertiser recruitment unit 531 acquires one or more hashtags for which advertisers are to be recruited, constructs recruitment screen information having the one or more hashtags or tags, and transmits the recruitment screen information to one or more terminal devices. For example, the advertiser recruitment unit 531 transmits recruitment screen information to terminal devices in response to receiving an instruction to submit an application page.
[0244] The response unit 532 automatically determines the advertiser for the hashtag. The response unit 532 associates at least one advertiser information from the two or more advertiser information of the advertiser management unit 512 with each of the one or more hashtags in the hashtag management unit 511.
[0245] The response unit 532 obtains one or more tag attribute values for each of the one or more hashtags in the hashtag management unit 511. Next, for each of the one or more hashtags, the response unit 532 determines one or more advertiser attribute values that satisfy the matching conditions with one or more tag attribute values of the hashtag, and associates the hashtag with the advertiser identifier that is paired with the said one or more advertiser attribute values.
[0246] Tag attribute values are the attribute values of a hashtag. These include, for example, the product attribute values, tag type, and price of the product information corresponding to the hashtag. Here, product attribute values are, for example, type information indicating the product type and the product price. Tag type refers to the type of hashtag. Tag type is, for example, the linguistic characteristics of the tag, such as a "phrase," "word," or "sentence." The price of a tag attribute value is the advertising fee for the hashtag. This advertising fee is, for example, the advertising fee for a unit period or the advertising fee for a single output of advertising information.
[0247] The advertiser information storage unit 533 stores the advertiser information that the correspondence unit 532 has associated with a hashtag.
[0248] The billing processing unit 534 performs billing processing to bill the advertiser corresponding to a single advertiser information stored by the advertiser information storage unit 533 for the advertising fee indicated by the advertising fee information associated with the hashtag.
[0249] The server transmission unit 54 transmits various types of information to the terminal device 6. These types of information include, for example, information indicating that a billing process has been completed.
[0250] The terminal storage unit 61, which constitutes the terminal device 6, stores various types of information. These types of information include, for example, a user identifier.
[0251] The terminal reception unit 62 receives various types of information and instructions. These types of information and instructions include, for example, instructions for creating a product management table, selecting hashtags, application information, and instructions for submitting the application page.
[0252] The instruction to submit the application page is an instruction to submit the advertiser's application page. The application page can be the same as the information on the recruitment screen.
[0253] Here, "reception" is a concept that includes receiving information input from input devices such as keyboards, mice, and touch panels; receiving information transmitted via wired or wireless communication lines; and receiving information read from recording media such as optical discs, magnetic discs, and semiconductor memory.
[0254] The means of inputting various information and instructions can be anything, such as a touch panel, keyboard, mouse, or menu screen.
[0255] The terminal processing unit 63 performs various processes. These processes include, for example, converting received information and instructions into information and instructions for transmission. Other processes include, for example, converting received information into information for output.
[0256] The terminal transmission unit 64 transmits various information and instructions to the information processing device 4 or the server 5. Examples of such information and instructions include instructions for creating a product management table, selecting hashtags, application information, and instructions for submitting the application page.
[0257] The terminal receiving unit 65 receives various types of information from the information processing device 4, the server 5, or a web server (not shown). These types of information include, for example, web pages.
[0258] The terminal output unit 66 outputs various types of information. These types of information include, for example, page numbers.
[0259] Here, "output" is a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, transmission to an external device, storage on a recording medium, and transfer of processing results to other processing devices or other programs.
[0260] The storage unit 41, page storage unit 411, product management unit 412, advertising management unit 413, server storage unit 51, hashtag management unit 511, advertiser management unit 512, or terminal storage unit 61 are preferably made of non-volatile recording media, but can also be made of volatile recording media.
[0261] The process by which information is stored in the storage unit 41, etc. is not relevant. For example, information may be stored in the storage unit 41, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 41, etc., or information input via an input device may be stored in the storage unit 41, etc.
[0262] The reception unit 42, selection reception unit 421, server reception unit 52, application reception unit 521, or terminal reception unit 65 are usually implemented by wireless or wired communication means, but may also be implemented by means of receiving broadcasts.
[0263] The processing unit 43, tag acquisition unit 431, advertising information acquisition unit 432, product information acquisition unit 433, page composition unit 434, billing processing unit 435, server processing unit 53, advertiser recruitment unit 531, response unit 532, advertiser information storage unit 533, billing processing unit 534, or terminal processing unit 63 can typically be implemented using a processor, memory, etc. The processing procedures of the processing unit 43, etc., are typically implemented in software, and this software is recorded on a recording medium such as ROM. However, it may also be implemented in hardware (dedicated circuitry). The processor can be a CPU, MPU, GPU, etc., and the type is not limited.
[0264] The output unit 44, page output unit 441, server transmission unit 54, or terminal transmission unit 64 are usually implemented by wireless or wired communication means, but may also be implemented by broadcasting means.
[0265] The terminal reception unit 62 can be implemented using device drivers for input means such as touch panels and keyboards, or control software for menu screens, etc.
[0266] The terminal output unit 66 may or may not be considered to include output devices such as displays and speakers. The terminal output unit 66 can be implemented using driver software for an output device, or a driver software for an output device and an output device.
[0267] Next, an operation example of the information processing apparatus 4 will be described using the flowchart of FIG. 16. Here, it is assumed that the information processing apparatus 4 has the functions of the server 5. Also, here, the information processing apparatus 4 is a server, not a terminal.
[0268] (Step S1601) The reception unit 42 determines whether it has received an instruction to construct a product management table from the terminal device 6. If it has received the instruction to construct a product management table, it proceeds to step S1602; if not, it proceeds to step S1603.
[0269] (Step S1602) The processing unit 43 performs product information accumulation processing. It returns to step S1601. The product information accumulation processing is a process of accumulating pairs of hash tags and product information in the product management unit 412. Note that the hash tags and the product information do not have to be one-to-one, and can be one-to-many, many-to-one, or many-to-many. An example of the product information accumulation processing will be described using the flowchart of FIG. 17.
[0270] (Step S1603) The selection reception unit 4 twenty-one determines whether it has received a selection of a hash tag. If it has received a selection of a hash tag, it proceeds to step S1604; if not, it proceeds to step S1610.
[0271] [[ID=##**##]] (Step S1604) The product information acquisition unit 433 acquires the hash tag selected by the user based on the selection of the hash tag.
[0272] (Step S1605) The product information acquisition unit 433 acquires one or more pieces of product information paired with the hash tag from the product management unit 412.
[0273] (Step S1606) The advertisement information acquisition unit 432 acquires one or more pieces of advertisement information paired with the hash tag from the advertisement management unit 413.
[0274] (Step S1607) The page configuration unit 434 constitutes a page having one or more product information obtained in step S1605 and one or more advertisement information obtained in step S1606. Preferably, this page is a page for purchasing products corresponding to one or more product information items.
[0275] (Step S1608) The page output unit 441 sends the page configured in step S1607 to the terminal device 6 that sent the hashtag selection.
[0276] (Step S1609) The billing processing unit 435 performs billing processing to invoice the advertiser for advertising fees in response to the transmission of advertising information. The process returns to Step S1601. An example of such billing processing will be explained using the flowchart in Figure 18.
[0277] (Step S1610) The processing unit 43 decides whether or not to determine an advertiser corresponding to the hashtag. If an advertiser is determined, the unit proceeds to step S1611; if an advertiser is not determined, the unit proceeds to step S1612. The unit decides to determine an advertiser corresponding to the hashtag, for example, when a predetermined time has arrived, when there is a user instruction, when there is no advertiser for the hashtag, and when the number of hashtags in the advertising management unit 413 exceeds a threshold.
[0278] (Step S1611) The advertiser recruitment department 531, etc., performs the process to determine the advertiser. Return to Step S1601. An example of such advertiser determination process will be explained using the flowchart in Figure 19.
[0279] (Step S1612) The processing unit 43 determines whether or not to accept advertiser applications for the hashtag. If the advertiser applications are accepted, the process proceeds to step S1613; otherwise, it returns to step S1601.
[0280] (Step S1613) The advertiser recruitment department 531, etc., processes the application. Return to Step S1601. The application process is the process of submitting advertisers to a hashtag. An example of the application process will be explained using the flowchart in Figure 20.
[0281] In the flowchart shown in Figure 16, processing is terminated by power-off or processing termination interrupts.
[0282] Next, an example of the product information storage process in step S1602 will be explained using the flowchart in Figure 17.
[0283] (Step S1701) The tag acquisition unit 431 assigns 1 to counter i.
[0284] (Step S1702) The tag acquisition unit 431 determines whether the i-th website 3, which is the source of the tag information, exists. If the i-th website 3 exists, the process proceeds to step S1703; otherwise, it returns to the higher-level process.
[0285] The website from which the tag source information is obtained is usually predetermined. Furthermore, the address information for accessing the i-th website is stored in storage unit 41.
[0286] Furthermore, the i-th website may be the information processing device 4. In this case, the web page is stored in the page storage unit 411.
[0287] (Step S1703) The tag acquisition unit 431 acquires one or more web pages from the i-th website 3.
[0288] (Step S1704) The tag acquisition unit 431 assigns 1 to counter j.
[0289] (Step S1705) The tag acquisition unit 431 determines whether the j-th product information exists in one or more web pages acquired in step S1703. If the j-th product information exists, it proceeds to step S1706; if it does not exist, it proceeds to step S1712.
[0290] (Step S1706) The tag acquisition unit 431 substitutes 1 for the counter k.
[0291] (Step S1707) The tag acquisition unit 431 determines whether the k-th UGC (for example, a review) corresponding to the j-th product information of the i-th website 3 exists. If the k-th UGC exists, it proceeds to step S1708; if it does not exist, it proceeds to step S1710.
[0292] (Step S1708) The tag acquisition unit 431 acquires the k-th UGC corresponding to the j-th product information of the i-th website 3. Next, the tag acquisition unit 431 acquires one or more tags from the UGC. It is preferable that the tag is a phrase having two or more words, but it may also be a word or a sentence. Next, the tag acquisition unit 431 accumulates the one or more acquired tags in association with the i-th website 3 and the j-th product information. The tag acquisition unit 431, for example, also associates the one or more acquired tags with the k-th UGC. The tag acquisition unit 431 accumulates the one or more acquired terms in a buffer (not shown) in association with, for example, the site identifier of the i-th website, the product identifier of the j-th product information, and the identifier of the k-th UGC.
[0293] [[ID=十六]](Step S1709) The tag acquisition unit 431 increments the counter k by 1. It returns to step S1707.
[0294] (Step S1710) The tag acquisition unit 431 acquires one or more tags from the j-th product information (e.g., product description information, product image) of the i-th website 3. Next, the tag acquisition unit 431 stores the acquired one or more tags in association with the i-th website 3 and the j-th product information. Note that the tags here are, for example, words (terms).
[0295] (Step S1711) The tag acquisition unit 431 increments counter j by 1. Return to step S1705.
[0296] (Step S1712) The tag acquisition unit 431 acquires the facets of the i-th website 3.
[0297] (Step S1713) The tag acquisition unit 431 assigns 1 to counter l.
[0298] (Step S1714) The tag acquisition unit 431 determines whether the l-th tag exists among the facets acquired in step S1712. If the l-th tag exists, the unit proceeds to step S1715; otherwise, the unit proceeds to step S1718.
[0299] (Step S1715) The tag acquisition unit 431 acquires the product identifier for each of the one or more product information items searched using the l-th tag.
[0300] (Step S1716) The tag acquisition unit 431 associates the l-th tag with the product identifier acquired in step S1715 and the i-th website 3, and stores it in a buffer (not shown).
[0301] (Step S1717) The tag acquisition unit 431 increments the counter l by 1. Return to step S1714.
[0302] (Step S1718) The tag acquisition unit 431 increments the counter i by 1. Return to step S1702.
[0303] (Step S1719) The tag acquisition unit 431 performs tag selection processing. It returns to the higher-level processing. An example of tag selection processing will be explained using the flowchart in Figure 21. Tag selection processing is the process of determining the tags to be selected and storing the product information and hashtag pairs in the product management unit 412. Note that the storage of hashtags can be considered synonymous with the storage of tags.
[0304] In the flowchart in Figure 17, tags were obtained from UGC, product information, and facets. However, in the flowchart in Figure 5, tags may be obtained from only one or two of the following types of information: UGC, product information, and facets.
[0305] Furthermore, in the flowchart of Figure 17, the tag acquisition unit 431 may acquire a set of two or more tags within a facet, associate the product identifier of one or more product pieces of information retrieved by the AND condition of the set of two or more tags with the set of two or more tags, and store them in a buffer (not shown).
[0306] Next, an example of the billing process in step S1609 will be explained using the flowchart in Figure 18.
[0307] (Step S1801) The billing processing unit 435 retrieves the selected hashtag.
[0308] (Step S1802) The billing processing unit 435 assigns 1 to counter i.
[0309] (Step S1803) The billing processing unit 435 determines whether or not the i-th advertisement information exists among the advertisement information contained in the submitted page. If the i-th advertisement information exists, the process proceeds to step S1804; otherwise, it returns to the higher-level processing.
[0310] (Step S1804) The billing processing unit 435 obtains the advertiser identifier that corresponds to the hashtag and the i-th advertisement information obtained in step S1801 from the advertising management unit 413.
[0311] (Step S1805) The billing processing unit 435 obtains advertising fee information from the advertising management unit 413 that corresponds to the hashtag obtained in step S1801.
[0312] (Step S1806) The billing processing unit 435 processes the billing of the advertising fee indicated by the advertising fee information obtained in step S1805 to the advertiser identified by the advertiser identifier obtained in step S1804.
[0313] (Step S1807) The billing processing unit 435 increments counter i by 1. Return to step S1803.
[0314] Next, an example of the advertiser selection process in step S1611 will be explained using the flowchart in Figure 19.
[0315] (Step S1901) The corresponding unit 532 assigns 1 to counter i.
[0316] (Step S1902) The response unit 532 determines whether the i-th hashtag for determining the advertiser exists in the advertising management unit 413. If the i-th hashtag exists, the process goes to step S1903; otherwise, the process goes to step S1913.
[0317] (Step S1903) The corresponding unit 532 determines whether the flag corresponding to the i-th hashtag is "automatically determined" or "manually determined". If it is "automatically determined", proceed to step S1904; if it is "manually determined", proceed to step S1911. The flag here indicates whether the advertiser for the hashtag is automatically determined or whether it is applied for (manually determined).
[0318] (Step S1904) The corresponding unit 532 obtains one or more tag attribute values for the i-th hashtag.
[0319] (Step S1905) The corresponding unit 532 assigns 1 to counter j.
[0320] (Step S1906) The response unit 532 determines whether the j-th advertiser information exists in the advertiser management unit 512. If the j-th advertiser information exists, the process proceeds to step S1907; otherwise, the process proceeds to step S1912.
[0321] (Step S1907) The response unit 532 obtains one or more advertiser attribute values from the advertiser management unit 512 that are present in the j-th advertiser information.
[0322] (Step S1908) The corresponding unit 532 determines whether the one or more tag attribute values obtained in step S1904 and the one or more advertiser attribute values obtained in step S1907 match the matching conditions. If the matching conditions are met, the process proceeds to step S1909; otherwise, the process proceeds to step S1912.
[0323] Matching conditions are the criteria used to match hashtags with advertisers. For example, matching conditions may involve one or more advertiser attribute values and one or more tag attribute values. For example, a matching condition may be that the advertiser attribute value "product type information" matches the tag attribute value "product type information". For example, a matching condition may be that "advertiser attribute value budget >= tag attribute value advertising fee".
[0324] (Step S1909) The correspondence unit 532 associates the i-th hashtag with the j-th advertiser information in the advertising management unit 413.
[0325] (Step S1910) The corresponding unit 532 increments counter i by 1. Return to step S1906.
[0326] (Step S1911) The corresponding unit 532 temporarily stores the i-th hashtag, etc. in a buffer (not shown). Hashtag, etc. refers to, for example, a hashtag and the advertising fee information corresponding to that hashtag.
[0327] (Step S1912) The corresponding unit 532 increments counter i by 1. Return to step S1902.
[0328] (Step S1913) The advertiser recruitment unit 531 is a page that has one or more hashtags etc. temporarily stored in a buffer (not shown), and constitutes a page for advertisers to apply for hashtags, and stores it in the storage unit 41. The process returns to the higher level.
[0329] Next, an example of the application process in step S1613 will be explained using the flowchart in Figure 20.
[0330] (Step S2001) The reception unit 42 determines from the terminal device 6 whether or not it has received an instruction to submit the application page. If an instruction to submit the application page has been received, the unit proceeds to step S2002; otherwise, it proceeds to step S2003.
[0331] (Step S2002) The page output unit 441 retrieves the application page from the storage unit 41 and transmits the application page to the terminal device 6. It then returns to the higher-level processing.
[0332] (Step S2003) The reception unit 42 determines whether or not it has received application information from the terminal device 6. If it has received application information, it proceeds to step S2004; otherwise, it returns to the higher-level process.
[0333] (Step S2004) The corresponding unit 532 retrieves the submitted hashtags from the application information.
[0334] (Step S2005) The corresponding unit 532 obtains advertiser information contained in the application information.
[0335] (Step S2006) The response unit 532 determines whether the registration conditions are met. If the registration conditions are met, the process proceeds to step S2007; otherwise, it returns to the higher-level process.
[0336] The registration conditions are the requirements for registering advertiser information in association with hashtags. For example, the registration conditions might be: "The advertiser attribute value, budget, >= the sum of the advertising fees, which are the tag attribute values of one or more hashtags (including the submitted hashtags) that are paired with the advertiser identifier."
[0337] (Step S2007) The corresponding unit 532 stores the advertiser information obtained in Step S2005 in the advertising management unit 413, associating it with the hashtag. It then returns to the higher-level processing.
[0338] Next, an example of the tag selection process in step S1719 will be explained using the flowchart in Figure 21.
[0339] (Step S2101) The processing unit 43 sorts the pairs of tags and product identifiers using the tags as keys.
[0340] (Step S2102) The processing unit 43 assigns 1 to counter i.
[0341] (Step S2103) The processing unit 43 determines whether or not the i-th type of tag exists in the set of tags sorted in step S2101. If the i-th type of tag exists, the process proceeds to step S2104; otherwise, it returns to the higher-level processing.
[0342] Note that the i-th tag of a particular type is a different i-th tag. The tag "good to the touch" and the tag "wide range of applications" are of different types. The tag "good to the touch" and the tag "good to the touch" are of the same type.
[0343] (Step S2104) The processing unit 43 obtains the occurrence count of the i-th type of tag.
[0344] (Step S2105) The processing unit 43 determines whether the i-th type of tag satisfies the selection conditions. If the selection conditions are met, the process proceeds to step S2106; otherwise, it proceeds to step S2111. The selection conditions are, for example, conditions relating to the i-th type of tag, or conditions relating to the product information to which the tag corresponds. Conditions relating to the i-th type of tag include, for example, that the number of occurrences of the tag is greater than or equal to a threshold, or that the tf / idf value for the tag is greater than or equal to a threshold. Conditions relating to product information include that the number of product information items paired with the tag is greater than or equal to a threshold.
[0345] (Step S2106) The processing unit 43 obtains a hashtag by adding "#" to the i-th type of tag.
[0346] (Step S2107) The processing unit 43 obtains one or more product information items that are paired with the i-th type tag.
[0347] (Step S2108) The processing unit 43 determines whether the product information obtained in step S2107 already exists in the product management unit 412. If the product information already exists in the product management unit 412, the process proceeds to step S2109; otherwise, the process proceeds to step S2110.
[0348] (Step S2109) The processing unit 43 adds the hashtag obtained in step S2106 to the product management unit 412, paired with the product information obtained in step S2107.
[0349] (Step S2110) The processing unit 43 stores the combination of product information obtained in step S2107 and hashtags obtained in step S2106 in the product management unit 412.
[0350] (Step S2111) The processing unit 43 increments counter i by 1. The process returns to step S2103.
[0351] Next, we will explain an example of the operation of Server 5 using the flowchart in Figure 22. In the flowchart in Figure 22, we will omit the explanation for steps that are the same as those in the flowcharts in Figures 16 and 20.
[0352] (Step S2201) The server processing unit 53 determines whether or not it is time to decide on advertisers for the hashtag. If it is time to decide on advertisers for the hashtag, the process proceeds to step S1611; otherwise, it proceeds to step S2001.
[0353] In the flowchart shown in Figure 22, processing is terminated by power-off or processing termination interrupts.
[0354] The following describes a specific example of the operation of information system B in this embodiment. Here, it is assumed that the information processing device 4 constituting information system B has all or part of the functions of the page generation device 1. The page storage unit 411 stores one or more web pages obtained from one or more e-commerce sites (websites 3) that sell clothing, bags, etc., and each website 3 contains information on multiple products. As explained in specific example 1 of Embodiment 1, the tag acquisition unit 431 of the information processing device 4 acquires a number of hashtags (for example, "#short length", "#casual", "#coordinate", "#simple", "#commuting", "#style", "#shoulder pain-free", "#various scenes") from the web pages and associates them with product information (904 in Figure 9). In this specification, the "#" in hashtags may be half-width or full-width.
[0355] The tag acquisition unit 431 then associates the acquired hashtags with the product information, or the product information, that corresponds to the tag source information (reviews), from which each hashtag was acquired, and stores this information in the product management unit 412. This information is represented in the product management table shown in Figure 23.
[0356] A product management table is a table that manages the correspondence between product information and hashtags. A product management table manages one or more records that have an "ID," "product identifier," "product attribute value," and "hashtag." The "product attribute value" includes "product name," "type information," "product image," and "product description." The "ID" is the information that identifies the record. The "hashtag" field stores one or more hashtags. Note that the "hashtag" field may also store tags without the "#" symbol instead of hashtags.
[0357] Furthermore, the tag acquisition unit 431 stores the numerous acquired hashtags in the advertising management unit 413. This information consists of hashtags that make up the advertising management table in Figure 24. The advertising management table is a table that manages the correspondence between hashtags and advertising information. The structure of the advertising management table is such that it has one or more records having "ID", "hashtag", "tag attribute value", "advertising identifier", "advertising information", and "advertising attribute value". The "tag attribute value" has "tag type", "type information", and "price". The "advertising attribute value" has "advertiser identifier", "data type", and "advertising fee". "Tag type" indicates the type of tag, which in this case is, for example, "phrase", "word", or "sentence". "Type information" indicates the type of product information (type of product) corresponding to the hashtag. "Price" is the price of the advertising space corresponding to the hashtag. "Price" is the cost per unit period (for example, one month) imposed on the advertiser of the hashtag. "Advertising information" in this case is the file name of the advertisement. "Data type" is the data type of the advertisement. "Advertising fee" is the advertising fee charged per instance when advertising information is sent to the terminal device 6 as a result of a hashtag being selected.
[0358] The tag acquisition unit 431 determines the tag type based on the linguistic characteristics of the tags that make up the hashtag and stores it in the advertising management table. The tag acquisition unit 431 also stores the product type information contained in the product information corresponding to the hashtag in the advertising management table. Furthermore, for each hashtag, the tag acquisition unit 431 determines the price based on the frequency of occurrence of the tags that make up the hashtag and stores the price in the advertising management table. For example, the higher the frequency of occurrence of a tag, the higher the price determined. The price may also be determined by the operator of the information processing device 4 or server 5 and stored in the advertising management table.
[0359] Furthermore, the storage unit 41 stores the advertiser management table shown in Figure 25. The advertiser management table is a table that manages advertiser information. The advertiser management table is a table that manages one or more records having an "ID," "advertiser identifier," and "advertiser attribute value." The "advertiser attribute value" has "type information," "advertiser flag," "budget," and "account information." "Type information" is the type information of the products handled by the advertiser. The "advertiser flag" is a flag that indicates whether the advertiser automatically purchases hashtags or not. An advertiser flag of "1" indicates that the advertiser may automatically associate hashtags with advertisers (automatic purchase is possible). An advertiser flag of "0" indicates that the advertiser will not automatically associate hashtags with advertisers (automatic purchase is not possible). Advertisers corresponding to an advertiser flag of "0" can only purchase hashtag advertising space by applying. "Budget" indicates the budget that the advertiser spends as advertising fees per month. "Account information" is the advertiser's account information, such as bank account information or credit card number.
[0360] In light of the above situation, three specific examples are described below. Specific example 1 describes the process of associating advertisers with hashtags. Specific example 2 describes the process of sending a page containing product information and advertising information associated with a hashtag to the user's terminal device 6 when the user selects a hashtag on the screen. Specific example 3 describes the process of sending a page in which advertising information associated with a hashtag is prominently displayed to the user's terminal device 6 when the user selects a hashtag on the screen. Furthermore, specific example 3 is a case where the advertising information has a similar image to the product information, and it is difficult to distinguish between the advertising information and the product information at first glance.
[0361] (Specific example 1) Here, the information processing device 4 is assumed to have the functionality of a server 5.
[0362] In this case, the corresponding unit 532 of the information processing device 4 automatically determines advertisers whose hashtags correspond to the tag type "word," and advertisers whose hashtags correspond to the tag type "phrase" or "sentence" apply.
[0363] In Figure 24, the tag type for the hashtags "#shortlength" and "#simple" is "phrase," so the corresponding unit 532 automatically determines the advertisers for the hashtags "#shortlength" and "#simple" as follows.
[0364] In other words, the response unit 532 obtains the type information "clothing" which is paired with the hashtag "#shortlength" from Figure 24. Next, the response unit 532 obtains the advertiser identifier "A02", which is paired with the type information "clothing" and advertiser flag "1", from the advertiser management table (Figure 25). Next, the response unit 532 stores the advertising identifier "A02" and the advertiser identifier "A02" in the advertising information management table (Figure 24) in conjunction with the hashtag "#shortlength". Note that the advertising identifier "A02" is unique and is information generated by the response unit 532. Subsequently, the advertiser identified by the advertiser identifier "A02" uploads the advertising information "A02.mp4" to the information processing device 4, associating it with the advertising identifier "A02" and the advertiser identifier "A02". As a result, the information processing device 4 receives the advertising information and stores it in the advertising information management table (Figure 24). Furthermore, the information processing device 4 analyzes the advertising information, obtains the data type "video," and stores the data type and the corresponding advertising fee "20" in the advertising information management table (Figure 24). The advertising fee for the data type "still image" is "10," the advertising fee for the data type "video" is "20," and the advertising fee for the data type "text" is "5." Furthermore, the corresponding unit 532 similarly automatically determines the advertiser identifier "A06" corresponding to the hashtag "#simple", and stores the generated unique advertising identifier "A06" and advertiser identifier "A06" in the advertising information management table (Figure 24).
[0365] Furthermore, the advertiser identified by the advertiser identifier "A06" then uploads the advertising information "A06.mp4" to the information processing device 4, associating it with the advertising identifier "A06" and the advertiser identifier "A06". As a result, the information processing device 4 receives the advertising information and stores it in the advertising information management table (Figure 24). The information processing device 4 also analyzes the advertising information, obtains the data type, and stores the data type and the advertising fee corresponding to the data type in the advertising information management table (Figure 24).
[0366] Next, the response unit 532 retrieves one or more hashtags and their prices for soliciting advertisers from the advertising information management table (Figure 24). Note that the hashtags for soliciting advertisers are hashtags that are paired with tag types "phrase" or "sentence". At this point, the response unit 532 has retrieved hashtags such as "#good to the touch", "#various scenes", "#no shoulder pain", and "#perfect for mountain climbing".
[0367] Next, the advertiser recruitment unit 531 constructs an application page containing the acquired hashtag and price pairs and stores it in the storage unit 41.
[0368] In the above situation, each of the candidate users of one or more advertisers has entered an instruction to submit the application page into terminal device 6.
[0369] Next, terminal device 6 receives the instruction to submit the application page and transmits the instruction to information processing device 4.
[0370] Next, the receiving unit 42 of the information processing device 4 receives an instruction to send the application page. Then, the page output unit 441 retrieves the application page from the storage unit 41 and transmits the application page to the terminal device 6.
[0371] Here, let's assume that user U's terminal device 6, with advertiser identifier "A01", receives and prints the application page shown in Figure 26. Then, let's assume that user U selects the hashtag "#goodfeel" (2601), enters the advertiser identifier "A01" (2602), and clicks the "Submit" button 2603.
[0372] Next, terminal device 6 receives the instructions, etc., and constructs the application information "<advertiser identifier>A01 <hashtag>#good to the touch", and transmits the application information to information processing device 4.
[0373] Next, the receiving unit 42 of the information processing device 4 receives the application information from the user U's terminal device 6.
[0374] Next, the response unit 532 retrieves the submitted hashtag "#TouchGood" based on the application information. The response unit 532 also generates a unique advertising identifier "A01". The response unit 532 also retrieves the advertiser identifier "A01" contained in the application information.
[0375] Next, the correspondence unit 532 associates the hashtag "#goodtouch" with the advertising identifier "A01" and the advertiser identifier "A01" and stores them in the advertising information management table (Figure 24).
[0376] Subsequently, the advertiser identified by advertiser identifier "A01" uploads the advertising information "A01.jpg" to the information processing device 4, associating it with the advertising identifier "A01" and the advertiser identifier "A01". As a result, the information processing device 4 receives the advertising information and stores it in the advertising information management table (Figure 24). The information processing device 4 also analyzes the advertising information, obtains the data type, and stores the data type and the advertising fee corresponding to the data type in the advertising information management table (Figure 24).
[0377] Through the above process, the advertisers for the hashtags were determined either automatically or manually (by application).
[0378] (Specific example 2) Now, let's assume that the screen shown in Figure 27 is displayed on user X's terminal device 6. Next, let's assume that user X instructed the user to click on the hashtag "#goodfeel" 2701 shown in Figure 27.
[0379] Next, terminal device 6 accepts the selection of the hashtag "#good to the touch". Then, terminal device 6 accepts the selection, configures a selection that has the hashtag "#good to the touch", and transmits the selection that has the hashtag "#good to the touch" to information processing device 4.
[0380] Next, the selection receiving unit 421 receives the selection of the hashtag "#good to the touch". Then, the product information acquisition unit 433 acquires the hashtag "#good to the touch" that the selected hashtag possesses.
[0381] Next, the product information acquisition unit 433 acquires one or more product information items that correspond to the hashtag "#good to the touch" from the product management table (Figure 23).
[0382] Furthermore, the advertising information acquisition unit 432 acquires one or more advertising pieces that are paired with the hashtag "#good to the touch" from the advertising information management table (Figure 24). Here, let's assume that the advertising information acquisition unit 432 has acquired the advertising piece "A01.jpg" with "ID=1".
[0383] Next, the page configuration unit 434 constitutes a page having one or more product information and one advertisement information.
[0384] Next, the page output unit 441 sends the configured page to the terminal device 6 that sent the hashtag selection.
[0385] Next, terminal device 6 receives and outputs the page. An example of such output is shown in Figure 28. In Figure 28, 2801 and 2802 are the acquired product information, and 2803 is the acquired advertisement information "A01.jpg".
[0386] (Specific example 3) Now, let's assume that the screen shown in Figure 11 is displayed on user X's terminal device 6. Next, let's assume that user X has instructed the user to use the hashtag "#EverydayUse" shown in Figure 11.
[0387] Next, terminal device 6 accepts the selection of the hashtag "#EverydayUse". Then, terminal device 6 accepts the selection, configures a selection that has the hashtag "#EverydayUse", and transmits the selection that has the hashtag "#EverydayUse" to information processing device 4.
[0388] Next, the selection reception unit 421 receives the selection of the hashtag "#everydayuse". Then, the product information acquisition unit 433 acquires the hashtag "#everydayuse" that the selected hashtag possesses.
[0389] Next, the product information acquisition unit 433 retrieves four product information items that correspond to the hashtag "#everydayuse" from the product management table (Figure 23).
[0390] Furthermore, the advertising information acquisition unit 432 acquired two pieces of advertising information corresponding to the hashtag "#everydayuse" from the advertising information management table (Figure 24).
[0391] Next, the page composition section 434 constitutes a page having two product information items and four advertising information items. Here, the page composition section 434 arranges the advertising information and product information on the page in a similar display manner, with the advertising information placed at the top of the page and the product information placed after the advertising information. Furthermore, the page composition section 434 configures the page so that the advertising information includes a marker that indicates it is an advertisement (in this case, an icon (text string) [PR]). The similar display manner here refers to a display manner in which "image," "product type name," and "price" are arranged from top to bottom.
[0392] Next, the page output unit 441 sends the configured page to the terminal device 6 that sent the hashtag selection.
[0393] Next, terminal device 6 receives and outputs the page. An example of such output is shown in Figure 29. In Figure 29, 2901 and 2902 are acquired advertising information, and 2903, 2904, 2905, and 2906 are acquired product information.
[0394] As described above, according to this embodiment, it is possible to provide a page that includes advertising information and product information related to the page's hashtags.
[0395] Furthermore, according to this embodiment, it is possible to provide a page that includes advertising information and product information for hashtags obtained from UGC, etc.
[0396] Furthermore, according to this embodiment, it is possible to provide a page that includes advertising information and product information for hashtags, which are phrases having two or more words.
[0397] Furthermore, according to this embodiment, advertisers can be charged advertising fees for advertisements related to the page's hashtags.
[0398] Furthermore, according to this embodiment, advertisers can bid on hashtags they wish to advertise.
[0399] Furthermore, according to this embodiment, advertisers can be automatically determined based on hashtags.
[0400] Furthermore, according to this embodiment, advertisers can be charged advertising fees for hashtags they have chosen.
[0401] The software that implements the information processing device 4 in this embodiment is as follows: This program causes the computer to function as a selection receiving unit that accepts the selection of hashtags, an advertising information acquisition unit that acquires advertising information corresponding to the hashtags accepted by the selection receiving unit from an advertising management unit that stores one or more pieces of advertising information corresponding to one or more hashtags, a product information acquisition unit that acquires product information corresponding to the hashtags accepted by the selection receiving unit from a product management unit that stores two or more pieces of product information corresponding to one or more hashtags, a page configuration unit that constitutes a page having the advertising information acquired by the advertising information acquisition unit and the product information acquired by the product information acquisition unit, and a page output unit that outputs the page configured by the page configuration unit.
[0402] Furthermore, the software that implements the server 5 in this embodiment is, for example, the following program. In other words, this program is a program that causes a computer that can access a hashtag management unit, which stores one or more hashtags obtained from the tag source information on a page by adding "#" to each of the one or more tags, to function as an advertiser recruitment unit that transmits recruitment screen information, which is screen information for recruiting advertisers for each of the one or more hashtags in the hashtag management unit, to one or more terminal devices; an application receiving unit that receives application information having advertiser information about advertisers from the terminal devices in association with hashtags in response to the transmission of the recruitment screen information; and an advertiser information storage unit that stores the advertiser information received by the application receiving unit in association with the hashtags.
[0403] Furthermore, the software that implements the server 5 in this embodiment is, for example, the following program. In other words, this program is a program that causes a computer that can access a hashtag management unit, which stores one or more hashtags obtained by adding "#" to one or more tags acquired from the tag source information on a page, to function as an advertiser management unit which stores two or more advertiser information about advertisers, a correspondence unit which associates at least one of the two or more advertiser information in the advertiser management unit with each of the one or more hashtags in the hashtag management unit, and an advertiser information storage unit which stores the one advertiser information associated by the correspondence unit in association with the hashtags.
[0404] Figure 30 is a block diagram of a computer system 300 that executes the program described herein to realize the various embodiments of the information processing device 4 or server 5 described above.
[0405] In Figure 30, the computer system 300 includes a computer 301 with a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.
[0406] In Figure 30, the computer 301 includes, in addition to the CD-ROM drive 3012, an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012, a ROM 3015 for storing programs such as boot-up programs, a RAM 3016 connected to the MPU 3013 for temporarily storing application program instructions and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, the computer 301 may further include a network card for providing connectivity to a LAN.
[0407] The program that causes the computer system 300 to execute the functions of the information processing device 4, etc., as described above, may be stored on the CD-ROM 3101, inserted into the CD-ROM drive 3012, and then transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored on the hard disk 3017. The program is loaded into the RAM 3016 during execution. The program may also be loaded directly from the CD-ROM 3101 or the network.
[0408] The program does not necessarily have to include an operating system (OS) or third-party program that causes the computer 301 to execute functions such as the information processing device 4 of the above embodiment. The program only needs to include the instruction portion that calls appropriate functions (modules) in a controlled manner and obtains the desired result. How the computer system 300 operates is well known, so a detailed explanation is omitted.
[0409] In the above program, steps such as sending information and receiving information do not include hardware-based processing, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).
[0410] Furthermore, the computer running the above program may be a single computer or multiple computers. In other words, it may perform centralized processing or distributed processing.
[0411] Furthermore, it goes without saying that in each of the above embodiments, two or more communication means present in a single device may be physically implemented in a single medium.
[0412] Furthermore, in each of the above embodiments, each process may be implemented by centralized processing by a single device, or by distributed processing by multiple devices.
[0413] It goes without saying that the present invention is not limited to the embodiments described above, and various modifications are possible, all of which are also included within the scope of the present invention. [Industrial applicability]
[0414] As described above, the information processing device 4 according to the present invention has the effect of providing a page that includes advertising information and product information for the page's hashtags, and is useful as a server or the like that links hashtags and advertisements. [Explanation of Symbols]
[0415] B Information Systems 4. Information Processing Device 5 Servers 6 Terminal devices 41 Storage Unit 42 Reception Department 43 Processing Unit 44 Output section 51 Server storage unit 52 Server receiving unit 53 Server Processing Unit 54 Server transmission section 61 Terminal storage section 62 Terminal Reception Section 63 Terminal Processing Unit 64 Terminal Transmitter 65 Terminal receiving unit 66 Terminal output section 411 Page Storage Section 412 Product Management Department 413 Advertising Management Department 421 Selection Reception Department 431 Tag acquisition section 432 Advertising Information Acquisition Department 433 Product Information Acquisition Department Page 434 Structure 435, 534 Billing Processing Unit Page 441 Output Section 511 Hashtag Management Department 512 Advertiser Management Department 521 Application Reception Department 530 Advertising Rate Determination Department 531 Advertiser Recruitment Department 532 Corresponding section 533 Advertiser Information Storage Department
Claims
1. A hashtag management unit stores one or more hashtags obtained by adding "#" to one or more tags acquired from the tag source information on the page, An advertiser recruitment unit transmits recruitment screen information, which is screen information for recruiting advertisers for each of the one or more hashtags of the hashtag management unit, to one or more terminal devices. In response to the transmission of the aforementioned recruitment screen information, the application receiving unit receives application information containing advertiser information about the advertiser, associated with hashtags, from the terminal device. A server comprising: an advertiser information storage unit that stores the advertiser information received by the application receiving unit in association with the hashtag; and an advertiser information storage unit.
2. A hashtag management unit stores one or more hashtags obtained by adding "#" to one or more tags acquired from the tag source information on the page, An advertiser management unit where two or more advertiser information entries for an advertiser are stored, A correspondence unit that associates at least one advertiser information from the two or more advertiser information of the advertiser management unit with each of the one or more hashtags of the hashtag management unit, A server comprising: an advertiser information storage unit that stores the advertiser information associated with the aforementioned correspondence unit, in association with the aforementioned hashtag.
3. The aforementioned hashtag management unit includes: The advertising fee information corresponding to each of the one or more hashtags mentioned above is stored. The server according to claim 1 or claim 2, further comprising a billing processing unit for billing an advertiser corresponding to the advertiser information stored by the advertiser information storage unit for the advertising fee indicated by the advertising fee information associated with the hashtag.
4. An information processing method implemented by a hashtag management unit which stores one or more hashtags obtained by adding "#" to one or more tags acquired from the tag source information on the page, an advertiser recruitment unit, an application receiving unit, and an advertiser information storage unit, The advertiser recruitment step involves the advertiser recruitment unit transmitting recruitment screen information, which is screen information for recruiting advertisers for each of the one or more hashtags of the hashtag management unit, to one or more terminal devices. The application receiving unit, in response to the transmission of the recruitment screen information, receives application information containing advertiser information about the advertiser, associated with hashtags, from a terminal device in the application receiving step. An information processing method comprising: an advertiser information storage step in which the advertiser information storage unit stores the advertiser information received by the application receiving unit in association with the hashtag.
5. An information processing method realized by a hashtag management unit which stores one or more hashtags obtained by adding "#" to one or more tags acquired from tag source information on a page, an advertiser management unit which stores two or more advertiser information items related to advertisers, a correspondence unit, and an advertiser information storage unit, The corresponding unit performs a corresponding step of associating each of the one or more hashtags in the hashtag management unit with at least one advertiser information from the two or more advertiser information in the advertiser management unit, An information processing method comprising: an advertiser information storage step in which the advertiser information storage unit stores the advertiser information associated with the corresponding unit in association with the hashtag.
6. A computer that can access the hashtag management section, which stores one or more hashtags obtained by adding "#" to one or more tags acquired from the tag source information on the page, An advertiser recruitment unit transmits recruitment screen information, which is screen information for recruiting advertisers for each of the one or more hashtags of the hashtag management unit, to one or more terminal devices. In response to the transmission of the aforementioned recruitment screen information, the application receiving unit receives application information containing advertiser information about the advertiser, associated with hashtags, from the terminal device. A program to cause the application receiving unit to function as an advertiser information storage unit that stores the advertiser information it receives in association with the hashtag.
7. A computer that can access a hashtag management unit, which stores one or more hashtags obtained by adding "#" to one or more tags acquired from the tag source information on the page, and an advertiser management unit, which stores two or more advertiser information items about advertisers, A correspondence unit that associates at least one advertiser information from the two or more advertiser information of the advertiser management unit with each of the one or more hashtags of the hashtag management unit, A program for causing the aforementioned correspondence unit to function as an advertiser information storage unit that stores the advertiser information associated with the aforementioned correspondence unit in association with the aforementioned hashtag.
Citation Information
Patent Citations
Search ad selection based on user behavior
JP2013524382A