JP2022149912A - Information processing apparatus - Google Patents

Abstract

To acquire a wide retrieval result.SOLUTION: An information processing apparatus includes: a storage unit that stores a retrieval target associated with at least one first keyword representing an emotion; and a control unit that performs receiving an input of a second keyword used in the retrieval and representing an emotion, acquiring the retrieval target associated with the first keyword matching the second keyword from the storage unit as a retrieval result, and outputting the acquired retrieval target. The retrieval target may be any of a person, an object, a place, and a thing.SELECTED DRAWING: Figure 8

Description

The present disclosure relates to an information processing device that performs searches.

A technology for searching and acquiring event information including date information and keywords, which is information about events collected from home pages on the Web, using keywords received from the outside is disclosed (for example, Patent Document 1). .

JP 2009-075757 A

In keyword searches, keywords are specified by the user. Keywords specified by users are often words that describe things or things that are being searched for. However, there is a high possibility that a search using such keywords will yield only the expected search results.

An object of the present disclosure is to provide an information processing method capable of acquiring a wide range of search results.

One aspect of the present disclosure is
a storage unit that stores search targets associated with at least one first keyword that expresses emotion;
Receiving input of a second keyword that expresses emotion and is used for searching;
Acquiring and outputting a search target associated with the first keyword that matches the second keyword from the storage unit as a search result;
a control unit that executes
It is an information processing device comprising

According to the present disclosure, a wide range of search results can be obtained.

FIG. 1 is a diagram showing an example of the system configuration of an event planning system according to the first embodiment. FIG. 2 is an example of the hardware configuration of the center server and user terminals. FIG. 3 is a diagram showing an example of functional configurations of a center server and user terminals. FIG. 4 is a diagram showing an example of information held in a user information database. FIG. 5 is an example of information held in the event information database. FIG. 6 is an example of a user registration screen of a user terminal. FIG. 7 is an example of an event registration screen of a user terminal. FIG. 8 is an example of a search screen of a user terminal. FIG. 9 is an example of a search result display screen of a user terminal. FIG. 10 is an example of a flowchart of processing of the user terminal. FIG. 11 is an example of a flowchart of processing of the center server.

One aspect of the present disclosure is a storage unit that stores a search target associated with at least one first keyword that expresses emotion, and receives input of a second keyword that expresses emotion, which is used for the search. and a control unit that acquires and outputs search results associated with a first keyword that matches a second keyword from a storage unit.

The information processing apparatus is, for example, a computer such as a server. The server may be, for example, a web server. The information processing device includes, for example, a control unit such as a processor. A search target is a person, an object, a place, an event, or the like. Events include, for example, events held by gathering a predetermined number of people at a predetermined location, events distributed on the web, crowdfunding, and the like. Events include, for example, dinner parties, experience meetings, consultation meetings, lectures, classrooms, concerts, and tours. Note that "things" that can be searched are not limited to these.

The first keyword and the second keyword that express emotions are, for example, pleasant, happy, interesting, happy, moving, calm, frustrated, sad, distressed, etc., and may be predefined or may be defined by the user. You may enter freely. A plurality of second keywords may be used for the search. When a plurality of second keywords are used for searching, search targets associated with matching first keywords may be obtained as search results for all of the second keywords. Alternatively, a search target associated with a first keyword matching at least one of a plurality of second keywords may be acquired as a search result.

According to one aspect of the present disclosure, since emotions are subjective and often differ from user to user, searching with keywords that express emotions increases the possibility of obtaining unexpected search results. can be done. As a result, a wide range of search results can be obtained, and an opportunity to broaden one's view of the world can be obtained.

In addition, the present disclosure provides an information processing apparatus that executes the information processing method described above, a program for causing a computer to execute the information processing method described above, or a non-temporary storage medium that stores the program in a computer-readable form. can also be captured.

Embodiments of the present disclosure will be described below based on the drawings. The configurations of the following embodiments are examples, and the present disclosure is not limited to the configurations of the embodiments.

<First Embodiment>
FIG. 1 is a diagram showing an example of the system configuration of an event planning system 100 according to the first embodiment. The event planning system 100 is a system that provides an SNS (social network service) for planning events and recruiting participants. In the first embodiment, an event is an activity that gathers a predetermined number of people at a predetermined place. Specifically, the event includes a dinner party, an experience meeting, a consultation meeting, a lecture, a classroom, a concert, a tour, and the like. The event may also be held on the web.

The event planning system 100 is a system that publishes places, things, and things that each user is interested in or that can be provided, and supports holding an event between users who sympathize with them. Places, things, and things that each user is interested in or can provide are hereinafter referred to as resources. Things are intangible, such as events and experiences. Objects are tangible and include, for example, people. In the event planning system 100, resources related to users and events are published, and searches for users and events are performed using the published resources as clues. In other words, the event planning system 100 is a system that aims to connect users with resources.

The event planning system 100 includes a center server 1 and user terminals 2 . Although only one user terminal 2 is shown in FIG. 1, the event planning system 100 includes a plurality of user terminals.

The center server 1 and the user terminal 2 are each connected to a network N1 and can communicate with each other through the network N1. Network N1 is, for example, the Internet.

A client application program of the event planning system 100 is installed in the user terminal 2 . A user of the user terminal 2 registers in the event planning system 100 by inputting user information into the user terminal 2 and transmitting a user information registration request to the center server 1 . User information includes, for example, account name, activity area, and information on resources that the user can provide.

Also, when the user of the user terminal 2 plans an event, for example, information about the event is input to the user terminal 2 . The information about the event includes, for example, the name of the event, the area where the event is held, and information on resources related to the event. Information about an event is hereinafter referred to as event information.

Resources included in user information and event information are tagged. In the first embodiment, resource tags are words that express emotions. A tag attached to a resource is an example of a "first keyword."

The user terminal 2 transmits an event disclosure request to the center server 1 according to the user's operation. When the center server 1 receives an event publication request from the user terminal 2, the center server 1 publishes the event information of the event on the website of the event planning system 100. FIG.

For example, when the user of the user terminal 2 wants to search for a user or an event, he/she inputs a word expressing emotion as a search keyword to the user terminal 2 . The user terminal 2 transmits a search request and a search keyword to the center server 1 according to the user's operation. When receiving a search request from the user terminal 2, the center server 1 acquires user information or event information including a tag matching the search keyword received together with the search request, and transmits it to the user terminal 2 as a search result. The search keyword is an example of the "second keyword".

According to the first embodiment, users or events are searched with keywords that express emotions. As a result, a user or an event that matches the emotion indicated by the search keyword is acquired. Keywords (tags) representing emotions associated with users and events are subjectively assigned by users, so that different users may have different emotions even for the same subject. Therefore, according to the first embodiment, there is a high possibility that a search result different from the search result expected by the searching user can be obtained, and a new encounter can be brought to the user.

In the first embodiment, the user information and the event information include resource information, and the resource is tagged with an emotion. Therefore, searching for users or events by tags is synonymous with searching for resources. However, the present invention is not limited to this, and neither the user information nor the event information may include resource information, and the user and the event may be directly tagged with emotions. It should be noted that attaching a tag is synonymous with associating a keyword representing an emotion.

FIG. 2 shows an example of the hardware configuration of the center server 1 and the user terminal 2. As shown in FIG. The center server 1 includes a CPU 101, a memory 102, an external storage device 103, and a communication section 104 as a hardware configuration. The memory 102 and the external storage device 103 are computer-readable recording media. The center server 1 is an example of an "information processing device".

The external storage device 103 stores various programs and data used by the CPU 101 when executing each program. The external storage device 103 is, for example, an EPROM (Erasable Programmable ROM) or a hard disk drive. The programs held in the external storage device 103 include, for example, an operating system (OS), a control program for the event planning system 100, and various other application programs.

The memory 102 is a storage device that provides the CPU 101 with a storage area and a work area for loading programs stored in the external storage device 103 and is used as a buffer. The memory 102 is, for example, ROM (Read Only Memory), RAM (Random
including semiconductor memory such as Access Memory).

The CPU 101 executes various processes by loading the OS and various application programs stored in the external storage device 103 into the memory 102 and executing them. The number of CPUs 101 is not limited to one, and a plurality of CPUs may be provided. The CPU 101 is an example of a "controller".

The communication unit 104 is, for example, a wired network card such as a LAN (Local Area Network) or a dedicated line, and connects to the network N1 through an access network such as the LAN. The hardware configuration of the center server 1 is not limited to that shown in FIG.

The user terminal 2 includes, for example, a CPU 201, a memory 202, an external storage device 203, a wireless communication section 204, and a touch panel display 205 as a hardware configuration. However, in FIG. 2, hardware related to the event planning system 100 is extracted and displayed, and the hardware configuration of the user terminal 2 is not limited to that shown in FIG.

The CPU 201, the memory 202, and the external storage device 203 are the same as the CPU 101, the memory 102, and the external storage device 103, respectively, so descriptions thereof will be omitted. A client application program for the event planning system 100 is stored in the external storage device 203 .

The wireless communication unit 204 is, for example, a wireless communication circuit compatible with mobile communication systems such as 5G (5th Generation), LTE (Long Term Evolution), LTE-Advanced, and 3G, or wireless communication systems such as WiFi. be. The wireless communication unit 204 connects to an access network by wireless communication, and connects to the network N1 through the access network.

The touch panel display 205 is an example of an input device and an output device. For example, a user operation is input to the touch panel display 205 and the content of the user operation is output to the CPU 201 . Further, the touch panel display 205 displays image data according to instructions from the CPU 201 .

FIG. 3 is a diagram showing an example of functional configurations of the center server 1 and the user terminal 2. As shown in FIG. The user terminal 2 includes a control unit 21 and a screen data storage unit 22 as functional configurations. These functional components are achieved by the CPU 201 of the user terminal 2 executing the client application program of the event planning system 100, for example.

Through the touch panel display 205 , the control unit 21 receives user operation input such as a user information registration request, an event disclosure request, a search request, and an event participation request. The control unit 21 transmits, for example, a user information registration request, an event disclosure request, a search request, an event participation request, and the like to the center server 1 through the wireless communication unit 204 . Further, the control unit 21 reads a screen corresponding to a user's operation and data received from the center server 1 from the screen data storage unit 22 and causes the touch panel display 205 to output the screen.

The screen data storage unit 22 is created in the storage area of the external storage device 203 . The screen data storage unit 22 holds screen data in the client application program of the event planning system 100 . Details of the processing of the control unit 21 and details of the screen data held in the screen data storage unit 22 will be described later.

Next, the center server 1 has a control unit 11, a user information DB 12, and an event information DB 13 as functional configurations. These functional configurations are achieved, for example, by the CPU 101 of the center server 1 executing the control program of the event planning system 100 stored in the external storage device 103 .

The control unit 11 manages user information and event information. The control unit 11 receives a user information registration request from the user terminal 2 through the communication unit 104 . Upon receiving a user information registration request from the user terminal 2, the control unit 11 updates corresponding user information in the user information DB 12, which will be described later.

Also, the control unit 11 receives, for example, a request to publish an event and a request to participate in the event from the user terminal 2 through the communication unit 104 . Event information is also received along with the event publication request. Along with the request to participate in the event, the identification information of the target event and the user identification information of the user of the user terminal 2 that is the transmission source are also received.

When an event disclosure request is received, the control unit 11 registers the event information received together with the disclosure request in the event DB 13, and makes the event available for publication on the website of the event planning system 100.例文帳に追加When receiving a request to participate in an event, the control unit 11 adds the information of the user who sent the participation request to the event information in the event information DB 13, which will be described later, as a participating user.

Also, the control unit 11 receives a search request from the user terminal 2 through the communication unit 104 . A search target and search criteria are also received along with the search request. A search target is either a user or an event in the first embodiment. The search condition includes at least a search keyword. The search keyword is a tag representing an emotion in the first embodiment. The search conditions may include search keywords as well as conditions such as the area where the event is held or the user's activity area.

Upon receiving a search request from the user terminal 2 , the control unit 11 extracts search targets that match the search conditions, and transmits the extracted search results to the user terminal 2 . When the search target is a user, the control unit 11 extracts from the user information DB 12 user information having a resource attached with a tag matching the keyword included in the search target as a search result. When the search target is an event, the control unit 11 extracts, from the event information DB 13, event information having a resource attached with a tag that matches the keyword included in the search target as the search result.

A user information DB 12 and an event information DB 13 are created in the storage area of the external storage device 103 . The user information DB 12 holds user information about users. The event information DB 13 holds event information about events. Details of the information held in the user information DB 12 and the event information DB 13 will be described later. The functional configurations of the center server 1 and user terminals 2 are not limited to the example shown in FIG.

FIG. 4 is a diagram showing an example of information held in the user information DB 12. As shown in FIG. The user information DB 12 holds user information about users. One record of the user information DB 12 corresponds to user information of one user. One record of the user information DB 12 includes, for example, user ID, account name, activity area, resource #1, . . . , and resource #N fields. N is a positive integer.

User identification information is stored in the user ID field. The user identification information is uniquely assigned within the event planning system 100 by the control unit 11 at the time of user registration, for example. A user's account name is stored in the account name field. Information indicating the user's activity area is stored in the activity area field. The information indicating the user's activity area may be, for example, a code.

Resource #1, . . . , and resource #N fields contain resource and tag subfields, respectively. The resource subfield stores a character string indicating the resource. The tag subfield stores information indicating keywords that express emotions. Information indicating a keyword representing emotion may be, for example, a character string or a code. A plurality of tags may be attached to one piece of resource information.

account name, region of activity, resource #1, . . . , and Resource #N field values are specified by the user. The information held in the user information DB 12 shown in FIG. 4 is an example, and the information held in the user information DB 12 is not limited to the example shown in FIG.

FIG. 5 is an example of information held in the event information DB 13. As shown in FIG. The event information DB 13 stores event information about events. One record of the event information DB 13 corresponds to event information of one event. One record of the event information DB 13 includes, for example, an event ID, a project user ID, an event name, an event area, a participating user ID, resource #1, . . . , and resource #M fields. M is a positive integer.

The event ID field stores event identification information. The event identification information is uniquely given in the event planning system 100 by the control unit 11, for example. The planning user ID field stores the user identification information of the planning user. An event name is stored in the event name field. The holding region field stores information indicating the planned holding region of the event. User identification information of users participating in the event is stored in the participating user ID field.

Resource #1, . . . , and resource #M fields contain resource and tag subfields, respectively. The resource subfield stores a character string indicating the resource. The tag subfield stores information indicating keywords that express emotions. Information indicating a keyword representing emotion may be, for example, a character string or a code. A plurality of tags may be attached to one piece of resource information.

An entry in the event information DB 13 is created by the control unit 11 when an event disclosure request is received from the user terminal 2 . Planning user ID, event name, venue area, resource #1, . . . , and resource #M field values are obtained from the event information received with the event publication request. The value of the event ID field is given when the control unit 11 receives an event disclosure request. In the participating user ID field, when a participation request for the event is received from the user terminal 2, the control unit 11 stores the user identification information of the participating user received together with the participation request. The information held in the event information DB 13 shown in FIG. 5 is an example, and the information held in the event information DB 13 is not limited to the example shown in FIG.

6 to 8 are screen examples of the user terminal 2. FIG. FIG. 6 is an example of a user registration screen of the user terminal 2. As shown in FIG. The user registration screen is a screen for registering information when registering a user to the event planning system 100 . The user registration screen is provided with fields for inputting, for example, an account name, activity area, resource information, and tags. Text can be freely entered in the input fields for the account name and resource information. The input of activity area and tag is, for example, selected from a drop menu list. The tag's drop menu list is filled with sentimental phrases.

When the “Register” button at the bottom of the screen is selected, a user operation requesting registration of user information is input to the user terminal 2 . When a user operation for requesting user information registration is input, the control unit 21 transmits the user information input on the user registration screen and the user information registration request to the center server 1 . The user information transmitted at this time includes, for example, user identification information, account name, activity area, resources, and tags attached to resources.

Upon receiving a user information registration request from the user terminal 2, the control unit 11 of the center server 1 gives user identification information to the user and registers new user information in the user information DB 12 (see FIG. 4). Note that the user registration screen shown in FIG. 6 is an example, and the configuration of the user registration screen is not limited to the example shown in FIG.

FIG. 7 is an example of an event registration screen of the user terminal 2. As shown in FIG. The event registration screen is a screen for inputting information when drafting an event. The event registration screen is displayed by menu operation, for example.

The event registration screen is provided with entry fields for, for example, the event name, venue area, resource information related to the event, and tags to be assigned to resources. Text can be freely entered in the entry fields for the event name and resource information related to the event. The venue and tag are selected from, for example, a pull-down menu and entered. It should be noted that it is not necessary to enter the location of the event. The tag's drop menu list is filled with sentimental phrases.

On the event registration screen shown in FIG. 7, a public button is provided at the bottom of the screen. When the public button is selected, a user operation requesting public disclosure of the event is input to the user terminal 2 , and the control unit 21 of the user terminal 2 transmits the public request and the event information to the center server 1 . The event information transmitted to the center server 1 at this time includes, for example, an event name,
The event area, resource information related to the event, and tags attached to resources are included. However, the venue area will be sent if there is an input.

Upon receiving an event disclosure request from the user terminal 2, the control unit 11 of the center server 1 adds event identification information to the event and registers the event information in the event information DB 13 (see FIG. 5). Note that the event registration screen shown in FIG. 7 is an example, and the configuration of the event registration screen can be changed as appropriate according to the embodiment.

FIG. 8 is an example of a search screen of the user terminal 2. As shown in FIG. The search screen is a screen for searching users or events from tags. The search screen is displayed by menu operation, for example. The search screen includes, for example, radio buttons for selecting a search target from users and events, and input fields for a target area and a tag as search conditions. The target area and tag are selected and input from, for example, a pull-down menu. Note that it is not necessary to enter the activity area. The tag's drop menu list is filled with sentimental phrases.

A search start button is provided on the search screen, and when the search start button is selected, a user operation requesting a search is input to the user terminal 2 . When a user operation for a search request is input, the control unit 21 of the user terminal 2 transmits the search request, the search target, and the input search conditions to the center server 1 . Upon receiving a search request from the user terminal 2, the control unit 11 of the center server 1 searches for user information from the user information DB 12 or event information from the event information DB 13, which is a search target using the received search conditions. and transmits the search result to the user terminal 2 . Upon receiving the search results from the center server 1, the control unit 21 of the user terminal 2 displays the search results.

FIG. 9 is an example of a search result display screen of the user terminal 2. As shown in FIG. The search result display screen is, for example, a screen that displays search results when searching is performed from the search screen shown in FIG. FIG. 9 shows an event search result display screen.

The event search result display screen shown in FIG. 9 includes a search condition and a display column for the event acquired as the search result. The display column for the event includes the event name, the planning user's account name, the location where the event is held, resource information associated with the event, and tags attached to the resource. The information contained in the display column for each event in the event search result display screen is the search result by the center server 1 .

In addition, the display column for the event shown in FIG. 9 includes a wish to participate button. When the desired participation button is selected, a user operation requesting participation in the event is input to the user terminal 2 . The control unit 21 of the user terminal 2 transmits a request for participation in the event to the center server 1 when a user operation requesting participation in the event is input. For example, user identification information and corresponding event identification information are also transmitted together with the event participation request.

Upon receiving the event participation request from the user terminal 2, the control unit 11 of the center server 1 updates the record of the event in the event information DB 13 (FIG. 5). For example, the control unit 11 adds the user identification information received together with the participation request to the participating user ID field of the record of the event in the event information DB 13 .

<Process flow>
FIG. 10 is an example of a flowchart of processing of the user terminal 2 . The processing shown in FIG. 10 is repeatedly executed in the user terminal 2 while the client application program of the event planning system 100 is being executed, for example. 10 is executed by the CPU 201 of the user terminal 2, but for the sake of convenience, functional components will be mainly described.

In OP101, the control unit 21 determines whether or not a user operation has been input. In the first embodiment, user operations input to the user terminal 2 include, for example, user information registration requests, event disclosure requests, search requests, and event participation requests.

If a user operation has been input (OP101: YES), the process proceeds to OP102. If no user operation has been input (OP101: NO), the process shown in FIG. 10 ends.

In OP102, the control unit 21 transmits to the center server 1 information according to the user operation input in OP101. For example, when a user operation requesting registration of user information is input, the control unit 21 transmits the user information registration request and the user information to the center server 1 . For example, when a user operation requesting disclosure of an event is input, the control unit 21 transmits an event disclosure request and event information to the center server 1 . For example, when a search request user operation is input, the control unit 21 transmits a search request, a search target (user or event), and search conditions to the center server 1 . For example, when a user operation requesting participation in an event is input, the control unit 21 transmits the request for participation in the event, the user identification information, and the event identification information of the target event to the center server 1 . After that, the processing shown in FIG. 10 ends. Note that the processing of the user terminal 2 is not limited to the processing shown in FIG. 10, and can be changed as appropriate according to the embodiment.

FIG. 11 is an example of a flow chart of processing of the center server 1 . The processing shown in FIG. 11 is repeatedly executed at a predetermined cycle. 11 is executed by the CPU 101 of the center server 1, but for the sake of convenience, functional components will be mainly described.

In OP201, the control unit 11 determines whether or not a user information registration request has been received from the user terminal 2. FIG. If a user information registration request has been received from the user terminal 2 (OP201: YES), the process proceeds to OP202. If a user information registration request has not been received from the user terminal 2 (OP201: NO), the process proceeds to OP203.

In OP202, the control unit 11 newly registers, for example, the received user information record in the user information DB 12 in response to the user information registration request received from the user terminal 2 (FIG. 4). After that, the processing shown in FIG. 11 ends.

In OP203, the control unit 11 determines whether a search request has been received from the user terminal 2 or not. If a search request has been received from the user terminal 2 (OP203: YES), the process proceeds to OP204. If a search request has not been received from the user terminal 2 (OP203: NO), the process proceeds to OP206.

In OP204, the control unit 11 searches the user information DB 12 or the event information DB 13 for the search target received together with the search request using the search condition received together with the search request. The search conditions include at least information indicating tags representing emotions. If the search target is a user, the control unit 11 acquires, from the user information DB 12, user information whose tag subfield value matches the information indicating the tag included in the search condition as a search result (Fig. 4). The user information transmitted to the user terminal 2 as a search result includes user identification information, an account name, resource information to which the same tag as the tag included in the search condition is attached, and the tag attached to the resource information. may be included. If the search target is an event, the control unit 11 acquires, from the event information DB 13, event information whose tag subfield value matches the information indicating the tag included in the search condition as a search result (Fig. 5). The event information transmitted to the user terminal 2 as a search result includes identification information of the event, user identification information and account name of the planning user, event name, event area, resource information, and the resource information. Tags may be included.

In OP205, the control unit 11 transmits the search result of OP204 to the user terminal 2. FIG. After that, the processing shown in FIG. 11 ends.

In OP206, the control unit 11 determines whether or not an event disclosure request has been received from the user terminal 2. If an event disclosure request is received from the user terminal 2 (OP206: YES), the process proceeds to OP207. If an event disclosure request has not been received from the user terminal 2 (OP206: NO), the process proceeds to OP208.

In OP207, the control unit 11 registers in the event information DB 13 the event information received together with the event publication request. After that, the processing shown in FIG. 11 ends.

In OP208, the control unit 11 determines whether or not a request to participate in the event has been received from the user terminal 2. If a request to participate in the event has been received (OP208: YES), the process proceeds to OP209. If a request to participate in the event has not been received from the user terminal 2 (OP208: NO), the process shown in FIG. 11 ends.

In OP209, the control unit 11 updates the event information DB 13 in response to the event participation request received from the user terminal 2. FIG. For example, when a request to participate in an event is received from the user terminal 2, the control unit 11 assigns the user identification information received together with the participation request to the event identification information received together with the participation request in the event information DB 13. Add to the participating user ID field of the record (Fig. 5). After that, the processing shown in FIG. 11 ends. Note that the processing of the center server 1 is not limited to the processing shown in FIG. 11, and can be changed as appropriate according to the embodiment.

<Action and effect of the first embodiment>
According to the first embodiment, users or events are tagged with emotions, and searched with keywords that express emotions. Emotions are abstract things that depend on the subjectivity of each user. Therefore, by performing a search using keywords that express emotions, the possibility of obtaining unexpected search results increases, and a wide range of search results can be obtained.

<Other embodiments>
The above-described embodiment is merely an example, and the present disclosure can be modified as appropriate without departing from the scope of the present disclosure.

The event planning system 100 according to the first embodiment is intended for planning events that are actually held by a plurality of people. It can also be applied to activities such as funding that are conducted by a plurality of operating users.

In the first embodiment, the wording expressing emotion used as the tag attached to the resource is selected from options prepared in advance, but is not limited to this, and may be freely input by the user. In this case, the center server 1 may determine whether or not the wording as a tag input by the user is a wording expressing an emotion. For example, a trained model may be used to determine whether or not a wording as a tag input by the user is a wording expressing an emotion. The center server 1 may not accept the tag text input by the user if it does not express emotion.

Further, in the first embodiment, the center server 1 performs the search using the keyword representing emotion, but the user terminal 2 may perform the search using the keyword representing emotion, for example.

The processes and means described in the present disclosure can be freely combined and implemented as long as there is no technical contradiction.

Also, the processing described as being performed by one device may be shared and performed by a plurality of devices. Alternatively, processes described as being performed by different devices may be performed by one device. In a computer system, it is possible to flexibly change the hardware configuration (server configuration) to implement each function.

The present disclosure can also be implemented by supplying a computer program implementing the functions described in the above embodiments to a computer, and reading and executing the program by one or more processors of the computer. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. A non-transitory computer-readable storage medium is any type of disk such as, for example, a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), Including read only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards, flash memory, optical cards, any type of medium suitable for storing electronic instructions.

Reference Signs List 1 Center server 2 User terminal 11 Control unit 12 User information database 13 Event information database 21 Control unit 22 Screen data storage unit 100 Event planning system 101, 201 CPU
102, 202... Memory 103, 203... External storage device 104... Communication unit 204... Wireless communication unit 205... Touch panel display

Claims (1)

a storage unit that stores search targets associated with at least one first keyword that expresses emotion;
Receiving input of a second keyword that expresses emotion and is used for searching;
Acquiring and outputting a search target associated with the first keyword that matches the second keyword from the storage unit as a search result;
a control unit that executes
Information processing device.

Images