Recommendation device, recommendation method, and recommendation program

Abstract

The present invention supports child-rearing by recommending experiential events which are for children of a young age and which meet the needs of a family. A recommendation device (1) is provided with: an acquisition unit (11) that acquires attribute information, which includes information about members of the family of a user, and desired conditions for participation of at least a member of the family other than the user in an experiential event; an identification unit (12) that, on the basis of the attribute information and the desired conditions, identifies an experiential event that is suitable at least to the member, from a database in which information about a plurality of experiential events is registered; and a recommendation unit (13) that recommends to the user an identified experiential event.

Description

[Technical field]

[0001] The present invention relates to a recommendation device, system, method, and program, and more particularly to a recommendation device, system, method, and program for recommending experiential events. [Background technology]

[0002] Patent Document 1 discloses a technology related to an information processing device that searches for facilities desired by users. The information processing device determines the relationship between two users based on their attributes, and searches for facilities that correspond to the attributes of one of the users and correspond to the relationship based on the attributes of the facilities.

[0003] Patent Document 2 discloses a technology related to an information trading device for trading personal information. The information trading device acquires user information from users who have agreed to provide the user information, and generates demand information according to the acquisition status. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-030469 A [Patent Document 2] JP 2015-118632 A Summary of the Invention [Problem to be solved by the invention]

[0005] Parents of child-rearing age have a need to provide their young children with education through hands-on experiences. However, with the increase in dual-income couples and the increase in educational content, it is difficult to find experiential events for young children that meet the needs of the family from among the many educational content options.

[0006] The present disclosure has been made to solve such problems, and aims to provide a recommendation device, system, method, and program for supporting child-rearing by recommending experiential events for young children that meet the needs of families. [Means for solving the problem]

[0007] A recommendation device according to a first aspect of the present disclosure, an acquisition unit that acquires attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; an identification unit that identifies at least an experience-based event suitable for the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation unit that recommends the identified experience-based event to the user; Equipped with.

[0008] A recommendation system according to a second aspect of the present disclosure includes: A user terminal of a user; A recommendation device, The recommendation device includes: an acquisition unit that acquires, from the user terminal, attribute information including information on family members of the user and desired conditions for the family members other than the user to participate in at least an experiential event; an identification unit that identifies at least an experience-based event suitable for the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation unit that recommends the identified experiential event to the user terminal; Equipped with.

[0009] A recommendation method according to a third aspect of the present disclosure includes: The computer Acquire attribute information including information on family members of the user and desired conditions for at least family members other than the user to participate in the experience-based event; Identifying at least one experience-based event suitable for the member from a database in which information on a plurality of experience-based events is registered based on the attribute information and the desired conditions; The identified experience-based event is recommended to the user.

[0010] A recommendation program according to a fourth aspect of the present disclosure, An acquisition process for acquiring attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; a process of identifying an experience-based event suitable for at least the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation process for recommending the identified experiential event to the user; to be executed by the computer. Effect of the Invention

[0011] The present disclosure can provide a recommendation device, system, method, and program for supporting parenting by recommending experiential events for young children that meet the needs of a family. [Brief description of the drawings]

[0012] [Figure 1] 1 is a block diagram showing a configuration of a recommendation device according to a first embodiment. [Diagram 2] 4 is a flowchart showing the flow of the recommendation method according to the first embodiment. [Diagram 3] FIG. 11 is a block diagram showing the overall configuration of a recommendation system according to a second embodiment. [Figure 4] FIG. 11 is a block diagram showing a configuration of a user terminal according to the second embodiment. [Diagram 5] FIG. 11 is a block diagram showing a configuration of an authentication device according to a second embodiment of the present invention. [Figure 6] FIG. 11 is a block diagram showing a configuration of a recommendation device according to a second embodiment. [Figure 7] FIG. 11 is a diagram showing an example of a registration screen for user information according to the second embodiment. [Figure 8] 13 is a flowchart showing the flow of a user information registration process according to the second embodiment. [Figure 9] 10 is a flowchart showing the flow of face information registration processing by the authentication device according to the second embodiment. [Figure 10] 11 is a flowchart showing the flow of a recommendation process according to the second embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a recommendation screen for an experience-based event according to the second embodiment. [Figure 12] 13 is a flowchart showing the flow of a process for registering images captured during an event according to the second embodiment. [Figure 13] 11 is a flowchart showing the flow of face authentication processing by the authentication device according to the second embodiment. [Figure 14] FIG. 11 is a diagram showing an example of a registration screen for an event experience record according to the second embodiment. [Figure 15] FIG. 11 is a diagram showing an example of a registration screen for a growth record according to the second embodiment. [Figure 16] FIG. 11 is a diagram showing an example of a display screen of an event experience record by a host according to the second embodiment. [Figure 17] 13 is a flowchart showing the flow of a re-recommendation process according to the second embodiment. [Figure 18] FIG. 11 is a diagram showing an example of a re-recommendation screen for an experiential event according to the second embodiment. [Figure 19] FIG. 11 is a block diagram showing the overall configuration of a recommendation system according to a third embodiment. [Figure 20] FIG. 11 is a block diagram showing a configuration of a recommendation device according to a third embodiment. [Figure 21] FIG. 13 is a sequence diagram showing the flow of an example of a recommendation process including auxiliary information according to the third embodiment. [Figure 22] FIG. 13 is a sequence diagram showing the flow of another example of the recommendation process including auxiliary information according to the third embodiment. [Figure 23]FIG. 13 is a sequence diagram showing the flow of a new event registration process according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.

[0014] <Embodiment 1> FIG. 1 is a block diagram showing the configuration of a recommendation device 1 according to the first embodiment. The recommendation device 1 is an information processing device for recommending to a user an experiential event in which at least members of the user's family other than the user can participate. Here, the recommendation device 1 may be connected to a predetermined terminal through a communication network (not shown, hereinafter, the communication network may also be simply referred to as a network) or a predetermined wireless communication. The network may be wired or wireless, and may use any type of communication protocol. The terminal may input to the recommendation device 1 and perform processing according to the output from the recommendation device 1. The terminal may be a user terminal operated by a user.

[0015] The recommendation device 1 includes an acquisition unit 11, a specification unit 12, and a recommendation unit 13. The acquisition unit 11 acquires attribute information of a user and desired conditions for participating in an experiential event. Here, the attribute information of the user includes information on members of the user's family. For example, if the user is a parent, the family members are the user's spouse, children, relatives, blood relatives, or people equivalent thereto. The desired conditions are desired conditions for at least members of the user's family other than the user to participate in an experiential event. The desired conditions may include the user's own wishes and the wishes of other members. The desired conditions may also include the members' specialties and preferences. The specification unit 12, which will be described later, specifies an experiential event suitable for the member based on the member's specialties and preferences, so the specialties and preferences can be considered as desired conditions in a broad sense.

[0016] The identification unit 12 identifies an experiential event suitable for at least the member from a database in which information on a plurality of experiential events is registered, based on the attribute information and the desired conditions. Here, the database may be built into the recommendation device 1 or managed by an external storage device. Here, the experiential event is a participatory event involving real-life experience, and is held at a predetermined time and place, for example. Alternatively, the experiential event may include weekly extracurricular activities, after-school care, etc. Furthermore, the experiential event identified by the identification unit 12 is one that meets the desired conditions of at least the members of the user's family other than the user. Furthermore, the identified experiential event may be one suitable for the user himself or other members of the family.

[0017] The recommendation unit 13 recommends the identified experiential event to the user. For example, the recommendation unit 13 may notify a user terminal operated by the user of information about the identified experiential event.

[0018] 2 is a flowchart showing the flow of the recommendation method according to the first embodiment. First, the acquisition unit 11 acquires attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in an experiential event (S11). Next, the identification unit 12 identifies an experiential event suitable for at least the members from a database in which information on multiple experiential events is registered based on the attribute information and the desired conditions (S12). Then, the recommendation unit 13 recommends the identified experiential event to the user (S13).

[0019] In this manner, in this embodiment, for example, when the members are children of the user, an experiential event suitable for at least the child is identified from a database of many events based on the user's family structure and desired conditions for the event. Therefore, the user who is recommended an experiential event is more likely to participate in the experiential event with the child or the whole family. This is particularly effective when the members are in their early childhood, since an event that takes into account the parents' educational policy and family structure is desirable. Therefore, it is possible to support child rearing by recommending an experiential event for young children that meets the needs of the family.

[0020] The recommendation device 1 includes a processor, a memory, and a storage device, which are not shown in the figure. The storage device stores a computer program that implements the processing of the recommendation method according to this embodiment. The processor loads the computer program from the storage device into the memory and executes the computer program. In this way, the processor realizes the functions of the acquisition unit 11, the identification unit 12, and the recommendation unit 13.

[0021] Alternatively, the acquisition unit 11, the identification unit 12, and the recommendation unit 13 may each be realized by dedicated hardware. Also, a part or all of the components of each device may be realized by a general-purpose or dedicated circuit, processor, or a combination of these. These may be configured by a single chip, or may be configured by multiple chips connected via a bus. A part or all of the components of each device may be realized by a combination of the above-mentioned circuits, etc., and a program. Also, as the processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field-Programmable Gate Array), a quantum processor (quantum computer control chip), etc. can be used.

[0022] In addition, when a part or all of the components of the recommendation device 1 are realized by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged or distributed. For example, the information processing devices, circuits, etc. may be realized as a client-server system, a cloud computing system, etc., in a form in which each is connected via a communication network. In addition, the functions of the recommendation device 1 may be provided in a SaaS (Software as a Service) format.

[0023] <Embodiment 2> The second embodiment is a specific example of the first embodiment. FIG. 3 is a block diagram showing the overall configuration of a recommendation system 1000 according to the second embodiment. The recommendation system 1000 is an information system for recommending experience-based events suitable for members (children) to users (parents). For example, a family F1 includes a user (parent) U11, a member (parent) U12, a member (child) U13, and a member (child) U14. A family F2 includes a member (parent) U22, a member (child) U23, and a user (parent) (not shown). A family F3 includes a user (parent) U31, a member (child) U33, and a member (child) U34. A family F4 includes a user (parent) U41 and a member (child) U43. A user (parent) U11, (a user (parent) of family F2),) U31, and U41 are users of the recommendation system 1000.

[0024] The recommendation system 1000 includes user terminals 101 and 102, an authentication device 200, a recommendation device 300, and a camera 401. The user terminals 101 and 102, the authentication device 200, the recommendation device 300, and the camera 401 are each connected via a network N. Here, the network N is a wired or wireless communication line, for example, the Internet. The camera 401 is installed in an experiential event venue 400 and is an image capturing device capable of network communication. Note that there may be multiple experiential event venues 400 for each event.

[0025] In the following description, the authentication for personal identification is assumed to be face authentication, which is an example of biometric authentication, and the personal identification information is assumed to be face feature information, which is an example of biometric information. However, other technologies using captured images can be applied to the biometric authentication and biometric information. For example, the biometric information may be data (feature amount) calculated from physical characteristics unique to an individual, such as a fingerprint, voiceprint, vein, retina, or iris pattern. Furthermore, the authentication for personal identification may be other than biometric authentication, and the personal identification information may also be other than biometric information. For example, the personal identification information may be, but is not limited to, a combination of an ID and a password, an electronic certificate, a two-dimensional code, and the like.

[0026] The recommendation system 1000 is used, for example, as follows. A user (parent) U11 uses a user terminal 101 to register the composition of family F1, facial images of members (children) U13 and U14, desired conditions for an experiential event, and the like in the recommendation device 300. In response to a recommendation request from the user terminal 101 or at a predetermined timing, the recommendation device 300 identifies an experiential event suitable for members (children) U13 and U14 from an event DB (described below) and presents (recommends) the event to the user terminal 101. The user (parent) U11 uses the user terminal 101 to apply to participate in the recommended experiential event, and goes to the experiential event venue 400 with family F1.

[0027] The experience-type event venue 400 is a venue where the recommended experience-type event is held. Examples of experience-type events include, but are not limited to, one-day agricultural experiences, language hiking, craft classes for each age group, and robot programming classes. Families F2, F3, and F4 are assumed to participate in the experience-type event venue 400 on the day the event is held. (For example, the user (parent) U11 and member (child) U13 of the family F1 may be the user (parent) U41 and member (child) U43 of the family F4.) It is not necessary for all family members to participate in the experience-type event, and at least the members (children) are assumed to participate. For example, the user (parent) U31 of the family F3 is accompanying members (children) U33 and U34, and does not need to enter the experience-type event venue 400.

[0028] The camera 401 captures a scene including participants in an event held in the experience-type event venue 400, and transmits the captured image to the recommendation device 300 via the network N. The camera 401 may capture a video and transmit the video to the recommendation device 300. The recommendation device 300 analyzes the video (a group of captured images) received from the camera 401 and determines whether or not the video contains a face image of a member who has been registered in advance. If the video contains a face image of a member, the recommendation device 300 determines whether or not the storage condition is met by a smile judgment of the video, and stores the video that satisfies the storage condition in the experience history (described later) of the member or his / her family.

[0029] After the event, the user (parent) U41 uses the user terminal 101 to input comments and records regarding the event experience of the member (child) U43, and registers them in the experience history of the recommendation device 300. Furthermore, the user terminal 102, through the operation of the user (parent) U41, retrieves from the experience history images taken during the event of the family member F4, particularly the member (child) U43, and displays them.

[0030] Thereafter, in response to a recommendation request from the user terminal 101 or at a specified timing, the recommendation device 300 identifies experiential events suitable for members (children) U13 and U14 from the event DB (described later) based on the family structure and desired conditions of family F1 as well as their experience history, and presents (recommends) the events to the user terminal 101.

[0031] The user terminal 101 is an information terminal possessed and operated by a user (parent) U11. The user terminal 102 is an information terminal possessed and operated by a user (parent) U41. The user terminals 101 and 102 are, for example, information processing devices such as mobile phone terminals, smartphones, tablet terminals, and notebook computers with cameras. The configuration of the user terminal 102 is the same as that of the user terminal 101, and therefore illustrations and detailed explanations will be omitted below.

[0032] 4 is a block diagram showing the configuration of a user terminal 101 according to the present embodiment 2. The user terminal 101 includes a camera 110, a storage unit 120, a memory 130, a communication unit 140, an input / output unit 150, and a control unit 160.

[0033] The camera 110 is an imaging device that captures images of users and members under the control of the control unit 160. The memory unit 120 is a storage device that stores a program 121 for implementing each function of the user terminal 101. The memory unit 120 includes a storage device including a non-volatile memory such as a flash memory or an SSD (Solid State Drive). The program 121 is a computer program that implements a process for registering user information, a process for applying to participate in an experiential event, a process for acquiring and displaying images captured during an event, a process for registering experience records and growth records, and the like. The program 121 includes a client application for the recommendation device 300 according to this embodiment.

[0034] The memory 130 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 160 is operating. The communication unit 140 is a communication interface with the network N. The input / output unit 150 includes a display device and an input device. The input / output unit 150 is, for example, a touch panel. The control unit 160 is a processor that controls the hardware of the user terminal 101. The control unit 160 loads the program 121 from the storage unit 120 into the memory 130 and executes it. In this way, the control unit 160 realizes the functions of a registration unit 161, an acquisition unit 162, and a display control unit 163.

[0035] The registration unit 161 transmits a request for registration of user information including the composition of family F1, personal information, face images of members (children) U13 and U14, desired conditions for an experiential event, and the like input by the user (parent) U11 to the recommendation device 300 via the network N. As a result, the registration unit 161 registers the user information in the recommendation device 300. Furthermore, the registration unit 161 accepts an operation of application for participation from the user (parent) U11 for an experiential event recommended by the recommendation device 300, and transmits a request for application for participation in the experiential event to the recommendation device 300 via the network N. Furthermore, the registration unit 161 transmits comments (experience information) and evaluation information regarding the event experience of members (children) U13 and U14 input by the user (parent) U11 to the recommendation device 300 via the network N. Furthermore, the registration unit 161 transmits to the recommendation device 300 via the network N information indicating the growth records of the members (children) U13 and U14, which information has been input by the user (parent) U11.

[0036] The acquisition unit 162 acquires information about the experiential event recommended by the recommendation device 300 via the network N, and outputs the acquired information about the experiential event to the display control unit 163. Furthermore, the acquisition unit 162 acquires a group of captured images of any member of the family F1 during the event from the recommendation device 300 via the network N, and outputs the acquired group of captured images to the display control unit 163. Furthermore, the acquisition unit 162 acquires an experience history or growth record of any member of the family F1 from the recommendation device 300 via the network N, and outputs the acquired experience history or growth record to the display control unit 163.

[0037] The display control unit 163 displays on the input / output unit 150 the experience-based event information, the captured images, the experience history, the growth record, and the like input from the acquisition unit 162 .

[0038] The user terminal 101 may transmit a recommendation request for an experiential event to the recommendation device 300 via the network N in response to an operation by the user (parent) U11. The user terminal 101 may also transmit a request to acquire a group of captured images to the recommendation device 300 via the network N in response to an operation by the user (parent) U11. The user terminal 101 may also transmit a request to refer to the experience history and growth record to the recommendation device 300 via the network N in response to an operation by the user (parent) U11.

[0039] At this time, the user terminal 101 includes in the recommendation request, acquisition request, or reference request the user ID of the user (parent) U11 or terminal identification information of the user terminal 101. Alternatively, the user terminal 101 may include at least some facial images of the members of the family F1, such as the user (parent) U11, in the recommendation request, acquisition request, or reference request.

[0040] Returning to FIG. 3, the explanation will be continued. The authentication device 200 is an information processing device that stores facial feature information of users who are members of the user or his / her family. In response to a facial authentication request received from the outside, the authentication device 200 compares the facial image or facial feature information included in the request with the facial feature information of each user, and returns the comparison result (authentication result) to the request source.

[0041] FIG. 5 is a block diagram showing the configuration of an authentication device 200 according to the second embodiment. The authentication device 200 includes a face information DB (DataBase) 210, a face detection unit 220, a feature point extraction unit 230, a registration unit 240, and an authentication unit 250. The face information DB 210 stores a user ID 211 and face feature information 212 of the user ID in association with each other. The face feature information 212 is a set of feature points extracted from a face image. The authentication device 200 may delete the face feature information 212 in the face feature DB 210 in response to a request from a registered user of the face feature information 212. Alternatively, the authentication device 200 may delete the face feature information 212 after a certain period of time has elapsed since the main registration.

[0042] The face detection unit 220 detects a face area included in a registration image for registering face information, and outputs the face area to the feature point extraction unit 230. The feature point extraction unit 230 extracts feature points from the face area detected by the face detection unit 220, and outputs face feature information to the registration unit 240. The feature point extraction unit 230 also extracts feature points included in a face image received from the recommendation device 300 or the like, and outputs the face feature information to the authentication unit 250.

[0043] The registration unit 240 issues a new user ID 211 when registering the facial feature information. The registration unit 240 registers the issued user ID 211 in the facial feature information DB 210 in association with the facial feature information 212 extracted from the registered image. The authentication unit 250 performs face authentication using the facial feature information 212. Specifically, the authentication unit 250 compares the facial feature information extracted from the face image with the facial feature information 212 in the facial information DB 210. If the comparison is successful, the authentication unit 250 specifies the user ID 211 associated with the compared facial feature information 212. The authentication unit 250 returns the presence or absence of a match of the facial feature information to the request source as a facial authentication result. The presence or absence of a match of the facial feature information corresponds to the success or failure of authentication. Incidentally, the facial feature information matches (matches) when the degree of match is equal to or greater than a threshold. Furthermore, if the facial authentication is successful, the facial authentication result includes the specified user ID.

[0044] Returning to Fig. 3, the description will continue. The recommendation device 300 is an example of the recommendation device 1 described above. The recommendation device 300 is an information processing device that performs processes such as registering user information, recommending an experience-based event, applying for an event, registering and providing a group of images captured during an event, and registering and referencing experience history and the like (recommendation method processing). The recommendation device 300 may be redundantly configured with multiple servers, and each functional block may be realized by multiple computers.

[0045] Next, the recommendation device 300 will be described in detail. FIG. 6 is a block diagram showing the configuration of the recommendation device 300 according to the second embodiment. The recommendation device 300 includes a storage unit 310, a memory 320, a communication unit 330, and a control unit 340. The storage unit 310 is an example of a storage device such as a hard disk, a flash memory, or an SSD. The storage unit 310 stores a program 311, user information 312, an event DB 313, and an experience history 314. The program 311 is a computer program in which the processing of the recommendation method according to the second embodiment is implemented.

[0046] The user information 312 is information about a user of the recommendation system 1000 and his / her family, as well as information about desired conditions for experiential events. The user information 312 is information that associates a user ID 3121, family information 3122, personal information 3123, desired conditions 3124, and growth record 3125. The family information 3122 and personal information 3123 are examples of user attribute information. The user ID 3121 is identification information of a user (contractor) of the recommendation system 1000. In the case of family F1, the user ID 3121 is the user ID of the user (parent) U11.

[0047] Family information 3122 is information about the user's family. Family information 3122 is information in which family structure 31220 and member IDs 31221 to 3122n (n is a natural number of 2 or more) are associated with each other. Family structure 31220 is information indicating the family structure of the user. Specifically, family structure 31220 is a collection of information about the relationship, sex, age, etc. of members belonging to the user's family. For example, in the case of family F1, family structure 31220 is information such as father, mother, older brother 5 years old, and younger sister 2 years old. Note that family members are not limited to those who are related by blood or kinship to the user. Member ID 31221, etc. are identification information of each member. For example, in the case of family F1, member ID 31221 is the user ID of user (parent) U11, member ID 31222 is the user ID of member (parent) U12, member ID 31223 is the user ID of member (child) U13, and member ID 31222 is the user ID of member (child) U14. However, member ID 31221 etc. only need to include the user ID of the participant of the experience-based event to be recommended. For example, in family F1, user (parent) U11 considers members (child) U13 and U14 to be participants, and wishes to recommend an experience-based event in which member (child) U13 or U14 can participate. In that case, member ID 31221 etc. only need to include the user ID of members (child) U13 and U14.

[0048] Personal information 3123 includes the residential area (address) of the user and / or family, the user's contact information, payment information, etc. The user's contact information is a telephone number, an application user ID, an email address, etc. Payment information is account information of a financial institution from which the payment amount is debited when paying for participation in a paid experience-based event, credit card information used to pay the payment amount, etc.

[0049] The desired conditions 3124 are information indicating desired conditions for participating in an experience-based event. The desired conditions 3124 include a request 31241 and schedule information 31242. The request 31241 is information indicating a request for an experience-based event for a family including the user. That is, the request 31241 is information indicating desired conditions for the field, content, and schedule of the experience-based event to be recommended. Specifically, the request 31241 may be a request regarding how to spend a holiday, a purpose of the experience, the content of an event that the child wants to experience, the parent's educational policy for the child, and the like. For example, the request 31241 may include an event related to a child's extracurricular activities on Saturday, and an event related to a day trip that the whole family can participate in on Sunday. Alternatively, the request 31241 may include a condition for participating in the event that a 5-year-old brother and a 2-year-old sister can participate in, and a nature experience that the siblings can enjoy as the event content. The schedule information 31242 is existing schedule information of the user's family. The existing schedule information includes an experience-based event for which participation has already been applied for. The schedule information 31242 is an exclusion condition on the schedule of the experience-based event to be recommended, and is a condition that excludes the event from being recommended, and can therefore be considered a desired condition in a broad sense.

[0050] The growth record 3125 is information for recording the progress of growth of each member. For example, the growth record 3125 may include information indicating lessons, skill acquisition goals, and degree of achievement of acquisition associated with the member ID.

[0051] Each of the member IDs 31221 to 3122n described above is information that can be uniquely identified by the user ID 211 managed in the face information DB 210 of the authentication device 200 described above. In other words, the member IDs 31221 to 3122n are information that is the same as or corresponds to the user ID 211 of each member. Therefore, it can be said that the family structure 31220, the personal information 3123, the desired conditions 3124, and the growth record 3125 are substantially associated with the facial feature information 212 of each member via the member ID 31221, etc. Also, the member ID may be used as the user ID 3121. And the member IDs 31221 to 3122n may be associated with the relationship in the family structure, etc. For example, the member IDs 31221 to 3122n may be associated with information that allows a father, a mother, an older brother, and a younger sister to be distinguished from each other.

[0052] The event DB 313 is an example of a database in which information on multiple experience-based events is registered. The event DB 313 includes event information 3131 to 313m (where m is a natural number equal to or greater than 2). The event information 3131 etc. may include the event ID, event name, field, content, date and time, location, participation requirements (target age, clothing, belongings) and the like of the experience-based event.

[0053] The experience history 314 is an event participation history including input information based on the experience of the member who participated in the recommended experience-based event. The experience history 314 is information in which a user ID 3141, event information 3142, member ID 3143, experience information 3144, evaluation information 3145, and a group of captured images 3146 are associated with each other. The user ID 3141 is identification information of a user who applied to participate in the event, and corresponds to the user ID 3121. The user ID 3141 is also a user ID of a user who is a family member of a member who participated in the event. In other words, the user ID 3141 can be said to be a user ID 3121 that includes the member ID 3143 in the family information 3122. The event information 3142 is event information that was applied for and actually participated in by the member. The event information 3142 may include at least the event ID in the event DB 313. The member ID 3143 is identification information of a member who was applied for and actually participated in the event. The experience information 3144 is input information, for example, text information, based on the experience of the members who participated in the experience-based event. The evaluation information 3145 is information indicating the evaluation of the participated experience-based event by the user or members (participants). The evaluation information 3145 may be an index value, for example, an evaluation level value. The captured image group 3146 is a collection of captured images of scenery including participants during the event, which include the members and satisfy predetermined registration conditions. The captured image group 3146 may be a video.

[0054] The memory 320 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information during operation of the control unit 340. The communication unit 330 is a communication interface with the network N.

[0055] The control unit 340 is a processor, that is, a control device, that controls each component of the recommendation device 300. The control unit 340 loads the program 311 from the storage unit 310 into the memory 320 and executes the program 311. In this way, the control unit 340 realizes the functions of an acquisition unit 341, a registration unit 342, an authentication control unit 343, an identification unit 344, a recommendation unit 345, and a determination unit 346.

[0056] The acquisition unit 341 is an example of the acquisition unit 11 described above. The acquisition unit 341 acquires a registration request for user information (registration information) from the user terminal 101 or the like. The registration information includes, for example, family composition, personal information of the user, facial images of members who are to participate in the event, desired conditions for the experiential event, and the like. The acquisition unit 341 acquires a recommendation request and a participation application request for the experiential event, a registration request and an acquisition request for a group of captured images, and a registration or reference request for an experience history and a growth record, and the like.

[0057] The registration unit 342 generates user information 312 based on the acquired user information registration request, and registers the user information 312 in the storage unit 310. Specifically, the registration unit 342 transmits a face information registration request including a face image included in the registration request to the authentication device 200. Then, the registration unit 342 acquires a user ID issued in response to the registration of face information from the authentication device 200. When a plurality of face images are included, the registration unit 342 may transmit a face information registration request for each face image (member). The registration unit 342 may also issue a new user ID. The registration unit 342 may use one of the user IDs issued in response to the registration of face information as the user ID. The registration unit 342 generates user information 312 by using the issued user ID as a member ID and associating the user ID with the family structure, personal information, and desired conditions included in the registration request. Since the member ID is associated with facial feature information as described above, the registration unit 342 can be said to register the biometric information of each member of the user in association with the attribute information and desired conditions as user information.

[0058] Furthermore, when a request to register an experience history (input information) is acquired, the registration unit 342 associates the input information, the experience-based event, and the members, and registers them in the experience history 314. Furthermore, when a request to register a growth record (input information) is acquired, the registration unit 342 associates the growth record 3125 with the user ID 3121, and registers them in the storage unit 310.

[0059] Furthermore, when the determination unit 346 determines that the captured image can be registered, the registration unit 342 registers the captured image in the experience history of the member corresponding to the facial feature information (or member ID) for which face authentication was successful.

[0060] Furthermore, if the registration request includes a user ID, that is, if the user ID has already been issued and the user information has already been registered, or if family information, personal information, desired conditions, or growth records are to be updated, the registration unit 342 updates the user information 312 corresponding to the user ID included in the registration request.

[0061] When the authentication control unit 343 receives a request to register a group of captured images from the camera 401, the authentication control unit 343 extracts a face image from the group of captured images and causes the authentication device 200 to perform face authentication on the extracted face image. That is, the authentication control unit 343 controls biometric authentication using biometric information for captured images of participants taken during the implementation of the recommended experience-based event. For example, the authentication control unit 343 transmits a face authentication request including a face image to the authentication device 200 via the network N and receives a face authentication result from the authentication device 200. The authentication control unit 343 may detect a face area of ​​the user from the face image and include an image of the face area in the face authentication request. Alternatively, the authentication control unit 343 may extract face feature information from the face area and include the face feature information in the face authentication request. The authentication control unit 343 determines whether face authentication has been successful from the received face authentication result. If it is determined that face authentication has been successful, the authentication control unit 343 specifies a user ID included in the face authentication result.

[0062] The identification unit 344 is an example of the identification unit 12 described above. The identification unit 344 identifies an experiential event suitable for at least some members of the family information from the event DB 313 based on the family structure, personal information, and desired conditions. In particular, when the desired conditions 3124 include the request 31241, the identification unit 344 identifies an experiential event that satisfies the request. In addition, when the desired conditions 3124 include the schedule information 31242, the identification unit 344 identifies an experiential event that is held on a date other than the schedule information 31242. In addition, the identification unit 344 may identify an experiential event based on the schedule contents included in the schedule information 31242. For example, if the schedule information 31242 includes an English conversation class every Saturday, the identification unit 344 may identify an English after-school care on weekdays or an English-related event on Sundays as an experiential event. Furthermore, if the family structure 31220 includes attributes of the user's children as members, the identification unit 344 identifies an experiential event in which the age of the children meets the participation requirements. For example, the identification unit 344 extracts a group of keywords, the field of the event, the ages of the members, and the schedule conditions from the family structure, personal information, and desired conditions, and searches the event DB 313 using the extracted various information as search conditions to identify event information that meets the search conditions. If multiple event information that meets the search conditions is found, the identification unit 344 may assign a priority order to the recommendation depending on the degree to which the search conditions are satisfied. The identification unit 344 may further take into account the input information (experience history and growth record) when identifying an experiential event. This allows an experiential event that is more suitable for the needs of the user's family to be identified with high accuracy.

[0063] The identification unit 344 may identify an experiential event using a predetermined model (processing logic). Specifically, the model may input family structure, personal information, and desired conditions (and growth records and experience history), identify an experiential event suitable for the members from the event DB 313, and output the identified experiential event. Publicly known technology such as an AI (Artificial Intelligence) model may be applied to the model. Furthermore, the model may be one that has been machine-learned using accumulated family structure, personal information, desired conditions, growth records, and experience history as teacher data and experiential events as correct answer data.

[0064] The recommendation unit 345 is an example of the above-mentioned recommendation unit 13. The recommendation unit 345 recommends the identified experience-based event to the user terminal 101 or the like of the user.

[0065] When face authentication is successful for a face image in a captured image acquired from camera 401, determination unit 346 determines whether registration is possible based on the analysis result of the captured image. Specifically, determination unit 346 analyzes the satisfaction level with the experience-based event of a member corresponding to the facial feature information for which face authentication was successful from the captured image, and determines that registration is possible if the satisfaction level is equal to or greater than a predetermined value.

[0066] The recommendation device 300 may perform a process of providing a group of captured images taken during an event in response to a request for acquiring the group of captured images from the user terminal 101 or the like. For example, when the recommendation device 300 receives a request for acquiring a group of captured images including a user ID and an event ID from the user terminal 101, the recommendation device 300 reads out the group of captured images 3146 associated with the user ID and the event ID. Then, the recommendation device 300 transmits the read out group of captured images 3146 to the user terminal 101 that is the request source via the network N. This allows the family F1 including the user (parent) U11 to view the group of captured images 3146 displayed on the user terminal 101.

[0067] Next, the user information registration process, the experience event recommendation process, the event application acceptance process, the registration process of the group of images taken during the event, the experience history registration process, and the like according to the second embodiment will be described. For example, the user (parent) U11 uses the user terminal 101 to register user information in order to receive recommendations for experience events suitable for the members (children) U13 and U14. In this case, the user terminal 101 accepts input of the family structure, face images of the members (children) U13 and U14, personal information, and desired conditions from the user (parent) U11. The user terminal 101 may also accept face images of the user (parent) U11 and the member (parent) U12. The user terminal 101 may also accept identification information (such as relationship) as a member of the family structure together with each face image. Here, the user terminal 101 may take pictures of the members (children) U13 and U14 using the camera 110 to obtain face images of each of them. Alternatively, the user terminal 101 may acquire face images of the members (children) U13 and U14 from another information processing device. The user terminal 101 also displays a user information registration screen and accepts input of various information from the user (parent) U11 via the registration screen.

[0068] FIG. 7 is a diagram showing an example of a registration screen of user information according to the second embodiment. The registration screen 61 of the desired conditions includes a selection field 611 for a day of the week when the desired conditions for the experience-based event are weekend lessons, a selection field 612 for lessons, and a registration button 613. The selection field 611 shows an example in which Saturday is selected. The selection field 612 shows an example in which English is selected. When the registration button 613 is pressed, a registration request for use information including the selection items in the selection fields 611 and 612 is transmitted to the recommendation device 300. It is assumed that there are other registration screens for user information besides the registration screen 61 of the desired conditions, such as registration screens for family structure, face image, personal information, and schedule information. When the registration button of any screen is pressed, the user terminal 101 transmits a registration request for use information including the input family structure, face image, personal information, and desired conditions (request (weekend lessons) and schedule information) to the recommendation device 300 via the network N. It is assumed that each face image is given with identification information of the member.

[0069] 8 is a flowchart showing the flow of a user information registration process according to the present embodiment 2. First, the acquisition unit 341 of the recommendation device 300 receives a request to register user information (registration information) from the user terminal 101 via the network N. That is, the acquisition unit 341 acquires personal information of the user (parent) U11, family structure, face images of members (children) U13 and U14, and desired conditions (S301).

[0070] Next, the registration unit 342 transmits a face information registration request including the face image included in the registration request to the authentication device 200 (S302). Here, the registration unit 342 may transmit a first face information registration request including the face image of the member (child) U13 and a second face information registration request including the face image of the member (child) U14.

[0071] 9 is a flowchart showing the flow of face information registration processing by the authentication device 200 according to the second embodiment. Here, an information registration terminal (not shown) photographs the body including the face of a user, and transmits a face information registration request including the photographed image (registration image) to the authentication device 200 via the network N. The information registration terminal is, for example, an information processing device such as a personal computer, a smartphone, or a tablet terminal. For example, the information registration terminal may be a user terminal 101 or the like. Here, the information registration terminal is assumed to be the recommendation device 300 that has accepted a registration request from the user terminal 101 or the like.

[0072] First, the authentication device 200 receives a face information registration request (S201). For example, the authentication device 200 receives the face information registration request from the recommendation device 300 via the network N. Next, the face detection unit 220 detects a face area from a face image included in the face information registration request (S202). Then, the feature point extraction unit 230 extracts feature points (facial feature information) from the face area detected in step S202 (S203). Then, the registration unit 240 issues a user ID 211 (S204). Then, the registration unit 240 associates the extracted facial feature information 212 with the issued user ID 211 and registers them in the face information DB 210 (S205). After that, the registration unit 240 returns the issued user ID 211 to the request source (information registration terminal, for example, the recommendation device 300) (S206).

[0073] Returning to FIG. 8, the description will be continued. The registration unit 342 of the recommendation device 300 acquires a user ID issued in response to the registration of face information from the authentication device 200 (S303). Here, the user ID issued in response to each of the first and second face information registration requests is acquired as a member ID. In this example, the registration request does not include a face image of the user (parent) U11, so the registration unit 342 issues a new user ID. However, if the registration request includes a face image of the user (parent) U11 or a member (parent) U12, the registration unit 342 transmits a third and a fourth face information registration request to the authentication device 200, and acquires the user ID issued in response to each request as a member ID. In addition, the registration unit 342 associates the acquired user ID with the identification information of the member assigned to the face image.

[0074] Next, the registration unit 342 generates the user information 312 (S304). Specifically, the registration unit 342 generates the family information 3122 by including the family structure 31220 included in the registration request and a collection of member IDs 31221 and the like acquired in step S303. Then, the registration unit 342 generates the user information 312 by associating the family information 3122, the personal information 3123 and the desired conditions 3124 included in the registration request with the issued user ID 3121. After that, the registration unit 342 registers the generated user information 312 in the storage unit 310 (S305). Note that the recommendation device 300 may transmit the issued user ID 3121 to the user terminal 101 via the network N. The user terminal 101 stores the received user ID in the storage unit 120.

[0075] 10 is a flowchart showing the flow of recommendation processing according to the present embodiment 2. For example, the user terminal 101 accepts a recommendation request for an experiential event based on user information registered by a user (parent) U11, and transmits a recommendation request including a user ID to the recommendation device 300 via the network N. The following describes the case where a recommendation request is transmitted.

[0076] First, the acquisition unit 341 of the recommendation device 300 receives a recommendation request from the user terminal 101 via the network N (S311). Then, the acquisition unit 341 acquires a user ID included in the received recommendation request. The acquisition unit 341 acquires a family structure 31220, personal information 3123, and desired conditions 3124 associated with the acquired user ID 3121 from the user information 312 (S312). Note that the recommendation request may include a face image of the user or a member instead of the user ID. In this case, the authentication control unit 343 may control face authentication, which will be described later, for the face image included in the recommendation request to specify the user ID. Then, the acquisition unit 341 may acquire a family structure 31220, personal information 3123, and desired conditions 3124 associated with the user ID for which face authentication has succeeded as the user ID 3121 or member ID 31221, etc.

[0077] Next, the identifying unit 344 identifies an experience-based event suitable for at least the members (children) U13 and U14 from the event DB 313 based on the acquired family structure 31220, personal information 3123, and desired conditions 3124 (S313). For example, the family structure 31220 includes information such as a father, a mother, an older brother aged 5, and a younger sister aged 2, and the request 31241 included in the personal information 3123 is an event related to children's lessons on Saturday and an event related to a day trip that the whole family can participate in on Sunday. In this case, the identifying unit 344 identifies a lesson suitable for a 5-year-old boy (meeting the participation conditions) held on Saturday and a lesson suitable for a 2-year-old girl as experience-based events. The identifying unit 344 also identifies a hiking event held on Sunday that satisfies the participation conditions for a 5-year-old boy, a 2-year-old girl, a father, and a mother, and that is carried out as an experience-based event.

[0078] Thereafter, the recommendation unit 345 transmits the identified experiential event(s) to the user terminal 101 of the user (parent) U11 (S314). In response, the user terminal 101 displays the received experiential events on the input / output unit 150 as a recommendation screen.

[0079] The recommendation device 300 may start the recommendation process at a predetermined timing. In that case, steps S312 and S313 are similarly executed, and in step S314, the recommendation device 300 transmits the identified experiential event to the user terminal of the user who is the recommendation target.

[0080] 11 is a diagram showing an example of a recommendation screen 62 for an experiential event according to the second embodiment. The recommendation screen 62 for an experiential event includes event information 621 and an application to participate button 622. The event information 621 is an example showing, for example, the name of the recommended experiential event, the date and time of the event, a description, the target age (participation conditions), and the location of the event. When the application to participate button 622 is pressed, a screen for inputting or selecting the names of participants is displayed.

[0081] When the user terminal 101 accepts the input or selection of a participant name, it transmits a participation application request including a list of participant names, a user ID, an event ID, etc. to the recommendation device 300 via the network N. The recommendation device 300 performs application processing for the corresponding event based on the information included in the received participation application request. If the applied-for event requires a fee, the recommendation device 300 settles the usage fee using payment information included in the personal information 3123 associated with the user ID 3121. After that, the user (parent) U11 goes to the experience-based event venue 400 with family member F1 and participates in the event.

[0082] The camera 401 at the experience-type event venue 400 captures a scene including the participants of the event while the event is being held, and transmits a registration request including the captured image to the recommendation device 300 via the network N. The registration request includes information for identifying the event being held. For example, the registration request includes an event ID and identification information of the camera 401. The registration request may also include video data captured by the camera 401.

[0083] FIG. 12 is a flowchart showing the flow of the registration process of the captured image during the event according to the second embodiment. First, the acquisition unit 341 acquires a registration request including a captured image of a participant during the experience-based event from the camera 401 via the network N (S321). Next, the authentication control unit 343 extracts a face image from the captured image included in the registration request (S322). For example, the authentication control unit 343 detects a face area included in the captured image as a face image, like the face detection unit 220 described above. Note that, when the registration request includes video data, the authentication control unit 343 may extract a face image from a frame image of the video data. Then, the authentication control unit 343 transmits a face authentication request including the extracted face image to the authentication device 200 via the network N (S323).

[0084] FIG. 13 is a flowchart showing the flow of face authentication processing by the authentication device 200 according to the second embodiment. First, the authentication device 200 receives a face authentication request from the recommendation device 300 via the network N (S211). Next, the authentication device 200 extracts face feature information from the face image included in the face authentication request in the same manner as in steps S202 and S203 described above. Then, the authentication unit 250 of the authentication device 200 compares the face feature information extracted from the face image included in the face authentication request with the face feature information 212 of the face information DB 210 (S212) and calculates the degree of match. Then, the authentication unit 250 determines whether the degree of match is equal to or greater than a threshold (S213). If the face feature information matches, that is, if the degree of match of the face feature information is equal to or greater than a threshold, the authentication unit 250 identifies the user ID 211 associated with the face feature information 212 (S214). Then, the authentication unit 250 returns the face authentication result including the fact that the face authentication was successful and the identified user ID 211 to the recommendation device 300 via the network N (S215). If the degree of match is less than the threshold in step S213, the authentication unit 250 returns the face authentication result including the fact that the face authentication was unsuccessful to the recommendation device 300 via the network N (S216).

[0085] Returning to FIG. 12, the description will be continued. After step S323, the authentication control unit 343 of the recommendation device 300 receives the face authentication result from the authentication device 200 via the network N (S324). Then, the authentication control unit 343 judges whether the face authentication is successful or not from the received face authentication result (S325). If it is judged that the face authentication is successful, the authentication control unit 343 specifies the user ID included in the face authentication result. Then, the specification unit 344 specifies the member ID corresponding to the user ID whose face authentication is successful from the user information 312 (S326). In addition, the specification unit 344 specifies the user ID 3121 associated with the specified member ID. Note that, if multiple face images are extracted from the captured image in step S322, steps S323 to S325 are executed the number of times corresponding to the number of extracted face images. Alternatively, the authentication control unit 343 may transmit a face authentication request including the multiple face images extracted in step S323, and the authentication device 200 may return the face authentication results for each face image in the face authentication request together. In these cases, in step S326, the identification unit 344 may identify multiple member IDs. For example, the member IDs of two members (child) U33 and U34 may be identified. Or, the member IDs of two members (child) U34 and U43 who belong to different families may be identified. In this case, the identification unit 344 also identifies the user ID of the user (parent) U31 who is a family member of the member (child) U34, and the user ID of the user (parent) U41 who is a family member of the member (child) U43.

[0086] Then, the determination unit 346 analyzes the face image that has been successfully authenticated and calculates the degree of satisfaction (S327). For example, the determination unit 346 may apply a smile analysis technique to the face image to calculate the degree of smile as the degree of satisfaction. Then, the determination unit 346 determines whether or not registration is possible based on the calculated degree of satisfaction (S328). For example, the determination unit 346 may determine whether or not the calculated degree of satisfaction is equal to or greater than a predetermined value, and if it is equal to or greater than the predetermined value, determine that registration is possible.

[0087] If it is determined in step S328 that registration is possible, the registration unit 342 associates the captured image acquired in step S321 with the member ID identified in step S326 and registers them in the experience history 314 (S329). Specifically, the registration unit 342 associates the user ID 3141 identified in step S326, the event ID (event information 3142) included in the registration request, the member ID 3143, and the captured image (captured image group 3146) and registers them in the experience history 314. Note that if multiple member IDs are identified in step S326, the registration unit 342 registers the captured image for each user ID corresponding to each member ID in the experience history 314. For example, if the member IDs of two members (children) U33 and U34 of the same family F3 are identified, the user ID of the user (parent) U31 is identified. At this time, the registration unit 342 registers the identified user ID, two member IDs, an event ID, and the captured image in the experience history 314 in association with each other. In this case, the degree of smile of the siblings included in the captured image is equal to or greater than a predetermined value. Thus, a photo of the siblings of the family F3 enjoying the experience-type event together can be recorded. Alternatively, the determination unit 346 may determine that registration is possible even if the degree of smile of one of the siblings is less than a predetermined value but the other is equal to or greater than a predetermined value. This allows the user (parent) U31 to know when one of the siblings is not enjoying (an event). On the other hand, when the member IDs of the two members (children) U34 and U43 belonging to different families are identified, the user ID of the user (parent) U31 and the user ID of the user (parent) U41 are identified. At this time, the registration unit 342 registers the captured image in the experience history 314 in association with the user ID, etc., of the user (parent) U31, and also registers the same captured image in the experience history 314 in association with the user ID, etc., of the user (parent) U41. Furthermore, if video data is included in the registration request, the registration unit 342 may register at least a portion of the video data as the captured image group 3146. Note that if face authentication fails in step S325, or if it is determined in step S328 that registration is not possible, the process ends.

[0088] After the event at the experience-based event venue 400 is completed, the recommendation device 300 transmits a request message for input of an experience record, etc. to the user terminal of the user who applied to participate. For example, after the event is completed, a user (parent) U41 of family F4 who participated in the experience-based event inputs an event experience record and growth record of a participating member (child) U43 via an event experience record registration screen displayed on the user terminal 102. In other words, the user terminal 102 accepts input information such as comments (experience information) and satisfaction level (evaluation information) regarding the event experience of the member (child) U43 from the user (parent) U41.

[0089] FIG. 14 is a diagram showing an example of a registration screen 63 for an event experience record according to the second embodiment. The event experience record registration screen 63 includes an experience record input field 631, a satisfaction level input field 632, a next preference input field 633, and a registration button 634. The experience record input field 631 is an input field for comments on the event experience. The experience record input field 631 is an example of a questionnaire in which a user (parent) U41 inputs in text a description of the state of participation in an event by a member (child) U43 or the like, but is not limited thereto. The satisfaction level input field 632 is an input field for satisfaction level as evaluation information for the participated experience-type event. Here, the satisfaction level is evaluated on a five-point scale, but the method of evaluating the satisfaction level is not limited thereto. The next preference input field 633 is an input field for preferences such as the field and date of the experience-type event that the user would like to participate in next, that is, the experience-type event that the user would like to be recommended next time. When the registration button 634 is pressed, a request to register an experience record (experience history) including the input information, the event ID, and the user ID on the event experience record registration screen 63 is transmitted to the recommendation device 300. In other words, when the registration button 634 is pressed, the user terminal 102 transmits the experience history registration request to the recommendation device 300 via the network N.

[0090] Thereafter, the acquisition unit 341 of the recommendation device 300 acquires a registration request for an experience history from the user terminal 102 via the network N. Then, the acquisition unit 341 acquires the input information, the event ID, and the user ID from the registration request. Thereafter, the registration unit 342 associates the acquired user ID 3141, event ID (event information 3142), and input information (experience information 3144) and registers (updates) them in the experience history 314. Note that the registration unit 342 may additionally register the input content of the next preference input field 633 out of the acquired input information as a request 31241 in the user information 312 in association with the acquired user ID 3121.

[0091] Furthermore, after one or more experiential events are completed, the user (parent) U41 can input a growth record of the member (child) U43 involved in participating in the event via the user terminal 102. The user terminal 102 displays a growth record registration screen in response to an operation by the user (parent) U41 or a notification from the recommendation device 300 at a predetermined timing.

[0092] FIG. 15 is a diagram showing an example of a growth record registration screen 64 according to the second embodiment. The growth record registration screen 64 includes a lesson selection field 641, a goal input field 642, an achievement status input field 643, and a registration button 644. The lesson selection field 641 is a selection field for a field of lessons that is recommended as an experiential event and in which the member (child) U43 has participated. The lesson selection field 641 indicates that English conversation has been selected as a lesson. The goal input field 642 is a field in which the user (parent) U41 inputs goal information of a skill that the member (child) U43 wants to learn. The achievement status input field 643 is a field in which the user (parent) U41 inputs the achievement status of a skill that the member (child) U43 has learned in the goal input field 642. When the registration button 644 is pressed, a growth record registration request including the input information of the growth record registration screen 64, the member ID, and the user ID is transmitted to the recommendation device 300. That is, when the registration button 644 is pressed, the user terminal 102 transmits a request to register the growth record to the recommendation device 300 via the network N.

[0093] Thereafter, the acquisition unit 341 of the recommendation device 300 acquires a registration request for a growth record from the user terminal 102 via the network N. Then, the acquisition unit 341 acquires the input information, the member ID, and the user ID from the registration request. Thereafter, the registration unit 342 updates the user information 312 by associating the acquired user ID 3121, (member ID 31221, etc.) and the input information (growth record 3125). In other words, the registration unit 342 additionally registers the acquired input information as the growth record 3125 in the user information 312 by associating it with the user ID 3121.

[0094] The organizer of the experience-based event may provide the user with event record information (such as a journal) that records the behavior of the participants (children) during the experience of the event. For example, the organizer's terminal (not shown) transmits the event record information to the recommendation device 300 via the network N. The event record information includes text information in which the organizer records the behavior of each participant, an event ID, and participant information (user ID, member ID, personal information, etc.). The event record information may also include an evaluation made by the organizer of the participants (for example, English proficiency and achievement status). The recommendation device 300 registers the text information of the received event record information in the experience history 314 (the experience information 3144) in association with each user or member. The recommendation device 300 also registers the evaluation of the received event record information in the growth record 3125 in association with each user or member. The recommendation device 300 then transmits the text information and evaluation of the corresponding user or member to the user terminal of the user corresponding to the event record information. In response, the user terminal displays the received text information and evaluation. This allows, for example, the user (parent) U41 to understand the state of the member (child) U43 during the event experience and the growth record from the organizer's records. In addition, the user (parent) U41 may input information into the event experience record registration screen 63 and the growth record registration screen 64 based on the event record information.

[0095] FIG. 16 is a diagram showing an example of a display screen 63a of the event experience record by the organizer according to the second embodiment. The display screen 63a of the event experience record by the organizer includes a person in charge observation record display field 631a, a proficiency display field 632a, and a registration screen display button 634a. The observation record display field 631a is a field for displaying a record of the person in charge of the organizer of the experience-type event observing the behavior of the participants (for example, children). The observation record display field 631a corresponds to a display field for displaying text information of the received event record information. The proficiency display field 632a is a display field for displaying the proficiency of the participants evaluated by the person in charge of the organizer of the experience-type event. The proficiency display field 632a corresponds to a display field for displaying the evaluation of the received event record information. The registration screen display button 634a is a button for switching the screen to the event experience record registration screen 63 or the growth record registration screen 64 described above.

[0096] Furthermore, the recommendation device 300 transmits a group of captured images 3146 of the user or members corresponding to the event record information to the user terminal of the user. In response to this, the user terminal displays the received group of captured images. This allows the user (parent) U41 to visually confirm how the member (child) U43 is experiencing the event, in particular, when he or she is smiling.

[0097] Thereafter, the recommendation device 300 recommends (re-recommends) the next experience-based event while taking into account the registered experience history and growth record. FIG. 17 is a flowchart showing the flow of the re-recommendation process according to the second embodiment. First, the acquisition unit 341 of the recommendation device 300 receives a recommendation request from the user terminal 102 via the network N (S311). Then, the acquisition unit 341 acquires the user ID included in the received recommendation request. The acquisition unit 341 acquires the family structure 31220, the personal information 3123, the desired conditions 3124, and the growth record 3125 associated with the acquired user ID 3121 from the user information 312 (S312a). In addition, the acquisition unit 341 acquires the event information 3142, the event information 3142, the experience information 3144, and the evaluation information 3145 associated with the acquired user ID 3141 from the experience history 314 (S312b).

[0098] Next, the identification unit 344 identifies an experience-based event suitable for at least the member (child) U43 from the event DB 313 based on the user information acquired in step S312a and the experience history acquired in step S312b (S313a). For example, if the member (child) U43 is highly satisfied with a grape picking event, an agricultural experience may be identified as the experience-based event. Also, if the member (child) U43 is highly satisfied with an English lesson event, a language hiking may be identified as the experience-based event. At this time, the user information (growth record) and experience history used by the identification unit 344 to identify the event may include the event record information input by the organizer as described above. Therefore, an event suitable for the member can be identified by comprehensively judging it. For example, the identification unit 344 may identify an advanced class event for a participant who is evaluated as having a high level of English proficiency, and a beginner class event for a participant who is evaluated as having a low level of English proficiency.

[0099] Thereafter, the recommendation unit 345 transmits the identified experiential event(s) to the user terminal 102 of the user (parent) U41 (S314). In response, the user terminal 102 displays the received experiential event(s) on the input / output unit 150 as a recommendation screen.

[0100] FIG. 18 is a diagram showing an example of a re-recommendation screen 65 for an experiential event according to the second embodiment. The re-recommendation screen 65 for an experiential event includes event information 651 and an application to participate button 652. The event information 651 and the application to participate button 652 are similar to the event information 621 and the application to participate button 622 in FIG. 11 described above. In other words, the user (parent) U41 can receive a recommendation for an experiential event that is specified taking into account the experience history and growth record. This allows an experiential event that better meets the needs of the family to be recommended, and the user's family can participate in such an experiential event.

[0101] In this way, the present embodiment can help families find experiential events for young children that meet their needs from among a large number of educational contents, and can provide a variety of experiential opportunities.

[0102] <Embodiment 3> The present embodiment 3 is another example of the above-mentioned embodiment 2. In the present embodiment 3, information (ancillary information) associated with the identified experiential event is also recommended. Here, in the present embodiment 3, the ancillary information is acquired from an external business operator or the like. However, the recommendation device may further identify ancillary information of the identified experiential event using an internal processing logic or database, and recommend the ancillary information to the user.

[0103] Fig. 19 is a block diagram showing the overall configuration of a recommendation system 1000a according to the present embodiment 3. In the recommendation system 1000a, compared to Fig. 3, the recommendation device 300 is replaced with the recommendation device 300a, and external servers 501 to 50k (k is a natural number equal to or greater than 2) are added. Since the other configurations are the same as those in Fig. 3, illustrations and detailed descriptions of overlapping contents will be omitted.

[0104] Each of the external servers 501 to 50k is an information processing device connected to the network N, and is a computer server operated by a different business operator. Examples of the business operators include, but are not limited to, a travel agency, an event company, a transportation facility, a toy manufacturer, a leisure manufacturer, an insurance company, and a real estate developer. The external server 501 receives an experience-based event, attribute information, desired conditions, and the like recommended to a specific user and his / her family from the recommendation device 300a via the network N. The external server 501 determines additional information of the experience-based event based on the received experience-based event, attribute information, desired conditions, and the like using a predetermined logic, and returns the determined additional information to the recommendation device 300a via the network N. The predetermined logic may include an AI model as described above. The external servers 502 (not shown) to 50k are assumed to operate in the same manner.

[0105] Here, the auxiliary information may be an auxiliary service for the experience-based event. Examples of the auxiliary service include information on transportation means available for traveling to the event venue, parking lots near the event venue, commercial facilities, accommodation facilities, restaurants (where children can dine), insurance, etc. The transportation means include information on train, bus, taxi, airplane tickets, etc., rental car and car sharing stores and vehicle models, etc. The auxiliary service may also include benefit information for services available for participating in the experience-based event. Benefit information is, for example, discount coupons and point information that can be used for payment for event participation fees, transportation means, parking lots, commercial facilities, accommodation facilities, restaurants, etc.

[0106] The auxiliary information may also be advertising information related to the experience-based event, or information on rental products to be used at the experience-based event.

[0107] Fig. 20 is a block diagram showing the configuration of a recommendation device 300a according to the present embodiment 3. In the recommendation device 300a, compared with Fig. 6 described above, a program 311a is changed and a notification unit 347 is added. Since the other configurations are the same as those in Fig. 6, detailed description of the overlapping contents will be omitted.

[0108] The program 311a is a computer program in which the process of the recommendation method according to the third embodiment is implemented.

[0109] The notification unit 347 is a first notification unit that notifies at least the first external server of the identified experience-based event, attribute information, and desired conditions. The acquisition unit 341 acquires additional information related to the identified experience-based event from the first external server. Then, the recommendation unit 345 presents the acquired additional information to the user. This allows a proposal of additional information related to the experience-based event to be accepted from a business operator or the like that operates the first external server, and a total recommendation including the identified experience-based event and the additional information can be realized. Therefore, the user's family can obtain useful information related to the event, which further promotes event participation.

[0110] In particular, the notification unit 347 may notify two or more external servers 501-50k of the identified experience-based event, attribute information, and desired conditions. In this case, the acquisition unit 341 collects attached information from each external server. The recommendation unit 345 then compiles the collected attached information and presents it to the user. This makes it possible to realize a more comprehensive total recommendation that includes a large amount of attached information. The notification unit 347 may further notify the external server of the experience history. This makes it possible to obtain attached information that is more in line with the needs of the family.

[0111] Furthermore, when the acquisition unit 341 acquires the above-mentioned ancillary services as ancillary information, the recommendation unit 345 further recommends the acquired ancillary services to the user. This allows the user to apply for the experience-based event and the ancillary services together, eliminating the need to search for services related to the event and improving convenience. Furthermore, when the ancillary information includes the above-mentioned special benefit information, the user can use coupons and the like when participating in the event, which promotes application for participation.

[0112] Furthermore, when the acquisition unit 341 acquires the above-mentioned advertising information as auxiliary information, the recommendation unit 345 may recommend the identified experience-based event and present the acquired advertising information. This improves the advertising effectiveness related to the event.

[0113] Furthermore, when the acquisition unit 341 acquires information on rental products used in an experiential event as auxiliary information, the recommendation unit 345 may recommend the identified experiential event and also recommend the acquired information on the rental products. This allows the user to apply for the event and also apply for the necessary rental products, improving convenience.

[0114] The acquiring unit 341 may acquire payment information for a fee for the presentation of the auxiliary information from an external server. That is, the operator of the recommendation device 300a may acquire a fee for the presentation of the auxiliary information from the business operator.

[0115] FIG. 21 is a sequence diagram showing a flow of an example of a recommendation process including auxiliary information according to the third embodiment. First, the recommendation device 300a identifies an experience-based event suitable for the family of a specific user (e.g., user (parent) U11) (S401). For example, it is assumed that the experience-based event is identified as in steps S312 and S313 of FIG. 10 described above. Next, the recommendation device 300a transmits the identified event information (experience-based event) to the user terminal 101 of the user (parent) U11 and recommends it (S402). In response, the user terminal 101 accepts an application to participate in the recommended event from the user (parent) U11, and transmits a participation application request to the recommendation device 300a (S403).

[0116] In response to the participation application request, the recommendation device 300a identifies the event to be applied for (application event) and performs application processing for the event based on the participation application request as described above. In addition, the recommendation device 300a notifies each of the external servers 501-50k of the application event, the user information 312 of the user (parent) U11, and the experience history 314 via the network N (S4041-S404k).

[0117] The external server 501 determines the attached information based on the notified information (S4051). Then, the external server 501 transmits the determined attached information to the recommendation device 300a via the network N (S4061). The same applies to other external servers. For example, the external server 50k determines the attached information based on the notified information (S405k). Then, the external server 50k transmits the determined attached information to the recommendation device 300a via the network N (S406k).

[0118] The recommendation device 300a aggregates each piece of attached information received from the external servers 501 to 50k (S407). Then, the recommendation device 300a transmits (presents) the aggregated group of attached information to the user terminal 101 via the network N (S408). Note that the recommendation device 300a does not necessarily need to aggregate all of the attached information, and may aggregate the attached information individually or in part.

[0119] The user terminal 101 accepts an application for the presented auxiliary information from the user (parent) U11, and transmits an application request specifying the auxiliary information to the recommendation device 300a via the network N (S409). For example, the user terminal 101 may apply for an auxiliary service or a rental product. The user terminal 101 may transmit the application request directly to an external server that provides the auxiliary information. Furthermore, when the auxiliary information is advertisement information, the user terminal 101 may transmit a request to the server that provides the advertisement information in response to a selection operation of the advertisement information by the user (parent) U11.

[0120] Thereafter, the recommendation device 300a may perform application processing on behalf of the relevant external server in response to an application for the attached information. In addition, the external servers 501-50k may perform processing to pay a fee to the operator of the recommendation device 300a in response to the attached information being presented (recommended, etc.) to the user. Alternatively, the external servers 501-50k may perform processing to pay a fee to the operator of the recommendation device 300a in response to the application for the attached information by the user or the reference of the advertisement information. Specifically, the external servers 501-50k may perform processing to transfer money from their own accounts to the account of the operator of the recommendation device 300a in a financial institution's system. At that time, each of the external servers 501-50k may transmit the result of the transfer as payment information to the recommendation device 300a via the network N (S4101-S410k). Alternatively, instead of the external server performing the transfer processing, the recommendation device 300a may perform the transfer processing on behalf of the external server in response to steps S4101-S410k.

[0121] FIG. 22 is a sequence diagram showing the flow of another example of the recommendation process including the attached information according to the third embodiment. Here, an example is shown in which the attached information is aggregated before the identified experience-based event is recommended to the user, and the experience-based event and the attached information are recommended to the user together. After step S401, the recommendation device 300a notifies each of the external servers 501 to 50k of the identified event, the user information 312 of the user (parent) U11, and the experience history 314 via the network N (S4111 to S411k). Steps S4051 to S405k, S4061 to S406k, and S407 are the same as those in FIG. 21 described above. Then, the recommendation device 300a transmits (presents) the identified experience-based event and the aggregated attached information group to the user terminal 101 via the network N (S408a). The user terminal 101 accepts an application to participate in the recommended event and an application for the presented attached information from the user (parent) U11. Then, the user terminal 101 transmits an application request for participation in the event and an application request specifying the attached information to the recommendation device 300a via the network N (S409a). The recommendation device 300a performs application processing for the event based on the application request for participation as described above. Furthermore, the recommendation device 300a may proxy application processing to the relevant external server in response to the application of the attached information. Furthermore, each of the external servers 501-50k may transmit the remittance result of the fee for the attached information as payment information to the recommendation device 300a via the network N (S4101-S410k).

[0122] In the above example, all the external servers 501 to 50k that received data provided from the recommendation device 300a (S4041 to S404k, etc.) presented the attached information, but this is not necessarily required. For example, some or all of the external servers 501, etc. may not present the attached information to the recommendation device 300a. For example, the operator of the external server 501, etc. may utilize the data provided from the recommendation device 300a (event information, user information, experience history, etc.) for the marketing of the company or the development of products and services. In this case, the operator of the external server 501, etc. may pay a data provision fee to the operator of the recommendation device 300a. In addition, the external server 501, etc. may transmit payment information to the recommendation device 300a as described above. In other words, the operator of the recommendation device 300a can utilize the accumulated data by transferring personal information of users and accumulated experience history, etc. to a third party for a fee or free of charge. For example, if the business to which the accumulated data is transferred is a real estate developer, the real estate developer may analyze the characteristics of each area in which residents live and provide services and information that are suitable for each resident. In addition, the real estate developer can increase the value of condominiums and areas by utilizing the provided data. In addition, if the business to which the accumulated data is transferred is a search site operator, it can acquire new customers and increase the utilization rate of the site.

[0123] The operator of the recommendation device 300a may tie up with an external business operator to provide a comprehensive recommendation. Specifically, the additional information may be information on rental products used in an experience-based event, as described above. For example, if the experience-based event is outdoor camping, the additional information may be tent equipment. In this case, the recommendation unit 345 may recommend outdoor camping and also recommend the rental of tent equipment free of charge. This allows the user's family to have an opportunity to try out a product from a specific manufacturer at the experience-based event. This may lead to the purchase of the product. Therefore, the tie-up can be expected to have an advertising effect for the product. Therefore, the tied-up business operator shall pay a tie-up fee or a publication advertising fee to the operator of the recommendation device 300a.

[0124] <Embodiment 4> The fourth embodiment is another example of the second embodiment. The fourth embodiment describes a case where the accumulated data is provided to a local government or a business, and a newly planned experiential event is registered in an event DB at the data provider. The schematic configuration of the recommendation system and the recommendation device are the same as those of the third embodiment, and therefore illustrations and explanations are omitted.

[0125] The recommendation device according to the fourth embodiment further includes a second notification unit that notifies a second external server (at least a part of 501 to 50k) of the attribute information, desired conditions, and experience history. The second notification unit may be the notification unit 347 described above. Then, the acquisition unit acquires information on a new experiential event planned based on the attribute information, desired conditions, and experience history from the second external server. The registration unit adds the acquired information on the new experiential event to a database (event DB313). This makes it possible to plan and recommend events that meet higher demand by taking into account the experience history, desired conditions, and attribute information of family members who actually participated in the experiential event.

[0126] Furthermore, the attribute information may include information on the user's residential area. In this case, the identification unit identifies a plurality of users whose residential areas are within a predetermined range. Then, the second notification unit notifies the second external server of the attribute information of the identified plurality of users and the experience history of each user. This makes it possible to plan and recommend events that meet the needs of the region. For example, if a weekend agricultural experience event is highly rated by many participants in a certain region, the local government of that region may plan a new food education event. Or, if many users in a certain region request English conversation as a lesson, a business operator in that region may plan a new English conversation event.

[0127] FIG. 23 is a sequence diagram showing the flow of the new event registration process according to the fourth embodiment. First, the identification unit 344 extracts user information and experience history of a specific region at a predetermined timing (S501). Specifically, the identification unit 344 may start this process in response to a request from a business operator or a local government of the second external server (e.g., the external server 501). Alternatively, the identification unit 344 may start this process periodically. Then, the identification unit 344 identifies addresses included in the personal information 3123 of the user information 312 that correspond to a specific region (e.g., a specific prefecture or city, ward, town, or village). Then, the identification unit 344 identifies the experience history 314 corresponding to the user ID 3121 of the identified user information 312.

[0128] Thereafter, the notification unit 347 transmits the user information 312 and experience history 314 identified in step S501 to the external server 501 via the network N (S502). The external server 501 plans a new experience-based event based on the received user information 312 and experience history 314 (S503). For example, the external server 501 displays the received user information 312 and experience history 314 on a screen to support the person in charge in planning the event. Then, the external server 501 accepts information on the event planned by the person in charge. Alternatively, the external server 501 may input the received user information 312 and experience history 314 into a predetermined model (processing logic) and accept the output of the plan for the new experience-based event. Thereafter, the external server 501 transmits a registration request for the planned new experience-based event to the recommendation device 300a via the network N (S504).

[0129] The acquisition unit 341 of the recommendation device 300a acquires a registration request for a new experiential event from the external server 501 via the network N. Then, the registration unit 342 adds information about the acquired new experiential event to the event DB 313 (S505). As a result, the added event information can also become a target for recommendation in the subsequent recommendation process. This makes it possible to further enrich the contents of the event DB. For example, the local government that operates the external server 501 can plan a new event such as an educational support event related to an event that was popular (highly rated) among local residents.

[0130] The local government that operates the external server 501 may provide administrative services suited to each resident based on the data provided by the recommendation device 300a.

[0131] <Other embodiments> The recommendation device 300 or 300a may recommend an experiential event based on the experience history of family members other than the user. For example, the recommendation device 300 etc. may recommend an event that has a high level of satisfaction among other residents in the user's neighborhood or an event that is frequently used by residents within a certain residential area. The recommendation device 300 etc. may also recommend an experiential event using word-of-mouth information about the event. For example, the recommendation device 300 etc. may identify the event to be recommended using experience information and evaluation information of users or members with similar attributes (mothers with children of the same age).

[0132] The event DB313 (database) may include the infectious disease control status of each of a plurality of experiential events. In this case, the identification unit identifies the experiential event by further taking into account the infectious disease control status. This allows the user (parent) to apply to participate in the recommended event after confirming its safety.

[0133] Here, the infection control status is a safety index indicating the difficulty of infection with an infectious disease at an event venue and the safety against the spread of infection. The higher the level of the safety index, the more difficult it is to be infected with an infectious disease and the higher the safety. In other words, the safety index is also an index indicating the low risk of infection with an infectious disease. The safety index can also be said to be an index indicating the degree of infection prevention measures taken by a store. Therefore, the recommendation unit 345 may add the safety index to the information of the experiential event to be recommended and transmit it to the request source. In addition, when multiple experiential events are identified, the identification unit 344 may assign a priority to each event according to its safety index, and the recommendation unit 345 may recommend multiple experiential events by adding the priority.

[0134] When the user's request is blank, the recommendation device 300 etc. may recommend events etc. that have high satisfaction (rating information) among other users with similar attributes (for example, residents living within a certain area).

[0135] In the above-mentioned second to fourth embodiments, the recommendation device 300 and the authentication device 200 are separate information processing devices, but they may be the same. For example, the recommendation device 300 may register facial feature information in association with the member ID 31221 of the user information 312. In this case, the control unit 340 may include the face detection unit 220, the feature point extraction unit 230, the registration unit 240, and the authentication unit 250 in FIG. 5.

[0136] Alternatively, at least one of the user information 312 , the event DB 313 and the experience history 314 may be stored in an external storage device connected to the authentication device 200 or the recommendation device 300 .

[0137] In the above embodiment, the present disclosure has been described as a hardware configuration, but is not limited to this. Any process of the present disclosure can be realized by causing a CPU to execute a computer program.

[0138] In the above example, the program can be stored and provided to the computer using various types of non-transitory computer readable media. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, DVD (Digital Versatile Disc), and semiconductor memory (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). The program may also be provided to the computer by various types of transitory computer readable media. Examples of the transitory computer readable media include electric signals, optical signals, and electromagnetic waves. The transitory computer readable media can provide the program to the computer via a wired communication path such as an electric wire and an optical fiber, or via a wireless communication path.

[0139] The present disclosure is not limited to the above-described embodiment, and may be modified as appropriate without departing from the spirit and scope of the present disclosure. In addition, the present disclosure may be implemented by appropriately combining the respective embodiments.

[0140] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes. (Appendix A1) an acquisition unit that acquires attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; an identification unit that identifies at least an experience-based event suitable for the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation unit that recommends the identified experience-based event to the user; A recommendation device comprising: (Appendix A2) The desired conditions include a request for the experience-based event in the family, The identification unit identifies an experience-based event that satisfies the request. 2. The recommendation device according to claim 1 . (Appendix A3) The desired conditions include schedule information of the family, The identification unit identifies the experience-based event to be held on a date other than the schedule information. Recommendation device according to appended claim A1 or A2. (Appendix A4) The attribute information includes attributes of the user's children as the members, The identification unit identifies the experience-based event for which the child satisfies a participation requirement. The recommendation device according to any one of appendices A1 to A3. (Appendix A5) The recommendation device includes: a first notification unit that notifies a first external server of the identified experience-based event, the attribute information, and the desired conditions; The acquisition unit acquires auxiliary information related to the identified experiential event from the first external server, The recommendation unit presents the acquired auxiliary information to the user. The recommendation device according to any one of appendices A1 to A4. (Appendix A6) the first notification unit notifies two or more of the first external servers of the identified experiential event, the attribute information, and the desired conditions; The acquisition unit collects the auxiliary information from each first external server, The recommendation unit compiles the collected auxiliary information and presents it to the user. 2. The recommendation device according to claim 1 , (Appendix A7) The acquisition unit acquires an ancillary service of the identified experiential event as the ancillary information, The recommendation unit further recommends the acquired auxiliary service to the user. Recommendation device according to appended claim A5 or A6. (Appendix A8) The auxiliary service includes information about benefits of a service that can be used when participating in the identified experience-based event. 2. The recommendation device according to claim 1 , (Appendix A9) The acquisition unit acquires advertising information related to the identified experiential event as the auxiliary information, The recommendation unit recommends the identified experience-based event and presents the advertising information. The recommendation device according to any one of Appendix A5 to A8. (Appendix A10) The acquisition unit acquires information on rental products to be used in the identified experience-based event as the auxiliary information. The recommendation device according to any one of Appendix A5 to A9. (Appendix A11) The acquisition unit acquires payment information for a fee associated with the presentation of the auxiliary information from the first external server. The recommendation device according to any one of Appendix A5 to A10. (Appendix A12) The acquisition unit acquires input information based on experiences of the members who have participated in the recommended experiential event, The recommendation device includes: A registration unit that registers the input information, the experience-based event, and the member in an experience history in association with each other. The recommendation device according to any one of Appendix A1 to A11. (Appendix A13) The identification unit identifies the experience-based event by further taking into account the input information. 2. The recommendation device according to claim 12. (Appendix A14) a second notification unit that notifies a second external server of the attribute information, the desired conditions, and the experience history; the acquisition unit acquires, from the second external server, information on a new experiential event planned based on the attribute information, the desired conditions, and the experience history; The registration unit adds information about the new experience-based event to the database. Recommendation device according to appended claim A12 or A13. (Appendix A15) The attribute information includes information about the user's residential area, The identification unit identifies a plurality of users whose residential areas are within a predetermined range, The second notification unit notifies the second external server of attribute information of the identified users and an experience history of each user. 2. The recommendation device according to claim 14 . (Appendix A16) The acquisition unit further acquires biometric information of each member of the user, the registration unit registers the biometric information, the attribute information, and the desired conditions as user information in association with each other; The recommendation device includes: an authentication control unit that controls biometric authentication using the biometric information for images of participants taken during the recommended experience-based event; a determination unit that, when the biometric authentication is successful, determines whether or not registration is possible based on an analysis result of the captured image, When the determination unit determines that registration is possible, the registration unit registers the captured image in an experience history of the member corresponding to the biometric information that has been successfully authenticated. The recommendation device according to any one of Appendix A12 to A15. (Appendix A17) The determination unit analyzes a degree of satisfaction with the experience-based event of a member corresponding to the biometric information that has been successfully authenticated from the captured image, and determines that registration is possible if the degree of satisfaction is equal to or greater than a predetermined value. 13. The recommendation device according to claim 16. (Appendix A18) The database includes infectious disease control statuses of each of the plurality of experiential events, The identification unit identifies the experience-based event by further taking into account the infectious disease countermeasure status. The recommendation device according to any one of Appendix A1 to A17. (Appendix B1) A user terminal of a user; A recommendation device, The recommendation device includes: an acquisition unit that acquires, from the user terminal, attribute information including information on family members of the user and desired conditions for the family members other than the user to participate in at least an experiential event; an identification unit that identifies at least an experience-based event suitable for the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation unit that recommends the identified experiential event to the user terminal; A recommendation system comprising: (Appendix B2) The desired conditions include a request for the experience-based event in the family, The identification unit identifies an experience-based event that satisfies the request. A recommendation system as described in Appendix B1. (Appendix C1) The computer Acquire attribute information including information on family members of the user and desired conditions for at least family members other than the user to participate in the experience-based event; Identifying an experience-based event suitable for at least the member from a database in which information on a plurality of experience-based events is registered based on the attribute information and the desired conditions; Recommending the identified experiential event to the user How to recommend. (Appendix D1) An acquisition process for acquiring attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; a process of identifying an experience-based event suitable for at least the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation process for recommending the identified experiential event to the user; A recommendation program that causes a computer to execute the above.

[0141] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-mentioned embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0142] This application claims priority to Japanese Patent Application No. 2021-036064, filed on March 8, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0143] 1 Recommendation device 11 Acquisition Department 12 Specific section 13 Recommendation Department 1000 Recommendation Systems F1 Family U11 User (Parent) U12 members (parents) U13 members (children) U14 members (children) F2 Family U22 members (parents) U23 members (children) F3 family U31 User (parent) U33 members (children) U34 members (children) F4 Family U41 User (parent) U43 Member (child) N Network 101 User terminal 102 User terminal 110 Camera 120 Storage section 121 Programs 130 Memory 140 Communications Department 150 Input / output section 160 Control section 161 Registration Department 162 Acquisition Department 163 Display control section 200 Authentication Device 210 Face Information DB 211 User ID 212 Facial Feature Information 220 Face detection unit 230 Feature Point Extraction Unit 240 Registration Department 250 Authentication Department 300 Recommendation device 310 Storage section 311 Program 312 User information 3121 User ID 3122 Family Information 31220 Family Composition 31221 Member ID 3122n Member ID 3123 Personal Information 3124 Desired conditions 31241 Request 31242 Schedule Information 3125 Growth Record 313 Event DB 3131 Event Information 313m Event Information 314 Experience History 3141 User ID 3142 Event Information 3143 Member ID 3144 Experience Information 3145 Evaluation Information 3146 Images 320 Memory 330 Communications Department 340 Control Unit 341 Acquisition Department 342 Registration Department 343 Authentication control section 344 Specific part 345 Recommendation Department 346 Judgment section 400 Experience-based event venue 401 Camera 1000a Recommendation System 300a recommendation device 311a Program 347 Notification Department 501 External Server 50k external servers 61 Desired conditions registration screen 611 Selection column 612 Selection column 613 Registration button 62 Experience-based event recommendation screen 621 Event Information 622 Participation application button 63 Event experience record registration screen 631 Experience record entry field 632 Satisfaction input field 633 Next preference entry field 634 Registration button 64 Growth record registration screen 641 Lesson selection column 642 Goal input field 643 Achievement status input field 644 Registration button 63a Event experience record display screen by organizer 631a Observation record display column by person in charge 632a Proficiency column 634a Registration screen display button 65 Re-recommendation screen for experiential events 651 Event Information 652 Participation application button

Claims

1. An acquisition means for acquiring attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; a specifying means for specifying at least an experience-based event suitable for the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation means for recommending the identified experience-based event to the user; Equipped with The acquiring means further acquires biometric information of each member of the user; a registration means for registering the biometric information, the attribute information, and the desired conditions as user information in association with each other; an authentication control means for controlling biometric authentication using the biometric information for images of participants taken during the implementation of the recommended experience-based event; a determination means for determining whether or not the biometric authentication is successful based on an analysis result of the captured image; Further equipped with When the determination means determines that registration is possible, the registration means registers the captured image in the experience history of the member corresponding to the biometric information that has been successfully authenticated. Recommendation device.

2. The desired conditions include a request for the experience-based event in the family, The specifying means specifies an experience-based event that satisfies the request. The recommendation device according to claim 1 .

3. The desired conditions include schedule information of the family, The specifying means specifies the experience-based event to be held on a date other than the schedule information. The recommendation device according to claim 1 or 2.

4. The attribute information includes attributes of the user's children as the members, The identification means identifies the experience-based event for which the child satisfies a participation requirement. The recommendation device according to any one of claims 1 to 3.

5. The recommendation device includes: a first notification means for notifying a first external server of the identified experience-based event, the attribute information, and the desired conditions; The acquisition means acquires auxiliary information related to the identified experiential event from the first external server, The recommendation means presents the acquired auxiliary information to the user. The recommendation device according to any one of claims 1 to 4.

6. the first notification means notifies the two or more first external servers of the identified experiential event, the attribute information, and the desired conditions; The acquisition means collects the auxiliary information from each first external server, The recommendation means compiles the collected auxiliary information and presents it to the user. The recommendation device according to claim 5 .

7. The acquiring means acquires input information based on experiences of the members who have participated in the recommended experiential event, The registration means registers the input information, the experience-based event, and the member in the experience history in association with each other. The recommendation device according to any one of claims 1 to 6.

8. a second notification means for notifying a second external server of the attribute information, the desired conditions, and the experience history; the acquiring means acquires information on a new experiential event planned based on the attribute information, the desired conditions, and the experience history from the second external server; The registration means adds information about the new experience-based event to the database.

8. The recommendation device according to claim 1 .

9. The computer an acquisition step of acquiring attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; a step of identifying an experience-based event suitable for at least the member from a database in which information on a plurality of experience-based events is registered based on the attribute information and the desired conditions; a recommendation step of recommending the identified experience-based event to the user; Including, In the acquiring step, biometric information of each member of the user is further acquired, a registration step of registering the biometric information, the attribute information, and the desired conditions as user information in association with each other; an authentication control step of controlling biometric authentication using the biometric information for images of participants taken during the recommended experience-based event; a determination step of determining whether or not registration is possible based on an analysis result of the captured image if the biometric authentication is successful; Further comprising: In the registration step, if it is determined in the determination step that registration is possible, the photographed image is registered in the experience history of the member corresponding to the biometric information that has been successfully authenticated. How to recommend.

10. An acquisition process for acquiring attribute information including information on members of the user's family and desired conditions for at least members of the family other than the user to participate in the experience-based event; a process of identifying an experience-based event suitable for at least the member from a database in which information on a plurality of experience-based events is registered, based on the attribute information and the desired conditions; a recommendation process for recommending the identified experiential event to the user; A recommendation program for causing a computer to execute the following: The acquisition process further includes acquiring biometric information of each member of the user; a registration process for registering the biometric information, the attribute information, and the desired conditions as user information in association with each other; an authentication control process for controlling biometric authentication using the biometric information for images of participants taken during the recommended experience-based event; a determination process for determining whether or not registration is possible based on an analysis result of the captured image if the biometric authentication is successful; and causing the computer to further execute the steps: In the registration process, if it is determined in the determination process that registration is possible, the captured image is registered in the experience history of the member corresponding to the biometric information that has succeeded in the biometric authentication. Recommendation program.

Images