Distribution server and printing program

Abstract

To provide a distribution server for storing and distributing label data, and to offer technology that reduces the possibility of unintended print results from the label data uploader. [Solution] Distribution server 1 connects to network 6 and receives label data uploads and print settings from distribution source PC 2 connected to network 6. Distribution server 1 stores the received label data and print settings linked together. Distribution server 1 distributes the stored label data and the print settings linked to that label data to distribution source PC 2 or label printer 5 connected to network 6. The destination PC 3 and label printer 5 use the print settings distributed along with the label data to print the label data.

Description

[Technical Field]

[0001] The technical field disclosed in the present specification relates to a delivery server that stores and delivers label data and a printing program. [Background Art]

[0002] Conventionally, techniques for registering and delivering label data by a delivery server are 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 accumulating 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 to consistently perform the processes of label design, label issuance and label cutting. [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2001-325084 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] When label data stored in a delivery server is downloaded and printed, print parameters are set in the client device that has downloaded the label data. Depending on the print parameters, the printing result may not match the intention of the uploader of the label data, that is, the creator of the label data. [Means for Solving the Problem]

[0005] One embodiment of the technology developed to solve the above-mentioned problems is a distribution server connected to a network, wherein the distribution server identifies one of the printers connected to the network, receives from a distribution source device connected to the network the specification of print settings based on the capabilities of the identified printer and the upload of label data, stores the uploaded label data and the specified print settings linked together, and the distribution server is configured to further distribute the uploaded label data and the print settings linked to the uploaded label data to a distribution destination device connected to the network.

[0006] The distribution server having the above configuration receives the upload of label data and the specification of print settings from the distribution source device, stores the received label data and print settings linked together, and distributes the label data and the print settings linked to that label data to the distribution destination device. As a result, when the distribution destination device prints based on the distributed label data, it is expected that it will use the print settings distributed along with the label data, increasing the likelihood that the print result will be as intended by the person who uploaded the label data.

[0007] Novel and useful control methods, devices, computer programs such as printing programs, and storage media readable by computers that store such computer programs are also necessary for realizing the functions of the above-mentioned distribution server. [Effects of the Invention]

[0008] The technology disclosed herein provides a distribution server for storing and distributing label data, which reduces the possibility of unintended printing results occurring on the label data uploader. [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 print settings upload process. [Figure 4] This diagram illustrates an example of a screen transition. [Figure 5] This is a sequence diagram illustrating an example of the label data upload process. [Figure 6] This diagram illustrates an example of a screen transition. [Figure 7] This is a sequence diagram illustrating an example of the manual distribution process. [Figure 8] This diagram shows an example of the automated distribution process procedure, and another diagram shows an example of the automated download settings screen. [Figure 9] This is a sequence diagram illustrating an example of the printing process. [Figure 10] This is a flowchart explaining the setup process. [Figure 11] This flowchart illustrates a modified version of the setup 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, 3 and a label printer 5 are connected to the distribution server 1 so that they can communicate via the network 6. The distribution server 1 is a server managed by the vendor of the label printer 5, 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.

[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. The label printer 5 is equipped with a main control panel 5a. The main control panel 5a 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 5a 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 stacked on 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 be loaded with a plurality of types of cassettes. There are various types of cassettes, including a cassette that accommodates a continuous long tape, a cassette that accommodates die-cut labels for price tags, and a cassette that accommodates die-cut labels for addresses. For sheets accommodated in the cassettes, the character color, background color, sheet size, material and the like differ depending on the cassette model. The sheet size includes a sheet width, which is a dimension in a direction orthogonal to the sheet conveyance direction, and a sheet length, which is a dimension in the sheet conveyance direction. The material is, for example, paper, resin sheet, or cloth. Further, the label printer 5 of the present embodiment may have a function of cutting a printed portion after printing and discharging the cut portion.

[0015] The PC 3 is communicably connected to the label printer 5. The communication method may be wireless or wired. A print application program (hereinafter referred to as a "print application") 32 for controlling printing by the label printer 5 is installed on the PC 3. The print application 32 is an example of a "print program".

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

[0017] The label printer 5 may be connected to the distribution server 1 via the distribution destination PC 3, or may be directly connected to the distribution server 1. Although only one distribution destination PC 3 and one label printer 5 are shown in FIG. 1, in practice, a plurality of distribution destination PCs 3 and a plurality of label printers 5 arranged in each store are connected to the distribution server 1.

[0018] PC2 is provided, for example, in a management company that manages the store described above. A label editing application program (hereinafter referred to as "label editing app") 22 for editing labels is installed on PC2.

[0019] The label editing app 22 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. PC2 can upload edited label data to the distribution server 1 via the label editing app 22. Further, PC2 can upload print settings associated with the label data to be uploaded to the distribution server 1 via the label editing app 22. The uploading of label data and print settings will be described later. In the following description, PC2 is referred to as "distribution source PC 2".

[0020] Note that the printing application 32 and the label editing app 22 can be communicably connected to the distribution server 1 via their own browser function or the browser included in the distribution destination PC 3 or the distribution source PC 2. The browser included in the distribution destination PC 3 or the distribution source PC 2 may be prepared in advance in the operating system (hereinafter referred to as "OS") of the distribution destination PC 3 or the distribution source PC 2, or may be installed separately from the OS.

[0021] The distribution source PC 2 is an example of the "distribution source device". The distribution destination PC 3 and the label printer 5 are examples of the "distribution destination device". The distribution destination PC 3 is an example of the "information processing device". The label printer 5 is an example of the "printer". Examples of the distribution source device, distribution destination device, and information processing device may be smartphones or tablet terminals.

[0022] <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.

[0023] 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.

[0024] 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"), the printer database 14 (hereinafter referred to as "printer DB 14"), and the configuration database 15 (hereinafter referred to as "configuration DB 15"). In Figure 1, the label DB 13, printer DB 14, and configuration DB 15 are located within the distribution server 1, but they may also be located outside the distribution server 1.

[0025] Label DB13 stores label data uploaded from the source PC2, etc. Figure 2(A) shows the structure of records registered in Label DB13. Label DB13 stores records for each label data, including fields that indicate the label ID, label name, label data, sample image, update history, and setting ID.

[0026] The field showing the label ID stores information that identifies the label. The field showing the label name stores the name of the label. The field showing the label data stores the label data uploaded to distribution server 1. The label data includes data indicating the type, content, and layout for each object placed in the label data. The field showing the sample image stores the URL indicating the location where the sample image for the label is saved. The field showing the update history stores the update history of the label data. The field showing the setting ID stores the setting ID of the print settings associated with the label data. For label data not associated with print settings, the field showing the setting ID will be left blank. The linking of label data and print settings will be described later.

[0027] Printer DB14 stores printer information for printers selected and registered from among the 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 name, capability information, and destination information.

[0028] 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 name stores the model name of the printer. 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 information stores information that indicates the destination of the printer, such as the IP address.

[0029] The settings database 15 stores the print settings uploaded from the source PC 2, etc. Figure 2(C) shows the structure of the records registered in the settings database 15. The settings database 15 stores a record for each print setting that includes fields indicating the settings ID and the print setting data. The settings ID stores information that identifies the print setting. The print setting data stores print setting data that indicates the uploaded print setting. The print setting data includes the setting values ​​set for each item of the print setting. The print setting data also includes change data that indicates whether the print setting can be changed.

[0030] <Explanation of streaming operation> Next, the distribution operation of system 100 will be explained. In this configuration, the example will be that label data and print settings uploaded by the administrator from the source PC 2 to the distribution server 1 are distributed from the distribution server 1 to the destination PC 3 or label printer 5. 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 is omitted when explaining the operation of each program. Also, "acquisition" is used as a concept that does not necessarily require a request.

[0031] <Creating label data> First, let's explain the process of creating the label data for distribution. The administrator launches the label editing application 22 on the source PC2 (A01) and creates the label data for distribution (A02).

[0032] When a label editing instruction is received, the label editing application 22 displays a label editing screen (not shown) on the source PC 2. The label editing application 22 has several objects prepared in advance, and objects are placed on the label editing screen according to user operations. The objects are, for example, text, images, frames, shapes, barcodes, and QR codes. For example, the administrator places a text object indicating the product name, a text object indicating the selling price, and a barcode object indicating a barcode that records a flag, product price, and product code on the label editing screen to create price tag label data. The label editing application 22 may also use a database to write text and numbers to the objects.

[0033] When the label editing application 22 receives a save command, it saves the edited label data to the source PC2 (A03). The label data is saved in format 1. Format 1 is a file format that can save not only the information necessary for printing but also the information necessary for editing the label data. Label data saved in format 1 can be edited even after saving.

[0034] <Printer Registration> Next, the process of registering a printer will be explained. As shown in Figure 3, when the source PC2 receives a command to connect to the distribution server 1 (A11), it connects to the distribution server 1 in a communicable manner using the browser function of the label editing application 22 or the browser of the source PC2 (A12). When the distribution server 1 connects to the source PC2, the front-end application 11 provides the source PC2 with the home screen D2 exemplified in Figure 4(A) (A13). The administrator who registers the printer operates the fourth button SW24 on the source PC2.

[0035] When the front-end application 11 receives a printer registration request in response to the operation of the fourth button SW24 (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 source PC2 with a printer registration screen including the search results (B05). The front-end application 11 accepts the specification of a printer 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).

[0036] 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).

[0037] In this configuration, the backend application 12 selected a printer from the searched printers, but the frontend application 11 could also accept input from the user and select a printer based on the entered destination information. Furthermore, the order of printer registration and label data creation does not matter.

[0038] <Upload print settings> Next, we will explain the operation of uploading print settings to the distribution server 1. As shown in Figure 3, when the third button SW23 on the home screen D2, as exemplified in Figure 4(A), is operated, the front-end application 11 receives a print setting registration request (C01) and requests the back-end application 12 to send a list of printers (C02), as shown in Figure 3.

[0039] The backend application 12 accesses the printer database 14 in response to a request to send a printer list and retrieves the information necessary to display the printer list from the printer database 14 (C03). The backend application 12 creates a printer list based on the information retrieved from the printer database 14 and passes it to the frontend application 11 (C05). The frontend application 11 provides the printer selection screen, which includes the printer list received from the backend application 12, to the source PC2 (C06). Figure 4(B) shows an example of the printer selection screen D5.

[0040] The printer selection screen D5 displays a printer list L51, which shows, for example, the printer name, printer ID, and model name for each printer. The printer selection screen D5 also displays radio buttons R51 for each printer to indicate whether it is selected or not. The administrator, for example, selects one printer via radio button R51 and then operates the apply button SW51.

[0041] As shown in Figure 3, when the front-end application 11 identifies a printer via the radio button R51 in response to the operation of the apply button SW51 (C11), it requests the back-end application 12 to send the capability information of the selected printer (C12). The request to send capability information is accompanied by the printer ID of the printer identified in C11. The back-end application 12 accesses the printer DB 14, retrieves the capability information associated with the printer ID attached to the request to send capability information (C13), and passes it to the front-end application 11 (C14). Since the back-end application 12 retrieves the capability information from the printer DB 14 in the distribution server 1, it can retrieve the capability information of the selected printer even if the selected printer is offline. Alternatively, the back-end application 12 may read destination information associated with the printer ID from the printer DB 14, connect to the printer identified based on the retrieved destination information, and retrieve the capability information.

[0042] When the front-end application 11 receives capability information from the back-end application 12, it provides the print settings registration screen to the source PC2 (C15). Figure 4(C) shows an example of the print settings registration screen D3. The print settings registration screen D3 accepts setting values ​​for each print setting item. The options for each item reflect the capability information received from the back-end application. Therefore, the print settings accepted via the print settings registration screen D3 are set to values ​​based on the capabilities of the selected printer.

[0043] The print settings may consist of some or all of the multiple settings available for the selected printer. The print settings registration screen D3 in this configuration includes setting fields PS31, PS32, PS33, and PS34 for the number of copies, sheet settings, resolution, and image quality mode. For example, depending on the label's application, such as medical labels, the required number of labels may be fixed. If the number of copies is arbitrarily set at the distribution destination, the required number of labels may not be printed. Therefore, it is preferable to be able to specify the number of copies. Also, for example, if the sheet settings such as sheet size, text color, and background color set during label editing differ from the sheet settings set in the print settings, there is a possibility of missing parts in the print result. Therefore, it is preferable to be able to specify the sheet settings. Furthermore, for example, two-dimensional codes such as barcodes and QR codes (registered trademarks) may not be readable without a certain resolution. Therefore, it is preferable to be able to specify the resolution. Also, for example, there are multiple algorithms for binarizing data, and the image quality of the print result may differ depending on the algorithm. Therefore, it is preferable to be able to specify the image quality mode.

[0044] Note that the print settings stored on distribution server 1 may differ from those in this configuration. For example, it is not necessary to be able to specify settings for all of the following: number of copies, sheet settings, resolution, and image quality mode. Also, for example, it is possible to specify items other than the number of copies, sheet settings, resolution, and image quality mode.

[0045] The print settings registration screen D3 has a changeability specification field PS35 that specifies whether the specified print settings can be changed or not. In this embodiment, the changeability specification field PS35 accepts the specification of whether the print settings as a whole can be changed or not, but it may also be provided for each print setting item, and the specification of whether the settings can be changed or not can be accepted for each item.

[0046] The administrator sets the values ​​for each item in the print settings displayed on the print settings registration screen D3, and after setting whether the print settings can be changed in the changeability specification field PS35, they operate the apply button SW31.

[0047] As shown in Figure 3, when the front-end application 11 receives a print setting registration instruction in response to the operation of the apply button SW31 (C22), it requests the back-end application 12 to register the print settings (C23). The print setting registration request includes the print settings set via the print setting registration screen D3 and change data indicating whether the settings can be changed, as set in the changeability specification field PS35.

[0048] When the backend application 12 receives a print settings registration instruction, it saves the print settings received from the frontend application 11 to the settings database 15 (C24). For example, the backend application 12 creates a settings ID and adds a record containing the created settings ID to the settings database 15. The backend application 12 stores print settings data, including the print settings and change data attached to the print settings registration instruction, in a field indicating the print settings data of the added record. When the registration of the print settings is complete, the backend application 12 notifies the frontend application 11 that the upload of the print settings is complete (C25). In response to the completion notification from the backend application 12, the frontend application 11 provides a screen to the source PC2 notifying that the upload of the print settings is complete (C26).

[0049] <Upload label data> Next, we will explain the operation of uploading label data to the distribution server 1. When the administrator operates the first button SW21 on the home screen D2, as exemplified in Figure 4(A), the front-end application 11 accepts the upload request (D01) and provides the upload screen to the distribution source PC2 (D02), as shown in Figure 5.

[0050] Figure 6(A) shows an example of the upload screen D7 displayed on the source PC2. The upload screen D7 displays the label list L71 of the label data stored on the source PC2. For example, a sample image is displayed for each label data in the label list L71. In addition, information such as the label name, last updated date, and label ID is displayed for each label data in the label list L71. Furthermore, a radio button R71 is displayed for each label data in the label list L71. The administrator selects one label data to be uploaded via the radio button R71. The upload screen D7 may also accept input of supplementary information used in the label list, such as the label name and sample image. After specifying the label data and entering the supplementary information, the administrator operates the post button SW71 displayed on the upload screen D7.

[0051] As shown in Figure 5, when the front-end application 11 accepts the submission of label data in response to the operation of the submission button SW71 (D07), it provides a print setting confirmation screen to the distribution PC2 (D09). Figure 6(B) is an example of the print setting confirmation screen D8 displayed on the distribution PC2. The print setting confirmation screen D8 has a button SW81 that instructs the user to specify print settings and another button SW81 that instructs the user not to specify print settings. The administrator operates button SW81 when specifying print settings on the distribution device.

[0052] As shown in Figure 5, when the front-end application 11 receives a print setting specification instruction in response to the operation of button SW81 (D11), it requests the back-end application 12 to send a list of print settings (D12). When the back-end application 12 receives the request to send the list of print settings, it accesses the settings DB 15 and reads the print setting data stored in the settings DB 15 along with the setting ID (D13). The back-end application 12 passes the print setting list, which displays the read print setting data, to the front-end application 11 (D14). The front-end application 11 provides the print setting specification screen, which includes the print setting list received from the back-end application 12, to the source PC2 (D15).

[0053] Figure 6(C) shows an example of the print settings selection screen D6 displayed on the source PC2. The print settings list L61 displays print setting data for each print setting, for example. Furthermore, the print settings selection screen D6 displays a radio button R61 for each print setting. Each radio button R61 is associated with a setting ID. After the administrator selects one print setting via radio button R61, they operate the apply button SW61.

[0054] As shown in Figure 5, when the front-end application 11 receives the specification of print setting data via the radio button R61 in response to the operation of the apply button SW61 (D21), it requests the back-end application 12 to register the label data (D22). The request for registration of label data includes the label data selected in D07 and the setting ID associated with the print setting data specified in D21. In addition, if the front-end application 11 accepts supplementary information such as the label name and sample image on the upload screen, it adds this supplementary information to the request for registration of label data.

[0055] When backend application 12 receives a request to register label data, it accesses label DB 13 and registers the label data uploaded from source PC 2 in label DB 13 (D23). For example, backend application 12 creates a label ID and adds a record containing the created label ID to label DB. Backend application 12 stores the label data attached to the label data registration request in the label data field. Backend application 12 stores the setting ID attached to the label data registration request in the setting ID field. Backend application 12 stores the label name and sample image fields, along with the URL information indicating the storage location of the sample image, which are included in the supplementary information. Backend application 12 stores the registration date and time in the update history field.

[0056] The backend application 12 may either save the label data to the label DB 13 in the uploaded file format (first format) or convert it to the second format before saving it to the label DB 13. The second format is a file format from which information unnecessary for printing is removed and which cannot be edited. Label data can be converted from the first format to the second format, but it cannot be converted from the second format to the first format.

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

[0058] As a result, the uploaded label data is associated with the specified print settings by having the setting ID stored in the setting ID field of the label DB13. However, if button SW82 on the print setting confirmation screen D8 provided by the frontend application 11 is operated, the distribution server 1 will not perform steps D11 to D21, but will register the label data selected on the upload screen D7 in the label DB13. In this case, the field indicating the setting data for the registered label data will be left blank, and it will not be associated with the print setting data.

[0059] <Manual download of label data> Next, we will explain the process of distributing label data. First, we will explain the process of the destination PC3 manually downloading the label data. As shown in Figure 7(A), when the destination PC3 receives a command to connect to the distribution server 1 (F01), it connects to the distribution server 1 using the browser function of the print application 32 or its own browser (F02). The front-end application 11 of the distribution server 1 provides the home screen D2 shown in Figure 4(A) to the destination PC3 (F03).

[0060] When the second button SW22 on the home screen D2 is pressed, the front-end application 11 accepts a download request (G01) and requests the back-end application 12 to send the label list (G11). Upon receiving the request for the label list, the back-end application 12 reads the label data from the label DB 13 (G12). Based on the label data read from the label DB 13, the back-end application 12 generates a label list and passes it to the front-end application 11 (G13). Upon receiving the label list, the front-end application 11 provides the download screen containing the received label list to the destination PC3 (G14).

[0061] The printing 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 deliver the label data (G23). The delivery request for the label data includes the label ID of the selected label data and the destination information of the PC 3 that sent the download request. When the back-end application 12 receives the delivery request, the delivery server 1 performs a delivery process to deliver the selected label data to the source of the delivery request. G21 is an example of a "specification process". The download instruction is an example of a "delivery request".

[0062] The distribution process will be explained with reference to Figure 7(B). The backend application 12, upon receiving the distribution request, determines whether or not there are print settings associated with the label data to be downloaded (H01). For example, if a setting ID is associated with the label data to be downloaded, the backend application 12 determines that there are print settings associated with the label data to be downloaded. If there are associated print settings (alt: yes), the backend application 12 reads the record containing the setting ID associated with the target label data from the setting DB 15 and obtains the print setting data (H11). The backend application 12 distributes the label data to be downloaded, the print setting data obtained from the setting DB 15, and the destination information attached to the distribution request in G23 of Figure 7(A) to the destination PC 3, which is the source of the download request (H12). Alternatively, the backend application 12 may distribute the label data to the destination PC 3 via the frontend application 11.

[0063] When the print application 32 on the receiving PC 3 receives the label data and print settings data distributed from the distribution server 1 (H12), it associates the received label data and print settings and saves them (H14). H13 is an example of the "download process". H14 is an example of the "save process".

[0064] On the other hand, if the backend application 12 does not associate a setting ID with the label data to be downloaded, it determines that there is no print setting associated with the label data to be downloaded. If there is no associated print setting (alt: none), the backend application 12 distributes only the label data to be downloaded to the destination PC 3, which is the source of the download request, according to the destination information attached to the distribution request in G23 of Figure 7(A) (H22). Alternatively, the backend application 12 may distribute the label data to the destination PC 3 via the frontend application 11. The print application 32 on the destination PC 3 saves the received label data (H23).

[0065] Therefore, if the receiving PC3 has the linked print settings associated with the label data to be downloaded, it can download and save the linked print settings along with the label data.

[0066] <Automatic download of label data> Next, we will explain how the destination PC3 automatically downloads the label data. As shown in Figure 8(A), the operator registers the setting to automatically download the label data in the printing application 32 in advance (J01).

[0067] Specifically, the print application 32 displays the automatic download settings screen D12, as illustrated in Figure 8(B), on the destination PC 3. The print application 32 connects to the distribution server 1, obtains a list of label data stored on the distribution server 1, and displays the obtained label list L121 on the automatic download settings screen D12. The automatic download settings screen D12 has radio buttons R121 for each label data. The automatic download settings screen D12 also has a download timing setting field ST121 for setting the timing at which download instructions are automatically sent. The timing at which download instructions are automatically sent can be a pre-specified timing, such as when the print application 32 is started, or it can be a periodic timing, such as every few hours.

[0068] When the print application 32 selects one label data from the label list L121 and sets the timing for automatically sending download instructions in the download timing setting field ST121, and the apply button SW121 is pressed, the print application 32 receives the specification of the label data to be downloaded and the download timing, and stores them in the memory area for the print application 32 provided on the destination PC 3. The process of receiving the specification of label data via the automatic download setting screen D12 is an example of a "specification process".

[0069] As shown in Figure 8(A), when the print application 32 detects the download timing set via the download timing setting field ST121 (K01), it connects to the front-end application 11 (K02) and automatically sends a download instruction to the front-end application 11 (K03). The download instruction is accompanied by the label ID of the label data specified in J01. The automatically sent download instruction is an example of a "delivery request". The front-end application 11 passes the download instruction, along with the label ID attached to the download instruction and the destination information of the distribution destination PC 3 which is the source of the download instruction, to the back-end application 12. When the back-end application 12 receives the download instruction, the distribution server 1 executes the distribution process. The distribution process is the same as described in Figure 7(B) above, so the explanation is omitted.

[0070] Therefore, if the label data to be downloaded is linked to print settings, the printing application 32 can update to the latest label data and print settings by automatically downloading and overwriting the linked print settings along with the label data.

[0071] Furthermore, the label printer 5, like the printing application 32, may manually or automatically download label data and print settings from the distribution server 1 and save them linked together. In other words, the distribution server 1 may directly distribute the label printer and print settings to the label printer 5 in response to a distribution request from the label printer 5.

[0072] In this configuration, the distribution server 1 distributes label data and print settings in response to a distribution request from the destination PC 3 or label printer 5. Alternatively, the distribution server 1 may push-distribute the label data and print settings to a predetermined destination device. When using push-distribution, for example, the distribution server 1 receives and registers the specification of the label data to be pushed, the destination information of the destination device, and the specification of the timing for push-distribution. When the distribution server 1 detects the specified push-distribution timing, it executes the distribution process shown in Figure 7(B) and distributes the label data specified as the target of push-distribution, along with the print settings associated with that label data, to the destination PC 3 or label printer 5 according to the specified destination information.

[0073] <Printing label data> This section describes the operation by which the printing application 32 causes the label printer 5 to print based on the label data downloaded from the distribution server 1. As shown in Figure 9, the printing application 32 accepts the selection of the label data to be printed and the label printer 5 to perform the printing (M01), and when a print command is received (M02), it executes a setting process (M03). The setting process involves displaying a setting screen that accepts print settings and accepting print settings through the setting screen.

[0074] The setup process will be explained with reference to Figure 10. First, the print application 32 determines whether it can communicate with the distribution server 1 (S1). If the print application 32 can communicate with the distribution server 1 (S1: YES), it causes the destination PC 3 to execute a download process to download the label data to be printed and the print setting data associated with the label data to be printed from the distribution server 1 (S3). The print application 32 causes the destination PC 3 to execute a process to update the label data to be printed and the print setting data associated with the label data to be printed using the downloaded label data and print setting data (S5). As a result, for example, even if the administrator updates the label data or print settings after the label data to be printed and the print setting data have been distributed to the destination PC 3, the updates will be reflected in the label data to be printed and the print settings used for printing. Therefore, the expectation that the administrator will obtain the intended print result is further increased.

[0075] On the other hand, if the print application 32 cannot communicate with the distribution server 1 (S1:NO), it skips S3 and S5 and proceeds to S11. In other words, the print application 32 does not download the label data and print settings data from the distribution server 1.

[0076] The print application 32 displays a settings screen on the destination PC 3 that accepts print settings (S11). The print application 32 determines whether or not print settings have been specified (S13). The print application 32 determines that print settings have been specified if it has saved print settings associated with the label data to be printed. If print settings have been specified (S13: YES), the print application 32 sets the specified print settings as the initial values ​​(S15). That is, the print application 32 sets the setting values ​​of the specified print settings as the initial values ​​for the items included in the specified print settings among the items displayed on the settings screen. The print application 32 also sets pre-prepared initial values ​​for the items not included in the specified print settings among the items displayed on the settings screen.

[0077] After S15, the print application 32 determines whether there is a specification that the specified print settings cannot be changed (S17). The print application 32 determines that there is a specification that the specified print settings cannot be changed if the print setting data associated with the label data includes change data indicating that the settings cannot be changed. If there is a specification that the settings cannot be changed (S17: YES), the print application 32 prohibits the operation to change the specified print settings (S19) and terminates the setting process. For example, the print application 32h grays out the specified print setting item and does not accept input. This allows the print application 32 to maintain the setting value for the specified print setting item while accepting settings for items other than the specified print setting.

[0078] The print application 32 determines that there is no specification to restrict the specified print settings if the print setting data associated with the label data does not contain any change data indicating that the settings cannot be changed. If there is no specification that the settings cannot be changed (S17:NO), the print application 32 skips S19 and terminates the setting process. In other words, the print application 32 allows changes to the print settings, including the specified print settings. The settings screen has the setting values ​​included in the specified print settings placed as initial values ​​in the items of the specified print settings, so the specified print settings can be used to print label data as long as the setting values ​​are not changed.

[0079] On the other hand, if the print application 32 has not saved the print settings associated with the label data to be printed, it determines that no print settings have been specified. If no print settings have been specified (S13:NO), the print application 32 places the pre-prepared initial values ​​in all items on the settings screen (S31) and terminates the settings process.

[0080] Returning to Figure 9, when the print application 32 receives a print command (M11), it generates a print command to print the label data using the print settings configured on the settings screen (M12). If the setting values ​​based on the specified print settings have not been changed by the setting values, the print application 32 can generate a print command to print the label data using the print settings associated with the label data.

[0081] The printing application 32 outputs the generated print command to the label printer 5 (M13). M13 is an example of a "printing process". The label printer 5 prints the label data according to the received print command (M15). If the print command is one that prints the label data using the print settings associated with the label data, the label printer 5 will execute the print according to the specified print settings. Therefore, it can be expected that the print result will be as intended by the administrator.

[0082] Furthermore, when the label printer 5 directly receives label data and print setting data from the distribution server 1 and stores the label data and print settings linked together, it receives the specification of label data and a print command via the main unit's control panel 5a, and prints the specified label data using the print settings linked to that label data. Therefore, similar to the print application 32, it can be expected that the print result will be as intended by the administrator.

[0083] As described above, the distribution server 1 in the above embodiment receives the upload of label data and the specification of print settings from the distribution source PC 2, stores the received label data and print settings linked together, and distributes the label data and the print settings linked to that label data to the distribution destination PC 3 or label printer 5. As a result, when the distribution destination PC 3 or label printer 5 prints based on the distributed label data, it is expected that the print settings distributed along with the label data will be used, increasing the likelihood that the print result will be as intended by the administrator who uploaded the label data.

[0084] 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.

[0085] For example, distribution server 1 may only perform push distribution. However, when distribution server 1 receives a request for distribution of a predetermined label data from a destination PC 3 or label printer 5, it is expected that the destination PC 3 or label printer 5 that made the distribution request will use the print settings when instructing the printing of the predetermined label data.

[0086] For example, distribution server 1 does not have to directly distribute label data to label printer 5. However, by distributing the label data stored in label DB 13 and the print settings associated with that label data to the specified label printer 5, distribution server 1 can be expected to print the label data using the specified print settings on the specified label printer 5.

[0087] For example, the PS35 field for specifying whether the print settings can be changed on the print settings registration screen D3 may be omitted, and print settings data without change data may be linked to the label data and distributed. However, the distribution server 1 accepts the specification of whether the specified print settings can be changed along with the print settings, and distributes change data indicating whether the print settings can be changed along with the label data and print settings to the destination PC 3 and label printer 5, thereby allowing the destination PC 3 and label printer 5 to restrict changes to the print settings.

[0088] For example, in the above embodiment, in D23 of Figure 5, the label data linked to the setting ID is registered in the label DB 13, thereby linking the label data with the print setting data. In contrast, the distribution server 1 stores the linking data that links the label ID and the setting ID in a predetermined storage area, and does not need to register the label data linked to the setting ID in the label DB 13.

[0089] For example, in the above embodiment, the label data and print setting data were stored in separate files on the distribution server 1. Alternatively, for example, during the label data upload process, a process to set values ​​for the print setting items could be performed, and the print settings set in that process could be included as part of the uploaded label data, so that the distribution server 1 stores the label data including the print settings. This eliminates the need to store linking data and print setting data separately from the label data, making it easier to manage the linking between label data and print setting data. However, by storing the label data and print setting data in separate files on the distribution server 1, it becomes possible to link one print setting data to multiple label data.

[0090] For example, in the setting process shown in Figure 10, even if print settings are specified, the setting screen is displayed (S11, S13: YES). In contrast, as shown in Figure 11, for example, if print settings are specified (S13: YES), the print application 32 may terminate the setting process without displaying the setting screen. On the other hand, if no print settings are specified (S13: NO), the print application 32 may display the setting screen (S103) and accept print settings. In this way, when printing label data downloaded together with print settings, the print application 32 does not display the setting screen on the destination PC 3 and prints using the downloaded print settings, thereby suppressing changes to the print settings on the destination PC 3.

[0091] For example, step S15 in Figure 10 may be omitted. However, when printing label data downloaded along with the print settings, the print application 32 displays a settings screen with the downloaded print settings as the initial value, allowing the user to confirm the print settings. Furthermore, if the print settings are not changed, printing will be performed using the downloaded print settings, so it can be expected that the label data will be printed with the print settings intended by the administrator who uploaded it.

[0092] For example, steps S17 and S19 in Figure 10 may be omitted. However, when printing label data downloaded along with print settings, the print application 32 increases the likelihood of achieving the print result intended by the person who uploaded the label data by prohibiting the operation to change the downloaded print settings. Furthermore, by prohibiting the operation to change print settings when the data to be changed indicates that it cannot be changed, changes to print settings in the print application 32 can be controlled according to the administrator's intentions.

[0093] For example, steps S1 to S5 in Figure 10 may be omitted. However, the printing application 32 periodically downloads the specified label data and print settings, so that even if the administrator updates the specified label data, the updates can be reflected on the destination PC 3.

[0094] 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, the order in which print settings and label data are saved, or the order in which label data and print settings are specified when specifying distribution labels, may differ from the above-described form.

[0095] 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]

[0096] 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 Identify one of the printers connected to the aforementioned network, The source device connected to the aforementioned network receives the specification of print settings based on the capabilities of the identified printer, and the upload of label data. The uploaded label data and the specified print settings are linked and saved. The aforementioned distribution server further: The uploaded label data and the print settings associated with the uploaded label data are distributed to the distribution destination device connected to the network. A distribution server configured in this way.

2. A distribution server as described in claim 1, The aforementioned distribution server is Upon receiving a delivery request from the aforementioned delivery destination device specifying one of the stored label data, The label data specified in the received distribution request and the print settings associated with the specified label data are distributed to the distribution destination device. A distribution server configured in this way.

3. A distribution server as described in claim 1, The aforementioned distribution server is The identified printer is designated as the distribution destination device, and the uploaded label data and the print settings associated with the uploaded label data are distributed to the distribution destination device. A distribution server configured in this way.

4. A distribution server according to any one of claims 1 to 3, The aforementioned distribution server is The distribution source device connected to the network receives the print setting specification, and stores the print setting data indicating the specified print setting. The distribution source device connected to the network receives the upload of the label data, and stores the uploaded label data. The system accepts a selection of one of the saved label data and a selection of one of the saved print setting data, and saves linking data indicating that the selected label data and print setting data are linked. The aforementioned distribution server further: Based on the stored linking data, the uploaded label data and the print setting data linked to the uploaded label data are distributed to the distribution destination device. A distribution server configured in this way.

5. A distribution server according to any one of claims 1 to 3, The aforementioned distribution server is By including the specified print settings in the uploaded label data and saving it, the label data and the print settings are linked. The aforementioned distribution server further: The uploaded label data, including the print settings, is distributed to the distribution destination device. A distribution server configured in this way.

6. A distribution server according to any one of claims 1 to 3, The print settings, based on the capabilities of the identified printer, include settings related to resolution. A distribution server configured in this way.

7. A distribution server according to any one of claims 1 to 3, The print settings based on the capabilities of the identified printer include setting values ​​related to sheet settings. A distribution server configured in this way.

8. A distribution server according to any one of claims 1 to 3, The print settings, based on the capabilities of the identified printer, include a setting value for the number of copies. A distribution server configured in this way.

9. A distribution server according to any one of claims 1 to 3, The aforementioned distribution server is The source device connected to the network receives a specification regarding whether or not the specified print settings can be changed. Change data indicating whether the specified print settings can be changed is included in the specified print settings and saved. The aforementioned distribution server further: The uploaded label data and the print settings associated with the uploaded label data, including the modified data, are distributed to the distribution destination device. A distribution server configured in this way.

10. A printing program that can be executed by an information processing device connected to a network and has the function of outputting a print command, wherein a distribution server is connected to the network, and label data and print settings are stored in association with each other on the distribution server. The aforementioned information processing device, A specification process that specifies one of the label data stored on the distribution server, A download process that downloads the label data specified in the aforementioned specification process and the print settings associated with the specified label data from the distribution server. A saving process that links and saves the label data and print settings downloaded in the aforementioned download process, A printing process that sends a print command to a printer to print the label data saved in the saving process using the print settings saved in association with the label data, To execute A printing program configured in such a way.

11. A printing program according to claim 10, The aforementioned information processing device, When a printer is selected and a print command is received for the label data being edited, If the label data being edited is not the same as the label data saved in the saving process, A settings screen is displayed that accepts print settings based on the capabilities of the selected printer, and a setting process is executed that accepts print settings via the settings screen. The print command to print the label data being edited using the print settings received on the settings screen is sent to the selected printer. If the label data being edited is the same label data that was saved in the saving process, The aforementioned setting process is not executed, and the aforementioned printing process is executed. A printing program configured in such a way.

12. A printing program according to claim 10, The aforementioned information processing device, When a print command is issued for the label data downloaded in the aforementioned download process, A settings screen is displayed that accepts print settings based on the capabilities of the selected printer; a setting process is executed that accepts print settings via the settings screen; and in the setting process, the print settings saved in association with the label data saved in the saving process are displayed as the initial values ​​on the settings screen. A printing program configured in such a way.

13. A printing program according to claim 12, In the aforementioned configuration process, The following operations on the settings screen are prohibited, which include changing the print settings that have been saved in association with the label data saved in the saving process. A printing program configured in such a way.

14. A printing program according to claim 12, The print settings downloaded from the distribution server include change data indicating whether the print settings can be changed. In the aforementioned configuration process, If the print settings saved in association with the label data saved in the aforementioned saving process contain change data indicating that the change cannot be changed, the predetermined operation on the settings screen that changes the print settings saved in association with the label data saved in the aforementioned saving process is prohibited. A printing program configured in such a way.

15. A printing program according to claim 10, The aforementioned information processing device, The aforementioned download process is performed periodically to update the saved label data and print settings. A printing program configured in such a way.

16. A printing program according to claim 15, The aforementioned information processing device, When a print command is issued for the label data downloaded in the aforementioned download process, If communication with the distribution server is possible, the download process is executed to update the stored label data and print settings, and after the download process is completed, the print process is executed. If communication with the aforementioned distribution server is not possible, the download process will not be executed, and the printing process will be executed instead. A printing program configured in such a way.

Images