Information processing device, method of operating the information processing device, operating program of the information processing device

Abstract

This invention provides an information processing device, a method for operating the information processing device, and an operating program for the information processing device, which enable users to reflect on past memories while more concretely contemplating future events. [Solution] The CPU of the user terminal includes a screen generation unit and a screen output unit. The screen generation unit generates an image list screen in which the images owned by the user are arranged in chronological order. At that time, the screen generation unit places future event images, which are images of future events related to the user, in a future event display area, which is a future area in the chronological order of the images compared to the most recent image. The screen output unit outputs the image list screen to the display.

Description

Technical Field

[0001] The technology of the present disclosure relates to an information processing apparatus, a method of operating the information processing apparatus, and an operating program for the information processing apparatus.

Background Art

[0002] Conventionally, in order to enable a user to view a plurality of images held by the user collectively, a method of arranging the plurality of images vertically and horizontally and displaying them in a list has been adopted. For example, Patent Document 1 describes a technique of arranging and displaying a plurality of images in a list in the order of shooting date and time or shooting position.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the conventional image list display, by viewing past images, one can look back on past memories. Such recollection of memories serves as a trigger for thinking about future events, such as where to go next or what photos to take at the next place to visit. In order to make the thoughts about future events more concrete, there has been a demand to display past images and images of future events in a form that allows one to look back on past memories while thinking about future events.

[0005] One embodiment of the technology according to the present disclosure provides an information processing apparatus, a method of operating the information processing apparatus, and an operating program for the information processing apparatus that can more specifically circulate thoughts about future events while looking back on past memories.

Means for Solving the Problems

[0006] The information processing device disclosed herein comprises a processor and memory connected to or embedded in the processor. When the processor generates an image list screen in which images owned by the user are arranged in chronological order, it places future event images, which are images of future events related to the user, in a region in the chronological order of the images that is further in the sequence than the most recent image, and outputs the generated image list screen.

[0007] Preferably, the processor places an icon displaying a future event image in a future region in a selectable manner, and when an icon is selected, generates a future event image list screen with the future event images arranged in a sequence, and outputs the generated future event image list screen.

[0008] The processor prefers to arrange the future event images in the future event image list screen in order of the event's arrival time.

[0009] The future event image is preferably at least one of the following: a registered event image related to a registered event that the user has registered as an event; and a recommended event image related to a recommended event that is recommended to the user.

[0010] It is preferable that the processor displays images taken by the user during registered events in the image list screen in a way that distinguishes them from images unrelated to those registered events.

[0011] Preferably, when an image taken by the user is selected in a registration event experienced by the user on the image list screen, the processor generates an image display screen that includes the selected image and a link to access the registration event image of the registration event experienced by the user, and outputs the generated image display screen.

[0012] Preferably, the processor generates a registration screen that includes a registration event image of the registration event experienced by the user, a button to re-register the registration event as an upcoming event, and a button to recommend the registration event to the user's acquaintances, and outputs the generated registration screen.

[0013] Recommended events should preferably include events selected based on user attributes.

[0014] The operation method of the information processing device disclosed herein includes, when generating an image list screen in which images owned by the user are arranged in chronological order, placing future event images, which are images of future events related to the user, in a region in the chronological order of the images that is later than the most recent image among the images, and outputting the generated image list screen.

[0015] The operating program for the information processing device of this disclosure causes a computer to perform the following processes when generating an image list screen in which images owned by the user are arranged in chronological order: placing future event images, which are images of future events related to the user, in a region in the chronological order of the images that is later than the most recent image among the images; and outputting the generated image list screen. [Effects of the Invention]

[0016] The technology disclosed herein provides an information processing device, a method for operating the information processing device, and an operating program for the information processing device, which enable users to reflect on past memories while more specifically contemplating future events. [Brief explanation of the drawing]

[0017] [Figure 1] This is a diagram showing an image management system. [Figure 2] This diagram shows the information exchanged between the image management server and the user terminal. [Figure 3] This diagram shows the internal workings of the image database. [Figure 4]It is a diagram showing the inside of an event information DB and the content of event information. [Figure 5] It is a block diagram showing computers constituting an image management server and a user terminal. [Figure 6] It is a block diagram showing a processing unit of a CPU of an image management server. [Figure 7] It is a diagram showing an event information acquisition request and event information corresponding to the event information acquisition request. [Figure 8] It is a block diagram showing a processing unit of a CPU of a user terminal. [Figure 9] It is a diagram showing an image list screen displayed when an image viewing AP is activated. [Figure 10] It is a diagram showing an image list screen displayed when an icon is selected. [Figure 11] It is a diagram showing a first registration screen. [Figure 12] It is a diagram showing an image list screen including simple event information of a registered event. [Figure 13] It is a diagram showing an image list screen on which an image taken by the user in a registered event experienced by the user is displayed. [Figure 14] It is a diagram showing a second registration screen and an image display screen. [Figure 15] It is a flowchart showing a processing procedure of a user terminal. [Figure 16] It is a diagram showing another example of an image list screen. [Figure 17] It is a diagram showing a mode of selecting a recommended event based on an image analysis result of an image owned by a user. [Figure 18] It is a diagram showing another example of a mode of selecting a recommended event based on an image analysis result of an image owned by a user. [Figure 19] It is a diagram showing yet another example of an image list screen. [Figure 20] It is a diagram showing a mode of using an image taken by a user in the past as a future event image.

Mode for Carrying Out the Invention

[0018] As an example, as shown in Figure 1, the image management system 2 comprises an image management server 10 and multiple user terminals 11. The image management server 10 and the user terminals 11 are connected to each other via a network 12, enabling mutual communication. The network 12 is a Wide Area Network (WAN), such as the Internet or a public telecommunications network.

[0019] The image management server 10 is, for example, a server computer, a workstation, etc. The user terminal 11 is a terminal owned by each user 13 and is an example of an "information processing device" related to the technology of this disclosure. The user terminal 11 has at least the function of playing back and displaying an image 22 (see Figure 2, etc.) and the function of transmitting the image 22 to the image management server 10. The user terminal 11 is, for example, a smartphone, a tablet terminal, and a personal computer, etc.

[0020] As an example, as shown in Figure 2, the image management server 10 is connected to an image database (hereinafter abbreviated as DB (Data Base)) server 20 and an event information DB server 21 via a network such as a LAN (Local Area Network) (not shown). The image management server 10 transmits images 22 from user terminals 11 to the image DB server 20. The image DB server 20 has an image DB 23. The image DB server 20 stores and manages the images 22 from the image management server 10 in the image DB 23. In addition, the image DB server 20 transmits the images 22 stored in the image DB 23 to the image management server 10 in response to a request from the image management server 10.

[0021] The event information DB server 21 has an event information DB 24. The event information DB 24 stores event information 25. Event information 25 is information about future events related to user 13. Here, events include places that user 13 will visit, such as tourist spots, theme parks, historical sites, art museums, and museums, as well as programs that user 13 will participate in, such as agricultural experiences, craft experiences, and lifelong learning experiences. In addition, events may also include concerts, soccer matches, exhibitions, or online seminars. Event information 25 is registered in advance by the person in charge of the location if the event is a location, or by the organizer of the program if the event is a program.

[0022] The image management server 10 receives an event information distribution request 26 from the user terminal 11. The image management server 10 requests the event information DB server 21 to send event information 25 corresponding to the event information distribution request 26. The event information DB server 21 searches the event information DB 24 for event information 25 corresponding to the request from the image management server 10 and sends the retrieved event information 25 to the image management server 10. The image management server 10 distributes the event information 25 from the event information DB server 21 to the user terminal 11 that sent the event information distribution request 26.

[0023] As an example, as shown in Figure 3, the image DB23 has multiple image folders 30. Each image folder 30 is assigned to each user 13, making it a unique folder for each user 13. Therefore, there are as many image folders 30 as there are users 13. Each image folder 30 is associated with a user ID (Identification Data) such as [U0001], [U0002], etc., to uniquely identify the user 13.

[0024] The image folder 30 stores the images 22 owned by user 13. The images 22 owned by user 13 include images taken by user 13 using the camera function of user terminal 11. In addition, the images 22 owned by user 13 also include images taken using digital cameras other than user terminal 11. Furthermore, the images 22 owned by user 13 also include images received by user 13 from other users 13 such as friends and family, images downloaded by user 13 from the internet, and images scanned by user 13. The images 22 in the image folder 30 are periodically synchronized with the images 22 stored locally on user terminal 11.

[0025] The image folder 30 is associated with user 13's attribute information 31. Attribute information 31 is registered by user 13. Attribute information 31 includes user 13's date of birth, gender, residential area, and family structure, etc. The residential area is a combination of prefecture and city / ward / town / village.

[0026] As an example, as shown in Figure 4, the event information DB24 is divided into multiple categories 35, and multiple event information entries 25 are stored in each category 35. Category 35 is a broad classification of events such as "Agricultural Experiences" and "Theme Parks / Parks." In addition to these, Category 35 also includes "Shrines and Temples," "Ancient Tombs," "Hot Springs / Spas," "Art Museums / Museums," "Craft Experiences," and "Lifelong Learning Experiences."

[0027] Event information 25 includes basic information 36, future event images 37, ranking information 38, and registered user information 39, etc. Basic information 36 includes name, rating value, total number of reviews, location, and recommended time of year. The name is the name of the location if the event is a place, or the name of the program if the event is a program. The rating value is a numerical value entered by users 13 who have experienced the event through the user terminal 11, and is expressed, for example, on a 5-point scale. The total number of reviews is the total number of reviews entered by users 13 who have experienced the event through the user terminal 11. The location is the address of the location if the event is a place, or the address of the location where the program is held if the event is a program. The recommended time of year is the time when the event is especially recommended, such as winter, summer, Christmas, New Year's, or October.

[0028] Future event image 37 is an image that succinctly represents the content of the event. Multiple future event images 37 are registered. Future event image 37 is an image taken by the person in charge of the event or the organizer. Alternatively, future event image 37 may be an image taken by a user 13 who has experienced the event using the camera function of the user terminal 11. In this case, a so-called "Like Button" is used to vote for support for each image, and the image with the relatively most support is adopted as future event image 37.

[0029] Thus, future event image 37 is an image taken in the past. The "future" in future event image 37 does not mean an image to be taken in the future, but rather an image of an event that user 13 will likely experience in the future.

[0030] Ranking information 38 includes overall rankings, prefecture-specific rankings, category-specific rankings, user attribute-specific rankings, and seasonal rankings. These rankings are determined based on the number of times users have registered the event as an event to attend. Attribute-specific rankings include rankings related to user age, gender, and family structure, such as "Ranking for men in their 30s with families." Attribute-specific rankings also include rankings related to user residential area, such as "Ranking for residents of Kanagawa Prefecture." Seasonal rankings include rankings related to each season, such as "Winter Ranking."

[0031] The registered user information 39 stores the user ID of user 13 who registered the event as an event, such as "U0001-2021.01.17", and the date on which user 13 is scheduled to attend the event. If user 13 cancels the event, or if the scheduled date has passed, the user ID and scheduled date pair are deleted from the registered user information 39.

[0032] As an example, as shown in Figure 5, the computers comprising the image management server 10 and the user terminal 11 have basically the same configuration and include storage 40, memory 41, CPU (Central Processing Unit) 42, communication unit 43, display 44, and input device 45. These are interconnected via a bus line 46.

[0033] Storage 40 is a hard disk drive built into the computers constituting the image management server 10 and user terminals 11, or connected via cables or a network. Alternatively, storage 40 is a disk array consisting of multiple hard disk drives installed in series. Storage 40 stores control programs such as the operating system, various application programs (hereinafter abbreviated as AP (Application Program)), and various data associated with these programs. A solid-state drive may be used instead of a hard disk drive.

[0034] Memory 41 is work memory for the CPU 42 to execute processing. The CPU 42 loads programs stored in storage 40 into memory 41 and executes processing according to the programs. In this way, the CPU 42 comprehensively controls each part of the computer. CPU 42 is an example of a "processor" related to the technology of this disclosure. Note that memory 41 may be built into the CPU 42.

[0035] The communication unit 43 is a network interface that controls the transmission of various types of information via the network 12, etc. The display 44 displays various screens. These screens are equipped with GUI (Graphical User Interface) operation functions. The computers constituting the image management server 10 and the user terminal 11 receive operation instructions from the input devices 45 through the various screens. The input devices 45 include keyboards, mice, and touch panels.

[0036] In the following explanation, each component of the computer constituting the image management server 10 will be denoted by the subscript "A," and each component of the computer constituting the user terminal 11 will be denoted by the subscript "B" to distinguish them.

[0037] As an example, as shown in Figure 6, the image management server 10's storage 40A stores an operation program 50. When the operation program 50 is started, the image management server 10's CPU 42A works in cooperation with the memory 41 and other components to function as a request reception unit 55, an attribute information acquisition unit 56, an event information acquisition unit 57, and a distribution control unit 58.

[0038] The request receiving unit 55 receives various requests from the user terminal 11. For example, the request receiving unit 55 receives an event information distribution request 26. The event information distribution request 26 includes a user ID and a terminal ID. The terminal ID is the ID of the user terminal 11 that sent the event information distribution request 26. The request receiving unit 55 outputs the user ID from the event information distribution request 26 to the attribute information acquisition unit 56 and the event information acquisition unit 57. The request receiving unit 55 also outputs the terminal ID from the event information distribution request 26 to the distribution control unit 58.

[0039] When the user ID for the event information distribution request 26 is entered from the request reception unit 55, the attribute information acquisition unit 56 sends an attribute information acquisition request 60 to the image DB server 20. The attribute information acquisition request 60 is a copy of the user ID from the event information distribution request 26 and requests the attribute information 31 of user 13 associated with that user ID.

[0040] The image database server 20 reads attribute information 31 from the image database 23 in response to the attribute information acquisition request 60 and sends the read attribute information 31 to the image management server 10. The attribute information acquisition unit 56 acquires the attribute information 31 sent from the image database server 20 in response to the attribute information acquisition request 60. The attribute information acquisition unit 56 outputs the acquired attribute information 31 to the event information acquisition unit 57.

[0041] The event information acquisition unit 57 sends an event information acquisition request 61 to the event information DB server 21 requesting event information 25 corresponding to the user ID of the event information distribution request 26 from the request reception unit 55 and the attribute information 31 from the attribute information acquisition unit 56. The event information DB server 21 reads the event information 25 requested in the event information acquisition request 61 from the event information DB 24 and sends the read event information 25 to the image management server 10. The event information acquisition unit 57 acquires the event information 25 sent from the event information DB server 21. The event information acquisition unit 57 outputs the acquired event information 25 to the distribution control unit 58.

[0042] The distribution control unit 58 controls the distribution of event information 25 from the event information acquisition unit 57 to the user terminal 11 that sent the event information distribution request 26. At this time, the distribution control unit 58 identifies the user terminal 11 that sent the event information distribution request 26 based on the terminal ID of the event information distribution request 26 from the request reception unit 55.

[0043] As an example, as shown in Figure 7, the event information acquisition request 61 includes a user ID. If the user ID of the event information acquisition request 61 matches the event information 25 registered in the registered user information 39 and is found in the event information DB 24, the event information DB server 21 reads the event information 25 from the event information DB 24 as registered event information 25A. Registered event information 25A means information about a registered event that user 13 has registered as an event. Hereafter, the future event image 37 registered in registered event information 25A will be referred to as registered event image 37A.

[0044] Furthermore, the event information acquisition request 61 includes ranking conditions 65. Ranking conditions 65 are set based on attribute information 31 and the time period. Specifically, ranking conditions 65 are conditions for ranking related to the user 13's age, gender, and family structure, conditions for ranking related to the user 13's residential area, and conditions for ranking related to the time period, all of which can be determined from attribute information 31. In Figure 7, "Top 3 in the ranking for males in their 30s with families" is shown as an example of ranking conditions 65 for the user 13's age, gender, and family structure. Also, "Top 3 in the ranking for residents of Kanagawa Prefecture" is shown as an example of ranking conditions 65 for the user 13's residential area. Furthermore, "Top 3 in the winter ranking" is shown as an example of ranking conditions 65 for the time period.

[0045] The event information DB server 21 reads event information 25 that has ranking information 38 that satisfies each of the ranking conditions 65 from the event information DB 24 as recommended event information 25B. Recommended event information 25B means information about recommended events that recommend the event in question to user 13. Hereafter, the future event image 37 registered in recommended event information 25B will be referred to as recommended event image 37B.

[0046] Recommended event information 25B that satisfies ranking criteria 65 for user 13's age, gender, and family structure is information about events selected based on user 13's attributes. Similarly, recommended event information 25B that satisfies ranking criteria 65 for user 13's residential area is information about events selected based on user 13's attributes. Therefore, recommended events include events selected based on user 13's attributes.

[0047] Thus, the event information 25 acquired by the event information acquisition unit 57 and distributed to the user terminal 11 by the distribution control unit 58 includes at least recommended event information 25B. Registered event information 25A may or may not be included in the event information 25 distributed to the user terminal 11. In other words, if user 13 has not registered any events as scheduled, and there is no event information 25 registered in the registered user information 39 in the event information DB 24 for a user ID that matches the user ID of the event information acquisition request 61, then registered event information 25A will not be included in the event information 25 distributed to the user terminal 11.

[0048] As an example, as shown in Figure 8, the storage 40B of the user terminal 11 stores the image viewing AP 70. The image viewing AP 70 is an application that causes the computer constituting the user terminal 11 to function as an "information processing device" according to the technology of this disclosure. In other words, the image viewing AP 70 is an example of an "operating program for an information processing device" according to the technology of this disclosure. The CPU 42B of the user terminal 11 works in cooperation with the memory 41, etc., to function as a browser control unit 75. The browser control unit 75 controls the operation of a web browser dedicated to the image viewing AP 70.

[0049] The browser control unit 75 includes an instruction receiving unit 77, a request transmission unit 78, a screen generation unit 79, and a screen output unit 80. The instruction receiving unit 77 receives various operation instructions input by the user 13 from the input device 45B through various screens. The request transmission unit 78 sends various requests to the image management server 10 in accordance with the operation instructions. For example, the request transmission unit 78 sends an event information distribution request 26 to the image management server 10 in conjunction with the instruction to start the image viewing AP 70.

[0050] The screen generation unit 79 generates various screens, such as the image list screen 90A (see Figure 9), based on images 22 (not shown) stored locally in the storage 40B and event information 25 from the image management server 10. The screen generation unit 79 outputs the screen data of the generated screens to the screen output unit 80. The screen output unit 80 displays the various screens on the display 44B based on the screen data of the screens from the screen generation unit 79.

[0051] Figure 9 shows an example of the image list screen 90A that is displayed when the image viewing AP70 is launched. The image list screen 90A has, from top to bottom, a set image display area 91, a menu button display area 92, a future event display area 93, and a past image display area 94.

[0052] The image display area 91 displays multiple images 22 from relatively distant past years and months, randomly selected according to a pre-set layout. The images 22 within the image display area 91 are selectable. When an image 22 is selected within the image display area 91, a screen is displayed in which each image 22 is enlarged and can be viewed back and forth. This image display area 91 allows the user 13 to look back on memories from the relatively distant past. Figure 9 shows an example where one of four images 22 from October 2014 is displayed enlarged on the left, and the other three are displayed vertically in parallel on the right.

[0053] Here, "forwarding" in "each image 22 can be forwarded and backwarded" refers to the display of an enlarged image 22 sequentially, with the acquisition date and time being updated in order, for example, by swiping left. Similarly, "backwarding" in "each image 22 can be forwarded and backwarded" refers to the display of an enlarged image 22 sequentially, with the acquisition date and time being updated in order, for example, by swiping right. The same applies to "forwarding and backwarding" in the following explanation. To return to the image list screen 90A from the screen where the images 22 in the composite image display area 91 are enlarged, for example, by selecting the close button provided on the screen where the images 22 in the composite image display area 91 are enlarged. The acquisition date and time is one of the following: the date and time when the image 22 was taken, the date and time when the image 22 was downloaded, or the date and time when the image 22 was scanned.

[0054] The menu button display area 92 is located approximately in the center of the image list screen 90A, separating the upper image set display area 91 from the lower future event display area 93 and past image display area 94. A menu button 95 is displayed in the left corner of the menu button display area 92. When the menu button 95 is selected, various menus are displayed as pop-ups on the image list screen 90A, making them selectable.

[0055] In the future event display area 93, an icon 96 is available for selection. The icon 96 displays a representative image 37R of the future event image 37 registered in the event information 25 sent from the image management server 10. The representative image 37R includes the registered event image 37A and / or the recommended event image 37B.

[0056] In the past image display area 94, past images 22 are arranged chronologically following frame 97, which represents the current year and month. More specifically, as indicated by the dashed-dotted arrow 98, the images 22 are arranged from bottom to top and right to left, in chronological order from oldest to newest acquisition date and time. In other words, the chronological order of the images 22 as a whole is from bottom to top. However, when viewed as a single row containing multiple images 22 (in this case, three frames of images 22) with different acquisition dates and times, the chronological order of the images 22 is from right to left. Therefore, the image 22 placed next to frame 97 is the most recent image 22N among the past images 22. The images 22 in the past image display area 94 are selectable. When an image 22 in the past image display area 94 is selected, a screen is displayed with each image 22 enlarged and viewable in reverse order, similar to the case of the composite image display area 91.

[0057] Furthermore, it is possible to display even older images 22 in the past image display area 94 by swiping. For example, if you swipe the past image display area 94 from bottom to top, older images 22 will be displayed in the past image display area 94 in chronological order of acquisition date and time. In this case, the icon 96 remains displayed, and the frame 97 representing the current year and month displays the year and month to which the acquisition date and time of the image 22 displayed in the past image display area 94 belongs, or more specifically, the year and month of acquisition of the latest image 22N among the multiple images 22 displayed in the past image display area 94. Alternatively, when a swipe operation is performed on the past image display area 94, the icon 96 and / or the frame 97 representing the current year and month may disappear. Then, past images 22 may be placed in the position of the icon 96 and / or the frame 97 representing the current year and month.

[0058] The future event display area 93, where icon 96 is placed, is located to the left of the latest image 22N, separated by frame 97, in the first row of the past image display area 94 where the latest image 22N is placed. As mentioned above, the chronological order of images 22 when viewed as a single row is from right to left. In other words, the future event display area 93 is an example of a "future area" related to the technology of this disclosure.

[0059] If icon 96 is selected, the system transitions to the image list screen 90B shown in Figure 10 as an example. In Figure 10, the image list screen 90B is a screen in which the image set display area 91 and the menu button display area 92 are removed, and the image set display area 91 and the menu button display area 92 are entirely replaced by the future event display area 93. In the image list screen 90B, the representative image 37R within icon 96 is grayed out. Note that the image set display area 91, the menu button display area 92, and even icon 96 do not necessarily have to be present from the beginning, and the image list screen 90B in Figure 10 may be displayed when the image viewing AP 70 is launched.

[0060] Here, one 1 / 4 frame with the word "FUTURE" and three 1 / 4 frames with the representative image 37R of the future event image 37 are combined to form icon 96, and icon 96 is selected as the target, but this is not limited to this. The 1 / 4 frame with the word "FUTURE" and the 1 / 4 frame with the representative image 37R of the future event image 37 may be displayed as selectable options separately. In this case, if the 1 / 4 frame with the word "FUTURE" is selected on the image list screen 90A, the user will transition to the image list screen 90B. Also, if the 1 / 4 frame with the representative image 37R of the future event image 37 is selected on the image list screen 90A, the user will transition to the first registration screen 105 (see Figure 11), which will be described later, without going through the image list screen 90B.

[0061] In the future event display area 93, in addition to the icon 96, multiple simplified event information 100 are displayed side by side. The simplified event information 100 can be scrolled up and down. The simplified event information 100 is information that simply shows the event information 25 from the image management server 10. The simplified event information 100 includes the name of the event, the type of event (registered event or recommended event), a star rating and a numerical value representing the evaluation value, and a future event image 37. The image list screen 90B, in which the simplified event information 100 including the future event image 37 are arranged, is an example of a "future event image list screen" relating to the technology of this disclosure.

[0062] Although the multiple future event images 37 of the simplified event information 100 are arranged in rows, they are not arranged in order of acquisition date and time like the past images 22. For this reason, the multiple future event images 37 of the simplified event information 100 are treated the same as a single frame of image 22. Furthermore, the future event display area 93, which replaces the composite image display area 91 and the menu button display area 92, is located above the latest image 22N. As mentioned above, the chronological order of images 22 as a whole is from bottom to top. In other words, the future event display area 93, which replaces the composite image display area 91 and the menu button display area 92, is also an example of a "future area" related to the technology of this disclosure.

[0063] The simplified event information 100 is arranged in order of the event's arrival date. More specifically, as shown by the dashed-dotted arrow 101 following the dashed-dotted arrow 98, the simplified event information 100 is arranged from bottom to top, from the closest to the furthest arrival date. As mentioned above, the simplified event information 100 includes the future event image 37, so arranging the simplified event information 100 in order of the event's arrival date also arranges the future event image 37 in order of the event's arrival date. The arrival date is the scheduled date of the registered event if the event represented by the simplified event information 100 is a registered event. If the event represented by the simplified event information 100 is a recommended event, the arrival date is the recommended date registered in the basic information 36. Figure 10 shows an example where the simplified event information 100B (recommended event image 37B) for recommended events such as "Yamanakako Park" and "Echigozawa Ski Resort" are displayed side by side.

[0064] The simplified event information 100 is selectable. If the simplified event information 100B for recommended events is selected, the user will proceed to the first registration screen 105, as shown in Figure 11. In Figure 11, the first registration screen 105 displays each recommended event image 37B in an enlarged format, allowing for forward and backward viewing. The first registration screen 105 also displays detailed information 106, which is an appropriate excerpt of the basic information 36 and ranking information 38. Furthermore, the first registration screen 105 is provided with a new registration button 107.

[0065] If the New Registration button 107 is selected, a screen (not shown in the figure) for registering a recommended event, which has its detailed information 106 etc. displayed on the first registration screen 105, will be displayed as a new registered event. On this screen, it is possible to enter the scheduled date of the registered event using the date selection GUI. Figure 11 shows an example of the first registration screen 105 for registering a recommended event at "Yamanakako Park".

[0066] Figure 12 shows an example of the image list screen 90B, which includes the simplified event information 100A for registered events. The simplified event information 100A for registered events displays the scheduled date of the registered event. This display of the scheduled date of the registered event distinguishes it from the simplified event information 100B for recommended events, which displays the word "Recommended". Figure 12 shows an example where the simplified event information 100A for the registered event "Yamanakako Park" is displayed.

[0067] User 13 goes to the registration event location on the scheduled date and experiences the registration event. While experiencing the registration event, User 13 takes an image 22 using the camera function of the user terminal 11. The captured image 22 is displayed as a past image 22 in the past image display area 94 on the image list screens 90A and 90B.

[0068] Figure 13 shows an example of an image list screen 90A where images 22 taken by user 13 during registration events experienced by user 13 are displayed in the past image display area 94. A mark 110 is displayed on the most recent image 22NN among the images 22 taken by user 13 during registration events experienced by user 13. This mark 110 distinguishes between images 22 taken by the user during registration events experienced by the user and images 22 unrelated to the registration events. Alternatively, or in addition to the mark 110, images 22 taken by user 13 during registration events experienced by user 13 may be distinguished from images 22 unrelated to the registration events by surrounding them with a colored frame.

[0069] If mark 110 is selected, the user transitions to the second registration screen 115, shown in the center of Figure 14 as an example. On the second registration screen 115, each registration event image 37A of the registration events experienced by user 13 is displayed in an enlarged format, allowing for forward and backward viewing. The second registration screen 115 also displays detailed information 106 of the registration events experienced by user 13. Furthermore, the second registration screen 115 is equipped with a re-registration button 116 and a "recommend to others" button 117 instead of a new registration button 107.

[0070] If the re-registration button 116 is selected, a screen (not shown in the illustration) is displayed on the second registration screen 115, where detailed information 106, etc., is displayed, allowing the user 13 to register the registration event again as a registration event. On this screen, the scheduled date of the registration event can be entered using the date selection GUI.

[0071] Furthermore, if the "Recommend to others" button 117 is selected, a transfer settings screen (not shown) is displayed. On the transfer settings screen, acquaintances of user 13 who have been previously set as phone contacts, etc., are displayed for selection. The browser control unit 75 transfers the registration event information 25A of the registration event experienced by user 13, for which detailed information 106, etc., is displayed on the second registration screen 115, to the user terminal 11 of the acquaintance of user 13 selected on the transfer settings screen. An acquaintance of user 13 may be, for example, user 13's family, relatives, lover, friend, or colleague. The second registration screen 115 is an example of a "registration screen" relating to the technology of this disclosure. The re-registration button 116 is an example of a "button for re-registering a registration event as a scheduled event" relating to the technology of this disclosure. Furthermore, the "Recommend to others" button 117 is an example of a "button for recommending a registration event to the user's acquaintances" relating to the technology of this disclosure.

[0072] Furthermore, if an image 22 (image 22NN with mark 110 displayed) taken by user 13 during a registration event experienced by user 13 is selected on the image list screen 90A or 90B, the user transitions to the image display screen 120, as shown on the right side of Figure 14, as an example. The selected image 22NN is displayed enlarged on the image display screen 120. The image display screen 120 also displays the tags 121 attached to image 22NN. The tags 121 include words representing the year and month the image 22NN was taken ("2021" and "January"), words representing the location where it was taken ("Japan", "Yamanashi", and "Lake Yamanaka"), and words representing the subjects in the image 22NN ("Mt. Fuji", "Sunrise", and "Morning Sun"). The tags 121 representing the year and month the image was taken are extracted from the date and time the image 22NN was taken. The tags 121 representing the location are extracted from the GPS (Global Positioning System) information of image 22NN. The tag 121, which represents the subject in image 22NN, is extracted by performing image analysis on image 22NN.

[0073] Furthermore, tag 121 includes the name of the registered event. The name of the registered event is extracted by comparing the scheduled date of the registered event with the date and time the image 22NN was taken, and by referring to the GPS information of the image 22NN. A link 122 is attached to tag 121 of the name of the registered event, as indicated by the hatching. When tag 121 (link 122) of the name of the registered event is selected, the user transitions to a second registration screen 115 where the registered event image 37A, etc., of the registered event experienced by user 13 is displayed. In other words, link 122 is an example of a "link for accessing the registered event image of a registered event experienced by the user" related to the technology of this disclosure. Thus, the second registration screen 115 is displayed not only when mark 110 is selected, but also when tag 121 (link 122) of the name of the registered event is selected.

[0074] Next, the operation of the above configuration will be explained with reference to the flowchart shown in Figure 15 as an example. The CPU 42A of the image management server 10 functions as a request reception unit 55, an attribute information acquisition unit 56, an event information acquisition unit 57, and a distribution control unit 58, as shown in Figure 6. The CPU 42B of the user terminal 11 functions as a browser control unit 75, as shown in Figure 8. The browser control unit 75 is composed of an instruction reception unit 77, a request transmission unit 78, a screen generation unit 79, and a screen output unit 80.

[0075] When the instruction to start the image viewing AP70 is received by the instruction receiving unit 77 (YES in step ST100), the request sending unit 78 sends an event information distribution request 26 to the image management server 10 (step ST110).

[0076] Upon receiving the event information distribution request 26, the image management server 10 acquires event information 25 corresponding to the event information distribution request 26 via the event information acquisition unit 57, as shown in Figures 6 and 7. The event information 25 includes registered event information 25A of registered events registered by user 13 as scheduled events, and / or recommended event information 25B of recommended events recommended to user 13. The recommended events include events selected based on user 13's attributes.

[0077] Event information 25 is output from the event information acquisition unit 57 to the distribution control unit 58. The distribution control unit 58 then distributes the event information 25 to the user terminal 11 that sent the event information distribution request 26.

[0078] On the user terminal 11, event information 25 distributed from the distribution control unit 58 of the image management server 10 is received by the screen generation unit 79 (step ST120). The screen generation unit 79 generates the image list screen 90A shown in Figure 9, etc. At this time, the screen generation unit 79 places an icon 96 displaying the representative image 37R of the future event image 37 in the future event display area 93, which is a future area in the chronological order of the past images 22, compared to the latest image 22N (step ST130).

[0079] The screen data for the image list screen 90A is output from the screen generation unit 79 to the screen output unit 80. Then, the screen output unit 80 displays the image list screen 90A on the display 44B based on the screen data of the image list screen 90A (step ST140).

[0080] If icon 96 is selected on the image list screen 90A (YES in step ST150), the screen generation unit 79 generates an image list screen 90B that includes the simplified event information 100 shown in Figure 10, etc. At this time, the screen generation unit 79 arranges the simplified event information 100, and by extension the future event images 37, in order of the arrival time of the events (step ST160).

[0081] The screen data for the image list screen 90B is output from the screen generation unit 79 to the screen output unit 80. Then, the screen output unit 80 displays the image list screen 90B on the display 44B based on the screen data of the image list screen 90B (step ST170).

[0082] As described above, the CPU 42B of the user terminal 11 includes a screen generation unit 79 and a screen output unit 80. The screen generation unit 79 generates image list screens 90A and 90B in which the images 22 owned by the user 13 are arranged in chronological order. At that time, the screen generation unit 79 places a future event image 37, which is an image of a future event related to the user 13, in a future event display area 93, which is a future area in the chronological order of the images 22, compared to the latest image 22N among the images 22. The screen output unit 80 outputs the image list screens 90A and 90B to the display 44B.

[0083] The arrangement of past images 22 and future event images 37 naturally represents a timeline that flows from the past to the present and into the future. As a result, user 13 can contemplate future events without interrupting their thoughts, as an extension of their reflection on past memories through past images 22. Furthermore, user 13 can make their thoughts about future events more concrete through future event images 37, such as where to go next or what kind of photos to take there. Thus, user 13 can reflect on past memories while more concretely contemplating future events. Since it is expected that user 13 will actively participate in future events and take many photos, the significance of the image management server 10 can be increased.

[0084] The screen generation unit 79 selectably places an icon 96 displaying a future event image 37 (representative image 37R) in the future event display area 93. When the icon 96 is selected, it generates an image list screen 90B in which the future event images 37 are arranged. The screen output unit 80 outputs the image list screen 90B to the display 44B. Therefore, the image list screen 90A, which is displayed before the icon 96 is selected, fully fulfills its original purpose of allowing users to view past images 22.

[0085] User 13 can learn an overview of the future event image 37 through icon 96. Furthermore, user 13 can learn the full details of the future event image 37 through the image list screen 90B. By gradually increasing the display format from an overview to the full details, user 13's anticipation for the future event can be steadily built.

[0086] The screen generation unit 79 arranges the future event images 37 in the image list screen 90B in order of the event's arrival date. This allows for a clearer representation of the timeline from the past to the present and into the future. The user 13 can more seamlessly connect reminiscing about past memories through past images 22 with contemplating future events.

[0087] The future event image 37 is at least one of the following: a registered event image 37A relating to a registered event that user 13 has registered as a scheduled event, and a recommended event image 37B relating to a recommended event that is recommended to user 13. The registered event image 37A serves as a reference for photos that user 13 will take at the registered event. The recommended event image 37B helps user 13 to intuitively visualize the recommended event.

[0088] The screen generation unit 79 displays a mark 110 on the image 22 (22NN) taken by user 13 at a registration event experienced by user 13, thereby distinguishing it from images 22 unrelated to the registration event. This allows user 13 to easily identify the image 22 taken by user 13 at a registration event they experienced. This makes it easy for user 13 to recall enjoyable memories of the registration event, increasing their motivation to attend the event again. As a result, this leads to an increase in the frequency of use of the image viewing AP 70.

[0089] The screen generation unit 79 generates an image display screen 120 that includes the selected image 22 and a link 122 to access the registration event image 37A of the registration event experienced by user 13, when the image 22 (22NN) taken by user 13 during a registration event experienced by user 13 is selected. The screen output unit 80 outputs the image display screen 120 to the display 44B. As a result, user 13 can easily access the registration event image 37A of the registration event while viewing the image 22 taken by user 13 during a registration event experienced by user 13.

[0090] The screen generation unit 79 generates a second registration screen 115 that includes a registration event image 37A of the registered event experienced by the user, a re-registration button 116, and a button 117 to recommend to others. The screen output unit 80 outputs the second registration screen 115 to the display 44B. As a result, the user 13 can easily re-register events they like and recommend events they like to their acquaintances. If a business model is considered in which compensation is obtained by having the user 13 register events, this can contribute to increased sales.

[0091] The second registration screen 115 can be displayed even while a registration event is in progress. The registration event image 37A is displayed on the second registration screen 115. Therefore, if the second registration screen 115 is displayed while a registration event is in progress, the registration event image 37A can be used to check for things like forgetting to take photos.

[0092] Recommended events include those selected based on the user's attributes. Therefore, compared to recommending events that have no connection to the user, this increases the likelihood that the user will register the recommended events in their schedule. In a business model where revenue is generated by users registering events, this can contribute to increased sales.

[0093] Note that in the image list screen 90B after icon 96 is selected, the combined image display area 91 and the menu button display area 92 are removed, while the past image display area 94 remains, but this is not limited to this. For example, as shown in the image list screen 90C in Figure 16, the past image display area 94 may also be removed and replaced with the future event display area 93. Figure 16 shows an example where, in addition to "Yamanakako Park" and "Echigozawa Ski Resort" shown in Figure 10, simplified event information 100B (recommended event image 37B) for "Sarugasawa Onsen" is displayed.

[0094] As an example, the configurations shown in Figures 17 and 18 may be adopted. That is, the CPU 42A of the image management server 10 performs image analysis on the images 22 owned by user 13 stored in the image folder 30, and selects recommended events based on the results of this image analysis.

[0095] Figure 17 shows an example where, if image analysis results indicate that user 13 likes flowers, such as a relatively large number of images 22 containing flowers, a flower viewing spot is selected as the recommended event information 25B. Figure 18 shows an example where, if image analysis results indicate that user 13 likes the outdoors and food, such as a relatively large number of images 22 containing outdoors and food, a fishing pond and a vegetable harvesting experience are selected as the recommended event information 25B. In this way, events that match user 13's preferences can be recommended. It should be noted that in the embodiments shown in Figures 17 and 18, the image analysis results obtained are attributes related to user 13's preferences, such as liking flowers and food. Therefore, the selection of recommended events remains based on user 13's attributes.

[0096] Recommended events are not required. For example, user 13 may search for a desired event information 25 in the event information DB 24 and register the event of the found event information 25 as an event. In this case, as shown in Figure 19 as an example, the simplified event information 100B (recommended event image 37B) of the recommended event will not be displayed on the image list screen 90B, and only the simplified event information 100A (registered event image 37A) of the registered event will be displayed.

[0097] The image viewing AP70 may be linked with a general-purpose scheduler AP. That is, events registered as scheduled by user 13 in the scheduler AP may be notified to the image viewing AP70 as registered events.

[0098] The future event image 37 is not limited to images taken by the person in charge or organizer of the event, or images taken by other users 13 who have experienced the event. The future event image 37 can be searched for from images on the internet using the event name or other keywords as search terms. Also, as shown in Figure 20 as an example, the user 13 who registered the event may select an image 22 that they took in the past and use it as the future event image 37 (registered event image 37A). Furthermore, the user 13 who registered the event may select an image from images on the internet and use it as the future event image 37.

[0099] In the above embodiment, an example was shown in which an event information distribution request 26 is sent from the user terminal 11 to the image management server 10 in conjunction with the startup command of the image viewing AP 70, but the embodiment is not limited to this. The event information distribution request 26 may also be sent from the user terminal 11 to the image management server 10 at a predetermined time. Examples of predetermined times include 8:00 PM on Thursday or Friday nights close to a holiday, or conversely, 8:00 PM on Monday nights after a holiday, or the beginning or end of the month.

[0100] When the recommended event information 25B distributed from the image management server 10 is received, the user terminal 11 may be configured to display a notification message indicating that the recommended event information 25B has been received on its home screen. The notification message may also include the recommended event image 37B. Furthermore, when the notification message is selected and opened, the first registration screen 105 may be immediately displayed on the display 44B without displaying the image list screen 90A, etc.

[0101] A frame 97 representing the current year and month is placed between the latest image 22N from the past images 22 and the icon 96, but frame 97 is optional. The latest image 22N may be placed in the position of frame 97. Alternatively, the latest image 22N may be displayed as a watermark behind frame 97.

[0102] The first registration screen 105 and the second registration screen 115 may have a "favorite" button. Furthermore, events for which the "favorite" button has been selected may be displayed together on a favorite events list screen, allowing the user 13 to view them all together later.

[0103] A button with the same function as the "Recommend to Others" button 117 on the second registration screen 115 may also be provided on the first registration screen 105. This would allow user 13 to share information about recommended events with their acquaintances, and to decide whether or not to register the recommended event as a new event in their schedule while also considering the opinions of their acquaintances.

[0104] Recommended events may be selected for each itinerary, such as day trips, overnight stays, or trips of two nights or more, and simplified event information 100B for each recommended event may be displayed on the image list screen 90B. Alternatively, recommended events may be selected based on evaluation values ​​and / or total number of reviews, such as evaluation values ​​being above a threshold or total number of reviews being above a threshold. Furthermore, recommended events may be selected randomly, completely unrelated to the user's attributes, evaluation values, and total number of reviews. By presenting unexpected recommended events, it is possible to pique the interest of users 13 who are tired of similar events.

[0105] Although the screens illustrated in the above embodiment are all portrait-oriented, they may of course be landscape-oriented. The operators of the image management server 10 and the image DB server 20 may be the same as, or different from, the operators of the event information DB server 21. In order to learn more about the user 13's attributes, the user 13 may be asked to answer questionnaires about places they frequently visit, things they are recently interested in, hobbies and preferences, etc.

[0106] The image management server 10 may be configured to handle some or all of the functions of the processing units of the user terminal 11, and the image management server 10 may function as an information processing device related to the technology of this disclosure. Specifically, the image management server 10 generates various screens such as the image list screen 90A and outputs them to the user terminal 11 in the form of web-distributed screen data created using a markup language such as XML (Extensible Markup Language). In this case, the browser control unit 75 of the user terminal 11 reproduces the various screens to be displayed on the web browser based on the screen data and displays them on the display 44B. Note that other data description languages ​​such as JSON (Javascript® Object Notation) may be used instead of XML.

[0107] The user terminal 11 that sends the image 22 to the image management server 10 and the user terminal 11 that receives the event information 25 from the image management server 10 may be different. For example, if there are multiple user terminals 11 with the same user 13 account, the image 22 may be sent from one of them to the image management server 10, and the event information 25 may be distributed from the image management server 10 to another of them.

[0108] The hardware configuration of the computers constituting the image management server 10 can be modified in various ways. For example, the image management server 10 can be configured with multiple computers separated as hardware, in order to improve processing power and reliability. For example, the functions of the request reception unit 55 and the attribute information acquisition unit 56, and the functions of the event information acquisition unit 57 and the distribution control unit 58 can be distributed among two computers. In this case, the image management server 10 is configured with two computers. Alternatively, the image management server 10, the image DB server 20, and the event information DB server 21 may be integrated into a single server.

[0109] Thus, the hardware configuration of the computer for the image management server 10 can be appropriately changed according to the required performance, such as processing power, security, and reliability. Furthermore, not only the hardware, but also the operating program 50 and application programs such as the image viewing AP 70 can, of course, be duplicated or distributed and stored on multiple storage devices for the purpose of ensuring security and reliability.

[0110] In the above embodiment, for example, the hardware structure of the Processing Unit that executes various processes such as the request reception unit 55, attribute information acquisition unit 56, event information acquisition unit 57, distribution control unit 58, and browser control unit 75 (instruction reception unit 77, request transmission unit 78, screen generation unit 79, and screen output unit 80) can be the various processors shown below. The various processors include CPUs 42A and 42B, which are general-purpose processors that execute software (operation program 50 and image viewing AP 70) and function as various processing units, as well as programmable logic devices (PLDs) such as FPGAs (Field Programmable Gate Arrays) whose circuit configuration can be changed after manufacturing, and / or dedicated electrical circuits such as ASICs (Application Specific Integrated Circuits) which have a circuit configuration specifically designed to execute a particular process.

[0111] A single processing unit may consist of one of these various processors, or it may consist of a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, and / or a combination of a CPU and an FPGA). Alternatively, multiple processing units may be composed of a single processor.

[0112] Examples of configuring multiple processing units with a single processor include, firstly, a configuration where one or more CPUs and software combine to form a single processor, which then functions as multiple processing units, as exemplified by client and server computers. Secondly, a configuration using a processor that realizes the functions of the entire system, including multiple processing units, on a single IC (Integrated Circuit) chip, as exemplified by System-on-a-Chip (SoC). Thus, various processing units are configured, in terms of hardware structure, using one or more of the above-mentioned processors.

[0113] Furthermore, the hardware structure of these various processors can more specifically utilize electrical circuits (Circuitry) that combine circuit elements such as semiconductor elements.

[0114] The technology of this disclosure can be appropriately combined with the various embodiments and / or variations described above. Furthermore, it is understood that various configurations can be adopted without departing from the spirit of the invention, and the invention is not limited to the embodiments described above. Moreover, the technology of this disclosure extends not only to programs but also to storage media for storing programs non-temporarily.

[0115] The descriptions and illustrations presented above are detailed explanations of the technical aspects of this disclosure and are merely examples of the technical aspects. For example, the above descriptions of the structure, function, operation, and effect are examples of the structure, function, operation, and effect of the technical aspects of this disclosure. Therefore, it goes without saying that you may delete unnecessary parts, add new elements, or replace elements in the descriptions and illustrations presented above, as long as you do not deviate from the essence of the technical aspects of this disclosure. Furthermore, in order to avoid confusion and facilitate understanding of the technical aspects of this disclosure, explanations of common technical knowledge and the like that do not require special explanation to enable the implementation of the technical aspects of this disclosure have been omitted from the descriptions and illustrations presented above.

[0116] In this specification, "A and / or B" is synonymous with "at least one of A and B." That is, "A and / or B" means that it may be A alone, or B alone, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" applies when expressing three or more things linked by "and / or."

[0117] All documents, patent applications, and technical standards described herein are incorporated by reference to the same extent as if each individual document, patent application, and technical standard were specifically and individually noted to be incorporated by reference. [Explanation of Symbols]

[0118] 2 Image Management System 10 Image Management Server 11 User terminals 12 Networks 13 users 20 Image Database Server (Image DB Server) 21 Event Information Database Server (Event Information DB Server) 22 images 22N Latest Images The most recent image taken by a user during a registration event experienced by a 22NN user. 23 Image Database (Image DB) 24 Event Information Database (Event Information DB) 25 Event Information 25A Registered Event Information 25B Recommended Event Information 26 Event Information Distribution Request 30 Image Folders 31 Attribute information 35 categories 36 Basic information 37 Future Event Images 37A Registered Event Image 37B Recommended Event Images 37R Representative Image 38 Ranking Information 39. Registered User Information 40, 40A, 40B storage 41 memory 42, 42A, 42B CPUs 43 Communications Department 44, 44B displays 45, 45B Input Devices 46 Bus Line 50 Operating Programs 55 Request Reception Department 56 Attribute information acquisition section 57 Event Information Acquisition Department 58 Distribution Control Unit 60 Attribute information acquisition request 61 Event Information Retrieval Request 65 Ranking Conditions 70 Image Viewing Application Programs (Image Viewing APs) 75 Browser Control Unit 77 Instruction Reception Department 78 Request transmission unit 79 Screen generation section 80. Screen output section 90A, 90B, 90C Image List Screen 91 Image display area 92 Menu button display area 93 Future Event Display Area 94 Past image display area 95 Menu button 96 Icons 97 frames 98 Arrows indicating the chronological order of the images. 100 Simple Event Information 100A Registered Event - Simple Event Information 100B Recommended Events: Brief Event Information 101 Arrows indicating the order of simplified event information 105 First Registration Screen 106 Detailed Information 107 New Registration Button 110 Mark 115 Second Registration Screen 116 Re-registration button 117 Recommend to others button 120 Image display screen 121 tags 122 links ST100, ST110, ST120, ST130, ST140, ST150, ST160, ST170 Step

Claims

1. Processor and The processor comprises, The aforementioned processor, The system has a past image display area where past images owned by the user are arranged chronologically in order of acquisition date and time, and a future event display area, and the future event display area generates an image list screen where the image is located further in the chronological order than the latest image among the past images displayed in the past image display area. In the aforementioned future event display area, a recommended event image related to the recommended event that is recommended to the user is placed, The aforementioned recommended events are events selected based on the user's attributes and include events that meet the ranking criteria for rankings related to the user's age, gender, family structure, or residential area. Output the image list screen on which the recommended event images are placed. Information processing device.

2. The information processing apparatus according to claim 1, wherein the aforementioned past images include images unrelated to the recommended events.

3. The aforementioned processor, In the aforementioned future event display area, selectable icons including the recommended event image are placed. If the aforementioned icon is selected, a recommended event image list screen is generated, displaying the recommended event images in order. The information processing device according to claim 1 or claim 2, which outputs the generated recommended event image list screen.

4. The aforementioned processor, The information processing device according to claim 3, wherein the recommended event images on the recommended event image list screen are arranged in order of the arrival date of the recommended events.

5. The aforementioned processor, The information processing apparatus according to any one of claims 1 to 4, wherein, in addition to the recommended event image, the registered event image relating to the registered event registered by the user as a scheduled event is placed in the future event display area.

6. The aforementioned processor, The information processing apparatus according to claim 5, which displays, in the image list screen, images taken by the user during the registration event experienced by the user in a manner that can be distinguished from images unrelated to the registration event.

7. The aforementioned processor, In the image list screen, if an image taken by the user during the registration event experienced by the user is selected, an image display screen is generated that includes the selected image and a link to access the registration event image of the registration event experienced by the user. The information processing apparatus according to claim 6, which outputs the generated image display screen.

8. The aforementioned processor, A registration screen is generated that includes the registration event image of the registration event experienced by the user, a button to re-register the registration event as a scheduled event, and a button to recommend the registration event to the user's acquaintances. The information processing device according to any one of claims 5 to 7, which outputs the generated registration screen.

9. The system has a past image display area where past images owned by the user are arranged chronologically in order of acquisition date and time, and a future event display area, and the future event display area generates an image list screen where the image is located further in the chronological order than the latest image among the past images displayed in the past image display area. In the aforementioned future event display area, a recommended event image related to the recommended event recommended to the user is placed. Here, the recommended events are events selected based on the user's attributes and include events that meet the ranking criteria for rankings related to the user's age, gender, family structure, or residential area. Output the image list screen on which the recommended event images are placed. A method for operating an information processing device, including the device itself.

10. The system has a past image display area where past images owned by the user are arranged chronologically in order of acquisition date and time, and a future event display area, and the future event display area generates an image list screen where the image is located further in the chronological order than the latest image among the past images displayed in the past image display area. In the aforementioned future event display area, a recommended event image related to the recommended event recommended to the user is placed. Here, the recommended events are events selected based on the user's attributes and include events that meet the ranking criteria for rankings related to the user's age, gender, family structure, or residential area. Output the image list screen on which the recommended event images are placed. An operating program for an information processing device that causes a computer to perform a process that includes [specific details].

Images