Distribution server

Abstract

To provide a distribution server for storing and distributing label data, and to offer technology that reduces the effort required of users to create label data that includes images. [Solution] The distribution server 1 connects to the network 6 and receives an image file GF uploaded from the distribution source PC 2 connected to the network 6. The distribution server 1 identifies one label printer 5A from the label printers 5A and 5B connected to the network 6. The distribution server 1 obtains printer information 52A from the identified label printer 5A. Based on the obtained printer information 52A, the distribution server 1 creates and saves label data including a processed image obtained by processing the image shown in the image file GF uploaded from the distribution source PC 2.

Description

TECHNICAL FIELD

[0001] The technical field disclosed in the present specification relates to a distribution server that stores and distributes label data. BACKGROUND ART

[0002] Conventionally, a technology for registering and distributing label data by a distribution server is known. For example, Patent Document 1 discloses a configuration in which a server side includes a personal computer for designing labels, a label database for storing labels, and a registration number database for assigning product numbers, a client side includes a personal computer for issuing labels, a printer, and a cutting plotter, the server and the client are connected, and the processes from label design, label issuance, to label cutting are consistently performed. PRIOR ART DOCUMENTS PATENT DOCUMENTS

[0003] Patent Document 1 Japanese Unexamined Patent Publication No. 2001-325084 SUMMARY OF THE INVENTION PROBLEM TO BE SOLVED BY THE INVENTION

[0004] When creating label data including an image, a complicated operation is required, such as activating an editing program capable of editing labels and pasting an image file storing image information to a size suitable for a sheet to be printed. Patent Document 1 does not disclose a configuration for creating label data including an image, and there is room for improvement. MEANS FOR SOLVING THE PROBLEM

[0005] The distribution server, which was created for the purpose of solving the above-mentioned problems, is a distribution server connected to a network, and is configured to accept the upload of an image file that stores image information from a distribution source device connected to the network, identify one of the printers connected to the network, acquire printer information including at least sheet information for the identified printer, and create and save label data including a processed image obtained by processing the image shown in the image file uploaded from the distribution source device based on the printer information acquired from the printer.

[0006] The distribution server with the above configuration acquires image files from the distribution source device, further acquires printer information for the specified printer, and automatically creates and saves label data that includes processed images based on the printer information. Therefore, anyone who wants to register label data containing images to the distribution server can easily register label data containing images suitable for the printer information to the distribution server simply by uploading the image files from the distribution source device to the distribution server.

[0007] The devices, control methods, computer programs, and computer-readable storage media for implementing the above-mentioned distribution server functions are also novel and useful. [Effects of the Invention]

[0008] The technology disclosed herein provides a distribution server for storing and distributing label data, which reduces the effort required of users to create label data that includes images. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the schematic configuration of the distribution system. [Figure 2] This diagram illustrates an example of database record structure. [Figure 3]This is a sequence diagram illustrating an example of the printer registration process. [Figure 4] This is a sequence diagram illustrating the image processing procedure. [Figure 5] This is a diagram illustrating an example of an image display screen. [Figure 6] This is a diagram illustrating an example of a preview screen. [Figure 7] This is a sequence diagram illustrating an example of the distribution process. [Modes for carrying out the invention]

[0010] The distribution server that distributes label data will be described in detail with reference to the attached diagram. This configuration discloses a distribution system in which the distribution server, the distribution source device, and the distribution destination device are connected via a network, and label data uploaded from the distribution source device to the distribution server is distributed to the distribution destination device.

[0011] <Outline of the distribution system configuration> The distribution system (hereinafter referred to as "the system") 100 shown in Figure 1 has a distribution server 1 connected to a network 6 such as the Internet. Personal computers (hereinafter referred to as "PCs") 2, 3A, 3B and label printers 5A, 5B are connected to the distribution server 1 via the network 6 so that they can communicate with each other. The distribution server 1 is a server managed by the label printer vendor, etc. In this configuration, the distribution server 1 has, for example, a function to store label data that represents labels and a function to distribute the stored label data. Note that in Figure 1, the number of destination PCs and printers connected to the network 6 may be three or more. Unless otherwise specified in the following explanation, destination PCs 3A, 3B and label printers 5A, 5B will be collectively referred to as destination PC 3 and label printer 5.

[0012] The PC3 and label printer 5 are installed in stores such as supermarkets. The label printer 5 is a device that has at least a communication function and a printing function. Each of the label printers 5 is equipped with a main control panel 51. The main control panel 51 is equipped with an operation section that accepts various operations such as print settings and main print commands to execute printing. The main control panel 51 may also be equipped with a display section that displays data.

[0013] The label printer 5, for example, can accommodate a roll of sheets and has the function of printing images on those sheets to create labels. The roll of sheets is a printing medium in which sheets are attached to a continuous strip of release paper and wound up. The sheets may be a continuous long tape or die-cut labels that have been pre-cut into a predetermined shape. The label printer 5 is equipped with a cassette for detachably storing the roll of sheets.

[0014] The label printer 5 can accommodate multiple types of cassettes. These cassettes include various types such as those containing continuous long tapes, those containing die-cut labels for price tags, and those containing die-cut labels for addresses. The sheets contained in the cassettes differ in text color, background color, sheet size, and material depending on the cassette model. Sheet size includes both the sheet width (the size perpendicular to the sheet's transport direction) and the sheet length (the size in the sheet's transport direction). Materials include, for example, paper, resin sheets, and cloth. Furthermore, this form of label printer 5 may have a function to cut and eject the printed portion after printing.

[0015] The label printer 5 has printer information 52 that includes at least sheet information, and can output the printer information 52 in response to requests from the distribution server 1, PC 3, etc. The printer information 52 may or may not include model information.

[0016] The model information is information indicating the model of the label printer 5. The model information is, for example, model information including information capable of uniquely identifying at least the printer model. The information capable of uniquely identifying a printer model is, for example: first information that is information capable of identifying the printer model or model type such as a model name or model identification information; second information that is information capable of identifying an individual printer such as a serial number; third information that indicates the model number of the thermal head; and fourth information that indicates control parameters of the thermal head such as resolution, the number of dots in the width direction parallel to the sheet width, printable width, and density correction parameters. The model information includes at least one of the first information, the second information, the third information, and the fourth information.

[0017] The sheet information includes, for example, a sheet size. The sheet size includes, for example, a sheet width that is a dimension in a direction perpendicular to the sheet conveyance direction, and a sheet length that is a dimension in the sheet conveyance direction. The label printer 5 may automatically detect the sheet information of the sheet stored in the currently mounted cassette and include it in the printer information 52, or may include the sheet information set via the main body operation panel 51 in the printer information 52.

[0018] The label printer 5 can perform printing on sheets of various sheet sizes. The sheet size of a sheet stored in a cassette mounted in the label printer 5A and the sheet size of a sheet stored in a cassette mounted in the label printer 5B may be different from each other.

[0019] For the label printer 5, the printable sheet size differs depending on the model. When the model of the label printer 5A is different from that of the label printer 5B, the printable sheet size for the label printer 5A and the printable sheet size for the label printer 5B may be different.

[0020] PC3 is communicatively connected to the label printer 5. The communication method may be wireless or wired. A print application program (hereinafter referred to as "print application") 32 that controls printing by the label printer 5 is installed in PC3.

[0021] The print application 32 is a program provided by a vendor or the like of the label printer 5, and can use the service provided by the distribution server 1. PC3 can download label data from the distribution server 1 via the print application 32. Furthermore, PC3 can display, via the print application 32, a setting screen for accepting print settings based on the capabilities of the label printer 5, and accept the print settings. For example, the print application 32 can output, to the label printer 5, a print command for printing the label data downloaded from the distribution server 1 using the print settings accepted via the setting screen. Hereinafter, PC3 is referred to as "distribution destination PC3".

[0022] The label printer 5 may be connected to the distribution server 1 via the distribution destination PC3, or may be directly connected to the distribution server 1.

[0023] PC2 is provided, for example, in a management company that manages the store. A label editing application program (hereinafter referred to as "label editing application") 22 for editing labels is installed in PC2. After being started, the label editing application 22 causes PC2 to display a label editing screen on which objects can be arranged, and can create label data including the objects arranged on the label editing screen. The objects are, for example, text, images, frames, barcodes, and QR code (registered trademark). The label editing application 22 can save the edited label data in PC2.

[0024] For example, the label editing application 22 can create label data that includes the image shown in the image file GF saved on PC2. Specifically, the label editing application 22 places an image object on the label editing screen displayed on PC2. The label editing application 22 accepts the sheet size setting and displays the printable area of ​​the label on the label editing screen according to the set sheet size. By placing the image object within the printable area of ​​the label, the image contained in the image object is printed.

[0025] The label editing application 22 allows the user to select one image file GF from the image files stored on PC2 to include in the image object. The label editing screen places the image shown in the selected image file GF at a predetermined position and size. If the image extends beyond the object area of ​​the image object, the excess portion may not be printed. The label editing application 22 can accept changes to the size and layout of the image shown in image file GF so that it fits within the object area of ​​the image object.

[0026] Furthermore, the label editing application 22 allows setting the image quality as an attribute of the image object. For example, there are multiple types of algorithms for binarizing images, and the label editing application 22 provides multiple image quality modes corresponding to different algorithms, allowing the user to select one image quality mode from among the multiple image modes to set for the image object. The label editing application 22 can adjust the image quality of the image shown in the image file GF according to the selected image quality mode.

[0027] When the label editing application 22 receives a save command via the label editing screen, it saves the label data, which includes the processed image processed by image processing such as image binarization and image processing to adjust image quality, to the PC2. The label editing application 22 saves the label data in a first format. The first format is, for example, a file format that allows editing of the label data even after saving.

[0028] The label editing application 22 is a program provided by the vendor of the label printer 5, and can utilize the services provided by the distribution server 1. PC2 can upload the edited label data to the distribution server 1 using the label editing application 22. For example, the label editing application 22 can upload label data, including processed images stored on PC2, to the distribution server 1. In the following explanation, PC2 will be referred to as "distribution source PC2".

[0029] The printing application 32 and the label editing application 22 can communicate with the distribution server 1 via their own browser functions or via the browsers of the destination PC 3 or the source PC 2. The browser may be one that is pre-installed on the operating system (hereinafter referred to as "OS") of the destination PC 3 or the source PC 2, or it may be one that is installed separately from the OS.

[0030] Source PC2 is an example of a "source device". Destination PC3 and label printer 5 are examples of "destination devices". Label printer 5 is an example of a "printer". Label printer 5A is an example of a "first printer", and label printer 5B is an example of a "second printer". Printer information 52A is an example of "first printer information". Printer information 52B is an example of "second printer information". The source and destination devices may also be smartphones or tablet devices.

[0031] <Configuration of distribution server 1> Distribution server 1 is a device having at least communication and storage functions. Distribution server 1 has a front-end application 11 and a back-end application 12. The front-end application 11 and the back-end application 12 cooperate to execute processing by distribution server 1. Note that the processing by distribution server 1 may be executed by a single application. Distribution server 1 shown in Figure 1 consists of a single device, but it may also consist of a system of multiple devices.

[0032] Frontend application 11 is a web application that can be used on the browser of the information processing device connected to the distribution server 1, without being installed on the information processing device. Frontend application 11 provides, for example, a screen that accepts user input and can be displayed in a browser. Frontend application 11 contains various page information for displaying the screen on the distribution source PC 2 and the distribution destination PC 3.

[0033] The backend application 12 is a program that executes various processes in response to requests from the frontend application 11. Specifically, the backend application 12 can call various databases to store and retrieve information. Databases that the backend application 12 can access include, for example, the label database 13 (hereinafter referred to as "label DB 13") and the printer database 14 (hereinafter referred to as "printer DB 14"). In Figure 1, the label DB 13 and the printer DB 14 are located within the distribution server 1, but they may also be located outside the distribution server 1.

[0034] Label DB13 stores label data. Figure 2(A) shows the structure of records registered in Label DB13. Label DB13 stores records for each label data entry, including fields that indicate the label ID, label name, label data, sample image, and update history.

[0035] The field indicating the label ID stores information that identifies the label. The field indicating the label name stores the name of the label. The field indicating the label data stores label data that describes the structure of the label. For example, the label data includes data indicating the type, content, and layout for each object placed in the label data. For example, if the label data includes an image object, "Image" is stored in the type field, and the image file, image layout, size, and image quality mode are stored in the content field. The field indicating the sample image stores a URL indicating the location where the sample image for the label is saved. The field indicating the update history stores the update history of the label data.

[0036] As described above, creating label data including images using the label editing application 22 requires complex operations. Therefore, the distribution server 1 in this configuration has a function to accept image file uploads and automatically create label data based on the uploaded image files. The distribution server 1 also has a function to save the automatically created label data to the label DB 13. Furthermore, the distribution server 1 has a function to distribute the automatically created label data. The automatic creation, saving, and distribution of label data by the distribution server 1 will be described later.

[0037] Printer DB14 stores printer information for printers connected to network 6. Figure 2(B) shows the structure of the records registered in Printer DB14. Printer DB14 stores a record for each printer that includes fields indicating the printer ID, printer name, model information, capability information, and destination information.

[0038] The field indicating the printer ID stores information that identifies the printer, such as the serial number. The field indicating the printer name stores the name of the printer. The field indicating the model information stores at least one of the following: 1. Information that can identify the printer model or type, such as the model name or model identification information; 2. Information that can identify the individual printer, such as the serial number; 3. Information that includes the thermal head model number; and 4. Information that includes information that indicates the control parameters of the thermal head, such as the resolution, number of dots in the width direction, printable width, and density correction parameters. The field indicating the capabilities store information that indicates the capabilities of the printer. The field indicating the capabilities store the configurable settings for each print setting item. The field indicating the destination store information that indicates the destination of the printer, such as the IP address.

[0039] <Explanation of streaming operation> Next, the distribution operation of system 100 will be explained. In this embodiment, the explanation will be based on the example where distribution server 1 automatically generates and saves label data based on the image file GF uploaded from distribution source PC 2, and then distributes the saved label data to distribution destination PC 3A. The procedures and processing steps of each program described below basically represent the CPU processing according to the instructions written in each program. That is, processes such as "judgment," "decision," "acquisition," and "reception" in the following explanation represent CPU processing. CPU processing includes hardware control using the OS API. In this specification, the description of the OS will be omitted when explaining the operation of each program. Also, "acquisition" is used as a concept that does not necessarily require a request.

[0040] <Printer Registration> First, let's explain the printer registration process. As shown in Figure 3, when the source PC2 receives a command to connect to the distribution server 1 (A11), it uses the browser function of the label editing application 22 or the browser of the source PC2 to establish a communication connection with the distribution server 1 (A12). Once the distribution server 1 connects to the source PC2, the front-end application 11 provides the home screen to the source PC2 (A13).

[0041] When the front-end application 11 receives a printer registration request via a home screen (not shown) (B01), it requests the back-end application 12 to search for a printer (B02). The back-end application 12 searches for printers connected to network 6 and obtains printer information from the found printers (B03). The back-end application 12 passes the search results to the front-end application 11 (B04). The front-end application 11 provides the printer registration screen, including the search results, to the source PC 2 (B05). The front-end application 11 accepts the printer specification via the printer registration screen (B11), and upon receiving the registration instruction (B12), it requests the back-end application 12 to register the specified printer in the printer DB 14 (B13). The request is accompanied by the printer ID of the specified printer. The back-end application 12 registers the printer information, including the printer ID attached to the request, in the printer DB 14 and updates the printer DB 14 (B14).

[0042] When the backend application 12 has finished registering the label data, it notifies the frontend application 11 that the registration is complete (B15). The frontend application 11 provides the source PC2 with a screen notifying it that the registration is complete (B16).

[0043] In this configuration, the backend application 12 selected a printer from the searched printers, but the frontend application 11 may also accept input from the user and select a printer based on the entered destination information.

[0044] <Automatic creation and saving of label data> Next, we will explain the operation of the distribution server 1 to automatically create and save label data as described above. For example, as shown in Figure 4, when the distribution source PC 2 connects to the distribution server 1 and receives a request to automatically create label data on the home screen provided by the distribution server 1 (D01), it requests the backend application 12 to send a list of printers (D02). The backend application 12 obtains printer information of printers registered in the printer DB 14 from the printer DB 14 (D03). The backend application 12 creates a list of printers based on the printer information obtained from the printer DB 14 and passes it to the frontend application 11 (D04). The frontend application 11 provides the distribution source PC 2 with a printer identification screen that includes the list of printers received from the backend application 12 (D05). The list of printers includes, for example, the printer name, printer ID, model name, and destination information.

[0045] When a printer is selected via the printer identification screen, the front-end application 11 accepts the selected printer as the identified printer (D11). In this embodiment, it is assumed that the label printer 5A is identified. Once the label printer 5A is identified, the front-end application 11 provides the source PC2 with an image upload screen (D12). The source PC2 then displays the images shown in the image files stored on the source PC2 via the label editing application 22, making them selectable on the image upload screen.

[0046] The frontend application 11 accepts the selection of an image file to be uploaded when one of the images displayed on the image upload screen is selected. In this embodiment, it is assumed that the image file GF is selected. When the frontend application 11 receives the selected image file GF from the label editing application 22 (D13), it requests the backend application 12 to process the image (D14). The request includes the image file GF that the frontend application 11 received from the label editing application 22 in D13.

[0047] When the backend application 12 receives an image processing request, it generates multiple copies of the image shown in the image file GF attached to the request (D15). For each of the generated copies, the backend application 12 performs image processing using a different algorithm for binarization (D16).

[0048] Specifically, the backend application 12 generates duplicate images equal to the number of image processing steps performed in D16. For example, if there are four types of image processing steps performed in D16—tither transformation, error diffusion transformation, edge transformation, and simple binarization—the backend application 12 will create four duplicate images. For the sake of explanation, these four created duplicate images will be referred to as the first to fourth duplicate images.

[0049] The backend application 12 tizers the first duplicate image and temporarily stores the tizer-transformed image. The backend application 12 also diffuses the second duplicate image and temporarily stores the diffuse-transformed image. Furthermore, the backend application 12 edge-transforms the third duplicate image and temporarily stores the edge-transformed image. Finally, the backend application 12 simply binarizes the fourth duplicate image and temporarily stores the simply binarized image. In short, the backend application 12 generates and temporarily stores four different images with varying image quality using different image processing algorithms.

[0050] The example image processing method may include methods other than tizer transformation, error diffusion transformation, edge transformation, and simple binarization. Furthermore, the example image processing method may include at least one of the following: tizer transformation, error diffusion transformation, edge transformation, and simple binarization.

[0051] The backend application 12 performs a similarity image selection process (D19) to select the image that best matches the image shown in the uploaded image file from the images processed in D16. For example, in the similarity image selection process, SSIM is used to determine the similarity of each image processed, and the image with the highest similarity is selected as the similarity image.

[0052] The backend application 12 passes the image processing results to the frontend application 11 (D20). The image processing results include all images processed in D16. Of the images processed in D16, the image selected as the closest match in D19 is set as the recommended image.

[0053] The frontend application 11 provides the source PC2 with an image display screen containing the image processing results received from the backend application 12 in D20 (D21). Figure 5 is an example of the image display screen D6. The image display screen D6 lists the images included in the image processing results as selected images PR61, PR62, PR63, and PR64. The image display screen D6 displays radio buttons R61, R62, R63, and R64 for each of the selected images PR61, PR62, PR63, and PR64, allowing the user to select one image from the selected images PR61, PR62, PR63, and PR64 to include in the label data. The image display screen D6 displays selected image PR61, which was selected as the closest image, at the top, and is further labeled "Recommended," giving it priority over selected images PR62, PR63, and PR64, which were not selected as the closest image. Therefore, closest images are more likely to be selected than images that are not closest images. The image display screen D6 displays an apply button SW61.

[0054] For example, if radio button R61 is selected, the front-end application 11 accepts the selection of the image PR61 associated with radio button R61, as shown in Figure 4 (D31). When the front-end application 11 receives an application instruction in response to the operation of the apply button SW61 (D32), it requests the back-end application 12 to automatically create the label data (D33). An application instruction is an example of a "selection instruction". The request includes the image PR61 selected in D31 and the printer ID of the label printer 5A identified in D11.

[0055] When the backend application 12 receives an automatic creation request (D33), it accesses the label printer 5A according to the destination information of the label printer 5A attached to the request and obtains printer information 52A from the label printer 5A (D34). The printer information 52A includes model information indicating the model of the label printer 5A, and sheet information including the sheet size of the sheet currently set on the label printer 5A. In D34, the backend application 12 may also obtain model information in addition to sheet information as printer information 52A.

[0056] Based on the printer information 52A obtained in D34, the backend application 12 automatically creates label data including a processed image obtained by processing the image PR61 attached to the request (D35).

[0057] Specifically, the backend application 12 identifies the sheet size based on the printer information 52A obtained in D34. For example, if the printer information 52A obtained in D34 contains one sheet information, the backend application 12 identifies the sheet size from that sheet information.

[0058] For example, if the printer information 52A acquired by D34 includes model information, and the distribution server 1 stores sheet information for each model, the backend application 12 acquires the sheet information associated with the model information acquired by D34 from the distribution server 1 and identifies the sheet size from the acquired sheet information. By acquiring printer information that includes model information in addition to sheet information, the accuracy of sheet size identification by the distribution server 1 improves.

[0059] Furthermore, if the backend application 12 obtains multiple sheet sizes for the identified label printer 5A, it may also determine the sheet size by having the frontend application 11 provide a screen to the source PC2 for selecting one sheet size from the multiple sheet sizes, and allowing the person uploading the image file to select the sheet size.

[0060] The backend application 12 generates a processed image by enlarging or reducing the image PR61 attached to the automatic creation request in D33 to match the specified sheet size. Therefore, the image shown in the image file is automatically resized to match the sheet size set in the specified label printer 5A. The backend application 12 also includes the processed image, obtained by binarization and size adjustment of the image shown in the uploaded image file GF, in the label data and automatically generates label data containing the image.

[0061] The backend application 12 generates a preview image of the label data created in D35 (D41) and passes the generated preview image to the frontend application 11 (D42). The frontend application 11 provides the preview screen, including the preview image received from the backend application 12, to the source PC2 (D43).

[0062] Figure 6 shows an example of the preview screen D7. The preview screen D7 displays, for example, a preview image PR71 of the automatically generated label data, a printer information display area DS71 that displays printer information 52A obtained from the identified label printer 5A, a save button SW71, and a back button SW72. The preview image PR71 displays the image shown in the uploaded image file GF, which is a processed image EG71 that has been resized from the image PR61 selected in D31 of Figure 4.

[0063] As shown in Figure 4, when the front-end application 11 receives a save command in response to the operation of the save button SW71 (D51), it requests the back-end application 12 to save the created label data (D52). The back-end application 12 saves the label data created in D35 to the label DB 13 (D53).

[0064] For example, the backend application 12 creates a label ID, adds a record to the label DB 13, and stores the automatically created label data in the label data field of the added record. The label data may be saved in a first format, or it may be saved after being converted to a second format from the first format. The second format is, for example, a file format in which information unnecessary for printing is removed and the label data cannot be edited. The backend application 12 also stores the printer name, printer ID, and sample image in the printer name, printer ID, and sample image fields of the added record, based on the printer information of the identified label printer 5A. Furthermore, the backend application 12 stores the save date and time in the update history field of the added record.

[0065] Furthermore, if the back button SW72 is pressed, the front-end application 11 closes the preview screen D7 and returns to the previous screen.

[0066] <Distribution to PC3> Next, the operation of distributing label data from distribution server 1 to destination PC 3 will be explained with reference to Figure 7. Here, we will explain using the example of distributing label data to destination PC 3 in response to receiving a distribution request from destination PC 3. When destination PC 3 receives an instruction to connect to distribution server 1 (F01), it connects to distribution server 1 using the browser function of the print application 32 or its own browser (F02). The front-end application 11 of distribution server 1 provides the home screen to destination PC 3 (F03).

[0067] When the frontend application 11 receives a download request via the home screen (G01), it requests the backend application 12 to send a list of labels (G11). When the backend application 12 receives the request to send the list of labels, it reads the label data from the label database 13 (G12). The backend application 12 generates a list of labels based on the label data read from the label database 13 and passes it to the frontend application 11 (G13). When the frontend application 11 receives the list of labels, it provides the download screen containing the received list of labels to the destination PC3 (G14). For example, the list of labels displays the label names from the label data in association with the sample images.

[0068] The print application 32 accepts the selection of a label data to be downloaded when one label data is selected from the label list on the download screen (G21). When the front-end application 11 receives the download instruction (G22), it requests the back-end application 12 to distribute the label data (G23). The label data distribution request includes the label ID of the selected label data and the destination information of the destination PC 3, which is the source of the download request. When the back-end application 12 receives the distribution request, it reads the label data associated with the label ID attached to the request from the label DB 13 (G24). The back-end application 12 distributes the read label data to the destination PC 3 according to the destination information attached to the distribution request (G25). The print application 32 on the destination PC 3 saves the received label data (G27). Alternatively, the back-end application 12 may distribute the label data to the destination PC 3 via the front-end application 11.

[0069] In the above explanation, the receiving PC3 received the label data in response to user operation, but it is also possible to automatically download the specified label data at predetermined times, such as when the printing application 32 is launched, or at regular intervals, such as every few hours.

[0070] Furthermore, the distribution server 1 may directly distribute the label data to the label printer 5A identified when the image file GF was uploaded. For example, the label printer 5A may download the label data from the distribution server 1 in response to an operation on the main unit's control panel 51A, or it may download the label data from the distribution server 1 at a pre-configured timing. In this case as well, the distribution server 1 may either have the backend application 12 directly distribute the label data to the label printer 5A, or it may distribute it via the frontend application 11.

[0071] Furthermore, the distribution server 1 may push the label data to the designated destination PC 3A or label printer 5A at the timing set on the distribution server 1.

[0072] <Printing label data> For example, if the print application 32A on the receiving PC 3A receives a print command to print the label data downloaded from the distribution server 1, it generates a print command instructing the printer to print based on the downloaded data and sends it to the label printer 5A. The label printer 5A prints the label data according to the print command.

[0073] For example, the label printer 5A stores the label data distributed from the distribution server 1, and when it receives the specification of the distributed label data and a print command via the main unit's control panel 51A, it performs printing based on the label data.

[0074] As described above, the distribution server 1 of the above embodiment acquires the image file GF from the distribution source PC 2, acquires printer information 52A for the identified label printer 5A, and automatically creates and saves label data including a processed image by processing the image in the image file GF based on the printer information 52A. Therefore, anyone who wants to register label data including an image to the distribution server 1 can easily register label data including an image suitable for the printer information to the distribution server 1 simply by uploading the image file GF from the distribution source PC 2 to the distribution server 1, without having to perform complex tasks such as launching the label editing application 22 and pasting the image file GF onto the label data to a size suitable for the sheet to be printed.

[0075] Furthermore, if, for example, a label printer 5B with a different model from label printer 5A and a different sheet size for the registered sheet is identified when an image file GF is uploaded, the distribution server 1 identifies the sheet size based on the printer information 52B of label printer 5B and resizes the image shown in image file GF to match the identified sheet size. The distribution server 1 creates and saves label data including the processed image based on the printer information 52B. Therefore, even with the same image file GF, the distribution server 1 can process the image shown in image file GF by expanding or shrinking it to match the sheet size of the sheet used by the identified label printers 5A and 5B. Thus, it can create and save label data including the image shown in image file GF for label printers 5A and 5B respectively and distribute it to label printers 5A and 5B.

[0076] The processed image processed based on printer information 52A is an example of a "first processed image," and the label data containing the processed image processed based on printer information 52A is an example of "first label data." The processed image processed based on printer information 52B is an example of a "second processed image," and the label data containing the processed image processed based on printer information 52B is an example of "second label data."

[0077] The embodiments disclosed herein are merely illustrative and do not limit the present invention in any way. Therefore, the technology disclosed herein can naturally be improved and modified in various ways without departing from its essence. For example, the layout and content of each screen are not limited to the embodiments described above.

[0078] For example, in the above embodiment, at D35 in Figure 4, the image shown in the image file was enlarged or reduced to fit the sheet size to generate a processed image. However, the processed image is not limited to an image resized to fit the sheet size. For example, the processed image may be an image from which the image shown in the image file has been adjusted in quality.

[0079] For example, in the above embodiment, the printer was identified when the image file was uploaded, as shown in D11 of Figure 4. In contrast, the distribution server 1 may have the destination printers registered in advance, and in D34 of Figure 4, printer information may be obtained from the registered printers.

[0080] For example, D42-D43 in Figure 4 may be omitted. However, before saving the label data, which includes processed images that have been enlarged or censored to fit the sheet size, the distribution server 1 can display a preview image of the label data on the distribution source PC 2, allowing the uploader who uploaded the image file to choose whether or not to save the label data including the processed image, thus saving the label data intended by the uploader.

[0081] For example, D15 to D16 in Figure 4 may be omitted. However, there are multiple types of image processing for binarization, and the results differ depending on the image processing method. Therefore, the distribution server 1 duplicates the uploaded image, performs image processing using a different algorithm on each duplicated image, selects one result, and generates label data that includes the processed image obtained by processing the selected image. This increases the likelihood of saving the label data intended by the uploader who uploaded the image file.

[0082] For example, the distribution server 1 may omit the processing steps D20 to D33 in Figure 4, automatically select the closest approximate image from the processed images to the uploaded original image, and create and save label data containing the approximate image. This increases the likelihood that the distribution server 1 can easily create the label data intended by the uploader who uploaded the image file.

[0083] For example, in the above embodiment, the distribution server 1 displayed all images processed by the backend application 12 on the image display screen D6 at S21 in Figure 4. Alternatively, the distribution server 1 could display only the image PR61 that most closely resembles the uploaded original image (closest image) on the image display screen D6 and allow the uploader to choose whether or not to create label data. Then, if the distribution server 1 receives a creation instruction, it may generate and save label data that includes the processed image obtained by processing the closest image. In this way, the distribution server 1 can save the label data intended by the uploader by displaying the closest image on the distribution source PC2 before creating label data that includes the processed image obtained by processing the automatically selected closest image, and allowing the uploader who uploaded the image file to choose whether or not to create label data that includes that closest image.

[0084] However, if distribution server 1 displays not only the image R61 that most closely resembles the uploaded source image (closest image), but also selected images PR62-PR64 that were not selected as closest images, to distribution source PC 2, and accepts selection instructions to specify the selected image, then label data including selected images different from the closest images can be created, and the label data intended by the uploader who uploaded the image file can be saved.

[0085] For example, as shown in Figure 4, D02 to D11, the distribution server 1 in the above embodiment identified the label printer 5A from the printers registered in the printer DB 14. Alternatively, the printer may be identified by manually entering destination information. However, by accepting the identification of a target printer from among multiple printers and creating label data that matches the sheet size of the identified printer, the use of label data on that printer can be promoted.

[0086] In any sequence diagram disclosed in the embodiments, any multiple processes can be executed in any order or in parallel, provided that no inconsistencies arise in the processing content. For example, as shown in Figure 4, the backend application 12 selected one image from the processed images after receiving a request to identify a printer. Printer identification can be performed before obtaining printer information in D34, and the distribution server 1 may, for example, receive the request to identify a printer after the process of selecting an image from the processed images.

[0087] For example, the printer information obtained by D34 may include only model information. For instance, if the identified printer is a model that supports only one type of sheet, and the distribution server 1 stores the model information and sheet information in association, the distribution server 1 can determine the sheet size from the printer's model information alone.

[0088] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as an ASIC, or a combination thereof. Furthermore, the processes disclosed in the embodiments can be implemented in various forms, such as a recording medium or method that stores a program for executing the process. [Explanation of Symbols]

[0089] 1 Distribution Server 2. Source PC 3. Distribution destination: PC 5 Label printers 6 Network

Claims

1. A distribution server connected to a network, The aforementioned distribution server is The distribution source device connected to the aforementioned network accepts the upload of an image file that stores image information. Identify one of the printers connected to the aforementioned network, For the identified printer, obtain printer information including at least sheet information. Based on the printer information obtained from the printer, label data including a processed image obtained by processing the image shown in the image file uploaded from the distribution source device is created and saved. A distribution server configured in this way.

2. A distribution server as described in claim 1, The aforementioned distribution server is Based on the printer information obtained from the printer, the sheet size is determined, and the label data, including the processed image which is enlarged or reduced to match the determined sheet size, is created and saved. A distribution server configured in this way.

3. A distribution server as described in claim 2, The aforementioned distribution server is Before saving the created label data, the processed image included in the created label data is displayed on the distribution source device. Subsequently, upon receiving a save instruction transmitted from the distribution source device, the created label data is saved. A distribution server configured in this way.

4. A distribution server as described in claim 1, The aforementioned distribution server is Multiple images are generated by duplicating the image shown in the uploaded image file. After multiple images are generated, image processing is performed on each image using a different algorithm for binarization. Select one of the multiple images after performing the aforementioned image processing, Based on the printer information obtained from the printer, the label data including the processed image obtained by processing the selected image after performing the image processing is generated and stored. A distribution server configured in this way.

5. A distribution server as described in claim 4, The aforementioned distribution server is From the multiple images after performing the aforementioned image processing, select the closest image which is the image that most closely resembles the image shown in the uploaded image file. Based on the printer information obtained from the printer, the system generates and stores label data including the processed image obtained by processing the selected approximate image. A distribution server configured in this way.

6. A distribution server as described in claim 5, The aforementioned distribution server is Before generating the label data which includes the processed image obtained by processing the selected approximate image, the selected approximate image is displayed on the distribution source device. Subsequently, upon receiving a transmission creation instruction from the distribution source device, the label data including the processed image obtained by processing the selected approximate image is generated and stored. A distribution server configured in this way.

7. A distribution server as described in claim 6, The aforementioned distribution server is Before generating the label data which includes the processed image obtained by processing the selected approximate image, the selected approximate image is displayed on the distribution source device. Subsequently, without receiving the creation instruction from the distribution source device, if the distribution source device receives a selection instruction that specifies a selected image which is one of the plurality of images after the image processing has been performed and is different from the approximate image, the label data including the processed image obtained by processing the selected image specified in the selection instruction is generated and stored. A distribution server configured in this way.

8. A distribution server as described in claim 1, The aforementioned distribution server is Multiple printers connected to the aforementioned network can be registered. The system identifies one of the printers connected to the network by receiving a selection of one of the registered printers from the distribution source device connected to the network. A distribution server configured in this way.

9. A distribution server as described in claim 1, The aforementioned distribution server is The created label data is distributed to the specified printer. A distribution server configured in this way.

10. A distribution server as described in claim 1, The aforementioned distribution server is In response to receiving a delivery request specifying the stored label data from a delivery destination device, which is a device different from the aforementioned delivery source device, The label data specified in the received distribution request is distributed to the distribution destination device. A distribution server configured in this way.

11. A distribution server as described in claim 1, For the identified printer, in addition to the sheet information, model information is also acquired as printer information. A distribution server configured in this way.

12. A distribution server according to claim 11, The model information obtained includes at least information that uniquely identifies the model of the printer. A distribution server configured in this way.

13. A distribution server connected to a network, The aforementioned distribution server is The distribution source device connected to the aforementioned network accepts the upload of an image file that stores image information. From the first printer connected to the aforementioned network, first printer information, including at least sheet information, is obtained. Based on the first printer information obtained from the first printer, a first label data is created and saved, which includes a first processed image obtained by processing the image shown in the image file uploaded from the distribution source device. From the second printer connected to the aforementioned network, second printer information, including at least sheet information, is obtained. Based on the second printer information obtained from the second printer, a second label data is created and saved, which includes a second processed image obtained by processing the image shown in the image file uploaded from the distribution source device. The first label data is distributed to the first printer. The second label data is distributed to the second printer. A distribution server configured in this way.

Images