Program, information processing apparatus, and system

Abstract

To provide a technique for facilitating posting of label data, in a system for utilizing label data.SOLUTION: A terminal 12 is configured to, through a printer application 14, acquire post condition data prepared by a label management server 22, and search a terminal label database to extract label data that meets the post condition data from the database. When a user performs specific operation, such as printing operation or operation to return to a homepage of a client application, on a user IF 19, the terminal displays the extracted label data 31 on the user IF 19, and suggests posting the extracted label data 31 to the user. The terminal receives an instruction to upload the extracted label data 31, and uploads the extracted label data 31 to the 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 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 creates label data used to print labels with a label printer can upload the label data to a server, and another user can download the label data from the server and use it. In such a system, since it is desired that many users post label data, a means is desired for the system operators to encourage users to post label data. Patent Document 1 describes having users select photo data to post, but does not describe any measures to encourage the posting of content such as photo data, so there is room for improvement.

[0006] The technology disclosed in this specification aims to realize a technology that promotes the posting of label data in a system that aims to utilize label data. [Means for solving the problem]

[0007] The present invention has been made to solve the above-mentioned problems, and provides a program executable by a computer of an information processing device to cause the information processing device to perform a function of accepting edits of label data and a function of saving the label data in the information processing device, the program comprising: The computer includes: A condition acquisition process for acquiring label data solicitation conditions from a server; an extraction process for extracting label data that matches the recruitment conditions acquired in the condition acquisition process from the label data stored in the information processing device; It is possible to execute The computer further comprises: executing a suggestion process for suggesting posting of the label data extracted in the extraction process; The computer further comprises: when an upload instruction for the label data extracted in the extraction process is received, an upload process is executed to upload the label data extracted in the extraction process to the server. The present invention is characterized in that it is configured as follows.

[0008] According to the technology disclosed in this specification, a program executed by an information processing device can obtain solicitation conditions prepared in a server, extract label data that matches the solicitation conditions from among the stored label data, and suggest posting of the extracted label data. This allows the system operator to store the solicitation conditions they wish to solicit in the server, and it is expected that users will be prompted to post label data that meets the solicitation conditions on their information processing devices, and that users will post the label data.

[0009] An information processing device and a system for implementing the functions of the above device are also novel and useful. Effect of the Invention

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

[0011] [Figure 1] FIG. 1 is an explanatory diagram illustrating a label data sharing system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a schematic explanatory diagram showing the electrical configuration of a terminal and a label management server. [Diagram 3] (A) is an explanatory diagram showing an example of user-related information stored in a user database, (B) is an explanatory diagram showing an example of posted label-related information stored in a posted label database, (C) is an explanatory diagram showing an example of content-related information stored in a content database, and (D) is an explanatory diagram showing an example of terminal label-related information stored in a terminal label database. [Figure 4] 11 is a sequence diagram showing an example of a procedure for creating a label to be provided to a user by the operation of a client application of the terminal. FIG. [Diagram 5]FIG. 13 is an explanatory diagram illustrating a terminal when creating a new post label. [Figure 6] FIG. 11 is a sequence diagram showing an example of a procedure for a label data submission solicitation process by a client application of a terminal, including the operation of a label management server program of the label management server. [Figure 7] 1A is an explanatory diagram showing a schematic diagram of a terminal in a state where a search result is displayed, and FIG. 1B is an explanatory diagram showing a schematic diagram of a terminal when content data is posted. [Figure 8] FIG. 11 is a sequence diagram showing an example of a procedure for a label data submission solicitation process by a client application of a terminal, including the operation of a label management server program of the label management server according to the second embodiment. [Figure 9] FIG. 13 is a sequence diagram showing an example of a procedure for a label data submission solicitation process by a client application of a terminal, including the operation of a label management server program of the label management server according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] (First embodiment) An embodiment of a label data sharing system 100 according to the present invention will be described in detail below with reference to the drawings. FIG.

[0013] That is, as shown in Fig. 1, the label data sharing system 100 of this embodiment is a system provided to a user by the vendor (manufacturer) of the printer 11. In the label data sharing system 100 of this embodiment, the owner or user (hereinafter referred to as the user) of the printer 11 can post label data to be printed by the printer 11 from the terminal 12 owned by the user, that is, upload the label data to the label management server 22. In the label data sharing system 100 of this embodiment, the user of the printer 11 can create a label by downloading the label data from the label management server 22 to the terminal 12 owned by the user, and then using the printer 11 connected to the terminal 12 to print based on the label data. The label management server is an example of a server.

[0014] The terminal 12 is configured as a smartphone owned by the user, but may also be configured as a tablet or a personal computer. Various application programs (also called apps) are stored in the terminal 12. For example, a client application 13 provided to the user by the vendor of the printer 11 has a function for creating and editing label data on the terminal 12. The client application 13 also has a function for uploading the created label data to the label management server 22. The terminal is an example of an information processing device.

[0015] The client application 13 also has a function for downloading label data from the label management server 22. The client application 13 also has a function for printing, using the printer 11, label data created on the terminal 12 or downloaded label data. The client application is an example of a program.

[0016] A tape cassette (not shown) is attached to the printer 11, and a long tape (not shown) for printing labels is wound on the tape cassette. The printer 11 also includes a printer application 14 for controlling printing, and a storage unit (not shown) capable of storing a total print volume 15 of the printer. The total print volume 15 as an index representing the proficiency level may be configured by the number of prints made by the printer 11. The total print volume 15 may also be configured by a total length obtained by adding up the print lengths of the long tape made by the printer 11. The total print volume 15 may also be a value that comprehensively evaluates the proficiency level of the user based on the number of prints and the total length.

[0017] The printer 11 may be any printer capable of printing based on label data, and may be an inkjet printer or laser printer capable of printing on cut paper, not limited to a printer dedicated to label creation. The 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 printer 11 and the terminal 12 may also be connected by wire using the USB communication standard.

[0018] Next, the label management server 22 and the print log server 23 constituting the label data sharing system 100 of this embodiment will be described. The label management server 22 and the print log server 23 are each connected to a large number of terminals 12 via an Internet line 21. The label management server 22 and the print log server 23 may be connected via the Internet line 21 or via a wired LAN line 27. A user database 24, a submitted label database 25, and a content database 26 are also connected to the label management server 22 in an accessible manner.

[0019] In addition, a print log database 28 is accessible and connected to the print log server 23. The print log database 28 also stores the print history and total print volume 15 of each printer 11 transmitted from each printer 11 via multiple terminals 12 and the Internet line 21.

[0020] 2, the label management server 22 has a control unit composed of a CPU 221, a ROM 222, and a RAM 223, a storage device 224, a network interface 225, an operation display unit 226, and an interface 227. The ROM 222 stores a startup program for starting up the label management server 22. The RAM 223 is used as a working area when various processes are executed, or as a storage area for temporarily storing data.

[0021] The storage device 224 is configured by, for example, a HDD, a flash memory, etc., and stores a label management server program 228 and various processing programs.

[0022] The CPU 221 executes various processes according to programs read from the ROM 222 or the storage device 224 .

[0023] In this embodiment, the network interface 225 is configured by an interface conforming to a wired LAN communication standard. In addition, the network interface 225 may be, for example, an interface conforming to a wireless LAN communication standard such as Wi-Fi, an interface conforming to a USB communication standard, or an interface conforming to a short-range wireless communication standard such as Bluetooth. The network interface 225 is connected to the Internet line 21.

[0024] The operation display unit 226 is composed of, for example, a display device and a touch panel arranged on the display device, etc. The display device displays necessary information, and the touch panel accepts inputs by the user.

[0025] In this embodiment, the interface 227 is configured by an interface conforming to the communication standard of a wired LAN, and is connected to the user database 24, the posted label database 25, and the content database 26. The user database 24, the posted label database 25, and the content database 26 may be included in the label management server 22.

[0026] As shown in Fig. 2, the terminal 12 has a control unit 16 which is responsible for the central control of the terminal 12. The control unit 16 is equipped with a CPU 161, a ROM 162, and a RAM 163. The CPU 161 is a central processing unit which executes various control programs. The ROM 162 stores various control programs executed by the CPU 161 and permanent data. The RAM 163 temporarily stores the results of calculations of the control programs by the CPU 161, etc. Note that the control unit 16 in Fig. 2 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.

[0027] The terminal 12 also includes a communication interface (hereinafter, referred to as "communication IF") 18 connected to the control unit 16. In this embodiment, the communication IF 18 is configured by an interface conforming to a wireless LAN communication standard such as Wi-Fi. Alternatively, the communication IF 18 may be, for example, an interface conforming to a wired LAN communication standard or a USB communication standard. It may also be an interface conforming to a short-range wireless communication standard such as Bluetooth.

[0028] The terminal 12 also includes a user interface (hereinafter, referred to as "user IF") 19 connected to the control unit 16. In this embodiment, the user IF 19 is configured as a touch panel having a display function and an operation reception function. Alternatively, the user IF 19 may be configured as a combination of a display, such as a liquid crystal display or an organic EL display, for displaying information, and a keyboard, a mouse, or the like for receiving input operations by the user.

[0029] The terminal 12 also has a storage device 17 connected to the control unit 16. For example, a hard disk drive (HDD) or a solid state drive (SSD) can be used as the storage device 17. The storage device 17 stores an operating system (hereinafter referred to as "OS") 171, a client application 13, a printer driver 172, a terminal label database 173, and the like.

[0030] The OS 171 is, for example, Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), iOS (registered trademark), or Android (registered trademark).

[0031] The client application 13 is a program for executing processing for a specific purpose, and specifically, for example, is a program that can create new label data, read out label data, accept edits to the label data, save the label data, accept print settings, specify the printer 11 to execute printing, accept instructions to execute printing, etc. As other client applications, various application programs such as a word processing program, a spreadsheet program, a web browser program, etc. may be stored.

[0032] The printer driver 172 is a program used to control the printer 11. For example, when the user issues a print request instruction via the user IF 19 while the client application 13 is running, the printer driver 172 is started. Also, when the client application 13 is started, the printer driver 172 may also be started.

[0033] Then, the started printer driver 172 generates print data that is compatible with the printer 11, based on the image data specified in the print instruction information. Furthermore, the printer driver 172 transmits a print job including the generated print data, print settings, etc., to the printer 11.

[0034] Furthermore, when the printer driver 172 receives an inquiry from the client application 13 about the total print amount 15 of the printer 11, the printer driver 172 acquires the total print amount 15 stored in the printer 11 and transmits the acquired total print amount 15 to the client application 13.

[0035] The terminal 12 includes a battery unit 20 configured by a rechargeable battery, and the battery unit 20 supplies power to the control unit 16 and the like.

[0036] The user database 24 stores user-related information 30 shown in Fig. 3A as a table. The user-related information 30 is made up of records including a user ID 301, a user name 302, point information 303, a password 304, a number of posts 305, etc. for each user.

[0037] The user ID 301 is identification information for identifying a user to whom the label data sharing system 100 of this embodiment is provided, and specifies the user who uses the terminal 12. The user name 302 is the name, nickname, address, contact information, email address, etc. of the individual or group (corporation) of the user to whom the label sharing service of this embodiment is provided. Note that when a label is posted for the first time using the label data sharing system 100 of this embodiment, a user ID for identifying the user posting is newly set and additionally stored in the user ID 301. Furthermore, when posting, the user name, etc. entered by the user on the terminal 12 is additionally stored in the user name 302 corresponding to the newly set user ID.

[0038] The point information 303 is information indicating owned points, which are points in the label data sharing system 100 of this embodiment and are points currently owned by the user. Note that owned points can be used in place of cash when purchasing content, printing paper, etc. using the label data sharing system 100 of this embodiment.

[0039] In the label data sharing system 100 of this embodiment, each time posted label data is downloaded or printed by a user other than the poster, the value of the point information 303 of the user who posted the posted label data is incremented. Note that, although a detailed explanation of the increment method is omitted, the increment of the value of the point information 303 is performed based on the user ID 402, the number of downloads 403, the number of prints 404, etc. of the posted label related information 40 described later.

[0040] The password 304 is a password set by each user stored in the user name 302. The number of postings 305 is the number of times that the user posted label data from the terminal 12 that the user owns, that is, the number of times that the user uploaded the label data to the label management server 22.

[0041] The posted label database 25 stores posted label related information 40 shown in Fig. 3(B) as a table. The posted label related information 40 is made up of records including, for each label data posted in the label data sharing system 100 of this embodiment, a label ID 401, a user ID 402, a download count 403, a print count 404, posted label information 405, a content ID 406, tape size information 407, tape color information 408, a posting date 409, and printer information (not shown) of the printer 11 set to print the posted label data.

[0042] The label ID 401 is a serial number sequentially assigned to each piece of label data registered in the posted label database 25 in the label data sharing system 100 of this embodiment. The user ID (creator) 402 is the user ID 301 of the user who posted the label data using the label data sharing system 100 of this embodiment. The download count 403 is the number of times the label data posted by the user has been downloaded. The print count 404 is the number of times the label data posted by the user has been printed.

[0043] The posted label information 405 is posted label data, and is data indicating the configuration of a label. Specifically, the label data is composed of object information of text and images, and layout information thereof. The object information includes parameters set for each object. Furthermore, in the case where the label data includes content downloaded from the label management server 22, information on the content is also included. The content ID 406 stores the content ID of the content included in the label data stored in the posted label information 405.

[0044] Tape size information 407 stores information about the tape width and length set by the user who posted the data. Tape color information 408 stores information about the tape color set by the user who posted the data. Posting date 409 is the date on which the label data was posted by the user.

[0045] The content database 26 stores content-related information 50 shown in Fig. 3(C) as a table. The content-related information 50 is composed of a content ID 501, content information 502, content classification information 503, etc. The content ID 501 is a serial number sequentially assigned to each piece of content registered in the content database 26 in the label data sharing system 100 of this embodiment. The content ID is an example of content information.

[0046] The content information 502 stores content data provided to the user by the vendor (manufacturer) of the printer 11. The content data may be posted by the user using the label data sharing system 100 of this embodiment. The content data is composed of special fonts, pictograms, character images, decorative images, special frames, etc.

[0047] Content classification information 503 is a classification code for classifying the content data stored in content information 502, and the content data is classified by the vendor (manufacturer) of printer 11, assigned a predetermined classification code, and stored in content classification information 503. Specifically, classification codes such as "animals," "flowers," "people," "symbols," "characters," "seasons," and "Christmas" are stored in association with the content data. Note that it is also possible to configure content classification information 503 so that multiple classification codes are stored in association with one piece of content data.

[0048] The terminal label database 173 stored in the terminal 12 stores terminal label related information 60 shown in Fig. 3(D) as a table. The terminal label related information 60 is made up of records including a terminal label ID 601, a print count 602, terminal label information 603, a terminal content ID 604, posted information 605, terminal tape size information 606, terminal tape color information 607, printer information 608, and creation date 609.

[0049] The terminal label ID 601 is a serial number that is sequentially assigned to each piece of label data after the user creates and saves label data using the client application 13, or when label data is downloaded from the label management server 22. The number of prints 404 is the number of times the label data stored in the terminal label database 173 has been printed, and the number of prints is stored for each piece of stored label data.

[0050] The terminal label information 603 is information indicating the storage destination of the label data. The content ID 605 stores the content ID of the content included in the label data indicated in the terminal label information 603.

[0051] Posted information 605 is information indicating whether the label data indicated in terminal label information 603 has been posted from the terminal 12, i.e., uploaded to the label management server 22. Terminal tape size information 606 stores tape width and length information set by the user who posted. Furthermore, terminal tape color information 607 stores tape color and tape type information set by the user who posted. Printer information 608 stores the model name, model number, and specifications of the printer 11 when the saved label data is printed by the printer 11. Creation date 609 is the date on which the label data was stored in the terminal label database 173 by the user.

[0052] (Label creation process) Next, an example of a procedure for creating label data by the client application 13 of the terminal 12 in this embodiment will be described with reference to the sequence diagram of FIG.

[0053] Each processing step in this embodiment indicates processing by the CPU 161 according to instructions written in a program such as the client application 13 of the terminal 12. The processing by the CPU 161 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.

[0054] In the label creation process of this embodiment, first, a user who wishes to create label data instructs terminal 12 to launch client application 13 (step 11 (hereinafter referred to as T11)), and terminal 12 launches client application 13 and displays a label data creation screen on its user IF 19 (T12).

[0055] Thereafter, when the user performs a label creation operation using the label data creation screen displayed on the user IF 19 (T13), the terminal 12 creates label data 31, for example, as shown in FIG. 5, based on the operation (T14).

[0056] Specifically, this label data 31 is composed of an image object 32 which is content that the user has already purchased, and a text object 33 which indicates text that the user has manually input on the terminal 12. The content is composed of special fonts, pictograms, character images, decorative images, etc.

[0057] In addition, the user IF 19 of the terminal 12 displays a "Tape color" button 121 for setting the tape color information of the label data 31 created by the user, a "Tape length" button 122 for setting the tape length of the label data 31, a "Save" button 123, and a "Print" button 124.

[0058] Therefore, the user can set the color of the tape in the label data 31 by touching the "Tape Color" button 121. At this time, the configuration may also be such that the user can set the type of tape, for example, laminate or ribbon. Furthermore, the user can set the length of the tape in the label data 31 by touching the "Tape Length" button 122.

[0059] Furthermore, when the user touches the "Save" button 123 (T15), the terminal 12 saves the label data 31 created by the user, and stores a record relating to the label data 31 in the terminal label database 173 (T16).

[0060] Specifically, after creating a new terminal label ID, the terminal 12 stores it in the terminal label database 173 as a new terminal label ID 601 in the terminal label related information 60 shown in Fig. 3(D) . Thereafter, in association with the new terminal label ID 601, the terminal 12 stores the storage destination of the label data 31 created by the user as terminal label information 603, and stores the content ID of the content included in the label data 31 as terminal content ID 604.

[0061] The terminal 12 also stores the tape color and tape type set by the user as terminal tape color information 607, the tape length set by the user as terminal tape size information 606, and the creation date of the label data 31 as creation date 609.

[0062] Although not shown in the sequence diagram of FIG. 4, when the user touches the "Print" button 124, the printer driver 172 is launched. Therefore, the terminal 12 generates print data, which is data that can be handled by the printer 11, based on the label data 31. The terminal 12 also transmits a print job, which includes the print data and print settings generated by the printer driver 172, to the printer 11. This allows the user to create labels by printing the created label data 31 with the printer 11.

[0063] Furthermore, when printing with this printer 11, the tape color and tape type of the label data 31 set by the user after touching the "Tape Color" button 121, and the tape length of the label data 31 set by the user after touching the "Tape Length" button 122 are reflected.

[0064] After the printer 11 finishes printing, the printer 11 updates the total print volume 15 stored in the memory unit. That is, if the total print volume 15 as an index representing the proficiency level is composed of the number of prints, the number of prints is incremented by one. If the total print volume 15 as an index representing the proficiency level is composed of the length of the tape printed, the length of the tape used in the current print is added to the current length of the tape.

[0065] Furthermore, after printing by the printer 11 is completed, the terminal 12 updates the terminal label database 173 shown in Fig. 3(D). Specifically, if a record relating to the currently printed label data is not stored in the terminal label database 173, the terminal 12 saves the currently printed label data, and then stores a record relating to that label data in the terminal label database 173. This operation is the same as when the user touches the "Save" button 123, as described above, and therefore a detailed explanation will be omitted here.

[0066] Furthermore, if a record relating to the currently printed label data is stored in the terminal label database 173, the printer information of the printer 11 is stored in the printer information 608 of the record relating to the currently printed label data, and the number of prints 602 is incremented by one. Also, the terminal tape size information 606, terminal tape color information 607, etc. are updated.

[0067] Although not shown in the sequence diagram of FIG. 4, when the user touches the “Post” button 128, the terminal 12 transmits to the label management server 22 the user's user ID, the posted label data which is the label data 31 created by the user, tape size information suitable for printing the label data 31 as set by the user, tape color information of the label data 31 as set by the user, etc.

[0068] Furthermore, the terminal 12 updates the terminal label database 173 shown in Fig. 3(D) for the posted label data 31. Specifically, if a record relating to the currently posted label data is not stored in the terminal label database 173, the terminal 12 saves the currently posted label data, and then stores a record relating to that label data in the terminal label database 173. This operation is the same as when the user touches the "Save" button 123 as described above, and therefore a detailed explanation will be omitted here.

[0069] Furthermore, if a record relating to the currently posted label data is stored in the terminal label database 173, the terminal 12 stores "Posted" as the posting information 605 of the record relating to the posted label data.

[0070] On the other hand, the label management server 22 that has received the submitted label data stores the received submitted label data, etc. in the submitted label database 25.

[0071] In this manner, in this embodiment, the label data sharing system 100 allows users to post the label data 31 they have created; however, the details of the posting process will be described in detail in the label submission solicitation process described later, and therefore will not be explained here in detail.

[0072] (Label submission submission process) Next, an example of a procedure for inviting submissions of label data by the client application 13 of the terminal 12, including the operation of the label management server program 228 of the label management server 22 in this embodiment, will be described with reference to the sequence diagram of FIG.

[0073] That is, first, the administrator of the label management server 22 creates conditions for inviting contributions for the label data 31 that he / she wishes to solicit using the label data sharing system 100 of this embodiment (T21). As the conditions for inviting contributions, for example, a classification code for classifying the content included in the label data 31 can be used. Specifically, as the classification code that he / she wishes to solicit, for example, classification codes such as "animals," "flowers," and "people" can be used.

[0074] Furthermore, as a condition for soliciting submissions, for example, tape information of the label data to be collected can be used. Specifically, as the tape information of the label data to be solicited, for example, the width and length of the tape of the label, the color of the tape, the type of tape, etc. can be used.

[0075] The submission solicitation conditions may include, for example, printer information, such as the model name, model number, and specifications.

[0076] In this embodiment, the administrator can create submission solicitation conditions by combining the classification codes for classifying the content included in the label data 31, the tape information of the label data, and the printer information. The administrator can also create submission solicitation conditions by using any one of the classification codes for classifying the content included in the label data 31, the tape information of the label data, and the printer information alone, or can create submission solicitation conditions by using multiple classification codes for classifying the content.

[0077] Next, the administrator of the label management server 22 operates the operation display unit 226 of the label management server 22 to set the created submission solicitation conditions in the label management server 22 (T22), and the label management server 22 stores the set submission solicitation condition data in the storage device 224 (T23).

[0078] In this embodiment, a case where the administrator sets the content classification code "flower" as a posting solicitation condition in the label management server 22 will be described below.

[0079] In this embodiment, when a classification code is included in the submission solicitation conditions set by the administrator, the label management server 22 searches the content database 26 shown in Fig. 3(C) based on the set classification code. Then, the label management server 22 stores the content ID stored in the content ID 501 of the record in which the set classification code is stored in the content classification information 503 as submission solicitation condition data in the storage device 224.

[0080] That is, in this embodiment, since the administrator sets the classification code of the content data "flower" as a submission solicitation condition in the label management server 22, the label management server 22 stores the content ID in which "flower" is stored as the classification code as submission solicitation condition data in the storage device 224. Note that the submission solicitation condition data is an example of the solicitation conditions.

[0081] In this manner, in this embodiment, the administrator can set the classification code for classifying the content included in the label data 31 as a posting solicitation condition in the label management server 22, which encourages the posting of label data including that content, and allows label data using that content to be collected in the label management server 22. As a result, it is possible to promote the sale of that particular content.

[0082] In addition, the administrator can set the tape information of the label data as a submission solicitation condition in the label management server 22, which encourages submission of label data using the label indicated by the tape information, and allows label data using the tape indicated by the tape information to be collected in the label management server 22. As a result, sales of that particular tape are promoted.

[0083] In addition, the administrator can set the printer information as a submission solicitation condition in the label management server 22, which encourages submission of label data using the printer indicated in the printer information, and label data using the printer indicated in the printer information can be collected in the label management server 22. As a result, sales of that particular printer are promoted.

[0084] On the other hand, when the user instructs the terminal 12 to start the client application 13 (T24), the terminal 12 starts the client application 13 and displays a connection request screen to the label management server 22 on its user IF 19. When the user inputs a user ID, password, etc. on the displayed connection request screen and then touches a connection request button (not shown), the terminal 12 transmits a connection request to the label management server 22 (T25).

[0085] Next, the label management server 22 that has received the connection request establishes a connection with the terminal 12 if the user ID, password, etc. sent from the terminal 12 are correct (T26).

[0086] On the other hand, when the terminal 12 establishes a connection with the label management server 22, it deletes the existing submission solicitation condition data stored in the storage device 17 (T27). That is, when the client application 13 is started up the previous time, the submission solicitation condition data stored in the storage device 17 at the time of the previous connection is deleted in the process of T31 described later. The process of T27 is an example of a deletion process.

[0087] Next, the terminal 12 requests the submission solicitation condition data from the label management server 22 (T28).

[0088] Next, the label management server 22 that has received the submission solicitation condition data reads out the submission solicitation condition data stored in the storage device 224 in the previous processing of T23 (T29), and then transmits the read out submission solicitation condition data to the terminal 12 (T30), so that the terminal 12 receives the submission solicitation condition data.

[0089] Next, the terminal 12 that has received the submission solicitation condition data stores the received submission solicitation condition data in its storage device 17. Thereafter, the terminal 12 searches the terminal label database 173 based on the received submission solicitation condition data, and reads out the terminal label ID of the label data that stores information that matches the submission solicitation condition data (T31).

[0090] In this embodiment, the terminal label database 173 stores information about label data that has been "saved," "printed," and "posted." Therefore, the terminal 12 searches for label data that satisfies the submission invitation condition data, and reads out the terminal label ID of that label data. The process of T31 is an example of a condition acquisition process, a storage process, and an extraction process.

[0091] Furthermore, by storing the submission invitation condition data acquired from the label management server 22 in the non-volatile storage device 17, the terminal 12 can extract label data even when offline, thereby increasing the opportunities to encourage submission of label data.

[0092] In this embodiment, the terminal 12 is configured to store the received post solicitation condition data in its storage device 17, and then search the terminal label database 173 based on the post solicitation condition data, but after storing the received post solicitation condition data in the storage device 17, the terminal 12 may search the terminal label database 173 when a subsequent specific operation is performed, or may execute the search in the background of the processing of the terminal 12, or may execute the search when the terminal 12 becomes inactive. If the terminal 12 is configured to execute the search when it becomes inactive, the load on the CPU 161 is reduced and the search can be executed smoothly.

[0093] Specifically, in the search of this embodiment, if a content ID is included as the submission solicitation condition data, the terminal label database 173 is searched based on the included content ID, and the terminal label ID of the label data in which a content ID matching the included content ID is stored as the terminal content ID 604 is read out.

[0094] In this embodiment, since the content ID corresponding to the classification code "flower" is the draft solicitation condition data, the terminal label ID of the label data including the content corresponding to the classification code "flower" is read out.

[0095] Also, in this embodiment, when tape information of the label data is included as the submission solicitation condition data, the terminal label database 173 is searched based on the tape width, length, and tape color included in the tape information, and the terminal label ID of the label data whose width, length, and tape color match the included tape width, length, and tape color are stored as terminal tape size information 606 and terminal tape color information 607 is read out.

[0096] In addition, in this embodiment, if printer information is included as the submission solicitation condition data, the terminal label database 173 is searched based on the printer information, and if the printer information matches the included printer information, the terminal label ID of the label data stored as printer information 608 is read out.

[0097] Thereafter, the terminal 12 deletes the terminal label IDs for which “posted” is stored in the posted information 605 from among the terminal label IDs read out from the terminal label database 173, and then stores the undeleted terminal label IDs in its storage device 17 (T32).

[0098] Next, when the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the home page of the client application 13 (T33), the terminal 12 displays a posting prompting screen as shown in Fig. 7(A) on the user IF 19 (T34). The processing of T34 is an example of a suggestion process.

[0099] Specifically, on the posting prompting screen shown in Fig. 7(A), the terminal 12 displays a message 125 encouraging posting of unposted labels. Furthermore, the terminal 12 searches the terminal label database 173 based on the terminal label IDs stored in the storage device 17 in the process of T32, and reads out label data from the terminal label information 603 corresponding to each terminal label ID. After that, the terminal 12 displays the label data 31 on the user IF 19 based on the read label data. Additionally, the terminal 12 displays an "Execute" button 126 and a "Cancel" button 127 on the posting prompting screen.

[0100] In this embodiment, on the posting prompting screen shown in FIG. 7(A), the terminal 12 is configured to display a message 125 encouraging posting for unposted labels, but instead of or in addition to this, the message encouraging posting may be notified to the user by voice.

[0101] In this embodiment, the terminal 12 displays, on the user IF 19, a plurality of unposted label data 31 including contents corresponding to the classification code "flower" on the posting prompting screen shown in FIG. 7(A).

[0102] In this embodiment, since it may take time to extract the label data, the terminal 12 that has received the post solicitation condition data subsequently searches the terminal label database 173 based on the received post solicitation condition data, and stores the terminal label ID that matches the post solicitation condition data in non-volatile memory. Therefore, at the timing of a subsequent post suggestion, the stored result can be read out to immediately display the post invitation screen on the user IF 19, which eliminates the user's sense of waiting time and improves the operability of the terminal 12.

[0103] In this embodiment, the terminal 12 displays three label data 31 on the posting prompting screen shown in Fig. 7(A), but it may be configured to sequentially display a larger number of label data 31 on the user IF 19 in accordance with the user's scrolling operation. Also, when there are multiple label data 31, the terminal 12 may sort the label data 31 in descending order of the number of times printed based on the number of prints 602 in the terminal label database 173 and display them on the user IF 19. This configuration makes it easier for users to post label data 31 that has been printed many times by the user, i.e., label data 31 that is highly practical.

[0104] When the user selects one of the label data 31 displayed on the user IF 19 on the submission invitation screen shown in Fig. 7(A) and then touches the "Execute" button 126 (T35), the terminal 12 displays a preview screen as shown in Fig. 7(B) on the user IF 19 (T36). If the user touches the "Cancel" button 127, the terminal 12 stops the process of inviting submissions of this label data.

[0105] Specifically, on the preview screen, terminal 12 displays the label data 31 selected by the user, a “Tape Color” button 121, a “Tape Length” button 122, a “Cancel” button 127, a “Post” button 128, etc.

[0106] Here, if the user touches the "Tape color" button 121 as necessary, sets the tape color and tape type of the label data 31, and also touches the "Tape length" button 122 and sets the tape length of the label data 31, and then touches the "Post" button 128 (T37), the client application 13 of the terminal 12 transmits to the label management server 22 the user ID of the user, the posted label data which is the label data 31 created by the user, tape size information suitable for printing the label data 31 as set by the user, tape color information of the label data 31 as set by the user, etc. The process of T37 is an example of an upload instruction, and the process of T38 is an example of upload processing.

[0107] Furthermore, the terminal 12 updates the posted information 605 of the terminal label database 173 shown in Fig. 3(D) for the posted label data 31. That is, the terminal 12 stores "Posted" as the posted information 605 (T39).

[0108] Meanwhile, the label management server 22 that has received the submitted label data stores the received submitted label data in the submitted label database 25, and also increments the value of the number of submissions 305 in the user database 24 shown in FIG. 3(A) by one (T40).

[0109] Specifically, the label management server 22 creates a new label ID and stores it in the posted label database 25 as a new label ID 401 of the posted label related information 40. After that, in association with the new label ID 401, the label management server 22 stores the user ID 301 of the receiving user as a user ID (creator) 402, the received posted label data as posted label information 405, the content ID of the content data included in the received posted label data as a content ID 406, the received tape size information as tape size information 407, the received tape color information as tape color information 408, and the posting date as posting date 409.

[0110] Furthermore, the label management server 22 searches the user database 24 based on the user ID of the user, and increments the value of the number of posts 305 by one for the record in which the user ID 301 and the user ID of the user are stored.

[0111] Next, the label management server 22 transmits a "registration complete" to the terminal 12 (T41). Then, the terminal 12 that has received the "registration complete" displays on its display unit a message indicating that the registration of the submitted label data has been completed, to notify the user (T42). This allows the user to know that the submitted label data 31 has been registered in the label data sharing system 100.

[0112] In this manner, in this embodiment, the terminal 12 can obtain the submission solicitation condition data prepared in the label management server 22, search the terminal label database 173, and extract label data that matches the submission solicitation condition data from there. Then, when the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the client application homepage, the terminal 12 suggests to the user that the user post the extracted label data. Therefore, by having the administrator of the label data sharing system 100 store the submission solicitation conditions that he / she wishes to solicit in the label management server 22, it is expected that the administrator will be prompted to post label data that meets the submission solicitation conditions, and that the user will post the label data.

[0113] Second embodiment Next, an example of the procedure of the label data submission solicitation process by the client application 13 of the terminal 12, including the operation of the label management server program 228 of the label management server 22 in this embodiment, will be described with reference to the sequence diagram of Fig. 8. In this description, the same parts as those in the first embodiment are denoted by the same reference numerals.

[0114] That is, in this embodiment, the administrator of the label management server 22 creates conditions for soliciting contributions for the label data 31 that he / she wishes to solicit using the label data sharing system 100 of this embodiment. At this time, the administrator also sets an expiration date for the contribution solicitation conditions that he / she has created (T51). The expiration date for the contribution is composed of an end date for the contribution, and may further include a start date for the contribution.

[0115] Next, the administrator of the label management server 22 operates the operation display unit 226 of the label management server 22 to set the created conditions for inviting contributions and the expiration date for inviting contributions (T52).

[0116] Next, when the user touches a connection request button (not shown) displayed on the terminal 12, the terminal 12 transmits a connection request to the label management server 22 (T25), and then the terminal 12 deletes, from the existing submission solicitation condition data stored in its storage device 17, any submission solicitation condition data whose expiration date, i.e., termination date, has passed (T53).

[0117] In this manner, in this embodiment, among the existing submission solicitation condition data stored in the storage device 17, any submission solicitation condition data whose deadline has passed is deleted, making it possible to propose submissions with appropriate solicitation conditions.

[0118] Next, in the process of T30, the terminal 12 that has received the submission solicitation condition data stores the received submission solicitation condition data in its storage device 17 (T54). Therefore, in this embodiment, the storage device 17 stores the submission solicitation condition data received in the process of T30 and, of the existing submission solicitation condition data stored in the storage device 17, the submission solicitation condition data whose solicitation expiration date has not yet passed.

[0119] In this manner, in this embodiment, by storing the submission solicitation condition data obtained from the label management server 22 in the non-volatile storage device 17, label data can be extracted even if the terminal 12 is offline, increasing the opportunities to encourage submission of label data.

[0120] Next, the terminal 12 requests the printer 11 for the total print volume, which is a value indicating the user's proficiency (T55). The printer 11 then reads out the total print volume 15 stored in the memory unit (T56). The total print volume is an example of a proficiency value.

[0121] Next, the printer 11 transmits the read total print volume to the terminal 12, and the terminal 12 receives the transmitted total print volume (T57). The process of T57 is an example of a skill value acquisition process.

[0122] Next, the terminal 12 transmits the user ID of the user of the terminal 12 to the label management server 22 and requests a skill value that indicates the skill level of the user (T58).

[0123] The label management server 22 that has received the request for the user's proficiency value searches the user database 24 shown in Fig. 3(A) based on the received user ID of the user, reads out the number of posts stored in the number of posts 305 of the record to which the received user ID of the user is associated as the user ID 301, and calculates the proficiency value (T59). In this case, the number of posts read out from the user database 24 may itself be the proficiency value. Also, the proficiency value may be calculated by combining the number of posts stored in the number of posts 305 and the points stored in the point information 303.

[0124] 3B based on the received user ID of the user, and reads out the number of prints and the number of downloads stored in the number of prints 404 and the number of downloads 403 in the post label database 25, and then calculates the proficiency value by combining the number of posts, points, the number of prints, the number of downloads, etc. Although not shown, the label management server 22 may be configured to calculate the proficiency value by taking into account, for example, the number of "likes" given by the download user.

[0125] Next, the label management server 22 transmits the calculated proficiency value to the terminal 12, and the terminal 12 receives the transmitted proficiency value (T60). The process of T60 is an example of a proficiency value acquisition process.

[0126] Then, the terminal 12 stores the total print volume transmitted from the printer 11 and the skill value transmitted from the label management server 22 in the storage device 17 (T61).

[0127] Next, the terminal 12 determines whether the total print volume and proficiency value stored in the storage device 17 exceed the threshold value (T62). If it is determined that the total print volume and proficiency value exceed the threshold value (T62: YES), the terminal 12 then searches the terminal label database 173 based on the submission solicitation condition data stored in the storage device 17 in the process of T54 and existing submission solicitation condition data whose solicitation expiration date has not yet passed, and reads out the terminal label ID of the label data that matches the submission solicitation condition data (T63).

[0128] The threshold value is a value set by an administrator of the label data sharing system 100, but the client application 13 may store it as a unique value, or, for example, the threshold value may be configured to be received from the label management server 22 together with the submission solicitation condition data received from the label management server 22 and set in the terminal 12.

[0129] Thereafter, the terminal 12 deletes, from among the terminal label IDs read out from the terminal label database 173, those terminal label IDs for which “posted” is stored in the posting information 605, and then stores the undeleted terminal label IDs in its storage device 17 (T32). Next, when the user performs a specific operation on the user IF 19 (T33), the terminal 12 displays a posting prompting screen such as that shown in Figure 7 (A) on the user IF 19 (T34), as in the first embodiment.

[0130] Furthermore, if the terminal 12 determines that the total print volume and the proficiency value do not exceed the threshold value (T62: NO), then the terminal 12 stops the submission solicitation process for this label.

[0131] In addition, the judgment of T62 of terminal 12 may be configured to determine that the threshold value has been exceeded if both the total printing volume and the expert value exceed the threshold value, or may be configured to determine that the threshold value has been exceeded if either the total printing volume or the expert value exceeds the threshold value.

[0132] Furthermore, in this embodiment, the terminal 12 is configured to obtain the total print volume from the printer 11, but it may be configured to obtain it from the label management server 22. In this case, the label management server 22 obtains the total print volume stored in the print log database 28 via the print log server 23. After that, the label management server 22 transmits the obtained total print volume to the terminal 12. Also, it may be configured so that the terminal 12 calculates the total print volume and proficiency value based on the user's usage record.

[0133] Furthermore, in this embodiment, the terminal 12 is configured to acquire both the total print volume and the skill value, but it may be configured to acquire either the total print volume or the skill value.

[0134] In this manner, in this embodiment, the terminal 12 can obtain the submission solicitation condition data with the solicitation expiration date set prepared in the label management server 22, search the terminal label database, and extract from it label data that matches the submission solicitation condition data whose solicitation expiration date has not yet expired. Then, when the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the client application homepage, the terminal 12 suggests to the user that he or she post the extracted label data. Therefore, by storing the submission solicitation conditions that the administrator of the label data sharing system 100 wishes to solicit in the label management server 22, the administrator is expected to be prompted to post label data that meets the submission solicitation conditions whose solicitation expiration date has not yet expired, and to have the user post the label data.

[0135] Setting a solicitation expiration date is particularly effective when soliciting label data that includes seasonal content, such as content related to flowers, festivals, fireworks displays, Christmas, etc., or time-limited content, such as the Olympics, sporting events, etc.

[0136] Generally, when the printer 11 has a small total print volume or a small number of label data submissions, the level of proficiency in creation is low, i.e., the quality of the label data tends to be low, so it is desirable to avoid suggesting submissions. In this embodiment, when the total print volume or proficiency level exceeds a threshold, the terminal 12 can collect high-quality label data in order to solicit submissions of label data.

[0137] Third embodiment Next, an example of the procedure of the label data submission solicitation process by the client application 13 of the terminal 12, including the operation of the label management server program 228 of the label management server 22 in this embodiment, will be described with reference to the sequence diagram of Fig. 9. In this description, the same parts as those in the first embodiment are denoted by the same reference numerals.

[0138] That is, in this embodiment, the terminal 12 that receives the submission solicitation condition data stores the received submission solicitation condition data in its storage device 17 (T71).

[0139] In this manner, in this embodiment, by storing the submission solicitation condition data acquired from the label management server 22 in the non-volatile storage device 17, the terminal 12 can perform searches based on the submission solicitation condition data even when it is offline. This increases the opportunities to encourage label data submission, improving convenience and is expected to increase the amount of label data submitted. On the other hand, searches based on the acquired submission solicitation condition data are not performed at this time.

[0140] Next, when the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the homepage of the client application 13 (T72), the terminal 12 reads out the submission solicitation condition data from the storage device 17. The terminal 12 then searches the terminal label database 173 based on the read out submission solicitation condition data, and reads out the terminal label ID of the label data that stores information matching the submission solicitation condition data. In other words, the terminal 12 searches for the label data at the timing of the specific operation.

[0141] Specifically, in this embodiment, when a content ID is included as the submission solicitation condition data, the terminal label database 173 is searched based on the included content ID, and the terminal label ID of the label data that stores a content ID matching the included content ID as the terminal content ID 604 is read out.

[0142] In addition, in this embodiment, if the submission solicitation condition data includes the tape width, length, and tape color, the terminal label database 173 is searched based on the included tape width, length, and tape color, and the terminal label ID of the label data whose width, length, and tape color match the included tape width, length, and tape color are stored as terminal tape size information 606 and terminal tape color information 607 is read.

[0143] Thereafter, the terminal 12 deletes, from among the terminal label IDs read out from the terminal label database 173, those terminal label IDs for which “posted” is stored in the posted information 605, and then stores the undeleted terminal label IDs in its storage device 17 (T73).

[0144] Thus, in this embodiment, the terminal 12 acquires and stores the submission solicitation condition data prepared in the label management server 22. Then, when the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the homepage of the client application 13, the terminal 12 can search the terminal label database based on the stored submission solicitation condition data and extract label data that matches the submission solicitation condition data from the terminal label database. Then, the terminal 12 suggests to the user that the user post the extracted label data. Therefore, by storing the submission solicitation conditions that the administrator of the label data sharing system wants to solicit in the label management server 22, the administrator is expected to encourage users to post label data that meets the submission solicitation conditions, and to have the users post the label data.

[0145] Furthermore, the terminal 12 does not search the terminal label database until the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the client application homepage, and when the user performs a specific operation, the terminal 12 searches the terminal label database based on the stored submission solicitation condition data and extracts label data that matches the submission solicitation condition data from there. Therefore, the terminal 12 does not need to hold the extraction results for a long time, and the load on the storage device 17 can be reduced.

[0146] As explained in detail above, it is possible to obtain the solicitation conditions prepared on the server and extract label data that matches those solicitation conditions from the stored label data. By suggesting the posting of the extracted label data, the system operators can store the solicitation conditions they wish to solicit on the server, which will encourage the posting of label data that meets those solicitation conditions, and it is expected that users will post that label data.

[0147] The embodiments disclosed in this specification are merely examples and do not limit the present invention in any way. Naturally, the technology disclosed in this specification can be improved or modified in various ways without departing from the spirit of the technology. Furthermore, the number of printers connected to the terminal is not limited to the illustrated example, and may be two or more.

[0148] In each of the above embodiments, the terminal 12 is configured to display a posting prompting screen as shown in Fig. 7(A) on the user IF 19 (T34) when the user performs a specific operation on the user IF 19, such as a print operation or an operation to return to the home page of the client application 13 (T33), but the present invention is not limited to this. For example, the terminal 12 may be configured to display the posting prompting screen (T34) when a certain number of unposted label data stored in the terminal label database 173 shown in Fig. 3(D) has been reached, and to sequentially execute the subsequent processes. The terminal 12 may also be configured to display the posting prompting screen (T34) periodically, for example, when one month or six months have passed since the previous label data was posted, and to sequentially execute the subsequent processes.

[0149] In addition, in this embodiment, the user database 24, the posted label database 25, and the content database 26 are accessible connected to the label management server 22, and the print log database 28 is accessible connected to the print log server 23, but the print log database 28 and any one of the user database 24, the posted label database 25, or the content database 26 may be accessible connected to the print log server 23.

[0150] In this embodiment, when a classification code is included in the posting solicitation conditions set by the administrator, the label management server 22 searches the content database 26 shown in Fig. 3(C) based on the set classification code. The label management server 22 is configured to store in the storage device 224, as posting solicitation condition data, the content ID stored in the content ID 501 on the same row as the row of the table in which the set classification code is stored in the content classification information 503. However, when the classification code of the content included in the content data stored in the terminal label information 603 is stored in the terminal label database 173 shown in Fig. 3(D), the label management server 22 may store in the storage device 224 the classification code as the posting solicitation condition data instead of the content ID.

[0151] In addition, in this embodiment, the posted label database 25 stores the posted label data posted by the user, but the posted label database 25 may store label data prepared in advance by the vendor (manufacturer) of the printer 11.

[0152] Furthermore, in this embodiment, the system is configured with the label management server 22 and the print log server 23, but these may be integrated into one server.

[0153] Furthermore, in any sequence diagram disclosed in the embodiments, 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.

[0154] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as ASIC, or a combination of these. 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]

[0155] 100 Label Data Sharing System 11 Printers 12 Terminal 13 Client Apps 173 Terminal Label Database 22 Label Management Server 24 User Database 25 Post Label Database 26 Content Database 31 Label Data 32 Content Data

Claims

1. A program executable by a computer of an information processing device to cause the information processing device to realize a function of accepting edits of label data and a function of saving the label data in the information processing device, The computer includes: A condition acquisition process for acquiring label data solicitation conditions from a server; an extraction process for extracting label data that matches the recruitment conditions acquired in the condition acquisition process from the label data stored in the information processing device; It is possible to execute The computer further comprises: executing a suggestion process for suggesting posting of the label data extracted in the extraction process; The computer further comprises: when an upload instruction for the label data extracted in the extraction process is received, an upload process is executed to upload the label data extracted in the extraction process to the server. A program that is structured as follows.

2. The program according to claim 1, The recruitment conditions acquired in the condition acquisition process include content information indicating content that can be included in label data, In the extraction process, extracting label data including the content indicated in the content information from the label data stored in the information processing device when the content information is included in the recruitment conditions acquired in the condition acquisition process; A program that is structured as follows.

3. The program according to claim 1, The solicitation conditions acquired in the condition acquisition process include tape information indicating a tape that can be used for printing label data, In the extraction process, extracting, from the label data stored in the information processing device, label data in which a tape indicated in the tape information is specified, when the tape information is included in the recruitment conditions acquired in the condition acquisition process; A program that is structured as follows.

4. The program according to claim 1, The recruitment conditions acquired in the condition acquisition process include printer information indicating a printer that can be used to print the label data, In the extraction process, extracting, from the label data stored in the information processing device, label data for which the printer indicated in the printer information is specified, when the printer information is included in the recruitment conditions acquired in the condition acquisition process; A program that is structured as follows.

5. The program according to claim 1, The computer includes: A proficiency value acquisition process can be executed to acquire a proficiency value that indicates a proficiency level in creating label data, The computer further comprises: When the proficiency value acquired in the proficiency value acquisition process exceeds a threshold, the suggestion process is executable; When the skill value acquired in the skill value acquisition process does not exceed the threshold value, the suggestion process is not executed. A program that is structured as follows.

6. The program according to claim 5, The skill level is the printing amount of label data. A program that is structured as follows.

7. The program according to claim 6, In the skill value acquisition process, a total printing amount counted by a printer connected to the information processing device is acquired as the proficiency value; A program that is structured as follows.

8. The program according to claim 5, The proficiency value is the amount of label data posted. A program that is structured as follows.

9. The program according to claim 8, In the skill value acquisition process, a server is requested to provide the number of posts by the logged-in user, and the number of posts sent from the server is acquired as the proficiency value, the server registers the uploaded label data in association with information of the user who uploaded the label data, and when the information processing device requests the number of posts, the server responds to the information processing device with the number of the registered label data associated with the information of the logged-in user included in the request as the number of posts. A program that is structured as follows.

10. The program according to claim 1, The computer includes: A storage process is executed to store the recruitment conditions acquired in the condition acquisition process in a non-volatile memory of the information processing device, In the extraction process, reading out the solicitation conditions stored in the non-volatile memory of the information processing device, and extracting label data that matches the read out solicitation conditions from the label data stored in the information processing device; A program that is structured as follows.

11. The program according to claim 10, The computer includes: In response to logging in to the server, the condition acquisition process and the storage process are executed, and before executing the condition acquisition process, an erasure process is executed to erase the recruitment conditions stored in the non-volatile memory. A program that is structured as follows.

12. The program according to claim 10, The recruitment conditions stored in the non-volatile memory are associated with an expiration date, In the extraction process, extracting label data that matches the solicitation conditions and is within a validity period from the label data stored in the information processing device; A program that is structured as follows.

13. The program according to claim 1, The computer includes: executing the extraction process following the execution of the condition acquisition process; The computer further comprises: executing a storage process for storing the result of the label data extraction process in a non-volatile memory of the information processing device, following the execution of the extraction process; In the proposal process, when a predetermined operation is performed via the information processing device, the extraction result stored in the non-volatile memory by the storage process is read out, and a proposal is made to post the label data indicated in the read out extraction result. A program that is structured as follows.

14. The program according to claim 1, The computer includes: When a predetermined operation is performed via the information processing device, the extraction process is executed, and the suggestion process is executed following the execution of the extraction process. A program that is structured as follows.

15. An information processing device that can be connected to a server via a network, has a function of accepting edits to label data, and a function of saving the edited label data, The information processing device includes: A condition acquisition process for acquiring label data solicitation conditions from the server; an extraction process for extracting label data that matches the recruitment conditions acquired in the condition acquisition process from the label data stored in the information processing device; It is possible to carry out The information processing device further comprises: executing a suggestion process for suggesting posting of the label data extracted in the extraction process; The information processing device further comprises: when an upload instruction for the label data extracted in the extraction process is received, an upload process is executed to upload the label data extracted in the extraction process to the server. It is configured as follows.

16. A system including an information processing device and a server, the information processing device being connectable to the server via a network, The information processing device includes: a function of accepting edits of label data and a function of storing the edited label data in the information processing device; The server, It is possible to save the label data recruitment conditions, The information processing device includes: The recruitment conditions can be acquired from the server, The information processing device further comprises: It is possible to extract label data that matches the acquired recruitment conditions from the label data stored in the information processing device, The information processing device further comprises: Propose posting the extracted label data; The information processing device further comprises: uploading the extracted label data to the server when an upload instruction for the extracted label data is received; The system is configured as follows:

Images