Program, information processing device, and label data sharing system

Abstract

To provide a technique for facilitating posting of label data in a system for utilizing label data.SOLUTION: A client application 13 causes, when receiving an instruction to execute printing of label data 15, a label printer 11 to perform printing based on the label data 15. The client application 13 calculates estimated time required for completing the printing of the label data 15. When the printing time exceeds a threshold, the client application 13 proposes posting of the label data 15 using a terminal 12. The client application 13 uploads, when receiving an instruction to upload the label data 15 to be printed, the label data 15 to a label management server 22.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The technical field disclosed in this specification relates to a program, an information processing device, and a label data sharing system used in a system that utilizes label data. [Background technology]

[0002] Conventionally, a system for utilizing content data is known in which a server for storing content data is provided on the Internet, content data is posted from a user's device, i.e., uploaded to the server, and the content data is then downloaded to another user's device.

[0003] An example of a document disclosing the above-mentioned system is Patent Document 1. In the point management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and purchased by User B's PC and downloaded from the WWW server, points are added to User B, the purchaser, according to the purchase amount, and further points are added to User A, the contributor, according to the data size of the photo data when the photo data is uploaded or downloaded. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-99746 A Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, a system has been considered in which a user who has created label data used to print labels with a label printer can upload the label data to a server, and another user can download and use the label data from the server. In such a system, it is desired that many users post label data, but for the user who created the label data, printing the label data and using the printed labels takes priority, and there are cases where the user does not post the data. Patent Document 1 describes having the user select the photo data to be posted, but does not describe any measures to encourage the posting of content such as photo data, so there is room for improvement. [Means for solving the problem]

[0006] The program devised to solve the above-mentioned problems is a program executable by a computer of an information processing device, and is configured to cause the computer to execute a print process that causes a label printer to print based on the label data, when an instruction to print label data is received, and a calculation process that calculates a predicted time until printing of the label data is completed, and to further cause the computer to execute a proposal process that suggests posting of the label data, if the predicted time calculated in the calculation process exceeds a threshold time, and to further cause the computer to execute an upload process that uploads the label data to a server, when an instruction to upload the label data is received after executing the proposal process.

[0007] When causing a label printer to print label data stored in an information processing device, such as label data created by a user, the program having the above configuration calculates a predicted time required to print the label data. If the predicted time exceeds a threshold time, i.e., if it looks like it will take a long time to complete printing, the program suggests posting the label data to be printed via the information processing device. This is expected to encourage users to post the label data while they are waiting for printing of the label data to complete.

[0008] An information processing device for implementing the functions of the above device, a label data sharing system, a control method, and a computer-readable storage medium storing the computer program are also novel and useful. Effect of the Invention

[0009] According to the technology disclosed in this specification, a technology is realized that promotes the posting of label data in a system that aims to utilize label data. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram illustrating a label data sharing system. [Diagram 2] FIG. 2 is an explanatory diagram showing an example of a user database and a label database. [Diagram 3] FIG. 11 is a diagram illustrating an example of a screen transition. [Figure 4] FIG. 11 is a sequence diagram showing an example of a procedure of a normal posting process. [Diagram 5] FIG. 11 is a sequence diagram illustrating an example of a procedure of a printing process. [Figure 6] FIG. 11 is a diagram illustrating an example of a screen transition. [Figure 7] 13 is a flowchart illustrating an example of a procedure for a post recommendation process. [Figure 8] 10 is a flowchart illustrating an example of a procedure for a print result display process. [Figure 9] FIG. 11 is a sequence diagram illustrating an example of a procedure of a download process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] An embodiment of a label data sharing system will be described in detail with reference to the accompanying drawings. This embodiment discloses a label data sharing system that connects a server and a plurality of information processing devices via a network to share label data used for printing labels with a label printer.

[0012] The label data sharing system (hereinafter abbreviated as "system") 100 of this embodiment shown in FIG. 1 is a system provided to a user by, for example, a label printer vendor. The system 100 comprises a terminal 12 and a label management server 22, which are connected via an Internet line 21. The terminal 12 is a terminal owned by the owner or user (hereinafter referred to as "user") of the label printer. The terminal 12 can be connected to a label printer 11. The label management server 22 is an example of a "server." The Internet line 21 is an example of a "network." Note that only one terminal 12 is shown in FIG. 1, but in reality, many terminals 12 are connected to the label management server 22.

[0013] The label printer 11 is a printing device that includes, for example, a thermal transfer print head and prints on a rolled tape while unwinding it. The label printer 11 prints an image on the stored tape and transports the tape based on, for example, a print job received from the terminal 12, and causes the printed portion to protrude outside the machine. A label having a predetermined label length and label width is created by the tape protruded outside the machine. The label length is the length in the direction in which the label is discharged from the label printer 11. The label width is the length in the direction perpendicular to the label length. The label printer 11 can be used by replacing multiple types of tape corresponding to the model.

[0014] The label printer 11 is connected to the terminal 12 by wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The label printer 11 and the terminal 12 may also be connected by wire using the USB communication standard.

[0015] The label management server 22 is a device having at least a storage function and a communication function. The label management server 22 can execute various functions by executing a server program 221. The label management server 22 has a web server function that provides a web page in response to a request from a terminal 12. The label management server 22 can accept label data posted from a large number of terminals 12 connected via the Internet line 21. The label management server 22 can also store label data created by parties other than users, such as the vendor (manufacturer) of the label printer 11. Thus, a wide variety of label data is stored in the label management server 22. The label management server 22 has a function to transmit label data in response to a request from the terminal 12. Each function will be described later.

[0016] The label management server 22 is connected to a user database (hereinafter referred to as "user DB") 25 and a label database (hereinafter referred to as "label DB") 26. The label management server 22 in this embodiment is connected to the user DB 25 and the label DB 26 via a wired LAN 24. The user DB 25 and the label DB 26 may be included in the label management server 22, or may be included in a server different from the label management server 22. The user DB 25 and the label DB 26 may also be included in different servers.

[0017] As shown in FIG. 2A, the user DB 25 can register a record, for each user who uses the terminal 12, that is made up of a user ID 251, a user name 252, and a password 253.

[0018] The user ID 251 is identification information for identifying a user who can use the system 100, and specifies the user who uses the terminal 12. The user name 252 is the name or nickname of the individual or group (corporation) of the user. The password 253 is a password set by each user stored in the user name 252. In addition, the user DB 25 may register personal information for each user, such as an email address and a telephone number.

[0019] The label DB 26 stores multiple pieces of label data that can be printed by the label printer. The label data may be label data uploaded, i.e., posted, from the terminal 12 to the label management server 22 by a user who uses the label data sharing system 100 of this embodiment (hereinafter referred to as "posted label data"), or may be label data registered in the label management server 22 by the vendor (manufacturer) of the label printer 11.

[0020] 2B, the label DB 26 can register, for each label data, a record consisting of a label ID 261, a user ID (creator) 262, label data 263, supplementary information 264, and a posting date 266. The user ID (creator) 262 may be a user name (creator).

[0021] The label ID 261 is a serial number sequentially assigned to each piece of label data registered in the label management server 22 in the system 100 of this embodiment. The user ID (creator) 262 is the user ID 251 of the user who posted the data using the system 100. The user ID (creator) 262 of label data created by someone other than the user may store the ID of the administrator, the ID of the vendor who created the data, or may be left blank.

[0022] The label data 263 is label data stored in the label management server 22. The label data 263 stores information indicating the configuration of the label indicated by the label data. The information indicating the label configuration includes, for example, the type of object set, parameters set for each object, and the arrangement of each object. The supplemental information 264 stores information supplemented when the label data is registered in the label management server 22. The posting date 266 is information indicating the date when the label data was posted.

[0023] 1, the terminal 12 is an information processing device having a communication function, a storage function, a display function, and an operation function. The terminal 12 in this embodiment is configured by a smartphone, but may also be configured by a tablet or a personal computer.

[0024] In the terminal 12, a communication interface (hereinafter referred to as "communication IF") 123 and a user interface (hereinafter referred to as "user IF") 124 are electrically connected to a controller 120 including a CPU 121 and a memory 122. The terminal 12 is an example of an "information processing device." The CPU 121 is an example of a "computer." The controller 120 may be an example of a "computer." Note that the controller 120 in FIG. 1 is a collective term for hardware and software used to control the terminal 12, and does not necessarily represent a single piece of hardware actually present in the terminal 12.

[0025] The CPU 121 of the terminal 12 executes various processes according to the program read from the memory 122 and based on the user's operation. The memory 122 stores various programs such as a client application program (hereinafter referred to as a "client application") 13. The client application 13 is an example of a "program". The memory 122 can store various data such as label data 15 and login information 16. The memory 122 is also used as a working area when various processes are executed. A buffer provided in the CPU 121 is also an example of a memory. Note that an example of the memory 122 is not limited to a ROM, RAM, HDD, etc. built into the terminal 12, but may be a storage medium that can be read and written by the CPU 121, such as a recording medium such as a CD-ROM, a DVD-ROM, or a USB memory.

[0026] The client application 13 is an application program provided by the vendor of the label printer 11. The client application 13 has a function for creating and editing label data on the terminal 12. The client application 13 has a function for posting, i.e. uploading, the created label data to the label management server 22 while logged in to the label management server 22, and a function for downloading label data from the label management server 22. The client application 13 has a function for storing posted information, which is information indicating that the uploaded label data has been posted, in the uploaded label data.

[0027] The client application 13 has a function for printing the label data 15 using the label printer 11. The client application 13 has a function for suggesting posting of the label data to be printed. Thus, the terminal 12 can be an example of a "first information processing device" and an example of a "second information processing device." Each function of the client application 13 will be described later.

[0028] Next, the operation of the system 100 will be described. Each processing step in this embodiment basically indicates processing by the CPU 121 according to instructions written in programs such as the client application 13. Processing by the CPU 121 also includes hardware control using the API of the OS. In this specification, the operation of each program will be described without a detailed description of the OS. For convenience of explanation, the subject of each process may be the terminal 12 or the label management server 22.

[0029] (Normal posting process) 3 and 4, a normal posting process in which a user opens a posting screen and posts label data will be described. The client application 13 of the terminal 12 saves the label data 15 created via the editing screen in the memory 122. The memory 122 can store multiple pieces of label data, such as label data created by the client application 13 and label data downloaded from the label management server 22.

[0030] For example, when the client application 13 accepts an operation of the server use button 203 displayed on the home screen 200 shown in Fig. 3(A) using the user IF 124 of the terminal 12, the client application 13 connects to the label management server 22 and displays a label search screen 300 shown in Fig. 3(B) on the user IF 124. On the label search screen 300, it is possible to search for label data registered in the label DB 26. On the label search screen 300, label data registered in the label DB 26 and a submit button 323 are displayed.

[0031] When the client application 13 receives an instruction to display the posting screen by operating the posting button 323 (A01), as shown in Fig. 4, it displays a saved label list screen that displays a selectable list of label data stored in the terminal 12. When the client application 13 receives an operation to select one piece of label data to be uploaded from the displayed list of label data (A02), it requests the label management server 22 to display a posting screen (A03). In response to the request, the label management server 22 provides the client application 13 with web page information corresponding to the posting screen (A04). The client application 13 displays the posting screen on the user IF 124 based on the web page information (A05).

[0032] The client application 13 can receive supplemental information about the label data 15 selected as the data to be uploaded via the submission screen 350 (A11).

[0033] For example, a label name input field 353, a label description input field 354, a tape type setting field 355, a usage example photo image setting field 356, and a new post button 361 are displayed on the posting screen 350 shown in FIG. 3(C). A label image 352 of the label data selected in A02 may be displayed on the posting screen 350. The label name indicating the name of the label data 15, the label description, the model number of the tape suitable for printing the label, and the photo image indicating the usage example of the label are input in the label name input field 353, the label description input field 354, the tape type setting field 355, and the usage example photo image setting field 356, and the client application 13 accepts the input label name and the like as supplementary information of the label data 15 selected in A02. The supplementary information is displayed, for example, on the label search screen 300, and helps the user select a download target. The supplementary information is not limited to this embodiment.

[0034] 4, when the new post button 361 on the posting screen 350 is operated, the client application 13 accepts an upload instruction (A12) and uploads the label data selected in A02 to the label management server 22 (A13). This upload instruction includes the user ID included in the login information 16 stored in the memory 122, the label data 15 selected in A02, and the supplemental information entered on the posting screen 350.

[0035] The label management server 22 stores the received label data 15 in the label DB 26 (A14). Specifically, the label management server 22 creates a new label ID "ddd1" and stores it as a new label ID 261 in the label DB 26 of Fig. 2(B). The label management server 22 stores the received user ID, label data 15, and supplemental information in the user ID (creator) 262, label data 263, and supplemental information 264 of the record corresponding to the new label ID 261, respectively.

[0036] When the registration of the posted label data is completed, the label management server 22 notifies the terminal 12 of the completion of registration (A15). The client application 13 stores the posted information in the posted label data 15 and updates it (A16). The client application 13 also causes the terminal 12 to display a message indicating that the registration of the posted label data 15 is completed (A17). This allows the user to know that the posting is completed.

[0037] In addition, the label data 15 in which the posted information is stored may be made unselectable in the next and subsequent A02 in order to avoid duplicate posting. Methods for making it unselectable include not displaying it on the saved label list screen, or displaying it as unselectable. Examples of methods for displaying it as unselectable include displaying it in a grayed-out state, or displaying it normally but not accepting a selection operation.

[0038] (About printing process) Generally, posted label data is often printed before being posted. There is a print wait time between when the client application 13 accepts a print instruction and when the label printer 11 completes printing. Meanwhile, it is desirable for as much label data as possible to be registered in the label management server 22. Therefore, the client application 13 of this embodiment proposes, via the terminal 12, that the label data to be printed be posted to the label management server 22 by utilizing the print wait time. Here, an example will be described in which user A causes the label printer 11A to print label data 15A being edited on the terminal 12A. The terminal 12A is an example of a "first information processing device."

[0039] As shown in Fig. 5, the client application 13A of the terminal 12A accepts editing of the label data 15A on, for example, an editing screen 750 shown in Fig. 6(A) (C01). In this embodiment, the label data 15A is newly created label data. Note that the client application 13A may read out the label data stored in the terminal 12A and accept the editing.

[0040] An image 751 of the label data 15A being edited is displayed on the editing screen 750. Function selection buttons for selecting functions are displayed in a selectable manner on the editing screen 750. The function selection buttons include, for example, a print setting button 753 that accepts an instruction to make print settings, a print button 754 that accepts a print instruction, and a save button 755 that accepts a save instruction to save the label data. The function selection buttons may also include an object setting button for setting objects and a text editing button for editing text.

[0041] 5, the client application 13A accepts a print instruction to print the label data 15A being edited by operating the print button 754 (C02). Having accepted the print instruction, the client application 13A sends a print command to the label printer 11A selected in the print settings to instruct printing (C03). The client application 13A selects the label data 15A being edited as the object to be printed, and attaches the label data 15A to the print command.

[0042] The client application 13A that sent the print command executes a post recommendation process (C04). The post recommendation process is a process that suggests posting the label data 15 to be printed to the label management server 22. The post recommendation process will be described later.

[0043] When the label printer 11A receives the print command output from the terminal 12A, it prints the label data 15A attached to the print command (C11). The label printer 11A sends the print results to the client application 13A. The print results are sent whether printing was successful or unsuccessful.

[0044] If printing is successful, the label printer 11A sends the print results when printing is completed, and if printing is unsuccessful, the label printer 11A sends the print results when it detects an error (C12). There are various causes of errors. Therefore, for example, if the resolution specified in the label data to be printed is not compatible with the label printer 11A, the label printer 11A may detect the error before printing begins and send the print results. On the other hand, for example, if the tape runs out during printing, the label printer 11A will detect the error after printing has begun and send the print results.

[0045] When the client application 13A receives the print result using the communication IF 123A of the terminal 12A, it performs a print result display process (C13). The print result display process is a process for displaying the print result in response to the print command on the terminal 12A. The print result display process will be described later.

[0046] (About post recommendation processing) The post recommendation process will be described with reference to Fig. 7. The CPU 121A of the terminal 12A executes the post recommendation process shown in Fig. 7 upon transmission of a print command, i.e., upon start of the print process. The CPU 121A first determines whether the label data 15A to be printed stores posted information (S10). If the CPU 121A determines that the label data 15A to be printed stores posted information (S10: YES), it ends the post recommendation process without suggesting posting of the label data 15A to be printed. This prevents duplicate posting of label data.

[0047] When the CPU 121A determines that the label data to be printed does not store posted information (S10: NO), it waits for the waiting time to elapse (S11). The waiting time is set to a time shorter than a threshold time that is a criterion for determining whether or not to display a posted recommendation screen in a posted recommendation process described later. For example, when the threshold time is one minute, the waiting time is 15 to 20 seconds.

[0048] After the waiting time has elapsed, the CPU 121A determines whether a print result indicating a print failure has been received within the waiting time (S12). If the CPU 121A receives a print result indicating a print failure within the waiting time (S12: YES), the CPU 121A ends the post recommendation process without suggesting posting of the label data 15A to be printed. For example, after receiving a print command, the label printer 11A may detect an error before starting printing and immediately notify the client application 13A of the print failure. This is because it is undesirable for label data with such inappropriate settings to be posted to the label management server 22.

[0049] If the CPU 121A does not receive a print result indicating a print failure within the waiting time (S12: NO), it calculates the printing time required to complete printing of the label data 15A to be printed (S13). S13 is an example of a "calculation process".

[0050] The client application 13A of this embodiment calculates the predicted time based on the number of prints, the label length, and the print speed of the label printer 11A. Specifically, the client application 13A estimates the exact print speed by the number of prints x label length / print speed of the label printer. The print speed of the label printer 11A may be calculated by the client application 13A acquiring the capabilities of the label printer 11A. The print speed of the label printer 11A may be acquired by reading the print speed corresponding to the model of the label printer 11A from a print speed previously stored for each model that the client application 13A can support. The number of prints is set at the time of print setting and is acquired from the print job. The label length can be acquired, for example, by the client application 13A calculating it based on the configuration of the label data 15A to be printed. The label length may be acquired from the label data 15A, for example, if the client application 13A calculates the label length when saving or editing the label data and stores it in the label data 15A.

[0051] The predicted time need not be calculated precisely as long as it is possible to determine whether the printing time is long or short. At least one of the parameters such as the number of sheets to be printed, the length of the label, and the printing speed may be used to calculate the predicted time. In addition, CPU 121A may obtain status information from label printer 11A, and when label printer 11A is printing another label data, the time until that printing is completed may be taken into consideration.

[0052] The CPU 121A determines whether the predicted time calculated in S13 exceeds a threshold time (S14). The threshold time is preferably a time corresponding to the time required to post label data, that is, the time required to input predetermined items into the posting screen 350, for example.

[0053] If the predicted time is equal to or less than the threshold time (S14: NO), the CPU 121A ends the post recommendation process without suggesting posting of the label data 15A to be printed, because this goes against the purpose of posting using the printing wait time.

[0054] If the predicted time exceeds the threshold time (S14: NO), the CPU 121A causes the user IF 124A of the terminal 12A to display a posting recommendation screen that suggests posting of the label data 15A to be printed (S15). S15 is an example of a "suggestion process".

[0055] For example, the posting recommendation screen 511 shown in FIG. 6(B) includes a suggestion section 512, an OK button 514, and a cancel button 515. The suggestion section 512 displays, for example, a message suggesting posting of label data to be printed. The OK button 514 is an operation object that receives an instruction to approve the posting. The OK button 514 is associated with the URL of the posting screen 350. The cancel button 515 is an operation object that receives an instruction to not approve the posting.

[0056] As shown in Fig. 7, after displaying the post recommendation screen, CPU 121A determines whether or not there is permission to post (S16). For example, if user A does not have time to wait for printing and wants to post later, he / she operates cancel button 515. When CPU 121A receives the operation of cancel button 515, it determines that there is no permission to post (S16: NO). In this case, CPU 121A closes post recommendation screen 511 (S23) and ends the post recommendation process without displaying the post screen. This causes terminal 12A to return to the edit screen.

[0057] In response to this, when the CPU 121A receives an operation of the OK button 514, it determines that the posting is permitted (S16: YES). In this case, the CPU 121A closes the posting recommendation screen 511 (S17), and displays the posting screen 350x on the user IF 124A of the terminal 12A (S18), as shown in FIG. 6(C). The method of displaying the posting screen 350x is similar to A03 to A05 in FIG. 4. Note that the posting screen 350x displayed via the posting recommendation screen 511 is displayed in a state in which the label data 15A to be printed is selected, without performing the process of A02 shown in FIG. 4, since the label data to be posted is determined to be the label data 400x. In this case, the image 352x of the label data 15A is displayed on the posting screen 350x. S18 is an example of a "screen display process".

[0058] The CPU 121A, which has displayed the posting screen 350x, determines whether an upload instruction has been received (S19). The CPU 121A waits until an upload instruction is received (S19: NO). If the CPU 121A receives an operation of the New post button 361 displayed on the posting screen 350x, it determines that an upload instruction has been received (S19: YES). In this case, the CPU 121A uploads the label data 15A to be printed to the label management server 22 (S20). The upload method is the same as A13 in FIG. 4. S20 is an example of an "upload process".

[0059] When uploading of the label data 15A is completed, the CPU 121A stores and updates the posted information in the label data 15 to be printed (S21). The CPU 121A closes the posting screen 350x (S22) and ends the posting recommendation process.

[0060] (About the print result display process) Next, the above-mentioned print result display process will be described. Upon receiving the print result, the CPU 121A of the terminal 12A executes the print result display process shown in Fig. 8. The CPU 121A determines whether or not a print result indicating a print failure has been received within the standby time (S31).

[0061] If the CPU 121A does not receive a print result indicating a print failure within the waiting time (S31: NO), it determines whether or not the posting screen 350x is being displayed in the posting recommendation process (S32). If the CPU 121A is displaying the posting screen 350x in the posting recommendation process (S32: YES), it determines whether or not the display of the posting screen 350x has ended (S33). The CPU 121A waits until the display of the posting screen 350x has ended (S33: NO).

[0062] When the CPU 121A determines that the display of the posting screen 350x has ended (S33: YES), it causes the user IF 124A to display the print result (S34), and ends the print result display process. That is, even if the client application 13A receives a print result indicating successful printing, the client application 13A does not display the print result while the posting screen 350x is displayed. S34 is an example of the "result display process."

[0063] For example, the CPU 121A causes the user IF 124A to display a print result display screen 501 shown in Fig. 6(D). A message 502 notifying whether printing has been successful or not is displayed on the print result display screen 501, and an OK button 504 is also displayed. This avoids the inconvenience of a screen unrelated to posting being displayed on the terminal 12A during a posting operation.

[0064] On the other hand, if the CPU 121A receives a print result indicating a print failure within the waiting time (S31: YES), the CPU 121A immediately displays the print result indicating a print failure on the user IF 124A (S34) and ends the print result display process. By displaying an error in response to an error occurrence, it is expected that there will be no need to wait for printing.

[0065] When displaying the print result based on a print failure in S34, the cause of the print failure and a method for solving the error may be displayed in addition to the print failure message.

[0066] (Download process) The process of downloading posted label data will be described with reference to FIG. 9. In the system 100, many terminals 12 are connected to the label management server 22, and many label data are registered in the label management server 22. Here, an example will be described in which user B uses terminal 12B, one of the many terminals 12, to download posted label data 15A posted by user A. For ease of explanation, the suffix "B" is added to the reference characters of users, terminals, and their components. Terminal 12B is an example of a "second information processing device." Note that the download target may be label data registered by a party other than the user, such as a label printer vendor.

[0067] For example, the client application 13B of the terminal 12B accepts a server usage instruction by operating the server usage button 203 on the edit screen (B01). When the client application 13B sends a usage request to the label management server 22 (B02), the label management server 22 sends web page information corresponding to the label search screen 300 to the client application 13B (B03). The client application 13B displays the label search screen 300 on the user IF 124B of the terminal 12B based on the web page information (B04).

[0068] For example, when the client application 13B receives an operation to select an image or thumbnail image corresponding to the posted label data 15A from among a plurality of image or thumbnail images displayed on the label search screen 300 shown in Fig. 3(B), the client application 13B receives the selection of the posted label data 15A as a download target (B20). B20 is an example of a "selection process."

[0069] When the client application 13B accepts the selection of the download target, it causes the user IF 124B to display a download screen provided by the label management server 22 (B21). The download screen includes a download execution button. In response to the operation of the download execution button, the client application 13B accepts a download instruction to instruct transmission of the posted label data 15A selected as the download target (B22). The client application 13B transmits the download instruction to the label management server 22 (B23).

[0070] The image displayed on the label search screen is associated with the label ID of the corresponding label data. For example, the image showing the posted label data 15A is associated with the label ID "ddd1" of the posted label data 15A. When the label management server 22 receives the download instruction, it accesses the label DB 26 and reads out the posted label data 15A from the label data 263 of the record including the label ID "ddd1" associated with the image selected in B20 (B24). The label management server 22 transmits the read out posted label data 15A to the terminal 12B (B25).

[0071] The client application 13B of the terminal 12B receives the posted label data 15A using the communication IF 123B and stores it in the memory 122B (B26). The processes of B22 to B26 are an example of a "download process." Note that user B may select multiple label data on the label search screen and download them to the terminal 12B. This allows user B to use the label data 15A uploaded by user A. In other words, the label data 15A is shared.

[0072] As described above, when the client application 13 of this embodiment causes the label printer 11 to print label data 15 stored in the terminal 12, such as label data created by a user, the client application 13 calculates the predicted time required to print the label data 15. If the predicted time exceeds the threshold time, i.e., if it looks like it will take a long time to complete printing, the client application 13 suggests posting the label data 15 to be printed via the terminal 12. This is expected to encourage the user to post the label data 15 while waiting for printing of the label data 15 to be completed.

[0073] It should be noted that the embodiments disclosed in this specification are merely examples and do not limit the present invention in any way. Therefore, the technology disclosed in this specification can be naturally improved and modified in various ways without departing from the scope of the invention. The calculation of the predicted time shown in S13 of FIG. 7 may be performed immediately after the print command is sent and the print process is started. In other words, the calculation of the predicted time may be performed without waiting for the waiting time.

[0074] 5, the client application 13 may receive a print instruction for label data selected from the label data stored in the terminal 12. For example, the client application 13 may open the selected label data on an edit screen or the like and receive a print instruction via the edit screen, or may receive a print instruction without opening the label data. This allows the client application 13 to suggest posting not only the label data being edited, but also the label data stored in the terminal 12 by utilizing the print wait time.

[0075] For example, in the posting recommendation process of FIG. 7, S18 and S28 may be omitted, and if posting is approved (S16: YES), the label data 15 to be printed may be automatically uploaded to the label management server 22 (S20). In this way, if posting is approved, that is, if the label data to be printed is selected as the data to be uploaded, the label data to be printed can be posted immediately without switching to the posting screen, which promotes the posting of label data. In this case, it is preferable that the supplementary information entered on the posting screen is stored in the label DB 26 in association with the label data after uploading. However, if posting is approved (S16: YES), even if the posting screen is displayed before uploading, the effort required for posting is reduced compared to, for example, manually displaying the posting screen 350 on the terminal 12 and uploading the label data as shown in FIG. 4, and the posting of label data is promoted. In addition, by displaying the posting screen 350, it is possible to prevent omissions in inputting supplementary information.

[0076] 4 and S10 in Fig. 7 may be omitted. However, the client application 13 can prevent the label data to be printed from being posted to the label management server 22 in duplicate by storing posted information about the label data that has already been posted.

[0077] 7 may be displayed in a state where the label data to be printed is not selected as the label data to be uploaded. However, the client application 13 causes the terminal 12 to display the posting screen 350x in a state where the label data to be printed is selected as the label data to be uploaded, thereby eliminating the need to select label data when posting label data and promoting the posting of label data.

[0078] 7 only accepts the selection of label data to be uploaded, and does not necessarily have to accept supplemental information. However, supplemental information can be input when posting normal label data, and by accepting supplemental information on the posting screen displayed in S18, the client application 13 can input the supplemental information while waiting for printing. This is expected to encourage more label data to be posted.

[0079] In the print result display process of Fig. 9, the print result may be displayed when it is received, regardless of the elapse of the waiting time or the display of the posting screen. However, when the posting screen is displayed, the user is likely to be working on posting, and may feel annoyed when the print result is displayed. Therefore, if printing is successful, it is preferable for the client application 13 to wait for the posting screen to close before displaying the print result.

[0080] 7, the client application 13 may display the post recommendation screen on the terminal 12 even if a print result of printing failure is received within the waiting time. However, if printing fails, there is a possibility that inappropriate label data will be posted. Therefore, after executing the printing process, the client application 13 waits for the waiting time to elapse before executing the proposal process, and if a print result of printing failure is received before the waiting time elapses, by not displaying the post recommendation screen on the terminal 12, it is possible to prevent inappropriate label data from being posted.

[0081] The label management server 22 may be composed of a front-end server having a web server function and a back-end server having a function other than the web server function. For example, the front-end server may receive download requests and upload requests by using the web server function, while the back-end server may manage the label data.

[0082] For example, the client application 13 may store proposed information indicating that the post has been proposed in the printed label data between S15 and S16 in FIG. 7. The posted information may be stored separately from the label data. In this case, the client application 13 may execute a proposal determination process for determining whether the proposed information is stored between S14 and S15 in FIG. 7, for example, and may proceed to S15 if it is determined that the proposed information is not stored, and may end the post recommendation process if it is determined that the proposed information is stored. This can prevent, for example, the user from operating the cancel button on the post recommendation screen and repeatedly making a proposal to post label data that the user does not want to post. Also, for example, the proposed information may be stored after the process of S17 in FIG. 7 and not stored after the process of S23. In this case, the client application 13 may execute the proposal determination process between S14 and S15 in FIG. 7. This means that, for example, even if a user does not give permission to post due to time constraints, the user can give permission to post again the next time the label data is printed, making it possible to give permission to post at any time.

[0083] In any sequence diagram disclosed in the embodiment, any of a plurality of processes can be executed in a different order or in parallel as long as no contradiction occurs in the process contents.

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

[0085] 11. Label Printer 12 Terminal 21 Internet connection 22 Label Management Server 13 Client Apps 100 Label Data Sharing System 121 CPU 122 Memory

Claims

1. A program executable by a computer of an information processing device, The computer includes: When a print instruction for label data is received, a printing process for causing a label printer to perform printing based on the label data; a calculation process for calculating a predicted time until printing of the label data is completed; Run the command, The computer further comprises: executing a suggestion process for suggesting posting of the label data when the predicted time calculated in the calculation process exceeds a threshold time; The computer further comprises: after the execution of the suggestion process, when an instruction to upload the label data is received, an upload process is executed to upload the label data to a server. A program that is configured to:

2. The program according to claim 1, In the calculation process, The predicted time is calculated based on the number of sheets to be printed, the length of the label, and the printing speed of the label printer. A program that is configured to:

3. The program according to claim 1, The computer includes: a screen display process for displaying a posting screen capable of receiving an instruction to upload the label data; The computer further comprises: When the predicted time calculated in the calculation process exceeds the threshold time, the screen display process is executed. A program that is configured to:

4. The program according to claim 3, The computer includes: executing the screen display process to display the posting screen with the label data selected as an upload target when the predicted time calculated in the calculation process exceeds the threshold time; A program that is configured to:

5. The program according to claim 3, The submission screen can accept input of supplemental information for the label data to be uploaded, In the upload process, When the upload instruction is received with the label data selected as the upload target, the label data is associated with the supplemental information input on the posting screen and uploaded to the server. A program that is configured to:

6. The program according to claim 3, The computer includes: executing a result display process for displaying a message based on the received print result when the print result is received from the label printer after the execution of the print process; The computer further comprises: even if the print result indicating successful printing is received from the label printer, if the posting screen is being displayed by the screen display process, the result display process is executed after waiting for the posting screen to be closed. A program that is configured to:

7. The program according to claim 1, In the proposal process, Accept a selection of whether or not to post the label data for which the printing instruction has been given, The computer includes: when the selection to post the label data is accepted, executing the upload process; A program that is configured to:

8. The program according to claim 1, The computer includes: when an instruction to print the label data is received, after executing the printing process, waiting for a waiting time that is shorter than the threshold time before executing the proposed process; If a print result indicating a printing failure is not received from the label printer before the waiting time has elapsed, the suggested process is executed. if the print result indicating a printing failure is received from the label printer before the waiting time has elapsed, the proposed process is not executed. A program that is configured to:

9. A program according to any one of claims 1 to 8, The computer includes: A selection process for selecting one of the label data registered in the server can be executed, and the server can register the uploaded label data, The computer further comprises: executing a download process for downloading the label data selected in the selection process from the server when a download instruction for the label data selected in the selection process is received; A program that is configured to:

10. An information processing device connectable to a server via a network, The information processing device includes: When a print instruction for label data is received, a printing process for causing a label printer to perform printing based on the label data; a calculation process for calculating a predicted time required for printing the label data; Run The information processing device further comprises: execute a suggestion process for suggesting posting of the label data when the predicted time calculated in the calculation process exceeds a threshold time; The information processing device further comprises: after the execution of the suggestion process, when an upload instruction for the label data is received, an upload process is executed to upload the label data to the server. It is configured as follows.

11. A label data sharing system comprising a first information processing device, a second information processing device, and a server, the first information processing device and the second information processing device being connectable to the server via a network, The first information processing device, When a print instruction for label data is received, a printing process for causing a label printer to perform printing based on the label data; a calculation process for calculating a predicted time required for printing the label data; Run The first information processing device further comprises: execute a suggestion process for suggesting posting of the label data when the predicted time calculated in the calculation process exceeds a threshold time; The first information processing device further comprises: after the execution of the suggestion process, when an upload instruction for the label data is received, an upload process is executed to upload the label data to the server; The server, The label data uploaded to the server can be registered, The second information processing device is When a download instruction for the label data registered in the server is received, a download process is executed to download the label data from the server. A label data sharing system configured to:

Images