Information processing device, information processing system, information processing method, and program

Abstract

The present invention achieves a configuration for providing a user with assist information for image capturing using a user terminal such as a smartphone. In this invention, an event information providing server provides a user terminal such as a smartphone with event information serving as assist information when a user captures an image, specifically, event information including imaging target information indicating a target to be imaged, imaging location information, imaging time information, and the like. A user capturing an image using the user terminal can capture an image without missing a photo opportunity by referring to the event information to obtain optimum information regarding the imaging target, the imaging location, and the imaging time.

Description

Information processing apparatus, information processing system, information processing method, and program

[0001] The present disclosure relates to an information processing apparatus, an information processing system, an information processing method, and a program. Specifically, the present disclosure relates to an information processing apparatus, an information processing system, an information processing method, and a program that provide information assisting a user's image capturing, such as recommended capturing targets, capturing times, and capturing locations, to a user who captures an image using a user terminal such as a smartphone.

[0002] In recent years, many users have been capturing still images and moving images using the camera function of smartphones. For example, at various events such as watching sports such as baseball, soccer, and boxing, or concerts, festivals, fireworks displays, and parades, many users capture a large number of images using smartphones.

[0003] However, in many cases, users who watch such events often do not know what should be set as a capturing target, or the optimal capturing timing, optimal capturing location, etc., and thus often miss photo opportunities.

[0004] For example, when a user who is not familiar with baseball visits a baseball stadium for the first time to watch a baseball game, the user often does not know information about events held at various locations in the baseball stadium, such as character shows held before or during the game, or events at restaurants. In such a case, the user is highly likely to lose the opportunity to capture photos of these events.

[0005] Furthermore, a user who is familiar with baseball can prepare for capturing in advance so as not to miss a photo opportunity, for example, pointing a smartphone at the batter when a home run hitter enters the batter's box. However, a user who is not familiar with baseball often cannot prepare for capturing in time, and is highly likely to be unable to capture an image of a moment such as a home run.

[0006] To prevent such situations, it is effective to inform users in advance of "event information," such as information that assists with image capture, information that identifies the subject to be photographed, information that indicates the timing of the shot, or information that indicates the shooting location. If users know this "event information" in advance, they can activate their smartphone camera and prepare to take pictures before a photo opportunity such as a character show or a home run.

[0007] Furthermore, Patent Document 1 (Japanese Patent Application Publication No. 2012-084979) discloses a prior art that provides a configuration for image editing processing using "event information" such as home runs. Patent Document 1 discloses a configuration that improves the efficiency of processing to generate short digest images by extracting highlight scenes such as home runs and fine plays from long-duration video footage of a baseball game, taken from the beginning to the end.

[0008] Specifically, the system discloses a configuration that generates digest images by using templates that record event information for each type of event, such as home runs, hits, or scoring scenes, and then extracting and connecting images of scenes that are similar to the templates from the long video footage to be edited.

[0009] However, the configuration described in Patent Document 1 is one that uses "event information" such as home runs to extract highlight scene images from already captured images, and does not disclose "event information" to inform the user of the timing of images to be captured.

[0010] Japanese Patent Publication No. 2012-084979

[0011] This disclosure aims to provide an information processing device, information processing system, information processing method, and program that can be used as information to assist in image capture, such as recommended subjects, shooting times, or shooting locations for users who take images using user terminals such as smartphones, and that enable users to take images using this information.

[0012] The first aspect of this disclosure is an information processing device having a control unit for executing an application, the control unit executing the application and executing a process to display event information on a display unit to assist the user in taking an image, wherein the event information includes information that includes a target to be photographed.

[0013] Furthermore, a second aspect of this disclosure is an information processing device comprising a communication unit that performs communication with a user terminal, and an event information generation unit that generates event information to be provided to the user terminal, wherein the event information generation unit generates event information that assists the user in taking images, and includes shooting target information indicating the object to be photographed, and provides this event information to the user terminal.

[0014] Furthermore, a third aspect of this disclosure is an information processing system having an event information providing server and a user terminal, wherein the event information providing server has a communication unit that performs communication with the user terminal and an event information generation unit that generates event information to be provided to the user terminal, the event information generation unit generates event information that assists the user using the user terminal in taking pictures, and includes shooting target information indicating the object to be photographed, and transmits it to the user terminal, and the user terminal is an information processing system that receives the event information from the event information providing server and performs the process of displaying it on a display unit.

[0015] Furthermore, a fourth aspect of this disclosure is an information processing method to be performed in an information processing device, wherein the information processing device has a control unit that executes an application, the control unit executes the application and performs a process to display event information on a display unit that assists the user in taking an image, and the event information is information that includes a target to be photographed.

[0016] Furthermore, a fifth aspect of this disclosure is a program that causes an information processing device to execute information processing, wherein the information processing device has a control unit that executes an application, and the program causes the control unit to execute the application and display event information on a display unit that assists the user in taking an image, wherein the event information is information that includes a target to be photographed.

[0017] The program disclosed herein is, for example, a program that can be provided to an information processing device or computer system capable of executing various program codes, via a storage medium or communication medium that provides it in a computer-readable format. By providing such a program in a computer-readable format, processing according to the program can be realized on the information processing device or computer system.

[0018] Further purposes, features, and advantages of this disclosure will become apparent from the more detailed descriptions based on the embodiments and accompanying drawings described below. In this specification, a system is a logical combination of multiple devices, and the devices in each configuration are not necessarily located within the same enclosure.

[0019] According to one embodiment of the present disclosure, a configuration is realized that provides users with assistance information for image capture using a user terminal such as a smartphone. Specifically, for example, an event information provision server provides event information to a user terminal such as a smartphone, which serves as assistance information when the user takes an image. Specifically, this event information includes information on the subject to be photographed, information on the shooting location, and information on the shooting time. Users who take images using a user terminal can refer to the event information to obtain optimal information regarding the subject, shooting location, and shooting time, thereby enabling them to capture images without missing a photo opportunity. These configurations realize a configuration that provides users with assistance information for image capture using a user terminal such as a smartphone. It should be noted that the effects described herein are merely examples and are not limited to those described herein, and additional effects may also exist.

[0020] This diagram illustrates a specific example of processing using a user terminal, which is an information processing device of the present disclosure. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates a specific example of processing using a user terminal. This diagram illustrates an example of the configuration of an information processing system that executes the processing of the present disclosure. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the processing executed by the event information provision server. This diagram illustrates the user information registration process for the event information provision server. This diagram illustrates an example of the configuration of the event information provision server. This diagram illustrates the processing executed by the image management server. This is a flowchart illustrating the processing sequence of operations performed on the user terminal. This is a flowchart illustrating the processing sequence of operations performed on the user terminal. This is a diagram illustrating an example of the configuration of a user terminal. This is a diagram illustrating an example of displaying event location (or event occurrence location) information along with event information. This is a diagram illustrating an example of displaying score information in a list of user-uploaded images. This is a diagram illustrating an example of notifying new event information. This is a diagram illustrating an example of notifying new event information.This figure illustrates an example of displaying real-time information along with event information. This figure illustrates an example of displaying the number of users viewing the event information and the number of images taken along with the event information. This figure illustrates an example of displaying a list of image library data stored on the image management server hardware configuration of the information processing device of this disclosure.

[0021] The details of the information processing device, information processing system, information processing method, and program described herein will be explained below with reference to the drawings. The explanation will follow the following items: 1. Specific examples of processing using a user terminal 2. Examples of information processing system configurations 3. Processing executed by the event information provision server 4. Examples of event information provision server configurations 5. Processing executed by the image management server 6. Sequence of processing executed on the user terminal 7. Examples of user terminal configurations 8. Other embodiments 9. Examples of hardware configurations of the information processing device 10. Summary of the configuration of this disclosure

[0022] [1. Specific Examples of Processing Using User Terminals] First, we will explain specific examples of processing using user terminals, which are information processing devices of this disclosure.

[0023] This disclosure provides event information, including recommended subjects for photography, to users who take pictures using a user terminal such as a smartphone. In this disclosure, the user terminal is not limited to a smartphone; any terminal equipped with a camera function for taking still images and videos, a communication function for communicating with external devices, and a display unit for displaying data is acceptable. In addition to smartphones, various devices such as tablet terminals, PCs, and cameras can be used as user terminals.

[0024] Referring to Figure 1 and subsequent figures, we will explain an example of processing using a smartphone, which is an example of a user terminal. In Figure 1, user 10 is carrying a user terminal 20 such as a smartphone and enters the event venue 30. In the example shown in Figure 1, the event venue 30 is a baseball stadium.

[0025] Although Figure 1 shows a baseball stadium as event venue 30, this is just one example, and event venues are not limited to baseball stadiums. For example, the processing described herein can be used in various event venues such as stadiums that host various sporting events like soccer and boxing, or plazas and arenas that host various events like concerts, festivals, fireworks displays, and parades.

[0026] In the example shown in Figure 1, user 10 enters the event venue 30, which is a baseball stadium, and watches a baseball game. The processes shown in Figure 1 (Steps S01) to (Steps S03) are then carried out sequentially. The processes of each of these steps will now be explained.

[0027] (Step S01) First, as shown in (Step S01) on the left side of Figure 1, when user 10 enters the baseball stadium which is the event venue 30, he launches the app (event information app) on his user terminal (smartphone) 20.

[0028] While the application (event information application) can be launched based on user input, it can also be configured to automatically launch when the user 10 enters the event venue (baseball field) 30 based on the GPS location information of the user terminal 20. Alternatively, the application can be configured to output a notification message to the user terminal 20 prompting it to launch when it detects that the user has entered the event venue.

[0029] (Step S02) After launching the app (event information provision app) in step S01, the user 10 then operates (taps) the queue instruction section (queue icon) in the operation section displayed at the bottom of the user terminal 20, as shown in (Step S02) at the bottom of Figure 1.

[0030] (Step S03) When the user operates (tap) the queue instruction unit (queue icon) in step S02, an event information list (= queue list) is displayed on the display unit of the user terminal 20, as shown in (Step S03) at the top of Figure 1.

[0031] The event information list (= queue list) displayed on the user terminal 20 is a list composed of information (event information) about various events taking place at the event venue into which user 10 has entered.

[0032] The "event information" provided by the event information server is information that can be used when user 10 takes pictures using user terminal 20, and is assist information to help user 10 take recommended pictures. Each of the multiple event information items that make up the event list (queue list) displayed on user terminal 20 of user 10 is information about various events that encourage the user to take pictures.

[0033] Each piece of event information is useful for users to take recommended photos, and for example, includes at least one of the following: (a) "Shooting subject information" indicating the subject to be photographed, (b) "Shooting time information" indicating the timing of the shoot, (c) "Shooting location information" indicating the shooting location, etc. Event information includes any of the above information (a) to (c).

[0034] By viewing the "event information" provided by the event information server, user 10 can anticipate various images that will be good photo opportunities, enabling them to take pictures more efficiently.

[0035] Figure 1 shows the user terminal 20 displaying the following two event information items (recommended photo information) included in the event information list provided by the event information server: (1) Event information 01, 21-1 (2) Event information 02, 21-2

[0036] Within "Event Information 01, 21-1," an image of the baseball stadium, which is the event venue visited by user 10, is displayed, along with the following messages: "Welcome to ABC Stadium" and "Arrived at the stadium! Let's take a commemorative photo." A photo-taking button 22 is also displayed.

[0037] The images and messages of the baseball stadium are information encouraging visitors to take commemorative photos and videos at the stadium upon arrival. In other words, it is information encouraging visitors to take pictures of themselves at the baseball stadium, and is event information that includes "information on subjects to photograph" and "information on locations to photograph."

[0038] Within "Event Information 02, 21-2," there is an image of the championship commemorative photo displayed at the championship commemorative booth, along with the following message: "Let's take a picture at the championship commemorative photo booth." These messages and the button 22 for proceeding to take a photo are displayed. The image of the championship commemorative photo and the message are information encouraging you to take photos or videos at the championship commemorative photo booth set up at the baseball stadium you have arrived at. In other words, it is information encouraging you to take pictures of the photos and trophies displayed at the championship commemorative photo booth set up at the baseball stadium, or pictures of yourself together with them, and is event information that includes "photo subject information" and "photo location information."

[0039] Furthermore, when the user operates (taps) the shooting transition button 22 within each event information 21, the process will proceed to the shooting stage. This process will be described later.

[0040] The event information list displayed on the user terminal 20 consists of various event information provided by the event information server. The user 10 can view various event information by scrolling.

[0041] Figure 2 shows an example of the display scrolling process on the user terminal 20 by user 10. Figure 2(a) shows the event information displayed before scrolling, and Figure 2(b) shows the event information displayed after scrolling.

[0042] The following two event information entries are displayed on the user terminal 20 in Figure 2(b): (3) Event information 03, 21-3 (4) Event information 04, 21-4

[0043] Within "Event Information 03, 21-3," there is an image of a hamburger being sold at a hamburger shop inside the baseball stadium, which is the event venue visited by user 10, along with the following message: "13:20 40 minutes before the game starts, you can take a photo with the players." These messages and a photo-taking button 22 are displayed. These images and messages are information encouraging users to take commemorative photos or videos with the players at the hamburger shop inside the baseball stadium where they have arrived.

[0044] Furthermore, in the "event information 03, 21-3", event occurrence position information 23 indicating the position of the hamburger shop where the event is held, and event occurrence time information 24 indicating that the event is held at 13:20 are also displayed. These correspond to "photographing location information" indicating the image capturing location and "photographing time information" indicating the photographing timing.

[0045] In the "event information 04, 21-4", an image of people toasting in the spectator seats of a baseball stadium, the following message "13:45 15 minutes before the game starts, let's take a photo to celebrate victory", this message, and a photographing transition button 22 are displayed. These images and messages are information that encourages capturing photos and moving images of the celebration victory in the spectator seats immediately before the game starts.

[0046] This event information includes the following pieces of information: photographing target information = self-photographing celebrating victory in the spectator seats, photographing time information = immediately before the start of the game (from 13:45), and photographing location information = spectator seats.

[0047] FIG. 3(b) shows a display example after the user 10 further performs a scrolling process in the display state of the user terminal 20 shown in FIG. 2(b).

[0048] The following two pieces of event information (recommended photographing information) are displayed on the user terminal 20 in FIG. 3(b): (4) event information 04, 21-4; (5) event information 05, 21-5. Said "event information 04, 21-4" is the event information already described with reference to FIG. 2.

[0049] In the "event information 05, 21-5", an image of a player playing a baseball game, the following message "14:00 The game starts, let's take a photo of your favorite player", these messages, and a photographing transition button 22 are displayed. These images and messages are information that encourages capturing photos and moving images of a user's favorite player playing the game on the field when the game starts.

[0050] This event information includes the following details: Photograph subject information = your favorite player during the match on the field; Photograph time information = match start time (14:00 onwards); Photograph location information = spectator seats (photographing players on the field from the spectator seats).

[0051] Note that the two event information entries 21-4 and 21-5 displayed on the user terminal 20 shown in Figure 3(c) do not show the shooting transition button 22. As explained earlier with reference to Figure 1 and others, the shooting transition button 22 is a button (operation icon) that the user 10 operates (taps) when taking an image.

[0052] For event information where the shooting transition button 22 is displayed, the user can proceed to the image capture process related to that event information by operating the shooting transition button 22. However, for event information where the shooting transition button 22 is not displayed, the user 10 cannot proceed to image capture related to that event information because the shooting transition button 22 is not displayed.

[0053] If a photo transition button is displayed within the event information, you can tap it to proceed with the photo shooting process according to the app's specifications. However, if the photo transition button is not displayed, you cannot proceed with the photo shooting process according to the app's specifications.

[0054] While it is possible to take regular photos by launching a separate, independent camera app, the process of coordinating with the app will not be performed automatically. For example, it is not possible to automatically upload captured images to an image management server that manages images on an event-by-event basis. The process of uploading captured images to the image management server will be described later.

[0055] The event list provided by the event information server contains a large amount of event information, but this information can be divided into two types: event information that does not include shooting time information and event information that does include shooting time information.

[0056] Event information that does not include shooting time information is event information that does not specify a recommended shooting time. For example, the two event information items 21-1 and 21-2 explained earlier with reference to Figure 1, are event information in which shooting is possible at any time after the user 10 arrives at the event venue 30, the baseball field, and no particularly recommended shooting time is specified. For event information that does not specify a recommended shooting time, a shooting transition button 22 is displayed within the event information 21 in conjunction with the display timing of the event information 21.

[0057] In other words, for event information that does not specify a recommended shooting time, the shooting transition button 22 is always displayed within the event information 21, and the user can perform the image capture process related to that event information at any time by operating (tapping) the shooting transition button 22 while the event information 21 is displayed.

[0058] On the other hand, for event information that specifies a recommended shooting time, when the recommended shooting time (= event occurrence time information) displayed in event information 21 approaches, a shooting transition button 22 will be displayed within that event information.

[0059] Specifically, when a predetermined time arrives, such as five minutes before the recommended shooting time (= event occurrence time information) displayed in the event information 21, the shooting transition button 22 will be displayed within that event information. This display control process is executed, for example, by the event display application.

[0060] Refer to Figure 4 and subsequent figures to explain an example of the control process for displaying event information 21 and the display process for the shooting transition button 22.

[0061] Figures 4(p) and (q) both show the display of the following two event information items, as explained earlier with reference to Figure 3(c). However, Figures 4(p) and (q) show two different time display examples: (p) Example of event information display at 13:35 (q) Example of event information display at 13:40

[0062] Figures 4(p) and 4(q) both display the following two event information, which were explained earlier with reference to Figure 3(c). "Event Information 04, 21-4" is event information that displays the message, "13:45 15 minutes before the match starts, let's take a photo to celebrate the victory." The event occurrence time information, i.e., the recommended time for taking a photo, is 13:45.

[0063] Furthermore, "Event Information 05,21-5" is an event information that displays the message, "Match starts at 14:00, take pictures of your favorite players," and the event time information, i.e., the recommended time for taking photos, is 14:00.

[0064] In the example of event information display at 13:35 shown on the left side of Figure 4 (p), the shooting transition button 22 is not displayed in either "Event Information 04, 21-4" displayed in the upper section of the user terminal 20, nor in "Event Information 05, 21-5" displayed in the lower section.

[0065] This is because the current time (13:35) is not yet 5 minutes before the event times (= recommended shooting times) for the two event information items 04 and 05. The event time (= recommended shooting time) for event information item 04, which is 13:45, is 10 minutes after the current time (13:35). Also, the event time (= recommended shooting time) for event information item 05, which is 14:00, is 25 minutes after the current time (13:35).

[0066] Furthermore, for event information with a defined event occurrence time, the display process for the entire event information data, i.e., the entire event information consisting of images and messages, may also be controlled to display it 30 minutes before the event occurrence time, or at least before the defined time of the event occurrence.

[0067] In the example of event information display at 13:40 shown on the right side of Figure 4 (q), the shooting transition button 22 is displayed only for "Event Information 04, 21-4" displayed in the upper section of the user terminal 20. However, the shooting transition button 22 is not displayed for "Event Information 05, 21-5" displayed in the lower section.

[0068] The reason why the "Shooting Transition Button 22" is displayed in "Event Information 04, 21-4" is because the current time (13:40) is 5 minutes before the event occurrence time of Event Information 04. The event occurrence time of Event Information 04, 13:45, is 5 minutes after the current time (13:40).

[0069] In this way, when a predetermined time arrives, such as five minutes before the recommended shooting time (= event occurrence time information) displayed in the event information 21, the shooting transition button 22 will appear in that event information. This display control process is executed by the event display application.

[0070] Furthermore, the event occurrence time of 14:00 in event information 05 is 20 minutes after the current time (13:40), and at this point, the shooting transition button 22 is not displayed in event information 05.

[0071] In this way, by controlling the system to display the shooting transition button 22 when the event time for each event information approaches, the user 10 can take a picture at the recommended shooting timing.

[0072] Figure 5 shows examples of event information displays, specifically (q) an example of event information display at 13:40, and (r) an example of event information display 15 minutes later at 13:55, as explained with reference to Figure 4.

[0073] As explained with reference to Figure 4(q), in Figure 5(q), the shooting transition button 22 is displayed only for "Event Information 04, 21-4," and not for "Event Information 05, 21-5." This is because the current time (13:40) is 5 minutes before the event occurrence time of Event Information 04, which is 13:45, but not 5 minutes before the event occurrence time of Event Information 05, which is 14:00.

[0074] Figure 5(r) shows an example of the event information display at 13:55, 15 minutes later. In this example, the display of the shooting transition button 22 for "Event Information 04, 21-4" is removed, and the shooting transition button 22 is displayed for "Event Information 05, 21-5".

[0075] The reason why the "Shooting Transition Button 22" is displayed in "Event Information 05, 21-5" is because the current time (13:55) is 5 minutes before the event occurrence time of Event Information 05, which is 14:00.

[0076] On the other hand, the event occurrence time for "Event Information 04, 21-4" = 13:45 is before the current time (13:55), so the event occurrence time (= recommended shooting time) has already passed, and therefore the shooting transition button 22 is set to hidden.

[0077] Furthermore, while it is possible to implement a control to hide the entire event information data if the event occurrence time has passed, the display of event information such as images and messages may be kept active in order to use it when searching for or viewing images taken in relation to that event (images taken by user 10 or other users). The process of searching for and viewing images taken using event information will be explained later.

[0078] Next, with reference to Figure 6 and subsequent figures, we will describe the specific sequence of image capture processing that is executed based on user operation (tap processing) on ​​the shooting transition button 22 displayed in the event information 21.

[0079] The image capture process, which is executed based on a user operation (tap) on the shooting transition button 22 displayed in the event information 21, is performed according to the sequence of steps S11 to S16 shown in Figures 6 to 8, for example. The processing of each of these steps will be explained in order below.

[0080] (Step S11) First, as shown in step S11 of Figure 6, the user performs a user operation (tap) on the shooting transition button 22 displayed in the event information 21 displayed on the display unit of the user terminal 20.

[0081] In Figure 6 (Step S11), the event information 21-4 displayed on the user terminal 20 is an event information 21-4 that recommends taking a "photo to celebrate victory" just before the start of the match (13:45). The user will follow the recommendation of this event information 21-4 and take a "photo to celebrate victory" just before the start of the match (13:45).

[0082] (Step S12) In step S11, when the user operates (tap) the shooting transition button 22 in the event information 21, the "Media Selection UI (User Interface) 25" is displayed on the display unit of the user terminal 20, as shown in step S12 of Figure 6.

[0083] The media selection UI25 includes the following options: Camera (still images), Camera (video), Gallery.

[0084] Select "Camera (Still Images)" to take a new still image using the user's device's camera function. Select "Camera (Video)" to take a new video using the user's device's camera function. Select "Gallery" to upload images that have already been taken and stored in the user's device's memory, etc.

[0085] (Step S13) After the "Media Selection UI (User Interface) 25" is displayed on the user terminal 20 in step S12, the user selects one option from the "Media Selection UI 25" as shown in step S13 of Figure 7. The example shown in the figure is an example where "Camera (Still Image)" is selected.

[0086] This process activates the camera function of the user terminal 20, allowing the user to take pictures. The user takes pictures of the images recommended by the event information.

[0087] As mentioned above, in this example, the event information 21-4 displayed on the user terminal 20 is an event information 21-4 that recommends taking a "photo to celebrate victory" just before the start of the match (13:45). The user follows the recommendation of this event information 21-4 and takes a "photo to celebrate victory" (still image) just before the start of the match (13:45). Once the still image has been taken, the user proceeds to the next step S14.

[0088] (Step S14) When the user completes taking the image, the user's captured image 26 is displayed on the user terminal 20, as shown in step S14 of Figure 7. In addition, the upload processing setting UI 27 is also displayed.

[0089] The upload processing settings UI 27 is a UI that allows users to configure whether or not to upload the captured images 26 to an external image management server, and if so, whether or not to make the uploaded images public.

[0090] As shown in Figure 7, the upload processing settings UI27 is a UI that allows the user to select from the following three types of processing: (a) If you want to upload with public access, specify "Public" and select "Upload" (b) If you want to upload without public access, specify "Private" and select "Upload" (c) If you do not want to upload, select "Cancel"

[0091] (Step S15) Step S15, shown in Figure 8, shows an example of user operation on the upload processing setting UI 27 displayed on the user terminal 20 in step S14.

[0092] Figure 8 shows an example where a user selects and executes the process described in (a) above, namely, (a) selecting "Public" and then "Upload" when making an upload that allows public access.

[0093] (Step S16) Step S16 shown in Figure 8 shows an example of the displayed data on the user terminal 20 when the user performs an "upload" process specifying "public" in step S15.

[0094] When a user performs an "upload" process specifying "public," the user's terminal 20 displays a list of images uploaded by other users, along with the uploaded image 28 uploaded by the user.

[0095] This list of images is a collection of photos taken by many users following the same event information, specifically the recommendation for event information 21-4 as explained earlier with reference to Figure 6 (Step S11). These are "photos celebrating victory" taken at approximately the same time, just before the start of the match (13:45).

[0096] Uploaded images include not only still images but also videos. All of these uploaded images are permitted to be made public. Each user can acquire these uploaded images, for example, by purchasing them at a predetermined price or acquiring them for free. These image purchase and transfer processes will be carried out according to the regulations of the image management server.

[0097] The image capture process, which is executed based on user operation (tap processing) on ​​the capture transition button 22 in the event information 21 displayed on the user terminal 20, has been described above with reference to Figures 6 to 8.

[0098] Next, referring to Figures 9 to 10, we will explain the processes executed based on user operations (tap operations) on areas other than the shooting transition button 22 within the event information 21 displayed on the user terminal 20. We will explain the processes of steps S21 to S24 in Figures 9 to 10 in order.

[0099] (Step S21) Step S21 shown in Figure 9 illustrates an example in which the user performs a user operation (tap) on an event information 21-4 display area other than the event information 21-4 displayed on the display unit of the user terminal 20, rather than the event information 21-4 display area.

[0100] Furthermore, the event information 21-4 displayed on the user terminal 20 in Figure 9 (step S21) is the same as explained earlier with reference to Figure 6 (step S11), and is the "event information 21-4" that recommends taking a "photo to celebrate the victory" just before the start of the match (13:45).

[0101] (Step S22) In step S21, if the user performs a user operation (tap) on an event information 21-4 display area other than the event information 21-4 displayed on the display unit of the user terminal 20, the event information 21-4 will be displayed as is in the upper area of ​​the user terminal 20, and the user-uploaded image list 29 will be displayed in the lower area, as shown in (Step S22) of Figure 9.

[0102] The user-uploaded image list 29 is a list of images taken by other users following the same event information, specifically the recommendations in event information 21-4, and is a list of "photos celebrating victory" taken at a time very close to the present, specifically just before the start of the match (13:45). Users can view these images to consider the subject, direction, and angle of their own photos.

[0103] (Step S23) Figure 10 shows an example of user operation when the user decides to take an image after checking the user-uploaded image list 29 displayed on the user terminal 20.

[0104] In this case, the user performs a user operation (tap) on the shooting transition button 22 displayed in the event information 21 shown on the display unit of the user terminal 20. The event information 21-4 displayed on the user terminal 20 is "event information 21-4" which recommends taking a "photo to celebrate victory" just before the start of the match (13:45), and the user will take a "photo to celebrate victory" just before the start of the match (13:45) following the recommendation of this event information 21-4.

[0105] (Step S24) Step S24 is the same as the process in Figure 6 (Step S12) described earlier. In Step S23, when the user operates (tap) the shooting transition button 22 in the event information 21, the "Media Selection UI (User Interface) 25" is displayed on the display of the user terminal 20, as shown in Step S24 of Figure 10.

[0106] The user selects media using the media selection UI25, then takes an image, determines the upload processing method, and then performs the upload process for the captured image. These processes are the same as those described earlier with reference to Figures 6 to 8.

[0107] [2. Example of Information Processing System Configuration] Next, an example of the configuration of an information processing system that performs the processing described herein will be explained.

[0108] Figure 11 shows an example configuration of an information processing system that performs the processing of the present disclosure. As shown in Figure 11, the information processing system 100 of the present disclosure is composed of a communication network that enables communication between user terminals 20 owned by multiple users 10, an event information provision server 110, and an image management server 120.

[0109] In the example shown in Figure 11, the event information server 110 and the image management server 120 are shown as separate servers, but these servers can also be configured as a single server. Furthermore, multiple event information servers 110 and image management servers 120 may be provided. For example, the event information server 110 can be configured as a dedicated server for baseball events at a particular baseball stadium, an event information server dedicated to concert events at a particular concert venue, etc., with separate servers for each event.

[0110] Furthermore, in the example shown in Figure 11, all users 10 are assumed to own a smartphone as their user terminal 20. However, as explained earlier, the user terminal 20 is not limited to a smartphone and may be any device such as a tablet, PC, or camera equipped with a camera function for taking still images and videos, a communication function for communicating with external devices, and a display unit for displaying data.

[0111] The event information server 110 shown in Figure 11 provides event information to the user terminal 20 owned by the user 10. That is, each user 10 shown in Figure 11 can view the event information provided by the event information server 110 using their own user terminal 20. This is the event information 21 explained earlier with reference to Figures 1 to 5, etc. In other words, it is information useful for the user to take recommended images, and includes, for example, at least one of the following types of information: (a) "Shooting target information" indicating the subject to be photographed, (b) "Shooting time information" indicating the timing of the shoot, (c) "Shooting location information" indicating the shooting location, etc.

[0112] By viewing the "event information" provided by the event information server, user 10 can anticipate various images that will be good photo opportunities, enabling them to take pictures more efficiently.

[0113] User 10 can view the "event information" provided by the event information server 110 to understand the subject to be photographed, and then upload the photographed images, such as still images and videos, to the image management server 120 shown in Figure 11.

[0114] The process of capturing images using the user terminal 20 by user 10 and uploading the captured images corresponds to the process described earlier with reference to Figures 6 to 10.

[0115] As explained earlier with reference to Figures 6 to 10, images uploaded by each user to the image management server 120 can be viewed on user terminal 20 of user 10. Furthermore, each user can acquire and purchase these images. The image acquisition and purchase process is performed according to the rules defined by the image management server 120.

[0116] [3. Processing performed by the event information server] Next, the processing performed by the event information server 110 shown in Figure 11 will be explained. The event information server 110 is composed of a computer system that performs data processing, a PC, a large-capacity storage unit, etc., and has a configuration that allows for various controls, such as data input, data updates, and setting changes using the event management manager's PC.

[0117] As shown in Figure 12, the event information server 110 provides event information to the user terminal 20 owned by the user 10. This event information 21, as previously explained with reference to Figures 1 to 5, includes at least one of the following: (a) "Shooting target information" indicating the subject to be photographed, (b) "Shooting time information" indicating the timing of the shoot, (c) "Shooting location information" indicating the shooting location, etc.

[0118] Figure 13 shows an example of an event information registration screen displayed on a PC or other device when an event administrator accesses the event information server 110 via PC or other device. The event information registration data entered on this registration screen is stored in the event information storage unit.

[0119] As shown in Figure 13, the event information registration data includes, for example, the following information: (a) Event information identifier (b) Event title (c) Event image (d) Event message (e) Date and time of event information display (f) Date and time of photo transition button display (g) Date and time of event information display stop

[0120] The event information registration data shown in Figure 13 corresponds to the event information 04, 21-4 explained earlier with reference to Figure 3 and others. Specifically, it is registration data that displays the event message, "13:45 15 minutes before the match starts, let's take a photo to celebrate the victory," and has a toast image as the event image.

[0121] As shown in Figure 13, the event information registration data includes, for example, the following date and time information: (e) Date and time of event information display (f) Date and time of the shooting transition button display (g) Date and time of event information display stop The event information providing server 110 sets this registered date and time information and controls the display timing and hiding timing of event information and the shooting transition button according to the set date and time information.

[0122] Figure 14 shows an example of a UI (user interface) for performing the above-mentioned date and time information setting process, i.e., an example of a "date and time information setting UI". This UI is an example of the UI that is displayed on a PC or other device when an event administrator accesses the event information provision server 110 from a PC or other device.

[0123] As shown in Figure 14, the "Date and Time Information Setting UI" has a calendar section and a time setting section for setting the date and time. The operator of the event information provision server 110 uses the Date and Time Information Setting UI shown in Figure 14, for example, to set the following dates and times: (e) Date and time for displaying event information (f) Date and time for displaying the shooting transition button (g) Date and time for stopping the display of event information.

[0124] These dates and times are set for each event. Based on the date and time settings for each event, each user's terminal 20 performs the following actions: displaying the event information, displaying the camera transition button, and hiding (deleting) the event information. In the example shown in Figure 14, the option to hide the camera transition button is not set, and the hiding of the camera transition button is performed in conjunction with the hiding of the event information.

[0125] If you want to hide the shooting transition button at a different date and time than the event information hiding process, use a UI where the settings for hiding the shooting transition button are configured independently of the settings for hiding the event information.

[0126] Multiple event information registration data generated using the date and time information setting UI as shown in Figure 14 are stored in the event information storage unit. The event information providing server 110 uses the numerous event registration data stored in the event information storage unit to display event information on the user's user terminal 20 and to control the display of the shooting transition button.

[0127] Figure 15 shows an example of a processing sequence for displaying event information and controlling the display of the shooting transition button, which are performed by the event information provision server 110 using event registration data.

[0128] Figure 15 shows an example of the display control sequence for event information and the shooting transition button, which is executed based on the event information registration data for each of the event information a, b, and c, along with the time axis (t).

[0129] In the example shown in Figure 15, based on the event information registration data for event information a, the display process for event information a is executed at 12:10, the display process for the shooting transition button is executed at 12:35, and the hiding process for event information a is executed at 17:15.

[0130] Based on the event information registration data for event information b, the display process for event information b is executed at 12:30, the display process for the shooting transition button is executed at 12:45, and the hiding process for event information b is executed at 17:45. The same display control is then performed for numerous other event information items such as event information c, d, e, etc.

[0131] The event information shown in Figure 15 is processed by the event information server 110 using event registration information that has been pre-registered before the start of each event. However, in events such as baseball games, there are events where the time of occurrence cannot be known in advance. For example, events that occur according to the progress of a baseball game. Specifically, for events such as the start of the top of the 7th inning, the time is uncertain, and it is not possible to set the display time of the event information or the shooting transition button in advance.

[0132] As shown in Figure 16, the event information provision server 110 receives real-time event analysis information sequentially from the information analysis processing execution server 130, generates real-time event information using the received event analysis information, and provides the generated real-time event information to the user.

[0133] The real-time event analysis information received from the information analysis processing execution server 130 includes various types of information obtained in real time, such as progress information of a baseball game, player statistics, count information, pitch speed information, and batted ball speed information. The event information provision server 110 receives such real-time event analysis information from the information analysis processing execution server 130, generates real-time event information using the received event analysis information, and provides the generated real-time event information to the user.

[0134] Referring to Figure 17, an example of the display sequence of real-time event information shown on user terminal 20 of user 10 will be described. The example of event information display shown in Figure 17 is an example of processing that provides the start of the attack in the top of the 7th inning of a baseball game as real-time event information.

[0135] As shown in the diagram, the process of displaying event information on the user terminal 20 is performed at 14:10, just before the start of the attack in the top of the 7th inning. This event information is real-time event information generated by the event information provision server 110 using real-time event analysis information received from the information analysis processing execution server 130.

[0136] As an event message, for example, "14:10 The big counterattack in the top of the 7th inning is about to begin. It's time for the powerful hitter, Suzuki, to bat. This is a great photo opportunity for a home run." Such an event message is generated and provided to the user's terminal 20 for display.

[0137] Furthermore, at 2:12 PM, the button to switch to recording will be displayed. This timing will be, for example, when batter Suzuki steps up to the batter's box. Then, at 2:20 PM, when batter Suzuki's at-bat ends, the event information will be hidden.

[0138] Furthermore, if, for example, batter Suzuki actually hits a home run, it is possible to generate and provide real-time event information, such as prompting users to take images of the moment the home run is celebrated.

[0139] In this way, the event information server 110, used by the event administrator, can register a large amount of event information according to a predetermined event schedule and provide this pre-registered event information to the user's terminal 20. It can also sequentially generate and provide real-time event information to the user terminal 20 for real-time events that have not been pre-registered.

[0140] Referring to Figures 18 and 19, an example of the event information provision and display processing sequence executed by the event information provision server 110, which mixes pre-registered event information and real-time event information, will be explained.

[0141] Figures 18 and 19 show an example of the sequence of events provided to a user attending a baseball game that starts at 14:00.

[0142] The first event information provided to the user's terminal 20 is the pre-registered event information 01 shown in Figure 18. This pre-registered event information 01 is event information where Event = "Arrival at the stadium". As shown in the figure, the timing of displaying and hiding the event information and the shooting transition button is as follows: Event information display date and time = 13:00 Shooting transition button display date and time = 13:00 Event information display stop date and time = 15:00

[0143] Furthermore, the following message will be displayed as an "event message": Event message = Let's take a commemorative photo at the stadium entrance.

[0144] Please note that this event information includes the following: Information on the subject of photography = stadium gate + information on your shooting location = stadium entrance

[0145] The pre-registered event information 02 shown in Figure 18 is also pre-registered event information. This pre-registered event information 02 is event information where the event is "character show". As shown in the figure, the timing of displaying and hiding the event information and the shooting transition button is as follows: Event information display date and time = 13:00 Shooting transition button display date and time = 13:00 Event information display stop date and time = 14:00

[0146] Furthermore, the following message will be displayed as an "event message": Event message = There will be a character show at the stadium event plaza from 13:10, let's take pictures with the characters!

[0147] This event information includes the following: Shooting subject information = Character + Yourself; Shooting location information = Stadium event plaza

[0148] The event information shown on the far right of Figure 18 is also pre-registered event information, with the event defined as "just before the start of the game." The event information shown on the far left of the following Figure 19 is also pre-registered event information, with the event defined as "first pitch ceremony."

[0149] The "Real-time event information r11" shown in the center of Figure 18 is not pre-registered event information, but rather real-time event information generated using match progress information, etc.

[0150] This real-time event information r11 is event information where the event is defined as "7 attacks started". As shown in the figure, the timing of displaying and hiding the event information and the shooting transition button is as follows: Event information display date and time = 15:14 Shooting transition button display date and time = 15:14 Event information display stopped date and time = 15:20 These time information is determined by referring to the event analysis information received from the information analysis processing execution server 130, as explained with reference to Figure 16.

[0151] Furthermore, the following message will be displayed as an "event message": Event message = Lucky seventh inning, the great counterattack in the 7th inning begins! Take a photo of player xx's powerful batting!

[0152] This event information includes the following details: Subject of photography = Player xx; Location of photography = Player xx photographed from the spectator seats; Time of photography = Start of the 7th inning.

[0153] The "Real-time event information r12" shown on the far right of Figure 18 is also real-time event information generated using match progress information, etc., rather than pre-registered event information.

[0154] This real-time event information r12 is event information where the event is set to "end of game". As shown in the figure, the timing of displaying and hiding the event information and the shooting transition button is as follows: Event information display date and time = 16:20 Shooting transition button display date and time = 16:30 Event information display stopped date and time = 17:00 These time information is determined by referring to the event analysis information received from the information analysis processing execution server 130, as explained with reference to Figure 16.

[0155] Furthermore, the following message will be displayed as an "event message": Event message = The match is over, let's take a photo to celebrate the victory.

[0156] This event information includes the following: Information on subjects to be photographed = baseball field, players, yourself, etc.; Time of photography = immediately after the end of the game.

[0157] In this manner, the event information server 110 provides user terminal 20 of user 10 with event information that includes both pre-registered event information and real-time event information.

[0158] In the above embodiment, the event information server 110 was described as providing common event information to all users, but it is also possible to perform processing that provides different event information to each user.

[0159] For example, the user sends user identification information (such as a user account) and user preference information to the event information server 110 in advance. The event information server 110 registers this information as user information in its database. Subsequently, the event information server 110 uses the registered user information to prioritize selecting event information that is estimated to be of high interest to the user and provides it to the user's user terminal 20. For example, it generates a user-specific user page that can be displayed using the registered account information and provides it to each user.

[0160] Referring to Figure 20, an example sequence of processes in which the event information server 110 provides user-specific event information to the user terminal 20 will be described. The process is carried out in the order of steps S41 to S44 shown in Figure 20. The process of each step will be described below.

[0161] (Step S41) First, in step S41, user 10 inputs user information 151 using user terminal 20.

[0162] User information 151 includes, for example, user identification information (user account, etc.) and user preference information. Figure 21 shows an example of a UI for inputting user preference information. Figure 21(a) is an example of a UI for selecting a favorite player. Figure 21(b) is a UI for selecting a favorite food.

[0163] The UI for selecting a favorite player shown in (a) can be used in the aforementioned baseball event when the event information server 110 provides event information on a per-user basis regarding the timing of the appearance of the user's favorite player.

[0164] The UI for selecting favorite foods shown in (b) can be used not only for the aforementioned baseball event, but also for food festivals offering a variety of foods, when the event information server 110 provides event information to each user on a per-user basis, such as when their favorite foods are on sale.

[0165] Returning to Figure 20, we will continue the explanation of an example sequence of processes in which the event information server 110 provides user-specific event information to the user terminal 20.

[0166] (Step S42) In step S41, when user 10 inputs user information 151 using user terminal 20, the input information is sent to event information provision server 110, and in step S42, it is registered in the database (user information database) within event information provision server 110.

[0167] These steps S41 to S42 complete the preliminary processing for sending user-specific event information.

[0168] (Steps S43-S44) Once the preliminary processing in steps S41-S42 is complete, the event information provision server 110 executes user-specific event information transmission processing from step S43 onwards.

[0169] In steps S43 to S44, the event information server 110 performs event information generation processing according to user preferences on a user-by-user basis, and event information selection processing from event information stored in the memory unit, thereby performing event information provision processing on a user-by-user basis.

[0170] For example, if user A's user information includes "favorite player" = "Suzuki," the system will generate or select event information that includes scenes featuring "Suzuki" and provide it to user A.

[0171] Furthermore, if user b's user information includes "Steak" as a favorite food, the system will generate or select event information related to "Steak" and provide it to user b.

[0172] In this way, the event information server 110 can provide user-specific event information to each user by utilizing user information that includes the implementation information of each user that has been registered in advance.

[0173] [4. Example of Event Information Server Configuration] Next, an example of the configuration of the event information server 110.

[0174] Figure 22 is a block diagram illustrating an example configuration of the event information provision server 110. As shown in Figure 22, the event information provision server 110 includes an event-related information storage unit 111, an event information generation and registration unit 112, an event information storage unit 113, a user information storage unit 114, an output event information (& shooting transition button) generation unit 115, an event information (& shooting transition button) output control unit 116, and a user information registration unit 117.

[0175] The event-related information storage unit 111 is a storage unit that stores event-related information necessary for generating event information. For example, in the case of a baseball game event at a baseball stadium, it records the game schedule, the locations and schedules of character shows held at various parts of the stadium, and information on restaurants, etc. This information may be information that an operator has previously obtained and registered from an external source or information obtained from an external server.

[0176] The event information generation and registration unit 112 refers to the event-related information stored in the event-related information storage unit 111 to generate event information consisting of images, messages, etc., to be output to a user terminal such as a smartphone, and stores it in the event information storage unit 113.

[0177] Specifically, the event information generation and registration unit 112 performs the processes described earlier with reference to Figures 13 and 14. That is, as shown in Figure 13, the event information generation and registration unit 112 generates event information consisting of, for example, the following data and stores it in the event information storage unit 113: (a) Event information identifier (b) Event title (c) Event image (d) Event message (e) Event information display date and time (f) Shooting transition button display date and time (g) Event information display stop date and time

[0178] The event information storage unit 113 stores event information generated by the event information generation and registration unit 112. The event information generation and registration unit 112 generates and stores in the event information storage unit 113 any event information that can be generated and registered in advance. Furthermore, as explained earlier with reference to Figure 16, the system receives real-time event analysis information sequentially from the information analysis processing execution server 130, generates real-time event information using the received event analysis information, and stores this generated real-time event information in the event information storage unit 113 as well.

[0179] The user information storage unit 114 is a storage unit that stores user information acquired from the user terminal by the user information registration unit 117. As explained earlier with reference to Figures 20 and 21, the event information provision server 110 acquires user information from the user in advance, consisting of user identification information (user account, etc.) and user preference information. The event information provision server 110 uses this acquired user information to generate and provide user-specific event information tailored to each user's preferences.

[0180] The user information registration unit 117 acquires user information consisting of user identification information (such as user account information) and user preference information entered into the user terminal 20 of the user 10, and stores the acquired user information in the user information storage unit 114.

[0181] The output event information (& shooting transition button) generation unit 115 generates event information for display on the user terminal 20 of user 10. Based on the event information retrieved from the event information storage unit, the output event information (& shooting transition button) generation unit 115 generates event information for display on the user terminal 20.

[0182] The event information generated by the output event information (& shooting transition button) generation unit 115 includes not only pre-generated event information but also real-time event information generated using event analysis information input from the information analysis processing execution server 130.

[0183] Furthermore, user-specific event information is generated using user-specific preference information registered in the user information storage unit 114 as needed.

[0184] The event information (& shooting transition button) output control unit 116 executes control to output the event information and shooting transition button generated by the output event information (& shooting transition button) generation unit 115 to the user terminal 20. For example, for event information related to an event with a defined event occurrence time, it executes the information display timing control described earlier with reference to Figures 4 and 5. Specifically, it executes output timing control such as outputting the event information 30 minutes before the defined event occurrence time, and outputting the shooting transition button 5 minutes before the defined event occurrence time.

[0185] Furthermore, the timing control process for displaying this event information and the shooting transition button may be configured to be executed by using an application installed on the user terminal 20 of user 10.

[0186] [5. Processes performed by the image management server] Next, we will explain the processes performed by the image management server 120.

[0187] As explained earlier with reference to Figure 11, user 10 can look at the "event information" provided by the event information server 110 to understand the subject to be photographed, and then upload the photographed images, such as still images or videos, to the image management server 120.

[0188] As mentioned above, the event information server 110 and the image management server 120 can also be configured as a single server.

[0189] Referring to Figure 23, the process performed between the image management server 120 and the user terminal 20 will be described. As shown in Figure 23, the user 10 can upload newly captured images, such as still images or videos, taken using the user terminal 20 to the image management server 120.

[0190] The image management server 120 stores images uploaded from the user terminal 20 in its image information storage unit. For example, it stores the corresponding captured image for each event information generated by the event information provision server 110.

[0191] User 10 can view images taken by multiple users stored in the image management server 120. For example, the images corresponding to each event information generated by the event information provision server 110 can be displayed as a list on the user terminal 20.

[0192] In other words, as explained earlier with reference to Figures 6 to 10, images uploaded by each user to the image management server 120 can be viewed on user terminal 20 of user 10. Furthermore, each user can also acquire and purchase these images. The image acquisition and purchase process is performed according to the rules defined by the image management server 120.

[0193] [6. Sequence of processes executed on the user terminal] Next, we will explain the sequence of processes executed on the user terminal.

[0194] User 10 can view event information provided by the event information server 110 using a user terminal 20 such as a smartphone. Furthermore, user 10 can perform processes such as uploading images taken with the user terminal 20 to the image management server 120. The following describes the processing sequence when these processes are executed on the user terminal 20.

[0195] The flowchart shown in Figure 24 illustrates the processing sequence of the operations to be performed on the user terminal 20. These operations are performed under the control of an application program installed on the user terminal 20. The processing steps of each step in the flowchart shown in Figure 24 will be explained sequentially below.

[0196] (Step S101) First, the user launches the application (event information provision application) on the user terminal 20, such as a smartphone.

[0197] As mentioned above, the user can initiate the launch of the app (event information provision app) by operating the user terminal 20 themselves. However, the app may also be automatically launched when the user 10 enters an event venue such as a baseball stadium, based on the GPS location information of the user terminal 20. Alternatively, the app may be configured to send a notification prompting the user to launch the app upon detection of entry into the event venue.

[0198] (Step S102) After launching the application (event information provision application) in step S101, the user terminal 20 displays a list of event information (queue list) provided by the event information provision server 110.

[0199] As explained earlier with reference to Figure 1 and subsequent figures, the list of event information displayed on the user terminal 20 is composed of various event information provided by the event information provider server. The user 10 can view various event information by scrolling.

[0200] (Step S103) Step S103 is a branching step based on the user's judgment. If the user finds event information they want to photograph from the event information displayed on the user terminal 20, the process proceeds to step S104. If they do not find any, the process of browsing the event in step S102 continues.

[0201] (Step S104) If, in step S103, the user finds event information that they want to photograph from the event information displayed on the user terminal 20, the process proceeds to step S104.

[0202] Step S104 is a branching step based on whether or not a shooting transition button is displayed in the event information that the user has focused on. If a shooting transition button is not displayed in the event information, the process proceeds to step S105. On the other hand, if a shooting transition button is displayed in the event information, the process proceeds to step S106.

[0203] As mentioned earlier, if the event information pertains to an event taking place at a specific time, the photo transition button will not appear until just before the event occurs, for example, five minutes before. If the photo transition button is displayed within the event information, tapping it will allow you to proceed with the photo shooting process according to the app's specifications. However, if the photo transition button is not displayed, you cannot proceed with the photo shooting process according to the app's specifications.

[0204] As mentioned above, while it is possible to take normal photos by launching a separate, independent camera app, if the app is not linked, it is not possible to automatically perform processes such as uploading images to the image management server 120 after taking a picture.

[0205] (Step S105) If the shooting transition button is not displayed in the event information in step S104, proceed to step S105.

[0206] In step S105, the user waits until the "Take a Photo" button appears within the event information, or operates (taps) an area within the event information other than the "Take a Photo" button. This process corresponds to the process described earlier with reference to Figure 9, and makes it possible to view the event information and uploaded images taken by other users related to that event information.

[0207] Furthermore, the processes in steps S104 to S105 can be repeated as a loop, and a button to proceed to shooting will be displayed in the event information after a predetermined time.

[0208] (Step S106) If a shooting transition button is displayed in the event information in step S104, proceed to step S106.

[0209] In step S106, the user operates (taps) the button to switch to shooting displayed in the event information.

[0210] (Step S107) In step S106, when the user operates (tap) the button to switch to taking a photo displayed in the event information, it becomes possible to take a photo according to the app's specifications, and in step S107, the user takes a photo according to the app's instructions. This process is the same process that was explained earlier with reference to Figures 6 and 7.

[0211] (Step S108) In step S107, when the user completes taking an image in accordance with the app's instructions, in step S108, the UI for setting the upload process of the captured image is displayed on the display unit of the user terminal 20.

[0212] This upload processing setting UI is the same UI described earlier with reference to Figures 7 and 8, and allows users to configure whether or not to upload captured images to an external image management server 120, and if so, whether or not to make the uploaded images public.

[0213] As explained earlier with reference to Figure 7, the upload processing settings UI27 is a UI that allows the user to select from the following three types of processing: (a) If you want to upload with public access, specify "Public" and select "Upload" (b) If you want to upload without public access, specify "Private" and select "Upload" (c) If you do not want to upload, select "Cancel"

[0214] (Steps S109 to S111) Step S109 is a branching step based on user operation on the upload processing setting UI displayed on the user terminal 20 in step S108.

[0215] If the user selects upload, the user's captured image is uploaded to the image management server 120 in step S110. As explained earlier with reference to Figure 8, when the user performs the "upload" process specifying public, a list of images uploaded by other users, along with the image uploaded by the user, is displayed on the user terminal 20.

[0216] On the other hand, if the user does not select to upload, in step S111 the user's captured image is stored in the memory of the user terminal 20, and the process ends.

[0217] Once these processes are complete, the display unit of the user terminal 20 will continue to display a list of event information (queue list) provided by the event information server 110.

[0218] Next, an example of a display control sequence for event information and the shooting transition button displayed on a user terminal 20 such as a smartphone will be explained with reference to the flowchart shown in Figure 25.

[0219] As explained earlier with reference to Figures 4 and 5, for example, the display timing of event information and the shooting transition button for events with a defined event occurrence time is controlled. Specifically, output timing is controlled such that event information is output 30 minutes before the defined event occurrence time, and the shooting transition button is output 5 minutes before the defined event occurrence time.

[0220] This display control process is performed by the event information server 110. Alternatively, it may be performed by the event display application installed on the user terminal 20. The processing of each step in the flowchart shown in Figure 25 will be explained sequentially below.

[0221] (Step S201) First, in step S201, it is determined whether the current date and time is the timing for displaying the event information.

[0222] The timing for displaying event information can be set to various times in advance. For example, if the timing for displaying event information is set to 30 minutes before the event occurs, the system will determine whether the current date and time has reached 30 minutes before the event occurs.

[0223] If the current date and time is not the time for displaying event information, wait. If the current date and time is the time for displaying event information, proceed to step S202.

[0224] (Step S202) If it is determined in step S201 that the current date and time is the timing for displaying event information, the process proceeds to step S202 and the event information is displayed. That is, the event information is output to the user terminal 20.

[0225] (Step S203) Next, in step S203, it is determined whether the current date and time is the timing for displaying the shooting transition button.

[0226] The timing of when the shooting transition button will be displayed can also be set to various times in advance. For example, if the timing of when the shooting transition button will be displayed is set to 5 minutes before the event occurs, the system will determine whether the current date and time has reached 5 minutes before the event occurs.

[0227] If the current date and time is not the time for the "Press to shoot" button to be displayed, wait. If the current date and time is the time for the "Press to shoot" button to be displayed, proceed to step S204.

[0228] (Step S204) If it is determined in step S203 that the current date and time is the timing for displaying the shooting transition button, the process proceeds to step S204 and the shooting transition button is displayed. That is, the shooting transition button is output within the event information displayed on the user terminal 20.

[0229] (Step S205) Steps S205 and below are sequences of control processes for pressing the shooting transition button and stopping the display of event information.

[0230] First, in step S205, it is determined whether the current date and time is the timing at which the display of the shooting transition button stops.

[0231] The timing for stopping the display of the shooting transition button can be set to various times in advance. For example, if the timing for stopping the display of the shooting transition button is set to 15 minutes after the event occurred, the system will determine whether 15 minutes have passed since the event occurred in the current date and time.

[0232] If the current date and time is not the time when the display of the shooting transition button will stop, wait. If the current date and time is the time when the display of the shooting transition button will stop, proceed to step S206.

[0233] (Step S206) If it is determined in step S205 that the current date and time is the timing to stop the display of the shooting transition button, the process proceeds to step S206, and the display of the shooting transition button is stopped. That is, the output of the shooting transition button displayed in the event information displayed on the user terminal 20 is stopped.

[0234] (Step S207) Next, in step S207, it is determined whether the current date and time is the timing for stopping the display of event information.

[0235] The timing for stopping the display of event information can be set in advance to various times. For example, if the timing for stopping the display of event information is set to 30 minutes after the event occurred, the system will determine whether 30 minutes have passed since the event occurred in the current date and time.

[0236] If the current date and time is not the time when the event information display will stop, wait. If the current date and time is the time when the event information display will stop, proceed to step S208.

[0237] (Step S208) If it is determined in step S207 that the current date and time is the time to stop displaying the event information, the process proceeds to step S208, and the display of the event information is stopped. That is, the output of the event information displayed within the event information currently displayed on the user terminal 20 is stopped.

[0238] Furthermore, the process of stopping the display of the shooting transition button may be set to be executed in conjunction with the process of stopping the display of event information. Alternatively, the process of stopping the display of the shooting transition button and the process of stopping the display of event information may be omitted, and the display may be set to be always active. These display control modes can be set on an event information basis. In other words, as explained earlier with reference to Figures 13 and 14, the display timing of event information and the shooting transition button can be arbitrarily set on an event information basis.

[0239] [7. Example of User Terminal Configuration] Next, we will explain an example of a user terminal configuration.

[0240] As explained earlier, the user terminal 20 is comprised of, for example, a smartphone. However, the user terminal is not limited to a smartphone; various devices such as tablet terminals, PCs, and cameras equipped with a camera function for taking still images and videos, a communication function for communicating with external devices, and a display unit for displaying data can be used.

[0241] An example configuration of a user terminal 20, such as a smartphone, will be described with reference to Figure 26. As shown in Figure 26, the user terminal 20 includes an operation unit 201, a storage unit 202, an imaging unit 203, a sensor unit 204, a display unit 205, an audio input unit 206, an audio output unit 207, and a control unit 208.

[0242] The operation unit 201 detects various user operations, such as operations and instructions on applications. These device operations include, for example, touch operations and image capture processing. Touch operations include various contact actions on the display unit 205, such as tapping and scrolling. The operation unit 201 includes, for example, a touch panel, buttons, a keyboard, and a mouse. The operation unit 201 also inputs the detected user operation information to the control unit 208.

[0243] The memory unit 202 is a memory area for temporarily or permanently storing various programs and data. For example, the memory unit 202 stores programs and data for the user terminal 20 to perform various functions. Specifically, the memory unit 202 stores programs for running various applications and management data for managing various settings, etc. However, the above is merely an example, and the types of data stored in the memory unit 202 are not particularly limited.

[0244] The imaging unit 203 captures still images and videos. The imaging unit 203 is equipped with an image sensor. The sensor unit 204 is composed of, for example, a GPS sensor that performs position detection, as well as an acceleration sensor, a gyroscope, a geomagnetic sensor, a vibration sensor, and the like.

[0245] The display unit 205 displays various information based on control by the control unit 208. For example, the display unit 205 displays images, characters, etc., controlled by the application being run. The display unit 205 may be equipped with various display devices, such as a liquid crystal display (LCD) or an OLED (organic light emitting diode) display. The display unit 205 also displays the UI of various applications.

[0246] The audio input unit 206 collects voices and other sounds emitted by the user based on control by the control unit 209. The audio input unit 206 is equipped with a microphone or the like. The audio output unit 207 outputs various types of sounds. The audio output unit 207 is equipped with a speaker and an amplifier.

[0247] The control unit 208 controls each component of the user terminal 20. For example, the control unit 208 executes and controls applications. Furthermore, it performs control processing for image capture using the imaging unit 203, and controls the display of various data on the display unit 205. It also detects user operations on the operation unit 201 and performs control according to the detected information.

[0248] Up to this point, we have described an example of the functional configuration of the user terminal 20. However, the functional configuration described using Figure 26 is merely an example, and the functional configuration of the user terminal 20 in this embodiment is not limited to this example. For example, the user terminal 20 does not necessarily have to have all of the configurations shown in Figure 26, and some components, such as the voice input unit 206, can be provided in a different device from the user terminal 20. The functional configuration of the user terminal 20 in this embodiment can be flexibly modified according to specifications and operation.

[0249] Furthermore, the functions of each component may be performed by a computing device such as a CPU (Central Processing Unit) reading a control program that describes the processing procedures for realizing these functions from a storage medium such as a ROM (Read Only Memory) or RAM (Random Access Memory), interpreting the program, and executing it. Therefore, it is possible to change the configuration used as appropriate depending on the technological level at the time of implementing this embodiment.

[0250] [8. Other Examples] Next, other examples will be described.

[0251] The following embodiments will be described in order. (a) An embodiment that displays event location (or event occurrence location) information along with event information. (b) An embodiment that displays score information in the list data of user-uploaded images. (c) An embodiment that notifies new event information. (d) An embodiment that displays real-time information along with event information. (e) An embodiment that displays the number of users viewing the event information and the number of images taken along with the event information. (f) An embodiment that displays the list data of the image library stored in the image management server 120. (g) An embodiment that uses a first user terminal to take pictures and a second user terminal to upload the images taken by the first user terminal to the image management server. Hereinafter, each of these embodiments will be described with reference to Figure 27 and subsequent figures.

[0252] (a) Figure 27 of the embodiment, which displays event location (or event occurrence location) information along with event information, shows an example of the display data of the user terminal 20 according to this embodiment.

[0253] In the lower area of ​​the display unit of the user terminal 20 shown in Figure 27, event information 08, 21-8 generated by the event information provision server 110 is displayed. This event information 08, 21-8 is event information related to a character show.

[0254] Furthermore, the upper area of ​​the display unit of the user terminal 20 displays a map data that includes the location where the event information 08, 21-8, i.e., the character show, will be held, i.e., the filming location information 251, which is displayed in the lower area.

[0255] Users can view the location map data, which includes location information 251 displayed alongside the event information, to confirm the location of the event. This allows them to arrive at the event area quickly and take the desired photos and videos.

[0256] (b) An example of displaying score information in a list of user-uploaded images Next, an example of displaying score information in a list of user-uploaded images will be described.

[0257] As explained earlier with reference to Figure 8, etc., images taken by a user using the user terminal 20 can be uploaded to and saved on the image management server 120. Furthermore, the uploaded images can be viewed as a list of data along with images taken by other users.

[0258] As shown in Figure 28, this embodiment displays scores, which are evaluation results from multiple users, along with a list of images uploaded to and held by the image management server 120. As shown in Figure 28, score information 252 is displayed along with each image in the image list data. This score information 252 is a score value calculated based on the evaluation value set by each user who viewed the image.

[0259] By displaying a score value alongside each image in this way, users can quickly find popular images among a large number of images.

[0260] As mentioned earlier, users can also retrieve uploaded images, for example, by purchasing them at a predetermined price or obtaining them for free. These image purchase and transfer processes will be carried out according to the regulations of the image management server.

[0261] (c) Example of notifying new event information Next, an example of notifying new event information will be described.

[0262] As explained earlier with reference to Figures 16 to 19, the event information provision server 110 may provide new real-time event information to the user terminal 20 based not only on pre-generated event information, but also on real-time event analysis information received from the information analysis processing execution server 130 shown in Figure 16, such as progress information of a baseball game.

[0263] In such cases, the event information server 110 executes a process to notify the user terminal 20 that new event information has been generated. The notification process for new event information differs depending on whether the user is running an application on the user terminal 20 and viewing the list of event information (queue list), or whether the user is not running an application on the user terminal 20.

[0264] Figure 29, "(c1) Example of process for notifying event information (while application is running)," shows an example of a new event information notification process when the user is running an application on the user terminal 20 and displaying a list of event information (queue list). In this case, the new event information is displayed over the list of event information (queue list) currently displayed on the user terminal 20, covering almost the entire area of ​​the display on the user terminal 20. Furthermore, a notification sound is output to inform the user that new event information has occurred. Through these processes, the user can immediately know that new event information has occurred.

[0265] On the other hand, Figure 30, "(c2) Example of process for notifying event information (when the app is stopped)," is an example of the process for notifying new event information when the user is not running the app on the user terminal 20. In this case, as shown in Figure 30, a notification message is displayed on the user terminal 20 indicating that new event information has been generated. For example, the message may read: "There is new event information. Launch the app to check the event information. Tap here." Furthermore, a notification sound is output to notify the user that new event information has occurred.

[0266] These processes allow users to immediately know when new event information has occurred and to tap the message area to instantly view the new event information.

[0267] (d) An example of displaying real-time information along with event information Next, an example of displaying real-time information along with event information will be described.

[0268] As explained earlier with reference to Figures 16 to 19, the event information provision server 110 receives real-time information from the information analysis processing execution server 130 shown in Figure 16, such as progress information of a baseball game, specifically score information, ball count information, batter and pitcher information, and various other real-time information such as the pitcher's ball speed.

[0269] The event information server 110 provides this real-time information along with the event information provided to the user terminal and displays it on the user terminal 20. The example shown in Figure 31 is an example in which baseball score information, ball count information, etc., are displayed along with event information related to a baseball game.

[0270] Users can perform tasks such as deciding on photo opportunities while checking this real-time information.

[0271] (e) An example of displaying the number of users viewing the event information and the number of images taken along with the event information Next, an example of displaying the number of users viewing the event information and the number of images taken along with the event information will be described.

[0272] The event information server 110 provides a large amount of event information to many users. This large amount of event information includes various types of events, such as popular events and unpopular events.

[0273] If the event information server 110 provides a large amount of event information, users may be confused about which event information to use for taking pictures. To solve this problem, information such as the number of users viewing each event information and the number of images taken corresponding to each event information will be displayed as a guide for selecting event information.

[0274] The example shown in Figure 32 displays the number of users viewing the event information (261) and the number of event-related images taken (uploaded images) (262) along with the event information displayed on the user terminal 20. This data is generated by the event information provision server 110 using management information from the event information provision server 110 and the image management server 120, and is provided from the event information provision server 110 to the user terminal 20.

[0275] Users can use this data as a guide to select event information to use for image capture, enabling them to efficiently select event information from a large number of events.

[0276] (f) An embodiment of displaying a list of image libraries stored in the image management server 120 Next, an embodiment of displaying a list of image libraries stored in the image management server 120 will be described.

[0277] As described above, when a user performs an action (tap) on the shooting transition button 22 in the event information 21 displayed on the user terminal 20 and takes a picture, the captured image can be uploaded to the image management server 120, and the uploaded image is stored in the memory unit of the image management server 120.

[0278] The specific processing sequence will be explained with reference to Figure 33. As shown in Figure 33 (step S301), the user operates (tap) the shooting transition button 22 in the event information 21 displayed on the user terminal 20, and then, as shown in Figure 33 (step S302), the user performs image capture.

[0279] Once image capture is complete, an upload UI is displayed along with the captured image 26, as shown in Figure 33 (step S303). By operating this UI, the captured image can be uploaded to the image management server 120. The uploaded image is stored in the memory unit of the image management server 120.

[0280] As mentioned above, while it is possible to take normal photos by launching a separate, independent camera app, if the app is not linked, the image upload process to the image management server 120 mentioned above cannot be automatically performed after taking a picture. In this case, it is necessary to upload the image using the "Gallery" function of the media selection UI 25 mentioned above after taking a picture.

[0281] However, by following a predetermined procedure and specifying the image management server 120 as the upload destination for captured images, it is possible to upload regular camera images that are not related to event information to the image management server 120 immediately after capture.

[0282] This specific processing sequence will be explained with reference to Figure 34. As shown in step S311 of Figure 34, the user operates (tap) the camera icon 271 displayed on the application screen (event information provision application) at the bottom of the user terminal 20 to activate the camera. This user operation activates the camera application, and then, as shown in step S312 of Figure 34, the user takes an image.

[0283] Once image capture is complete, in Figure 34 (step S313), the user specifies the image management server 120 as the upload destination for the captured images, and can upload these normal captured images to the image management server 120. During the upload process, the user can specify either "public," which allows the uploaded images to be made public to third parties, or "private," which does not allow them to be made public to third parties. The uploaded images are stored in the memory unit of the image management server 120.

[0284] In this way, users can upload to the image management server 120 not only event-related images taken by operating the shooting transition button within the event information, but also regular images taken by operating the camera icon (second shooting transition button) displayed in a location independent of the event information.

[0285] Furthermore, users can view images uploaded to the image management server 120 on their user terminal 20. As shown in Figure 35, user 10 can upload any of the following images (still images and videos) taken using the user terminal 20 to the image management server 120: (a) Event-related images taken by operating the shooting transition button in the event information; (b) Normal images taken by operating the camera icon displayed in a location independent of the event information.

[0286] The image management server 120 stores images uploaded from the user terminal 20 in its image information storage unit.

[0287] Users can upload images to the image management server 120 and view the images stored in the storage unit of the image management server 120 on their user terminal 20. The image viewing process for event-related images is as previously explained with reference to Figures 8 and 9. The list images explained earlier with reference to Figures 8 and 9 are a list of images taken by many users following the recommendations of the same event information, and are a list of images taken at approximately the same time. This process corresponds to the process when the "Event-Related Image List Display" shown in Figure 35 is executed.

[0288] The user can perform a different image list display process from this "event-related image list display" using the user terminal 20. This process is the "library image list display" process shown in Figure 35.

[0289] The "Display Library Image List" process can be executed by user operation on the user terminal 20. By instructing the user terminal 20 to execute "Display Library Image List," the user can view on the user terminal 20 all images stored in the memory of the image management server 120, namely: (a) event-related images taken by operating the shooting transition button in the event information; and (b) normal images taken by operating the camera icon displayed in a location independent of the event information. All of these captured images (still images and videos) can be viewed on the user terminal 20. Note that the images that can be displayed are limited to those uploaded with the "Public" designation, in the case of images taken by other people.

[0290] Referring to Figure 36, an example of the display data shown on the user terminal 20 when the user executes "Display Library Image List" using the user terminal 20 will be explained.

[0291] Figure 36 shows an example of displaying library image list data 270 on the user terminal 20. The library image list data 270 is display data that combines the following two types of display areas: (a) Thumbnail image list display area 271 of normal captured images (b) Event information corresponding captured image display area 272

[0292] "(a) The thumbnail image list display area 271 for normal captured images" displays a list of normal camera captured images that are not related to the event information, as explained earlier with reference to Figure 34. The displayed images are reduced images (thumbnail images). On the other hand, "(b) The event information-related captured image display area 272" displays event information-related images that the user has captured and uploaded by operating the shooting transition button within the event information, as explained earlier with reference to Figure 33, as well as other information related to the event.

[0293] The right side of Figure 36 shows specific examples of the following two types of display areas: (a) Thumbnail image list display area 271 for normal captured images (b) Event information-compatible captured image display area 272

[0294] As described above, the "(a) Thumbnail image list display area 271 for normal captured images" displays a list of normal camera captured images that are not related to event information. The image size of each image displayed in this display area may be uniform or set to be different. For example, a score similar to that explained earlier with reference to Figure 28 may be set for each image, and the image with the highest score may be displayed in a larger size.

[0295] On the other hand, the "(b) Event Information Compatible Captured Image Display Area 272" displays event information-related images that the user has captured and uploaded by operating the capture transition button within the event information, as well as other event-related information. As shown on the right side of Figure 36, one large image is displayed in the upper right, and a row of smaller images is displayed at the bottom. Event-related information is displayed in the upper left. This information is generated by the event information provision server 110 and is provided to the user terminal 20 via the image management server 120.

[0296] Thus, the library image list display data 270 displayed on the user terminal 20 is display data that contains a mixture of the following two types of display areas: (a) a thumbnail image list display area 271 of normal captured images (b) an event information-compatible captured image display area 272 These are displayed, for example, as time-series data.

[0297] Referring to Figure 37, an example of the display of the library image list data 270 will be explained. As shown in Figure 37, the library image list data 270 displayed on the user terminal 20 is data that displays the following two types of display areas in chronological order: (a) Thumbnail image list display area 271 of normal captured images (b) Event information corresponding captured image display area 272

[0298] Images taken more recently are displayed at the top of the display unit on the user terminal 20, and images taken more recently are displayed at the bottom of the display unit on the user terminal 20. As shown in the figure, the user can scroll the screen of the display unit on the user terminal 20, and can sequentially view images from the oldest to the newest by scrolling.

[0299] Figure 38 shows specific examples of multiple "(b) Event Information Corresponding Captured Image Display Area 272" included in the time-series display of library image list data 270. On the right side of Figure 38, three specific examples of event information corresponding captured image display areas 272 are shown, from bottom to top as 272a to 272c, and examples of the display data for these three event information corresponding captured image display areas 272.

[0300] The lower data represents older data than the upper data, i.e., data where the event occurrence time is related to a previous event, while the upper data represents newer data than the lower data, i.e., data where the event occurrence time is related to a newer event.

[0301] In the example shown in Figure 38, the lowest event information corresponding captured image display area 272a displays images taken at the time of entry into the baseball stadium, which is the timing of the event occurrence, as well as event-related information obtained at that time.

[0302] The timing of entry into the baseball stadium varies from user to user, and the timing of image capture also varies from user to user. However, the images displayed in the event information corresponding to captured images display area 272a at the very bottom are images taken by the user when they operate the capture transition button in the event information related to the baseball stadium entry event provided to the user terminal 20 by the event information provision server 110. In other words, these are image data stored in the memory unit of the image management server 120 in association with the baseball stadium entry event.

[0303] The central event information corresponding captured image display area 272b displays the image captured at the moment when player Suzuki hit a home run during a baseball game, as well as event-related information obtained at that time.

[0304] The uppermost event information corresponding captured image display area 272c displays images taken at the start of the 7th inning, which is the event occurrence timing in a baseball game, as well as event-related information obtained at that time.

[0305] Referring to Figure 39 and following, the specific configuration of the display data in these three event information-corresponding captured image display areas 272a to 272c will be explained.

[0306] First, with reference to Figure 39, the display data of the event information-compatible captured image display area 272a will be explained. The event information-compatible captured image display area 272a displays images taken at the time of entry into the baseball stadium, as well as event-related information obtained at that time.

[0307] As shown in Figure 39, the event information-corresponding captured image display area 272a is composed of the following three display units: (1) Event-related information display unit 281 (2) Representative image display unit 282 (3) User-uploaded image list display unit 283

[0308] (1) The event-related information display unit 281 displays information related to the event. In this example, the event is admission to a baseball stadium, and the information related to this event, such as the number of spectators, weather, and temperature, is displayed. As mentioned above, this event-related information is generated by the event information provision server 110 and provided to the user terminal 20 via the image management server 120.

[0309] (2) The representative image display unit 282 is an area that displays a representative image selected from a large number of images taken by many users based on event information. For example, a score similar to that explained earlier with reference to Figure 28 is calculated for each uploaded image, and the image with the highest score is displayed in a larger size. In addition to selecting from images taken by users, the representative image display unit 282 may also display an image taken by the event management side and stored in the event information storage unit 113 of the event information provision server 110 as a representative image.

[0310] The "(3) User-uploaded image list display unit 283" displays uploaded images other than the representative image, that is, numerous images taken by multiple users based on the same event information (= baseball stadium entry event). This display area can be scrolled by the user, allowing them to view multiple images by scrolling.

[0311] Next, with reference to Figure 40, the display data of the event information-corresponding captured image display area 272b will be explained. The event information-corresponding captured image display area 272b displays images taken at the moment when player Suzuki hit a home run during a baseball game, as well as event-related information obtained at that time.

[0312] The "(1) Event-related information display unit 281" displays information related to the event. In this example, the event is Suzuki's home run, and the information related to this event is displayed, including information about the batter Suzuki, the distance of the home run, and the speed of the batted ball. As mentioned above, this event-related information is generated by the event information provision server 110 and provided to the user terminal 20 via the image management server 120.

[0313] (2) The representative image display unit 282 displays a representative image selected from a large number of images taken by many users at the time a home run occurred, based on event information. As mentioned above, for example, a score similar to that explained earlier with reference to Figure 28 is calculated for each uploaded image, and the image with the highest score is displayed in a larger size.

[0314] The "(3) User-uploaded image list display unit 283" displays uploaded images other than the representative image, that is, numerous images taken by multiple users based on the same event information (= Suzuki's home run). This display area can be scrolled by the user, allowing them to view multiple images by scrolling.

[0315] Next, referring to Figure 41, the display data of the event information-compatible captured image display area 272c will be explained. The event information-compatible captured image display area 272c displays images taken at the start of the 7th inning, the final stages of a baseball game, as well as event-related information obtained at that time.

[0316] The "(1) Event-related information display unit 281" displays information related to the event. In this example, the event is the start of the 7th inning, and the information related to this event includes information such as the cheerleading team's support and cheering messages related to the 7th inning. As mentioned above, this event-related information is generated by the event information provision server 110 and provided to the user terminal 20 via the image management server 120.

[0317] (2) The representative image display unit 282 displays a representative image selected from a large number of images taken by many users at the start of seven attacks based on event information. As mentioned above, for example, a score similar to that explained earlier with reference to Figure 28 is calculated for each uploaded image, and the image with the highest score is displayed in a larger size.

[0318] The "(3) User-uploaded image list display unit 283" displays uploaded images other than the representative image, that is, numerous images taken by multiple users based on the same event information (= 7 attack initiation events). This display area can be scrolled by the user, allowing them to view multiple images by scrolling.

[0319] In addition, while the library image list data 270 described with reference to Figure 36 and subsequent figures was shown as being displayed across the entire display area of ​​the user terminal 20, it is also possible to set it to display the library image list data 270 in an area other than the display area of ​​the event information 21, for example, as shown in Figure 42.

[0320] In this example of display data, the display area of ​​the library image list data 270 can be scrolled by the user, allowing the user to view and check images, event information, etc., from the oldest data to the newest data by scrolling.

[0321] Furthermore, regarding the display area of ​​event information 21, users can view different event information by scrolling left and right.

[0322] (g) An embodiment using a first user terminal for taking images and a second user terminal for uploading the images taken by the first user terminal to an image management server Next, an embodiment using a first user terminal for taking images and a second user terminal for uploading the images taken by the first user terminal to an image management server will be described.

[0323] In the embodiment described above, it was explained that, for example, a single smartphone is used as the user terminal to perform all processes such as image capture and image uploading. However, the terminal that captures images and the terminal that uploads the captured images to the image management server 120 may be configured as separate terminals.

[0324] For example, a device such as a camera is designated as the first user terminal that takes pictures, and a smartphone, tablet, or PC is designated as the second user terminal that receives the images taken by the camera (first user terminal) and uploads them to the image management server 120.

[0325] Multiple user terminals can be combined in this way to perform image capture and image upload processing. The event information provided by the event information server 110 can be sent to either the camera (first user terminal), a smartphone, tablet, or PC (second user terminal), or to one of them. An example of operation when the first user terminal is a camera and the second user terminal is a smartphone will be explained further. In this example, event information is sent only to the smartphone. The camera and smartphone are connected, for example, via Wi-Fi Direct. When the user operates (tap) the shooting transition button 22 in the event information 21 on the display screen of the smartphone receiving the event information, as shown in Figure 6, a new option, "Import from external camera," becomes available on the media selection UI 25, in addition to the options explained in Figure 6, etc. When the user selects "Import from external camera," the smartphone accesses the camera's internal memory and displays images (still images, videos) already captured by the camera on the smartphone screen. The user can then select the images they want to upload from the images already captured by the camera while viewing them on the smartphone screen. Images selected by the user for upload are further specified as public or private on the smartphone before being uploaded to the image management server 120. This configuration allows users to primarily use the event information app on their smartphones to understand event information and perform various settings operations, while using a dedicated camera for photography, enabling them to capture higher quality images.

[0326] [9. Hardware Configuration Examples of Information Processing Devices] Next, with reference to Figure 43, we will describe an example of a hardware configuration of an information processing device that can be used as a user terminal 20, an information provision server 110, or an image management server 120.

[0327] The CPU (Central Processing Unit) 301 functions as a control unit and data processing unit that execute various processes according to the program stored in the ROM (Read Only Memory) 302 or the storage unit 308. For example, it executes processing according to the sequence described in the above embodiment. The RAM (Random Access Memory) 303 stores the program and data that the CPU 301 executes. These CPU 301, ROM 302, and RAM 303 are interconnected by a bus 304.

[0328] The CPU 301 is connected to the input / output interface 305 via the bus 304. The input / output interface 305 is connected to an input unit 306 consisting of various switches, a keyboard, a mouse, a microphone, etc., and an output unit 307 that performs data output to a display unit, a speaker, etc. The CPU 301 performs various processes in response to commands input from the input unit 306 and outputs the processing results to, for example, the output unit 307.

[0329] The storage unit 308, connected to the input / output interface 305, consists of, for example, flash memory, a hard disk, etc., and stores programs executed by the CPU 301 and various data. The communication unit 309 functions as a transmitting and receiving unit for data communication via Wi-Fi communication, mobile wireless communication, Bluetooth® (BT) communication, and other networks such as the Internet and local area networks, and transmits and receives data with external devices using wired or wireless communication.

[0330] The drive 310 connected to the input / output interface 305 drives removable media 311 such as magnetic disks, optical disks, magneto-optical disks, or semiconductor memory such as memory cards, and performs data recording or reading.

[0331] [10. Summary of the Structure of the Disclosure] The embodiments of the Disclosure have been explained in detail above with reference to specific examples. However, it is obvious that a person skilled in the art can modify or substitute the embodiments without departing from the gist of the Disclosure. In other words, the present invention has been disclosed in the form of examples and should not be interpreted restrictively. In order to determine the gist of the Disclosure, the claims section should be considered.

[0332] Furthermore, the technology disclosed in this specification may have the following configuration: (1) An information processing device having a control unit for executing an application, wherein the control unit executes the application and performs a process to display event information on a display unit to assist the user in taking an image, and the event information includes information on a target to be photographed.

[0333] (2) The information processing device described in (1), wherein the event information includes shooting time information indicating the timing of shooting.

[0334] (3) The information processing device described in (1) or (2), which includes location information indicating the location to be photographed as the event information.

[0335] (4) The information processing device described in any of (1) to (3), which includes a shooting transition button, which is an operation unit for transitioning to image capture, for the event information.

[0336] (5) The control unit is an information processing device according to any one of (1) to (4) that receives the event information from the event information provision server and performs the process of displaying it on the display unit.

[0337] (6) The control unit is an information processing device according to any one of (1) to (5) that receives multiple event information from an event information provision server and performs a process of listing the received multiple event information and displaying it on a display unit.

[0338] (7) The information processing device according to any one of (1) to (6), wherein the control unit executes a process to display event information relating to an event for which an event occurrence time has been defined, before the defined time of the event occurrence.

[0339] (8) The control unit, with respect to event information relating to an event for which an event occurrence time has been defined, executes a process to display a shooting transition button, which is an operation unit for transitioning to image capture, before the defined time for the event occurrence time, as described in any of (1) to (7).

[0340] (9) The control unit receives pre-generated event information generated in advance from the event information provision server, as well as real-time event information generated in real time, and displays both the received pre-generated event information and the real-time event information on the display unit.

[0341] (10) The control unit is an information processing device according to any one of (1) to (9) that performs event information display processing and display stop processing according to event information display date and time information and event information display stop date and time information set for each event information unit.

[0342] (11) The control unit is an information processing device according to any one of (1) to (10) that performs a display process for the shooting transition button according to the display date and time information of the shooting transition button corresponding to the event information set for each event information unit.

[0343] (12) The information processing device according to any one of (1) to (11), wherein the control unit receives user-specific event information selected based on user preference information pre-registered in the event information providing server that provides the event information, and displays it on the display unit.

[0344] (13) The control unit is an information processing device mounted on any of (1) to (12) that, in response to detection of a user operation on the shooting transition button, which is an operation unit for transitioning to image capture displayed in the event information, controls the user to perform image capture.

[0345] (14) The control unit, after a user operation on the shooting transition button, displays a UI for uploading the captured image to the image management server when the user has taken an image.

[0346] (15) The information processing device according to any one of (1) to (14), wherein the control unit detects a user operation on the event information area displayed on the display unit and displays on the display unit images taken by other users that have been uploaded to the image management server.

[0347] (16) Information processing device comprising a communication unit that performs communication with a user terminal, and an event information generation unit that generates event information to be provided to the user terminal, wherein the event information generation unit generates event information that assists the user in taking images, and includes shooting target information indicating the object to be photographed, and provides the event information to the user terminal.

[0348] (17) The information processing device according to (16), wherein the event information generation unit generates event information including at least one of the following: shooting time information indicating the timing of the user taking an image, or shooting location information indicating the location where the user took the image, and provides it to the user terminal.

[0349] (18) An information processing system having an event information providing server and a user terminal, wherein the event information providing server has a communication unit that performs communication with the user terminal and an event information generation unit that generates event information to be provided to the user terminal, the event information generation unit generates event information that assists a user using the user terminal in taking pictures, and includes shooting target information indicating the object to be photographed, and transmits it to the user terminal, and the user terminal is an information processing system that performs processing to receive the event information from the event information providing server and display it on a display unit.

[0350] (19) An information processing method to be performed in an information processing device, wherein the information processing device has a control unit that executes an application, the control unit executes the application and performs a process to display event information that assists the user in taking an image on a display unit, and the event information is information that includes a target to be photographed.

[0351] (20) A program that causes an information processing device to execute information processing, wherein the information processing device has a control unit that executes an application, and the program causes the control unit to execute the application and to display event information that assists the user in taking an image on a display unit, wherein the event information is information that includes a target to be photographed.

[0352] Furthermore, the series of processes described in the specification can be executed by hardware, software, or a combination of both. When executing processes by software, a program recording the processing sequence can be installed and executed in the memory of a computer embedded in dedicated hardware, or the program can be installed and executed on a general-purpose computer capable of executing various processes. For example, the program can be pre-recorded on a recording medium. In addition to installing from the recording medium to a computer, the program can also be received via a network such as a LAN (Local Area Network) or the Internet and installed on a recording medium such as a built-in hard disk.

[0353] Furthermore, the various processes described in this specification may not only be executed sequentially as described, but may also be executed in parallel or individually as needed, depending on the processing capacity of the device performing the process. In addition, in this specification, a system is a logical combination of multiple devices, and the devices in each configuration are not limited to being located in the same enclosure.

[0354] As described above, according to the configuration of one embodiment of this disclosure, a configuration is realized in which information assisting image capture using a user terminal such as a smartphone is provided to the user. Specifically, for example, an event information provision server provides event information to a user terminal such as a smartphone, which serves as information assisting the user when taking pictures. Specifically, this event information includes information on the subject to be photographed, information on the shooting location, and information on the shooting time. A user taking pictures using a user terminal can refer to the event information to obtain optimal information regarding the subject, shooting location, and shooting time, thereby enabling them to take pictures without missing a photo opportunity. With these configurations, a configuration is realized in which information assisting image capture using a user terminal such as a smartphone is provided to the user.

[0355] 10 User 20 User Terminal 21 Event Information 22 Shooting Transition Button 23 Event Occurrence Location Information 24 Event Occurrence Time Information 25 Media Selection UI 26 Captured Image 27 Upload Processing Settings UI 28 Uploaded Image 29 User Uploaded Image List 30 Event Venue 100 Information Processing System 110 Event Information Provision Server 111 Event-Related Information Storage Unit 112 Event Information Generation and Registration Unit 113 Event Information Storage Unit 114 User Information Storage Unit 115 Output Event Information (& Shooting Transition Button) Generation Unit 116 Event Information (& Shooting Transition Button) Output Control Unit 117 User Information Registration Unit 120 Image Management Server 130 Information Analysis Processing Execution Server 151 User Information 152 User-Related Event Information 201 Operation Unit 202 Storage Unit 203 Imaging Unit 204 Sensor Unit 205 Display Unit 206 Audio Input Unit 207 Audio output unit 207 Control unit 251 Shooting location information 252 Score information 261 Number of users viewing event information 262 Number of event information related images taken 270 Library image list display data 271 Thumbnail image list display area for normal shooting images 272 Event information related shooting image display area 281 Event related information display unit 282 Representative image display unit 283 User uploaded image display unit 301 CPU 302 ROM 303 RAM 304 Bus 305 Input / output interface 306 Input unit 307 Output unit 308 Storage unit 309 Communication unit 310 Drive 311 Removable media

Claims

1. An information processing device having a control unit for executing an application, wherein the control unit executes the application and performs a process to display event information on a display unit to assist the user in taking an image, and the event information includes information on a target to be photographed.

2. The information processing device according to claim 1, wherein the event information includes shooting time information indicating the timing of shooting.

3. The information processing device according to claim 1, wherein the event information includes shooting location information indicating the location to be photographed.

4. The information processing device according to claim 1, which includes a shooting transition button, which is an operation unit for transitioning to image capture, for the event information.

5. The information processing apparatus according to claim 1, wherein the control unit receives the event information from the event information provision server and performs the process of displaying it on the display unit.

6. The information processing apparatus according to claim 1, wherein the control unit receives multiple event information from an event information provision server and performs a process of listing the received multiple event information and displaying it on the display unit.

7. The information processing apparatus according to claim 1, wherein the control unit performs a process to display event information relating to an event for which an event occurrence time has been defined, before the defined time of the event occurrence.

8. The information processing apparatus according to claim 1, wherein the control unit performs a process to display a shooting transition button, which is an operation unit for transitioning to image capture, before the specified time of the event occurrence, for event information relating to an event for which the event occurrence time has been specified.

9. The information processing apparatus according to claim 1, wherein the control unit receives real-time event information generated in real time, in addition to pre-generated event information generated in advance from an event information provision server, and displays both the received pre-generated event information and the real-time event information on the display unit.

10. The information processing apparatus according to claim 1, wherein the control unit performs event information display processing and event information display stop processing according to event information display date and time information and event information display stop date and time information set for each event information unit.

11. The information processing apparatus according to claim 1, wherein the control unit performs a display process for the shooting transition button according to the display date and time information of the shooting transition button corresponding to the event information set for each event information unit.

12. The information processing apparatus according to claim 1, wherein the control unit receives user-specific event information selected based on user preference information pre-registered in the event information providing server that provides the event information, and displays it on the display unit.

13. The information processing apparatus according to claim 1, wherein the control unit detects a user operation on the shooting transition button, which is an operation unit for transitioning to image capture displayed in the event information, and controls the user to enable image capture.

14. The information processing apparatus according to claim 13, wherein, after a user operation on the shooting transition button, the control unit displays a UI for uploading the captured image to the image management server.

15. The information processing apparatus according to claim 1, wherein the control unit detects a user operation on the event information area displayed on the display unit and displays a captured image of another user that has been uploaded to the image management server on the display unit.

16. An information processing device comprising a communication unit that performs communication with a user terminal, and an event information generation unit that generates event information to be provided to the user terminal, wherein the event information generation unit generates event information that assists the user in taking images, and includes shooting target information indicating the object to be photographed, and provides this event information to the user terminal.

17. The information processing device according to claim 16, wherein the event information generation unit generates event information including at least one of the following: shooting time information indicating the timing of image capture by the user, or shooting location information indicating the location where the user took the image, and provides it to the user terminal.

18. An information processing system comprising an event information provision server and a user terminal, wherein the event information provision server comprises a communication unit that performs communication with the user terminal and an event information generation unit that generates event information to be provided to the user terminal, the event information generation unit generates event information that assists the user using the user terminal in taking images, and includes target information indicating the object to be photographed, and transmits it to the user terminal, and the user terminal is an information processing system that receives the event information from the event information provision server and performs the process of displaying it on a display unit.

19. An information processing method to be performed in an information processing device, wherein the information processing device has a control unit that executes an application, and the control unit executes the application and performs a process to display event information on a display unit that assists the user in taking an image, wherein the event information includes information on a target to be photographed.

20. A program that causes an information processing device to execute information processing, wherein the information processing device has a control unit that executes an application, and the program causes the control unit to execute the application and display event information on a display unit that assists the user in taking an image, wherein the event information is information that includes a target to be photographed.

Images