WO2022190741A1

WO2022190741A1 - Recommendation device, system, and method, and computer-readable medium

Info

Publication number: WO2022190741A1
Application number: PCT/JP2022/004884
Authority: WO
Inventors: ちあき松川; 沙月信清; 由梨香道下
Original assignee: 日本電気株式会社
Priority date: 2021-03-08
Filing date: 2022-02-08
Publication date: 2022-09-15
Also published as: JPWO2022190741A1

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

Recommendation device, system and method, and computer readable medium

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.

Patent Document 1 discloses a technology related to an information processing device that searches for facilities desired by a user. The information processing apparatus determines the relationship from the attributes of the two users, and searches for a facility that corresponds to the attribute of one user from the attributes of the facility and that corresponds to the relationship.

Patent Document 2 discloses a technology related to an information trading device for trading personal information. The information transaction device acquires user information from users who have agreed to the provision of user information, and generates demand information according to the acquisition status.

Japanese Patent Application Laid-Open No. 2020-030469 JP 2015-118632 A

Here, parents of the child-rearing generation have a need to provide education through real-life experiences to their children in early childhood. On the other hand, with the increase in dual-income couples and the increase in educational content, there is a problem that it is difficult to find experiential events for early childhood children that meet the needs of families from a large number of educational content. be.

The present disclosure has been made to solve such problems, and is a recommendation device and system for supporting child-rearing by recommending experiential events for early childhood children that meet the needs of families. , to provide a method and a program.

A recommendation device according to a first aspect of the present disclosure includes:
an acquisition unit that acquires attribute information including information on members of a 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 unit that specifies a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation unit that recommends the identified experiential event to the user;
Prepare.

A recommendation system according to a second aspect of the present disclosure includes:
the user's user terminal;
a recommendation device;
The recommendation device is
Acquisition unit for acquiring, from the user terminal, 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. When,
a specifying unit that specifies a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation unit that recommends the identified experiential event to the user terminal;
Prepare.

A recommendation method according to a third aspect of the present disclosure includes:
the computer
Acquire 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,
Based on the attribute information and the desired conditions, identifying a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered,
The identified experiential event is recommended to the user.

A recommendation program according to the fourth aspect of the present disclosure includes:
Acquisition processing 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 process of specifying a hands-on event suitable for at least the member from among a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation process of recommending the identified experiential event to the user;
run on the computer.

With the present disclosure, it is possible to provide a recommendation device, system, method, and program for supporting child-rearing by recommending experiential events for early childhood children that meet the needs of families.

1 is a block diagram showing the configuration of a recommendation device according to the first embodiment; FIG. 4 is a flow chart showing the flow of a recommendation method according to the first embodiment; FIG. 11 is a block diagram showing the overall configuration of a recommendation system according to a second embodiment; FIG. FIG. 9 is a block diagram showing the configuration of a user terminal according to the second embodiment; FIG. FIG. 11 is a block diagram showing the configuration of an authentication device according to the second embodiment; FIG. FIG. 11 is a block diagram showing the configuration of a recommendation device according to a second embodiment; FIG. FIG. 11 is a diagram showing an example of a user information registration screen according to the second embodiment; 10 is a flow chart showing the flow of user information registration processing according to the second embodiment. 9 is a flow chart showing the flow of face information registration processing by the authentication device according to the second embodiment; 13 is a flowchart showing the flow of recommendation processing according to the second embodiment; FIG. 11 is a diagram showing an example of a recommendation screen for a hands-on event according to the second embodiment; FIG. 10 is a flow chart showing the flow of registration processing of captured images during an event according to the second embodiment. 9 is a flow chart showing the flow of face authentication processing by the authentication device according to the second embodiment; FIG. 11 is a diagram showing an example of an event experience record registration screen according to the second embodiment; FIG. 11 is a diagram showing an example of a growth record registration screen according to the second embodiment; FIG. 11 is a diagram showing an example of a display screen of event experience records by the organizer according to the second embodiment; FIG. 12 is a flow chart showing the flow of re-recommendation processing according to the second embodiment; FIG. FIG. 12 is a diagram showing an example of a re-recommendation screen for a hands-on event according to the second embodiment; FIG. 11 is a block diagram showing the overall configuration of a recommendation system according to a third embodiment; FIG. FIG. 11 is a block diagram showing the configuration of a recommendation device according to a third embodiment; FIG. FIG. 14 is a sequence diagram showing an example flow of a recommendation process including attached information according to the third embodiment; FIG. 20 is a sequence diagram showing another example of the flow of recommendation processing including attached information according to the third embodiment; FIG. 21 is a sequence diagram showing the flow of new event registration processing according to the fourth embodiment;

Below, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same reference numerals are given to the same or corresponding elements, and redundant description will be omitted as necessary for clarity of description.

<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 the user an experiential event in which at least members of the user's family other than the user participate. Here, the recommendation device 1 may be connected to a predetermined terminal via a communication network (not shown; hereinafter, the communication network will simply be referred to as a network) or predetermined wireless communication. It does not matter whether the network is wired or wireless, and the type of communication protocol does not matter. The terminal may perform 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 or the like operated by a user.

The recommendation device 1 includes an acquisition unit 11, a specification unit 12, and a recommendation unit 13. Acquisition unit 11 acquires user attribute information and desired conditions for participating in a hands-on event. Here, the user's attribute information includes information on the members of the user's family. Family members are, for example, when the user is a parent, the user's spouse, children, relatives, blood relatives, or similar people. Further, the desired condition is a desired condition for at least members of the user's family other than the user to participate in the experience-based event. The desired conditions may include the user's own wishes and other member's wishes. In addition, the desired conditions may include the member's area of specialty and preference. Since the specifying unit 12, which will be described later, specifies an experiential event suitable for the member based on the member's specialty and preference, the specialty and preference can be said to be desired conditions in a broad sense.

Based on attribute information and desired conditions, the identifying unit 12 identifies, at least, a hands-on event suitable for members from among a database in which information on a plurality of hands-on events is registered. Here, the database may be built in the recommendation device 1 or managed by an external storage device. Here, the experiential event is a participatory event involving actual experience, and is held at a predetermined date and time at a predetermined place, for example. Alternatively, the experiential event may include weekly lessons, after-school care, and the like. Also, the experience-based event specified by the specifying unit 12 meets the desired conditions of at least members of the user's family other than the user. Additionally, the experiential event identified may be appropriate for the user or other members of the family.

The recommendation unit 13 recommends the specified experiential event to the user. For example, the recommendation unit 13 may notify the user terminal operated by the user of information on the specified experiential event.

FIG. 2 is a flow chart 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 the experience-based event ( S11). Next, the specifying unit 12 specifies a hands-on event suitable for at least the members from a database in which information on a plurality of hands-on events is registered based on the attribute information and desired conditions (S12). Then, the recommendation unit 13 recommends the specified experience-based event to the user (S13).

As described above, in this embodiment, for example, when the members are children of the user, based on the user's family structure and desired conditions for the event, an experience-based event suitable for at least children is selected from a large number of event databases. It identifies the event. Therefore, a user who is recommended an experience-based event can easily participate in the experience-based event with his/her children and the whole family. In particular, when the members are in their early childhood, it is desirable to have an event that takes into account parental educational policies, family composition, and the like, which is effective. Therefore, it is possible to support child-rearing by recommending experiential events for early childhood children that meet the needs of the family.

The recommendation device 1 includes a processor, a memory, and a storage device (not shown). Further, the storage device stores a computer program in which the processing of the recommendation method according to the present embodiment is implemented. Then, the processor loads the computer program from the storage device into the memory and executes the computer program. Thereby, the processor implements the functions of the acquisition unit 11 , the identification unit 12 and the recommendation unit 13 .

Alternatively, the acquisition unit 11, the identification unit 12, and the recommendation unit 13 may each be realized by dedicated hardware. Also, part or all of each component of each device may be implemented by general-purpose or dedicated circuitry, processors, etc., or combinations thereof. These may be composed of a single chip, or may be composed of multiple chips connected via a bus. A part or all of each component of each device may be implemented by a combination of the above-described circuits and the like and programs. As a processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field-Programmable Gate Array), a quantum processor (quantum computer control chip), or the like can be used.

Further, when some or all of the components of the recommendation device 1 are implemented by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged or distributed. may be placed. For example, the information processing device, circuits, and the like may be implemented as a form in which each is connected via a communication network, such as a client-server system, a cloud computing system, or the like. Also, the functions of the recommendation device 1 may be provided in a SaaS (Software as a Service) format.

<Embodiment 2>
The second embodiment is a specific example of the first embodiment described above. 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 a user (parent) or the like an experiential event suitable for a member (child) or the like. For example, the family F1 includes user (parent) U11, member (parent) U12, member (child) U13, and member (child) U14. The 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. User (parent) U11, (user (parent) of family F2) U31 and U41 are users of the recommendation system 1000. FIG.

The recommendation system 1000 includes

user terminals

101 and 102 , an authentication device 200 , a recommendation device 300 and a camera 401 .

User terminals

101 and 102, authentication device 200, recommendation device 300, and camera 401 are connected via network N, respectively. Here, the network N is a wired or wireless communication line such as the Internet. The camera 401 is installed in the experiential event venue 400 and is a photographing device capable of network communication. Note that there may be a plurality of experiential event venues 400 for each event.

In the following description, face authentication, which is an example of biometric authentication, is used as authentication for personal identification, and facial feature information, which is an example of biometric information, is used as personal identification information. However, biometric authentication and biometric information can be applied to other techniques that use captured images. For example, biometric information may be data (feature amounts) calculated from physical features unique to an individual, such as fingerprints, voiceprints, veins, retinas, and iris patterns. Further, authentication for personal identification may be other than biometric authentication, and personal identification information may be other than biometric information. Examples of personal identification information include, but are not limited to, a combination of an ID and a password, an electronic certificate, a two-dimensional code, and the like.

The recommendation system 1000 is used, for example, as follows. The user (parent) U11 uses the user terminal 101 to register the configuration of the family F1, the face images of the members (children) U13 and U14, the desired conditions for the experiential event, and the like in the recommendation device 300. FIG. The recommendation device 300 identifies experiential events suitable for members (children) U13 and U14 from an event DB (described later) in response to a recommendation request from the user terminal 101 or at a predetermined timing, and presents them to the user terminal 101. (Recommendation to. A user (parent) U11 uses the user terminal 101 to apply for participation in the recommended experiential event, and goes to the experiential event venue 400 with his family F1.

The experiential event venue 400 is assumed to be a venue for implementing the above recommended experiential event. Examples of experiential events include, but are not limited to, one-day farming experiences, language hiking, handicraft classes for each age group, robot programming classes, and the like. It is assumed that families F2, F3, and F4 are participating in the experiential event venue 400 on the day of the event. (For example, user (parent) U11 and member (child) U13 of family F1 may be user (parent) U41 and member (child) U43 of family F4. It is not necessary for all family members to participate, but at least members (children) should participate. For example, a user (parent) U31 of family F3 is accompanied by members (children) U33 and U34, and does not have to enter the experiential event venue 400. FIG.

The camera 401 captures the scenery including the participants during the event in the experiential event venue 400 and transmits the captured image to the recommendation device 300 via the network N. The camera 401 may shoot a moving image and transmit the moving image to the recommendation device 300 . The recommendation device 300 analyzes the moving image (captured image group) received from the camera 401 and determines whether or not the face image of the member registered in advance is included. In the case where the moving image includes the member's face image, the recommendation device 300 determines whether or not the storage condition is satisfied by determining whether or not the moving image satisfies the facial image of the member or their family members. to the experience history (described later).

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 register them in the experience history of the recommendation device 300. In addition, the user terminal 102 acquires and displays a photographed image during the event of the family member F4, especially the member (child) U43 from the experience history by the operation of the user (parent) U41.

After that, at a recommendation request from the user terminal 101 or at a predetermined timing, the recommendation device 300 selects members ( Child) Identify a hands-on event suitable for U13 and U14 and present (recommend) it to the user terminal 101.

The user terminal 101 is an information terminal owned and operated by the user (parent) U11. The user terminal 102 is an information terminal owned and operated by the user (parent) U41. The

user terminals

101 and 102 are, for example, information processing devices such as mobile phone terminals, smart phones, tablet terminals, and notebook computers with cameras. Since the configuration of the user terminal 102 is the same as that of the user terminal 101, illustration and detailed description thereof will be omitted below.

FIG. 4 is a block diagram showing the configuration of the user terminal 101 according to the second embodiment. User terminal 101 includes camera 110 , storage unit 120 , memory 130 , communication unit 140 , input/output unit 150 and control unit 160 .

The camera 110 is a photographing device that takes pictures of users and members under the control of the control unit 160 . The storage unit 120 is a storage device that stores a program 121 for realizing each function of the user terminal 101 . The storage unit 120 includes a storage device including non-volatile memory such as flash memory and SSD (Solid State Drive). The program 121 is a computer program in which user information registration processing, experience-based event participation application processing, acquisition and display processing of captured images during the event, experience record and growth record registration processing, and the like are implemented. The program 121 includes a client application for the recommendation device 300 according to this embodiment.

The memory 130 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 160 operates. The communication unit 140 is a communication interface with the network N. FIG. 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 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. Thereby, the control unit 160 realizes the functions of the registration unit 161 , the acquisition unit 162 and the display control unit 163 .

The registration unit 161 registers user information including the structure of the family F1 input by the user (parent) U11, personal information, face images of the members (children) U13 and U14, desired conditions for the experience-based event, and the like. The request is sent to the recommendation device 300 via the network N. Thereby, the registration unit 161 registers the user information in the recommendation device 300 . Further, the registration unit 161 accepts an operation of application for participation in the hands-on event recommended by the recommendation device 300 from the user (parent) U11, and sends a request for participation in the hands-on event to the recommendation device via the network N. 300. Further, the registration unit 161 transmits comments (experience information) and evaluation information regarding the event experiences of the members (children) U13 and U14, which are input by the user (parent) U11, to the recommendation device 300 via the network N. do. Further, the registration unit 161 transmits information indicating growth records of members (children) U13 and U14 input by the user (parent) U11 to the recommendation device 300 via the network N. FIG.

The acquisition unit 162 acquires information on the experiential event recommended by the recommendation device 300 via the network N, and outputs the acquired information on the experiential event to the display control unit 163 . In addition, the acquisition unit 162 acquires a group of captured images in which any member of the family F1 is captured during the event from the recommendation device 300 via the network N, and displays the acquired group of captured images on the display control unit 163. Output to Further, the acquisition unit 162 acquires the experience history and growth record of any member of the family F1 from the recommendation device 300 via the network N, and outputs the acquired experience history and growth record to the display control unit 163. .

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

Note that the user terminal 101 may transmit a recommendation request for a hands-on event to the recommendation device 300 via the network N in accordance with the operation of the user (parent) U11. In addition, the user terminal 101 may transmit a request to acquire a captured image group to the recommendation device 300 via the network N in response to an operation by the user (parent) U11. Further, the user terminal 101 may transmit a request to refer to the experience history and the growth record to the recommendation device 300 via the network N in accordance with the operation of the user (parent) U11.

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

Returning to FIG. 3, the description continues.
The authentication device 200 is an information processing device that stores facial feature information of a user or a member of the user's family. In addition, in response to a face authentication request received from the outside, the authentication device 200 compares the face image or face feature information included in the request with the face feature information of each user, and requests the result of matching (authentication result). Reply to original.

FIG. 5 is a block diagram showing the configuration of the authentication device 200 according to the second embodiment. The authentication device 200 includes a face information DB (DataBase) 210 , a face detection section 220 , a feature point extraction section 230 , a registration section 240 and an authentication section 250 . The face information DB 210 associates and stores a user ID 211 and face feature information 212 of the user ID. The facial feature information 212 is a set of feature points extracted from the facial image. Note that the authentication device 200 may delete the facial feature information 212 in the facial feature DB 210 at the request of the registered user of the facial feature information 212 . Alternatively, the authentication device 200 may delete the facial feature information 212 after a certain period of time has elapsed since the official registration.

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

The registration unit 240 newly issues a user ID 211 when registering facial feature information. The registration unit 240 associates the issued user ID 211 with the facial feature information 212 extracted from the registered image and registers them in the facial information DB 210 . Authentication unit 250 performs face authentication using facial feature information 212 . Specifically, the authentication unit 250 collates the facial feature information extracted from the facial image with the facial feature information 212 in the facial information DB 210 . If the verification is successful, the authentication unit 250 identifies the user ID 211 associated with the verified facial feature information 212 . The authenticating unit 250 replies to the requester as a face authentication result indicating whether or not the facial feature information matches. Whether the facial feature information matches or not corresponds to the success or failure of the authentication. Note that matching of facial feature information (matching) means a case where the degree of matching is equal to or greater than a threshold. Also, the face authentication result shall include the specified user ID when the face authentication is successful.

Return to Figure 3 and continue the explanation. The recommendation device 300 is an example of the recommendation device 1 described above. The recommendation device 300 performs user information registration processing, experience-based event recommendation processing, event application processing, registration and provision processing of captured images during the event, registration and reference processing of experience history, etc. (recommendation method processing). ). The recommendation device 300 may be made redundant by a plurality of servers, and each functional block may be implemented by a plurality of computers.

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, flash memory, SSD, or the like. Storage unit 310 stores program 311 , user information 312 , event DB 313 and experience history 314 . A program 311 is a computer program in which the processing of the recommendation method according to the second embodiment is implemented.

The user information 312 is information about the users of the recommendation system 1000 and their families, and information such as desired conditions for experience-based events. The user information 312 is information in which a user ID 3121, family information 3122, personal information 3123, desired conditions 3124, and growth record 3125 are associated with each other. The family information 3122 and personal information 3123 are examples of user attribute information. The user ID 3121 is identification information of the user (contractor) of the recommendation system 1000 . In the case of family F1, the user ID 3121 is the user ID of user (parent) U11.

The family information 3122 is information about the user's family. The family information 3122 is information in which a family structure 31220 and member IDs 31221 to 3122n (n is a natural number of 2 or more) are associated with each other. The family composition 31220 is information indicating the family composition of the user. Specifically, the family structure 31220 is a set of information relating to the relationship, gender, age, etc. of members belonging to the user's family. For example, in the case of family F1, the family structure 31220 is information such as father, mother, older brother 5 years old, and younger sister 2 years old. Members of the family are not limited to those who have a blood relationship or a kinship relationship with the user. The member ID 31221 and the like 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, member ID31222 is the user ID of member (child) U14. However, the member ID 31221 and the like should at least include the user ID of the participant of the hands-on event who wishes to be recommended. For example, a user (parent) U11 in a family F1 considers members (children) U13 and U14 to be participants, and wishes to recommend an experiential event in which member (children) U13 or U14 can participate. and In that case, the member ID 31221 and the like should include at least the user IDs of the members (children) U13 and U14.

Personal information 3123 includes the user's and family's residential area (address), user's contact information, payment information, etc. A user's contact information includes a telephone number, an application user ID, an e-mail address, and the like. The payment information includes account information of a financial institution from which the payment amount is withdrawn at the time of payment of the participation fee for a paid experience-type event, credit card information used for payment of the payment amount, and the like.

The desired condition 3124 is information indicating desired conditions for participating in the experience-based event. Desired condition 3124 includes request 31241 and schedule information 31242 . The request 31241 is information indicating a request for a hands-on event in the 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, the purpose of the experience, the content of the event that the child wants to experience, the parent's education policy for the child, and the like. For example, requests 31241 may include an event on Saturdays related to children's lessons, and an event on Sundays related to day trips for the whole family. Alternatively, the request 31241 may include a 5-year-old brother and a 2-year-old sister as conditions for participation in the event, and a nature experience that the brothers and sisters can enjoy as the event content. Schedule information 31242 is existing schedule information of the user's family. Existing schedule information includes hands-on events for which participation has been completed. The schedule information 31242 is an exclusion condition on the schedule of the recommended experience-type event, and is a condition not to be recommended, so it can be said to be a desired condition in a broad sense.

The growth record 3125 is information for recording the growth progress of each member. For example, the growth record 3125 may include information indicating lessons associated with member IDs, skill acquisition goals, achievement levels of acquisition, and the like.

It should be noted that each of the member IDs 31221 to 3122n described above is information that can be uniquely specified 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 and the like. Also, the user ID 3121 may be a member ID. The member IDs 31221 to 3122n may be associated with relationships in the family structure. For example, the member IDs 31221 to 3122n may be associated with information that distinguishes father, mother, older brother, and younger sister.

The event DB 313 is an example of a database in which information on multiple experiential events is registered. The event DB 313 includes event information 3131 to 313m (m is a natural number of 2 or more). The event information 3131 and the like preferably include an event ID, event name, field, content, date and time, location, participation requirements (target age, clothes, belongings), etc. of the experience-based event.

The experience history 314 is an event participation history that includes input information based on the experiences of members who have 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 photographed image group 3146 are associated with each other. The user ID 3141 is identification information of the user who applied for the event, and corresponds to the user ID 3121 . User ID 3141 is the user ID of a user who is a family member of the member who participated in the event. In other words, the user ID 3141 can be said to be the user ID 3121 including the member ID 3143 in the family information 3122 . The event information 3142 is event information in which an application for participation was made and the members actually participated. The event information 3142 may contain at least the event ID in the event DB 313 . Member ID 3143 is identification information of a member who applied for participation and actually participated in the event. The experience information 3144 is input information, such as text information, based on the experiences of the members who participated in the experience-based event. The evaluation information 3145 is information indicating the evaluation by the users or members (participants) of the experiential event in which they participated. The rating information 3145 may be an index value, eg, a rating level value. A captured image group 3146 is a set of images that include members and satisfy predetermined registration conditions, among captured images of scenery including participants during the event. The captured image group 3146 may be a moving image.

The memory 320 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 340 operates. A communication unit 330 is a communication interface with the network N. FIG.

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

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, user's personal information, facial images of event participants, desired conditions for experience-based events, and the like. The acquisition unit 341 acquires experience-type event recommendation requests and participation application requests, photographed image group registration requests and acquisition requests, experience history and growth record registration or reference requests, and the like.

The registration unit 342 generates user information 312 based on the acquired user information registration request and registers it in the storage unit 310 . Specifically, registration unit 342 transmits a face information registration request including the face image included in the registration request to authentication device 200 . Then, the registration unit 342 acquires the user ID issued by the authentication device 200 in accordance with the registration of the face information. When multiple face images are included, the registration unit 342 may transmit a face information registration request for each face image (member). Further, the registration unit 342 may issue a new user ID. Note that the registration unit 342 may use one of the user IDs issued according to the registration of the face information as the user ID. The registration unit 342 uses the issued user ID as a member ID, and generates user information 312 by associating the user ID with the family structure, personal information, and desired conditions included in the registration request. Since member IDs are associated with facial feature information as described above, the registration unit 342 associates the biometric information, attribute information, and desired conditions of each member of the user and registers them as user information. It can be said.

Also, when a registration request for experience history (input information) is acquired, the registration unit 342 associates the input information, the experience-based event, and the member and registers them in the experience history 314 . Further, when a growth record (input information) registration request is acquired, the registration unit 342 registers the growth record 3125 in the storage unit 310 in association with the user ID 3121 .

In addition, when the determination unit 346 determines that the captured image can be registered, the registration unit 342 stores the captured image in the experience history of the member corresponding to the face feature information (or member ID) that has successfully passed face authentication. sign up.

When the user ID is included in the registration request, that is, when the user ID has been issued and the user information has been registered, and the family information, personal information, desired conditions, and growth record are updated, the registration unit 342 updates the user information 312 corresponding to the user ID included in the registration request.

When the authentication control unit 343 receives a request for registering a captured image group from the camera 401, it extracts a face image from the captured image group and causes the authentication device 200 to perform face authentication on the extracted face image. In other words, the authentication control unit 343 controls biometric authentication using biometric information for the captured images of the participants captured during 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 . Note that the authentication control unit 343 may detect the user's face area from the face image and include the image of the face area in the face authentication request. Alternatively, the authentication control unit 343 may extract facial feature information from the face area and include the facial feature information in the face authentication request. The authentication control unit 343 determines success or failure of face authentication based on the received result of face authentication. When determining that the face authentication has succeeded, the authentication control unit 343 identifies the user ID included in the face authentication result.

The identification unit 344 is an example of the identification unit 12 described above. The identification unit 344 identifies, from the event DB 313, a hands-on event suitable for at least some members in the family information based on family composition, personal information and desired conditions. In particular, when the request 31241 is included in the desired condition 3124, the identifying unit 344 identifies a hands-on event that satisfies the request. Also, when the desired condition 3124 includes the schedule information 31242 , the identifying unit 344 identifies a hands-on event held on a schedule other than the schedule information 31242 . Further, the identifying unit 344 may identify a hands-on event based on the schedule content included in the schedule information 31242 . For example, if the schedule information 31242 includes lessons in an English conversation class every Saturday, the identifying unit 344 may identify after-school English childcare on weekdays and events related to English on Sundays as experiential events. . Also, when the family structure 31220 includes attributes of children of the user as members, the identifying unit 344 identifies experiential events in which the children's age and the like satisfy participation requirements. For example, the identifying unit 344 extracts a keyword group, an event field, member ages, and 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, Identify event information that meets your search criteria. Note that, when a plurality of pieces of event information satisfying the search condition are hit, the specifying unit 344 may assign a recommendation priority according to the degree of satisfaction of the search condition. It should be noted that the identification unit 344 may further consider the input information (experience history and growth record) to identify the experiential event. As a result, it is possible to accurately identify an experiential event that is more suitable for the needs of the user's family.

Note that the identifying unit 344 may identify a hands-on event using a predetermined model (processing logic). Specifically, the model inputs family structure, personal information and desired conditions (further growth record and experience history), identifies experiential events suitable for members from the event DB 313, and It may be something that outputs a type event. A known technique such as an AI (Artificial Intelligence) model can be applied to the model. In addition, the model can be machine-learned using accumulated family structure, personal information, desired conditions, growth records, and experience history as teacher data and experiential events as correct data.

The recommendation unit 345 is an example of the recommendation unit 13 described above. The recommendation unit 345 recommends the specified experiential event to the user terminal 101 or the like of the user.

When the face image in the captured image acquired from the camera 401 is successfully authenticated, the determination unit 346 determines whether registration is possible based on the analysis result of the captured image. Specifically, the determination unit 346 analyzes the degree of satisfaction of the experiential event of the member corresponding to the facial feature information for which face authentication has succeeded from the photographed image, and if the degree of satisfaction is equal to or higher than a predetermined value, it is determined that registration is possible. judge.

Note that the recommendation device 300 may perform processing for providing a group of captured images in response to an acquisition request for a group of captured images during an event from the user terminal 101 or the like. For example, when the recommendation device 300 receives a request to acquire a captured image group including a user ID and an event ID from the user terminal 101, it reads the captured image group 3146 associated with the user ID and the event ID. Then, the recommendation device 300 transmits the read photographed image group 3146 via the network N to the user terminal 101 that is the source of the request. Thereby, the family F1 including the user (parent) U11 can visually recognize the photographed image group 3146 displayed on the user terminal 101. FIG.

Next, a description will be given of user information registration processing, experiential event recommendation processing, event application acceptance processing, registration processing of a group of captured images during an event, registration processing of experience history, etc., according to the second embodiment. For example, the user (parent) U11 uses the user terminal 101 to register user information in order to receive recommendations for experiential events suitable for members (children) U13 and U14. In this case, the user terminal 101 accepts input of family composition, face images of members (children) U13 and U14, personal information, and desired conditions from the user (parent) U11. The user terminal 101 may accept the face image of the user (parent) U11 or member (parent) U12. In addition, the user terminal 101 may receive identification information (relationship, etc.) as a family member together with each face image. Here, the user terminal 101 may take images of the members (children) U13 and U14 with the camera 110 to acquire their facial images. Alternatively, the user terminal 101 may acquire the 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 receives input of various information from the user (parent) U11 via the registration screen.

FIG. 7 is a diagram showing an example of a user information registration screen according to the second embodiment. The desired condition registration screen 61 includes a day of the week selection column 611, a lesson selection column 612, and a registration button 613 when the desired condition for the experiential event is a weekend lesson. A selection column 611 shows an example in which Saturday is selected. A selection column 612 shows an example in which English is selected. When the registration button 613 is pressed, a usage information registration request including selection items in the selection fields 611 and 612 is transmitted to the recommendation device 300 . It is assumed that there are user information registration screens other than the desired condition registration screen 61, such as a family composition, face image, personal information, and schedule information registration screen. When the registration button on any of the screens is pressed, the user terminal 101 registers usage information including the entered family composition, face image, personal information, and desired conditions (requests (weekend lessons) and schedule information). The request is sent to the recommendation device 300 via the network N. It is assumed that identification information of the member is attached to each face image.

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

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 sends a first face information registration request including the face image of member (child) U13 and a second face information registration request including the face image of member (child) U14. You may send.

FIG. 9 is a flow chart showing the flow of face information registration processing by the authentication device 200 according to the second embodiment. Here, the information registration terminal (not shown) photographs the user's body including the face, and transmits a face information registration request including the photographed image (registered 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 smart phone, or a tablet terminal. For example, the information registration terminal may be the user terminal 101 or the like. Here, it is assumed that the information registration terminal is the recommendation device 300 that has received a registration request from the user terminal 101 or the like.

First, the authentication device 200 receives a face information registration request (S201). For example, the authentication device 200 receives a face information registration request via the network N from the recommendation device 300 . Next, the face detection unit 220 detects a face area from the 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 the 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 facial information DB 210 (S205). After that, the registration unit 240 returns the issued user ID 211 to the request source (the information registration terminal, for example, the recommendation device 300) (S206).

Return to Fig. 8 and continue the explanation. The registration unit 342 of the recommendation device 300 acquires the user ID issued according to the registration of the face information from the authentication device 200 (S303). Here, user IDs issued in response to each of the first and second face information registration requests are acquired as member IDs. In this example, since the face image of user (parent) U11 is not included in the registration request, registration unit 342 newly issues a user ID. However, if the registration request includes the face image of the user (parent) U11 or member (parent) U12, the registration unit 342 transmits the third and fourth face information registration requests to the authentication device 200, and A user ID issued in response to a request is acquired as a member ID. Further, the registration unit 342 associates the acquired user ID with the identification information of the member assigned to the face image.

Subsequently, the registration unit 342 generates user information 312 (S304). Specifically, registration unit 342 generates family information 3122 including family structure 31220 included in the registration request and a set of member IDs 31221 and the like acquired in step S303. Then, the registration unit 342 generates the user information 312 by associating the issued user ID 3121 with the family information 3122 and the personal information 3123 and desired conditions 3124 included in the registration request. 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. FIG. User terminal 101 stores the received user ID in storage unit 120 .

FIG. 10 is a flowchart showing the flow of recommendation processing according to the second embodiment. For example, the user terminal 101 receives a recommendation request for an experiential event based on the user information registered from the user (parent) U11, and sends the recommendation request including the user ID to the recommendation device 300 via the network N. Send. A case where a recommendation request is transmitted will be described below.

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 the user ID included in the received recommendation request. The acquisition unit 341 acquires the 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 the face image of the user or member instead of the user ID. In that case, the authentication control unit 343 may specify the user ID by controlling face authentication, which will be described later, for the face image included in the recommendation request. Then, the acquisition unit 341 may acquire the family composition 31220, the personal information 3123, and the desired conditions 3124 associated with the user ID for which face authentication has succeeded as the user ID 3121, the member ID 31221, or the like.

Subsequently, the identifying unit 344 identifies, from the event DB 313, a hands-on event suitable for at least the members (children) U13 and U14 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 father, mother, older brother 5 years old, younger sister 2 years old, etc. Request 31241 included in the personal information 3123 is an event related to children's lessons on Saturday and a day trip that the whole family can participate on Sunday. Suppose that it is an event related to In this case, the identifying unit 344 identifies, as experiential events, lessons suitable for a 5-year-old boy (which satisfies participation conditions) and lessons suitable for a 2-year-old girl, which are held on Saturdays. In addition, the identification unit 344 identifies, as an experiential event, a 5-year-old boy, a 2-year-old girl, a father, and a mother who satisfy the participation conditions and which is carried out on Sunday.

After that, the recommendation unit 345 transmits the specified experiential event (group) to the user terminal 101 of the user (parent) U11 (S314). In response, the user terminal 101 displays the received experiential event on the input/output unit 150 as a recommendation screen.

Note that 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 specified experiential event to the user terminal of the user to be recommended.

FIG. 11 is a diagram showing an example of the experience-based event recommendation screen 62 according to the second embodiment. The experience-based event recommendation screen 62 includes event information 621 and a participation application button 622 . The event information 621 is an example showing, for example, the name of the experience-based event to be recommended, the date and time of the event, an explanation, the target age group (participation conditions), and the location of the event. When the participation application button 622 is pressed, a screen for inputting or selecting a participant name is displayed.

When the user terminal 101 accepts input or selection of participant names, it sends a participation application request including a list of participant names, user IDs, event IDs, etc. to the recommendation device 300 via the network N. The recommendation device 300 performs application processing for the event based on the information included in the received participation application request. If the event for which the application is made is charged, the recommendation device 300 uses the payment information included in the personal information 3123 associated with the user ID 3121 to settle the usage fee. After that, the user (parent) U11 goes to the experiential event site 400 with the family F1 and participates in the event.

The camera 401 of the experiential event venue 400 takes a picture of the scenery including the participants of the event during the event, and transmits a registration request including the taken image to the recommendation device 300 via the network N. It is assumed that the registration request includes information specifying the event in progress. For example, it is assumed that the registration request includes an event ID, identification information of the camera 401, and the like. Also, the registration request may include video data shot by the camera 401 .

FIG. 12 is a flow chart showing the flow of registration processing of captured images during an event according to the second embodiment. First, the acquisition unit 341 acquires from the camera 401 via the network N a registration request including a photographed image of a participant during the hands-on event (S321). Next, the authentication control unit 343 extracts a face image from the photographed 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. If the registration request includes moving image data, the authentication control unit 343 may extract a face image from some frame images of the moving image data. The authentication control unit 343 then transmits a face authentication request including the extracted face image to the authentication device 200 via the network N (S323).

FIG. 13 is a flow chart 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 facial feature information from the face image included in the face authentication request, similarly to steps S202 and S203 described above. Then, the authentication unit 250 of the authentication device 200 collates the facial feature information extracted from the face image included in the face authentication request with the facial feature information 212 of the face information DB 210 (S212), and calculates the matching degree. Then, the authentication unit 250 determines whether or not the degree of matching is equal to or greater than the threshold (S213). If the facial feature information matches, that is, if the degree of matching of the facial feature information is equal to or greater than the threshold, the authentication unit 250 identifies the user ID 211 associated with the facial feature information 212 (S214). Then, the authentication unit 250 returns the result of the face authentication including the result of the successful face authentication and the identified user ID 211 to the recommendation device 300 via the network N (S215). If the degree of matching is less than the threshold in step S213, the authenticating unit 250 returns the face authentication result including the failure of the face authentication to the recommendation device 300 via the network N (S216).

Return to Fig. 12 and continue the explanation. 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 determines success or failure of face authentication from the received result of face authentication (S325). When determining that the face authentication has succeeded, the authentication control unit 343 identifies the user ID included in the face authentication result. Then, the identifying unit 344 identifies the member ID corresponding to the user ID for which face authentication has succeeded, from the user information 312 (S326). The identifying unit 344 also identifies the user ID 3121 associated with the identified member ID. If a plurality of face images are extracted from the photographed image in step S322, steps S323 to S325 are executed for the number of extracted face images. Alternatively, authentication control unit 343 transmits a face authentication request including a plurality of face images extracted in step S323, and authentication device 200 collectively returns face authentication results for each face image in the face authentication request. You may In these cases, the identification unit 344 may identify a plurality of member IDs in step S326. For example, the member IDs of two members (children) U33 and U34 may be identified. Alternatively, two member IDs of members (children) U34 and U43 belonging to different families may be identified. In this case, the identification unit 344 determines 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. also identify.

Then, the determination unit 346 analyzes the face image for which face authentication has succeeded and calculates the degree of satisfaction (S327). For example, the determination unit 346 may apply smile analysis technology to the face image to calculate the degree of smile as the degree of satisfaction. Then, the determination unit 346 determines whether 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 may determine that registration is possible when the degree is equal to or greater than the predetermined value.

If it is determined in step S328 that registration is possible, the registration unit 342 associates the photographed image acquired in step S321 with the member ID specified 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 photographed image (the photographed image group 3146) with each other to perform the experience. Register in history 314 . Note that when a plurality of member IDs are specified in step S326, the registration unit 342 registers captured images in the experience history 314 for each user ID corresponding to each member ID. For example, when the member IDs of two members (children) U33 and U34 of the same family F3 are identified, the user ID of user (parent) U31 is identified. At this time, the registration unit 342 associates the identified user ID, the two member IDs, the event ID, and the captured image with each other and registers them in the experience history 314 . Also, in this case, the degree of smile of the siblings included in the photographed image is equal to or greater than a predetermined value. Therefore, it is possible to record a photograph of the siblings of the family F3 enjoying the hands-on event together. Alternatively, the determining unit 346 may determine that registration is possible even when one of the brothers' smile levels is less than a predetermined value and the other is greater than or equal to a predetermined value. Thereby, the user (parent) U31 can grasp the case (event) in which one of the siblings is not enjoying themselves. On the other hand, when two member IDs of members (children) U34 and U43 belonging to different families are specified, the user ID of user (parent) U31 and the user ID of user (parent) U41 are identified. At this time, the registration unit 342 registers the photographed image in the experience history 314 in association with the user ID or the like of the user (parent) U31, and also associates the same with the user ID or the like of the user (parent) U41. The photographed image is registered in the experience history 314 . Also, when moving image data is included in the registration request, the registration unit 342 may register at least part of the moving image data as the captured image group 3146 . If face authentication fails in step S325, or if it is determined that registration is not possible in step S328, the process ends.

After the event has been held at the experience-based event venue 400, the recommendation device 300 sends a message requesting input of experience records and the like to the user terminal of the user who applied for participation. For example, the user (parent) U41 of family F4 who participated in the experience-based event, through the registration screen of the event experience record displayed on the user terminal 102 after the end of the event, member (child) who is a participant Enter the event experience record and growth record of U43. That is, the user terminal 102 receives input information such as comments (experience information) and satisfaction levels (evaluation information) regarding the event experience of the member (child) U43 from the user (parent) U41.

FIG. 14 is a diagram showing an example of an event experience record registration screen 63 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 desired input field 633 , and a register button 634 . The experience record input column 631 is a comment input column regarding the event experience. The experience record input field 631 is an example of a questionnaire or the like in which the user (parent) U41 inputs the situation of the member (child) U43 or the like participating in the event in text, but is not limited to this. The satisfaction level input field 632 is a field for inputting the level of satisfaction as evaluation information for the experience-based event in which the user has participated. Here, the satisfaction level is evaluated in five grades, but the method of evaluating the satisfaction level is not limited to this. The next desired input column 633 is an input column for desired fields, dates, and the like of the next experience-type event that the user wants to participate in, that is, the next experience-type event that the user wants to be recommended. When the registration button 634 is pressed, an experience record (experience history) registration request including the input information on the event experience record registration screen 63 , the event ID, and the user ID is transmitted to the recommendation device 300 . That is, 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. FIG.

After that, the acquisition unit 341 of the recommendation device 300 acquires an experience history registration request 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 registers (updates) the acquired user ID 3141 , event ID (event information 3142 ), and input information (experience information 3144 ) in the experience history 314 in association with each other. The registration unit 342 may additionally register the input contents of the next desired input field 633 in the acquired input information as a request 31241 in the user information 312 in association with the acquired user ID 3121 .

In addition, the user (parent) U41 can input the growth record of the member (child) U43 accompanying event participation via the user terminal 102 after one or more experiential events have ended. The user terminal 102 displays a growth record registration screen in response to an operation by the user (parent) U41 or in response to a notification from the recommendation device 300 at a predetermined timing.

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 register button 644 . The lesson selection column 641 is a column for selecting the field of lessons recommended as an experiential event and in which the member (child) U43 has participated. The lesson selection column 641 indicates that English conversation is selected as a lesson. The target input column 642 is a column for inputting target information of a skill that the user (parent) U41 wants the member (child) U43 to acquire. The achievement status input column 643 is a column for the user (parent) U41 to input the achievement status of the skill acquired by the member (child) U43 in the target input column 642. FIG. When the registration button 644 is pressed, a growth record registration request including the input information on the growth record registration screen 64 , the member ID, and the user ID is transmitted to the recommendation device 300 . In other words, when the registration button 644 is pressed, the user terminal 102 transmits the growth record registration request to the recommendation device 300 via the network N. FIG.

After that, the acquisition unit 341 of the recommendation device 300 acquires a growth record registration request 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.) with the input information (growth record 3125). That is, the registration unit 342 additionally registers the acquired input information as the growth record 3125 in the user information 312 in association with the user ID 3121 .

The organizer of the experience-based event may provide the user with event record information (such as a diary) that records the state of the participants (children) during the event experience. For example, the host's terminal (not shown) transmits the event record information to the recommendation device 300 via the network N. FIG. The event record information includes text information in which the host etc. recorded the state of each participant, an event ID, and participant information (user ID, member ID, personal information, etc.). The event record information may also include evaluations of the participants by the organizer or the like (for example, the level of proficiency in English and achievement status). The recommendation device 300 registers the text information of the received event record information in the experience history 314 (experience information 3144 thereof) in association with each user or member. In addition, the recommendation device 300 registers the evaluation of the received event record information in the growth record 3125 in association with each user or member. Then, the recommendation device 300 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. As a result, for example, the user (parent) U41 can grasp how the member (child) U43 is experiencing the event and the growth record from the organizer's side records. Further, the user (parent) U41 may make an input to the event experience record registration screen 63 or the growth record registration screen 64 based on the event record information.

FIG. 16 is a diagram showing an example of the display screen 63a of the event experience record by the organizer according to the second embodiment. The event experience record display screen 63a by the organizer includes an observation record display column 631a by the person in charge, a proficiency level display column 632a, and a registration screen display button 634a. The observation record display column 631a is a column for displaying a record of observations of participants (for example, children) by the person in charge of the organizer of the experiential event. The observation record display column 631a corresponds to the display column of the text information of the received event record information. The proficiency level display column 632a is a display column for the proficiency level of the participant evaluated by the person in charge of the organizer of the experience-based event. The proficiency level display field 632a corresponds to a display field for 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.

Furthermore, the recommendation device 300 transmits a group of captured images 3146 of the corresponding user or member to the user terminal of the user corresponding to the event record information. In response to this, the user terminal displays the received captured image group. As a result, the user (parent) U41 can visually recognize how the member (child) U43 is experiencing the event, in particular, the smiling scene.

After that, the recommendation device 300 makes a recommendation (re-recommendation) for the next experiential event in consideration of the registered experience history and growth record. FIG. 17 is a flowchart showing the flow of re-recommendation processing 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). The acquisition unit 341 also 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).

Subsequently, the identifying unit 344 identifies, from the event DB 313, a hands-on event suitable for at least the member (child) U43 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 the grape picking event, the agricultural experience may be identified as the hands-on event. In addition, when the member (child) U43 is highly satisfied with the English learning event, the language hiking may be identified as the experiential event. At this time, the user information (growth record) and experience history used by the identifying unit 344 to identify the event may include the event record information input by the host side described above. Therefore, it is possible to comprehensively judge and specify an event suitable for the member. For example, the identifying unit 344 may identify an advanced class event for participants evaluated as having high proficiency in English, and a beginner class event for participants evaluated as having low proficiency in English.

After that, the recommendation unit 345 transmits the specified experiential event (group) to the user terminal 102 of the user (parent) U41 (S314). In response, the user terminal 102 displays the received experiential event on the input/output unit 150 as a recommendation screen.

FIG. 18 is a diagram showing an example of the experiential event re-recommendation screen 65 according to the second embodiment. The experience-based event re-recommendation screen 65 includes event information 651 and a participation application button 652 . The event information 651 and participation application button 652 are the same as the event information 621 and participation application button 622 in FIG. 11 described above. In other words, the user (parent) U41 can receive a recommendation of an experiential event specified in consideration of experience history and growth record. As a result, an experiential event that better satisfies the needs of the family is recommended, and the user's family can participate in such an experiential event.

In this way, according to this embodiment, it is possible to support the search for experiential events for early childhood children that meet the needs of families from among a large number of educational contents. And we can provide a variety of experience opportunities.

<Embodiment 3>
Embodiment 3 is another example of Embodiment 2 described above. The third embodiment also recommends information (attached information) attached to the specified experiential event. Here, in the third embodiment, it is assumed that the attached information is acquired from an external business operator or the like. However, the recommendation device may further identify attached information of the identified experiential event using internal processing logic or a database, and recommend the attached information to the user.

FIG. 19 is a block diagram showing the overall configuration of a recommendation system 1000a according to the third embodiment. 3, the recommendation system 1000a replaces the recommendation device 300 with the recommendation device 300a and adds an external server 501 to 50k (k is a natural number of 2 or more). Since other configurations are the same as those in FIG. 3, illustration and detailed description of overlapping contents are omitted.

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 operator. Business operators include, but are not limited to, travel agencies, event companies, transportation facilities, toy manufacturers, leisure manufacturers, insurance companies, real estate developers, and the like. The external server 501 receives, via the network N from the recommendation device 300a, experience-based events, attribute information, desired conditions, and the like, which are recommended to specific users and their families. The external server 501 uses a predetermined logic to determine attached information of the experience-based event based on the received experience-type event, attribute information, desired conditions, etc., and recommends the determined attached information via the network N. Reply to device 300a. It should be noted that the above-described AI model or the like may be used for the predetermined logic. It is assumed that the external servers 502 (not shown) to 50k also operate in the same manner.

Here, the attached information may be an attached service of the experiential event. Ancillary services include, for example, introduction information such as transportation available when moving to the event venue, parking lots near the event venue, commercial facilities, accommodation facilities, restaurants (where you can eat with children), insurance, etc. be done. The means of transportation includes information on tickets for railroads, buses, taxis, airplanes, etc., as well as information on rental cars and car sharing shops, vehicle types, and the like. In addition, the accessory service may include privilege information of services that can be used when participating in the experience-based event. The privilege information is, for example, event participation fees, transportation means, parking lots, commercial facilities, lodging facilities, discount coupons that can be used for settlement of restaurants, point information, and the like.

Also, the attached information may be advertising information related to the experience-based event. Also, the attached information may be information on rental products used in the hands-on event.

FIG. 20 is a block diagram showing the configuration of the recommendation device 300a according to the third embodiment. The recommendation device 300a has a program 311a changed and a notification unit 347 added, as compared with FIG. 6 described above. Since other configurations are the same as those in FIG. 6, detailed descriptions of overlapping contents will be omitted.

The program 311a is a computer program in which the processing of the recommendation method according to the third embodiment is implemented.

The notification unit 347 is a first notification unit that notifies at least the first external server of the identified experiential event, attribute information, and desired conditions. The acquisition unit 341 acquires attached information about the specified experience-based event from the first external server. Then, the recommendation unit 345 presents the acquired attached information to the user. As a result, it is possible to receive proposals of attached information about experiential events from the business operator or the like that operates the first external server, and to implement total recommendations including the identified experiential events and attached information. Therefore, the user's family can obtain useful information related to the event, further promoting event participation.

In particular, the notification unit 347 preferably notifies two or more external servers 501 to 50k of the identified experiential event, attribute information, and desired conditions. In this case, the acquisition unit 341 collects attached information from each external server. Then, the recommendation unit 345 collectively presents the collected attached information to the user. It is possible to realize a more complete total recommendation including a lot of attached information. Note that the notification unit 347 may further notify an external server of the experience history. As a result, it is possible to acquire additional information that is more suitable for the needs of the family.

Also, when the acquisition unit 341 acquires the above-described attached service as attached information, the recommendation unit 345 further recommends the attached service to the user. As a result, the user can collectively apply for ancillary services together with the experience-based event, saving the trouble of searching for services related to the event and increasing convenience. Further, when the attached information includes the privilege information described above, the user can use a coupon or the like as he/she participates in the event, which promotes application for participation.

Further, when the acquisition unit 341 acquires the above-described advertising information as attached information, the recommendation unit 345 may recommend the specified experience-based event and present the acquired advertising information. This improves the advertising effectiveness associated with the event.

In addition, when the acquisition unit 341 acquires information on rental products used in a hands-on event as attached information, the recommendation unit 345 may recommend the specified hands-on event and the acquired information on rental products. As a result, the user can apply for the necessary rental products together with the application for the event, thereby improving convenience.

Note that the acquisition unit 341 may acquire the payment information of the fee associated with the presentation of the attached information from an external server. In other words, the operator of recommendation device 300a may obtain a commission for presenting attached information from the business operator.

FIG. 21 is a sequence diagram showing an example flow of recommendation processing including attached information according to the third embodiment. First, the recommendation device 300a identifies a hands-on event suitable for the family of a specific user (for example, user (parent) U11) (S401). For example, it is specified as in steps S312 and S313 of FIG. 10 described above. Next, the recommendation device 300a transmits the specified event information (experience-based event) to the user terminal 101 of the user (parent) U11 to recommend (S402). In response, the user terminal 101 accepts a participation application for the recommended event from the user (parent) U11, and transmits a participation application request to the recommendation device 300a (S403).

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

The external server 501 determines attached information based on the notified information (S4051). The external server 501 then transmits the determined attached information to the recommendation device 300a via the network N (S4061). Other external servers are similar. For example, the external server 50k determines attached information based on the notified information (S405k). The external server 50k then transmits the determined attached information to the recommendation device 300a via the network N (S406k).

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

The user terminal 101 accepts an application for the presented attached information from the user (parent) U11, and transmits an application request designating the attached information to the recommendation device 300a via the network N (S409). For example, the user terminal 101 may apply for additional services or rental products. Note that the user terminal 101 may directly transmit the application request to the external server that provides the attached information. When the attached information is advertising information, the user terminal 101 may transmit a request to the server that provides the advertising information in response to the advertisement information selection operation by the user (parent) U11.

After that, the recommendation device 300a may perform application processing on behalf of the relevant external server in response to the application for the attached information. In addition, the external servers 501 to 50k perform fee payment processing to the operator of the recommendation device 300a in response to the presentation (recommendation, etc.) of the attached information to the user. Alternatively, the external servers 501 to 50k may pay the operator of the recommendation device 300a a fee in response to a user applying for the attached information or referring to the advertisement information. . Specifically, the external servers 501 to 50k may perform remittance processing from their own account to the account of the operator of the recommendation device 300a in the system of the financial institution. At this time, each of the external servers 501 to 50k may transmit the remittance result as payment information to the recommendation device 300a via the network N (S4101 to S410k). Alternatively, instead of the external server performing the remittance process, the recommendation device 300a may perform the remittance process according to steps S4101 to S410k.

FIG. 22 is a sequence diagram showing the flow of another example of recommendation processing including attached information according to the third embodiment. Here, before recommending the specified experience-based event to the user, attached information is collected, and an example is shown in which the experience-based event and the attached information are collectively recommended to the user. After step S401, the recommendation device 300a notifies the specified event, user information 312 and experience history 314 of the user (parent) U11 to the external servers 501 to 50k via the network N (S4111 to S411k). Steps S4051 to S405k, S4061 to S406k, and S407 are the same as in FIG. 21 described above. Then, the recommendation device 300a transmits (presents) the identified experiential event and the aggregated attached information group to the user terminal 101 via the network N (S408a). The user terminal 101 receives an application for participation in the recommended event and an application for the presented attached information from the user (parent) U11. Then, the user terminal 101 transmits an event participation application request and an application request specifying attached information to the recommendation device 300a via the network N (S409a). The recommendation device 300a performs application processing for the relevant event based on the participation application request as described above. In addition, the recommendation device 300a may perform application processing on behalf of a corresponding external server in response to an application for attached information. Further, each of the external servers 501 to 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 to S410k).

In the above example, all the external servers 501 to 50k that have received data (S4041 to S404k, etc.) from the recommendation device 300a present attached information, but this is not always necessary. For example, some or all of the external server 501 and the like may not present the attached information to the recommendation device 300a. For example, a business operator such as the external server 501 may utilize the data (event information, user information, experience history, etc.) provided by the recommendation device 300a for their own marketing and development of products and services. At this time, the operator of the external server 501 or the like may pay the data provision fee to the operator of the recommendation device 300a. Also, the external server 501 or the like 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 the user's personal information, the accumulated experience history, etc. to a third party for a charge or free of charge. For example, if the business operator to whom the accumulated data is transferred is a real estate developer, the real estate developer may analyze the characteristics of each area where residents live and provide services and information suitable for each resident. good. In addition, real estate developers can improve the value of condominiums and areas by utilizing the provided data. Also, if the operator to whom the accumulated data is transferred is a search site operator, it is possible to acquire new customers and improve the utilization rate of the site.

It should be noted that the operator of the recommendation device 300a may tie up with an external business operator to make a total recommendation. Specifically, as described above, the attached information may be information on rental products used in experiential events. For example, if the experiential event is outdoor camping, the attached information is tent supplies. In this case, the recommendation unit 345 may recommend outdoor camping and rental of tent equipment free of charge. As a result, the user's family can obtain an opportunity to try out the products of the predetermined manufacturer at the hands-on event. And there is a possibility that it will lead to the purchase of the product. Therefore, the tie-up can be expected to be effective in advertising the product. Therefore, the tie-up business operator pays the operator of the recommendation device 300a a tie-up fee or a posted advertisement fee.

<Embodiment 4>
Embodiment 4 is another example of Embodiment 2 described above. In the fourth embodiment, a case will be described in which accumulated data is provided to a local government or a business operator, and a hands-on event newly planned by the provider is registered in the event DB. Note that the schematic configuration of the recommendation system and the recommendation device are the same as those of the above-described third embodiment, so illustration and description are omitted.

The recommendation device according to the fourth embodiment further includes a second notification unit that notifies the second external server (at least part of 501 to 50k) of attribute information, desired conditions, and experience history. The second notifier may be the notifier 347 described above. Then, 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 the acquired new experiential event information to the database (event DB 313). As a result, it is possible to plan and recommend events with higher needs by considering the experience history, desired conditions, and attribute information of the families who actually participated in the experience-based event.

　Furthermore, the attribute information should 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 identified attribute information of the plurality of users and the experience history of each user. This makes it possible to plan and recommend events that meet local needs. For example, if a weekend agricultural experience event is highly rated by many participants in the area, the local government in the area may plan a new food education event. Alternatively, if English conversation is often requested by users in a certain area, it is conceivable that the operator in that area will newly plan an English conversation event.

FIG. 23 is a sequence diagram showing the flow of new event registration processing according to the fourth embodiment. First, the identification unit 344 extracts user information and experience history of a specific area at a predetermined timing (S501). Specifically, the specifying unit 344 may start this process in response to a request from the business operator of the second external server (external server 501, for example) or the local government. Alternatively, the identifying unit 344 may periodically start this process. Then, the identifying unit 344 identifies an address included in the personal information 3123 of the user information 312 that corresponds to a specific area (for example, a specific prefecture or municipality). The specifying unit 344 then specifies the experience history 314 corresponding to the user ID 3121 of the specified user information 312 .

After that, the notification unit 347 transmits the user information 312 and the experience history 314 specified in step S501 to the external server 501 via the network N (S502). The external server 501 plans a new experiential 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 the screen to support event planning by the person in charge. Then, external server 501 receives information on events 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 receive an output of a plan for a new experience-based event. After that, the external server 501 transmits a registration request for the planned new experiential event to the recommendation device 300a via the network N (S504).

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 the acquired new experience-based event information to the event DB 313 (S505). As a result, the added event information can also be recommended in subsequent recommendation processing. Therefore, the contents of the event DB can be further enhanced. For example, the local government that operates the external server 501 can plan new events such as educational support related to events that were popular (highly rated) by local residents.

The local government that operates the external server 501 may provide administrative services suitable for each resident based on the data provided from the recommendation device 300a.

<Other embodiments>
Note that the

recommendation device

300 or 300a may recommend a hands-on event based on the experience history of family members other than the user. For example, the recommendation device 300 or the like may recommend an event that is highly satisfied by other residents in the neighborhood of the user or an event that is frequently used by residents living within a certain range. Also, the recommendation device 300 or the like may recommend a hands-on event using word-of-mouth information about the event. For example, the recommendation device 300 or the like may specify an event to be recommended using experience information or evaluation information of users or members (mothers with children of the same age) who have similar attributes.

It should be noted that the event DB 313 (database) may include the infectious disease countermeasure status of each of a plurality of experience-based events. In that case, the identification unit identifies the experience-based event by further considering the status of infectious disease countermeasures. This allows the user (parent) to apply for participation after confirming the safety of the recommended event.

Here, the infectious disease control status is a safety indicator that indicates the difficulty of being infected with an infectious disease at the event venue and the safety against the spread of infection. As for the safety index, the higher the degree of the 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 that indicates the low risk of infection. In addition, the safety index can also be said to be an index that indicates the degree of infection prevention measures at the store. Therefore, the recommendation unit 345 may add a safety index to the information of the experience-based event to be recommended and transmit the information to the request source. Further, when a plurality of experiential events are specified, the specifying unit 344 assigns a priority according to the safety index of each event, and the recommending unit 345 assigns a priority to the plural experiential events. May recommend.

Note that when the request of the user is blank, the recommendation device 300 or the like recommends an event or the like with a high level of satisfaction (evaluation information) of other users with similar attributes (for example, residents living within a certain range). may

In the second to fourth embodiments described above, the recommendation device 300 and the like and the authentication device 200 are separate information processing devices, but they may be the same. For example, the recommendation device 300 may further associate facial feature information with the member ID 31221 of the user information 312 and register it. In that 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 shown in FIG.

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.

In addition, in the above-described embodiment, the hardware configuration has been described, but the configuration is not limited to this. The present disclosure can also implement arbitrary processing by causing a CPU to execute a computer program.

In the above example, the program can be stored and supplied to the computer using various types of non-transitory computer readable media. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible discs, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs, Includes CD-R/W, DVD (Digital Versatile Disc), semiconductor memory (eg, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). The program may also be delivered to the computer on various types of transitory computer readable medium. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. Transitory computer-readable media can deliver the program to the computer via wired channels, such as wires and optical fibers, or wireless channels.

It should be noted that the present disclosure is not limited to the above embodiments, and can be modified as appropriate without departing from the scope. In addition, the present disclosure may be implemented by appropriately combining each embodiment.

Some or all of the above embodiments may also be described in the following additional remarks, but are not limited to the following.
(Appendix A1)
an acquisition unit that acquires attribute information including information on members of a 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 unit that specifies a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation unit that recommends the identified experiential event to the user;
recommendation device.
(Appendix A2)
The desired conditions include a request for the experiential event in the family,
The recommendation device according to appendix A1, wherein the specifying unit specifies an experiential event that satisfies the request.
(Appendix A3)
The desired condition includes schedule information of the family,
The recommendation device according to appendix A1 or A2, wherein the specifying unit specifies the experiential event held on a schedule other than the schedule information.
(Appendix A4)
The attribute information includes attributes of the user's child as the member,
The recommendation device according to any one of appendices A1 to A3, wherein the specifying unit specifies the experiential event in which the child satisfies participation requirements.
(Appendix A5)
The recommendation device is
further comprising a first notification unit that notifies a first external server of the identified experiential event, the attribute information, and the desired condition;
The acquisition unit acquires attached information related to the specified experiential event from the first external server,
The recommendation device according to any one of Appendixes A1 to A4, wherein the recommendation unit presents the acquired attached information to the user.
(Appendix A6)
The first notification unit notifies the identified experiential event, the attribute information and the desired condition to the two or more first external servers,
The acquisition unit collects the attached information from each first external server,
The recommendation device according to appendix A5, wherein the recommendation unit collectively presents the collected attached information to the user.
(Appendix A7)
The acquisition unit acquires the attached service of the identified experiential event as the attached information,
The recommendation device according to appendix A5 or A6, wherein the recommendation unit further recommends the acquired accessory service to the user.
(Appendix A8)
The recommendation device according to appendix A7, wherein the ancillary service includes privilege information of a service that can be used when participating in the identified experiential event.
(Appendix A9)
The acquisition unit acquires advertising information related to the specified experiential event as the attached information,
The recommendation device according to any one of appendices A5 to A8, wherein the recommendation unit recommends the identified experience-based event and presents the advertisement information.
(Appendix A10)
The recommendation device according to any one of appendices A5 to A9, wherein the acquisition unit acquires, as the attached information, information about a rental product used in the specified experiential event.
(Appendix A11)
The recommendation device according to any one of appendices A5 to A10, wherein the acquisition unit acquires, from the first external server, payment information of a fee associated with presentation of the attached information.
(Appendix A12)
The acquisition unit acquires input information based on the experience of the member who participated in the recommended hands-on event,
The recommendation device is
The recommendation device according to any one of appendices A1 to A11, further comprising a registration unit that associates the input information, the experience-based event, and the member with each other and registers them in an experience history.
(Appendix A13)
The recommendation device according to Appendix A12, wherein the specifying unit specifies the experiential event by further considering the input information.
(Appendix A14)
Further comprising 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 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 recommendation device according to appendix A12 or A13, wherein the registration unit adds information about the new experiential event to the database.
(Appendix A15)
The attribute information includes information on the user's residential area,
The identification unit identifies a plurality of users whose residence area is within a predetermined range,
The recommendation device according to appendix A14, wherein the second notification unit notifies the second external server of the identified attribute information of the plurality of users and the experience history of each user.
(Appendix A16)
The acquisition unit further acquires biometric information of each member of the user,
The registration unit associates the biometric information with the attribute information and the desired condition and registers them as user information,
The recommendation device is
an authentication control unit that controls biometric authentication using the biometric information for a captured image of a participant captured during the recommended experience-based event;
If the biometric authentication is successful, further comprising a determination unit that determines whether registration is possible based on the analysis result of the captured image,
If the determination unit determines that the registration is possible, the registration unit registers the captured image in the experience history of the member corresponding to the biometric information for which the biometric authentication is successful. Recommended device as described.
(Appendix A17)
The determination unit analyzes, from the photographed image, the degree of satisfaction of the experiential event of the member corresponding to the biometric information for which the biometric authentication was successful, and determines that registration is possible when the degree of satisfaction is equal to or greater than a predetermined value. The recommendation device according to A16.
(Appendix A18)
the database includes infectious disease control statuses for each of the plurality of experiential events;
The recommendation device according to any one of appendices A1 to A17, wherein the specifying unit specifies the experience-based event in consideration of the infectious disease countermeasure status.
(Appendix B1)
the user's user terminal;
a recommendation device;
The recommendation device is
Acquisition unit for acquiring, from the user terminal, 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. When,
a specifying unit that specifies a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation unit that recommends the identified experiential event to the user terminal;
Recommendation system with
(Appendix B2)
The desired conditions include a request for the experiential event in the family,
The recommendation system according to appendix B1, wherein the specifying unit specifies an experiential event that satisfies the request.
(Appendix C1)
the computer
Acquire 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,
Based on the attribute information and the desired conditions, identifying a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered,
A recommendation method for recommending the identified experiential event to the user.
(Appendix D1)
Acquisition processing 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 process of specifying a hands-on event suitable for at least the member from among a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation process of recommending the identified experiential event to the user;
A recommended program that causes a computer to run

Although the present invention has been described with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various changes 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.

This application claims priority based on Japanese Patent Application No. 2021-036064 filed on March 8, 2021, and the entire disclosure thereof is incorporated herein.

1 recommendation device 11 acquisition unit 12 identification unit 13 recommendation unit 1000 recommendation system F1 family U11 user (parent)
U12 member (parent)
U13 member (child)
U14 member (child)
F2 family members U22 members (parents)
U23 member (child)
F3 Family U31 User (parent)
U33 member (child)
U34 member (child)
F4 Family member U41 User (parent)
U43 member (child)
N network 101 user terminal 102 user terminal 110 camera 120 storage unit 121 program 130 memory 140 communication unit 150 input/output unit 160 control unit 161 registration unit 162 acquisition unit 163 display control unit 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 unit 250 authentication unit 300 recommendation device 310 storage unit 311 program 312 user information 3121 user ID
3122 Family information 31220 Family structure 31221 Member ID
3122n Member ID
3123 Personal information 3124 Desired condition 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 photographed image group 320 memory 330 communication unit 340 control unit 341 acquisition unit 342 registration unit 343 authentication control unit 344 identification unit 345 recommendation unit 346 determination unit 400 experiential event venue 401 camera 1000a recommendation system 300a recommendation device 311a Program 347 Notification unit 501 External server 50k External server 61 Desired condition registration screen 611 Selection field 612 Selection field 613 Registration button 62 Experience event recommendation screen 621 Event information 622 Participation application button 63 Event experience record registration screen 631 Experience record Input field 632 Satisfaction level input field 633 Desired next time input field 634 Register button 64 Growth record registration screen 641 Lesson selection field 642 Goal input field 643 Achievement status input field 644 Register button 63a Event experience record display screen by organizer 631a Person in charge Observation record display field 632a Proficiency level display field 634a Registration screen display button 65 Re-recommendation screen for experiential event 651 Event information 652 Participation application button

Claims

Acquisition means for acquiring attribute information including information on members of a user's family, and desired conditions for at least members of the family other than the user to participate in the experience-based event;
identifying means for identifying a hands-on event suitable for at least the member from among a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired conditions;
a recommendation means for recommending the identified experiential event to the user;
recommendation device.
The desired conditions include a request for the experiential event in the family,
The recommendation device according to claim 1, wherein the identifying means identifies an experiential event that satisfies the request.
The desired condition includes schedule information of the family,
The recommendation device according to claim 1 or 2, wherein the identifying means identifies the experiential event held on a schedule other than the schedule information.
The attribute information includes attributes of the user's child as the member,
The recommendation device according to any one of claims 1 to 3, wherein the identifying means identifies the experiential event that satisfies participation requirements for the child.
The recommendation device is
further comprising a first notification means for notifying a first external server of the specified experiential event, the attribute information and the desired condition;
The acquisition means acquires attached information related to the specified experiential event from the first external server,
The recommendation device according to any one of claims 1 to 4, wherein the recommendation means presents the acquired attached information to the user.
The first notification means notifies the specified experiential event, the attribute information, and the desired condition to the two or more first external servers,
The acquisition means collects the attached information from each first external server,
6. The recommendation device according to claim 5, wherein said recommendation unit collectively presents said collected attached information to said user.
The acquisition means acquires the attached service of the specified experiential event as the attached information,
7. The recommendation device according to claim 5, wherein said recommendation means further recommends said acquired accessory service to said user.
8. The recommendation device according to claim 7, wherein the accessory service includes privilege information of a service that can be used when participating in the specified experiential event.
The acquisition means acquires advertising information related to the specified experiential event as the attached information,
9. The recommendation device according to any one of claims 5 to 8, wherein said recommendation means recommends said specified experiential event and presents said advertisement information.
10. The recommendation device according to any one of claims 5 to 9, wherein said acquisition means acquires information on rental products used in said specified experience-based event as said attached information.
11. The recommendation device according to any one of claims 5 to 10, wherein said acquisition means acquires from said first external server payment information of a commission associated with presentation of said attached information.
The acquisition means acquires input information based on the experience of the member who participated in the recommended hands-on event,
The recommendation device is
12. The recommendation device according to any one of claims 1 to 11, further comprising a registration unit that associates the input information, the experience-based event, and the member with each other and registers them in an experience history.
13. The recommendation device according to claim 12, wherein said identifying means further considers said input information to identify said experiential event.
Further comprising a second notification means for notifying a second external server of the attribute information, the desired condition and the experience history,
The acquisition 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 recommendation device according to claim 12 or 13, wherein said registration means adds information on said new experiential event to said database.
The attribute information includes information on the user's residential area,
The specifying means specifies a plurality of users whose residence area is within a predetermined range,
15. The recommendation device according to claim 14, wherein said second notification means notifies said second external server of said plurality of identified users' attribute information and experience history of each user.
The acquisition means further acquires biometric information of each member of the user,
The registration means associates the biometric information with the attribute information and the desired condition and registers them as user information;
The recommendation device is
Authentication control means for controlling biometric authentication using the biometric information for the photographed image of the participant taken during the recommended experience-based event;
If the biometric authentication is successful, further comprising determination means for determining whether registration is possible based on the analysis result of the captured image,
16. The registration means registers the photographed image in the experience history of the member corresponding to the biometric information for which the biometric authentication is successful when the determination means determines that the registration is possible. The recommended device described in .
The judging means analyzes, from the photographed image, the degree of satisfaction of the experiential event of the member corresponding to the biometric information for which the biometric authentication has succeeded, and judges that registration is possible when the degree of satisfaction is equal to or greater than a predetermined value. Item 17. The recommendation device according to Item 16.
the database includes infectious disease control statuses for each of the plurality of experiential events;
The recommendation device according to any one of claims 1 to 17, wherein the specifying means specifies the experience-based event by further considering the status of infectious disease countermeasures.
the user's user terminal;
a recommendation device;
The recommendation device is
Acquisition means for acquiring, from the user terminal, attribute information including information about members of the user's family, and desired conditions for at least participation in the hands-on event by members of the family other than the user. When,
identifying means for identifying a hands-on event suitable for at least the member from among a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired conditions;
a recommendation means for recommending the identified experiential event to the user terminal;
Recommendation system with
The desired conditions include a request for the experiential event in the family,
20. The recommendation system according to claim 19, wherein said identifying means identifies an experiential event that satisfies said request.
the computer
Acquire 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,
Based on the attribute information and the desired conditions, identifying a hands-on event suitable for at least the member from a database in which information on a plurality of hands-on events is registered,
A recommendation method for recommending the identified experiential event to the user.
Acquisition processing 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 process of specifying a hands-on event suitable for at least the member from among a database in which information on a plurality of hands-on events is registered based on the attribute information and the desired condition;
a recommendation process of recommending the identified experiential event to the user;
A non-transitory computer-readable medium storing a recommended program that causes a computer to execute