Information processing device, information processing method, and program

Abstract

It provides opportunities for active communication with others and enables effective sales promotion. [Solution] The information processing device according to the embodiment is an information processing device connected to a user terminal via a predetermined network, and includes a registration unit that registers the user's anniversary date entered into the user terminal, a proposal unit that determines a first number of days starting from the anniversary date, and on the day when a second number of days, which is a predetermined number of days less than the first number of days, has elapsed from the anniversary, proposes to the user that they create an opportunity to converse with others on the day when the first number of days has elapsed from the anniversary date, and a recommendation unit that recommends to the user the purchase of a product to be used on the new anniversary.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] In recent years, with the digitalization of various things around us, the number of people who manage their daily schedules using electronic devices such as personal computers and smartphones instead of things like notebooks has been increasing.

[0003] For example, in Patent Document 1 shown below, a topic table is stored in advance in a computer such as a personal computer, and when an operator inputs the date of occurrence of a specific event such as "birth", "marriage", "death", etc., a new event is automatically generated based on the topic table after a specific number of days have passed from the event occurrence date. A technique for this is disclosed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the above-described conventional technology, new events automatically generated based on registered events such as "visiting a shrine 30 days after" "birth" and "starting to eat 100 days after" "birth" are limited to the events registered in the topic table created in accordance with traditions and customs. Therefore, in the conventional technology, there is a problem that it is only possible to automatically generate and manage events following traditions and customs on days following traditions and customs, and it cannot play a role other than the function as a mere scheduler.

[0006] For example, with the spread of remote work and online classes, people are spending more time in the same space as family and friends, or not seeing each other face-to-face for extended periods. This increases the likelihood of becoming estranged from others or encountering problems, and the reduced opportunities for proactive communication make it difficult to build smooth relationships. However, the conventional technologies mentioned above have been unable to address these challenges.

[0007] Furthermore, advertising merchandise needed for an event, or goods to enhance the event experience, on the day the event is scheduled can be expected to have a high promotional effect, but the conventional technology described above did not possess the functionality to achieve such an effect.

[0008] Therefore, this disclosure is made in view of the above issues and aims to provide an information processing device, an information processing method, and a program that provide opportunities for active communication with others and enable effective sales promotion. [Means for solving the problem]

[0009] An information processing device according to one embodiment of the present disclosure is an information processing device connected to a user terminal via a predetermined network, comprising: a registration unit that registers a user's anniversary date entered into the user terminal; a proposal unit that determines a first number of days starting from the anniversary date, and on the day when a second number of days, which is a predetermined number of days less than the first number of days, has elapsed from the anniversary, proposes to the user that they create an opportunity to converse with others on the day when the first number of days has elapsed from the anniversary date, and a recommendation unit that recommends to the user the purchase of a product to be used on the new anniversary.

[0010] An information processing method according to one embodiment of the present disclosure is an information processing method performed in an information processing device connected to a user terminal via a predetermined network, and includes registering a user's anniversary date entered in the user terminal, determining a first number of days starting from the anniversary date, proposing to the user that the day on which the first number of days has elapsed from the anniversary date be designated as a new anniversary date and that a place for conversation be set up with others, on a second number of days that is a predetermined number less than the first number of days, and recommending to the user that they purchase a product to be used on the new anniversary date.

[0011] A program according to one embodiment of the present disclosure is a program for causing a processor implemented in an information processing device connected to a user terminal via a predetermined network to function, and causes the processor to execute the following processes: registering a user's anniversary entered into the user terminal; determining a first number of days starting from the anniversary; proposing to the user that on a second number of days less than the first number of days has elapsed since the anniversary, the day on which the first number of days has elapsed from the anniversary be designated as a new anniversary and that an opportunity be set up for conversation with others; and recommending to the user the purchase of a product to be used on the new anniversary. [Brief explanation of the drawing]

[0012] [Figure 1] This is a schematic diagram showing an example of the general configuration of an information processing system according to one embodiment of the present disclosure. [Figure 2] This is a block diagram showing an example of the functional configuration of a service server according to one embodiment of the present disclosure. [Figure 3] This figure shows an example of a commemorative day type classification table according to one embodiment of the present disclosure. [Figure 4] This figure shows an example of a sentiment category classification table according to one embodiment of this disclosure. [Figure 5] This is a flowchart illustrating a series of service steps according to one embodiment of this disclosure. [Figure 6] This flowchart shows an example of operation according to one embodiment of the present disclosure. [Figure 7]It is a diagram showing an example of a memorial day registration screen according to an embodiment of the present disclosure. [Figure 8] It is a diagram showing an example of another memorial day registration screen according to an embodiment of the present disclosure. [Figure 9] It is a diagram showing an example of a memorial day selection screen in FIG. 8. [Figure 10] It is a diagram showing an example of a rhyming table according to an embodiment of the present disclosure. [Figure 11] It is a diagram showing an example of a daily sharing screen according to an embodiment of the present disclosure (Part 1). [Figure 12] It is a diagram showing an example of a daily sharing screen according to an embodiment of the present disclosure (Part 2). [Figure 13] It is a diagram showing an example of a small celebration day proposal screen according to an embodiment of the present disclosure. [Figure 14] It is a diagram showing an example of a drink gift recommendation screen according to an embodiment of the present disclosure. [Figure 15] It is a diagram showing an example of a message input screen according to an embodiment of the present disclosure. [Figure 16] It is a diagram showing an example of a feedback screen according to an embodiment of the present disclosure (Part 1). [Figure 17] It is a diagram showing an example of a feedback screen according to an embodiment of the present disclosure (Part 2). [Figure 18] It is a hardware configuration diagram showing an example of an information processing apparatus that realizes functions such as a service server according to an embodiment of the present disclosure.

Embodiments for Carrying Out the Invention

[0013] Hereinafter, some embodiments of the present disclosure will be described in detail based on the drawings. In the following embodiments, the same parts are denoted by the same reference numerals, and redundant descriptions are omitted.

[0014] In the following embodiments, we illustrate a case where a beverage manufacturer acts as a service vendor, providing a space for conversation (hereinafter also referred to as "a time for conversation") by proposing a new commemorative day (hereinafter also referred to as "a small special day") to the user. However, this disclosure is not limited to this, and various companies, organizations, and institutions can act as service vendors and provide the services exemplified in the following embodiments.

[0015] (Example system configuration) Figure 1 is a schematic diagram showing an example of the general configuration of an information processing system according to one embodiment of the present disclosure. As shown in Figure 1, the information processing system 1 comprises a service server 100, a sales server 200, a database 300, and one or more user terminals 400-1 to 400-N (where N is a positive integer; hereafter, if individual user terminals are not distinguished, their sign will be 400), all of which are connected to each other via a network 500 so that they can communicate with one another. The network 500 may be various networks such as the Internet, a mobile communication system, or a LAN (Local Area Network).

[0016] The service server 100 implements various functions to propose "small special occasions" to users and provide "times for conversation." For example, the service server 100 determines a new "small special occasion" from anniversaries registered by the user, proposes this "small special occasion" to the user, and recommends that the user send a drink as a gift to the person with whom they will share the "time for conversation" to make the "time for conversation" on the "small special occasion" even better. In addition, the service server 100 collects (shares daily) the user's hopes, wishes, frustrations, efforts, and concerns in their daily life (hereinafter also referred to as "daily feelings"), and provides the user with topics for "time for conversation" as, for example, the title of a "small special occasion." Furthermore, the service server 100 may receive feedback from users about their experiences during "small celebrations" and analyze this feedback to determine the title of future "small celebrations" and the recommended "drink gifts." It should be noted that the service server 100 does not necessarily have to consist of a single information processing unit; for example, it could be a cloud server.

[0017] Here, the term "user" in this description may refer to a user of a service provided by the information processing system 1 according to this embodiment through an SNS (Social Networking service) application or the like. Examples of SNS applications include messenger applications such as LINE®, X (formerly Twitter)®, Facebook®, and Instagram®. However, the system is not limited to these; various methods may be used to provide the service according to this embodiment to the user, such as using an application provided by a beverage manufacturer (hereinafter also referred to as a service application), or using a webpage or email. For simplicity, the following description will illustrate the case where a service is provided to the user through an SNS application. Note that a service application may be included within an SNS application.

[0018] The sales server 200 may be, for example, a server that provides a drink gift sales site on the network 500. For example, the sales server 200 may provide a drink gift purchase page to the user terminal 400. A user guided from the service server 100 may purchase a drink gift recommended in the service according to this embodiment from the drink gift purchase page displayed on the user terminal 400. The sales server 200 does not need to be composed of a single information processing device, and may be, for example, a cloud server. Furthermore, the sales server 200 may be a sales site unique to a beverage manufacturer, or an existing e-commerce (electronic commerce) site.

[0019] Database 300 stores, for example, "daily feelings" collected through daily sharing with users, for each user. Database 300 may also store, for example, candidate titles for "small special occasions" or candidate numbers of days from a certain anniversary registered by the user to a "small special occasion." Furthermore, Database 300 may store feedback on "conversation time" and its analysis results that are fed back to the service server 100. Note that Database 300 does not need to be composed of a single information processing device, but may be composed of multiple databases, such as a cloud database. Also, it is not necessary for Database 300 to be connected to Network 500, but it is sufficient that it is connected to the service server 100 in a way that allows communication. In that case, Database 300 may be a storage device built into or externally attached to the service server 100.

[0020] The user terminal 400 may be an information processing terminal equipped with communication functions, such as a personal computer or a smartphone. By operating the user terminal 400, users can register anniversaries, purchase drink gifts, and provide feedback on their "time for conversation." Users can also enjoy services such as suggestions for "small special occasions" and recommendations for drink gifts through the user terminal 400. Note that the number of user terminals 400 is not limited to one per user; one user may use multiple user terminals 400.

[0021] (Example of server function configuration) Figure 2 is a block diagram showing an example of the functional configuration of a service server according to this embodiment. As shown in Figure 2, the service server 100 includes, as its functional configuration, a user registration unit 101, a commemorative day registration unit 102, a daily sharing unit 103, an elapsed days measurement unit 104, an analysis unit 105, a small special occasion suggestion unit 106, a drink gift recommendation unit 107, and a feedback collection unit 108.

[0022] The user registration unit 101, for example, accepts user registrations from users to the service according to this embodiment, and registers and manages them as service recipients.

[0023] The anniversary registration unit 102 registers and manages anniversaries entered by the user via, for example, the user terminal 400.

[0024] Furthermore, the anniversary registration unit 102 may identify the type of the registered anniversary. To identify the type of anniversary, an anniversary type classification table, such as the one exemplified in Figure 3, may be used.

[0025] The daily sharing unit 103 collects "daily feelings" from the user, for example, via the user terminal 400. Various methods may be used to collect "daily feelings" from the user, such as using an SNS application (including a service application), or using a web page or email.

[0026] For example, when using an SNS application, the service server 100 may send questions or surveys to the SNS application on the user terminal 400 from time to time or periodically (for example, daily) to collect "daily feelings," and collect the user's responses as "daily feelings." Alternatively, the service server 100 may link with other applications such as a diary application, calendar application, or scheduler, and collect "daily feelings" from the information the user enters into those applications.

[0027] The elapsed days measurement unit 104 measures, for example, the number of days elapsed since an anniversary registered by the anniversary registration unit 102. The small special day suggestion unit 106 may suggest a "small special day" to the user based on the number of days elapsed measured by the elapsed days measurement unit 104.

[0028] The analysis unit 105, for example, analyzes the "daily feelings" of each user collected by the daily sharing unit 103 and stored in the database 300 to identify "how the user has been feeling" or "what they have been thinking" recently or on a daily basis. The analysis unit 105 may also analyze the "conversation time" impressions of each user collected by the feedback collection unit 108 (described later) and stored in the database 300 to identify "what the user did" during the "conversation time," "how they felt," and "what kind of changes in their state of mind occurred" as a result of the "conversation time."

[0029] Furthermore, analysis results such as "what kind of feelings" or "what kind of thoughts" a user identified from "daily feelings" has recently or on a daily basis may be stored in database 300 as part of the user's "daily feelings." Similarly, analysis results such as "what the user did" or "how they felt" during "time for conversation" and "what kind of changes in their state of mind occurred" as a result of "time for conversation" may be stored in database 300 as part of the feedback on "time for conversation."

[0030] The Small Celebration Day Proposal Section 106 sets a "small celebration day" (hereinafter also referred to as the "scheduled small celebration day") a certain number of days after an anniversary managed by the Anniversary Registration Section 101. The "certain number of days" may be a number determined based on wordplay, such as 39 days (thank you), 104 days (I love you), or 112 days (that's great). However, it is not limited to this, and may be any number of days, such as round numbers like 100, 500, or 1000 days, or numbers that follow the calendar, such as 6 months or 3 years, or numbers obtained by generating pseudo-random numbers, without being restricted to numbers that follow tradition or custom. For simplicity, the following explanation will use the example where the "certain number of days" is a number determined based on wordplay.

[0031] Furthermore, the Small Special Occasion Proposal Unit 106 proposes to the user that the scheduled Small Special Occasion date be designated as the "Small Special Occasion" on a predetermined number of days before the scheduled Small Special Occasion date (for example, two weeks or 30 days before) (hereinafter also referred to as the "proposal date").

[0032] In this case, the Small Special Occasion Proposal Unit 106 may decide on the title of the "Small Special Occasion" to propose to the user based on the "Everyday Feelings" and "Times of Conversation" stored in the database 300. For example, if the Small Special Occasion Proposal Unit 106 finds from the "Everyday Feelings" that the user has recently felt grateful to their partner or wants to be appreciated by their partner, it may decide on the title of the "Small Special Occasion" to be "A Day to Express Gratitude to Your Partner."

[0033] Specifically, the Small Special Occasion Proposal Unit 106 may decide which category of "Small Special Occasion" to propose to the user when determining the title of the "Small Special Occasion." For this decision, a mood category classification table, such as the one illustrated in Figure 4, may be used. Next, the Small Special Occasion Proposal Unit 106 may estimate the user's "daily feelings" based on their impressions of "daily feelings" and "moments of conversation," and then determine the category of the "Small Special Occasion" to propose by comparing the estimated "daily feelings" with the mood category classification table. Then, the Small Special Occasion Proposal Unit 106 may determine the title of the "Small Special Occasion" to propose to the user according to the determined category.

[0034] Furthermore, when determining the title of "Small Special Day," the Small Special Day Proposal Unit 106 may decide which type of anniversary to use as the starting date. For example, the user's "everyday feelings" may be used in this decision. For example, if it is found that the user has recently felt grateful to their partner or wants to be appreciated by their partner, the Small Special Day Proposal Unit 106 may decide to use an anniversary classified as "2" "Anniversary for Two" (for example, a wedding anniversary or a dating anniversary) in the anniversary type classification table in Figure 3 as the starting date.

[0035] The drink gift recommendation unit 107 recommends to the user the purchase of a drink gift to enhance the "time for conversation" held on the "small special day," for example, when the small special day suggestion unit 106 suggests a "small special day" to the user. The drink gift recommendation unit 107 may also determine the type of drink gift to recommend to the user according to the title of the "small special day" decided by the small special day suggestion unit 106. For example, if the title of the "small special day" is decided to be "A day to express gratitude to your partner," the drink gift recommendation unit 107 may recommend coffee, cocoa, or tea, which are expected to have a relaxing effect. Alternatively, if the title of the "small special day" is decided to be "A day to play sports together," the drink gift recommendation unit 107 may recommend sports drinks or citrus-flavored soft drinks with a sour taste, which are suitable for hydration during exercise.

[0036] Furthermore, the drink gift recommendation unit 107 may include a link to the drink gift purchase page in its recommendations for drink gifts to the user. For example, the image or text of the recommended drink gift may have a link attached, and by selecting one of these, the user terminal 400 may be guided to the drink gift purchase page provided by the sales server 200.

[0037] The feedback collection unit 108 may, for example, collect feedback from users on the evening of the "small special day" proposed by the small special day proposal unit 106 (for example, after 8 p.m.) or the following day, regarding their impressions of the "time for conversation," and store this feedback in the database 200 for each user.

[0038] (Example service flow) Next, we will describe the sequence of services according to this embodiment. Figure 5 is a flowchart illustrating the sequence of services according to this embodiment.

[0039] As shown in Figure 5, in the service according to this embodiment, first, the user registers using the SNS application on the user terminal 400 (step S10). Next, the user registers one or more anniversaries, such as birthdays or wedding anniversaries, using the SNS application on the user terminal 400 (step S20). After that, daily sharing begins, collecting "daily feelings" from the user using the SNS application on the user terminal 400 (step S30).

[0040] Next, the user is presented with a "small special day" set as the starting date, via the user terminal 400 (step S40). The user is also recommended a drink gift to enhance the "time of conversation" that takes place on the "small special day" (step S50). At this time, a link to the drink gift sales site may be displayed on the user terminal 400 to guide the user.

[0041] Subsequently, the user holds a "Time for Conversation" on the suggested "Small Special Day" (Step S60). Then, the user provides feedback on the "Time for Conversation" using the SNS app on user terminal 400 (Step S70).

[0042] By enjoying this series of services, users can gain opportunities for active communication with others, such as partners and family members. In addition, beverage manufacturers can recommend the purchase of drink gifts to coincide with "small celebratory occasions," enabling effective sales promotion.

[0043] (Example of operation) Next, an example of operation when providing the service according to this embodiment will be described in detail with reference to the drawings.

[0044] Figure 6 is a flowchart showing an example of operation according to this embodiment. Figure 7 is a diagram showing an example of the anniversary registration screen according to this embodiment. Figure 8 is a diagram showing another example of the anniversary registration screen according to this embodiment, and Figure 9 is a diagram showing an example of the anniversary selection screen in Figure 8. Figure 10 is a diagram showing an example of the wordplay table according to this embodiment. Figures 11 and 12 are diagrams showing examples of the daily sharing screen according to this embodiment. Figure 14 is a diagram showing an example of the drink gift recommendation screen according to this embodiment, and Figure 15 is a diagram showing an example of the message input screen according to this embodiment. Figures 16 and 17 are diagrams showing examples of the feedback screen according to this embodiment.

[0045] As shown in Figure 6, first, the user registration unit 101 of the service server 100 performs user registration requested by the user from the SNS application on the user terminal 400 (step S100). This step S100 may correspond to, for example, the "user registration" operation in step S10 in Figure 5. In addition, user registration may use, for example, a function such as friend registration in the SNS application.

[0046] Once user registration is performed, the anniversary registration unit 102 displays an anniversary registration screen, as shown in Figure 7 or Figure 8, on the SNS application of the user terminal 400. When the user enters the date of an anniversary for themselves, their partner, children, pets, friends, etc., on this anniversary registration screen, the anniversary registration unit 102 registers and manages the entered anniversaries for each user (step S200). This step S200 may correspond, for example, to the "anniversary registration" operation in step S20 of Figure 5.

[0047] Figure 7 shows a screen for registering the birthdays of the user, their partner, children, pets, or friends as anniversaries. On the other hand, Figure 8 shows a screen for registering any arbitrary anniversary. In the anniversary registration screen shown in Figure 8, an input field may be provided for selecting or entering the anniversary to be registered. This input field may be configured to allow the user to select the type of anniversary in a pull-down menu format, as illustrated in Figure 9.

[0048] Thus, when one or more anniversaries are registered, the elapsed days measurement unit 104 starts measuring the number of days elapsed since each anniversary (step S301). Also, the daily sharing unit 103 starts daily sharing to collect "daily feelings" from the user (step S302). The collected "daily feelings" may be stored in the database 300 for each user.

[0049] Furthermore, a wordplay table, such as the one shown in Figure 10, may be used to determine the number of days until the "small special day" ("a certain number of days"). The wordplay table may contain multiple numbers of days determined based on wordplay. The anniversary registration unit 102 may, for example, generate a pseudo-random number and use the number of days corresponding to the generated pseudo-random number as the number of days until the scheduled small special day for the registered anniversary. Alternatively, appropriate wordplay numbers may be pre-associated with the type and attributes of the anniversary, such as 104 days ("I love you") for wedding anniversaries or dating anniversaries, or 250 days ("Thank you for your hard work") for the day one started working or the start date of parental leave. However, the number of days until the "small special day" may be determined by various methods, and the system is not limited to these methods.

[0050] Furthermore, steps S301 to S302 may correspond, for example, to the "daily sharing" action in step S30 of Figure 5. Also, the measurement of elapsed days and daily sharing may be performed continuously until this operation is completed.

[0051] Here, as illustrated in Figure 11, the collection of the user's "daily feelings" may be done, for example, by the daily sharing unit 103 asking questions or conducting surveys to the user through the SNS application on the user terminal 400. Also, as illustrated in Figure 12, in daily sharing, the "daily feelings" of people other than the target user (who may also be users of this service) may be collected by asking questions or conducting surveys to the user's partner, children, friends, etc., through the SNS application.

[0052] Furthermore, questions and surveys posed through SNS apps may be generated each time by artificial intelligence such as generative AI, entered each time by staff at the service vendor, or pre-prepared for each user or for common users.

[0053] Next, the Small Special Occasion Suggestion Unit 106 determines whether the suggested date has become a few days earlier than the scheduled Small Special Occasion date, based on the number of days elapsed since each anniversary, as measured by the Elapsed Day Measurement Unit 104 (Step S401). This Step S401 is repeated until the suggested date arrives (Step S401 NO). On the other hand, if the suggested date arrives (Step S401 YES), the Small Special Occasion Suggestion Unit 106 instructs the Analysis Unit 105 to perform an analysis of the "everyday feelings" stored in the database 300 (Step S402).

[0054] Next, the Small Special Occasion Proposal Unit 106 determines the title of the "Small Special Occasion" to propose to the user based on the analysis results obtained by analyzing "everyday feelings" (step S403). At this time, the title of the "Small Special Occasion" and the anniversary to be used as the starting date may be determined using the anniversary type classification table exemplified in Figure 3 or the feeling category classification table exemplified in Figure 4.

[0055] Here, the Small Celebration Ideas Proposal Team 106 may propose a "Small Celebration Idea" to the user in a different category than the one proposed last time. By proposing a different category of "Small Celebration Idea" each time, it is possible to avoid monotonous proposals and thus improve user satisfaction.

[0056] Furthermore, the Small Celebration Day Suggestion Department 106 may prioritize suggesting categories of "Small Celebration Days" that have a higher satisfaction rate to users, based on feedback received from users regarding "Time for Conversation." Categories that have a high satisfaction rate for one user may also be used for other users.

[0057] Then, as illustrated in Figure 13, the Small Special Day Proposal Unit 106 proposes to the user via the SNS application on the user terminal 400 that the date for the Small Special Day be designated as a "Small Special Day" (step S404). This proposal may include the date of the "Small Special Day" (for example, December 4th) and the title of the "Small Special Day" (for example, "The day to talk about plans for our 3000th day anniversary"), as well as a description of the proposed "Small Special Day" and content collected through daily sharing. Steps S401 to S404 may correspond, for example, to the "Small Special Day Proposal" in step S40 in Figure 5.

[0058] In addition, in conjunction with the "Small Celebration Day" proposal by the Small Celebration Day Proposal Department 106, the Drink Gift Recommendation Department 107 recommends to the user via the SNS app on the user terminal 400 that they purchase a drink gift to enhance the "Time for Conversation" held on the "Small Celebration Day" (Step S501).

[0059] As shown in Figure 14, the drink gift recommendation screen displayed in the SNS app on the user terminal 400 may show one or more drink gift options to give to the person with whom the "time to chat" is shared. In addition, the drink gift recommendation screen may also display the preferred drinks of the person with whom the "time to chat" is shared, for the user's reference.

[0060] Next, as shown in Figure 15, the SNS app on the user terminal 400 may display a message input screen for entering a message to send along with the drink gift to the person with whom the "time to chat" is shared. The message entered on the message input screen may be a message that the user wants to send to the person with whom the "time to chat" is shared. The message entered by the user on the message input screen may be sent later as a message card along with the drink gift.

[0061] Furthermore, the message input screen may list several recommended message examples to send to the recipient. The listed message recommendations may be selected from a pre-prepared list of message candidates that match the sentiment category (see Figure 4) set for "A Small Special Day." In other words, the pre-created message candidates are assigned a sentiment category as attribute information, and the listed message recommendations may be selected based on this sentiment category.

[0062] In response, when a user selects one of the recommended drink gifts from the suggested options on the drink gift recommendation screen and clicks the "Next" button, the user terminal 400 is directed to the sales site of the sales server 200. When the user completes the purchase procedure for the drink gift on the sales site (YES in step S502), this purchase procedure is processed by the beverage manufacturer and the drink gift is shipped (step S503), and this operation proceeds to step S600. The recipient of the drink gift may be the user or the person with whom to share the "time to talk." In other words, the recipient of the drink gift may be arbitrarily set by the user. On the other hand, if a drink gift is not purchased (NO in step S502), this operation proceeds directly to step S600. Steps S501 to S504 may correspond, for example, to the "preparation for conversation" in step S50 in Figure 5.

[0063] In step S600, the user hosts a "time for conversation" on a "small special day." Step S600 may, for example, correspond to the "time for conversation" in step S60 in Figure 5.

[0064] At a predetermined time during the "Small Special Day," the feedback collection unit 108 collects feedback on the "Time for Conversation" through the SNS application on the user terminal 400 (step S701), and stores the collected feedback on the "Time for Conversation" in the database 300 for each user (step S702). Steps S701 to S702 may correspond, for example, to the "feedback" in step S70 in Figure 5.

[0065] Here, as illustrated in Figure 16, feedback on "Katarai no Toki" may be collected, for example, by the feedback collection unit 108 asking questions or conducting surveys to the user through the SNS application on the user terminal 400. Also, as illustrated in Figure 17, in the collection of feedback on "Katarai no Toki," feedback on "Katarai no Toki" may be collected not only from the user but also from people with whom "Katarai no Toki" was shared, by asking questions or conducting surveys through the SNS application to people other than the target user (who may also be users of this service).

[0066] Furthermore, for example, the analysis unit 105 can analyze the feedback collected from the "Time for Conversation" to classify the user's feelings and changes in feelings as a result of holding the "Time for Conversation" according to the feeling category classification table exemplified in Figure 4. By performing such classification, it becomes possible to grasp the user's satisfaction level, which can then be used to improve the content of future "Small Special Days" proposed.

[0067] Furthermore, collecting and analyzing feedback on "Time for Conversation" not only enables the provision of an album function to users, but also allows for the quantification of communication volume (number of conversations) and what was discussed during "Time for Conversation," which can be used to improve the interpersonal relationships surrounding users.

[0068] This operation is expected to continue until the service ends. Therefore, this operation may be repeated by returning to step S302 after completing step S702.

[0069] (Effects / Actions) As explained above, according to this embodiment, a new commemorative day, "Small Celebration Day," which is not bound by tradition or custom, is automatically generated and proposed to the user, using the anniversary date registered by the user as the starting date. This allows the user to have opportunities for active communication with others, such as partners and family members. In addition, beverage manufacturers can recommend to users the purchase of drink gifts to enhance "times of conversation" in conjunction with "Small Celebration Day," enabling effective sales promotion.

[0070] (Hardware configuration) The service server 100, sales server 200, user terminal 400, etc., according to the embodiments and their modified versions described above can be realized by an information processing device 1000 with a configuration such as that shown in Figure 18. Figure 18 is a hardware configuration diagram showing an example of an information processing device 1000 that realizes the functions of the service server 100, sales server 200, user terminal 400, etc. The information processing device 1000 has a CPU 1100, ROM (Read Only Memory) 1200, RAM (Random Access Memory) 1300, a recording device 1400, an input / output interface (I / F) 1500, and a communication unit 1600. Each part of the information processing device 1000 is connected by a bus 1700.

[0071] The CPU 1100 operates based on programs stored in the ROM 1200 or the recording device 1400, and controls each part. For example, the CPU 1100 loads the programs stored in the ROM 1200 or the recording device 1400 into the RAM 1300 and executes processing corresponding to various programs.

[0072] ROM1200 stores boot programs such as the BIOS (Basic Input Output System) that are executed by the CPU1100 when the information processing unit 1000 starts up, as well as programs that depend on the hardware of the information processing unit 1000.

[0073] The recording device 1400 is a computer-readable recording medium that non-temporarily records programs executed by the CPU 1100 and data used by such programs. Specifically, the recording device 1400 is a recording medium that records a program for executing each operation related to this disclosure, which is an example of program data.

[0074] The communication unit 1600 is an interface for the information processing device 1000 to connect to an external network 1650 (e.g., the Internet). For example, the CPU 1100 can receive data from other devices or transmit data it has generated to other devices via the communication unit 1600.

[0075] The input / output interface 1500 is an interface for connecting the input / output device 1650 and the information processing device 1000. For example, the CPU 1100 receives data from input devices such as keyboards and mice via the input / output interface 1500. The CPU 1100 also transmits data to output devices such as displays, speakers, and printers via the input / output interface 1500. The input / output interface 1500 may also function as a media interface for reading programs and the like recorded on a predetermined recording medium.

[0076] For example, when the information processing device 1000 functions as a service server 100, sales server 200, user terminal 400, etc., according to the above-described embodiment, the CPU 1100 of the information processing device 1000 realizes the functions of the service server 100, sales server 200, user terminal 400, etc., by executing a program loaded on the RAM 1300. The recording device 1400 stores the program and the like according to this disclosure. The CPU 1100 reads and executes the program data from the recording device 1400, but as another example, these programs may be obtained from other devices via an external network 1650.

[0077] While embodiments and modifications thereof have been described above, the technical scope of this disclosure is not limited to the embodiments or modifications thereof as described above, and various modifications are possible without departing from the gist of this disclosure. Furthermore, components from different embodiments and modifications may be combined as appropriate.

[0078] In the embodiments and variations thereof described above, drinks (gifts) were used as examples of products to be used for the new commemorative day. However, the products are not limited to drinks (gifts), and may include products other than drinks (for example, food products, books, miscellaneous goods, clothing, etc.), or combinations of these products. [Explanation of Symbols]

[0079] 1. Information Processing System 100 service servers 101 User Registration Section 102 Anniversary Registration Department 103 Daily common area 104 Elapsed Days Measurement Unit 105 Analysis Department 106 Small Special Occasion Proposal Department 107 Drink Gift Recommendation Section 108 Feedback Collection Department 200 sales servers 300 databases 400, 400-1~400-N User Terminals 500 Networks

Claims

1. An information processing device connected to a user terminal via a predetermined network, A registration unit that registers the user's anniversary date entered on the user terminal, A proposal unit that determines the first number of days starting from the aforementioned anniversary, and proposes to the user that on the day when a second number of days, which is a predetermined number of days less than the first number of days, has elapsed since the aforementioned anniversary, the day when the first number of days has elapsed since the aforementioned anniversary be designated as a new anniversary and a place for conversation with others is established. A recommendation section that recommends to the user the purchase of a product to be used for the new commemorative day. An information processing device equipped with the following features.

2. A sharing unit that collects the user's daily feelings via the user terminal, An analysis unit that analyzes the collected daily feelings and Furthermore, The proposal unit determines the title of the new anniversary based on the results analyzed by the analysis unit, and proposes to the user that the day on which the first number of days has elapsed since the anniversary be designated as the day of the title. The information processing apparatus according to claim 1.

3. The information processing device according to claim 2, wherein the sharing unit collects the user's daily feelings through an SNS (Social Networking service) application implemented on the user terminal.

4. The information processing device according to claim 3, wherein the sharing unit provides the user with questions or questionnaires to collect the user's daily feelings through the SNS application, and collects the user's answers to the questions or questionnaires as the user's daily feelings.

5. The system further includes a collection unit that collects comments on the new anniversary from the user via the user terminal, The aforementioned proposal department will take into consideration the collected feedback and determine the title of the next new commemorative day. The information processing apparatus according to claim 2.

6. The recommendation unit guides the user to the sales site by displaying a link to the sales site that sells the product on the user's terminal. The information processing apparatus according to claim 1.

7. The system further includes a collection unit that collects comments on the new anniversary from the user via the user terminal, The recommendation unit, taking into consideration the collected feedback, determines which products to recommend for the next new anniversary. The information processing apparatus according to claim 6.

8. The proposed part is an information processing device according to claim 1, wherein the number of days determined based on a mnemonic is the first number of days.

9. The information processing apparatus according to claim 1, wherein the product includes at least a drink.

10. An information processing method performed on an information processing device connected to a user terminal via a predetermined network, The user's anniversary date entered on the user terminal is registered. The first day is determined with the aforementioned anniversary as the starting date. On the day when a second number of days, which is a predetermined number of days less than the first number of days, has elapsed since the aforementioned anniversary, the user is proposed to create a space for conversation with others, designating the day when the first number of days has elapsed since the aforementioned anniversary as a new anniversary. The user is recommended to purchase the product to be used for the aforementioned new anniversary. Information processing methods that include the following.

11. A program for causing a processor implemented in an information processing device connected to a user terminal via a predetermined network to function, The process of registering the user's anniversary date entered on the user terminal, A process to determine the number of days in the first day, with the aforementioned anniversary as the starting date, A process to propose to the user that on the day when a second number of days, which is a predetermined number of days less than the first number of days, has elapsed since the aforementioned anniversary, the first number of days that has elapsed since the aforementioned anniversary be designated as a new anniversary, and a place for conversation with others to take place; A process to recommend to the user the purchase of a product to be used for the new anniversary. A program to cause the aforementioned processor to execute.

Images