JP2024029349A - Application programs and information processing devices - Google Patents

Abstract

The present invention provides an application program and an information processing device that can manage dates for meeting with acquaintances.
An application program causes an information processing device 3 to include a profile information recording processing unit 9 that records frequency information related to the frequency of the schedule in which the user meets with friends, which is input by the user, as profile information for each friend; A calendar recording processing unit 11 that records schedule information input by the user, including the date on which the user most recently met with a friend, in the user's calendar for each friend; It functions as a meeting schedule proposal processing unit 13 that proposes a meeting schedule for each friend.
[Selection diagram] Figure 2

Description

The present invention relates to an application program and an information processing device that can manage dates for meeting with acquaintances.

Patent Document 1 describes schedule management software. This schedule management software allows users to enter the date on which they should send gifts such as birthdays, wedding anniversaries, baby gifts, mid-year gifts, year-end gifts, etc. to their immediate family, relatives, friends, and acquaintances. A few days before the date of the gift, we will send an e-mail to the user informing them of the date on which the gift should be sent.

Japanese Patent Application Publication No. 2001-216419

With the above-mentioned conventional technology, although it is possible to notify the user of an acquaintance's anniversary, it is not possible to manage the schedule for meeting the acquaintance.

An object of the present invention is to provide an application program and an information processing device that can manage dates for meeting with acquaintances.

In order to achieve the above object, the application program of the present invention causes an information processing device to record frequency information input by the user, which is related to the frequency of the user's meeting schedule with an acquaintance, as profile information for each acquaintance. a profile information recording processing unit, a calendar recording processing unit that records schedule information input by the user, including the date when the user most recently met the acquaintance, in the user's calendar for each acquaintance; It functions as a meeting schedule proposal processing unit that proposes a meeting schedule for each of the acquaintances based on the schedule information.

Further, in order to achieve the above object, an information processing device of the present invention is an information processing device having a processor, and the processor has a frequency related to the frequency of the schedule of the user to meet with an acquaintance, which is inputted by the user. recording information as profile information for each acquaintance; and recording schedule information input by the user, including the date when the user most recently met the acquaintance, in the user's calendar for each acquaintance. and proposing a meeting schedule for each of the acquaintances based on the frequency information and the schedule information.

In the present invention, the user can send information related to the frequency of meeting with acquaintances (including family, relatives, friends, acquaintances, etc.), such as once a year, every six months, once a season. You can enter profile information for each acquaintance, such as whether you want to meet someone or meet them every month. The user can also record the date of the most recent meeting with an acquaintance in the user's calendar for each acquaintance. The application then proposes a meeting schedule for each acquaintance based on the recorded frequency information and the date of the most recent meeting with the acquaintance. This allows the user to know the optimal meeting schedule for each acquaintance according to his or her wishes, so even if the user is busy, he or she can easily make plans in advance with the acquaintance he or she wants to meet. Moreover, even if the number of acquaintances increases, it becomes possible to meet all of them. In this way, the user can manage dates for meeting acquaintances.

According to the present invention, it is possible to manage the schedule for meeting with acquaintances.

1 is a diagram illustrating an example of the overall configuration of an information management system according to an embodiment. FIG. 2 is a block diagram illustrating an example of a functional configuration of an information processing device. FIG. 3 is a diagram illustrating an example of a friend's profile screen displayed on the touch panel of the information processing device. FIG. 3 is a diagram illustrating an example of a friend's profile screen displayed on the touch panel of the information processing device. FIG. 2 is a diagram illustrating an example of a calendar screen displayed on a touch panel of an information processing device. FIG. 2 is a diagram illustrating an example of a friend list displayed on a touch panel of an information processing device. FIG. 3 is a diagram illustrating an example of a recommended schedule screen that displays a list of meeting schedules proposed by a meeting schedule proposal processing unit. It is a figure showing an example of a recommended schedule screen in the case where the one with the longest elapsed number of days from the last matching date is displayed preferentially. FIG. 3 is a diagram illustrating an example of a recommended place screen that displays areas and places proposed by a meeting place proposal processing unit. FIG. 7 is a diagram illustrating an example of an anniversary reminder screen that displays a list of anniversaries reminded by the anniversary reminder processing unit. It is a figure showing an example of the recommended present screen which displays the present proposed by the present proposal processing part. FIG. 3 is an explanatory diagram illustrating an example of a first stage of a present proposal method executed by a present proposal processing unit. FIG. 7 is an explanatory diagram illustrating an example of a second stage of the present proposal method executed by the present proposal processing unit. FIG. 12 is an explanatory diagram illustrating an example of the third stage of the present proposal method executed by the present proposal processing unit. It is an explanatory diagram showing an example of the present proposal method by a present proposal processing part. 2 is a flowchart illustrating an example of a processing procedure executed by a CPU of an information processing device. FIG. 2 is a block diagram illustrating an example of the hardware configuration of an information processing device.

An embodiment of the present invention will be described below with reference to the drawings.

<1. Overall configuration of information system>
An example of the overall configuration of an information management system 1 according to this embodiment will be described using FIG. 1. As shown in FIG. 1, the information management system 1 includes an information processing device 3 operated by a user and a plurality of server devices 5. The information processing device 3 and the server device 5 are communicably connected via a network NW such as the Internet, for example. The plurality of server devices 5 include, for example, servers that provide product information on various products, servers that provide sales services for various products, servers that provide reservation services for shops such as cafes and restaurants, and servers that provide payment services. etc. are included. The plurality of server devices 5 may be composed of a single computer.

The information processing device 3 is a portable terminal device such as a smartphone or a tablet computer. However, the computer is not limited to these, and may be, for example, a desktop computer or a notebook computer. The information processing device 3 has a touch panel 7 on which various displays and various input operations are performed by the player. The player performs a desired operation input by touching the touch panel 7 with a finger, pen, or the like.

The detection method of the touch panel 7 is not particularly limited, but various detection methods such as a resistive film method, a capacitance method, an optical method, and an electromagnetic induction method can be employed. Note that the information processing device 3 may include an input section such as a button, a switch, a keyboard, etc., or a display section such as a liquid crystal panel, instead of or in addition to the touch panel 7. Further, an audio output unit such as a speaker may be provided.

The server device 5 is a so-called server computer. The server device 5 receives a request from the information processing device 3 via the network NW, and provides the information processing device 3 with, for example, product information on various products, sales services, reservation services for cafes and restaurants, payment services, etc. provide.

<2. Functional configuration of information processing device>
Next, an example of the functional configuration of the information processing device 3 will be described using FIGS. 2 to 15. Each processing unit of the information processing device 3 is implemented by the information processing device 3 executing the application program of the present invention.

As shown in FIG. 2, the information processing device 3 includes the above-mentioned touch panel 7, a profile information recording processing section 9, a calendar recording processing section 11, a meeting schedule proposal processing section 13, a meeting place proposal processing section 15, It has an anniversary reminder processing section 17, a present proposal processing section 19, a purchase execution processing section 21, and a product information acquisition processing section 23.

The profile information recording processing unit 9 records the profile information input by the user of the information processing device 3 regarding the profile of the user's acquaintance for each acquaintance. The profile information is recorded in, for example, a recording device 517 (see FIG. 17 described later) installed in the information processing device 3. "Acquaintances" include the user's family, relatives, friends, acquaintances, and the like. In this embodiment, a case where the acquaintance is mainly a friend will be explained.

Specifically, the profile information recording processing unit 9 records basic information input by the user, including, for example, the friend's gender, age, marital status, presence or absence of children, etc., as the friend's profile information. Further, the profile information recording processing unit 9 records present-related information input by the user, including, for example, the friend's hobbies and preferences, anniversary, and present budget, as the friend's profile information. Further, the profile information recording processing unit 9 records, as the friend's profile information, information related to a group including other friends with whom the user is expected to meet when meeting the friend, which is input by the user. In this case, when the frequency information of any friend belonging to a group is set or updated, the profile information recording processing unit 9 causes the frequency information to be reflected on other friends belonging to the group. Further, the profile information recording processing unit 9 records frequency information, which is input by the user and relates to, for example, the frequency of the schedule in which the user meets with friends, as profile information for each friend. Further, the profile information recording processing unit 9 records information input by the user, such as information related to the area and place where the user meets the friend, as the friend's profile information.

3 and 4 show an example of a friend's profile screen displayed on the touch panel 7 of the information processing device 3. 3 and 4 are, for example, profile screens of "Tomoko", one of the user's friends. In FIG. 3, icon 25 is an avatar representing the user. Moreover, the icons 27, 29, 31, and 33 are avatars representing the user's friends "Tomoko," "Sakura," "Midori," and "Kenta," respectively. In this example, when the user meets "Tomoko", it is assumed that other friends "Sakura", "Midori", and "Kenta" will also gather together to meet, so "Tomoko"'s profile screen will be displayed. , "Sakura," "Midori," and "Kenta" are set to belong to the same group. Note that the user can add a friend to the group by touching the plus button 35.

As shown in FIG. 3, the profile screen displays a friend's hobby input field 37 and a favorite thing input field 39. The user inputs "Tomoko's" hobbies and favorite things into these input fields 37 and 39. Furthermore, an anniversary input field 41 and a budget input field 43 are displayed on the profile screen. In these input fields 41 and 43, the user inputs "Tomoko's" anniversary and the budget for gifts to be given on the anniversary. It is possible to input multiple anniversaries and budgets. For example, different budgets can be set for different types of anniversaries, such as birthdays, Valentine's Day, wedding anniversaries, etc.

FIG. 4 is a continuation of the friend's profile screen shown in FIG. 3. For example, the user vertically scrolls the profile screen shown in FIG. 3 to display the screen shown in FIG. 4. As shown in FIG. 4, an input field 45 for a friend's address and an input field 47 for a group are displayed on the profile screen. The user enters the name of the group to which the friend belongs in the input field 47. The number of people making up the group is automatically displayed in parentheses of the group name. In the example shown in FIG. 4, "Tomoko" is set to belong to the group "Tomoko (4)" consisting of four people.

Also displayed on the profile screen is an input field 49 for the frequency of meetings with friends. In the example shown in FIG. 4, the frequency of meeting with "Tomoko" is set, for example, once every six months. The frequency of meeting is set in advance, for example, once a year, once every six months, once every three months (one season), every month, every week, etc., and the user selects and sets the meeting frequency. For example, for a friend who meets once a year for an anniversary, the frequency of meeting is set to once a year. When meeting the friend, the user may purchase a recommended present in advance using a present suggestion function, which will be described later, and bring it with him or her to give it.

Also displayed on the profile screen are an input field 51 for the area where the user meets friends and an input field 53 for the location. The user inputs into the input field 51 the area (for example, a place name such as Yokohama) in which he/she desires to meet a friend. For example, if it's a holiday, you can select the midway point between your friend's address and the user's address, or if it's a weekday, you can set the optimal area by selecting the midway point between each other's workplaces. The user also inputs in the input field 53 the type of place where he or she desires to meet with friends. For example, you can choose a location such as a cafe, park, restaurant, etc. according to your or your friends' preferences.

Returning to FIG. 2, the calendar recording processing unit 11 records schedule information input by the user, including the date on which the user most recently met with a friend, in the user's calendar for each friend. Furthermore, the calendar recording processing unit 11 causes the calendar to display dates on which the schedule is available based on the user's settings. The calendar recording processing unit 11 displays a list of friends when a specific date is selected based on a meeting schedule proposed by a meeting schedule proposal processing unit 13 (to be described later) from among dates with free schedules. When a specific friend is selected from the list of friends, the calendar recording processing unit 11 records the date as the day to meet the friend, and displays the friend's avatar on the date. The schedule information is recorded in, for example, a recording device 517 (see FIG. 17 described later) installed in the information processing device 3.

FIG. 5 shows an example of a calendar screen displayed on the touch panel 7 of the information processing device 3. As shown in FIG. 5, the calendar screen displays an input field 55 for setting open days in the schedule. When the user inputs the type of date in the input field 55, an "O" mark 56 indicating no events is automatically displayed on the calendar. In the example shown in FIG. 5, holidays, weekends, Wednesdays, and Fridays are set, for example. Further, when the user touches the "x" mark 58 indicating that the user has a scheduled event and then selects a date on which the schedule on the calendar is filled, the "x" mark 58 that indicates that the user has an event scheduled is displayed on the calendar. Further, when the user selects a specific date from among the dates on which the "〇" mark 56 is displayed, for example, a date based on a recommended schedule proposed by the meeting schedule proposal processing unit 13 described later, for example, as shown in FIG. A friend list will be displayed. When the user selects a specific friend from the friend list, the selected date is set as the day to meet the friend, and an icon 57 that is the friend's avatar is displayed on the date. Although the icon 57 is shown in a simplified manner in FIG. 5, avatars representing each friend are actually displayed.

If the user actually meets a friend on the scheduled date, the user records that the meeting has been completed on that date. This records the date on which the user most recently met a friend on the calendar.

For example, by selecting a specific friend or group from the recommended schedule screen shown in FIG. 7 or FIG. When selected, the icon 57 of the friend or group may be automatically displayed on the date.

FIG. 6 shows an example of the friend list. In the example shown in FIG. 6, a list of the user's friends is displayed, and for each friend, for example, icons 27, 31, and 59, which are avatars, group information 61 related to the group to which it belongs, and anniversary information 63, which is the date of the anniversary, are displayed. Displayed. Although FIG. 6 shows simplified avatars of friends "Kaho" and "Ken," avatars representing each friend are actually displayed. The same applies to FIGS. 7, 8, 10, etc., which will be described later.

Returning to FIG. 2, the meeting schedule proposal processing unit 13 proposes a plan for meeting with a friend based on the frequency information recorded as the friend's profile information and the schedule information (the date of the most recent meeting with the friend) recorded in the calendar. Suggest meeting dates for each friend. For example, you may suggest a date that is simply the date of the most recent meeting plus the period of frequency information, or you may suggest a date that the user has set in the calendar as a day when the user's schedule is free around the date. good. At this time, if a group is set for the friend, the meeting schedule proposal processing unit 13 proposes a meeting schedule for each group. For example, in the case of "Tomoko", "Sakura", "Midori", and "Kenta" who belong to "Tomoko"'s group, instead of proposing a schedule for each friend individually, they will propose a schedule for "Tomoko (4)" group. Suggest a date.

FIG. 7 shows an example of a recommended schedule screen that displays a list of meeting schedules proposed by the meeting schedule proposal processing section 13. As shown in FIG. 7, on the recommended schedule screen, recommended dates for each friend or group are displayed together with icons 27 and 59 in chronological order. In the example shown in FIG. 7, "Ken" is displayed as a friend because no group is set, and the others "Tomoko (4)" and "Kaho (2)" are displayed as a group.

In addition, when displaying a list of multiple meeting dates for meeting with friends or groups, the meeting schedule proposal processing unit 13 selects the meeting schedule of the friend or group whose number of days has elapsed from the last meeting date to the shorter one. It may be displayed with priority over other friends' or group's meeting schedules. In this case, the meeting schedule proposal processing unit 13 calculates the number of days that have passed since the last meeting for each friend or group based on the date of the last meeting for each friend or group and the current date. FIG. 8 shows an example of the recommended schedule screen in this case. In the example shown in FIG. 8, recommended dates for each friend or group are displayed higher as the number of days elapsed since the last date they met is higher. In this example, for example, the number of days that have passed since the last matching date increases in the order of "Kaho (2)" group, "Tomoko (4)" group, and "Ken".

Returning to FIG. 2, the meeting place proposal processing unit 15 proposes a specific place to meet the friend based on information related to the area and type of place recorded as the friend's profile information. The meeting place proposal processing unit 15 accesses the server device 5 and searches for and extracts a shop or the like that exists within the set area and corresponds to the set place.

FIG. 9 shows an example of a recommended place screen that displays places proposed by the meeting place proposal processing section 15. The recommended place screen is displayed when a specific friend or group is selected from the recommended schedule screen shown in FIG. 7 or 8, for example. FIG. 9 shows a recommended place screen when, for example, the group "Tomoko (4)" is selected on the recommended schedule screen. As shown in FIG. 9, the recommended place screen includes, for example, a "Tomoko" icon 27, a proposed date and weather forecast information 65 for that date, and area information 67 set as "Tomoko" profile information. and location information 69 are displayed. Further, on the recommended place screen, a list of recommended places and shops proposed by the meeting place proposal processing unit 15 is displayed together with an image 71 and a description 73. In the example shown in FIG. 9, a plurality of parks, cafes, restaurants, etc. in Yokohama, for example, are displayed based on the area and location information of "Tomoko". The user can view more recommended locations by scrolling horizontally. Note that in FIG. 9, illustration of the image 71 is omitted. By selecting a specific location from among the displayed locations, the user can, for example, make a reservation if the location is a store, or purchase tickets if the location is an amusement park. You can purchase it. The reservation and purchase processing may be executed via an external server device 5 that provides a reservation service and a payment service, for example.

The meeting place proposal processing unit 15 also proposes a gift to be used as a souvenir when the user meets the group of "Tomoko (4)". The meeting place proposal processing unit 15 may select, for example, based on the user's address, products or special products unique to the user's local area from within a budget range initially set in advance or set by the user. At that time, you can propose a single gift according to your budget, or you can distribute the budget to the number of people in the group (for example, if the budget is 2000 yen, you can distribute it to 4 people and give 500 yen per person). etc.) You may also suggest gifts for each person. Furthermore, a gift that matches the friend's hobbies and preferences may be suggested by a process similar to that of the present proposal processing unit 19 described later. On the recommended place screen, a list of recommended gifts proposed by the meeting place proposal processing unit 15 is displayed together with an image 75 and a description 77. In the example shown in FIG. 9, based on the user's address information, a plurality of baked goods, cakes, chocolates, etc. sold at a famous confectionery shop in the user's hometown are displayed, for example. The user can further refer to recommended gifts by scrolling horizontally. Note that in FIG. 9, illustration of the image 75 is omitted. A user can purchase a specific product by selecting a specific product from among the displayed multiple products. The purchase process may be executed, for example, via an external server device 5 that provides a payment service.

Returning to FIG. 2, the anniversary reminder processing unit 17 reminds each friend of an anniversary that approaches a predetermined period of time based on the anniversary information recorded as the friend's profile information. The "predetermined period" is, for example, one week, two weeks, one month, etc.

FIG. 10 shows an example of an anniversary reminder screen that displays a list of anniversaries reminded by the anniversary reminder processing section 17. As shown in FIG. 10, on the anniversary reminder screen, each friend's anniversary is displayed along with icons 27, 29, and 59 in descending order of date. In this example, for example, there is less than one week until Tomoko's birthday, less than two weeks until Sakura's birthday, and less than one month until Yumi's Valentine's Day. is displayed.

Returning to FIG. 2, the gift proposal processing unit 19 sends a present to the friend on the anniversary based on the friend's gift-related information selected by the user from among the friend's anniversaries reminded by the anniversary reminder processing unit 17. Suggest a gift. Details of the present proposal method will be described later.

The purchase execution processing unit 21 executes a purchase process for a present selected by the user from among the presents proposed by the gift proposal processing unit 19. The purchase process may be executed, for example, via an external server device 5 that provides a payment service.

FIG. 11 shows an example of a recommended present screen that displays presents proposed by the present proposal processing section 19. The recommended gift screen is displayed when a specific friend is selected from the anniversary reminder screen shown in FIG. 10, for example. FIG. 11 shows a recommended present screen when, for example, "Tomoko's" birthday is selected on the anniversary reminder screen. As shown in FIG. 11, the recommended gift screen includes, for example, the "Tomoko" icon 27, the birthday date 79 set as Tomoko's anniversary, and a shopping cart containing the product selected by the user. 81 is displayed. Further, on the recommended present screen, presents proposed by the present proposal processing section 19 are displayed in a list along with an image 83 and a description 85. In the example shown in FIG. 11, a plurality of products are displayed for each genre, such as tennis and video games, based on "Tomoko's" hobbies. The user can further refer to recommended products by scrolling horizontally. Note that in FIG. 11, illustration of the image 83 is omitted. When the user selects a specific product from among the displayed products, the product is stored in the shopping cart 81. Thereafter, the user can purchase the product by performing an appropriate purchase operation. The delivery destination of the purchased product may be set to the user and the user hands the present to the friend when the user meets the friend, or the user may set the delivery destination of the purchased product to the friend and deliver the present directly to the friend.

Returning to FIG. 2, the product information acquisition processing unit 23 acquires product information of a product that is a candidate for a gift from, for example, an external server device 5 operated by a seller of the product. "Product information" includes basic information representing the content of the product, information such as target demographics, etc. The gift proposal processing unit 19 determines the score of the present by matching the product information acquired by the product information acquisition processing unit 23 with basic information including the friend's gender, age, marital status, presence of children, etc. The first stage calculates the gift score by associating the above product information with the hobbies and preferences included in the friend's profile information. a third stage of calculating a score of the present for the persona using an algorithm; The predetermined algorithm also includes other machine learning such as, for example, logistic regression. The present proposal processing unit 19 proposes a present based on the sum of the scores of the first stage, second stage, and third stage.

12 to 15 show an example of a present proposal method by the present proposal processing unit 19. FIG. 12 shows an example of the first stage. As shown in FIG. 12, the gift proposal processing unit 19 performs predetermined matching items (for example, gender, age category, marital status) for each product based on the basic information of the friend's profile and the target group. Matching is performed regarding the presence or absence of parents, presence or absence of children, etc.), and it is determined whether it is OK or NG. If there is data (? in FIG. 12) that is not included in the friend's profile or product information, matching is performed based on usable data other than the data. The present proposal processing unit 19 calculates a score for each product according to the matching result. In the example shown in FIG. 12, for example, the score of product 1 is 1, the score of product 2 is 0.8, and the score of product 3 is 0.5.

FIG. 13 shows an example of the second stage. The present proposal processing unit 19 calculates a score for each product by associating product information with hobbies and preferences included in the friend's profile information, for example, by using Word embedding or other NLP (natural language processing) methods. . FIG. 13 is a graph plotting each word (indicated by a node) vectorized by, for example, word embedding and showing the relationship with related fields. For example, in the example shown in Figure 13, the groups that correspond to cats, stuffed animals, and flowers, which are included in Tomoko's favorite things, are group 2 (pet-related), group 5 (toy-related), and group 6 (gardening-related). be. The present proposal processing unit 19 calculates the sum of scores for groups 2, 5, and 6 for each product. In the example shown in FIG. 13, for example, the score for product 1 is 1.0, which is the sum of the score 0.5 for group 2 and the score 0.5 for group 5, and the score for product 2 is 0.5 for group 6. ing.

FIG. 14 shows an example of the third stage. The present proposal processing unit 19 constructs a persona based on the basic information of the friend's profile. For example, in the example shown in Figure 14, Persona A is male, in his teens, with no spouse and children, Persona B is female, in his 20s, with a spouse and no children, and Persona B is male, in his 30s, with a spouse and children. Persona C and Persona D, who is female, in her 40s, has a spouse and children, are constructed. Next, the present proposal processing unit 19 uses a predetermined algorithm based on, for example, the following equations (1) to (5) to calculate the score of each product for the friend's persona.

ln[Y/(1-Y)]=a+b ₁ X ₁ +b ₂ X ₂ +b ₃ X ₃ ... Formula (1)
Note that Y is the probability of the persona, Xn is the product, and bn is the partial regression coefficient.

ln(odds of A)=-0.74+0.38X ₁ +0.21X ₂ +... Formula (2)
ln(odds of B)=-0.34+0.76X ₁ +0.13X ₂ +... Formula (3)
ln(odds of C)=-0.74+0.38X ₁ +0.21X ₂ +... Formula (4)
ln(odds of D)=-0.34+0.76X ₁ +0.13X ₂ +... Formula (5)

As shown in FIG. 15, as described above, the present proposal processing unit 19 calculates the first stage score, second stage score, third stage score, and first to third stage scores for a specific friend. Calculate the total score for each product. Then, the gift proposal processing unit 19 sorts the products in descending order of the total score, and suggests products in descending order of the score.

<3. Processing procedure executed by the information processing device>
Next, an example of a processing procedure executed by the CPU 501 of the information processing device 3 (see FIG. 17 described later) will be described using FIG. 16.

As shown in FIG. 16, in step S5, the information processing device 3 determines whether the user has performed an operation to display the profile screen. When the information processing device 3 determines that the user has not performed the above operation (step S5: NO), the information processing device 3 moves to step S25, which will be described later. On the other hand, if the information processing device 3 determines that the user has performed the above operation (step S5: YES), the information processing device 3 moves to the next step S10.

In step S10, the information processing device 3 displays a profile screen on the touch panel 7.

In step S15, the information processing device 3 determines whether the profile information has been edited by the user. Editing of profile information includes, for example, basic information including gender, age, marital status, and presence of children, hobbies and preferences, anniversaries, gift-related information including gift budget, information about groups, information about the frequency of meeting dates, These are new settings and updates of information related to areas and locations. If the profile information is not edited (step S15: NO), the information processing device 3 moves to step S25, which will be described later. On the other hand, if the profile information has been edited (step S15: YES), the information processing device 3 moves to the next step S20.

In step S20, the information processing device 3 causes the profile information recording processing unit 9 to record the profile information edited in step S15.

In step S25, the information processing device 3 determines whether the user has performed an operation to display the calendar screen. If the information processing device 3 determines that the user has not performed the above operation (step S25: NO), the information processing device 3 moves to step S45, which will be described later. On the other hand, if the information processing device 3 determines that the user has performed the above operation (step S25: YES), the information processing device 3 moves to the next step S30.

In step S30, the information processing device 3 displays a calendar screen on the touch panel 7.

In step S35, the information processing device 3 determines whether the schedule information has been edited by the user. Editing schedule information includes new settings and updates, such as days when the schedule is free, days when the schedule is full, days when you plan to meet friends, and days when you met friends. If the schedule information is not edited (step S35: NO), the information processing device 3 moves to step S45, which will be described later. On the other hand, if the schedule information has been edited (step S35: YES), the information processing device 3 moves to the next step S40.

In step S40, the information processing device 3 causes the calendar recording processing unit 11 to record the schedule information edited in step S35.

In step S45, the information processing device 3 determines whether the user has performed an operation to display the recommended schedule screen. If the information processing device 3 determines that the user has not performed the above operation (step S45: NO), the process moves to step S65, which will be described later. On the other hand, if the information processing device 3 determines that the user has performed the above operation (step S45: YES), the information processing device 3 moves to the next step S50.

In step S50, the information processing device 3 causes the meeting schedule proposal processing unit 13 to display a recommended schedule screen on the touch panel 7.

In step S55, the information processing device 3 determines whether a specific friend or group has been selected on the recommended schedule screen. If a specific friend or group is not selected (step S55: NO), the information processing device 3 moves to step S65, which will be described later. On the other hand, if a specific friend or group is selected (step S55: YES), the information processing device 3 moves to the next step S60.

In step S60, the information processing device 3 causes the meeting place proposal processing unit 15 to display a recommended place screen. Although not shown in the flowchart, by selecting a specific location on the recommended location screen, the user can make a reservation for a restaurant, etc.

In step S65, the information processing device 3 determines whether the user has performed an operation to display the anniversary reminder screen. When the information processing device 3 determines that the user has not performed the above operation (step S65: NO), the information processing device 3 moves to step S85, which will be described later. On the other hand, if the information processing device 3 determines that the user has performed the above operation (step S65: YES), the information processing device 3 moves to the next step S70.

In step S70, the information processing device 3 causes the anniversary reminder processing unit 17 to display an anniversary reminder screen on the touch panel 7.

In step S75, the information processing device 3 determines whether a specific friend has been selected on the anniversary reminder screen. If a specific friend is not selected (step S75: NO), the information processing device 3 moves to step S85, which will be described later. On the other hand, if a specific friend is selected (step S75: YES), the information processing device 3 moves to the next step S80.

In step S80, the information processing device 3 causes the present proposal processing unit 19 to display a recommended present screen on the touch panel 7.

In step S85, the information processing device 3 determines whether or not the user has performed a product purchase operation on the recommended gift screen. If there is no product purchase operation (step S85: NO), the process moves to step S95, which will be described later. On the other hand, if there is an operation to purchase a product (step S85: YES), the process moves to the next step S90.

In step S90, the information processing device 3 causes the purchase execution processing unit 21 to execute a purchase process for the present selected by the user in step S85.

In step S95, the information processing device 3 determines whether there is an operation to terminate the application program. If there is no end operation (step S95: NO), the process returns to the first step S5. On the other hand, if there is an end operation (step S95: YES), this flowchart ends.

<4. Effects of embodiment>
In the information processing device 3 of the present embodiment, the user can send information related to the frequency of meeting with friends, such as wanting to meet once a year, wanting to meet every six months, wanting to meet once a season, wanting to meet every month, etc. You can enter profile information for each friend, such as. The user can also record the date on which the user most recently met a friend for each friend in the user's calendar. The information processing device 3 then proposes a meeting schedule for each friend or group based on the recorded frequency-related information and the date of the most recent meeting with the friend. This allows the user to know the optimal meeting schedule for each friend or group according to his or her wishes, so even if the user is busy, he or she can easily make plans in advance with the friends he or she wants to meet. Moreover, even if the number of friends increases, it becomes possible to meet all of them. In this way, the user can efficiently manage the schedule for meeting friends.

Furthermore, in this embodiment, the user records in the calendar the dates on which his/her schedule is free, selects a specific date based on the proposed meeting schedule from among the available dates, and displays the selected date. By selecting the friend you want to meet from the list of friends displayed, you can record the date on which you plan to meet the friend on the calendar. Also, since the friend's avatar is displayed on the date, it is easy to see who you are planning to meet and when. Therefore, it is possible to efficiently manage the schedule for meeting friends.

Furthermore, in this embodiment, the meeting schedule of the friend whose number of days has elapsed since the last meeting is given priority over the meeting schedule of the friend whose number of days has passed since the last meeting is displayed with priority. For example, when multiple meeting dates are displayed in a list vertically in parallel on the recommended schedule screen, the meeting schedule of a friend with the longest elapsed time will be displayed higher up so that it is displayed preferentially. . This allows you to prioritize meetings with friends you haven't seen for a long time.

Moreover, in this embodiment, when a user meets a friend, a case can be considered in which the user meets in a group including another friend that the user and the friend have in common. In this embodiment, such a group can be recorded as a friend's profile information, and if frequency information is set for any friend who belongs to the group, it will also be recorded for other friends who belong to the group. The frequency information is reflected and meeting dates are proposed for each group. This eliminates the need to manage the meeting schedule for each friend when meeting with multiple friends at once, making it easier to manage the meeting schedule. Further, since the trouble of setting frequency information for each friend can be saved, convenience for the user can be improved.

Further, in this embodiment, in particular, recommended shops and places are suggested along with the meeting schedule, so that user convenience can be further improved.

In addition, in this embodiment, the user records the friend's hobbies, preferences, anniversary, gift budget, etc. as the friend's profile information, and the user is reminded of the friend's anniversary one by one. It is possible to prevent a user from forgetting a friend's anniversary. Furthermore, since the most suitable present is proposed according to the friend's hobbies and preferences and one's own budget in accordance with the anniversary, it is possible to maintain good human relations with the friend. Furthermore, since the purchase of the proposed present can be executed on the application, the user's convenience can be further improved.

Moreover, in this embodiment, the scores of products are calculated in three stages, ie, the first stage, the second stage, and the third stage, and presents are proposed based on the total of these scores. This makes it possible to propose gifts even during periods when the amount of data such as profile information is small, and can cover such periods. Further, when profile information and product information increase, it becomes possible to make more detailed proposals, and the proposal function can be improved.

<5. Hardware configuration of information processing device>
Next, with reference to FIG. 17, an example of the hardware configuration of the information processing device 3 that implements each processing unit implemented by the application program executed by the CPU 501 described above will be described.

As shown in FIG. 17, the information processing device 3 includes, for example, a CPU 501, a ROM 503, a RAM 505, a dedicated integrated circuit 507 built for a specific purpose such as an ASIC or FPGA, an input device 513, and an output device 513. It has a device 515, a recording device 517, a drive 519, a connection port 521, and a communication device 523. These configurations are connected to each other so as to be able to transmit signals via a bus 509, an input/output interface 511, and the like.

The application program can be recorded in, for example, a ROM 503, a RAM 505, a recording device 517 such as a hard disk, or the like.

Further, the application program may be temporarily or permanently (non-temporarily) recorded on a removable recording medium 525 such as a magnetic disk such as a flexible disk, various CDs, an MO disk, an optical disk such as a DVD, or a semiconductor memory. You can also leave it as is. Such a recording medium 525 can also be provided as so-called package software. In this case, the application programs recorded on these recording media 525 may be read by the drive 519 and recorded on the recording device 517 via the input/output interface 511, the bus 509, or the like.

Further, the application program can also be recorded on, for example, a download site, another computer, another recording device, etc. (not shown). In this case, the application program is transferred via a network NW such as the Internet, and the communication device 523 receives this application program. The application program received by the communication device 523 may be recorded in the recording device 517 via the input/output interface 511, the bus 509, or the like.

Further, the application program can also be recorded in an appropriate external connection device 527, for example. In this case, the application program may be transferred via an appropriate connection port 521 and recorded on the recording device 517 via the input/output interface 511, bus 509, or the like.

Then, the CPU 501 executes various processes according to the programs recorded in the recording device 517, so that the profile information recording processing section 9, the calendar recording processing section 11, the meeting schedule proposal processing section 13, the meeting place proposal processing 15, an anniversary reminder processing section 17, a present proposal processing section 19, a purchase execution processing section 21, a product information acquisition processing section 23, and the like. At this time, the CPU 501 may, for example, directly read the application program from the recording device 517 and execute it, or may once load the application program into the RAM 505 and then execute it. Furthermore, for example, when receiving an application program via the communication device 523, drive 519, or connection port 521, the CPU 501 may directly execute the received program without recording it on the recording device 517.

Further, the CPU 501 may perform various types of processing based on signals and information input from an input device 513 including, for example, a mouse, a keyboard, a microphone, and the like.

Then, the CPU 501 outputs the result of executing the above processing from the output device 515, which includes, for example, an audio output unit (not shown) such as a speaker or headphones. Further, the CPU 501 may transmit the processing result via the communication device 523 or the connection port 521, or may record it on the recording device 517 or the recording medium 525, if necessary.

Further, in addition to the methods described above, the methods according to the above embodiments and each modification may be used in combination as appropriate.

Although not illustrated in detail, the present invention can be implemented with various modifications within the scope of the invention.

1 Information management system 3 Information processing device 5 Server device 7 Touch panel 9 Profile information recording processing section 11 Calendar recording processing section 13 Meeting schedule proposal processing section 15 Meeting place proposal processing section 17 Anniversary reminder processing section 19 Present proposal processing section 21 Purchase execution Processing unit 23 Product information acquisition processing unit

Claims (8)

information processing equipment,
a profile information recording processing unit that records frequency information related to the frequency of the schedule in which the user meets with acquaintances, input by the user, as profile information for each of the acquaintances;
a calendar recording processing unit that records schedule information input by the user, including the date when the user most recently met the acquaintance, in the user's calendar for each acquaintance;
a meeting schedule proposal processing unit that proposes a meeting schedule for meeting the acquaintances for each of the acquaintances based on the frequency information and the schedule information;
An application program to function as The calendar recording processing section includes:
Displaying on the calendar the dates on which the schedule is available based on the settings of the user, and selecting a specific date from among the dates on which the schedule is available based on the meeting schedule proposed by the meeting schedule proposal processing unit. If a specific acquaintance is selected from the list of acquaintances, the date is recorded as the date of meeting the acquaintance, and the avatar of the acquaintance is displayed on the date.
The application program according to claim 1. The meeting schedule proposal processing unit,
A list of a plurality of meeting dates for meeting a plurality of acquaintances is displayed, and the meeting schedule of the acquaintance whose number of days has elapsed since the last meeting is given priority over the meeting schedule of the acquaintance whose number of days has elapsed since the last meeting. indicate,
The application program according to claim 1. The profile information recording processing unit includes:
Recording information input by the user regarding a group including other acquaintances with whom he or she is expected to meet when meeting the acquaintance, as profile information of the acquaintance;
When the frequency information of any of the acquaintances belonging to the group is set or updated, the frequency information is reflected on other acquaintances belonging to the group,
The meeting schedule proposal processing unit
proposing the meeting schedule on a group-by-group basis;
The application program according to claim 1. The profile information recording processing unit includes:
Recording information input by the user regarding the area and location where the user meets the acquaintance as the acquaintance's profile information;
The information processing device,
a meeting place proposal processing unit that proposes a store or place to meet the acquaintance based on information related to the area and place;
The application program according to claim 1, for further functioning as an application program. The profile information recording processing unit includes:
Recording present-related information input by the user, including hobbies and preferences, anniversaries, and gift budget of the acquaintance, as profile information of the acquaintance;
The information processing device,
an anniversary reminder processing unit that reminds each of the acquaintances of the anniversary that is approaching a predetermined period;
a present proposal processing unit that proposes a present to give to the acquaintance on the anniversary based on the present-related information of the acquaintance selected by the user from among the reminded anniversaries of the acquaintance;
a purchase execution processing unit that executes purchase processing for the present selected by the user from among the proposed presents;
The application program according to any one of claims 1 to 5, for further functioning as an application program. The information processing device,
a product information acquisition processing unit that acquires product information of products that are candidates for the present;
further function as
The profile information recording processing unit includes:
Recording basic information input by the user, including the acquaintance's gender, age, marital status, and presence or absence of children, as the acquaintance's profile information,
The gift proposal processing unit is
a first stage of calculating the score of the present by matching the product information and the basic information;
a second stage of calculating the score of the present by associating the product information with the hobbies and preferences;
a third stage of constructing a persona of the acquaintance based on the basic information and calculating a score of the gift for the persona using a predetermined algorithm;
proposing the present based on the sum of scores of the first stage, the second stage, and the third stage;
The application program according to claim 6. An information processing device having a processor,
The processor includes:
recording frequency information related to the frequency of the schedule in which the user meets with acquaintances, which is input by the user, as profile information for each of the acquaintances;
recording schedule information input by the user, including the date when the user most recently met the acquaintance, in the user's calendar for each acquaintance;
proposing a meeting schedule for each of the acquaintances based on the frequency information and the schedule information;
An information processing device that executes.

Images