JP7775725B2 - Anniversary production device and anniversary production method - Google Patents

Description

The present invention relates to an anniversary production device and an anniversary production method.

Conventionally, fragrance emitting devices have been disclosed that release a blended scent inside a vehicle to notify occupants that their anniversary is approaching (for example, Patent Document 1). When an occupant is in the vehicle on their anniversary, the fragrance emitting device described in Patent Document 1 stores the scent inside the vehicle detected by the scent detection unit in a scent memory unit in association with the occupant's anniversary, and releases into the vehicle cabin a scent approximately equivalent to the scent inside the vehicle associated with the anniversary around the time of the anniversary stored in the scent memory unit.

JP 2016-199098 A

The above-mentioned fragrance emitting device has the problem that when anniversaries determined based on the relationships between multiple users are notified, even if the relationships between these multiple users change, the anniversary will still be notified through the scent, resulting in unnecessary celebration of the anniversary.

The problem that this invention aims to solve is to provide an anniversary production device or anniversary production method that can celebrate anniversaries in response to changes in the relationships between multiple users.

The present invention solves the above problem by storing information about common anniversaries based on common attributes shared between the target user and related users other than the target user, determining whether the relationship between the target user and related users has changed before executing a performance process to celebrate the anniversary, and either canceling the performance process or changing the content of the performance process depending on the determination result.

The present invention allows anniversaries to be celebrated in response to changes in the relevance between multiple users.

FIG. 1 is a block diagram of a vehicle including an anniversary effect production device according to this embodiment. FIG. 2 is a table for explaining anniversary information. FIG. 3 is a flowchart showing the control flow of the controller. FIG. 4 is a flowchart showing a sub-flow of step S7 in FIG. FIG. 5 is a flowchart showing a sub-flow (modification) of step S7 in FIG.

One embodiment of the anniversary production device according to the present invention will be described with reference to the drawings. Figure 1 is a block diagram showing an example of the configuration of a vehicle equipped with an anniversary production device according to this embodiment. Below, an embodiment in which the anniversary production device is installed in a vehicle 200 will be described, but the anniversary production device is not limited to vehicles and may also be installed in a house, for example, as part of a residential system.

The anniversary production device is a device (system) that celebrates anniversaries of users riding in vehicle 200, and is installed in vehicle 200. The anniversary production device installed in vehicle 200 includes a camera 1, a display 2, a speaker 3, a memory 4, and a controller 10. Note that the components included in vehicle 200 are not limited to those shown in Figure 1, and may include other components, such as an engine or a motor.

Camera 1 is fixed inside the vehicle cabin and captures images of the interior from a fixed position within the cabin, outputting the captured image data to controller 10. Display 2 is mounted on the dashboard and displays images or videos, including map information, to the occupants. Display 2 is controlled by controller 10 and displays map images and guide images generated by the navigation system. Display 2 also displays special images for celebrating anniversaries. Special images include messages such as "Happy birthday, Mr./Ms. XX!" and animated videos. Display 2 is a touch panel that acquires information input by the user and outputs the acquired information to controller 10. Display 2 is controlled by controller 10 and displays maps and guide images from the navigation system.

Speaker 3 is installed inside the vehicle cabin and outputs sounds to the occupants. Speaker 3 is used for special effects to celebrate anniversaries, and may output a message such as "Congratulations on your wedding anniversary, Mr./Ms. XX!" or special sounds (such as the sound of fireworks). Speaker 3 is controlled by controller 10.

Memory 4 records user-related information related to the user, as well as information about anniversaries commemorating events and things. User-related information is information related to the user and includes at least information about the user's attributes, such as the user's personal information (name, age, gender, etc.). User attributes include personal attributes that belong to the individual user and common attributes that belong to relationships with other users. Common attributes include romantic partner, spouse, family, friendships, and business relationships.

Anniversaries are days to commemorate events or things, and are set according to the user's attributes. For example, if the user's attribute is individual, anniversaries set according to the individual's attributes (personal attributes) include anniversaries such as birthdays that belong to the individual, or anniversaries set by the individual at their discretion. If the user's attribute is common attributes, anniversaries set according to the common attributes include birthdays of lovers (users other than the user), wedding anniversaries, birthdays of family members or pets, birthdays of friends, and company anniversaries. Anniversaries are also categorized as individual anniversaries and common anniversaries. Individual anniversaries are anniversaries that are related to (attributed to) only the attributes (personal attributes) of the target user (the user), such as birthdays. Common anniversaries are anniversaries set according to common attributes between the target user and related users other than the target user (common attributes shared between the target user and related users).

The controller 10 identifies a target user based on user-related information and executes a performance process to celebrate an anniversary for the identified target user. The controller 10 is equipped with a computer having a processor (hardware and software). This computer has a ROM storing programs, a CPU for executing the programs, and the like. The controller 10 includes functional blocks: a user identification unit 11, an information processing unit 12, a relevance determination unit 13, and a performance processing unit 14. In this embodiment, the functions of the controller 10 are divided into four blocks, and the functions of each functional block are explained, but the functions of the controller 10 may also be divided into three or fewer, or five or more functional blocks.

The user identification unit 11 identifies the target user in the vehicle 200 based on a facial image (Face ID) included in the image captured by the camera 1, a key ID detected by the keyless entry system, or detection information from a fingerprint authentication sensor mounted on the steering wheel or vehicle door. The target user is a passenger who is the subject of the performance and is a user who is in the vehicle 200. The controller 10 identifies the target user by the following method, for example. The user's facial image is registered in advance, and the controller 10 performs image recognition on the image captured by the camera 1 and compares it with the registered facial image to identify the target user. Furthermore, under the keyless entry system, the key ID is registered in advance, and when a user operates the key around the vehicle or a user with the key approaches the vehicle, the controller 10 performs key authentication, unlocks the door, and identifies the target user. Note that other methods of identifying the target user may also be used.

The information processing unit 12 acquires user-related information and anniversary information from information input via the touch-panel display 2 and processes the user-related information and anniversary information by updating the data stored in memory 4 according to the acquired information. The information processing unit 12 also controls the display 2 to display a guide image (operation image) for the user to input user-related information and/or anniversary information. The guide image is a screen that allows the user to select the anniversary to be input, for example, using a pull-down menu. For example, when the user operates the display 2 to input user-related information such as name, birthday, family composition, friendships, etc., the information processing unit 12 acquires the user-related information and anniversary information from the information input by the user and stores the user-related information and anniversary information in memory 4.

Here, referring to Figure 2, the anniversary information stored in memory 4 will be described. Figure 2 is a table for explaining anniversary information. As shown in Figure 2, an ID is assigned to each anniversary, and the data indicating the anniversary information includes the following information: "target user," "single/shared anniversary," "related user," "name," and "date." The target user is the user who will be celebrating through the controller 10's performance processing. "Single/shared anniversary" indicates whether the anniversary is a single anniversary or a shared anniversary with other users. "Related user" indicates a related user when the anniversary is a shared anniversary. For example, the anniversary data for ID1 is data on User 1's birthday, so the information shown in Figure 2 is stored as the anniversary data. For example, the anniversary data for ID2 is data on the wedding anniversary between User 1 and User 2, so the information shown in Figure 2 is stored as the anniversary data. In particular, "single/shared anniversary" is shared, and the "related user" is User 2, User 1's spouse. In other words, memory 4 stores the shared anniversary information by associating the "target user (User 1)" with the "related user (User 2)."

When recording anniversary information in memory 4, the information processing unit 12 distinguishes between individual anniversaries and common anniversaries before storing the anniversary information in memory 4. For example, suppose user 1 selects "Birthday (own)" from a pull-down menu selection guide image on the screen of display 2 and enters the date of their birthday. The information processing unit 12 assigns a predetermined ID to the entered birthday information and stores each piece of anniversary information in memory 4. In this case, because "birthday" belongs only to user 1's "own" attribute, the information processing unit 12 associates the individual anniversary with the selected anniversary and stores the anniversary information in memory 4. Also, for example, if user 1 selects "wedding anniversary," the information processing unit 12 associates the common anniversary with the selected anniversary and stores the anniversary information in memory 4. In this way, the user does not necessarily have to enter the "individual/common anniversary" information; the information processing unit 12 may associate either the individual anniversary or the common anniversary with the anniversary selected by the user and store the anniversary information in memory.

Furthermore, when information about an anniversary other than a single anniversary is input, the information processing unit 12 may associate the input anniversary with a shared anniversary and store the anniversary information in memory. For example, a birthday, as an example of a single anniversary, is uniquely determined from user-related information and is not a shared anniversary with other users. On the other hand, anniversaries other than single anniversaries, such as birthdays, are anniversaries based on shared attributes with other users, so when information about an anniversary that does not correspond to a single anniversary is input, the information processing unit 12 may store the "Single/Shared Anniversary" item in memory 4 as a shared anniversary.

Before executing a special effect to celebrate an anniversary, the relevance determination unit 13 determines whether there has been a change in the relevance between the target user and related users. The relevance determination unit 13 determines whether there has been a change in the relevance based on the time/number of times the related user has boarded the vehicle, the number/number of times users other than the related user have boarded the vehicle, or input from the target user. The time related to boarding is, for example, the period from the related user's last boarding to the current boarding. The number of times related to boarding is the number of boardings per predetermined period. The method for determining whether there has been a change in the relevance will be explained together with the explanation of the overall control flow of the effect processing.

The effect processing unit 14 cancels the effect processing or changes the content of the effect processing depending on the relevance determination result by the relevance determination unit 13. The effect processing includes effect processing for celebrating an anniversary and normal effect processing when the vehicle system is started up normally. The effect processing for celebrating an anniversary is processing such as displaying a congratulatory message on the display 2 or playing music appropriate to the anniversary from the speaker 3. The normal processing is processing such as displaying a welcome message on the display 2 to welcome the user on board.

A specific example will be given to explain the performance processing by the performance processing unit 14 in response to the determination result of the relevance determination unit 13. For example, if the target user is "User A" and the related user is "User B," the common attribute derived from the information stored in memory 4 is "lover" and the anniversary is "dating anniversary." Assume that a change has occurred in the relevance between "User A" and "User B" from this state. The relevance determination unit 13 determines that there has been a change in the relevance between "User A" and "User B" because, for example, the number of rides by "User B" has decreased, or because it has been a long time since "User B" last rode until now. The relevance determination unit 13 determines the relevance at the time "User A" rides. If the relevance determination unit 13 determines that the relevance between "User A" and "User B" has changed when User A gets on the train, the performance processing unit 14 does not execute a performance effect celebrating the dating anniversary, even if the time of boarding is close to the dating anniversary between User A and User B, or even if the boarding date falls on the dating anniversary between User B. Instead of executing a performance process to celebrate the dating anniversary, the performance processing unit 14 executes a performance process that differs from the performance process executed during normal startup or the performance process to celebrate an anniversary.

The performance processing unit 14 also determines the content of the performance processing depending on the attributes of the target user or related users. For example, when celebrating the birthday of user D, who is user C's child, if the target user is user C, the performance processing unit 14 celebrates user D's birthday using messages and sounds for performance processing aimed at adults. On the other hand, if the target user is user D, i.e., if user D is riding in vehicle 200, the performance processing unit 14 celebrates user D's birthday using animated images and music preferred by user D for performance processing aimed at children. User D's preferences may be input in advance as user-related information, or may be estimated from user D's user-related information.

Next, the process of creating an anniversary effect using the controller 10 will be described with reference to Figure 3. Figure 3 is a flowchart showing the control flow of the controller 10.

In step S1, the user identification unit 11 of the controller 10 acquires information necessary to identify the user from images captured by the camera 1, etc., and compares the acquired information with user-related information stored in memory 4 to identify the target user. In step S2, the information processing unit 12 of the controller 10 extracts anniversary information related to the target user from memory 4. For example, in the example of Figure 2, if the target user is "User 1," the information processing unit 12 extracts anniversary data for ID1, ID2, and ID4.

In step S3, the information processing unit 12 determines whether today is one of the extracted anniversaries. If today is not an anniversaries, the control flow proceeds to step S5; if today is an anniversaries, the control flow proceeds to step S13.

In step S4, the information processing unit 12 identifies the closest anniversary from the extracted anniversaries. In step S5, the information processing unit 12 determines whether the identified anniversary is a common anniversary. If the identified anniversary is not a common anniversary, in step S6, the performance processing unit 14 of the controller 10 executes performance processing to announce the closest anniversary. For example, the performance processing unit 14 displays on the display 2 the date, name, etc. of the closest anniversary identified in the control flow of step S4.

On the other hand, if the identified anniversary is a common anniversary, in step S7, the association determination unit 13 of the controller 10 determines whether there has been a change in the association between the target user and the related user. The subflow shown in Figure 4 is executed in the flow for determining whether there has been a change in the association. In step S21, the association determination unit 13 extracts a determination threshold set for each association between the related user and the target user. The determination threshold is a threshold that is pre-set depending on the type of anniversary. The determination threshold is indicated by the length of the ride interval between the related users. For example, if the common anniversary is "User 2's birthday," the common attribute between the target user and the related user is friend. Since the ride interval between friends is relatively long, the determination threshold is set, for example, to six months or one year. For example, if the common anniversary is "wedding birthday," the common attribute between the target user and the related user is spouse. Since the ride interval between spouses is short, the determination threshold is set, for example, to several months (e.g., two or three months). The user identification unit 11 identifies the related user when the related user rides, and the information processing unit 12 stores the ride history of the related user in memory 4.

In step S22, the relevance determination unit 13 identifies a period during which the related user is not riding by calculating the riding interval of the related user from the riding history of the related user. The relevance determination unit 13 compares the period during which the related user is not riding with a determination threshold, and determines whether the period during which the related user is not riding is longer than the determination threshold. If the period during which the related user is not riding is longer than the determination threshold, in step S23, the relevance determination unit 13 determines that the relevance between the target user and the related user has changed. On the other hand, if the period during which the related user is not riding is equal to or shorter than the determination threshold, in step S24, the relevance determination unit 13 determines that the relevance between the target user and the related user has not changed (no change). The subflow then ends.

In the subflow shown in Figure 4, the number of rides of the related user may be used instead of the riding time. The number of rides is indicated as the number of times per predetermined period, and the judgment threshold is also indicated as the number of rides. The relevance determination unit 13 calculates the number of rides of the related user from the related user's riding history and compares the number of rides of the related user with the judgment threshold. If the number of rides of the related user is less than the predetermined number, the relevance determination unit 13 determines that the relevance between the target user and the related user has changed. Furthermore, if the number of rides of the related user is equal to or greater than the predetermined number, the relevance determination unit 13 determines that the relevance between the target user and the related user has not changed (no change).

The flow for determining whether there is a change in relevance may be the subflow shown in FIG. 5 instead of the subflow shown in FIG. 4. In step S31, the relevance determination unit 13 extracts a determination threshold set for each relevance between the related user and the target user. The determination threshold is a threshold set in advance depending on the type of anniversary and is expressed as the number of times the user has traveled. For example, if the common anniversary is "User 2's birthday," the common attribute with the related user is friend. Since the number of times friends travel is relatively low, the determination threshold is set, for example, to twice every six months. For example, if the common anniversary is "wedding birthday," the common attribute with the related user is spouse. Since the number of times spouses travel is high, the determination threshold is set, for example, to once per week. The user identification unit 11 also manages the number of times traveled for each identified target user. That is, for example, in the example of FIG. 2, in addition to the number of times traveled by User 1 and User 2, if a user other than User 1 and User 2 has traveled, the number of times this other user has traveled is also managed.

In step S32, the relevance determination unit 13 calculates the number of rides of a user other than the related user and compares the calculated number of rides with a determination threshold to determine whether the number of rides of the user other than the related user is greater than the determination threshold. If the number of rides of the user other than the related user is greater than the determination threshold, in step S33, the relevance determination unit 13 determines that the relevance between the target user and the related user has changed. On the other hand, if the number of rides of the user other than the related user is equal to or less than the determination threshold, in step S34, the relevance determination unit 13 determines that the relevance between the target user and the related user has not changed. For example, in the example of Figure 2, assume that another user 3 has more rides than user 2, who is registered as a related user on the wedding anniversary, and that user 3's number of rides is greater than the determination threshold set for the wedding anniversary. In such a case, the relevance determination unit 13 determines that the relevance between user 1 and user 2 has changed. Note that the relevance determination unit 13 may also compare the number of rides of user 2 and user 3 and determine that the relevance between the target user and the related user has changed if user 3's number of rides is greater. The subflow then ends.

Referring to FIG. 3 , if the determination flow in step S7 determines that the relationship between the target user and the related user has not changed, the relationship determination unit 13 executes a process in step S8 to inquire of the user about the relationship between the target user and the related user. The inquiry is directed to the target user. For example, the inquiry process displays information about the related user registered as a common anniversary on the display 2, and then displays a selection screen that allows the user to select "Yes" or "No" as to whether the relationship has changed. The occupant (target user) then touches a "Yes" or "No" button on the display 2 to input whether the relationship has changed. Note that the inquiry in step S8 is made when the identified anniversary is a common anniversary, but is not made when the identified anniversary is an individual anniversary. In other words, the controller 10 does not inquire of the target user about the individual anniversary. An individual anniversary is an anniversary attributed to an individual attribute, and does not cease to be an anniversary or change in content due to the association with another user. Therefore, the controller 10 does not make an inquiry about the individual anniversary.

Then, in step S9, the relevance determination unit 13 determines whether there has been a change in the relevance between the target user and the related user based on the results of the inquiry process. If there has been no change in the relevance, in step S10, the performance processing unit 14 executes performance processing to celebrate the common anniversary.

On the other hand, if the relationship has changed, in step S11, the information processing unit 12 updates the information about the common anniversary stored in memory 4. For example, in the example of Figure 2, if the relationship between the target user (user 1) and the related user (user 2) has changed, the information processing unit 12 deletes at least the information about the related user from the anniversary data for ID2. Note that updating the anniversary information is not limited to deleting the data about the related user, and the content of the related data may also be changed, for example, from "ordinary friends" to "close friends." Then, in step S12, the performance processing unit 14 executes normal performance processing.

That is, before executing the common anniversary effect processing, the controller 10 determines whether the relationship between users who share a common attribute corresponding to the common anniversary has changed (corresponding to the control flow of steps S7 and S9). If it determines that the relationship has changed, the controller 10 cancels the common anniversary effect processing. Furthermore, if the related user information is changed when updating the anniversary information, the controller 10 may change the effect processing content corresponding to the related user before the change to the effect processing content corresponding to the related user after the change. For example, if the attribute of the related user changes from "ordinary friend" to "close friend" based on the birthday data, the controller 10 may change the effect content from the ordinary birthday effect processing to a more spectacular effect processing.

If the determination flow in step S3 determines that today is an anniversary, then in step S13 the information processing unit 12 determines whether the identified anniversary is a common anniversary. If the identified anniversary is not a common anniversary, the control flow proceeds to step S15. On the other hand, if the identified anniversary is a common anniversary, then in step S14 the relevance determination unit 13 determines whether there has been a change in the relevance between the target user and related users. The relevance determination flow in step S14 is a subflow shown in Figure 4 or 5, and is similar to the determination flow in step S7.

If the judgment flow in step S3 determines that the identified anniversary is not a common anniversary, then in step S15, the performance processing unit 14 executes performance processing to celebrate the individual anniversary. Also, if the judgment flow in step S14 determines that there has been no change in the relationship between the target user and related users, then in step S15, the performance processing unit 14 executes performance processing to celebrate the common anniversary.

If it is determined that the relationship between the target user and related users has changed, the controller 10 executes the control flow of steps S16 and S17. The control flow of steps S16 and S17 is similar to the control flow of steps S11 and S12. Then, the controller 10 ends the control flow shown in FIG. 3.

As described above, in this embodiment, the memory 4 stores information about common anniversaries according to common attributes shared between the target user and related users other than the target user, and the controller 10 determines whether the relationship between the target user and related users has changed before executing the presentation process for celebrating the anniversary, and either cancels the presentation process or changes the content of the presentation process depending on the determination result. This allows anniversaries to be celebrated in accordance with changes in the relationship between multiple users. In other words, it is possible to avoid celebrating anniversaries when the relationship has changed, and therefore anniversaries can be celebrated appropriately. Furthermore, because the presentation process is executed with presentation content according to the change in relationship, anniversaries can be celebrated with appropriate presentation content.

Furthermore, in this embodiment, the controller 10 determines that the relationship between the target user and the related user has changed if the period during which the related user has not ridden is longer than a predetermined period and/or if the number of times the related user has ridden is less than a predetermined number. This allows the relationship between the target user and the related user to be appropriately determined.

In addition, in this embodiment, the memory 4 associates the target user with the related user and stores information about common anniversaries, and the controller 10 calculates the number of rides by the user and determines that the association between the target user and the related user has changed if the number of rides by a user other than the related user is greater than a predetermined number. This allows the association between the target user and the related user to be appropriately determined.

In addition, in this embodiment, the controller 10 executes an inquiry process to inquire of the user about the relationship between the target user and related users before the common anniversary, and determines whether the relationship between the target user and related users has changed based on the results of the inquiry process. This allows the relationship between the target user and related users to be appropriately determined.

Furthermore, in this embodiment, the controller 10 does not query the target user about individual anniversaries. This simplifies the query process.

In addition, in this embodiment, the display 2 acquires information about anniversaries selected by the user, and the controller 10 associates the selected anniversary with either an individual anniversary or a common anniversary, and stores the anniversary information in the memory 4. This eliminates the need for the user to select "individual" or "common" on the display 2 screen, thereby improving the operability of the system.

In addition, in this embodiment, the controller 10 determines the content of the effect processing according to the user's attributes. This allows appropriate effect processing to be executed.

In this embodiment, when the display 2 acquires information about an anniversary selected by a user, the controller 10 may inquire of the target user as to whether the selected anniversary is a separate anniversary or a shared anniversary. This allows the user to arbitrarily set the anniversary attributes.

In this embodiment, the user attribute information and anniversary information do not necessarily need to be stored in the on-board memory 4; they may be stored, for example, in a database within a server that can communicate with the vehicle 200, and the controller 10 may execute the above control process for celebrating the anniversary while communicating with the server.

As a variation of this embodiment, instead of executing the subflow shown in FIG. 4 or FIG. 5, the controller 10 may inquire of the target user whether the relationship between the target user and related users has changed. The inquiry to the target user can be made by executing processing similar to the control flow of step S8.

Note that the memory 4 corresponds to the "storage unit" of the present invention, and the display 2 corresponds to the "acquisition means" of the present invention.

The above-described embodiments have been described to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. Therefore, each element disclosed in the above embodiments is intended to include all design modifications and equivalents that fall within the technical scope of the present invention.

REFERENCE SIGNS LIST 1... camera 2... display 3... speaker 4... memory 10... controller 11... user identification unit 12... information processing unit 13... relevance determination unit 14... performance processing unit 200... vehicle

Claims (10)

In an anniversary production device for producing an anniversary of a user,
a storage unit that stores user-related information related to a user and information on anniversaries according to attributes of the user;
a controller that identifies a target user based on the user-related information and executes a performance process to celebrate the anniversary for the identified target user;
The storage unit stores information about a common anniversary according to a common attribute shared between the target user and related users other than the target user,
The controller
Before executing the rendering process, it is determined whether or not a relationship between the target user and the related user has changed;
The anniversary effect producing device stops the effect producing process or changes the content of the effect producing process according to the determination result. The anniversary effect producing device according to claim 1,
The controller
An anniversary production device that determines that the relationship between the target user and the related user has changed if the period in which the related user has not ridden is longer than a predetermined period and/or if the number of times the related user has ridden is less than a predetermined number. The anniversary effect producing device according to claim 1,
The storage unit stores information about the common anniversary in association with the target user and the related user;
The controller
Calculating the number of rides of the user;
The anniversary effect production device determines that the relationship between the target user and the related user has changed if the number of times a user other than the related user has ridden the vehicle is greater than a predetermined number. The anniversary effect production device according to any one of claims 1 to 3,
The controller
Before the common anniversary, an inquiry process is executed to inquire of the user about the relationship between the target user and the related user;
The anniversary effect production device determines whether or not the relationship between the target user and the related user has changed depending on the result of the inquiry process. The anniversary effect producing device according to claim 4,
The storage unit stores information about a single anniversary related only to attributes of the target user,
The anniversary production device wherein the controller does not inquire about the single anniversary to the target user. The anniversary effect production device according to any one of claims 1 to 4,
an acquisition means for acquiring information about the anniversary selected by the user;
The storage unit stores information about a single anniversary related only to attributes of the target user,
The controller inquires of the target user whether the selected anniversary corresponds to the individual anniversary or the common anniversary. The anniversary effect production device according to any one of claims 1 to 4,
an acquisition means for acquiring information about the anniversary selected by the user;
The storage unit stores information about a single anniversary related only to attributes of the target user,
The controller associates the selected anniversary with either the individual anniversary or the common anniversary, and stores information about the anniversary in the storage unit. The anniversary effect production device according to any one of claims 1 to 4,
an acquisition means for acquiring information about the anniversary from information input by the target user;
The storage unit stores information about a single anniversary related only to attributes of the target user,
The controller is an anniversary effect device that, if the input anniversary input by the target user is an anniversary other than the single anniversary, stores the input anniversary in the memory unit as the common anniversary. The anniversary effect production device according to any one of claims 1 to 8,
The controller is an anniversary effect producing device that determines the content of the effect processing according to the attributes of the user. An anniversary presentation method for presenting an anniversary of a user, executed by a processor, comprising:
a storage unit that stores information about anniversaries according to attributes of the user, storing user-related information related to the user and information about common anniversaries shared between the user and related users other than the target user;
Identifying the target user based on the user-related information;
determining whether or not a relationship between the target user and the related user has changed before executing a performance process for celebrating the anniversary for the identified target user;
The anniversary effect producing method stops the effect producing process or changes the content of the effect producing process depending on the determination result.