Photographed image management system

Abstract

To provide a photographed image management system that allows a user to quickly check a photographed image related to the user.SOLUTION: A photographed image management system connected to a terminal comprises: a ticket identification information acquisition unit that acquires, from a ticket acquired by a user, ticket identification information identifying the ticket; a photographing unit that photographs people including the user, and a server that acquires a photographed image photographed by the photographing unit via a network, and stores the photographed image in linkage with the ticket identification information acquired by the ticket identification information acquisition unit. The server receives input of the ticket identification information from the terminal, and outputs, to the terminal, at least part of one or more photographed images linked directly or indirectly to the ticket identification information.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present invention relates to a photographed image management system capable of outputting an image of a user to a terminal.

Background Art

[0002] In parks such as theme parks and amusement parks, there is a service that automatically photographs users enjoying attractions and allows the users to purchase the photos displayed after the attraction ends. There is also a service that allows users to select a photographed image from a list of photographed images displayed on a large display after the attraction ends and purchase a photo. Patent Document 1 discloses a service in which a theme park automatically photographs the scenery of a jet coaster on which a customer has ridden, and the customer checks their own photographed image among the photographed images displayed on a large display and then purchases it at a sales booth.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When there are many users, it takes time to find oneself, family members, etc. from many photos and photographed images. Since users cannot find themselves, family members, etc. from photos and photographed images in a short time, they may postpone purchasing.

Means for Solving the Problems

[0005] The photographed image management system of the present invention is a photographed image management system connected to a terminal, a ticket identification information acquisition unit that acquires ticket identification information for identifying a ticket acquired by a user from the ticket, A photographing unit that photographs a person including the user; A server that acquires a photographed image photographed by the photographing unit via a network, associates the photographed image with the ticket identification information acquired by the ticket identification information acquisition unit, and stores the photographed image; The server has a mode of receiving an input of the ticket identification information from the terminal and outputting at least a part of one or more photographed images directly or indirectly associated with the ticket identification information to the terminal.

Brief Description of the Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

MODE FOR CARRYING OUT THE INVENTION

[0007] Hereinafter, embodiments of the present invention will be described. Of course, the following embodiments are merely illustrative of the present invention, and not all of the features shown in the embodiments are necessarily essential to the solution means of the invention.

[0008] (1) Outline of the aspects included in the present invention: First, an outline of the aspects included in the present invention will be described with reference to the examples shown in FIGS. 1 to 15. Note that the drawings of the present application are diagrams schematically showing examples, and the magnification ratios in each direction shown in these drawings may be different, and the drawings may not be consistent. Of course, each element of this aspect is not limited to the specific examples indicated by the reference numerals. In the "outline of the aspects included in the present invention", the content in parentheses means a supplementary explanation of the immediately preceding word.

[0009] As illustrated in FIGS. 1 and 3, a photographing image management system SY1 according to one aspect is a photographing image management system SY1 connected to a terminal 200, and includes a ticket identification information acquisition unit 30, a photographing unit 40, and a server 100. The ticket identification information acquisition unit 30 acquires ticket identification information IDT0 for identifying a ticket TI0 acquired by a user US0 from the ticket TI0. The photographing unit 40 photographs a person including the user US0. The server 100 acquires a photographed image IM0 photographed by the photographing unit 40 via a network NE1, associates the photographed image IM0 with the ticket identification information IDT0 acquired by the ticket identification information acquisition unit 30, and stores the photographed image IM0. The server 100 receives an input of the ticket identification information IDT0 from the terminal 200, and outputs at least a part of one or more photographed images IM0 directly or indirectly associated with the ticket identification information IDT0 to the terminal 200.

[0010] The above-described server 100 stores a photographed image IM0 associated with identification information of a ticket TI0 acquired by a user US0. When the ticket identification information IDT0 is input to the terminal 200, at least a part of one or more photographed images IM0 directly or indirectly associated with the ticket identification information IDT0 is output to the terminal 200. The user US0 can confirm the photographed image IM0 related to himself / herself on the terminal 200. Therefore, the above aspect can provide a photographing image management system that enables a user to quickly confirm a photographed image related to himself / herself.

[0011] In addition, various examples can be cited in the above-described aspect. The terminal may be a computer installed in a theme park, a park in an amusement park, etc., or a computer such as a mobile terminal used by a user. The ticket identification information may be printed information such as a ticket number, a two-dimensional code, or a barcode printed on the ticket, display information, or recorded information such as an IC (Integrated Circuit) tag or a magnetic recording layer recorded on the ticket. The captured images indirectly associated with the ticket identification information include captured images associated with the identification information of tickets obtained by users other than a certain user included in the group.

[0012] This captured image management system SY1 may include the ticket identification information acquisition unit 30 and the imaging unit 40 in each of a plurality of areas (for example, areas A1 to A4). For each of the areas (A1 to A4), the server 100 may associate the captured image IM0 acquired from the imaging unit 40 existing in the area (A1 to A4) with the ticket identification information IDT0 acquired by the ticket identification information acquisition unit 30 existing in the area (A1 to A4). The server 100 may output at least a part of one or more captured images IM0 directly or indirectly associated with the ticket identification information IDT0 for the plurality of areas (A1 to A4) to the terminal 200. In the above case, since the captured images IM0 of the plurality of areas (A1 to A4) are associated with the user US0 and output to the terminal 200, convenience is improved.

[0013] The server 100 may associate the face image FA0 of the user US0 with the ticket identification information IDT0. The server 100 may associate the captured image IM0 with the ticket identification information IDT0 by performing face recognition based on the face image FA0 on the captured image IM0 not associated with the ticket identification information IDT0. In the above case, even when it is difficult to identify the position of the user, such as in the case of unreserved seats, etc., the captured images related to the user can be provided to the user.

[0014] This captured image management system SY1 may further include a printing unit 50 for printing the captured image IM0. The server 100 may receive a selection of a purchase target image IMp from the terminal 200 from among one or more captured images IM0 directly or indirectly associated with the ticket identification information IDT0. The server 100 may cause the printing unit 50 to print the purchase target image IMp. In the above case, it is possible to provide a photographed image management system that enables a user to promptly purchase a printed matter of a photographed image related to the user himself / herself.

[0015] Furthermore, the above-described mode is applicable to the server included in the above-described photographed image management system, the photographed image management method corresponding to the above-described photographed image management system, the control method of the above-described server, the control program of the above-described server, a computer-readable non-transitory medium recording the control program, etc. The above-described server may be composed of a plurality of distributed parts.

[0016] (2) Specific example of the photographed image management system: FIG. 1 schematically illustrates a photographed image management system SY1 of a park 10. FIG. 2 schematically illustrates ticket identification information IDT0 assigned to each group user USi. FIG. 3 schematically illustrates the configuration of the photographed image management system SY1. The park 10 shown in FIG. 1 is a theme park and has a plurality of areas A1, A2, A3, A4 equipped with attractions, a service center 12, a ticket center 13, etc. There is an entrance gate 11 at the entrance of the park 10, and area entrance gates 21, 22, 23, 24 for entering areas A1 to A4 are provided at the entrances of areas A1 to A4, respectively. The park 10 shown in FIG. 1 is provided with a photographed image management system SY1 including a ticket identification information acquisition unit 30, a photographing unit 40, a printing unit 50, and a server (server computer) 100. Note that although the server 100 shown in FIG. 1 is in the ticket center 13, the server 100 may be in another location within the park 10 such as the service center 12, or may be outside the park 10.

[0017] The service center 12 is equipped with, for example, a park terminal 201 which is an example of the terminal 200, a printing unit 50 that prints the captured image IM0, and the like. The ticket center 13 is equipped with a ticket vending machine 14 that can issue a paid ticket TI0 for entering the park 10 to the user US0, a camera 15 that can capture the face of the user US0, and the like. The entrance gate 11 is equipped with a ticket identification information acquisition unit 30 that reads the ticket TI0, a camera 16 that can capture the face of the user US0, and the like. Each of the area entrance gates 21 to 24 is equipped with a ticket identification information acquisition unit 30 that reads the ticket TI0, a camera 17 that can capture the face of the user US0, and the like. The user US0 can acquire the ticket TI0 by purchasing the ticket TI0 having the ticket identification information acquisition unit 30 at the ticket vending machine 14. Also, the user US0 can purchase the ticket TI0 with the user terminal 202 which is an example of the terminal 200. The ticket TI0 may be an image displayed on the user terminal 202. The user US0 can enter the park 10 by having the ticket identification information acquisition unit 30 of the entrance gate 11 read the ticket TI0. Moreover, the user US0 can enter the areas A1 to A4 and enjoy the attractions by having the ticket identification information acquisition unit 30 of the area entrance gates 21 to 24 read the ticket TI0.

[0018] Each ticket identification information acquisition unit 30 acquires ticket identification information IDT0 that identifies ticket TI0 acquired by user US0 from ticket TI0. As shown in FIG. 2, a different ticket number is assigned to each ticket TI0. Therefore, the ticket number can be the ticket identification information IDT0. The ticket identification information IDT0 may be information embedded in printed information such as a two-dimensional code or a barcode, or may be recorded information recorded on a non-temporary recording medium capable of reading information such as an IC tag or a magnetic recording layer. These pieces of information may be the ticket number or information different from the ticket number. For example, when a two-dimensional code in which the ticket identification information IDT0 is embedded is printed on the ticket TI0, the ticket identification information acquisition unit 30 can acquire the ticket identification information IDT0 by optically reading the two-dimensional code. When the ticket TI0 has an IC tag in which the ticket identification information IDT0 is recorded, the ticket identification information acquisition unit 30 can acquire the ticket identification information IDT0 from the IC tag using radio waves.

[0019] The plurality of users US0 includes a plurality of group users USi belonging to a group GR0 such as family members and friends. FIG. 2 shows an example in which users US1, US2, US3, and US4 each hold tickets TI1, TI2, TI3, and TI4. The tickets TI1, TI2, TI3, and TI4 each have ticket identification information IDT1, IDT2, IDT3, and IDT4. Of course, users US1 to US4 are examples of user US0, tickets TI1 to TI4 are examples of ticket TI0, and ticket identification information IDT1 to IDT4 are examples of ticket identification information IDT0. The server 100 can associate a plurality of ticket identification information IDT0 assigned to a plurality of group users USi with group identification information IDG0 (see FIGS. 4 and 5).

[0020] Areas A1 to A4 each include one or more photographing units 40 that automatically photograph a person including the user US0 enjoying the attraction. Therefore, the photographed image management system SY1 includes a ticket identification information acquisition unit 30 and a photographing unit 40 in each of the plurality of areas A1 to A4. The photographing unit 40 transmits the photographed image IM0 of the user US0 to the server 100. The photographed image IM0 is stored in the server 100 and can be displayed on the terminal 200. The server 100 receives from the terminal 200 the selection of the purchasable image IMp (see FIGS. 13A and 13B) from among one or more photographed images IM0, and issues a print instruction for the purchasable image IMp to the printing unit 50. The printing unit 50 prints the photographed image IM0 according to the print instruction from the server 100. Therefore, the user US0 can select the purchasable image on the terminal 200 from among one or more photographed images IM0, and can purchase a photograph, which is a printed matter of the purchasable image, at the service center 12 or the like. As the printing unit 50, a photo printer or the like that directly prints the photographed image IM0 can be used.

[0021] In the photographed image management system SY1 shown in FIG. 3, the server 100, cameras 15 to 17, a plurality of ticket identification information acquisition units 30, a plurality of imaging units 40, and a printing unit 50 are connected via the network NE1. The photographed image management system SY1 is connected via the network NE1 to the park terminal 201 and a plurality of user terminals 202. The server 100 can also be said to be a photographed image management device included in the photographed image management system SY1. Note that the printing unit 50 may be directly connected to the server 100, the park terminal 201 may be directly connected to the server 100, and other elements may also be directly connected to the server 100 if they are near the server 100.

[0022] Server 100 includes a CPU (Central Processing Unit) 111 as a processor, a ROM (Read Only Memory) 112, a RAM (Random Access Memory) 113, a storage device 114, an input device 115, a display device 116, an I / F (interface) 117, etc. The above-mentioned elements (111 - 117) are electrically connected and can input and output information to each other. Note that the ROM 112, the RAM 113, and the storage device 114 are memories, and at least the ROM 112 and the RAM 113 are semiconductor memories. Server 100 may have all the components (111 - 117) in one housing, or may be composed of a plurality of devices that are divided so as to be communicable with each other.

[0023] The storage device 114 stores an OS (Operating System) not shown, a shooting image management program PR1, a user management table TA1 illustrated in FIG. 4, a shooting image table TA2 illustrated in FIG. 5, a priority determination rule RU1 illustrated in FIG. 9, etc. The shooting image management program PR1 causes the computer to function as a shooting image management device. Examples of the storage device 114 include non-volatile semiconductor memories such as flash memories, magnetic storage devices such as hard disks, etc. Examples of the input device 115 include pointing devices, hard keys such as keyboards, touch panels, etc. Examples of the display device 116 include liquid crystal display panels, etc. The I / F 117 is connected to the network NE1 and can communicate with cameras 15 - 17, a ticket identification information acquisition unit 30, an imaging unit 40, a printing unit 50, a park terminal 201, a user terminal 202, etc.

[0024] The CPU 111 of server 100 appropriately reads the information stored in the storage device 114 into the RAM 113 and performs various processes by executing the read program. The CPU 111 performs a photographed image management process by executing the photographed image management program PR1 read into the RAM 113. The computer-readable recording medium storing the photographed image management program PR1 is not limited to the internal storage device of the server 100 and may be an external recording medium of the server 100. Note that the tables (TA1, TA2) that can be used for the photographed image management process are merely examples. Therefore, the structure of the tables (TA1, TA2) for the photographed image management process can be changed as appropriate.

[0025] Figure 4 schematically shows an example of the structure of the user management table TA1. The user management table TA1 has ticket identification information IDT0, group identification information IDG0, assigned seat information RS0, user information INUS0, and face image FA0. The ticket identification information IDT1 to IDT7 shown in FIG. 4 are examples of the ticket identification information IDT0. The group identification information IDG0 means information for identifying the group GR0 to which a plurality of group users USi belong, and is associated with the ticket identification information IDT0. FIG. 4 shows that the group identification information IDG1 is associated with the ticket identification information IDT1 to IDT4, and the group identification information IDG2 is associated with the ticket identification information IDT6 and IDT7. Of course, the group identification information IDG1 and IDG2 are examples of the group identification information IDG0. When the user US0 does not belong to the group GR0, the group identification information IDG0 is not assigned to the user US0. FIG. 4 shows that the group identification information IDG0 is not associated with the ticket identification information IDT5. The assigned seat information RS0 means information indicating the assigned seat where the user US0 sits in the attraction, and is associated with the ticket identification information IDT0. FIG. 4 shows that the assigned seat information RS1 to RS7 are respectively associated with the ticket identification information IDT1 to IDT7. When the user US0 has not acquired an assigned seat, the assigned seat information RS0 is not associated with the ticket identification information IDT0. The user information INUS0 means information about the user US0 who obtained the ticket TI0, for example, name, address, etc., and is associated with the ticket identification information IDT0. FIG. 4 shows that the user information INUS1 to INUS7 are respectively associated with the ticket identification information IDT1 to IDT7. The face image FA0 means an image obtained by photographing the face of the user US0 with, for example, cameras 15 to 17, and is associated with the ticket identification information IDT0. The face image FA0 can be used for face recognition and the like. In the user management table TA1, instead of the face image FA0 itself, the file name of the face image FA0 or the address indicating the storage location of the face image FA0 may be stored.

[0026] FIG. 5 schematically shows an example of the structure of the photographed image table TA2. The photographed image table TA2 has ticket identification information IDT0, group identification information IDG0, the date (Date) on which the photographed image IM0 was taken, the photographed image IM0, and the paid photo image PP0. Note that since the group identification information IDG0 is associated with the ticket identification information IDT0 in the user management table TA1, it may not be present in the photographed image table TA2. The date is associated with the ticket identification information IDT0. The photographed image IM0 means an image photographed by the photographing unit 40 and is associated with the ticket identification information IDT0. Attraction identification information IDAi is associated with each photographed image IM0. For example, attraction identification information IDA1 is associated with the captured image IM0 photographed by the photographing unit 40 in area A1, and attraction identification information IDA2 is associated with the captured image IM0 photographed by the photographing unit 40 in area A2. Also, attraction identification information IDA3 is associated with the captured image IM0 photographed by the photographing unit 40 in area A3, and attraction identification information IDA4 is associated with the captured image IM0 photographed by the photographing unit 40 in area A4. The attraction identification information IDAi can also be said to be information capable of identifying areas A1 to A4. In the photographed image table TA2, instead of the photographed image IM0 itself, the file name of the photographed image IM0 or the address indicating the storage location of the photographed image IM0 may be stored. The paid photo image PP0 means an image photographed at a spot where paid photos can be taken and is associated with the ticket identification information IDT0. In the photographed image table TA2, instead of the paid photo image PP0 itself, the file name of the paid photo image PP0 or the address indicating the storage location of the paid photo image PP0 may be stored.

[0027] (3) Specific example of photographed image management process: Next, an example of the photographed image management process performed by the photographed image management system SY1 will be described. FIG. 6 schematically illustrates the ticket information registration process performed by the server 100. The ticket information registration process starts triggered by the ticket vending machine 14 receiving an operation of the ticket issuing button, or triggered by the user terminal 202 receiving an operation of the ticket purchase procedure. FIG. 7A schematically illustrates the ticket purchase screen 500 displayed on the ticket vending machine 14 or the user terminal 202. FIG. 7B schematically illustrates the charge claim screen 520 displayed on the ticket vending machine 14 or the user terminal 202.

[0028] When the ticket information registration process starts, the server 100 performs a ticket issuance acceptance process of issuing a paid ticket TI0 to the user US0 (step S102). Hereinafter, the description of "step" may be omitted, and the step number may be indicated in parentheses. In S102, the server 100 causes, for example, the ticket purchase screen 500 shown in FIG. 7A to be displayed on the ticket vending machine 14 or the user terminal 202. The ticket purchase screen 500 has a number of persons input section 501, a next button 502, etc., and accepts the number of tickets TI0 to be issued in one purchase operation. In the example shown in FIG. 7A, since the fares are different for adults and children, the ticket vending machine 14 or the user terminal 202 accepts the number of adults and the number of children from the user US0 in the number of persons input section 501. When the total number of persons is 2 or more, a plurality of tickets TI0 will be issued in the group GR0, and when the total number of persons is 1, a ticket TI0 not associated with the group GR0 will be issued. By the ticket vending machine 14 or the user terminal 202 accepting the issuance of 2 or more tickets TI0 at once, the server 100 can associate a plurality of tickets TI0 with the group GR0.

[0029] When the ticket vending machine 14 or the user terminal 202 receives an operation of the next button 502 from the user US0 and notifies the server 100 of the reception of the operation, the server 100 causes, for example, the charge billing screen 520 shown in FIG. 7B to be displayed on the ticket vending machine 14 or the user terminal 202. The charge billing screen 520 has a ticket price display area 521, a payment button 522, etc., and accepts payment of the ticket price. When the total number of people is 2 or more, the ticket vending machine 14 or the user terminal 202 displays the price of a plurality of tickets TI0 grouped together in the ticket price display area 521. When the ticket vending machine 14 or the user terminal 202 receives an operation of the payment button 522, it accepts payment of the ticket price. At this time, the ticket vending machine 14 or the user terminal 202 may receive input of the user information INUS0. The user terminal 202 may display an installment payment button 523 on the charge billing screen 520. In this case, when the user terminal 202 receives an operation of the installment payment button 523, it accepts installment payment of the ticket price. Since payment can be made in a lump sum in the purchase procedure for family visits, group users USi can smoothly purchase tickets. In order to ensure that group registration can be reliably implemented even when a certain group user USi visits with a plurality of friends, the ticket vending machine 14 or the user terminal 202 may support individual payments.

[0030] When the ticket vending machine 14 or the user terminal 202 notifies the server 100 of payment of the ticket price, the server 100 assigns ticket identification information IDT0 for identifying the ticket TI0 to each ticket TI0 and stores it in the user management table TA1 (see FIG. 4) (S104). When the server 100 acquires the user information INUS0 from the ticket vending machine 14 or the user terminal 202, it associates the user information INUS0 with the ticket identification information IDT0 and stores it in the user management table TA1. In addition, when there are assigned seats for the attraction, the server 100 may assign an assigned seat to the user US0 and associate assigned seat information RS0 indicating the assigned seat with the ticket identification information IDT0 and store it in the user management table TA1. The assigned seat information RS0 is printed on the ticket TI0 and shown to the user US0, for example. When the total number of people is 2 or more, the server 100 assigns group identification information IDG0 common to a plurality of ticket identification information IDT0, associates the group identification information IDG0 with each ticket identification information IDT0, and stores it in the user management table TA1 (S106). In this way, the server 100 acquires the group identification information IDG0 and the ticket identification information IDT0 assigned to each group user USi from the terminal 200. Then, the server 100 associates the plurality of ticket identification information IDT0 assigned to the plurality of group users USi with the group identification information IDG0.

[0031] The ticket information registration process shown in FIG. 6 may end in S106, but the server 100 may perform a face image registration process for face recognition (S108). When the face image registration process is performed, the server 100 causes the camera 15 or the user terminal 202 to capture the face of the user US0, acquires the face image FA0 of the user US0 from the camera 15 or the user terminal 202, associates it with the ticket identification information IDT0, stores it in the storage device 114, and updates the user management table TA1.

[0032] FIG. 8 schematically illustrates the automatic shooting process performed by the server 100. First, the outline of the automatic shooting process will be described.

[0033] FIG. 5 shows that attraction identification information IDAi is associated with each captured image IM0. Thereby, each attraction is associated with photo shooting. Since each captured image IM0 is associated with the ticket identification information IDT0, the captured photo image is associated with the ticket TI0 and stored in the server 100.

[0034] When the seats for the attraction are unreserved seats, even if the server 100 acquires the ticket identification information IDT0 from the ticket identification information acquisition unit 30 and the photographed image IM0 from the photographing unit 40, there is a possibility that the photographed image IM0 cannot be associated with the ticket identification information IDT0. Therefore, the server 100 associates the face image FA0 of the user US0 with the ticket identification information IDT0 (see Fig. 4), and performs face recognition for the association between the photographed image IM0 and the ticket identification information IDT0 as appropriate. Note that the server 100 can improve the accuracy of face recognition by narrowing down the target of face recognition based on the acquisition timing of the ticket identification information IDT0. In addition, by using face recognition, a mechanism for automatically selecting a best shot such as a smiling photograph from a plurality of photographed images can be introduced. By providing a better photographed image to the user US0, the motivation for purchasing a photograph can be increased.

[0035] Fig. 5 shows that the photographed image IM0 is associated with each ticket identification information IDT0. It is assumed that the accumulation of the photographed image IM0 targets all the visitors to the park 10. Photographs are taken for each attraction under the condition that face recognition is used as needed for each ticket TI0 and the photographed image IM0 is associated, and the photographed image IM0 is accumulated in the server 100. The photograph data (paid photographed image PP0) of the paid photographing spot site for the purpose of photograph purchase is also accumulated in the same server 100.

[0036] Next, the automatic photographing process will be described according to the flowchart shown in Fig. 8. When the ticket identification information acquisition units 30 at the area entrance gates 21 to 24 acquire the ticket identification information IDT0 from the ticket TI0, they transmit the ticket identification information IDT0 to the server 100 together with a transmission request. When the server 100 receives the transmission request from the ticket identification information acquisition unit 30, it starts the automatic photographing process and acquires the ticket identification information IDT0 from the ticket identification information acquisition unit 30 (S202).

[0037] Next, the server 100 refers to the user management table TA1 shown in FIG. 4 and performs face image registration processing when the face image FA0 of the user US0 is not associated with the ticket identification information IDT0 (S204). When the face image registration processing is performed, the server 100 causes the camera 17 to capture the face of the user US0, acquires the face image FA0 of the user US0 from the camera 17, associates it with the ticket identification information IDT0, stores it in the storage device 114, and updates the user management table TA1. After that, the photographing unit 40 automatically photographs a person including the user US0 enjoying the attraction. Therefore, the server 100 acquires a photographed image IM0 of the person photographed by the photographing unit 40 in the same area as the ticket identification information acquisition unit 30 from the photographing unit 40 (S206).

[0038] Next, the server 100 associates the photographed image IM0 acquired in S206 with the attraction identification information IDAi and the photographed date (S208). For example, the server 100 associates the photographed image IM0 acquired from the photographing unit 40 in the area A1 with the attraction identification information IDA1 and the photographing date, and associates the photographed image IM0 acquired from the photographing unit 40 in the area A2 with the attraction identification information IDA2 and the photographing date.

[0039] Finally, the server 100 associates the photographed image IM0 acquired in S206 and the photographed date with the ticket identification information IDT0, stores them in the storage device 114, and updates the photographed image table TA2 (see FIG. 5) (S210). The processing of S206 to S210 is repeated until the user US0 exits. The exit of the user US0 can be determined by the ticket identification information acquisition unit 30 at the exit gate acquiring the ticket identification information IDT0 associated with the user US0, or the ticket identification information acquisition unit 30 in another area acquiring the ticket identification information IDT0 associated with the user US0.

[0040] For example, it is assumed that user US0 sits in a reserved seat of an attraction. In this case, the server 100 can identify the user US0 sitting in the reserved seat by referring to the user management table TA1 shown in FIG. 4 and checking the ticket identification information IDT0 associated with the reserved seat information RS0. Therefore, the server 100 refers to the user management table TA1, associates the captured image IM0 generated by capturing the user US0 sitting in the reserved seat with the ticket identification information IDT0, stores it in the storage device 114, and can update the captured image table TA2. Incidentally, when the user US0 rides on a vehicle such as a roller coaster, in order to reduce errors in the ticket identification information IDT0 associated with the captured image IM0, a gate for reading the ticket identification information IDT0 may be installed for each seat.

[0041] When it is difficult to install a gate for each seat, or when the user US0 sits in an unreserved seat of an attraction, the server 100 performs a process of identifying the user US0 shown in the captured image IM0 by face recognition. The server 100 can identify the user US0 shown in the captured image IM0 by referring to the user management table TA1 and checking the ticket identification information IDT0 associated with the face image FA0. Therefore, the server 100 refers to the user management table TA1, associates the captured image IM0 generated by capturing the user US0 with the ticket identification information IDT0, stores it in the storage device 114, and updates the captured image table TA2. In this way, the server 100 associates the captured image IM0 with the ticket identification information IDT0 by performing face recognition based on the face image FA0 on the captured image IM0 that is not associated with the ticket identification information IDT0. Thereby, even when it is difficult to identify the position of the user US0, such as in the case of an unreserved seat, the captured image IM0 related to the user US0 can be provided to the user US0. As described above, the server 100 acquires the captured image IM0 captured by the imaging unit 40 via the network NE1, associates the captured image IM0 with the ticket identification information IDT0 acquired by the ticket identification information acquisition unit 30, and stores the captured image IM0.

[0042] FIG. 9 schematically illustrates the ranking process performed by the server 100. FIG. 10 schematically illustrates the priority information INP1 generated by the ranking process. First, an overview of the ranking process will be described.

[0043] When visiting a theme park in a group GR0 such as a family or friends, registration as the group GR0 is performed at the time of ticket purchase or the like. The fact that photo shooting is performed for each attraction in association with a ticket TI0 is the same as in the case of not being in the group GR0. The server 100 has decided to increase the priority of photos in which a larger number of people are photographed simultaneously within the group GR0 and photos in which all members of the group are photographed. At the time of later photo selection, the server 100 preferentially displays the photos with higher priority on the terminal 200. When shooting using a camera or terminal brought by one of the group users USi, there is a tendency for the number of photos in which the shooter is photographed to decrease. Therefore, if photos in which all members of the group are photographed can be presented to the group user USi, it is expected to increase the purchase intention of the group user USi. Furthermore, the server 100 introduces a recognition technology to automatically select the best shot, and by increasing the priority at the time of photo selection and displaying the best shot on the terminal 200, the purchase intention of the group user USi can be increased.

[0044] Next, the ranking process will be described according to the flowchart shown in FIG. 9. The ranking process is performed repeatedly. When a new captured image IM0 is stored in the storage device 114 in the automatic shooting process shown in FIG. 8, the server 100 performs the processes after S304 (S302). In S304, the server 100 acquires the attraction identification information IDAi associated with the new captured image IM0, and refers to the captured image table TA2 to acquire the ticket identification information IDT0 associated with the captured image IM0.

[0045] Next, if the group identification information IDG0 is associated with the ticket identification information IDT0 in the user management table TA1 shown in FIG. 4, the server 100 raises the priority of the captured image IM0 as the number of group users USi captured in the new captured image IM0 increases (S306). First, the server 100 may obtain all the ticket identification information IDT0 associated with the group identification information IDG0 in the user management table TA1. Then, the server 100 may assign priorities to each captured image IM0 in descending order of the number of group users USi, together with these ticket identification information IDT0 and the captured images IM0 associated with the attraction identification information IDAi and the new captured image IM0. For example, as shown in FIG. 10, the captured image IM0 in which all four people in a four-person group are captured has a higher priority than the captured image IM0 in which only three people are captured. As in this example, the server 100 determines the priority so that the captured image IM0 in which all of the plurality of group users USi are captured is given the highest priority among one or more captured images IM0 associated with the plurality of ticket identification information IDT0 associated with the group identification information IDG0.

[0046] Next, the server 100 raises the priority of the captured image IM0 as the facial expression of the user US0 shown in the new captured image IM0 is better (S308). When the user US0 is not a group user USi, the server 100 determines an expression determination value indicating the goodness of the facial expression of the user US0 by performing face recognition on one or more captured images IM0 directly associated with the ticket identification information IDT0 acquired in S304, and may assign priorities to each captured image IM0 in descending order of the expression determination value. When the user US0 is a group user USi, the server 100 first determines an expression determination value by performing face recognition on one or more captured images IM0 associated with a plurality of ticket identification information IDT0 associated with the group identification information IDG0 associated with the ticket identification information IDT0 acquired in S304. Then, the server 100 may assign priorities to each captured image IM0 in descending order of the expression determination value while maintaining the order of the number of group users USi shown in the captured image IM0. For example, among the captured images IM0 in which all four people are shown in a group of four, the expression determination value of the captured image IM0 in which all four people have good facial expressions is large, and the expression determination value of the captured image IM0 in which all four people have bad facial expressions is small. In this case, as shown in FIG. 10, priorities are assigned to each captured image IM0 in descending order of the expression determination value. As in this example, the server 100 performs an expression determination of the user US0 on one or more captured images IM0 directly or indirectly associated with the ticket identification information IDT0, and determines priorities based on the expression determination.

[0047] From the above, the information for realizing the processing of S306 to S308 can be said to be a predetermined priority determination rule RU1. It can be said that the server 100 determines the priorities of one or more captured images IM0 directly or indirectly associated with the ticket identification information IDT0 according to the priority determination rule RU1.

[0048] Finally, the server 100 associates the determined priority order with each captured image IM0, and stores it in the storage device 114 as priority order information INP1 as shown in FIG. 10 (S310). Note that the priority order information INP1 may hold not the captured image IM0 itself but the file name of the captured image IM0 or an address indicating the storage location of the captured image IM0.

[0049] FIG. 11 schematically illustrates a photo printing process performed by the server 100. FIG. 12A schematically illustrates a photo selection screen 540 displayed on the terminal 200. FIG. 12B schematically illustrates a photo enlargement screen 560 displayed on the terminal 200. FIG. 13A schematically illustrates a photo confirmation screen 580 displayed on the terminal 200. FIG. 13B schematically illustrates a photo enlargement screen 600 displayed on the terminal 200. Note that the terminal 200 may be a park terminal 201 or a user terminal 202. First, an overview of the photo printing process will be described.

[0050] User US0 can view only the photos they took by, for example, entering a ticket number or reading a two-dimensional code printed or displayed on ticket TI0 at park terminal 201. Park terminal 201, according to the control by server 100, preferentially displays photos tagged with a high priority and accepts an operation to select a photo. After user US0 selects a photo, park terminal 201 displays an amount, etc., and if OK, causes print unit 50 to print the photo. The captured image IM0 may be printed as a single photo or bound in the form of a photo book. By binding paid photos in the captured image IM0 in the form of a photo book, user US0 can be further encouraged to make a purchase. If user US0 requests printing on the same day within park 10, they can receive single photos or a photo book at park 10. Also, if park terminal 201 presents the waiting time until a single photo or a photo book is completed and shows the option to receive a single photo or a photo book by delivery, user US0 can select the receiving method on the spot when the waiting time is long. Further, server 100 can keep the captured image IM0 for several days so that user US0 can select a photo in a state associated with ticket TI0 after returning home, and single photos or a photo book may be delivered to their home or the like. User US0 can select a photo at home, calmly and, in the case of family members, after consulting with others.

[0051] Next, according to the flowchart shown in FIG. 11, the photo printing process will be described. When the terminal 200 receives an operation for photo selection from the user US0, the server 100 starts a photo printing process and causes the terminal 200 to acquire ticket identification information IDT0 (S402). When the terminal 200 is the park terminal 201, the ticket identification information IDT0 can be acquired by reading print information or display information such as a two-dimensional code, reading recording information such as an IC tag, receiving an operation of directly inputting a ticket number, and the like. When the terminal 200 is the user terminal 202 with a camera, the ticket identification information IDT0 can be acquired by reading print information or display information such as a two-dimensional code, receiving an operation of directly inputting a ticket number, and the like. It can be said that the server 100 receives the input of the ticket identification information IDT0 from the terminal 200.

[0052] Next, when the group identification information IDG0 is associated with the ticket identification information IDT0 in the user management table TA1 shown in FIG. 4, the server 100 causes the terminal 200 to display the captured images IM0 associated with the group identification information IDG0 in order of priority (S404). For example, the server 100 causes the terminal 200 to display a screen in which the captured images IM0 are arranged in the order according to the priority shown in FIG. 10. Thereby, the user US0 can view the captured images IM0 arranged in the order according to the priority on the terminal 200. Further, the server 100 may cause the terminal 200 to display the captured images IM0 in the order according to the priority shown in FIG. 10. Thereby, the user US0 can view the captured images IM0 in the order according to the priority on the terminal 200. As described above, the server 100 outputs at least a part of one or more captured images IM0 associated with a plurality of ticket identification information IDT0 associated with the group identification information IDG0 associated with the input ticket identification information IDT0 to the terminal 200. Thereby, the group user USi can quickly confirm the captured images IM0 related to the group GR0.

[0053] For example, assume a case where the user US1 (see FIG. 2) associated with the ticket identification information IDT1 associated with the group identification information IDG1 shown in FIG. 4 operates the terminal 200. In this case, in addition to the captured image IM0 directly associated with the ticket identification information IDT1, the captured image IM0 associated only with the ticket identification information IDT2 to IDT4 associated with the group identification information IDG1 is also displayed. The captured image IM0 associated only with the ticket identification information IDT2 to IDT4 can be said to be a captured image IM0 indirectly associated with the ticket identification information IDT1. Therefore, the user US1 can quickly check the captured image IM0 related to the group GR0.

[0054] Also, in S404, at least a part of one or more captured images IM0 is output to the terminal 200 according to the priority determined according to the priority determination rule RU1. Since the captured image IM0 in which all of the plurality of group users USi are captured is given the highest priority and output to the terminal 200, the purchasing desire of the user US0 can be increased.

[0055] On the other hand, when the group identification information IDG0 is not associated with the ticket identification information IDT0, the server 100 causes the terminal 200 to display the captured image IM0 associated with the ticket identification information IDT0 according to the priority (S406). In this way, the server 100 outputs at least a part of one or more captured images IM0 directly associated with the received ticket identification information IDT0 to the terminal 200. Thereby, the user US0 can quickly check the captured image IM0 related to himself / herself. In S404 and S406, at least a part of one or more captured images IM0 is output to the terminal 200 according to the priority determined according to the priority determination rule RU1. Since the captured image IM0 is output to the terminal 200 according to the priority, the purchasing desire of the user US0 can be increased.

[0056] Also, in S404 and S406, at least a part of one or more captured images IM0 is output to the terminal 200 according to the priority determined based on the facial expression determination of the user US0 in accordance with the priority determination rule RU1. Since the captured image IM0 is output to the terminal 200 in the priority order based on the facial expression determination of the user US0, the purchasing desire of the user US0 can be further increased.

[0057] After the captured image IM0 is displayed, the server 100 receives, from the terminal 200, the selection of the purchase target image IMp from among one or more captured images IM0 directly or indirectly associated with the ticket identification information IDT0 (S408). The server 100 performs the processes of S404 to S408 for all attractions (S410), and performs the processes of S404 to S410 until the confirmation or correction by the user US0 is completed (S412).

[0058] In S404 to S412, the server 100 causes the terminal 200 to display, for example, a photo selection screen 540 shown in FIG. 12A. The photo selection screen 540 has a photo list 541, a selection button 542, a deselection button 543, a selected photo confirmation button 544, switching buttons 545 to 548, and the like. In the photo list 541, the captured images IM0 stored in the server 100 are displayed according to the priority automatically determined for each attraction. When the terminal 200 receives an operation of the triangular switching buttons 547 and 548 located beside each captured image IM0 from the user US0, the terminal 200 switches the display of the captured images IM0 in the order according to the priority under the control of the server 100. FIG. 12A shows an example in which, by reducing the captured images IM0, as many captured images IM0 of attractions as possible are displayed. Depending on the screen size for displaying the captured images IM0, the number of photos to be displayed, that is, the number of attractions, may be reduced. For example, when the terminal 200 is a smartphone with a small screen, two or four photos may be displayed on the screen. Index display may be performed for the selected photos. FIG. 12A shows that index display in which the frame of the captured image IM0 of the attraction "A_4" is emphasized more than the frames of the other captured images IM0 is performed. When the terminal 200 receives an operation of the selection button 542 from the user US0, the server 100 accepts the captured image IM0 with index display as a purchase target image IMp. When the terminal 200 receives an operation of the deselection button 543 from the user US0, the server 100 removes the captured image IM0 with index display from the purchase target image IMp. When the terminal 200 receives an operation of the switching buttons 545 and 546 from the user US0, the terminal 200 switches the target of the index display to the captured images IM0 of other attractions.

[0059] When the terminal 200 receives a tap operation on the captured image IM0 in the photo list 541 from the user US0, the server 100 causes the terminal 200 to display a photo enlargement screen 560 as shown in FIG. 12B. The photo enlargement screen 560 has an enlarged photo 561, a selection button 562, a deselection button 563, a back button 564, switching buttons 565, 566, etc. The photo 561 is an enlarged image of the captured image IM0 tapped from the photo list 541 shown in FIG. 12A. By viewing the enlarged display of the captured image IM0, the user US0 can more clearly confirm the captured image IM0 including the facial expression, etc., and can make an accurate selection as the purchase target image IMp. When the terminal 200 receives an operation of the triangular switching buttons 565, 566 located beside the photo 561 from the user US0, it switches the enlarged display of the captured image IM0 in the order according to the priority under the control of the server 100. When the terminal 200 receives an operation of the deselection button 563 from the user US0, the server 100 removes the photo 561 from the purchase target image IMp. When the terminal 200 receives an operation of the selection button 562 from the user US0, the server 100 accepts the photo 561 as the purchase target image IMp. When the terminal 200 receives an operation of the back button 564 from the user US0, the server 100 causes the terminal 200 to display the photo selection screen 540 shown in FIG. 12A.

[0060] When the terminal 200 receives an operation of the selected photo confirmation button 544 from the user US0, the server 100 causes the terminal 200 to display a photo confirmation screen 580 shown in FIG. 13A. The photo confirmation screen 580 has a photo list 581, a deselection button 582, a purchase button 583, switching buttons 584 to 587, and the like. In the photo list 581, the purchase target images IMp are displayed according to the priority automatically determined for each attraction. In the photo list 581, the display of attractions for which the purchase target image IMp is not selected disappears. When the terminal 200 receives an operation of the triangular switching buttons 586 and 587 located beside the photo from the user US0, it switches the display of the purchase target images IMp in the order according to the priority under the control of the server 100. When the terminal 200 receives an operation of the deselection button 582 from the user US0, the server 100 removes the purchase target image IMp for which the index display is being performed. When the terminal 200 receives an operation of the switching buttons 584 and 585 from the user US0, it switches the target of the index display to the purchase target images IMp of other attractions.

[0061] When the terminal 200 receives a tap operation on the purchase target image IMp in the photo list 581 from the user US0, the server 100 causes the terminal 200 to display a photo enlargement screen 600 shown in FIG. 13B. The photo enlargement screen 600 has an enlarged photo 601, a deselection button 602, a back button 603, switching buttons 604 and 605, and the like. The photo 601 is an enlarged image of the purchase target image IMp tapped from the photo list 581 shown in FIG. 13A. When the terminal 200 receives an operation of the triangular switching buttons 604 and 605 located beside the photo 601 from the user US0, it switches the enlarged display of the purchase target images IMp in the order according to the priority under the control of the server 100. When the terminal 200 receives an operation of the deselection button 602 from the user US0, the server 100 removes the photo 601 from the purchase target image IMp. When the terminal 200 receives an operation of the back button 603 from the user US0, the server 100 causes the terminal 200 to display the photo confirmation screen 580 shown in FIG. 13A.

[0062] When the terminal 200 receives the operation of the purchase button 583 from the user US0, the server 100 proceeds to the process of S414 shown in FIG. 11. In S414, the server 100 causes the terminal 200 to display the selling price of the image IMp to be purchased, and receives confirmation from the terminal 200 from the user US0. When the terminal 200 receives the operation of price confirmation from the user US0, the server 100 causes the selected image IMp to be purchased to be printed by the printing unit 50 (S416), and ends the photo printing process. The printed purchased image IMp may be bound in the form of a photo book. As described above, the user US0 can promptly purchase a printed matter of the captured image IM0 related to himself / herself. In addition, when the user US0 is outside the park 10 and operates the purchase button 583 from the user terminal 202, the printed purchased image IMp is sent to the user US0, so that the user US0 can promptly obtain a printed matter of the captured image IM0 related to himself / herself. As will be described later, the purchase procedure of the printed matter may be on a day after the use date of the park 10.

[0063] As described above, in the server 100, the captured image IM0 is linked to the identification information of the ticket TI0 acquired by the user US0 and stored. When the ticket identification information IDT0 is input to the terminal 200, at least a part of one or more captured images IM0 directly or indirectly linked to the ticket identification information IDT0 is output to the terminal 200. The user US0 can confirm the captured image IM0 related to himself / herself on the terminal 200. As a result, it is not necessary to spend time finding oneself or family members from many captured images IM0. Therefore, in this specific example, the user US0 can promptly confirm the captured image IM0 related to himself / herself. As a result, a situation where the user delays the purchase because he / she cannot find himself / herself or family members from the captured image IM0 in a short time does not occur, and unnecessary printing can be eliminated. In addition, since the captured image IM0 is linked to the user US0 for each area and output to the terminal 200, the present captured image management system SY1 is convenient.

[0064] (4) Modification example: The present invention includes various modification examples. For example, the number of areas within the park 10 is arbitrary and may be 5 or more, 3 or less, or even 1. Even if the park 10 is not divided into areas, it is included in the aspects of the present application. The photographed image IM0 may be sold not only as a printed matter but also as electronic data.

[0065] As illustrated in FIG. 14, the server 100 may perform a process capable of accepting an order for a photo on a day after the usage date of the park 10. FIG. 14 schematically illustrates the photo order process performed by the server 100. The photo order process starts triggered by the user terminal 202 receiving an operation for a photo purchase procedure. FIG. 14 also illustrates a shooting date specification screen 620 displayed on the user terminal 202. As shown in FIG. 5, the server 100 associates the date on which the photographed image IM0 was taken with the photographed image IM0. When the photo order process starts, the server 100 causes the user terminal 202 to acquire ticket identification information IDT0 (S502). The user terminal 202 can acquire the ticket identification information IDT0 by reading printed information or display information such as a two-dimensional code, accepting an operation of directly inputting a ticket number, and the like. It can be said that the server 100 receives the input of the ticket identification information IDT0 from the terminal 200.

[0066] Next, the server 100 causes the user terminal 202 to display the shooting date specification screen 620 (S504). The shooting date specification screen 620 has a checkbox 621 for receiving whether to specify a shooting date, a shooting date input field 622, a photo display button 623, and the like. When the user terminal 202 receives an operation from the user US0 to check the checkbox 621, the user terminal 202 receives an operation from the user US0 to input the shooting date in the shooting date input field 622. When the user terminal 202 receives an operation of the photo display button 623 from the user US0, the server 100 refers to the shooting image table TA2 shown in FIG. 5 and displays the shooting images IM0 of the date input in the shooting date input field 622 in order of priority (S506). When the checkbox 621 is not checked and the user terminal 202 receives an operation of the photo display button 623 from the user US0, the server 100 displays the shooting images IM0 of the date on which the ticket identification information acquisition process of S502 was performed in order of priority. The process of S506 is the same as the processes of S404 to S406 shown in FIG. 11. As described above, the server 100 outputs at least a part of one or more shooting images IM0 associated with one of the date when the ticket identification information IDT0 was input from the terminal 200 and the date specified from the terminal 200 to the terminal 200. Therefore, the present shooting image management system SY1 can provide the captured image IM0 of the date on which the shooting image IM0 was captured to the user US0.

[0067] After that, the server 100 receives the selection of the purchase target image IMp from the terminal 200 in the same manner as the purchase target image selection acceptance process of S408 shown in FIG. 11 (S508). Next, the server 100 causes the terminal 200 to display the selling price of the purchase target image IMp and receives confirmation from the terminal 200 from the user US0 in the same manner as the price confirmation process of S410 shown in FIG. 11 (S510). When the user terminal 202 receives an operation for price confirmation from the user US0, the server 100 causes the selected purchase target image IMp to be printed by the printing unit 50 (S512) and ends the photo order process. The printed purchase target image IMp is sent to the user US0. At this time, the printed purchase target image IMp may be bound in the form of a photo book.

[0068] As illustrated in FIG. 15, the server 100 may handle the paid photo image PP0 taken by the user US0 at the paid shooting spot together with the captured image IM0 that has been automatically captured. FIG. 15 schematically illustrates the paid photo image association process performed by the server 100. The paid photo image association process is performed repeatedly. At the paid shooting spot, a gate (not shown) equipped with a ticket identification information acquisition unit 30 and a shooting unit 40 (not shown) for shooting the user US0 are installed. When the aforementioned ticket identification information acquisition unit 30 acquires the ticket identification information IDT0 from the ticket TI0, the server 100 acquires the ticket identification information IDT0 from the ticket identification information acquisition unit 30 (S602). After that, when the shooting unit 40 shoots the user US0, the server 100 acquires the paid photo image PP0 from the shooting unit 40 (S604). Finally, the server 100 associates the paid photo image PP0 taken by the user US0 and the shooting date with the ticket identification information IDT0 and stores them in the storage device 114, and updates the captured image table TA2 (see FIG. 5) (S606).

[0069] When user US0 presents ticket TI0 and enters the shooting spot, a photo is automatically taken and uploaded to server 100 as a paid photo image PP0. If the shooting image management system SY1 has a mechanism to inform the recognition technology and shooting timing, for example, a light blinking means similar to the timer shooting of a camera, it is possible to easily take a preferable photo. The shooting image management system SY1 may automatically take several photos and select the best shot by recognition. At the shooting spot, it is also possible to take photos with a camera brought by oneself. Although there are few differences when comparing only photos, when combined with bookbinding such as a photo book, the value of the paid photo can be improved and the motivation to purchase the paid photo can be increased.

[0070] The output of the paid photo image PP0 can be performed according to the process shown in FIG. 11 or FIG. 14. Server 100 receives the input of ticket identification information IDT0 from user terminal 202 and outputs the paid photo image PP0 directly or indirectly associated with the ticket identification information IDT0 to user terminal 202. User terminal 202 displays the paid photo image PP0. In this way, this shooting image management system SY1 can also transmit the paid photo image PP0 to user US0.

[0071] (5) Conclusion: As described above, according to the present invention, various aspects can provide a configuration that enables a user to quickly confirm a shooting image related to himself / herself. Of course, even in an aspect consisting only of the constituent elements according to the independent claims, the above-described basic operations and effects can be obtained. In addition, a configuration in which each configuration disclosed in the above-described examples is mutually replaced or the combination is changed, a known technique, and a configuration in which each configuration disclosed in the above-described examples is mutually replaced or the combination is changed, etc. are also implementable. The present invention also includes these configurations and the like.

Explanation of Reference Numerals

[0072] 10…Park, 11…Entrance Gate, 12…Service Center, 13…Ticket Center, 14…Ticket Vending Machine, 15 - 17…Camera, 21 - 24…Area Entrance Gate, 30…Ticket Identification Information Acquisition Unit, 40…Shooting Unit, 50…Printing Unit, 100…Server, 200…Terminal, 201…Park Terminal, 202…User Terminal, 500…Ticket Purchase Screen, 520…Charge Billing Screen, 540…Photo Selection Screen, 541…Photo List, 560…Photo Enlargement Screen, 561…Photo, 580…Photo Confirmation Screen, 581…Photo List, 600…Photo Enlargement Screen, 601…Photo, 620…Shooting Date Specifying Screen, A1 - A4…Area, FA0…Face Image, GR0…Group, IDAi…Attraction Identification Information, IDG0…Group Identification Information, IDT0…Ticket Identification Information, IM0…Shot Image, IMp…Image to be Purchased, INP1…Priority Information, INUS0…User Information, NE1…Network, PP0…Paid Photo Image, PR1…Shot Image Management Program, RS0…Designated Seat Number, RU1…Priority Determination Rule, SY1…Shot Image Management System, TA1…User Management Table, TA2…Shot Image Table, TI0…Ticket, US0…User, USi…Group User.

Claims

1. A photographing image management system connected to a terminal, comprising: a ticket identification information acquisition unit that acquires ticket identification information for identifying a ticket acquired by a user from the ticket; a photographing unit that photographs a person including the user; a server that acquires a photographed image photographed by the photographing unit via a network, associates the photographed image with the ticket identification information acquired by the ticket identification information acquisition unit, and stores the photographed image; The server receives an input of the ticket identification information from the terminal, and outputs at least a part of one or more of the photographed images directly or indirectly associated with the ticket identification information to the terminal. A photographing image management system.

2. There are a plurality of the users, There are a plurality of the ticket identification information, The server, acquires group identification information for identifying a group to which a plurality of group users included in the plurality of users belong, and the ticket identification information assigned to each of the group users from the terminal, associates the plurality of ticket identification information assigned to the plurality of group users with the group identification information, Outputs at least a part of one or more of the photographed images associated with the plurality of ticket identification information associated with the group identification information associated with the input ticket identification information to the terminal. The photographing image management system according to claim 1.

3. The server determines a priority order so that the photographed image in which all of the plurality of group users are photographed among one or more of the photographed images associated with the plurality of ticket identification information associated with the group identification information is given the highest priority, and outputs at least a part of one or more of the photographed images to the terminal according to the priority order. The photographing image management system according to claim 2.

4. The photographing image management system includes the ticket identification information acquisition unit and the photographing unit in each of a plurality of areas. For each of the areas, the server associates the captured image acquired from the capturing unit existing in the area with the ticket identification information acquired by the ticket identification information acquisition unit existing in the area, and outputs at least a part of one or more of the captured images directly or indirectly associated with the ticket identification information for the plurality of areas to the terminal. The captured image management system according to claim 1 or claim 2.

5. The server associates the face image of the user with the ticket identification information, and associates the captured image with the ticket identification information by performing face recognition based on the face image on the captured image not associated with the ticket identification information. The captured image management system according to claim 1 or claim 2.

6. The server associates the date on which the captured image was captured with the captured image, and outputs at least a part of one or more of the captured images associated with one of the date on which the input of the ticket identification information was received from the terminal and the date on which the designation was received from the terminal to the terminal. The captured image management system according to claim 1 or claim 2.

7. The system further includes a printing unit that prints the captured image. The server receives, from the terminal, a selection of a purchase target image from among one or more of the captured images directly or indirectly associated with the ticket identification information, and causes the printing unit to print the purchase target image. The captured image management system according to claim 1 or claim 2.

8. The server determines the priority order of one or more of the captured images directly or indirectly associated with the ticket identification information according to a predetermined priority order determination rule, and outputs at least a part of one or more of the captured images to the terminal according to the priority order. The captured image management system according to claim 1 or claim 2.

9. The server performs an expression determination of the user on one or more of the captured images directly or indirectly associated with the ticket identification information, and determines the priority order based on the expression determination. The captured image management system according to claim 8.

10. The server associates the paid photo image taken by the user with the ticket identification information, stores the paid photo image, receives an input of the ticket identification information from a user terminal used by the user as the terminal, and outputs the paid photo image directly or indirectly associated with the ticket identification information to the user terminal. The photographing image management system according to claim 1 or claim 2.

Images