Label printer and printing system

Abstract

To provide a technique for optimally printing label data created by an external device on a label printer.SOLUTION: PC 100 transmits label data 23 created by a label creation application 110 to a cloud server 200 and a label printer 1. In response to a print command in a state where an offline mode is selected, the label printer 1 performs printing based on print data obtained by rasterizing the received label data 23, using printer font data 22 stored in a memory 12. On the other hand, in response to a print command in a state where an online mode is selected, the label printer receives, from the cloud server 200, print data obtained through rasterization by the cloud server 200 on the label data 23 stored in the cloud server 200 using server font data 211 stored in the cloud server 200, and then prints the rasterized data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technical field disclosed herein relates to label printers and printing systems. [Background technology]

[0002] Conventionally, there is known a configuration in which data to be printed is converted into data that can be handled by a printer by an external device other than the printer. For example, Patent Document 1 discloses a configuration in which a printer acquires a document file from a web server, and if the file format of the acquired document file is not a file format that the printer can process, the printer requests a server that can convert the document file into data that the printer can process, and then receives and prints the data transmitted from the server in response to the conversion and transmission request. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-055051 Summary of the Invention [Problem to be solved by the invention]

[0004] Label printers can print based on label data created on an external device such as a personal computer (PC). While external devices can use a variety of fonts when creating label data, label printers are limited in the fonts they can support. When printing based on label data that uses a font that the label printer cannot support, one possible configuration is to pass the label data to a server and request rasterization, as disclosed in Patent Document 1, for example. However, there is room for improvement in the technology for printing label data created by external devices. [Means for solving the problem]

[0005] The label printer, which was developed to solve the above-mentioned problems, A printing department; a communication interface; A user interface; a memory capable of storing font data and label data; A controller; A label printer comprising: The controller receiving label data transmitted from an information processing device via the communication interface and executing a storage process to store the received label data in the memory, the label data being transmitted from the information processing device to the label printer and the server; The controller further comprises: a label selection process for accepting a selection of one of the label data stored in the memory via the user interface; a print instruction process for receiving a print instruction via the user interface when one of the label data stored in the memory is selected; the print instruction includes a first print instruction and a second print instruction, The controller further comprises: if the received print instruction is the first print instruction, executes a first print process that uses the font data stored in the memory to rasterize the selected label data to generate first print data, and uses the printing unit to print based on the generated first print data; executes a transmission request process to send a transmission request specifying the selected label data to the server via the communication interface if the received print instruction is the second print instruction; The controller further comprises: When second print data, which is rasterized by the server from the label data stored in the server and corresponds to the label data specified in the transmission request, is received from the server via the communication interface in response to the transmission request, the second print process is executed to print based on the received second print data using the printing unit. It is configured as follows.

[0006] The label printer disclosed in this specification receives label data created by a program on an information processing device and stores it in its own memory. The label data is also stored in advance on a server. When a first print command is received, the label printer uses font data stored in its own memory to print based on first print data rasterized from the label data stored in its own memory, enabling offline printing. When a second print command is received, the label printer receives and prints second print data rasterized from label data stored on the server. Even if a font that the label printer cannot support is set in the label data created by the program on the information processing device, if the server has font data corresponding to that font, the text will be printed in that font.

[0007] A control method for realizing the functions of the above-described device, a computer program, and a computer-readable storage medium storing the computer program are also novel and useful. [Effects of the Invention]

[0008] The technology disclosed in this specification enables a label printer to suitably print label data created by an external device. [Brief explanation of the drawings]

[0009] [Figure 1]1 is a block diagram showing a configuration of a printing system and an electrical configuration of a label printer according to an embodiment of the present invention; [Figure 2] FIG. 2 is a diagram illustrating a storage mode of the label printer. [Figure 3] 1 is an external perspective view of a label printer according to an embodiment; [Figure 4] FIG. 1 is a diagram illustrating an outline of the internal configuration of a label printer. [Figure 5] FIG. 10 is a sequence diagram showing a preparation procedure of the printing system according to the embodiment. [Figure 6] FIG. 4 is a sequence diagram showing a main procedure of the printing system according to the embodiment. [Figure 7] FIG. 10 is a sequence diagram showing the procedure of online processing. [Figure 8] 10 is a flowchart showing the procedure of offline processing. FIG. 11 is a diagram showing the contents of label data to be stored. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the label printer of the present invention will be described in detail with reference to the accompanying drawings. This embodiment discloses a printing system including the label printer of the present invention, a cloud server, and a personal computer (PC).

[0011] <Outline of printing system configuration> 1, the printing system 400 of this embodiment includes a label printer 1, a PC 100, and a cloud server 200, each of which is connected to the Internet 40 and is configured to be able to communicate with one another. Note that the number of label printers and PCs that can configure the printing system 400 is not limited to one, and there may be multiple devices.

[0012] The label printer 1 of this embodiment is equipped with a controller 10 including a CPU 11 and a memory 12. The label printer 1 also has a user interface (hereinafter referred to as "user IF"), a communication interface (hereinafter referred to as "communication IF") 14, and a printing unit 15, which are electrically connected to the controller 10.

[0013] The CPU 11 executes various processes in accordance with programs read from the memory 12 and based on user operations. Note that the controller 10 in Figure 1 is a general term for the hardware and software used to control the label printer 1, and does not necessarily represent a single piece of hardware that actually exists in the label printer 1.

[0014] The memory 12 of the label printer 1 of this embodiment stores various programs and various data, including a control program 21. The control program 21 is a program that causes the label printer 1 to perform printing operations and input and output various data. The control program 21 includes a program that functions as an operating system. Examples of data stored in the memory 12 include font data 22 (hereinafter, font data held by the label printer 1 will be referred to as "printer font data") and label data 23 to be printed.

[0015] The label printer 1 stores one or more printer font data 22, and is capable of supporting fonts based on the printer font data 22 stored in the memory 12. The label data 23 is data in a format that can be used for printing by the label printer 1, and is created by a label creation application 110, which will be described later. Details of each piece of data will be described later. The memory 12 is also used as a work area when various processes are executed. The buffers provided in the CPU 11 are also an example of memory.

[0016] Note that examples of memory are not limited to ROM, RAM, HDD, etc. built into the label printer 1, but may also be storage media that can be read and written by the CPU 11. For example, external memory such as a USB memory or HDD connected to the label printer 1, and memory or HDD provided in a device connected to the label printer 1 via the communication IF 14 are also examples of memory.

[0017] The memory 12 of the label printer 1 has a memory area reserved for saving multiple pieces of label data 23, and the label printer 1 can store multiple pieces of label data 23 in the memory 12. As shown in FIG. 2, the label printer 1 of this embodiment has five memory areas reserved for saving label data 23, and each memory area is assigned a storage number. The label printer 1 then stores the label data 23 in association with the storage number. When the label printer 1 is shipped from the factory, no label data 23 is stored in the memory 12. Furthermore, the number of label data 23 that can be saved is not limited to five, and may be four or less, or six or more.

[0018] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting user operations. Specifically, the user IF 13 of this embodiment includes a key group 31 consisting of a plurality of keys and a liquid crystal display 32, as shown in FIG. 3. The user IF 13 may also include a touch panel having a notification function and an operation acceptance function. The user IF 13 may also include another notification means such as an indicator lamp.

[0019] The communication IF 14 includes hardware for communicating with external devices. Communication standards for the communication IF 14 include Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The label printer 1 may be equipped with multiple communication IFs 14 that support multiple communication standards. As shown in FIG. 1 , the label printer 1 can connect to the Internet 40 via the communication IFs 14, and can communicate with various devices connected to the Internet 40, such as a PC 100 or a cloud server 200.

[0020] The printing unit 15 includes components for printing images on a long print medium that will become a label. Because the label printer 1 prints on a continuous tape-like print medium having a predetermined width and transports the print medium, the printing unit 15 includes a print engine 51 that prints, various transport rollers 52 that transport the print medium, and a cutter 53 that cuts the print medium after printing. In this embodiment, the print medium is referred to as "tape," and the width of the tape is referred to as the "tape width." The direction in which the tape is transported through the label printer 1 is referred to as the "length direction." The tape is a tape-like substrate with multiple sticker-like labels attached lengthwise to a backing paper. The label printer 1, for example, prints labels while unwinding a built-in roll of tape and then cuts the printed labels from the tape.

[0021] Specifically, as shown in FIG. 4, the label printer 1 is capable of detachably mounting a cassette 54 that stores a roll of tape 50. With the cassette 54 installed, the tape 50 is unwound by a transport roller 52 and printed on by a print engine 51 in parallel. The print engine 51 may be of a thermal type or a thermal transfer type. The label printer 1 is compatible with multiple tape widths and determines the print range depending on the tape 50 that is installed. The printable range in the width direction by the label printer 1 is determined for each tape width by the mechanical configuration of the print engine 51. The print engine 51 is an example of a printing unit.

[0022] The label printer 1 prints on the tape 50 while unwinding it. The printed portion of the tape 50 is then projected outside the machine through the discharge port (see FIG. 1). The label printer 1 has a cutter 53 located near the inside of the discharge port (see FIG. 4), and the label that has projected outside the machine from the remaining tape 50 is cut by the cutter 53. The cutter 53 may also be attached to the outside of the discharge port as an optional unit.

[0023] The PC 100 is capable of communicating with the label printer 1 and the cloud server 200, and can execute various processes. Although not shown in FIG. 1, the PC 100 has a CPU, memory, a user interface, and a communication interface, just like the label printer 1. The PC 100 may be a desktop or mobile computer.

[0024] The PC 100 stores a label creation application 110 that has a function for creating label data, and font data 111 (hereinafter, the font data stored in the PC 100 is referred to as "PC font data"). The PC 100 also stores one or more pieces of PC font data 111, and the PC 100 can support fonts based on the PC font data 111. The fonts supported by the PC 100 may be the same as those of the label printer 1, or may be different. Generally, the PC 100 has a larger memory capacity than the label printer 1, and often stores more font data than the label printer 1. In other words, the PC 100 is likely to support more fonts than the label printer 1.

[0025] Cloud server 200 is capable of communicating with label printer 1 and PC 100 and can execute various processes. Although not shown in Figure 1, cloud server 200 also has a CPU, memory, a user interface, and a communication interface, just like label printer 1 and PC 100.

[0026] Cloud server 200 stores server program 210, which has the function of rasterizing label data to generate print data, and font data 211 (hereinafter, the font data stored in cloud server 200 is referred to as "server font data"). Cloud server 200 also stores one or more sets of server font data 211, and cloud server 200 can support fonts based on server font data 211. The fonts supported by cloud server 200 may be the same as those of label printer 1 or PC 100, or they may be different. Generally, cloud server 200 has a larger memory capacity than label printer 1 or PC 100, and often stores more font data than label printer 1 or PC 100. In other words, cloud server 200 is likely to support more fonts than label printer 1 or PC 100.

[0027] The cloud server 200 can also store one or more pieces of label data 23 created by the label creation application 110. The label data 23 is stored in the cloud server 200 in association with various types of information.

[0028] <Printing procedure on the printing system> Next, we will explain the printing procedure in the printing system 400 of this embodiment. The printing procedure in the printing system 400 of this embodiment includes a preparation procedure that is executed by the user operating the PC 100, and a main procedure that is executed by the user operating the label printer 1.

[0029] <Preparation steps> 5 is a sequence diagram showing the preparation procedure in the printing system 400. Of the preparation procedures, the processes executed by the PC 100 are executed by the CPU of the PC 100. The processes executed by the label printer 1 are executed by the CPU 11 of the label printer 1. The processes executed by the cloud server 200 are executed by the CPU of the cloud server 200.

[0030] In the preparation procedure, first, the PC 100 creates label data 23 (S01). Specifically, the PC 100 starts the label creation application 110, and the label creation application 110 accepts edits from the user on the label data 23 to be printed. The label creation application 110 can use PC font data 111, and fonts compatible with the PC 100 are set in the label data 23 created by the label creation application 110.

[0031] Next, the PC 100 selects a destination for the created label data 23 (S02). Candidate label printers for the destination are registered in the PC 100 in advance, and the PC 100 accepts the selection of the destination label printer from among the registered label printers. When registering a label printer, the PC 100 communicates with the label printer to be registered, obtains the printer name, address information, serial number, specification information, etc. of the label printer to be registered, and registers this information. Once the destination label printer 1 has been selected, the PC 100 further inquires of the selected label printer 1 about available storage numbers, which are storage numbers where no label data is saved, and accepts the selection of one of the available numbers to be used as a storage destination. Once the destination has been selected, it becomes possible to accept a transfer instruction.

[0032] When the PC 100 receives the transfer instruction, it uploads the created label data 23 to the cloud server 200 (S11). In addition to the label data 23, the PC 100 transmits the serial number of the selected transfer destination label printer 1, the selected storage number, and authentication information, in association with the label data 23. The authentication information is information used for authentication when using the label data 23, and may be generated automatically by the label creation application 110 or may be input by the user. The authentication information uploaded to the cloud server 200 in S11 is an example of first authentication information.

[0033] When the cloud server 200 receives the label data 23, it saves the label data 23 and information associated with the label data 23 (S12). That is, the label data 23 created in S01 is stored in the cloud server 200 in association with the manufacturing information, storage number, and authentication information of the label printer selected in S02.

[0034] Furthermore, when the PC 100 receives the transfer instruction, it creates label data 23 by converting the font settings of the created label data 23 to a font that is compatible with the label printer 1 selected as the transfer destination (S21). Information about the fonts that are compatible with the label printer 1 selected as the transfer destination may be obtained when S02 is executed and an available number is obtained from the label printer 1 selected as the transfer destination, or it may be obtained and saved in advance when the label printer 1 is registered with the PC 100. Note that if the font set in the created label data 23 is a font that is compatible with the label printer 1 selected as the transfer destination, S21 may be omitted and the label data 23 created in S01 may be regarded as the label data 23 after conversion in S21.

[0035] The PC 100 then transfers the converted label data 23 to the label printer 1 selected as the transfer destination (S22). In addition to the converted label data 23, the PC 100 also transmits the selected storage number, server access information for accessing the cloud server 200, and authentication information, all associated with the label data 23. The server access information may be, for example, the URL or IP address of the server. If account information for accessing the server is required, the account information may also be included. Note that the transfer destination label printer 1 may already have server access information for accessing the cloud server 200, in which case there is no need to transfer the server access information. The authentication information sent to the label printer 1 is the same as the authentication information transferred to the cloud server 200.

[0036] When the destination label printer 1 receives the converted label data 23 via the communication IF 14, it saves the label data 23 and the information associated with the label data 23 (S23). That is, the label data 23 converted in S21 is stored in the memory area corresponding to the selected storage number, and the server access information and authentication information are stored in the label printer 1 in association with the storage number. S23 is an example of storage processing.

[0037] It should be noted that the uploading of the label data 23 to the cloud server 200 by the PC 100 and the transfer of the label data 23 to the label printer 1 may occur first, or may occur simultaneously.

[0038] Through this preparation procedure, the label data 23 created by the label creation application 110 of the PC 100 is stored in the cloud server 200 and the label printer 1. Specifically, the label data 23 itself created by the label creation application 110 is stored in the cloud server 200. On the other hand, the label printer 1 stores not the label data 23 itself created by the label creation application 110, but label data 23 converted into a font that is compatible with the label printer 1.

[0039] Note that the label data 23 may be converted by the label printer 1 instead of by the PC 100. That is, the PC 100 may send the label data 23 created by the label creation application 110 as is, and if the label printer 1 receives the label data 23 and sets a font that it does not support, it may convert it to a font that it supports. By having the label printer 1 convert the font to one that it supports, the likelihood of the font being converted to an appropriate font increases. On the other hand, as shown in FIG. 5, if the PC 100 converts the font to one that is supported by the label printer 1 beforehand and sends the label data 23, the label printer 1 does not need to convert the font to one that it supports, which reduces the processing load on the label printer 1.

[0040] <Main unit procedure> 6 is a sequence diagram showing the main procedure in the printing system 400. Of the main procedure, the processes executed by the label printer 1 are executed by the CPU 11 of the label printer 1. The processes executed by the cloud server 200 are executed by the CPU of the cloud server 200.

[0041] In the main procedure, the label printer 1 first selects the label data to be printed (S31). Specifically, the label printer 1 accepts a user selection of label data to be printed from the label data 23 stored in the memory 12 via the user IF 13, and selects the accepted label data. S31 is an example of label selection processing.

[0042] Next, the label printer 1 selects whether to perform label printer editing online or offline (S32). Specifically, the label printer 1 accepts a user selection of whether to perform online or offline via the user IF 13. S32 is an example of usage selection processing. If offline is selected, the label printer 1 does not communicate with the cloud server 200, but instead performs offline processing by editing and printing the label data using the label data 23 stored in the memory 12. Details of the offline processing will be described later.

[0043] If online is selected, the label printer 1 edits and prints the label data using the label data 23 stored in the cloud server 200. Then, the label printer 1 uses the server access information associated with the selected label data to send a connection confirmation request to the cloud server 200 via the communication IF 14 (S33). Upon receiving the connection confirmation request, the cloud server 200 responds to the connection confirmation request (S34).

[0044] Alternatively, the label printer 1 may send a login request to the cloud server 200 as a connection confirmation request, and receive the result of the login process as a response to the login request from the cloud server 200. In this case, the label printer 1 may store the information required to log in to the cloud server 200 in advance, or may receive the information from the PC 100 as server access information.

[0045] When the label printer 1 receives a response from the cloud server 200 to the connection confirmation request (Alt: Response received), the label printer 1 sends an authentication request specifying the selected label data to the cloud server 200 via the communication IF 14 (S41). The authentication request is associated with the serial number of the label printer 1 itself, the storage number of the selected label data, and authentication information associated with the selected label data. S41 is an example of authentication request processing. The authentication information sent to the cloud server 200 in S41 is an example of second authentication information.

[0046] Upon receiving the authentication request, the cloud server 200 performs data authentication processing for the specified label data using various information associated with the authentication request (S42). For example, the cloud server 200 determines whether the label data 23 corresponding to the serial number and storage number received from the label printer 1 is stored in the cloud server 200, and if not, responds to the label printer 1 with an authentication failure. On the other hand, if the label data 23 is stored, the cloud server 200 further determines whether the authentication number associated with the stored label data 23 matches the authentication number received from the label printer 1, and if they match, responds to the label printer 1 with an authentication success, or if they do not match, responds to the label printer 1 with an authentication failure. This authentication failure response may be distinguished between when the label data is not stored and when the authentication numbers do not match, or may be the same.

[0047] The cloud server 200 uses the serial number and storage number to check whether or not label data corresponding to the label data selected by the label printer 1 exists, thereby avoiding unnecessary operations on the label printer 1 if the label data does not exist in the cloud server 200. Note that, in addition to the serial number and storage number, the file name of the label data can also be used to check whether or not label data exists.

[0048] Furthermore, even if label data corresponding to the label data selected by the label printer 1 is stored in the cloud server 200, the authentication information can be further used to determine whether or not the label data corresponds to the label data selected by the label printer 1, i.e., whether or not both label data were sent simultaneously from the label creation application 110 in the preparation procedure, thereby reducing the possibility of editing incompatible label data.

[0049] If the cloud server 200 responds that authentication was successful (Alt: Authentication successful), the label printer 1 cooperates with the cloud server 200 and executes online processing that uses the label data stored in the cloud server 200 and that corresponds to the selected label data (S50).

[0050] 7 is a sequence diagram showing the procedure for the online processing of S50. In the online processing, the label printer 1 first displays an edit screen for the selected label data on the LCD display 32 (S501). The label printer 1 uses the printer font data 22 to display text included in the selected label data on the LCD display 32. S501 is an example of label data display processing. Then, with the edit screen displayed, the label printer 1 accepts various operations from the user via the key group 31 (S502).

[0051] Operations that can be accepted in S502 include, for example, key operations related to editing text included in the label data 23, print instructions, and operations to end online processing. A print instruction accepted in online processing is an example of a second print instruction, and S502 accepting a print instruction is an example of print instruction processing. S502 accepting key operations related to editing text is an example of edit operation processing.

[0052] For example, each time a key operation related to editing text is performed (Opt: key operation), the label printer 1 updates the text displayed on the editing screen based on the accepted key operation (S511). When updating the text displayed on the editing screen, the label printer 1 also uses the printer font data 22. S511 is an example of the first update process.

[0053] Furthermore, each time a key operation related to editing text is performed, the label printer 1 sends an update request specifying the selected label data to the cloud server 200 via the communication IF 14 (S512). The update request associates the serial number of the label printer 1 itself, the storage number of the selected label data, and the key code corresponding to the accepted key operation. S512 is an example of the second update process.

[0054] Upon receiving the update request, cloud server 200 reads out the label data 23 stored therein that corresponds to the serial number and storage number received from label printer 1, and updates the text included in that label data based on the received key code (S513). The label data 23 stored in cloud server 200 is set with a font that can be used by PC 100, so the font is not updated even when the text is updated. After updating the text, cloud server 200 sends a response to the update request to label printer 1 (S514).

[0055] When the label printer 1 receives a response to the update request from the cloud server 200 via the communication IF 14, it updates the text included in the selected label data 23 stored in the memory 12 based on the accepted key operation (S515). As a result, both the label data 23 in the label printer 1 and the label data 23 in the cloud server 200 are updated based on a single key operation on the label printer 1.

[0056] Furthermore, for example, when a print instruction is received (Opt: print instruction), the label printer 1 sends a raster request specifying the selected label data to the cloud server 200 via the communication IF 14 (S521). The raster request associates the serial number of the label printer 1 itself with the storage number of the selected label data. S521 is an example of transmission request processing.

[0057] Upon receiving the raster request, cloud server 200 reads out the label data 23 stored therein that corresponds to the serial number and storage number received from label printer 1, and generates print data rasterized based on that label data using server font data 211 (S522). The print data generated in S522 is an example of second print data. Rasterization in cloud server 200 uses server font data 211 stored in cloud server 200. Because cloud server 200 is likely to be able to use fonts available on PC 100, it is likely that it will be able to generate print data drawn using that font, even for label data set with a font available on PC 100. After generating the print data, cloud server 200 sends the print data generated in S522 to label printer 1 as a response to the raster request (S523).

[0058] When the label printer 1 receives print data from the cloud server 200 via the communication IF 14 as a response to the raster request, it uses the print engine 51 to print based on the print data (S524). This makes it possible for the label printer 1 to print an image with text written in a font that is usable by the PC 100. S524 is an example of the second print process.

[0059] Furthermore, for example, when an operation to end online processing is performed (Opt: end operation), the label printer 1 ends the online processing. When an operation to end the online processing is performed, the label printer 1 may instruct the cloud server 200 to log out, etc.

[0060] Returning to the explanation of Figure 6, if there is a response from the cloud server 200 indicating authentication failure (Alt: authentication failed), or if there is no response from the cloud server 200 indicating authentication success and a timeout occurs, the label printer 1 does not communicate with the cloud server 200, but instead performs offline processing using the label data 23 stored in the memory 12 (S60).

[0061] 8 is a flowchart showing the procedure for offline processing in S60. In offline processing, the label printer 1 first displays an edit screen for the selected label data on the LCD display 32 (S601). The label printer 1 displays the text included in the selected label data on the LCD display 32 using the printer font data 22. Then, with the edit screen displayed, the label printer 1 accepts various operations from the user via the key group 31 (S602).

[0062] Like S502, the possible operations accepted in S602 include key operations related to editing the text included in the label data 23, print instructions, and operations to end offline processing. The print instruction accepted in S602 is an example of a first print instruction, and S602 accepting a print instruction is an example of print instruction processing.

[0063] For example, if the operation accepted in S602 is a key operation related to editing text (S611: YES), the label printer 1 updates the text displayed on the editing screen based on the accepted key operation (S612). When updating the text displayed on the editing screen, the label printer 1 also uses the printer font data 22.

[0064] In offline processing, when a key operation is performed, the text on the editing screen is updated, but the label data 23 stored in the memory 12 is not updated. In other words, when the label data 23 stored in the label printer 1 is updated in offline processing, the text content will no longer match the label data 23 stored in the cloud server 200. Therefore, when a key operation is performed, the updated text content is temporarily stored, and the editing screen is displayed or printed using this temporarily stored text, without updating the label data 23 itself.

[0065] Furthermore, if the operation accepted in S602 is not a key operation (S611: NO) but a print instruction (S621: YES), the label printer 1 determines whether the font set in the selected label data 23 is compatible (S622), and if it is not compatible (S622: NO), it uses the printer font data 22 to convert the font set in the selected label data 23 into a font that is compatible with the label printer 1 (S623).

[0066] After the font has been converted in S623, or if a compatible font has been set (S622: YES), the label printer 1 uses the printer font data 22 to rasterize the selected label data 23 to generate print data (S624). The print data generated in S624 is an example of first print data. The label printer 1 then performs printing based on the generated print data using the print engine 51 (S625). As a result, even when offline, an image with text written in a font that can be used by the PC 100 is printed. S624 and S625 are an example of the first print process.

[0067] If the operation accepted in S602 is not a key operation (S611: NO), not a print instruction (S621: NO), but an end operation (S631: YES), the label printer 1 ends the offline processing. If the operation is not an end operation (S631: NO), the label printer 1 executes other processing corresponding to the accepted instruction (S641).

[0068] If the cloud server 200 responds that authentication has failed, the label printer 1 cannot receive the print data rasterized by the cloud server 200. Therefore, the label printer 1 executes offline processing, rasterizes the label data 23 stored in the memory 12 using the printer font data 22, and performs printing based on the print data generated by that rasterization, thereby avoiding a situation in which the selected label data cannot be printed.

[0069] After receiving a response from the cloud server 200 indicating authentication failure, and before executing the offline processing of S60, the label printer 1 may inquire of the user via the user IF 13 whether or not to continue the processing. If the user selects to continue the processing, the offline processing of S60 may be executed. However, if the user selects not to continue the processing, the main procedure may be terminated without executing the offline processing of S60.

[0070] Furthermore, when printing is performed offline, the printing is not based on print data rasterized by the cloud server 200, so there is a possibility that the text will be printed in a font different from the font set in the label creation application 110 of the PC 100. Therefore, when printing is performed offline after authentication has failed, the label printer 1 may notify the user via the user IF 13 that printing has been performed offline or that printing has been performed in a font that the label printer 1 can support.

[0071] Returning to the explanation of Figure 6, even if there is no response from the cloud server 200 to the connection confirmation request in S33 (Alt: No response), the label printer 1 executes offline processing (S61), in the same way as when there is a response from the cloud server 200 that authentication has failed. The offline processing in S61 is the same as the offline processing in S60. Alternatively, the user is queried via the user IF 13 as to whether or not to continue processing, and if a selection to continue processing is accepted, the offline processing in S61 is executed. Even if printing is performed through offline processing because there is no response from the cloud server 200, the user may be notified via the user IF 13 that printing has been performed offline, or that printing has been performed with a font that is compatible with the label printer 1, in the same way as when there is a response from the cloud server 200 that authentication has failed.

[0072] If communication with the cloud server 200 is not possible, the print data rasterized by the cloud server 200 cannot be received. Therefore, the label printer 1 can avoid a situation where the specified label data cannot be printed by performing offline processing and printing using the printer font data 22.

[0073] Furthermore, if the user selects offline in S32, the label printer 1 executes offline processing in the same manner as when an authentication failure response is received from the cloud server 200. This allows the specified label data to be printed even in an offline environment.

[0074] As described above in detail, the label creation application 110 of the PC 100 sends the label data 23 to both the cloud server 200 and the label printer 1. When a print instruction is received with offline selected, the label printer 1 uses the printer font data 22 stored in its own memory 12 to print based on print data obtained by rasterizing the label data 23 stored in its own memory 12. This allows printing based on the label data 23 to be performed offline. On the other hand, when a print instruction is received with online selected, the label printer 1 receives print data from the cloud server 200 that is obtained by rasterizing the label data 23 stored in the cloud server 200 using the server font data 211 stored in the cloud server 200, and prints the print data. As a result, even if a font that cannot be supported by the label printer 1 is set in the label data 23 created by the label creation application 110 of the PC 100, if the cloud server 200 has server font data 211 that corresponds to that font, the text will be printed in that font.

[0075] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the present invention can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the device having the label creation application 110 is not limited to a PC, but may also be a smartphone.

[0076] Furthermore, in the embodiment, if there is no response from the cloud server 200 to the connection confirmation request (Alt: no response), the label printer 1 executes offline processing, but may not execute the offline processing, but may instead report an error via the user IF 13 and terminate the main procedure. Similarly, if there is a response from the cloud server 200 indicating authentication failure (Alt: authentication failed), the label printer 1 may not execute offline processing, but may instead report an error via the user IF 13 and terminate the main procedure.

[0077] Furthermore, in the embodiment, during online processing, each time a key operation is performed on the label printer 1, both the label data 23 on the label printer 1 and the label data 23 on the cloud server 200 that corresponds to that label data 23 are updated, but the timing of updates is not limited to this. For example, it is also possible to accept update instructions in addition to key operations, and to update the display on the editing screen in response to a key operation but not send an update request to the cloud server 200, by temporarily storing information indicating all key operations performed up until the update instruction is received, and then, at the timing of the update instruction, to send an update request specifying the selected label data to the cloud server 200 in association with the information indicating the key operations that had been stored up until then, and update the label data 23 stored on the cloud server 200 based on the update request.

[0078] In the embodiment, an authentication request is made when online is selected, but is not made when a key operation or a print instruction is given. However, an authentication request may be made when a key operation or a print instruction is given. Furthermore, if an authentication failure is received, an update request or raster request may not be sent.

[0079] Furthermore, in the embodiment, the same authentication information is sent from the PC 100 to both the label printer 1 and the cloud server 200, but it may be configured to send authentication information to the cloud server 200 but not to the label printer 1. In this case, when the label printer 1 sends an authentication request, it requests the user to input authentication information via the user IF 13, and associates the input authentication information with the authentication request.

[0080] Also, in the embodiment, when online is selected, a connection check and an authentication request with the cloud server 200 are made, and then printing is performed in response to receiving a print instruction, but a raster request may be sent without making a connection check or an authentication request.

[0081] Furthermore, in the embodiment, after selecting label data, the user is prompted to select whether to operate online or offline, but this selection does not have to be made by the user. For example, the label printer 1 may periodically check the connection with the cloud server 200 and automatically select whether to operate online when connected to the cloud server 200 or offline when not connected. Alternatively, for example, the label printer 1 may receive a print instruction without receiving a selection of online or offline when one piece of label data has been selected. When a print instruction is received, the label printer 1 first checks the connection with the cloud server 200, and if communication is possible, executes online processing (S50), and if communication is not possible, executes offline processing (S60). In this case, since label data has been selected, an authentication request may be made in addition to a connection check.

[0082] Furthermore, in any flowchart disclosed in the embodiments, the execution order of multiple processes in any multiple steps can be changed or they can be executed in parallel as long as no contradiction occurs in the processing content.

[0083] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processes disclosed in the embodiments may be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method. [Explanation of symbols]

[0084] 1 label printer 22 Printer font data 23 Label Data 100 PC 110 Label Creation App 111 PC font data 200 cloud servers 211 Server font data 400 Printing System

Claims

1. A printing department; a communication interface; A user interface; a memory capable of storing font data and label data; A controller; A label printer comprising: The controller receiving label data transmitted from an information processing device via the communication interface and executing a storage process to store the received label data in the memory, the label data being transmitted from the information processing device to the label printer and the server; The controller further comprises: a label selection process for accepting, via the user interface, a selection of one of the label data stored in the memory; a print instruction process for receiving a print instruction via the user interface when one of the label data stored in the memory is selected; the print instruction includes a first print instruction and a second print instruction, The controller further comprises: If the received print instruction is the first print instruction, a first print process is executed in which the selected label data is rasterized using the font data stored in the memory to generate first print data, and printing is performed based on the generated first print data using the printing unit; executes a transmission request process to transmit a transmission request specifying the selected label data to the server via the communication interface if the received print instruction is the second print instruction; The controller further comprises: When second print data is received from the server via the communication interface in response to the transmission request, the second print process executes a second print process using the printing unit to print based on the received second print data, in which the label data stored in the server and corresponding to the label data specified in the transmission request is rasterized by the server. A label printer configured to:

2. 2. The label printer according to claim 1, The controller If communication with the server is not possible, the second printing process is not executed, and the first printing process is executed. A label printer configured to:

3. 2. The label printer according to claim 1, The controller If the label data corresponding to the selected label data is not stored in the server, the second printing process is not executed, and the first printing process is executed. A label printer configured to:

4. 2. The label printer according to claim 1, The controller executes a usage selection process for accepting a selection of whether the selected label data is to be used online or offline; In the print instruction process, if the selection is made to go offline, the first print instruction is accepted as the print instruction, and if the selection is made to go online, the second print instruction is accepted as the print instruction. A label printer configured to:

5. 5. The label printer according to claim 4, The controller With one of the label data stored in the memory selected, a label data display process for displaying text included in the label data selected via the user interface using the font data stored in the memory; an editing operation process for accepting an editing operation for editing the text included in the selected label data; Run The controller further comprises: When the editing operation is accepted after the selection to go online, a first updating process for updating the text included in the selected label data, which is displayed via the user interface, based on the accepted editing operation, using the font data stored in the memory; a second update process in which an update request specifying the selected label data is sent to the server via the communication interface in association with an operation command corresponding to the accepted editing operation, and the server updates, based on the operation command, the text included in the label data stored in the server that corresponds to the label data specified in the update request; To execute A label printer configured to:

6. 6. The label printer according to claim 5, The controller In the editing operation process, a key operation for each character of editable text is accepted as the editing operation via the user interface; The controller further comprises: When the key operation for each character is accepted in the editing operation process, In the first updating process, based on the received key operation for one character, text included in the selected label data and displayed via the user interface is updated using the font data stored in the memory; In the second update process, the update request specifying the selected label data is transmitted to the server via the communication interface in association with a key code corresponding to the received key operation for one character, and the server is caused to update, based on the key code, the text included in the label data stored in the server that corresponds to the label data specified in the update request. A label printer configured to:

7. 6. The label printer according to claim 5, When transmitting the label data to the server, the information processing device associates first authentication information with the label data and transmits the label data; The controller after one of the label data stored in the memory is selected and the selection to go online is made, and before the editing operation is accepted, an authentication request process is executed to send to the server via the communication interface an authentication request specifying the selected label data, the authentication request including second authentication information associated with the selected label data; The controller permitting acceptance of the editing operation when a successful authentication result indicating that the first authentication information associated with the label data corresponding to the label data specified in the authentication request among the label data stored in the server matches the second authentication information attached to the authentication request is received from the server via the communication interface as a response to the authentication request, and restricting acceptance of the editing operation when the successful authentication result is not received. A label printer configured to:

8. A printing department; a communication interface; A user interface; a memory capable of storing font data and label data; A controller; A label printer comprising: The controller receiving label data transmitted from an information processing device via the communication interface and executing a storage process to store the received label data in the memory, the label data being transmitted from the information processing device to the label printer and the server; The controller further comprises: a label selection process for accepting, via the user interface, a selection of one of the label data stored in the memory; a print instruction process for receiving a print instruction via the user interface when one of the label data stored in the memory is selected; Run The controller further comprises: When the print instruction is received, If communication with the server is possible, a transmission request specifying the selected label data is transmitted to the server via the communication interface; When the server receives, via the communication interface in response to the transmission request, print data in which the label data stored in the server and corresponding to the label data specified in the transmission request has been rasterized by the server, the printer uses the printing unit to print based on the received print data, If communication with the server is not possible, the selected label data is rasterized using the font data stored in the memory to generate print data, and printing is performed based on the generated print data using the printing unit. A label printer configured to:

9. A printing system including an information processing device on which a program having a function for creating label data is installed, a label printer, and a server, The program is configured to: a label data creation process for creating label data; a label data transmission process for transmitting the label data created in the label data creation process to the server and the label printer; Execute The server storing the label data transmitted from the information processing device in a memory of the server; The label printer storing the label data transmitted from the information processing device in a memory of the label printer; accepting, via a user interface of the label printer, a selection of one of the label data stored in the memory of the label printer; a print instruction is received via the user interface of the label printer with one of the label data stored in the memory of the label printer selected, the print instruction including a first print instruction and a second print instruction; if the received print instruction is the first print instruction, rasterize the selected label data using font data stored in the memory of the label printer to generate first print data, and perform printing based on the generated first print data using a printing unit of the label printer; If the received print instruction is the second print instruction, a transmission request specifying the selected label data is sent to the server; The server When the transmission request is received from the label printer, the server generates second print data by rasterizing the label data stored in the memory of the server that corresponds to the label data specified in the transmission request, and transmits the generated second print data to the label printer. The label printer When the second print data is received from the server in response to the transmission request, printing is performed based on the received second print data using the printing unit. A printing system configured to:

10. 10. A printing system according to claim 9, In the label data transmission process of the program, If the label data to be transmitted contains a font that cannot be supported by the label printer, the font set in the label data is converted to a font that can be supported by the label printer, the converted label data is sent to the label printer, and the unconverted label data is sent to the server. A printing system configured to:

11. 10. A printing system according to claim 9, The label printer When the first print instruction is accepted, if a font that cannot be supported by the label printer is set in the selected label data, the font set in the label data is converted to a font that corresponds to the font data stored in the label printer, and printing is performed using a printing unit of the label printer. A printing system configured to:

Images