Image data management method and system using network

[0001] 1. Field of the Invention

[0002] The invention relates to a method and a system for managing image data, and more particularly, to a method and a system for managing image data uploaded via a network.

[0003] 2. Description of the Related Art

[0004] Recently, a digital camera is equipped in a portable communication terminal (hereinafter, referred to as a client terminal), such as a PDA (Personal Digital Assistant), a cellular phone, etc., and provides original image data of an object captured thereby to the client terminal. Then, the client terminal compresses the original image data to form a compressed image file having a data compression format, and stores it. Also, the client terminal can transfer the compressed original image data file to a receiver via a network. The receiver is another client terminal or communication terminal being able to download compressed image files via the network, such as a personal computer, a PDA, etc. But, since the storage capacity of a client terminal is typically very low, an additional system is required for managing the compressed image files (i.e., the compressed original image data).

[0005] To meet this requirement, the conventional image data management systems generally transfer a compressed image file, uploaded from a client terminal, to a database. And, the conventional systems transfer the compressed image file stored in the database to a receiver, responsive to an image transfer command externally inputted. Also, the conventional systems decode the compressed image file, and then display the original image of the object.

[0006] However, when the file size of a compression image file is large, there is a disadvantage in the conventional systems that a retrieval time is increased for reading out the compression image file, so that a time interval is increased in display of the original image. Therefore, a need exists for an image data management system and method in which search and retrieval of image files in a database are performed more efficiently to reduce the time period for processing the image data.

[0007] To overcome the above and other disadvantages, the invention provides an image data management method using a network and being able to reduce a retrieval time period.

[0008] The invention also provides an image data management system for performing the method via the network.

[0009] In one aspect of the invention, there is provided an image data management method comprising the steps of: (a) storing an original image data file, uploaded from a client terminal via a network, in a database; (b) generating a preview image data file by using the original image data file; (c) storing the preview image data file in the database; and (d) linking the preview image data file with the original image data file. Wherein, the preview image data file has a predetermined file size much smaller than that of the original image data file, and includes a preview image substantially same as an original image included in the original image data file. Wherein the original image data file is a compressed image file having a predetermined compression format, and the step (b) includes the steps of: (b1) reading out the compressed image file from the database; and (b2) decoding the compressed image file to generate the preview image data file.

[0010] In another aspect of the invention, there is provided an image data management system comprising a storage device, an image management device, a retrieval device and an image process device. The storage device stores information of a client, at least one original image data file and at least one preview image data file linked with the original image data file. Wherein, the file size of the preview image data file is smaller than that of the original image data file. The image management device generates the preview image data file by using the original image data file, and links the preview image data file with the original image data file. The retrieval device reads out the original image data file from the storage device, on the basis of search data externally provided. The image process device processes the original image data file, which is read out by the retrieval device. In this case, the image process device provides an image selection page to the client terminal so that the client selects at least one preview image data file, and then generates the search data for the preview image data file selected by the client.

[0023] FIG. 1 is a block diagram showing an image data management system according to one exemplary embodiment of the invention. Referring to FIG. 1, the image data management system includes a main server 20 and a database 30. The main server 20 communicates with multiple client terminals 10 via a network 1.

[0024] In this embodiment, the network 1 is a communication network, such as a cable communication network or a wireless communication network, for transferring one or more compressed image data files, album files, signals, personal information of one or more clients, etc.

[0025] A client terminal 10 has a web browser for accessing the main server 20, and generates compressed image data files each obtained from original image data provided by a digital camera. Also, the client terminal 10 transfers the compressed image data files and signals to the main server 20, and downloads the compressed image data files and the album files from the main server 20. The signals include an image upload signal (IMG_UP), a “Shared” selection signal (SHARE) or a “Not Shared” selection signal (NOT_SHARE), an album manufacture request signal (ALBUM_REQ), a preview selection signal (PRE_SEL), a background image selection signal (BIMG_SEL), and a transfer request signal (TR_REQ) for the compressed image data files and/or the album files. The client terminal 10 may be made by changing or modifying a general potable communication terminal. Therefore, detailed description for the client terminal 10 is omitted in this specification.

[0026] The main server 20 transfers the personal information and the compressed image data files to the database 30. The personal information and the compressed image data files are uploaded from the client terminal 10. Also, the main server 20 supplies an album manufacture service, a file transfer service, an image sharing service, etc. to the clients via the network 1. The personal information is information about a client registered as a member. Also, the main server 20 reads out a compressed image data file stored in the database 30, and decodes the same. Thereafter, the main server 20 generates a preview image file to be transferred to the database 30. Then, the main server 20 links the preview image file with the compressed image data file. The preview image file includes a preview image substantially same as an original image included in the compressed image data file. But, the image size of a preview image is smaller than that of an original image. For example, when the image size of an original image is 100 mm (millimeter)×152 mm, the image size of a preview image can be 25 mm (millimeter)×35 mm. Therefore, the overall file size of a preview image file is much smaller than that of a compressed image data file.

[0027] The main server 20 includes multiple sub-servers each for performing a programmed function. In this embodiment, the main server 20 includes a communication server 20a, a web server 20b, an authentication server 20c, an image management server 20d, a retrieval server 20e, an album manufacture server 20f and a mail server 20g. Each of the servers 20a through 20g has at least one program for performing its own function.

[0028] The communication server 20a has a communication program to access the network 1 and interfaces communication between one or more of the client terminals 10 and one or more of the sub-servers, for example the mail server 20g, in the main server 20.

[0029] The web server 20b selectively connects a client terminal 10 to the authentication server 20c, the image management server 20d, the retrieval server 20e, the album manufacture server 20f or the mail server 20g. In other words, when a client terminal 10 accesses the web server 20b, the web server 20b connects the client terminal 10 to the authentication server 20c. Also, when the authentication server 20c authenticates the client as the member registered in the database 30, the web server 20b provides a primary page to the client terminal 10. The primary page is formed for the client to select one of the services, such as the album manufacture service, the file transfer service and the image sharing service. Thereafter, the web server 20b connects the client terminal 10 to one of the image management server 20d, the retrieval server 20e, the album manufacture server 20f and the mail server 20g, according to the client's selection.

[0030] The authentication server 20c authenticates the client according to a predetermined authentication process. That is, the authentication server 20c requests a log-in of the client, in order to receive a membership I.D. and a password of the client. And, the authentication server 20c searches the database 30 to confirm whether the client is the member registered in the database 30 or not. As a result of the confirmation, when the client is not a member, the authentication server 20c guides the client in accordance with a predetermined member registration process. And, for registering the client as a member, the authentication server 20c transfers the client information to the database 30. The client information is uploaded during the member registration process. The client information includes the personal information (e.g., name, e-mail address, telephone number, etc.), the membership I.D., and the password. Then, the authentication server 20c requests the log-in of the client again. On the other hand, as a result of the confirmation, when the client is the member, the authentication server 20c generates a predetermined authentication message.

[0031] The image management server 20d transfers a compressed image data file to the database 30. The compressed image data file is uploaded from the client terminal 10. And, the image management server 20d reads out the compressed image data file stored in the database 30, and then decodes the compressed image data file to generate a preview image file corresponding to the compressed image data file decoded. Thereafter, the image management server 20d transfers the preview image file to the database 30, and simultaneously links the preview image file with the compressed image data file. Further, the image management server 20d provides a “Shared” or “Not Shared” selection page to the client terminal 10, so that the client determines whether to share or not to share the image files (i.e., compressed image data file and preview image file). When the client selects the “Shared” option, the image management server 20d records the “Shared” option of the image files in the database 30. That is, the image management server 20d records the image files as shared image files in the database 30. Also, when the client selects the “Not Shared” option, the image management server 20d records the “Not Shared” option of the image files in the database 30. That is, the image management server 20d records the image files as non-shared image files in the database 30.

[0032] The retrieval server 20e retrieves a compressed image data file linked with a preview image file from the database 30, on the basis of search data provided from the album manufacture server 20f or the mail server 20g. Then, the retrieval server 20e reads out the retrieved compressed image data file, and provides the same to the album manufacture server 20f or the mail server 20g.

[0033] The album manufacture server 20f provides an image selection page to the client terminal 10. An image selection page is formed for a client to select at least one preview image file, which is linked with a compressed image data file uploaded from a client and/or a shared compressed image data file of other client. Then, the album manufacture server 20f generates search data for the preview image file selected by the client, and provides the search data to the retrieval server 20e. Thereafter, for manufacturing an album file, the album manufacture server 20f decodes the compressed image data file provided from the retrieval server 20e, and inserts the original image of the decoded image data file into the album file. It should be noted that since the image search and retrieval in and from the database 30 is performed using preview image files, the time period for the image search and retrieval in the present invention is reduced in comparison with that of the conventional image search and retrieve systems. Also, the album manufacture server 20f reads out background images from the database 30, and provides them to the client terminal 10 so that the client selects at least one background image. Then, the album manufacture server 20f inserts the background image, which is selected by the client, into the album file.

[0034] The mail server 20g provides the image selection page to the client terminal 10 connected thereto, and then provides the search data to the retrieval server 20e, in similar manner to what the album manufacture server 20f does for the image search and retrieval. Also, the mail server 20g provides a receiver's address input page (ADDR_IN_PG) to the client terminal 10, onto which the client enters address information (e.g., a telephone number, an e-mail address, etc.) of at least one receiver. And, the mail server 20g downloads the compressed image data file, which is provided from the retrieval server 20e, to the receiver.

[0035] The database 30 includes a client DB 30a for storing personal information of each client, an image DB 30b for storing the image files and schematic information for each image provider (i.e., a client registered as a member), and a background image DB 30c for storing the background images to be inserted in the album file.

[0036] FIGS. 2A to 2C respectively illustrate data stored in the client DB 30a, the image DB 30b and the background image DB 30c of the main server 20 shown in FIG. 1.

[0037] Referring to FIG. 2A, the client DB 30a stores personal information of each client, such as membership I.D., password, name, e-mail address, telephone number, etc.

[0038] Referring to FIG. 2B, the image DB 30b stores the membership I.D. of an image provider, the password of an image provider, the compressed image data files uploaded from an image provider, the preview image files respectively linked with the compressed image data files, and the album files. Also, in the image DB 30b, either the “Shared” or the “Not Shared” option for the image files is recorded.

[0039] Referring to FIG. 2C, the background image DB 30c stores character images and nature images to be inserted in the album file. The character images include multiple classified character images, such as first through N-th character image. The nature images include mountain image, coast image, river image, etc.

[0040] FIGS. 3A and 3B are flowcharts for explaining an image data upload process of an image data management method of the present invention. Referring to FIGS. 1, 3A and 3B, when the client terminal 10 accesses the web server 20b, the web server 20b connects the client terminal 10 to the authentication server 20c. Then, the authentication server 20c provides a log-in page to the client terminal 10 so that the client performs the log-in, at step S310. Thereafter, the authentication server 20c searches the client DB 30a to confirm whether the client is a registered member or not, at step S320. And, when the client is not a registered member, the authentication server 20c guides the member registration process in order to register the client as a member, at step S325. On the other hand, when the client is a registered member, the authentication server 20c generates an authentication message.

[0041] When the authentication message is generated, the web server 20b provides a primary page (PRI_PG) to the client terminal 10, at step S330. Referring to FIG. 4, the primary page (PRI_PG) has an “Image Upload” button 401, an “Album manufacture” button 403 and a “File Transfer” button 405.

[0042] When the client clicks the “Image Upload” button 401, the web server 20b receives an image upload signal (IMG_UP), and connects the client terminal 10 to the image management server 20d for starting the image upload. Then, the image management server 20d uploads a compressed image data (COMP_IMG) file from the client terminal 10, at step S340, and transfers the compressed image data (COMP_IMG) file to the image DB 30b in order to store the same in the image DB 30b, at step S350. Also, the image management server 20d reads out and decodes the compressed image data (COMP_IMG) file stored in the image DB 30b, at steps S355 and S360, and then generates a preview image (PRE_IMG) file corresponding to the compressed image data (COMP_IMG) file, at step S370. The image management server 20d transfers the preview image (PRE_IMG) file to the image DB 30b in order to store the same, at step S372. Continuously, the image management server 20d links the preview image (PRE_IMG) file with the compressed image data (COMP_IMG) file, at step S374.

[0043] Thereafter, the image management server 20d provides a share selection page to the client terminal 10, so that the client determines whether the image files (i.e., the preview image file and the compressed image data file) are shared or not shared, at step S380. Referring to FIG. 5, the share selection page has the preview image file, a “Shared” button 501 and a “Not Shared” button 503.

[0044] When the client clicks the “Shared” button 501, the image management server 20d receives a “Shared” selection signal (SHARE), and records the compressed image data file and the preview image file in the image DB 30b as “Shared” files, at step S390. As above-mentioned, when the client wants to show the image files to other clients, the client can easily share them with the other clients.

[0045] On the other hand, when the client clicks the “Not Shared” button 503, the management server 20d receives a “Not Shared” selection signal (NOT_SHARE), and records the compressed image data file and the preview image file in the image DB 30b as “Not Shared” files, at step S385.

[0046] FIG. 6 is a flowchart for explaining an album manufacture process of the image data management method of the present invention. Referring to FIGS. 1 and 6, when the client terminal 10 accesses the web server 20b, the authentication server 20c performs steps S610, S620 and S625 for authenticating the client. The steps S610, S620 and S625 are substantially same as the steps S310, S320 and S325 in FIG. 3A. Accordingly, detailed description for the steps S610, S620 and S625 is omitted. After the authentication steps S610, S620 and S625, the web server 20b provides the primary page (PRI_PG) to the client terminal 10, at step S630, when the authentication message is generated.

[0047] Then, when the client clicks the “Album Manufacture” button 403 (referring to FIG. 4), the web server 20b receives an album manufacture request signal (ALBUM_REQ), at step S640, and connects the client terminal 10 to the album manufacture server 20f.

[0048] In this case, the album manufacture server 20f provides the image selection page to the client terminal 10 so that the client selects at least one preview image (PRE_IMG) file, at step S650. Referring to FIG. 7, the image selection page displays preview image files being able to be selected, a “Next” button 701 and a “Previous” button 703.

[0049] And, when the client selects at least one preview image (PRE_IMG) file, the album manufacture server 20f receives a preview selection signal (PRE_SEL), at step S660, and provides search data for the selected preview image (PRE_IMG) file to the retrieval server 20e. Then, the retrieval server 20e retrieves the compressed image data (COMP_IMG) file linked with the preview image (PRE_IMG) file from the image DB 30b, in accordance with the search data, at step S665. And, the retrieval server 20e reads out the retrieved compressed image data (COMP_IMG) file, and provides the same to the album manufacture server 20f.

[0050] Continuously, the album manufacture server 20f provides a background image selection page (BIMG_SEL_PG) to the client terminal 10, and then receives a background image selection signal (BIMG_SEL) from the client terminal 10, at steps S670 and S680. Then, the album manufacture server 20f decodes the compressed image data (COMP_IMG) file linked with the selected preview image (PRE_IMG) file, at step S690. The background image selection page (BIMG_SEL_PG) has the contents similar to those of the image selection page (IMG_SEL_PG).

[0051] Thereafter, the album manufacture server 20f manufactures an album file, at step S695. The original image and the background image, which are selected by the client, are inserted in the album file by the album manufacture server 20f. The album file is stored in the image DB 30b, and can be transferred to one or more other receivers. The image transfer to other receivers is described in detail below. According to the image data management method and system of the present invention, a client can easily manufacture the album file by using the preview image (PRE_IMG) files, of which the file size is relatively small.

[0052] FIG. 8 is a flowchart for explaining an image data transfer process of the image data management method of the present invention. Referring to FIGS. 1 and 8, when the client terminal 10 accesses the web server 20b, the web server 20b connects the client terminal 10 to the authentication server 20c. In this case, for authenticating the client, the authentication server 20c performs steps S810, S820 and S825 substantially same as the steps S310, S320 and S325 in FIG. 3A, and then generates the authentication message. When the authentication message is generated, the web server 20b provides the primary page (PRI_PG) to the client terminal 10, at step S830.

[0053] And, when the client clicks the “File Transfer” button 405 (referring to FIG. 4), the web server 20b receives a transfer request signal (TR_REQ), at step S840, and connects the client terminal 10 to the mail server 20g.

[0054] Then, the mail server 20g provides the receiver's address input page (ADDR_IN_PG) to the client terminal 10, at step S845, and uploads the receiver's address from the client terminal 10, at step S850. Thereafter, the mail server 20g provides the image selection page (IMG_SEL_PG) to the client terminal 10, at step S860, and receives the preview selection signal (PRE_SEL) from the client terminal 10, at step S870.

[0055] In this case, the mail server 20g provides the retrieval server 20e with search data for the preview image (PRE_IMG) file selected by the client. Then, the retrieval server 20e retrieves the compressed image data (COMP_IMG) file linked with the preview image (PRE_IMG) file in the image DB 30b, in accordance with the search data, at step S875. And, the retrieval server 20e provides the retrieved compressed image data (COMP_IMG) file to the album manufacture server 20f.

[0056] Then, the mail server 20g transfers the compressed image data (COMP_IMG) file to the receiver, at step 880. In this case, since the client searches the image DB 30b with the preview image (PRE_IMG) file of which the size is smaller than that of the compressed image data (COMP_IMG) file, the image search can be rapidly performed.

[0057] FIG. 9 is a block diagram for explaining the image data upload process shown in FIGS. 3A and 3B. Referring to FIGS. 1, 4 and 9, when the client registered as a member clicks the “Image Upload” button 401 on the primary page (PRI_PG), the main server 20 receives the image upload signal (IMG_UP). Then, the main server 20 uploads the compressed image data (COMP_IMG) file from the client terminal 10, and transfers the same to the database 30.

[0058] Then, the main server 20 stores the uploaded compressed image data (COMP_IMG) in the database 30. Thereafter, the main server 20 reads out the compressed image data (COMP_IMG) from the database 30 and decodes the compressed image data (COMP_IMG) file to generate the preview image (PRE_IMG) file. The preview image (PRE_IMG) file includes the preview image of which size is smaller than that of the original image. Thereafter, the main server 20 transfers the preview image (PRE_IMG) file to the database 30. And, the main server 20 links the preview image (PRE_IMG) file with the compressed image data (COMP_IMG) file.

[0059] Further, the main server 20 provides the share selection page (SHARE_SEL_PG) to the client terminal 10, and receives either the “Shared” selection signal (SHARE) or the “Not Shared” selection signal (NOT_SHARE). Thereafter, the main server 20 records the “Shared” or the “Not Shared” for the preview image (PRE_IMG) file and the compressed image data (COMP_IMG) file in the database 30.

[0060] FIG. 10 is a block diagram for explaining the album manufacture process shown in FIG. 6. Referring to FIGS. 1, 6 and 10, when the client registered as a member clicks the “Album Manufacture” button 403 on the primary page (PRI_PG) (referring to FIG. 4), the main server 20 receives the album manufacture request signal (ALBUM_REQ). Then, the main server 20 provides the image selection page (IMG_SEL_PG) to the client terminal 10, and receives the preview selection signal (PRE_SEL) from the client terminal 10. In this case, the client can also select shared preview image (PRE_IMG) files provided by other clients.

[0061] Thereafter, the main server 20 provides the background image selection page (BIMG_SEL_PG) to the client terminal 10. Then, the main server 20 retrieves the compressed image data (COMP_IMG) file from the database 30, in order to read out the compressed image data (COMP_IMG) file linked with the preview image (PRE_IMG) file selected by the client. Also, the main server 20 receives the background image selection signal (BIMG_SEL) from the client terminal 10. In this case, the main server 20 searches the background image selected by the client in the database 30. Thereafter, the main server 20, which inserts the original image and the background image, manufactures the album (ALBUM) file. Also, the main server 20 transfers the album (ALBUM) file to the database 30.

[0062] FIG. 11 is a block diagram for explaining the image data transfer process shown in FIG. 8. Referring to FIGS. 1, 8 and 11, when the client registered as a member clicks the “File Transfer” button 405 on the primary page (PRI_PG) (referring to FIG. 4), the main server 20 receives the transfer request signal (TR_REQ). In this case, the main server 20 provides the receiver's address input page (ADDR_IN_PG) to the client terminal 10, and uploads the receiver's address.

[0063] Then, the main server 20 provides the image selection page (IMG_SEL_PG) to the client terminal 10, and receives the preview selection signal (PRE_SEL) from the client terminal. In this case, the main server 20 retrieves the database 30 on the basis of the search data for the preview image (PRE_IMG) file selected by the client. The main server 20 reads out the compressed image data (COMP_IMG) file linked with the selected preview image (PRE_IMG) file from the database 30. Thereafter, the main server 20 transfers the compressed image data (COMP_IMG) file to the receiver 10-1.

[0064] The above described embodiments may be implemented with a computer-readable medium (or, article of manufacture) comprising program instructions for managing original image data uploaded from a terminal of a client via a network by performing: storing an original image data file, uploaded from a client terminal via the network, in a database; generating a preview image data file by using the original image data file; storing the preview image data file in the database; and linking the preview image data file with the original image data file. Wherein, the preview image data file has a predetermined file size smaller than that of the original image data file, and includes a preview image substantially same as an original image included in the original image data file. The term “computer-readable medium” as used herein is intended to encompass one or more computer programs and data files accessible from one or more computer-readable devices, carriers, or media, such as magnetic storage media, floppy disk, CD-ROM, DVD-ROM, etc.

[0065] As above-mentioned, in the present invention, time period for the image search and retrieval is remarkably reduced regardless of the file size of a compressed image data file, since the image search and retrieval is performed by using a preview image file having a file size smaller than that of a compressed image data file. Therefore, according to the image data management method and system of the present invention, the retrieval of the original image files requires less time than the conventional image retrieval systems do.

[0066] Further, the image data management system of the present invention provides various services, such as the album manufacture service, the file transfer service, the image sharing service, etc.

[0067] While this invention has been particularly shown and described with reference to the embodiments thereof, it will be understood by those skilled in the art that various changes and equivalents may be made without departing from the spirit and scope of the invention.

[0068] For example, in the embodiment, the client terminal 10 compresses the image data of objects to generate the compressed image data files, and then uploads the compressed image data files to the main server 20. But, in another embodiment, the main server 20 can receive the image data from the client terminal 10, and compress the same to generate the compressed image data files.

[0069] Also, in the embodiment, the authentication process is performed for each of the image data upload process, the album manufacture process and the file transfer process. But, in another embodiment, the image data upload process, the album manufacture process and the file transfer process may be selectively performed after one authentication process.

[0070] Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments within the scope of the appended claims.