JP2005301338A - Image service system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a management system by which images stored on a plurality of servers providing image services are effectively shared. <P>SOLUTION: A control management part 101 transmits registration information stored in a service management table, an image identified with identification information included in the registration information, and attached information inputted in a registration picture to a service server 2 specified with the registration information (S13). A processing part 21 of the service server 2 once receiving the registration information, image, and attached information stores them as browsed information in a browsed information management table in a service DB 22 while making them correspond to one another (S14). A user of a terminal 4a, therefore, need not upload an image a plurality of times by accessing respective service servers 2 even when the image uploaded to one service server is browsed on other service servers 2. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a system that provides a service using an image, and more particularly to a system that centrally manages an image that is commonly used in a plurality of systems that provide a service that uses an image.

In recent years, services for uploading images taken by individual users and browsing the images on the Internet have become widespread. For example, according to Patent Document 1, a registered user accesses a dedicated site of a website management server using a computer or a mobile phone, selects an image uploaded to a photographic image data storage area, and stores content using the selected image data. Select from the content group provided by the administrator computer group. By doing in this way, the image of the same user can be reused with a plurality of contents.
JP 2002-189723 A

  However, in the technique of the above-described Patent Document 1, it is necessary to collectively manage all images used by the content manager computer group in the website management server and the photographic image data storage area, and the image management burden is large. The present invention has been made in view of such problems, and an object of the present invention is to provide a management system capable of effectively sharing images stored in a plurality of servers that provide image services.

  In order to solve the above-mentioned problem, the invention according to claim 1 is any one of the plurality of service servers that allow images uploaded from user terminals to be viewed on different service browsing screens, and the plurality of service servers. An image service system comprising a management server for browsing an image uploaded to a service server of another service server on a service browsing screen of another service server, each service server including an image uploaded from a user terminal and other A first database for managing image link information for accessing an image managed by the service server, the uploaded image and registration information of an image corresponding to the image link information, and the uploaded Register an image and registration information of the image in the first database. And registration means for registering image registration information and image link information transmitted from the management server in the first database, and registration information, image link information and reduced image of the uploaded image to the management server. A first transmission means for transmitting, a second database for managing the registration information, image link information, and reduced image transmitted from each service server for each user, and a request from a user terminal. And a means for causing the user terminal to display a list of registration information and reduced images corresponding to a user image among the registered information and reduced images managed in the second database, and the list displayed Different from the registration information of the service server registered in the second database for the image selected from the reduced images. Registration information receiving means for receiving registration information of the service server, registration information for the service server received by the registration information receiving means and image link information of the selected image are added to the second database and correspondingly Second transmitting means for transmitting to the service server.

  According to the present invention, an image stored in one service server can be used in another service server. That is, it is possible to share images between service servers by utilizing the resources of existing service servers.

  According to a second aspect of the present invention, in the image service system according to the first aspect, the service server further includes image processing means for performing predetermined image processing on the uploaded image, and the registration information receiving means is the image information receiving means. Receiving an input of registration information for designating which service server the processed image is to be used for, and the second transmission means further receives image link information of the image processed image in the service server designated by the registration information Send.

  According to the present invention, an image obtained by performing predetermined image processing on an image uploaded to a certain service server can be used by another service server.

  According to a third aspect of the present invention, in the image service system according to the first or second aspect, the management server includes a print order receiving unit that receives a print order that is an order for printing the image in a predetermined format and number of sheets. Printing means for printing the image based on the print order.

  According to the present invention, an image uploaded to each service server can be printed.

  According to the present invention, an image stored in one service server can be used in another service server. That is, it is possible to share images between service servers by utilizing the resources of existing service servers.

  Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings.

<First Embodiment>
[Schematic configuration]
FIG. 1 is a schematic configuration diagram of an image service system according to a preferred embodiment of the present invention. This system includes a plurality of service servers 2a to 2d that allow the terminal 4b to browse images and comments uploaded from the terminal 4a via the network 7 such as the Internet, and service servers 2a to 2d that are provided from the terminal 4a. The central management server 1 is provided that transmits the uploaded image and the like to all or a part of the other service servers 2a to 2d in accordance with registration information described later inputted from the terminal 4a. The overall management server 1 has a processing unit 11 constituted by a CPU and a management DB 12 constituted by a relational database or the like. The processing unit 11 has an overall management unit 101 as an execution program. Processing executed by the overall management unit 101 will be described later. Each service server 2a to 2d has a processing unit 21 constituted by a CPU and a service DB 22 constituted by a relational database or the like. The processing unit 21 includes a service management unit 201 and an image processing unit 202 as programs. The processing of the service management unit 201 will be described later. Based on an instruction from the terminal 4a, the image processing unit 202 performs various image processing such as brightness correction, sepia processing, frame composition, and monochrome conversion of an image uploaded from the terminal 4a to the service server 2.

  The terminal 4a may be any device as long as it can transmit images and various information such as comments attached to images (hereinafter referred to as supplementary information) to the overall management server 1 via the network 7, for example, a personal computer or a mobile phone with a camera. It is a telephone. The terminal 4b may be any device that can access the service server 2 via the network 7 and browse images and the like, such as a personal computer, a mobile phone with an Internet connection function, and a PDA. In the present embodiment, the photo collection server 2a, the photo map server 2b, the photo diary server 2c, and the photo contest server 2d are collectively referred to as the service server 2. The service server 2 is not limited to the above as long as it has a function of allowing the terminal 4b to browse images and supplementary information via the network 7, and may browse images and the like in any format.

  The photo collection server 2a categorizes images taken with a digital camera or the like in order to record changes in seasons, growth of children, etc., and information and comments about the shooting date and time or shooting location in each image. It is a server to which additional information consisting of etc. is added for browsing. FIG. 2 shows an example of a browsing information management table stored in the service DB 22a of the photo collection server 2a. In the service DB 22a of the photo collection server 2a, a user ID for identifying the user of the terminal 4a, a user nickname, and a collection ID that defines a unit for viewing each image, which are common to the overall management server 1 and all the service servers 2. Categories for classifying images, titles, introduction comments, used image identification information (in this case, image file names) that is information for identifying images to be browsed, and identification information on the network 7 that the terminal 4b accesses to browse images ( Here, browsing information corresponding to information (viewing permission / inhibition information) such as URL) and information indicating whether browsing is possible is stored. The processing unit 21a of the photo collection server 2a browses incidental information including images, nicknames, categories, titles, and introduction comments based on the browsing information. That is, when the URL included in the browsing information is accessed from the terminal 4b and the browsing permission / inhibition information corresponding to the URL is “permitted”, the photo collection server 2a displays the image and incidental information corresponding to the URL in the terminal 4b. Let them browse. It is assumed that the image data itself identified by the use image identification information is stored in the service DB 22a. However, the image data itself is stored in a resource other than the service DB 22a (for example, a service server 2 other than the photo collection server 2a, the overall management system 1, or another file server), and the service DB 22a includes a part of the used image identification information. Link information specifying a resource storing image data may be stored.

  The photo map server 2b allows the user of the terminal 4a to specify the location where the subject is photographed on the electronic map and accepts uploading of images and supplementary information. Then, for the terminal 4b that has accessed the photo map server 2b, the thumbnail image of the uploaded image is displayed at the designated location on the electronic map, and the location is designated from the terminal 4b so that the image corresponding to the location is displayed. The terminal 4b is made to browse the incidental information. FIG. 3 shows an example of a browsing information management table stored in the service DB 22b of the photo map server 2b. In the service DB 22b of the photo map server 2b, a user ID that identifies the user of the terminal 4a in common with the overall management server 1 and all the service servers 2, a nickname of the user, a map ID that defines a unit for browsing each image, The shooting date, the shooting prefecture, which is information for specifying the shooting location on the electronic map, the used image identification information (here, the file name), which is information for identifying the image to be browsed, and the browsing information corresponding to the title and comment are stored. Is done. The processing unit 21b of the photo map server 2b browses images based on browsing information stored in the service DB 22b. That is, when the photo map server 2b is accessed from the terminal 4b, the thumbnail image of the uploaded image is displayed at each location together with the electronic map, and the location where the thumbnail image is displayed is designated from the terminal 4b. The terminal 4b is made to browse incidental information including an image corresponding to, a nickname, a shooting date, a shooting prefecture, a title, and a comment. It is assumed that the image data itself identified by the used image identification information is stored in the service DB 22b. However, the image data itself is stored in a resource other than the service DB 22b (for example, a service server 2 other than the photo map server 2b, the overall management system 1 or other file server), and the service DB 22b includes a part of the used image identification information. Link information specifying a resource storing image data may be stored.

  The photo diary server 2c accepts uploading of images and incidental information after allowing the user of the terminal 4a to specify a posting date that is a date for posting an image. Then, the calendar image is displayed on the terminal 4b that has accessed the photo diary server 2c, the posting date of the image is designated, and the image posted on the designated posting date and the accompanying information are browsed in a diary format. FIG. 4 shows an example of a browsing information management table stored in the service DB 22c of the photo diary server 2c. In the service DB 22c of the photo diary server 2c, a user ID that identifies the user of the terminal 4a, a user nickname, and a diary ID that defines the unit of browsing of each image in common to the overall management server 1 and all the service servers 2, The browsing information corresponding to the category, the posting date, the comment, and the use image identification information (here, the file name) that is information for identifying the image to be browsed is stored. The processing unit 21c of the photo diary server 2c browses an image based on browsing information stored in the service DB 22c. That is, when the photo diary server 2c is accessed from the terminal 4b, an icon image indicating that there is a post on the posting date is displayed together with a calendar image displaying each date, and the date of the icon image displayed from the terminal 4b is displayed. The terminal 4b is made to designate the incidental information including the image corresponding to the designated date, the nickname, the category, the posting date, and the comment. It is assumed that the image data itself identified by the use image identification information is stored in the service DB 22c. However, the image data itself is stored in a resource other than the service DB 22c (for example, a service server 2 other than the photo diary server 2c, the overall management system 1, or another file server), and the service DB 22c stores a part of the used image identification information. Link information specifying a resource storing image data may be stored.

  The photo contest server 2d accepts uploading of incidental information such as images and comments from the terminal 4a. The administrator of the photo contest server 2d evaluates the content of the uploaded image, and causes the terminal 4b that has accessed the photo contest server 2d to browse the image with particularly excellent content. FIG. 5 shows an example of a browsing information management table stored in the service DB 22d of the photo contest server 2d. In the service DB 22d of the photo contest server 2d, a user ID that identifies the user of the terminal 4a in common with the overall management server 1 and all the service servers 2, a contest ID that defines a unit for viewing each image, a user nickname, The browsing information corresponding to the title, the posting date, the comment, and the use image identification information (here, the file name) that is information for identifying the image to be browsed is stored. The photo contest server 2d browses images based on browsing information stored in the service DB 22d. That is, when the photo contest server 2d is accessed from the terminal 4b, the photo contest server 2d displays thumbnail images of images identified by all the used image identification information stored in the service DB 22d and selects an arbitrary thumbnail image. Let When a thumbnail image is selected, the photo contest server 2d transmits an image corresponding to the thumbnail image to the terminal 4b for browsing. It is assumed that the image data itself identified by the use image identification information is stored in the service DB 22d. However, the image data itself is stored in a resource other than the service DB 22d (for example, a service server 2 other than the photo contest server 2d, the overall management system 1 or other file server), and the service DB 22d has a part of used image identification information. Link information specifying a resource storing image data may be stored.

  As described above, the photo collection server 2a, the photo map server 2b, the photo diary server 2c, and the photo contest server 2d have been described as one aspect of the service server 2. However, the service server 2 displays the images uploaded from the terminal 4a in various formats in the terminal 4b. Needless to say, it is not limited to the above as long as it has a function of browsing. Hereinafter, information stored in the service DB 22 is referred to as browsing information, and an image identified by the use image identification information stored in the service DB 22, that is, an image that the service server 2 causes the terminal 4b to browse is referred to as a browsing image.

  Returning to FIG. 1 again, the overall management server 1 receives information for ordering printing of an image uploaded from the terminal 4a (hereinafter referred to as order information). The photo print server 3 prints an image based on the order information transmitted from the terminal 4a to the overall management server 1. The printed matter on which the image is printed may be mailed to the address specified by the order information, or may be stored by the administrator of the photo print server 3 and directly delivered to the user of the terminal 4a who has picked up the image. . FIG. 6 is an example of print information stored in the print DB 32 of the photo print server 3. The print DB 32 includes a user ID that identifies the user of the terminal 4a in common with the overall management server 1 and all the service servers 2, a print ID that defines the unit of the print job, use image identification information that identifies an image to be printed, and Order information defining the contents of the printed matter desired by the user of the terminal 4a is stored correspondingly. The order information may include a mailing address of the printed matter in addition to the illustrated contents. The photo print server 3 prints an image on a printer (not shown) based on information stored in the print DB 32.

  FIG. 7 shows an example of the contents of the image management table stored in the management DB 12 of the overall management server 1. In the image management table, a user ID for identifying the user of the terminal 4a, the original image identification information, and the processed image identification information are stored in association with each other in the overall management server 1 and all the service servers 2. The original image identification information is identification information of an original image that is an image uploaded to the service server 2 from the terminal 4a. The processed image identification information is information for identifying a processed image that is an image obtained by performing image processing on the original image by the image processing unit 202. That is, in the image management table, the original image and the processed image are distinguished from each other, and the both are not confused. In this figure, the processed image identification information “image1′.jpg” corresponds to the original image identification information “image1.jpg”. Although not shown, the management DB 12 can also store a plurality of processed image identification information in association with one original image identification information. Naturally, when no image processing is performed on the original image, the processed image identification information is not stored in correspondence with the original image identification information. Further, as described above, it is assumed that the image data itself identified by the original image identification information or the processed image identification information is stored in the service DB 22. However, the image data itself is stored in a resource (for example, the overall management system 1 or other file server) other than the service DB 22, and the management DB 12 stores the image data as part of the original image identification information or the processed image identification information. Link information specifying a resource may be stored.

  FIG. 8 shows an example of the contents of the service management table stored in the management DB 12. The service management table is information stored for identifying, with the overall management server 1, an image to be browsed by a plurality of service servers 2, and includes a table created for each service server 2. In this embodiment, since the service server 2 is four of the photo collection server 2a, the photo map server 2b, the photo diary server 2c, and the photo contest server 2d, as shown in FIGS. 8A to 8D, A collection management table, a map management table, a diary management table, and a contest management table, which are tables corresponding to these, are stored in the management DB 12. The structures of the tables included in the service management table are common, and a user ID, a collection ID, a map ID, a diary ID or a contest ID, and used image identification information are stored correspondingly. The overall management server 1 can identify which image is being used by which service server 2 by referring to the service management table. In particular, the same use image identification information may be stored in a plurality of service management tables. For example, as shown in this figure, the used image identification information “image1.jpg” is stored in the collection management table, the diary management table, and the contest management table. The collection ID, the map ID, the diary ID, and the contest ID define a unit for browsing an image on each service server 2. The overall management server 1 uniquely assigns the collection ID, map ID, diary ID, and contest ID. Hereinafter, the collection ID, map ID, diary ID, and contest ID are collectively referred to as a service ID. The service ID also has a function of identifying which service server 2 uses the corresponding image.

[Process flow]
Hereinafter, the flow of processing executed in the present system will be described based on the flowchart of FIG. In this system, registration information for specifying whether or not an image uploaded to a service server 2 from a terminal 4a identified by a user ID is to be used in another service server 2 is input from the terminal 4a, and the overall management server 1 transmits the image (or its identification information) uploaded according to the registration information to the designated service server 2.

  In S1, the service management unit 201 of the service server 2 authenticates the terminal 4a with the user ID and permits access, and accepts upload of one or more images and input of incidental information. In S2, the service management unit 201 issues a unique service ID and associates the service ID with the uploaded image and the input incidental information and stores them in the browsing information management table of the service DB 22. For example, as shown in FIG. 8A, a unique collection ID “CL001” is issued and stored in the collection management table for the authenticated user ID and the identification information image1.jpg of the image 123-1. . In S <b> 3, the service management unit 201 transmits the user ID, the service ID, and the corresponding image from the service DB 22 to the overall management server 1. In S10, the overall management unit 101 stores the received image identification information in the image management table in association with the received user ID as the original image identification information. The overall management unit 101 stores registration information in which the received user ID, service ID, and image identification information are associated with each other in the service management table corresponding to the received service ID.

  In S11, the overall management unit 101 authenticates the terminal 4a with the user ID and permits access, displays a list of thumbnail images of the images identified by the original image identification information stored in the image management table, and displays the images. A registration screen for displaying a check box 121 for designating which service server 2 is to be used and a text box 122 for inputting incidental information is transmitted to the terminal 4a for display. FIG. 10 shows an example of a registration screen, which lists thumbnail images 123-1, 123-2, and 123-3 of the three images identified by the three original image identification information images1.jpg, image2.jpg, and image3.jpg. it's shown. Hereinafter, for the sake of simplicity, the images identified by the use image identification information and their thumbnail images are treated as being the same. Information input to the check box 121 and the text box 122 from the terminal 4a is transmitted to the overall management unit 101 by CGI (Common Gateway Interface), and the overall management unit 101 receives this information as registration information. This registration screen displays four check boxes 121a-d and text boxes 122a-d for each of the four service servers 2a-d as a registration unit 112 corresponding to each image. That is, the number of check boxes 121 and text boxes 122 displayed on the registration screen may be increased or decreased according to the number of service servers 2. Further, the number of registration units 112 displayed on the registration screen may be increased or decreased according to the number of original images. For example, in this figure, it is input that the image 123-1 is used by the photo collection server 2a, the photo diary server 2c, and the photo contest server 2d. Although not shown, incidental information can be input in the text box 122. Hereinafter, information indicating the contents input to the check box 121 and the text box 122 corresponding to a certain image is also represented by registration information.

  In S12, when the registration button 126 displayed on the registration screen is pressed, the overall management unit 101 issues a unique service ID used by the service server 2 designated on the registration screen, and the user ID, service ID, Registration information in which the identification information of the original image is associated is stored in the service management table (see FIG. 8). As an example, in FIG. 10, it is input that the image 123-1 having the image identification information image1.jpg is used by the photo collection server 2a, the photo diary server 2c, and the photo contest server 2d. Therefore, as shown in FIG. 8C, a unique diary ID “D001” is issued and stored in the diary management table for the authenticated user ID and the identification information image1.jpg of the image 123-1. The Further, as shown in FIG. 8C, a unique contest ID “CON001” is issued and stored in the contest management table for the authenticated user ID and the identification information image1.jpg of the image 123-1. . Although not shown, the incidental information input in the text box 122 may also be stored in the service management table.

  In S13, the overall management unit 101 uses the registration information stored in the service management table, the image identified by the identification information included in the registration information, and the incidental information input on the registration screen, as a service server specified by the registration information. 2 to send. In S <b> 14, when the processing unit 21 of the service server 2 receives the registration information, the image, and the incidental information, these are associated with each other and stored as browsing information in the browsing information management table of the service DB 22. As an example, when registration information as shown in FIG. 8C is transmitted to the photo diary server 2c, browsing information as shown in FIG. 4 is stored.

  In S15, the overall management unit 101 determines whether any image is selected by clicking or the like on the registration screen and the image processing button 150 is pressed. If the image processing button 150 is pressed, the process proceeds to S16, and if not, the process proceeds to S19.

  In S16, the overall management unit 101 transmits an image processing screen as illustrated in FIG. 11 to the terminal 4a. The terminal 4a displays an image processing screen. On this screen, the original image selected in S15 is displayed. On this screen, an instruction to perform desired image processing on the original image can be designated by selecting from the list box 140. The image processing that can be selected is arbitrary, for example, brightness correction of an uploaded image, sepia processing, predetermined frame composition, monochrome conversion, and the like. In this figure, frame synthesis processing is selected. When the execute button 128 is pressed on this screen, the image processing unit 202 executes the image processing selected in the list box 140 for the original image selected in S15. When the image processing is completed, a processed image that is an image obtained as a result of the image processing is displayed on the screen. In this figure, a processed image 123-4 in which a frame is combined with the original image 123-1 is displayed. The image data of the processed image is stored in the service DB 22, and the identification information of the processed image 123-4 is stored in the image management table in association with the identification information of the original image that is the source of the image processing as the processed image identification information. . As an example, in FIG. 7, the original image identification information of image1.jpg and the processed image identification information of image1′.jpg are associated with each other.

  In S <b> 18, the overall management unit 101 changes the image used in each service server 2 from the original image to the processed image in response to an input to the browse image change specifying unit 127 displayed on the image processing screen. The browse image change specifying unit 127 is a button 132 for specifying that the processed image created in S17 is newly added as a browse image, and a list box for inputting incidental information for the processed image when the processed image is newly set as a browse image. 135, a button 133 for designating that the browse image is changed from the original image to the image processed in S17, and a button 134 for designating that the browse image remains the original image. The buttons 132 to 134 and the list box 135 are provided for each service server 2. In this embodiment, the buttons 132a to 132d, the buttons 133a to 133d, the buttons 134a to 134d, and the list boxes 135a to 135d corresponding to the four service servers 2a to 2d are provided. d is displayed. The information input from the terminal 4a to the browsing image change designation unit 127 is transmitted from the terminal 4a to the overall management unit 101 as in S13. If the button 134 is specified and the execution button 128 is pressed, the process proceeds to S21. If the button 132 or the button 133 is specified and the execution button 128 is pressed, the process proceeds to S19.

  In S19, when the button 132 is pressed in S18, the overall management unit 101 issues the service ID of the service server 2 corresponding to the buttons 132a to 132d specified on the processed image registration screen, and the user ID, service ID, and processing are issued. The image identification information is associated and stored in the service management table. In FIG. 11, as an example, the fact that the image 123-4 whose processed image identification information is image1′.jpg is used by the photomap server 2 b is input. Therefore, as shown in FIG. 8B, the map management table includes a map ID “M001” uniquely issued to the authenticated user ID and the processed image identification information image1′.jpg of the image 123-4. Are stored in association with each other. Then, the overall management unit 101 transmits the registration information stored in the service management table, the image file corresponding to the registration information, and the incidental information input in the text box 135 to the service server 2 specified by the registration information. On the other hand, when the button 133 is pressed in S18, the overall management unit 101 specifies the original image identification information corresponding to the processed image identification information from the service management table, and updates the specified original image identification information to the processed image identification information. To do. Then, the overall management unit 101 transmits the updated registration information and the processed image identified by the registration information to the service server 2 specified by the registration information. In S20, when the processing unit 21 of the service server 2 receives the registration information, the image, and the incidental information, the processing unit 21 associates them and stores them in the service DB 22 as browsing information. As an example, when registration information as shown in FIG. 8B is transmitted to the photo map server 2b, browsing information as shown in FIG. 3 is stored.

  In S21, the overall management unit 101 determines whether the print button 160 has been pressed on the registration screen of FIG. When the print button 160 is pressed, the process proceeds to S22. In S22, the overall management unit 101 displays a list of images identified by the original image identification information and the processed image identification information corresponding to the user ID authenticated in S11, and prints a desired image from the list in a desired form. Display the print order screen. FIG. 12 is a display example of a print order screen. 12, images 123-1, 123-2, 123-3 identified by the original image identification information image1.jpg, image2.jpg, image3.jpg corresponding to the user ID “U001” in the image management table of FIG. In addition, a list of images 123-4 identified by the processed image identification information image1′.jpg is displayed. Similar to the registration screen of FIG. 10, each image has four check boxes 124-1 a to d for designating four printing forms “L size”, “Seal”, “Mug”, “T-shirt”,. Text boxes 125-1a-d,..., 124-5a-d for inputting the number of copies 124-4a-d and the number of prints of each printing form are displayed. From the terminal 4a, a check box 124 corresponding to an image to be printed can be designated, and the number of sheets to be printed can be input in the text box 125. Hereinafter, information designated and input on the print order screen is referred to as order information.

  In S <b> 23, when the order button 170 is pressed on the print order screen, the overall management unit 101 transmits the user ID, the order information, and the designated image to the photo print server 3. The processing unit 31 of the photo print server 3 stores in the print DB 32 (see FIG. 6) print information assigned with a unique print ID by associating the received user ID, order information, and image identification information. In S24, the processing unit 31 causes the printer (not shown) to print an image based on the print information stored in the print DB 32.

  Through the above processing, if the user of the terminal 4a accesses the central management server 1 and designates on the registration screen which service server 2 is to browse the image uploaded to the existing service server 2, the central management server 1 The uploaded image is transmitted to the designated service server 2. Therefore, even when the user of the terminal 4a browses an image uploaded to a certain service server on another service server 2, it is not necessary to access each service server 2 and upload the image a plurality of times.

  It is also possible to perform various image processing on the uploaded image and browse it on the service server 2. Furthermore, it is possible to place an order for printing an uploaded image or an image subjected to image processing by a predetermined method.

<Other embodiments>
(1) In the first embodiment, the image uploaded to the service server 2 is transmitted to each service server 2 according to the registration information, but the image identification information and the image data are stored instead of the image data itself. You may make it transmit the link information which designates a resource. In this case, the service DB 22 of each service server may store link information as part of the image identification information. And each service server 2 may acquire and browse the image to browse from the resource designated by link information. Similarly, the photo print server 3 may acquire and print the image to be printed from the resource specified by the link information.

  (2) The overall management server 1 may be integrated with any service server 2. For example, the overall management server 1 may be integrated with the photo collection server 2a. In this case, the overall management server 1 may transmit the image used by the service server 2 other than the photo collection server 2a or image identification information (including link information) in the above-described processing step S13 or S19.

1 is a schematic configuration diagram of an image service system according to a preferred embodiment of the present invention. Explanatory diagram of information stored in the service DB of the photo collection server Explanatory drawing of the information memorize | stored in service DB of a photo map server Explanatory drawing of the information memorize | stored in service DB of a photo diary server Explanatory drawing of information stored in service DB of photo contest server Explanatory diagram of information stored in the print DB of the photo print server Explanatory diagram of information stored in the image management table Explanatory diagram of information stored in the service management table Flow chart showing the flow of processing executed in this system Figure showing an example of the registration screen Figure showing an example of image processing screen Figure showing an example of the print order screen

Explanation of symbols

1: central management server, 2: service server, 3: photo print server, 4: terminal

Claims (3)

A plurality of service servers that allow images uploaded from user terminals to be viewed on different service browsing screens, and images uploaded to any one of the plurality of service servers as a service browsing on other service servers An image service system comprising a management server for browsing on a screen,
Each service server
Manages images uploaded from user terminals, image link information for accessing images managed by other service servers, and registered information of the uploaded images and images corresponding to the image link information A first database to
Registration means for registering the uploaded image and registration information of the image in the first database, and registering the registration information and image link information of the image transmitted from the management server in the first database;
First uploaded means for sending the uploaded image registration information, image link information and reduced image to the management server;
The management server
A second database that manages, for each user, the registration information, image link information, and reduced image transmitted from each service server;
Means for causing the user terminal to display a list of registered information and reduced images corresponding to the user's image among the registered information and reduced images managed in the second database in response to a request from the user terminal; ,
Registration information receiving means for receiving registration information of a service server different from registration information of a service server registered in the second database for an image selected from the reduced images displayed in the list;
An image service comprising: second registration means for adding registration information for the service server accepted by the registration information acceptance means and image link information of the selected image to the second database and transmitting the information to the corresponding service server system. The service server further includes image processing means for performing predetermined image processing on the uploaded image,
The registration information accepting unit accepts input of registration information for designating which service server to use the image processed image;
The image service system according to claim 1, wherein the second transmission unit further transmits image link information of the image processed image to a service server specified by the registration information. The management server
A print order receiving means for receiving a print order which is an order for printing the image in a predetermined format and number;
Printing means for printing the image based on the print order;
The image service system according to claim 1, further comprising:

Images