JP2017034564A - Image transfer method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize, with a simple method, a mechanism for accepting only images photographed by a person himself/herself and preventing an image photographed by others from being used.SOLUTION: The image transfer method includes: transmitting information on a photographer and image specific information from a camera to a server at a time of image photographing; and accepting only images photographed by the person himself/herself at the server by transmitting the information on a photographer at a time of image uploading.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a method for transferring an image.

  Services that can create photo books on the Web have become widespread, and users can create photo books using arbitrary digital images. In addition, it has become widespread to publish images on Web services, making it easy to obtain images taken by others. From such a background, copyright protection technology that accepts only images taken by the person and prevents the use of images taken by others is important.

  Here, in Patent Document 1, a captured image and photographer information such as a fingerprint can be stored in association with each other at the time of image capturing. Then, by transmitting the photographer information at the time of connection with the external storage device, it is possible to transmit only the images with the matched photographer information from the imaging device to the external storage device.

JP 2011-109291 JP

  In Patent Document 1, there is a problem that an apparatus capable of identifying an individual such as a fingerprint authentication apparatus is required to associate a photographed image with a photographer in the imaging apparatus.

  Therefore, I would like to realize a mechanism that accepts only images taken by the person and prevents the use of images taken by others by a simple method.

  In the image transfer method according to the present invention, in a server capable of storing an image, the first photographer information and the first image specifying information group are received from the imaging device, and the two pieces of information are stored in association with each other; Means for receiving second photographer information and an image group from the imaging device or an arbitrary information device, and reading out a second image specifying information group embedded in the received image; Means for comparing the first photographer information stored in the server with the received second photographer information, and for reading the first image specifying information group associated with the photographer information whose comparison result matches; And only the image that matches the read first image specifying information group is stored in the server.

  According to the image transfer method of the present invention, it is possible to realize a mechanism that accepts only images taken by the person and prevents the use of images taken by others by a simple method.

1 is a diagram illustrating a configuration of an entire image transfer system according to an embodiment of the present invention. It is a flowchart figure which shows operation | movement of the imaging device and server at the time of the image photographing which concerns on one Embodiment of this invention. It is a figure which shows the structure of the photographer information and image specific information which concern on one Embodiment of this invention. It is a figure which shows the state of the image in the imaging device which concerns on one Embodiment of this invention. It is a figure which shows the structure of the photographer information and password information which concern on one Embodiment of this invention. It is a flowchart figure which shows operation | movement of PC and a server at the time of the image transfer which concerns on one Embodiment of this invention. It is a flowchart figure which shows operation | movement of PC and a server at the time of the automatic transfer of the image which concerns on one Embodiment of this invention. It is a figure which shows the edit screen of the bookbinding service which concerns on one Embodiment of this invention. It is a flowchart figure which shows the operation | movement which uses the transfer image which concerns on one Embodiment of this invention for bookbinding service. It is a flowchart figure which shows the notification process at the time of the image transfer which concerns on one Embodiment of this invention. It is a flowchart figure which shows the operation | movement of the imaging device at the time of the image photographing which concerns on one Embodiment of this invention, and the server at the time of image transmission. It is a figure which shows the structure of the photographer information which concerns on one Embodiment of this invention, image specific information, and public setting information. It is a flowchart figure which shows operation | movement of the imaging device and server at the time of confirmation and update of public setting information which concerns on one Embodiment of this invention. It is a figure which shows the structure of the photographer information at the time of public setting information update which concerns on one Embodiment of this invention, image specific information, and public setting information. It is a figure which shows the screen structure of the imaging device at the time of confirmation and update of public setting information which concerns on one Embodiment of this invention. It is a figure which shows the 2nd structure of the photographer information and image specific information which concern on one Embodiment of this invention. It is a flowchart figure which shows operation | movement of the imaging device at the time of acquiring photographer information intrinsic | native to the imaging device which concerns on one Embodiment of this invention. It is a flowchart figure which shows operation | movement of the imaging device and server at the time of encrypting and decoding of the image specific information which concerns on one Embodiment of this invention.

  An embodiment of the present invention will be described. Here, a case where a captured image is uploaded from a PC to a server after the image is captured by the imaging apparatus will be described as an example.

  FIG. 1 is a block diagram showing a configuration of an apparatus according to an embodiment of the present invention.

  The imaging apparatus 100 includes an optical system 101, an imaging element 102, a CPU 103, a primary storage device 104, a secondary storage device 105, a storage medium 106, a display unit 107, an operation unit 108, and a communication device 109. It is configured. The optical system 101 includes a lens, a shutter, and an aperture, and forms an image of light from a subject on the image sensor 102 with an appropriate amount and timing. The image sensor 102 converts light imaged through the optical system 101 into an image. The CPU 103 performs various calculations and controls each part of the imaging apparatus 100 according to the input signal and program.

  The primary storage device 104 stores temporary data and is used for the work of the CPU 103. The secondary storage device 105 stores a program (firmware) for controlling the imaging device 100, various setting information, and the like. The storage medium 106 stores image data. A display unit 107 displays a viewfinder image at the time of shooting, displays a shot image, and displays characters for interactive operation. The operation unit 108 is for accepting a user operation. The communication device 109 is for communicating with the server 110 and the PC 115.

  The server 110 is a server that stores information transmitted from the imaging device 110 or the PC 117. Reference numeral 111 denotes a CPU. A secondary storage device 113 such as a hard disk stores a program for operating the CPU. Reference numeral 112 denotes a primary storage device such as a RAM, in which a program read from the secondary storage device is stored. Reference numeral 114 denotes a communication device that communicates with the imaging apparatus 100 and the PC 115.

  A PC 120 transmits images to the server. Reference numeral 116 denotes a CPU. Reference numeral 118 denotes a secondary storage device such as a hard disk, which stores a program for operating the CPU. Reference numeral 117 denotes a primary storage device such as a RAM, which stores a program read from the secondary storage device. Reference numeral 119 denotes a display unit such as a liquid crystal display, which displays a GUI of an application operating on the PC. An operation unit 120 such as a keyboard or a mouse is used for operating an application. Reference numeral 121 denotes a communication device that communicates with the imaging device 100 and the server 110.

  FIG. 2A shows a flow when an image is taken by the imaging apparatus 100. It is assumed that photographer information is registered in the imaging device before taking an image. Here, a character string “YamadaTaro@aaa.com” is registered as photographer information. In step 200, the CPU 103 generates image specifying information. The image specifying information is information for uniquely identifying an image and is unique to each captured image. Here, it is assumed that a character string such as 302 in FIG.

  In step 201, the CPU 103 adds the generated image specifying information to the image data. Next, in step 202, the CPU 103 transmits photographer information and image specifying information to the server 110. Information to be transmitted to the server is as shown by 300 in FIG. The photographer information 301 and the image specifying information 302 form a set, and are information that associates the photographer with the photographed image.

  Here, reference numeral 400 in FIG. 4 shows image data and image specifying information when a plurality of images are captured by the imaging apparatus 100. Image specifying information 402 is embedded in the image data 401. Similarly, image specifying information 404 is embedded in the image 403. When the image 403 is captured, the photographer information 301 and the image specifying information 404 are transmitted to the server 110.

  When the photographer information and the image specifying information are transmitted from the imaging apparatus 100, the server 110 receives the transmitted information and stores it in the server. FIG. 2B shows this flow. In step 210, the CPU 111 checks whether the received photographer information is stored in the server. If the photographer information is transmitted to the server for the first time, the process proceeds to step 211. In step 211, the CPU 111 stores the received photographer information and image specifying information as new data in the server.

  Next, when the user has captured the second and subsequent images, the process proceeds to step 212, and the received image specifying information is added to the existing photographer information. Even if the image is taken once and taken at another opportunity, the process proceeds to step 212. The information stored in the server in this way is indicated by 310 in FIG. Looking at 310, it can be seen that the photographer information 311 "YamadaTaro@aaa.com" is associated with four pieces of image specifying information 312 to 315. In addition, it can be seen that the other photographer information 316 is associated with eight pieces of image specifying information. In this way, information that associates the photographer with the photographed image is stored in the server, and is stored so that the photographer for each image can be understood.

  Next, a flow when uploading a photographed image to the server will be described. The image upload may be performed directly from the imaging apparatus 100, or may be performed from the PC after the image is transferred to the PC. Here, a case where an image is uploaded from the PC 115 will be described as an example. FIGS. 6A, 6B, and 6C show the flow on the PC side when uploading images, and FIGS. 6D and 6E show the flow on the server side. is there.

  FIG. 6B shows details of step 600 in FIG. 6A, and FIG. 6C shows details of step 602. When the user uploads an image, a user authentication process is performed in step 600. Details of step 600 will be described later with reference to FIG. In step 600, the CPU 116 communicates with the server to perform user authentication processing. Next, in step 601, the CPU 116 determines whether the authentication is successful. If the authentication is successful, the CPU 116 proceeds to step 602. If authentication fails, the process proceeds to step 603 to display an authentication failure message, and the process ends. In step 602, image transmission processing is performed. Details of step 602 will be described later with reference to FIG.

  Turning to the description of FIG. In step 610, the CPU 116 receives input of photographer information from the user. The photographer information is input by the operation unit 120. Here, it is assumed that information 501 in FIG. 5A is input as photographer information. In step 611, the CPU 116 receives an input of password information from the user. The password information here is for more accurately performing user authentication processing, and can be omitted. It is assumed that password information associated with photographer information is registered in the server.

  Here, it is assumed that the information 502 in FIG. 5B is input as the password information. Next, in step 612, the CPU 116 transmits the photographer information and password information input by the user to the server. Data to be transmitted to the server is as indicated by 500 in FIG. Next, let's move on to the server description. FIG. 6D shows a flow showing the operation of the server when the photographer information and password information are received from the PC. In step 630, the CPU 111 receives photographer information and password information.

  Next, in step 631, the CPU 111 determines whether the photographer is associated with password information. Here, an example of the photographer and password information stored in the server is 510 in FIG. Photographer information 511 “YamadaTaro@aaa.com” is associated with password information 512 “password111”. Also, password information 514 is associated with the photographer information 513.

  Here, since the information 500 transmitted from the PC 115 matches the photographer information 511 and the password information 512 stored in the server, it is assumed that the authentication is successful. In step 632, the CPU 116 transmits the authentication result to the PC 110. Returning to the description of FIG. In step 613, the CPU 116 stands by until an authentication result is returned from the server. When the authentication result is received from the server, the flow in FIG. That is, the process proceeds to step 601 in FIG. Here, since the authentication is successful, the process proceeds to step 602.

  Details of step 602 will be described with reference to the flowchart of FIG. In step 620, the CPU 116 receives an input of an image to be transmitted to the server from the user. It is assumed that the user can select an image to be transmitted to the server from among the captured images. Here, it is assumed that four images 401, 403, 405, and 407 in FIG. 4 have been selected.

  Next, in step 621, the CPU 116 transmits photographer information and an image to the server. Next, let's move on to the server description. FIG. 6E shows a flow showing the operation of the server when the photographer information and the image are received from the PC. In step 640, the CPU 111 receives photographer information and an image from the PC. Next, in step 641, the CPU 111 calculates the total number N of received images. Since four images have been selected in step 620 described above, the value of N is 4. Next, in step 642, the CPU 111 initializes the value of n to 1.

  Next, in step 643, the CPU 111 repeats the processing of steps 645 to 647 four times. Next, in step 644, the CPU 111 reads the image specifying information in the received nth image. Here, since n is 1, the image specifying information 402 of the image 401 is acquired. Next, in step 645, the CPU 111 checks whether the received photographer information is associated with the image specifying information read in step 644 using the information 310 stored in the server.

  Here, since the photographer information 311 and the image specifying information 312 are associated with each other, the process proceeds to step 646. In step 646, the CPU 111 stores the received nth image in the server. That is, the image 401 is stored in the server. In this way, the information 310 stored in the server is used to determine whether the image was taken by the user, and only when the image is determined to be taken by the user, the image is stored in the server. If the photographer information and the image specifying information are not associated with each other in step 645, it is determined that the photographer is not an image photographed by the person himself, and the server proceeds to step 647 without storing the image in the server.

  In step 647, the CPU 111 increments the value of n. Here, since the value of n is 1, the value of n is 2. In this way, steps 644 to 647 are repeated for the number of images. When all the images have been processed, the process proceeds to step 648. In step 648, the CPU 111 transmits the storage result at the server to the client. For example, if all the images can be stored in the server, a response is sent to the client so that it can be understood. If there is an image that is not saved on the server, the file name is sent as a response to the client.

  Returning to the description of FIG. After the photographer information and the image are transmitted to the server in step 621, the CPU 116 waits until a response is returned from the server in step 622. When a response is returned from the server, the process proceeds to step 623. In step 623, the CPU 116 analyzes the response from the server and determines whether the image transmission is successful. If all the transmitted images have been transmitted to the server, the process proceeds to step 624. In step 624, the CPU 116 displays a message indicating successful image transmission. If it is determined that all the images transmitted in step 623 cannot be stored in the server, the process proceeds to step 625.

  In step 625, the CPU 116 displays a message indicating that image transmission has failed. Here, the file name of the image that failed to be transmitted may be displayed. As described above, the photographer of the image can be determined using the flow of FIG. 6, and only the image photographed by the person can be stored in the server. In the above description, the image is transmitted from the PC to the server after the image is captured. However, the image may be transmitted directly from the imaging device to the server.

  In the description so far, the user has selected an image to be sent to the server. Here, since the image specifying information for each photographer is stored in the server, the image captured by the person himself / herself may be automatically transmitted from the PC or the imaging device using the information. The flow of FIG. 7 is an example in the case of transmitting photographer information to the server, and automatically determining only the image taken by the person from the images stored on the PC and transmitting it to the server. Here, FIG. 6A, which is the overall flow of this processing, and FIG. 6B, which is processing on the client side of user authentication, are the same as the above-described flow, and thus description thereof will be omitted.

  FIG. 7A shows a flow on the server side after the photographer information and the password are transmitted to the server in step 612. Steps 700 and 701 are the same as steps 630 and 631 in FIG. In step 702, the CPU 111 determines whether the user authentication is successful. If successful, the process proceeds to step 703. In step 703, the CPU 111 transmits image specifying information associated with the photographer information to the server. That is, if the photographer information received by the server is 311 in FIG. 3B, the image specifying information 312 to 315 is transmitted to the client.

  If the authentication fails in step 702, the process proceeds to step 704. In step 704, the CPU 111 transmits an authentication failure response to the client. In this way, in FIG. 6D, only the success or failure of the authentication is transmitted to the client. However, when the authentication is successful, information 312 to 315 representing the image taken by the person is transmitted to the client. To do. If the authentication is successful, in step 602, the CPU 116 performs image transmission processing. FIG. 7B shows the details of the transmission process when an image is automatically transmitted. In step 710, the CPU 116 receives the image specifying information from the server.

  Next, in step 711, the CPU 116 calculates the total number N of images stored in the PC. Since Steps 712 to 714 are the same as Steps 642 to 644 described above, description thereof will be omitted. In step 715, the CPU 116 determines whether the read image specifying information is included in the image specifying information transmitted from the server. For example, if the image specifying information read in step 714 is 312, it is included in the image specifying information received from the server, so the process proceeds to step 716. In step 716, the CPU 116 transmits the nth image to the server.

  Next, in step 717, the CPU 116 increments the value of n. Here, since the value of n is 1, the value of n is 2. In this way, by repeating steps 714 to 717 for the number of images stored in the PC, only the images taken by the person can be transmitted to the server.

  Next, an example in which an image automatically transferred to the server is used as an image used for the bookbinding service will be described. The bookbinding service here is a service that creates a book on the Web using digital images, and that can publish the book on the Web or create a book that has actually been bound. This bookbinding service can be operated by a Web browser on the PC 115 or a dedicated application. Here, reference numeral 800 in FIG. 8 shows an example of the bookbinding service. The image display area 801 has a book shape so that an operator can place an image.

  Reference numerals 806 and 807 denote page switching buttons, which can switch pages. FIG. 9 shows a flow when the bookbinding service is started using the image received on the server side after the image is automatically transmitted from the client. In step 900, the CPU 111 receives an image sent from the client. In step 901, the CPU 111 calculates the total number N of received images. Next, in step 902, the CPU 111 initializes the value of n to 1.

  Next, in step 903, the CPU 111 repeats the processing of steps 904 and 905 N times. In step 904, the CPU 111 uses the nth image for the bookbinding service. For example, if the first image is 401 in FIG. 4, the image is displayed in 802 on the image display area of the product service. Next, in step 905, the CPU 111 increments the value of n. In this way, by using the image transmitted to the server as the image used for the bookbinding service, the user can easily use the bookbinding service.

  In the description so far, even when an image taken by the person and an image taken by another person are mixed, only the image taken by the person on the server side is accepted. Here, when a user tries to use an image of another person, it is desirable that there is a mechanism capable of detecting that. Here, an example in which a predetermined operation is performed on the server side when an image associated with other person's photographer information is to be uploaded will be described. FIG. 10 shows this flow.

  The flow of FIG. 10 is obtained by adding steps 1009 and 1010 to the flow of FIG. Steps 1000 to 1008 are the same as steps 640 to 648 in FIG. In step 1009, the CPU 111 determines whether image specifying information that is not associated with photographer information is associated with other person's photographer information. For example, when the photographer information transmitted by the user is 311 and the image specifying information is 317, the process proceeds to step 1010 because it is associated with the photographer information 316 of another person. In step 1010, the CPU 111 notifies the photographer associated with the server administrator and the image specifying information. That is, when an attempt is made to upload an image photographed by another person but not photographed by the other person, notification is performed. In this way, a mechanism for detecting a user who uses an image can be realized.

  Here, depending on the photographer and the photographed image, it may be possible to allow others to use the image. Therefore, it is desirable that there is a mechanism that allows an image to be used by anyone other than the user. Therefore, this mechanism can be realized by providing public setting information for each image. The flow in FIG. 11A is a flow showing processing of the imaging apparatus when an image is taken. It is assumed that the public setting is input to the imaging apparatus together with the above-described photographer information. In step 1100, the CPU 103 acquires the public setting information input to the imaging apparatus.

  Here, it is assumed that the setting is permitted to be disclosed. Images taken with this setting can be used by anyone other than the photographer. Note that if it is not permitted to be used by another person, it may be set so as not to permit disclosure by the imaging device. Steps 1101 and 1102 are the same as steps 200 and 201 in FIG. In step 1103, the CPU 103 transmits photographer information, image specifying information, and public setting information to the server. Here, 1200 of FIG. 12A shows an example of information to be transmitted to the server.

  Here, it is assumed that the photographer information 1201, the image specifying information 1202, and the public setting information 1203 are transmitted to the server. In this way, information including the public setting is stored in the server. An example of information stored in the server is 1210. Here, four pieces of image specifying information are associated with the photographer information 1211, of which 1212 and 1213 are images permitted to be disclosed, and 1214 and 1215 are images not permitted to be disclosed. Is shown. Next, FIG. 11B is a flowchart showing an operation when uploading an image from the PC.

  Here, steps 1110 to 1118 are the same as steps 640 to 648 in FIG. In the flow of FIG. 6E described above, if the photographer information and the image specifying information are not associated in step 645, the image is not stored in the server. Here, in step 1119, the CPU 111 determines whether publication is permitted or an image. For example, assume that a user having photographer information 1211 transmits an image having 1217 image specifying information to the server. In this case, the image specifying information 1217 is not associated with the photographer information 1211, but is included in the other image specifying information 1217 and permitted to be disclosed.

  In such a case, it is determined that the image is permitted to be disclosed by another person, and the process proceeds to step 1116. The processing in step 1116 is as described above. In this way, even if the image is not taken by the user, the transmitted image can be stored on the server as long as the image is permitted to be disclosed by another person.

  In the case of the above-described example, it is possible to change the disclosure setting at any time and take an image. In such a case, it is desirable to be able to confirm what public settings the captured image has. FIGS. 13A and 13B are flows for acquiring public setting information of a captured image. FIG. 13A shows a flow on the imaging apparatus side when the user requests confirmation of the public setting on the imaging apparatus. In step 1300, the CPU 103 transmits photographer information to the server. It is assumed that photographer information has already been input as in the above-described embodiment.

  FIG. 13B shows a flow on the server side when the photographer information is transmitted to the server. In step 1310, the CPU 111 receives photographer information from the client. In step 1311, the CPU 111 transmits image specifying information and public setting information associated with the received photographer information to the client. For example, when the photographer information received from the client is 1401 and the information stored in the server is 1400, the information 1410 is transmitted to the client.

  This includes public setting information 1411 to 1416 corresponding to the image specifying information. Returning to the description of FIG. In step 1301, the CPU 103 waits until a response is returned from the server. When a response is returned from the server, the process proceeds to step 1302. In step 1302, the CPU 103 displays the public setting information corresponding to the image in the imaging apparatus. FIG. 15A shows a UI in the imaging apparatus. It can be seen that images 1501 to 1506 are displayed on the display unit of the imaging apparatus 1500.

  Each image has a check box. If the image is permitted to be released, the image is checked. In this way, the public setting information for each image can be confirmed.

  Here, there is a case where it is desired to change the public setting information after taking an image. FIGS. 13C and 13D are flowcharts for changing the public setting information of the captured image. FIG. 13A shows a flow on the imaging apparatus side when the user requests to change the public setting on the imaging apparatus. When the button 1507 in FIG. 15A is selected, the mode changes to a mode for changing the public setting. FIG. 15B shows the UI of the imaging apparatus when the mode changes to the public setting change mode. After the check box of the displayed image is switched ON / OFF, by selecting a button 1513, the public setting information update process is transmitted to the server.

  Here, a case will be described as an example where the user selects the button 1513 in a state where the public setting of the images 1511 and 1512 is not permitted. In step 1320, the CPU 103 receives the input of the target image and the public setting information. In step 1321, the CPU 103 transmits the input information to the server. Here, reference numeral 1420 in FIG. 14C indicates information to be transmitted to the server. FIG. 13D shows a flow on the server side when information is transmitted to the server. In step 1330, the CPU 111 receives information transmitted from the client.

  Next, in step 1331, the CPU 111 updates information related to the public settings stored in the server according to the received information. That is, what was in the state 1400 before the update becomes the state 1420. In this way, the public setting information for each image can be changed even after the image is taken.

  In the above description, each image has a public setting information. Here, the image disclosure setting may be changed according to the area in which the image is stored in the server. For example, if the image is to be used only by the photographer, the image specifying information is held in a region dedicated to the photographer. Further, if the image allows use by others, the image specifying information is held in the shared area. FIG. 16 shows a configuration having an area dedicated to the photographer and a shared area.

  Reference numerals 1601 and 1602 denote areas dedicated to the photographer, and the image specifying information stored here can be used only by the photographer himself / herself. Reference numeral 1603 denotes a shared area, and the image specifying information stored here can be used by all users. In order to realize such a mechanism, the user can select which area to use when capturing an image.

  Next, an example in which a value unique to the imaging apparatus is set in advance as photographer information will be described. If the photographer information is set in advance, it is possible to save the user from inputting the photographer information before the image is taken or before the image is transmitted to the server. As a value uniquely set for each imaging apparatus, a UUID is considered. In addition, by uploading an image to the server, the user and the user involved in the user authentication process can be reduced by connecting the PC and the imaging device. The flow in FIG. 17 shows a flow in the case of uploading an image to the server with the PC and the imaging device connected.

  Compared with FIG. 6B, it can be seen that steps 610 and 611 are eliminated and step 1700 is increased instead. In this method, the procedure of authenticating using the photographer information and password information input by the user is replaced with the photographer information acquired from the imaging apparatus. That is, if it is a person who has an imaging device, it will determine with the person who image | photographed the image.

  Next, a case will be described as an example in which the image specifying information is encrypted and embedded when embedding the image specifying information in the image. Here, it is assumed that the image identification information is encrypted using the photographer information and embedded in the image, and the image identification information is decrypted when the image identification information is read by the server. FIG. 18A shows a flow when an image is taken, and FIG. 18B shows a flow when image specifying information is compared by a server. The difference between FIG. 18A and FIG. 2A is that step 1801 is added. In step 1801, the CPU 103 encrypts the image specifying information using the photographer information.

  In this way, the encrypted image specifying information is embedded in the image. Note that the image specifying information before encryption is transmitted to the server in step 1803. Next, a description will be given of the flow in FIG. The difference between FIG. 18B and FIG. 6E is that step 1815 is added. In step 1815, the CPU 111 decodes the image specifying information using the photographer information. Thus, by encrypting the image specifying information using the photographer information, it becomes more difficult to analyze the image specifying information.

  Although the present invention has been described in detail based on preferred embodiments thereof, the present invention is not limited to these specific embodiments, and various forms within the scope of the present invention are also included in the present invention. included. A part of the above-described embodiments may be appropriately combined.

  The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

100 imaging device, 101 optical system, 102 imaging device, 103 CPU

Claims (12)

In the server that can store the image, the first photographer information and the first image specifying information group are received from the imaging device, and the two pieces of information are associated with each other and stored from the imaging device or any information device. Means for receiving the second photographer information and the image group and reading out the second image specifying information group embedded in the received image, and the first image stored in the server when the image group is received; Means for comparing the photographer information with the received second photographer information, and for reading a first image specifying information group associated with the photographer information whose comparison result matches, and reading the first image An image transfer method, wherein only an image that matches a specific information group is stored in a server.   2. The image transfer method according to claim 1, wherein when the received second image specifying information is associated with other photographer information, a predetermined operation is performed on the server.   The image transfer method according to claim 2, wherein the predetermined operation is notification to a server administrator or notification to a photographer associated with image specifying information.   When receiving the first photographer information and the first image specifying information group from the imaging device, the first photographer information is received together with the public setting information for each image, and the image group is received and the image specifying information is compared. 2. The image transfer method according to claim 1, wherein storage of an image including the public setting information is controlled.   5. The image transfer method according to claim 4, wherein the photographer information is received from the imaging device or an arbitrary information device, and the image specifying information associated with the received photographer information is transmitted.   5. The photographer information, the image specifying information, and the public setting information are received from the imaging device or an arbitrary information device, and the public setting information for each image associated with the received photographer information is updated. The image transfer method described in 1.   Even when the received second image specifying information is associated with other photographer information, the predetermined operation is not performed when the information permitted to be disclosed is added. The image transfer method according to any one of claims 2 to 4.   2. The image transfer method according to claim 1, wherein whether or not image storage is to be controlled is determined by comparing image specifying information in accordance with server settings.   The image transfer method according to claim 1, wherein the photographer information is a unique value assigned in advance according to the imaging apparatus.   2. The image transfer method according to claim 1, wherein the image specifying information in the image is embedded by being encrypted.   Means for receiving the first photographer information and the first image specifying information group from the imaging device and storing the two pieces of information in association with each other; and the second photographer information from the imaging device or any information device. A server having a means for receiving and transmitting a second image specifying information group associated with the received second photographer information to the imaging device or an arbitrary information device; and receiving the second image specifying information Then, the image specifying information for each image stored in the device is read out, compared with the second image specifying information, and only an image whose comparison result matches is transmitted to the server or any information An image transfer method comprising an apparatus.   12. The image transfer method according to claim 11, wherein when the image is received by the server, the received image is used as an image used for the bookbinding service.