Program, server, and label data sharing system

Abstract

The present invention allows a user to easily select label data to be downloaded in a system for utilizing label data.　A label management server 22 can access a label DB 26, and label data are registered in the label DB 26. The label management server 22 acquires a print log to be outputted when a terminal 12B causes a label printer 11B to print the label data. The print log includes a label ID and a print date and time. The label management server 22 acquires a print log for each label data stored in the label DB 26, and counts the number of times of printing performed within a prescribed time. When a proposal request from a terminal 12C is received, the label management server 22 proposes the label data with high printing frequency to the terminal 12C on the basis of the number of times of printing counted for each label data.

Description

Program, server, and label data sharing system

[0001] The technical field disclosed in this specification relates to a program, a server, and a label data sharing system used in a system that utilizes label data.

[0002] A conventional system for utilizing content data is known in which a server that stores 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 points management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and then 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.

[0004] Japanese Patent Application Laid-Open No. 2002-99746

[0005] In recent years, systems have been considered that allow users who create label data to upload that data to a server, where other users can download and use that data for printing labels with a label printer. In such systems, as the number of label data items collected on the server increases, it becomes a hassle for users to select the label data items to download. While Patent Document 1 describes displaying a list of photo data stored on the server and allowing users to select, it does not describe any ideas for making it easier to select content such as photo data, leaving room for improvement.

[0006] A program made to solve the above-mentioned problems is a program executable by a server computer, the server being able to access a label database, in which label data and a label ID identifying the label data can be registered in association with each other, the computer being able to execute a transmission process, when a download request specifying one of the label data registered in the label database is received from a first information processing device, to transmit the specified label data to the first information processing device in association with the corresponding label ID, and further being able to execute an acquisition process to acquire a print log, the print log being stored in the server by the first information processing device. The print log is output from the first information processing device when a label printer is caused to print based on the label data received from the first information processing device, and the print log includes the label ID corresponding to the printed label data and time information. The computer is further configured to execute a counting process that counts the number of times each of the label data registered in the label database has been printed within a predetermined period based on the print log acquired in the acquisition process, and when a proposal request is received from the second information processing device, to execute a proposal process that suggests label data that are printed frequently based on the number of times each of the label data has been printed counted in the counting process.

[0007] A server equipped with a program having the above configuration counts the number of times each label data item is printed within a predetermined period based on a print log received from a first information processing device that caused a label printer to print the label data. When a suggestion request is received from a second information processing device, the server suggests label data items that are frequently printed based on the number of times each label data item is printed. This allows the server to suggest label data items that are frequently printed within the predetermined period to the user via the second information processing device. This allows the user who made the suggestion request to recognize label data items that are frequently printed by other users, i.e., that tend to have high utility value, and makes it easier for them to select such label data.

[0008] A system, device, and control method for realizing the functions of the above program, as well as a computer-readable storage medium storing the program, are also novel and useful.

[0009] The technology disclosed in this specification realizes a technology that allows a user to easily select label data to be downloaded in a system that utilizes label data.

[0010] FIG. 1 is an explanatory diagram that shows an outline of a label data sharing system; FIG. 2 is an explanatory diagram that shows an example of a user database, a label database, and a tape database; FIG. 3 is an explanatory diagram that shows an example of a print log database; FIG. 4 is a sequence diagram that shows an example of the procedure of a posting process and a download process; FIG. 5 is a diagram that explains an example of screen transitions; FIG. 6 is a sequence diagram that shows an example of the procedure of a printing process; FIG. 7 is a sequence diagram that shows an example of the procedure of a cache process; FIG. 8 is a sequence diagram that shows an example of the procedure of a recommendation display process; FIG. 9 is a flowchart that shows an example of the procedure of a counting process; FIG. 10 is a flowchart that shows an example of the procedure of a proposal information generation process.

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

[0012] The label data sharing system 100 (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 includes a terminal 12 and a label management server 22, which are connected via an internet line 21. The terminal 12 is owned by the owner or user of the label printer (hereinafter referred to as "user"). The terminal 12 can be connected to a print log server 23 via the internet line 21. The terminal 12 can be connected to a label printer 11. The label management server 22 can be connected to the print log server 23. The label management server 22 is an example of a "server." The internet line 21 is an example of a "network." Note that although only one terminal 12 is shown in FIG. 1, in reality, many terminals 12 are connected to the label management server 22. The print log server 23 can access a print log database (hereinafter referred to as the "print log DB") 30, and can store and manage in the print log DB 30 each print log in which the numerous terminals 12 that make up the system 100 cause the label printers 11 to print label data.

[0013] The label printer 11 is a printing device that includes, for example, a thermal transfer print head and prints on a roll of tape while unwinding it. Based on a print job received from, for example, the terminal 12, the label printer 11 prints an image on the stored tape and feeds the tape, causing the printed portion to protrude outside the machine. A label having a specified label length and label width is created using the tape protruded outside the machine. The label length is the length in the direction in which the label is ejected from the label printer 11. The label width is the length in the direction perpendicular to the label length.

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

[0015] There are several types of tape that can be used with the label printer 11. The types of tape may be distinguished, for example, by the width of the tape, the color of the tape or ink, or the material or whether the tape has been specially treated. Compatible label printer models are predetermined for each type of tape. The user can replace the type of tape that is most suitable for the purpose or application of the label printer from the multiple types of tape that are compatible with the model of label printer that will be used to print.

[0016] The terminal 12 is an information processing device equipped with communication functions, display functions, and operation functions. In this embodiment, the terminal 12 is configured as a smartphone, but may also be configured as a tablet or a personal computer. The terminal 12 stores a client application program (hereinafter referred to as a "client app") 13.

[0017] The terminal 12 can acquire and store capability information 14 from the label printer 11. The capability information 14 includes, for example, an IP address, printer information, and tape information. These pieces of information will be described later.

[0018] 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 stores content information 16 of content downloaded from the label management server 22, and can use that content to create and edit label data. The client application 13 has a function for posting, i.e., uploading, created label data to the label management server 22. The client application 13 has a function for downloading label data from the label management server 22. The client application 13 can save created or edited label data and label data downloaded from the label management server 22 as label data 15 on the terminal 12.

[0019] The client application 13 has a function for printing label data 15 using the label printer 11. When the client application 13 causes the label printer 11 to print label data, it has a function for outputting a print log of the print data to the print log server 23 via the Internet line 21. The client application 13 has a function for requesting the label management server 22 to suggest label data that is printed frequently. Therefore, the terminal 12 can be an example of any of the following: a "third information processing device" that posts label data, a "first information processing device" that prints label data and outputs a print log, and a "second information processing device" that sends a suggestion request. Each function of the client application 13 will be described later.

[0020] The label management server 22 is a device having at least a storage function and a communication function. The label management server 22 has a control unit 220 having a CPU 221 and a memory 222. The label management server 22 has a network interface (hereinafter referred to as "network IF") 225, an operation display unit 226, and an interface 227, which are connected to the control unit 220. The CPU 221 is an example of a "computer." The control unit 220 may also be an example of a "computer."

[0021] The CPU 221 executes various processes in accordance with programs read from the memory 222 and based on user operations. The memory 222 is a storage area that stores various programs such as a server program 228 and various data such as cache information 230. The memory 222 is also used as a work area when various processes are executed.

[0022] The server program 228 is a program for managing label data and the printing of label data. The server program 228 has the function of accepting submissions of label data and transmitting submitted label data to the terminals. When the server program 228 accepts a proposal request output from the terminal 12, it has the function of counting the number of times each label data is printed based on the print log and proposing label data with a high printing frequency to the terminal 12. The server program 228 is an example of a "program." The functions of the server program 228 will be described later.

[0023] The cache information 230 is information that the label management server 22 periodically counts the number of times each label data is printed, regardless of a proposal request, and stores in the memory 222. The cache information 230 will be described later.

[0024] 1 is not limited to a ROM, RAM, HDD, etc. built into the device, but may also be a storage medium that is readable and writable by the CPU 221. In addition to the above examples, storage media that the CPU 221 can read also include recording media such as a CD-ROM and a DVD-ROM.

[0025] The operation display unit 226 includes hardware for displaying a screen for notifying the user of information and hardware for accepting operations by the user. The operation display unit 226 may be a touch panel having both a display function and an operation acceptance function, or may be a combination of a display having a display function and a keyboard, mouse, trackball, or the like having an operation acceptance function.

[0026] The network IF 225 includes hardware for communicating with external devices such as the terminal 12 and the print log server 23. The communication standard of the network IF 225 is Ethernet (registered trademark), Wi-Fi, etc. The communication mode of the network IF 225 may be wired or wireless. The network IF 225 in this embodiment is connected to the Internet line 21. The network IF 225 is connected to the print log server 23 by wire or wirelessly. The print log server 23 is connected to a print log database (hereinafter referred to as "print log DB") and registers print logs. The print log DB 30 will be described later.

[0027] The interface 227 is connected to a user database (hereinafter referred to as "user DB") 25, a label database (hereinafter referred to as "label DB") 26, and a tape database (hereinafter referred to as "tape DB") 27. In this embodiment, the interface 227 is connected to the user DB 25 and the label DB 26 via the 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 separate from the label management server 22. The user DB 25 and the label DB 26 may also be included in separate servers. The label management server 22 and the print log server 23 may be integrated into one unit; for example, the label management server 22 may include a print log DB 30.

[0028] 2A, the user DB 25 can store information about users who can use the services provided by the system 100. The user DB 25 is composed of records that associate a user ID 251, a user name 252, and an address or residence 253.

[0029] 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 organization (corporation) of the user. The address or residence 253 specifies the place where the user who uses the terminal 12 resides. The user ID 251 is newly set when using a service provided by the system 100 for the first time. For example, when using a service provided by the system 100 for the first time, the user name and address or residence entered by the user on the terminal 12 are additionally stored in the user name 252 and address or residence 253 corresponding to the new user ID 251. In addition, personal information for each user, such as an email address and a telephone number, may be registered in the user DB 25.

[0030] 2B, the label DB 26 can store label data in association with a user ID. The label data stored in the label DB 26 may be label data posted from the terminal 12 (hereinafter also referred to as "posted label data"), or label data created by a party other than the user, such as a label printer vendor. The label DB 26 is composed of records that associate a label ID 261, a user ID (creator) 262, label data 263, supplemental information 264, a paid content list 265, and a posting date 266.

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

[0032] The label data 263 is label data stored in the label management server 22. The label data 263 stores information and arrangement of objects included in the label data, and further stores the type and arrangement of the content when specific content or functions are used. The label data may also include tape information. The paid content list stores paid content IDs that identify paid content and functions set in the label data 263. The supplemental information 264 stores information that was supplemented when the label data was registered in the label management server 22. The paid content list 265 stores paid content IDs that identify paid content or functions set in the label data 273. The posting date 266 is information that indicates the date on which the label data was posted.

[0033] As shown in FIG. 2C , the tape DB 27 can store specifications for each tape model number. In this embodiment, the tape DB 27 stores a tape model number 271 in association with a tape width 272, a tape type 273, a tape color 274, a text color 275, and a compatible model 276. The tape model number 271 is information identifying the type of tape. The tape width 272 is the length of the tape in a direction perpendicular to the tape length in the direction in which the tape is fed out from the label printer. The tape type 273 is information indicating the paper quality of the tape, and examples of the type stored include continuous tape, laminated tape, ribbon, masking tape, and half-cut label. The tape color 274 is the background color of the tape. The text color 275 is the color of the text printed on the tape. The compatible model 276 stores the model names of compatible label printers 11. There may be one or more model names.

[0034] 3, the print log DB 30 can store print logs output by the terminal 12. The print log DB 30 is configured with records that associate a print log ID 301, a user ID (printer) 302, a label ID 304, area information 305, printer information 306, tape information 307, content information 308, and a print date and time 309 as the print log.

[0035] The print log ID 301 is a serial number assigned in order to each print log registered in the print log DB 30. The user ID (printer) 302 is the user ID 251 of the user who printed the label using the label printer 11. The label ID 304 stores the label ID assigned to the label data printed by the label printer 11.

[0036] Region information 305 is information indicating the region where printing was performed. Printer information 306 is information about the printer that performed the printing. Tape information 307 is information indicating the tape used for printing. Content information 308 is information indicating the type of content included in the printed label data. Printing date and time 309 is information indicating the year / month / day / time when the label was printed by the label printer 11.

[0037] Next, the operation of the system 100 will be described. Each processing step in this embodiment basically indicates processing by the CPU 221 in accordance with instructions written in programs such as the server program 228. Processing by the CPU 221 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.

[0038] (Posting Process) The posting process for posting label data to the label management server 22 will be described with reference to Fig. 4(A). Here, an example will be described in which user A (hereinafter referred to as "poster A") posts label data 15A created on terminal 12A. For ease of explanation, the reference numerals for the user, terminal, their components, and label data will be given the suffix "A."

[0039] As shown in the sequence diagram of FIG. 4A , poster A starts the client application 13A on the terminal 12A and performs an upload operation on the terminal 12A (A01). For example, the client application 13A, while logged in to the label management server 22, causes a posting screen (not shown) provided by the label management server 22 to be displayed on the terminal 12A. Poster A selects label data 15A to post on the posting screen (not shown). Poster A inputs supplemental information on the posting screen (not shown). The supplemental information may be, for example, the label name, category, description of the label data, and an image showing an example of use. When poster A taps the new post button on the posting screen (not shown), the label management server 22 accepts an upload instruction (A02). The label management server 22 accepts the user ID of logged-in user A, the posted label data (hereinafter also referred to as "posted label data") 15A, and the supplemental information input on the posting screen, along with the upload instruction. A02 is an example of an "upload acceptance process."

[0040] Here, the label data 15A stores content information indicating the type of content included in the label data 15A, tape information received when creating the label data 15A, printer information for the label printer 11A, and regional information for the region where the label printer 11A is used. The content information is, for example, a content ID. The content ID may be the content ID for paid content or the content ID for free content. The tape information is, for example, a tape model number. The printer information is, for example, the model name of the label printer 11A. The regional information is, for example, country information.

[0041] The label management server 22 accesses the label DB 26 using the interface 227 and stores the received posted label data 15A (A03). A03 is an example of a "registration process." Specifically, the label management server 22 creates a new label ID as the new label ID 261 and creates a record including the new label ID in the label DB 26. After that, for the record including the new label ID 261, the label management server 22 stores the received user ID 251 of poster A as the user ID (creator) 262, the received posted label data 15A as the label data 263, the received supplemental information as the supplemental information 264, and the year, month, and day of posting as the posting date 266. The label management server 22 also creates a paid content list including the paid content IDs stored in the posted label data 15A and stores the list in the paid content list 265.

[0042] When the label management server 22 has finished storing the posted label data 15A, it notifies the terminal 12A that "registration is complete" (A04). The terminal 12A that has received the "registration is complete" notification displays, for example, a message indicating that the registration of the posted label has been completed (A05). This allows poster A to know that the posting has been completed.

[0043] (Downloading Process) The process of downloading posted label data will be described using Figure 4 (B). Here, an example will be described in which user B (hereinafter referred to as "printer B") downloads posted label data 15A posted by poster A to terminal 12B. For ease of explanation, the reference numerals of the user, terminal, and their components will be suffixed with the letter "B." Terminal 12B is an example of a "first information processing device." Note that the data to be downloaded may also be label data registered by a party other than the user, such as a label printer vendor.

[0044] For example, when the client application 13B is started, the terminal 12B displays a home screen (not shown) provided by the client application 13B. The home screen (not shown) includes a server use button for using the label management server 22.

[0045] When the client application 13B accepts a server usage instruction via the operation of the server usage button, it displays a label search screen 200 provided by the label management server 22 on the terminal 12B, as shown in FIG. 5(A). The label search screen displays image or thumbnail images of downloadable label data. The images are associated with the label IDs of the corresponding label data. For example, as shown in FIG. 4(B), the client application 13B accepts the selection of a download target when an image corresponding to posted label data 15A is tapped on the label search screen 200 (B01). In response to the selection of a download target, the label management server 22 provides a download screen (not shown) to the client application 13B and displays it on the terminal 12B (B11).

[0046] The download screen (not shown) includes a download execution button. The client application 13B accepts a download instruction through operation of the download execution button (B21) and sends the download instruction to the label management server 22 (B22). The label management server 22 accesses the label DB 26 and reads out posted label data 15A from the label DB 26 based on the label ID associated with the image selected in B01 (B23). The label management server 22 sends the read posted label data 15A to the terminal 12B (B24).

[0047] The client application 13B of terminal 12B stores the received posted label data 15A (B25). The processes of B01, B11, and B21 to B25 are examples of "downloading processes." The process of B24 is an example of "sending processes." Note that user B may select multiple label data on the label search screen and download them to terminal 12B.

[0048] (Printing Process) The printing process for printing label data will be described with reference to Figure 6. Here, we will explain an example in which printer B edits and prints the downloaded posted label data 15A. For ease of explanation, the reference numerals for the user, terminal, and their components will be suffixed with the letter "B."

[0049] For example, when printer B taps the file button 202 shown in Fig. 5A, the client application 13B displays a list of label data stored in terminal 12B on terminal 12B. When printer B taps posted label data 15A included in the list, the client application 13B opens the posted label data 15A and displays the contents of the posted label data 15A on the editing screen. The client application 13B accepts an editing operation for the posted label data 15A on the editing screen (C01).

[0050] When the client application 13B receives a print instruction via the edit screen (C02), it sends the print instruction to the label printer 11B selected at the time of print setting (C03). The print instruction includes the edited post label data 15A. The label printer 11B prints the post label data 15A (C04) and sends the print result to the client application 13B (C05).

[0051] When the client application 13B receives the print results from the label printer 11B, it determines whether the printing was successful based on the print results (D01). If the printing was successful (alt: successful), the client application 13B outputs a print log of the printing to the print log server 23 (D02). D02 is an example of an "output process." The client application 13B may output a print log that it generated itself, or may obtain and output a print log from the label printer 11B. The print log includes the user ID of printer B, the label ID of the printed post label data 15A, and the printing date and time when the post label data 15A was printed. The printing date and time may be the time when printing was completed or the time when the print job was submitted to the printer. The printing date and time may also include the day of the week. The printing date and time is an example of "time information." The print log may also include attribute information that indicates the attributes of the printed label data.

[0052] The attribute information includes, for example, area information, printer information, tape information, and content information. The area information, printer information, and tape information are, for example, information based on capability information 14B of the label printer 11B stored in the terminal 12B. The capability information 14B is obtained, for example, when the terminal 12B connects to the label printer 11B, when print settings are accepted, when post label data 15A is sent to the label printer 11B, and when the print results are received.

[0053] For example, the capability information 14B includes the IP address of the label printer 11B. The IP address includes region information indicating the region. The client application 13B obtains the region information from the IP address and includes it in the print log. The client application 13B includes, for example, the model name of the label printer 11B as printer information in the print log. The client application 13B includes, for example, the tape model number obtained from the tape installed in the label printer 11B as tape information in the print log. Note that the tape information may be the tape model number saved in the terminal 12B by reading a QR code attached to the tape itself or its packaging when the tape was purchased. The tape information may also be the tape width, tape type, tape color, text color, etc.

[0054] The client application 13B adds the type of content contained in the printed label data as content information in the print log. The content may be, for example, text fonts, pictograms, shapes, symbols, images, frames, or two-dimensional barcodes.

[0055] The print log server 23 registers the print log output from terminal 12B in the print log DB 30 (D03). Specifically, the print log server 23 generates a new print log ID and stores the new print log ID in print log ID 301 of the new record. The print log server 23 stores the user ID, label ID, area information, printer information, tape information, content information, and print date and time included in the received print log in user ID 302, label ID 304, area information 305, printer information 306, tape information 307, content information 308, and print date and time 309 of the new record, respectively.

[0056] When the print log server 23 has completed the registration of the print log, it notifies the terminal 12B of the completion of the registration (D04). If the print result received from the label printer 11B indicates a printing failure (alt: failure), the client application 13B notifies the terminal 12B of an error (D05).

[0057] The print log DB 30 can store print logs output from all the terminals 12 and label printers 11 that make up the system 100, not just the terminal 12B.

[0058] (Cache Processing) The cache processing executed by the label management server 22 using the server program 228 will be described with reference to FIG.

[0059] When the label management server 22 detects the cache timing to execute the cache process (F01), it requests the print log server 23 to send a print log (F02). The cache process is a process that periodically counts the number of prints within the cache period for each label data, regardless of the proposal request output from the client application 13. The cache period is attached to the request in F02.

[0060] The cache timing may be, for example, a preset date such as the beginning or end of the month, or may be when a preset period has elapsed, such as three months since the last cache. The cache timing may also be set based on the day of the week. Furthermore, the cache timing is not limited to conditions related to date and time, and may be, for example, when it is detected that the number of print logs within a predetermined period of time has exceeded a predetermined number.

[0061] The cache period is information that specifies the period that is counted when the cache process is executed. The cache timing and cache period are set by the administrator of the label management server 22. The cache period may be a fixed period, such as from January to March, or a variable period, such as one year from a specified date. The cache period is preferably a long period during which the number of print logs that are counted increases. The cache period may be, for example, seasonal, or a period corresponding to a specific event such as Christmas or an entrance ceremony, or may be a period that is divided regardless of season or event, such as every three months or every year.

[0062] When the print log server 23 receives a request output from the label management server 22 (F02), it accesses the print log DB 30, reads the print log in which the print date and time within the cache period attached to the request is stored in the print date and time 309 (F03), and sends it to the label management server 22 (F04). When the label management server 22 receives the print log using the network IF 225, it counts the number of times each label data has been printed (F05).

[0063] When the label management server 22 has finished counting the number of prints for all the acquired print logs, it saves the count results in the memory 222 as cache information 230 (F06). The cache period is associated with the cache information 230. For example, if the cache timing is June 1, when spring changes to summer, and the cache period is "spring," the label management server 22 acquires the print logs of label data printed between March 1 and May 31, counts the number of prints for each label ID included in the acquired print logs, and saves the count results as the cache information 230 in association with the cache period "spring."

[0064] (Recommendation Display Processing) The recommendation display processing executed by the label management server 22 using the server program 228 will be described with reference to Fig. 8. Here, an example will be described in which the label management server 22 receives a proposal request from the terminal 12C and proposes label data with a high printing frequency using the terminal 12C. For ease of explanation, the subscript "C" will be added to the reference numerals of the user, terminal, and their components.

[0065] For example, when user C (hereinafter referred to as "proposal requester C") operates the server use button 203 to accept an instruction to use the server (H01), the client application 13C sends a usage request to the label management server 22 (H02). Upon receiving the usage request, the label management server 22 provides a label search screen to the client application 13C (H03), which is displayed on the terminal 12C (H04). For example, the label search screen 200 shown in FIG. 5(A) includes a popular label display button 211. The popular label display button 211 is an operation object that accepts an instruction to view label data that is printed frequently, that is, popular label data. Note that in this embodiment, the popular label display button 211 is displayed on a screen provided by the label management server 22, but it may also be displayed on a screen provided by the client application 13C.

[0066] When the proposal requester C taps the popular label display button 211, the client application 13C accepts the recommendation instruction (H05) and sends a proposal request to the label management server 22 (H06), as shown in FIG. 8 . The proposal request is accompanied by period information specifying the period to be displayed. In the client application 13C of this embodiment, the default value of the period specified by the period information is set to "within the last 24 hours." The proposal request also includes the user ID of the proposal requester C.

[0067] 8, when the label management server 22 receives a proposal request using the network IF 225 (H06), it determines whether there is a cache corresponding to the period information attached to the proposal request (H07). In this embodiment, "within the last 24 hours" is a short period, and no corresponding cache information is stored in the memory 222. In this case, the label management server 22 determines that there is no cache corresponding to the period information attached to the proposal request (alt: none), and requests the print log server 23 to send a print log for the same area as the current user (H21). This is because proposal requester C is likely to use label data that matches the characteristics of the area where he or she lives. H21 is an example of an "acquisition process."

[0068] For example, the label management server 22 accesses the user DB 25 and acquires the address or residence 253 associated with the user ID of the proposal requester C attached to the proposal request. The label management server 22 identifies the region in which the proposal requester C resides based on the acquired address or residence 253. The label management server 22 requests the print log server 23 to send a print log, specifying the identified region.

[0069] The print log server 23 accesses the print log DB 30, acquires all print logs for the specified region stored in the region information 305 (H22), and sends them to the label management server 22 (H23). Once the label management server 22 acquires the print logs using the network IF 225, it executes a counting process (H24). The counting process counts the number of times printing has been performed within a specified period for each label data item stored in the label DB 26, based on the print logs.

[0070] 9, the CPU 221 of the label management server 22 extracts print logs printed within a predetermined period (S11). The predetermined period is the period specified in the period information. In this example, the predetermined period is "within the last 24 hours." The label management server 22 extracts print logs whose print date and time 309 is between the current time and 24 hours ago from the print logs acquired in H23.

[0071] The CPU 221 determines whether an attribute is specified in the proposal request (S12). At this point, no attribute information is attached to the proposal request. In this case, the label management server 22 determines that an attribute is not specified in the proposal request (S12: NO) and counts the number of prints for each label data item for the print logs extracted in S11 (S14). For example, the label management server 22 extracts print logs that include the same label ID and counts the number of prints. When the CPU 221 has counted the number of prints for all print logs extracted in S11, it ends the counting process.

[0072] When acquiring print logs from the print log server 23 in H22, the label management server 22 may specify a period and acquire only print logs that correspond to the specified region and period. In this case, S11 may be deleted from the procedure in FIG. 9.

[0073] 8, when the counting process in H24 is completed, the label management server 22 executes a proposal information generation process to generate proposal information (H31). The proposal information is information for suggesting label data that is frequently printed.

[0074] 10(A), in the proposal information generation process of H31, the CPU 221 of the label management server 22 sorts the label data in descending order of the number of times it has been printed (S21). The CPU 221 determines whether a display count has been set (S22). The display count may be set on the label management server 22 side, or may be set based on an instruction from the client application 13C side. By setting the display count to "1," only the label data with the most number of times it has been printed may be proposed, or by setting the display count to "2 or more," multiple label data with the most number of times it has been printed may be proposed.

[0075] If the display count is set (S22: YES), the label management server 22 generates proposal information for the number of label data items to be displayed, starting from the top of the label data items sorted in S21 (S23). Label data items that have been printed only a small number of times and have little basis for being proposed are excluded from the proposals, making it easier for the user to select label data.

[0076] On the other hand, if the display count is not set (S22: NO), the label management server 22 generates proposal information for all label data from the top to the bottom (S25). This allows the proposal requester C to check the label data printed within a specified period.

[0077] 8, the label management server 22 sends the proposal information generated in H31 to the client application 13C of the terminal 12C (H32). H31 and H32 are examples of "proposal processing." Based on the received proposal information, the client application 13C displays label data that is frequently printed, i.e., popular, on the terminal 12C (H33).

[0078] For example, the proposal screen 240 shown in FIG. 5(B) displays a label image so that proposal requester C can easily understand the contents of the label data. Label data that has been printed many times tends to have high utility value. Therefore, the proposal screen 240 may display label data with a higher number of prints at the top. In this case, the label data may be displayed in order. The number of downloads of the proposed label data may also be displayed.

[0079] The method of proposing label data is not limited to that shown in FIG. 5B. For example, an image showing an example of how to use the label may be displayed for each piece of label data together with a conceptual image. Alternatively, for example, a label example of how to use the label, the label name, the name of the label creator, and the number of downloads may be displayed for each piece of label data. In this case, a conceptual image of the label may or may not be displayed.

[0080] The proposal screen 240 has a specification field 241 for specifying the display target. The specification field 241 has radio buttons 242 for specifying the period to be displayed. The client application 13C of this embodiment can change the period specified in the period information between "within the last 24 hours" and "this season" using the radio buttons 242 in the specification field 241. Note that the specification field 241 may allow the proposal requester C to specify the period as desired.

[0081] The specification field 241 is provided with a filter condition setting button 243. The filter condition setting button 243 is an operation object that accepts an instruction to set filter conditions other than the period. When the proposal target C taps the filter condition setting button 243 with, for example, "within the last 24 hours" selected, the client application 13C displays a filter setting screen 245 shown in FIG. 5(C) on the terminal 12C. The filter setting screen 245 is provided with an attribute specification field 246, a content specification field 247, an OK button 248, and a cancel button 249. The attribute specification field 246 can accept specification of an attribute. The content specification field 247 can accept specification of content from among content that can be set for the specified attribute.

[0082] For example, when proposal recipient C enters tape information in the attribute specification field 246, the tape model number included in the capability information 14C acquired from the label printer 11C is automatically displayed in the content specification field 247. The content specification field 247 may automatically display any one of the label width, tape type, label color, and text color corresponding to the tape model number. The content specification field 247 may also display selectable tape model numbers corresponding to the model of the label printer 11C. When proposal recipient C operates the OK button 248, the client application 13C outputs a proposal request to the label management server 22 in H02 of Fig. 8, with attribute information including the specified attribute "tape information" and content type "tape model number" attached.

[0083] 9, the CPU 221 of the label management server 22 determines that an attribute is specified in the proposal request (S12: YES). In this case, the CPU 221 extracts print logs corresponding to the specified tape model number from the print logs acquired in S11 based on the period (within the last 24 hours) specified in the time information (S13). For example, the CPU 221 extracts print logs in which the specified tape model number is stored in the tape information 307. The processing from S14 onwards is as described above, so a description thereof will be omitted.

[0084] 5(D), the label management server 22 can cause the terminal 12C to display a proposal screen 270 that displays label data printed with the tape model number specified in the proposal request and within the period specified in the proposal request (within the last 24 hours). This allows the label management server 22 to propose, for example, popular label data for tapes that the proposal requester C owns to the proposal requester C via the terminal 12C. This allows the proposal requester C to avoid downloading label data for a tape that he or she does not own and resulting in printing failure.

[0085] 5C , the model name included in the capability information 14C acquired from the label printer 11C is automatically displayed in the content specification field 247. When the proposal target C operates the OK button 248, the client application 13C outputs a proposal request to the label management server 22 in H02 of FIG. 8 , with attribute information including the specified attribute "model information" and content type "model name." In this case, the label management server 22 extracts in S13 of FIG. 9 the print log in which the specified printer name is stored in the printer information 306 of the print log. This allows the label management server 22 to propose label data that can be printed by the label printer 11C used by the proposal requester C, for example, and to avoid printing failures.

[0086] 9 。 9 。 English: Furthermore, for example, when the proposal requester C enters "emoji" in the attribute specification field 246 in FIG. 5C , the emojis purchased by the proposal requester C are automatically displayed in a selectable manner in the content specification field 247. For example, if the user DB 25 stores purchase information indicating the type of content and functions purchased for each user, the label management server 22 reads out the purchase information corresponding to the user ID "aaa3" of the proposal requester C from the user DB 25. The label management server 22 extracts content information of the emoji from the content information included in the read purchase information and displays it in a selectable manner in the content specification field 247. When the proposal requester C selects, for example, the "Santa Claus" emoji from the emojis displayed in the content specification field 247, the label management server 22 extracts the print log in which the specified Santa Claus emoji is stored in the content information 308 in S13 of FIG. According to this, the label management server 22 can propose label data including a Santa Claus emoticon that the proposal requester C wants to use, for example, and the proposal requester C can download the proposed label data and immediately use it for editing, printing, etc.

[0087] Furthermore, suppose that proposal requester C changes the period set in the period information from "within 24 hours" to "this season" in the specification field 241 of the proposal screen 240 shown in FIG. 5 (B). The label management server 22 counts the number of prints for each season and stores the count results in the memory 222 as cache information 230. If the season corresponding to "this season" is "spring," the label management server 22 reads the cache information 230 corresponding to "spring" from the memory 222 in H03 of FIG. 8 (alt: present, H11). The label management server 22 further identifies the region in which proposal target C resides based on the user ID of proposal requester C, and extracts print logs for which the identified region is stored in the region information 305 (H12). The method for identifying the region was explained in H21, so a detailed explanation will be omitted here. Thereafter, the label management server 22 executes proposal information generation processing (H31). The processing from H31 onward has been described above, so a detailed explanation will be omitted here.

[0088] When the period to be displayed is long, such as a season, there will be a large number of print logs, and it will take time for the label management server 22 to count the number of prints for each label data. However, as in this embodiment, the label management server 22 counts the number of prints for each season at a time unrelated to a proposal request, caches the count results as cache information 230, and uses this cache when a proposal request is made, thereby enabling the label data to be proposed to be extracted quickly.

[0089] As described above, the label management server 22 equipped with the server program 228 of this embodiment counts the number of times each label data item is printed within a predetermined period, i.e., within the period specified by the period information, based on the print log received from the terminal 12B that caused the label printer 11B to print the label data. When a proposal request is received from the terminal 12C, the label management server 22 proposes label data items that have a high printing frequency based on the number of prints counted for each label data item. This allows the label management server 22 to propose label data items that have a high printing frequency within the predetermined period to the proposal requester C via the terminal 12C. This allows the proposal requester C who made the proposal request to recognize label data that other users have printed frequently, i.e., label data that tends to have high utility value, and makes it easier for them to select such label data. Therefore, the server program 228 of this embodiment makes it easy for users to select label data items to download in the system 100 that utilizes label data.

[0090] 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 naturally be improved and modified in various ways without departing from the spirit and scope of the invention. In the above embodiment, the printing frequency is determined based on the number of prints itself, but if the print was recently performed, the printing frequency may be determined by weighting the number of prints.

[0091] The proposal request may be output from the client application 13C at a timing separate from the operation of the popular label display button 211. For example, the client application 13C may output a proposal request when an image displayed on the label search screen 200 shown in FIG. 5A is tapped, and an instruction to view specific label data is received. This allows the label management server 22 to propose label data in conjunction with the display of a template. For example, the client application 13C may automatically send a proposal request when the server use button 203 is received. In this case, the label search screen 200 may not have the popular label display button 211. This allows the label management server 22 to automatically propose label data on the label search screen 200. Furthermore, the user can check frequently printed label data with few operations, making it easier to select what to download.

[0092] The predetermined period in S11 of Fig. 9 may be fixed. For example, the specification field 241 of the proposal screen 240 may not have an item for specifying a period.

[0093] Instead of steps S22, S23, and S25 shown in FIG. 10A , the proposed information generation process may generate proposed information targeting label data that have been printed more than a predetermined number of times (S31) as shown in FIG. 10B . By proposing all label data that have been printed more than the predetermined number of times in this manner, the user's freedom of choice is increased, while label data with fewer prints is not proposed, increasing the reliability of the proposals. The predetermined number of prints may be a fixed value or a variable value. If the variable value is set, it may be set by an administrator or may be changed based on the total number of prints. For example, if the total number of prints is less than 100, the predetermined number may be 10, but if the total number is less than 1,000, the predetermined number may be 100. However, the more frequently printed a label data item, the more useful it tends to be. Therefore, by proposing a predetermined number of label data items in descending order of print count, the user can easily select label data with high usefulness. Because the number of proposed label data items is kept within the predetermined number, problems such as an excessive number of proposed label data items making it difficult to choose are less likely to occur.

[0094] The proposal request output by the client application 13C does not need to include attribute information. However, if attribute information is included in the proposal request, the label management server 22 can limit the proposal targets not only by period but also by attribute, thereby proposing label data that is more suited to the user's purpose. The attribute information may be information different from the region information, printer information, tape information, and content information. Attribute information specifying multiple attributes may be included in the proposal request.

[0095] The period to be displayed may be arbitrarily specified in the specification field 241 on the proposal screen 240 shown in FIG. 5(B). This allows the label management server 22 to propose label data that is more suited to the user's purpose. The specified period may be a period going back from the present, such as the past week or the past year, or a specific period such as weekends, weekdays, summer, or winter. This allows the label management server 22 to propose label data that is more suited to the user's purpose.

[0096] The cache process in Fig. 7 does not have to be performed. Also, H03, H11, and H12 in Fig. 8 may be omitted. However, if the period to be counted is long, acquiring the cache information 230 allows the label management server 22 to extract the proposed label data at an early stage.

[0097] The label management server 22 may count only posted label data. This allows the label management server 22 to suggest posted label data that is frequently printed, thereby promoting the use of posted label data.

[0098] The label management server 22 may be configured with 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 use its web server function to accept download requests and proposal requests and send label data and proposal information, while the back-end server may obtain print logs and count the number of prints.

[0099] In addition to the print log output by the terminal 12, the print log DB 30 may also store the print log output by the label printer 11 if the label printer 11 has a function to output a print log.

[0100] In any sequence diagram disclosed in the embodiments, any of a plurality of processes can be executed in any order or in parallel as long as no contradiction occurs in the process content.

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

[0102] REFERENCE SIGNS LIST 11 Label printer 12 Terminal 21 Internet line 22 Label management server 25 User DB 26 Label DB 100 Label data sharing system 221 CPU 228 Server program

Claims

1. A program executable by a server computer, the server being able to access a label database, in which label data and a label ID identifying the label data can be registered in association with each other, the computer being able to: when a download request is received from a first information processing device in which one of the label data registered in the label database is specified, execute a sending process to send the specified label data to the first information processing device in association with the corresponding label ID, the computer being further able to execute an acquisition process to acquire a print log, the print log being output from the first information processing device when the first information processing device causes a label printer to perform printing based on the label data received from the server, the print log including the label ID corresponding to the printed label data and time information, the computer being further able to execute a counting process to count the number of times that printing has been performed within a predetermined period for each of the label data registered in the label database based on the print log acquired in the acquisition process, the computer being further able to execute and executing a proposal process to propose label data that is printed frequently, based on the number of times each of the label data is printed counted in the count process, when a proposal request is received from a second information processing device.

2. A program as recited in claim 1, wherein said proposal process is configured to extract a predetermined number of said label data in descending order of the number of times each of said label data has been printed in said count process, and to propose the extracted label data.

3. A program as recited in claim 1, wherein said suggestion process is configured to extract label data that has been printed more than a predetermined number of times based on the number of times each label data is printed counted in said count process, and to suggest the extracted label data.

4. A program as recited in claim 1, wherein the print log includes attribute information indicating attributes, and the program is configured to, when the proposal request in which an attribute is specified is received from the second information processing device, execute the following counting process, for each of the label data registered in the label database, based on the print log acquired in the acquisition process, to count the number of times that the label data has been printed with the specified attribute within the specified period, and the proposal process, for suggesting label data that is printed frequently, based on the number of times that each of the label data has been printed according to the specified attribute counted in the counting process.

5. A program as recited in claim 4, wherein the attribute information is regional information indicating a region where printing was performed, and the counting process is configured to, when a proposal request in which a region is specified as the attribute is received from the second information processing device, count the number of times printing was performed in the specified region and within the predetermined period for each of the label data registered in the label database based on the print log acquired in the acquisition process.

6. A program as recited in claim 4, wherein the attribute information is printer information indicating the type of the label printer that printed the label, and the counting process is configured to, when a proposal request in which the type of printer is specified as the attribute is received from the second information processing device, count the number of times printing was performed with the specified type of printer within the specified period for each of the label data registered in the label database based on the print log acquired in the acquisition process.

7. A program as described in claim 4, wherein the attribute information is tape information indicating a type of printed tape, and the counting process is configured to, when a proposal request in which the type of tape is specified as the attribute is received from the second information processing device, count the number of times that printing has been performed with the specified type of tape within the specified period for each of the label data registered in the label database based on the print log acquired in the acquisition process.

8. A program as recited in claim 4, wherein the attribute information is content information indicating a type of content included in the printed label data, and the counting process is configured to, when a proposal request in which a content type is specified as the attribute is received from the second information processing device, count the number of times that each of the label data registered in the label database including the specified content type has been printed within the specified period based on the print log acquired in the acquisition process.

9. A program as recited in claim 1, configured to cause the computer to execute, when the proposal request with a specified period is received from the second information processing device, a counting process that counts the number of times each of the label data registered in the label database has been printed within the specified period based on the print log acquired in the acquisition process, and a proposal process that suggests label data that is printed frequently based on the number of times each of the label data has been printed according to the specified period counted in the counting process.

10. A program as recited in claim 1, configured to cause the computer to execute a cache process to save in the server's memory the number of prints for each of the label data counted in the count process, and further cause the computer of the server, when a proposal request is received from the second information processing device, if the number of prints for each of the label data is saved in the memory, in the proposal process it reads the number of prints for each of the label data from the memory and suggests the label data that is printed frequently based on the number of prints for each of the label data that has been read, and if the number of prints for each of the label data is not saved in the memory, it causes the computer of the server to execute the count process, and in the proposal process it suggests the label data that is printed frequently based on the number of prints for each of the label data counted in the count process executed in response to the proposal request.

11. A program as recited in any one of claims 1 to 10, capable of causing the computer to execute an upload reception process for receiving an instruction to upload label data from a third information processing device, and further configured to cause the computer to execute a registration process, when the upload instruction is received in the upload reception process, for receiving posted label data that is label data uploaded from the third information processing device, and for associating the received posted label data with the label ID assigned to the posted label data, and for registering the data in the label database, and in the transmission process, when the download request specifying the posted label data is received from the first information processing device, for transmitting the posted label data to the first information processing device.

12. A server connectable to a first information processing device and a second information processing device via a network, the server being able to access a label database, in which label data and a label ID identifying the label data are registered in association with each other, the server further being able to, when a download request is received from the first information processing device in which one of the label data registered in the label database is specified, execute a sending process for sending the specified label data to the first information processing device in association with the corresponding label ID, the server further being able to execute an acquisition process for acquiring a print log, the print log being output from the first information processing device when the first information processing device causes a label printer to perform printing based on the label data received from the server, the print log including the label ID corresponding to the printed label data and time information, the server further being able to execute a counting process for counting the number of times that printing has been performed within a predetermined period for each of the label data registered in the label database based on the print log acquired in the acquisition process, the server further being able to, When a proposal request is received from the second information processing device, a proposal process is executed to propose label data that is printed frequently, based on the number of times each label data is printed counted in the count process.

13. 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 server being able to access a label database, in which label data and a label ID identifying the label data can be registered in association with each other, the first information processing device being able to specify one of the label data registered in the label database, and execute a download process for downloading the specified label data from the server in association with the corresponding label ID, the first information processing device being able to further execute an output process for outputting a print log to the server when the first information processing device causes a label printer to perform printing based on the label data received from the server, the print log including the label ID corresponding to the printed label data and time information, the server being able to execute a count process for counting the number of times that printing has been performed within a predetermined period for each of the label data registered in the label database based on the print log, the server being able to further execute and when a proposal request is received from the second information processing device, executes a proposal process to propose label data that is printed frequently, based on the number of times each of the label data is printed counted in the count process.

Images