Program, server, and system

Abstract

To propose appropriate use of consumable goods in a system for sharing label data.SOLUTION: A label management server 22 registers purchase information of consumable goods, for each user, on a user DB 25. The label management server 22 acquires a print log including use information indicating consumable goods used for printing label data. The label management server 22 detects, based on the acquired print log, unused consumable goods out of the consumable goods included in the purchase information. The label management server 22 issues notice information indicating the detected consumable goods, to a user who purchased the consumable goods.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, systems for sharing label data used to print labels with label printers have been considered, and in such systems, a mechanism for suggesting suitable uses of consumables for printing the label data to system users is desirable. Patent Document 1 discloses a system for sharing photo data via a WWW server, but does not disclose a mechanism for suggesting consumables that utilize the data to be shared. [Means for solving the problem]

[0006] a program executable by a server, the program having access to a purchase information database, in which purchase information indicating purchased consumables for printing label data can be registered for each user ID; when a computer of the server receives the purchase information associated with a user ID, the program is capable of executing a registration process of registering the received purchase information in the purchase information database in association with the user ID associated with the received purchase information; and the program is capable of executing an acquisition process of acquiring a print history related to the printing of the label data, the print history including usage information indicating consumables used to print the label data; and the program is capable of executing a detection process of detecting unused consumables among the consumables indicated in the purchase information registered in the purchase information database based on the print history acquired in the acquisition process; and a notification process of notifying a user who purchased the consumable detected in the detection process of notification information indicating the consumable detected in the detection process.

[0007] A server that executes a program having the above configuration registers purchasing information of consumables for each user in a purchasing information database. The server detects consumables that have been purchased but not used based on the printing history of the label data, and notifies the user who purchased the detected consumable of notification information indicating the consumable. This makes it easier for the user who purchased the consumable indicated in the notification information to realize that the consumable has not been used. As a result, it is expected that the consumable will not be left unused and will be used.

[0008] A server and a system for implementing the functions of the above-mentioned program, and a computer-readable storage medium for storing the program are also novel and useful. Effect of the Invention

[0009] According to the technology disclosed in this specification, a technology is realized that can suggest suitable uses of consumables in a system that aims to share label data. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram illustrating a label data sharing system according to a first embodiment. [Diagram 2] 3A and 3B are explanatory diagrams showing examples of a user database, a label database, and a tape database. [Diagram 3] FIG. 4 is an explanatory diagram illustrating an example of a print log database. [Figure 4] FIG. 11 is a sequence diagram illustrating an example of a procedure for a consumables purchasing process. [Diagram 5] FIG. 11 is a sequence diagram showing an example of a procedure of a posting process and a download process. [Figure 6] FIG. 13 is a diagram illustrating an example of a label search screen. [Figure 7] FIG. 11 is a sequence diagram illustrating an example of a procedure of a printing process. [Figure 8] 13 is a flowchart illustrating an example of a procedure for a purchase information update process. [Figure 9]FIG. 11 is a sequence diagram illustrating an example of a procedure of a recommendation process. [Figure 10] 13 is a flowchart illustrating an example of a procedure for an unused item detection process. [Figure 11] FIG. 11 is a sequence diagram showing the procedure of a recommendation process executed in the label data sharing system of the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] (First embodiment) A label data sharing system 100 (hereinafter abbreviated as "system 100") according to a first 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 a terminal owned by an owner or user (hereinafter referred to as a "user") of the label printer. The terminal 12 can be connected to a label printer 11. The system 100 is an example of a "system." The terminal 12 is an example of an "information processing device." The label management server 22 is an example of a "server." The Internet line 21 is an example of a "network." Although only one terminal 12 is shown in FIG. 1, in reality, many terminals 12 are connected to the label management server 22.

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

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

[0015] There are multiple 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, by the color of the tape or ink, or by the material of the tape or whether or not it has been specially processed. The model of the label printer that can be used with the tape is determined in advance depending on the type of tape. The user can replace the type of tape suitable for the purpose or use, etc., from among the multiple types of tape that correspond to the model of the label printer that will be used to print.

[0016] The terminal 12 is an information processing device having a communication function, a display function, and an operation function. The terminal 12 in this embodiment 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 client application 13 is an application program provided by the vendor of the label printer 11. The client application 13 has a function for creating and editing label data on the terminal 12. The client application 13 has a browser function, and can display on the terminal 12 a screen provided from an external device such as the label management server 22 via the Internet line 21.

[0018] The client application 13 has a function for posting, i.e. uploading, the 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 the created or edited label data and the label data downloaded from the label management server 22 in the terminal 12.

[0019] The client application 13 has a function for printing label data using the label printer 11. The client application 13 has a function for saving a print log every time the client application 13 causes the label printer 11 to print label data, and further for outputting the saved print log to the label management server 22 via the Internet line 21. The print log will be described later.

[0020] The client application 13 can obtain capability information 14 from the label printer 11 connected to the terminal 12 and store it in the terminal 12. The capability information 14 is, for example, printer information and tape information. The printer information is, for example, the model name. The tape information is information about the tape loaded in the label printer 11. The tape information is, for example, the tape model number and a serial number that identifies the tape. The client application 13 can store in the terminal 12 a user ID 17 used when logging in to the label management server 22. The functions of the client application 13 will be described later.

[0021] The label management server 22 is a device having at least a storage function and a communication function. The label management server 22 includes a control unit 220 having a CPU 221 and a memory 222. The label management server 22 includes 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".

[0022] The CPU 221 executes various processes according to programs read from the memory 222 and based on user operations. The memory 222 is a storage area in which various programs such as a server program 228 and various data are stored. The memory 222 is also used as a working area when various processes are executed.

[0023] The server program 228 is a program for managing label data and the printing of label data. The server program 228 has a function for accepting submissions of label data from the terminal 12. The server program 228 has a function for transmitting the submitted label data to the terminal. When the server program 228 accepts a specific request with a user ID 17 from the client application 13, the server program 228 has a function for notifying unused consumables among those purchased by the user corresponding to the user ID 17. The server program 228 is an example of a "program". The functions of the server program 228 will be described later.

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

[0025] The network IF 225 includes hardware for controlling communication with an external device such as the terminal 12. The operation display unit 226 includes hardware for displaying a screen for notifying a user of information, and hardware for accepting operations by the user. Note that 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, a mouse, a trackball, or the like having an operation acceptance function.

[0026] 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, a tape database (hereinafter referred to as "tape DB") 27, and a print log database (hereinafter referred to as "print log DB") 30. In this embodiment, the interface 227 is connected to the user DB 25, the label DB 26, the tape DB 27, and the print log DB 30 via the wired LAN 24. The user DB 25, the label DB 26, the tape DB 27, and the print log DB 30 may be included in the label management server 22, or may be included in a server other than the label management server 22. The user DB 25, the label DB 26, the tape DB 27, and the print log DB 30 may be included in different servers. The user DB 25 is an example of a "purchase information database". The print log DB 30 is an example of a "print history database".

[0027] 2(A), 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, a password 253, purchase information 254 for each consumable, a cumulative print volume 255 for each consumable, and a notification count 256 for each consumable.

[0028] The user ID 251 is identification information for identifying a user who can use the system 100, and specifies a user who uses the terminal 12. The user name 252 is the name or nickname of the individual or group (corporation) of the user. The 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 password entered by the user on the terminal 12 are additionally stored in the user name 252 and password 253 corresponding to the new user ID 251. In addition, personal information for each user, such as an email address, an address or residence, and a telephone number, may be registered in the user DB 25.

[0029] The purchase information 254 can store information about consumables purchased by the user for each user ID 251. In this embodiment, the purchase information 254 stores the serial number of each tape purchased by the user. The accumulated print amount 255 can store the accumulated length of the printed labels for each tape purchased by the user. The notification count 256 can store the number of times notification information has been notified to the user for each tape purchased by the user.

[0030] 2(B), 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 may be label data created by a party other than the user, such as a label printer manufacturer. The label DB 26 can store information related to label data, and is composed of records that associate a label ID 261, a user ID (creator) 262, label data 263, supplemental information 264, and a posting date 266.

[0031] The label ID 261 is a serial number sequentially assigned 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 data using the system 100. The user ID (creator) 262 for label data created by someone other than the user may store the ID of the administrator, the ID of the manufacturer who created the label, or be left blank.

[0032] The label data 263 stores the label data stored in the label management server 22. The label data 263 stores, for example, information and arrangement of objects set in the label data. The label data 263 stores the label width and label length of the label. The supplemental information 264 stores information that supplements the label data. The posting date 266 is information indicating the date on which the label data was posted.

[0033] 2C, the tape DB 27 can store specifications for each tape model number. In this embodiment, the tape DB 27 is configured by records in which a tape model number 270 is associated with a tape width 271, a total length 272, a tape type 273, a tape color 274, a character color 275, and a corresponding model 276.

[0034] The tape model number 270 is information for identifying the type of tape. The tape width 271 is the length in a direction perpendicular to the direction in which the tape is fed out from the label printer. The total length 272 is the length of the tape in the direction in which it is fed out from the label printer. The tape type 273 is information indicating the paper quality of the tape, and for example, long tape, laminated tape, ribbon, masking tape, and half-cut label are stored. The tape color 274 is the background color of the tape. The character color 275 is the color of the characters printed on the tape. The compatible model 276 stores the model name of the compatible label printer 11. There may be one model name or multiple model names. The tape model number can be identified based on the serial number of the tape.

[0035] 3, the print log DB 30 can store print logs output from the terminal 12. The print log DB 30 is configured as a record that associates a print log ID 301, a user ID (printer) 302, label size information 305, label color information 306, a tape serial number 307, a tape model number 308, and a print date and time 309 as a print log. The records that make up the print log DB 30 are an example of a "print history." The label size information 305, the label color information 306, the tape serial number 307, and the tape model number 308 are an example of "usage information."

[0036] The print log ID 301 is a serial number that is 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 with the label printer 11.

[0037] The label size information 305 can store the label width and label length of the printed label. The label color information 306 can store the tape color and text color of the printed label. The tape serial number 307 can store the serial number of the tape used for printing. The tape model number 308 can store the tape model number of the tape used for printing. The printing date and time 309 is information that indicates the year / month / day / time that the label was printed by the label printer 11.

[0038] Next, the operation of the system 100 will be described. Each processing step in this embodiment basically indicates processing by the CPU 221 according to 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 ease of explanation, the subject of each process may be the terminal 12 or the label management server 22.

[0039] (Purchase information registration process) The purchase information registration process will be described with reference to Fig. 4. The purchase information registration process is a process for registering consumables purchased by a user in the label management server 22. In the following, an example will be described in which a tape purchased by a user is registered in the label management server 22.

[0040] For example, as shown in FIG. 4(A), the tape to be loaded into the label printer 11 can be purchased through a mail-order system or at a store. A QR code is attached to the tape itself, the wrapping paper, or the packaging box. The QR code stores a URL indicating the location of a purchase information registration site and a serial number that identifies the tape. Tape is an example of a "consumable item." The consumable item may be a consumable item other than tape. The QR code may store information indicating the consumable item other than the serial number, such as a tape model number. The serial number, tape model number, URL of the purchase information registration site, etc. are printed on the tape itself or the packaging box.

[0041] The terminal 12 is equipped with a camera for reading images. For example, the client application 13 uses the camera of the terminal 12 to read a QR code printed on the packaging paper of a purchased tape (G01). The client application 13 analyzes the read QR code and obtains the URL of a purchase information registration site and the serial number of the purchased tape (G02).

[0042] The client application 13 accesses the label management server 22 based on the acquired URL, and causes the terminal 12 to display a purchase information registration screen (G03). For example, a purchase information registration screen 230 shown in FIG. 4(B) includes a serial number input field 231, a register button 232, and a cancel button 233. The serial number input field 231 is a field in which the serial number of the purchased tape is input. The serial number input in the serial number input field 231 may be read from a QR code and input automatically, or may be input manually. The register button 232 is an object that accepts an instruction to execute the registration of purchase information. The cancel button 233 is an object that accepts an instruction to cancel the purchase information registration procedure.

[0043] 4(A), when the client application 13 receives an instruction to register purchase information by operating the registration button 232 (G11), the client application 13 logs in to the label management server 22 (G12). For example, the client application 13 displays a login screen for logging in to the label management server 22, and after the user inputs the information required for logging in, logs in to the label management server 22. Note that if the user has already logged in and performed the process of G01, the client application 13 omits the process of G12.

[0044] After that, the client application 13 transmits a purchase information registration request to the label management server 22 (G13). The purchase information registration request includes the serial number entered in the serial number entry field 231 and the user ID of the logged-in user.

[0045] When the label management server 22 receives the purchase information registration request using the network IF 225 (G13), it registers the purchase information in the user DB 25 (G14). That is, the label management server 22 accesses the user DB 25, and adds the serial number attached to the purchase information registration request to the purchase information 254 of the record including the user ID of the logged-in user. As a result, the purchased tape is registered in the user DB 25 in association with the user ID of the purchaser. G14 is an example of a "registration process".

[0046] When the registration of the purchase information is completed, the label management server 22 notifies the user of this (G15). Based on the notification, the client application 13 causes the terminal 12 to display a message indicating that the registration of the purchase information is completed (G16). This allows the user to know through the terminal 12 that the registration of the purchase information is completed.

[0047] (Posting process) The posting process will be described with reference to Fig. 5(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 characters for the user, terminal, and their components, and label data will be suffixed with the letter "A."

[0048] Contributor A starts the client application 13A of 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 the terminal 12A to display a posting screen (not shown) provided by the label management server 22. The client application 13A causes the label data 15 stored in the terminal 12 to be selectable on the posting screen (not shown), and can accept an operation to select one of the data to be uploaded. The posting screen (not shown) has an input field for accepting input of supplemental information. The supplemental information is, for example, the label name, category, explanation of the label data, and an image showing an example of use. The supplemental information may include tape information such as a tape model number.

[0049] The posting screen (not shown) has a new posting button. When the client application 13A receives an upload instruction by operating the new posting button (A02), it transmits an upload request to the label management server 22. The upload request is associated with the user ID of the contributor A who is the logged-in user, the posted label data 15A, and the supplemental information entered on the posting screen.

[0050] When the label management server 22 receives an upload request using the network IF 225 (A02), it registers the submitted label data 15A uploaded from the terminal 12A that is the request source of the upload request in the label DB 26 (A03). A02 is an example of an "upload reception process". A03 is an example of a "label registration process". Specifically, the label management server 22 creates a new label ID as a new label ID 261, and provides a record including the new label ID in the label DB 26. After that, the label management server 22 stores the user ID of the received poster A in the user ID (creator) 262, the received submitted label data 15A in the label data 263, the received supplemental information in the supplemental information 264, and the date of the posting date and time in the posting date 266 for the record including the new label ID 261.

[0051] If the client application 13 is not logged in to the label management server 22 when making an upload request, the client application 13 displays a login screen and logs in to the label management server 22 before making the request.

[0052] When the storage of the posted label data 15A is completed, the label management server 22 notifies the terminal 12A of "registration complete" (A04). The terminal 12A that receives the "registration complete" notification displays, for example, that the registration of the posted label is complete (A05). This allows the poster A to know that the posting is complete. Note that a wide variety of label data is uploaded to the label management server 22 from terminals 12 that can log in.

[0053] (Download process) The download process will be described with reference to FIG. 5(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 characters for users, terminals and their components are given the suffix "B." Terminal 12B is an example of a "first information processing device." Note that the object to be downloaded may be label data registered by a party other than the user, such as a label printer vendor.

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

[0055] When the client application 13B receives a server usage instruction by operating the server usage button (B01), it transmits a connection request to the label management server 22 (B02). The label management server 22 causes the client application 13B to display a label search screen (B03). For example, as shown in FIG. 6, the label search screen 200 displays image images or thumbnail images of downloadable label data. The images are associated with the label IDs of the corresponding label data. The client application 13 displays a file button 203 and a server usage button 203 while it is running.

[0056] For example, as shown in Fig. 5(B), the client application 13B accepts the selection of the download target by tapping an image corresponding to the posted label data 15A on the label search screen 200 (B10). In response to the selection of the download target, the label management server 22 provides a download screen to the client application 13B and causes the terminal 12B to display it (B11).

[0057] The download screen (not shown) includes a download execution button. When the client application 13B receives a download instruction by operating the download execution button (B21), it transmits a download request to the label management server 22 (B22). If the client application 13 is not logged in to the label management server 22 when making a download request, the client application 13 displays a login screen and logs in to the label management server 22 before making the request.

[0058] The label management server 22 accesses the label DB 26 and reads out the posted label data 15A from the label DB 26 based on the label ID associated with the download target (B23). The label management server 22 transmits the read out posted label data 15A to the terminal 12B that is the request source of the download request (B24). The process of B24 is an example of a "transmission process".

[0059] The client application 13B of the terminal 12B stores the received posted label data 15A (B25). This makes the posted label data 15A available for use on the terminal 12B. Note that the printer B may select multiple label data on the label search screen and download the multiple label data together to the terminal 12B.

[0060] (Regarding print log registration) The printing process for printing label data will be described with reference to Fig. 7. Here, an example will be described in which printer B edits and prints the downloaded posted label data 15A. For ease of explanation, the reference characters for the user, terminal, and their components will be suffixed with the letter "B."

[0061] For example, when the client application 13B accepts an operation of the file button 202 shown in Fig. 6, it causes the terminal 12B to display a list of label data stored in the terminal 12B. The label data stored in the terminal 12B includes the posted label data downloaded from the label management server 22, as well as label data created by the client application 13B. When the client application 13B accepts an operation to select the downloaded posted label data 15A from the label data displayed in a list, it 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 of the posted label data 15A on the editing screen (C01).

[0062] 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 edited posted label data 15A is attached to the print instruction. The label printer 11B prints the posted label data 15A (C04) and sends the print result to the client application 13B (C05).

[0063] When the client application 13B receives the print result from the label printer 11B, it determines whether the printing was successful or not based on the print result (D01). If the printing was successful (alt: successful), the client application 13B outputs a print log of the printing to the label management server 22 (D02). The client application 13B may output a print log that it created, or may obtain and output a print log generated by the label printer 11B.

[0064] The print log includes the user ID 17 of printer B, the printing date and time when the posted label data 15A was printed, label size information, and label color information. The printing date and time may be the time when printing is completed or the time when the print job is input to the printer. The label size information includes the label width and label length. The label width and label length are set by the client application 13 when the label data is created or edited.

[0065] If the client application 13B can obtain the serial number and tape model number of the tape, it may include them in the print log. For example, when the client application 13B registers the serial number of a purchased tape in the label management server 22, the client application 13B may store the serial number in the terminal 12B and include it in the print log. For example, if the tape model number can be obtained from the tape installed in the label printer 11B, the client application 13B may obtain the tape model number from the label printer 11B and include it in the print log.

[0066] Note that the client application 13B does not output a print log if the client application 13B is not logged in to the label management server 22 when it receives a print instruction at C02. In this case, the client application 13B may store the print log in the terminal 12B, and when the client application 13B logs in next time and receives a print instruction, send all the print logs stored in the terminal 12B to the label management server 22. In this case, each print log includes the user ID of the logged-in user.

[0067] When the label management server 22 receives the print log output from the terminal 12B via the network IF 225, it registers the print log in the print log DB 30 (D03). Specifically, the label management server 22 generates a new print log ID. The label management server 22 accesses the print log DB 30 and stores the new print log ID in the print log ID 301 of the new record. The label management server 22 stores the user ID of the person who printed B, the label size information, the label color information, the tape serial number, the tape model number, and the printing date and time contained in the received print log in the user ID 302, label size information 305, label color information 306, the tape serial number 307, the tape model number 308, and the printing date and time 309 of the new record, respectively.

[0068] The label management server 22 that has registered the print log executes a purchase information update process (D04). The purchase information update process is a process for updating the purchase information 254 stored in the user DB 25.

[0069] 8, the CPU 221 of the label management server 22 judges whether or not the serial number of the tape is stored in the print log (S11). If the serial number of the tape is stored in the print log (S11: YES), the CPU 221 identifies the tape corresponding to the serial number and proceeds to S14.

[0070] On the other hand, if the serial number of the tape is not stored in the print log (S11: NO), the CPU 221 cannot identify a single tape used for printing. Therefore, the CPU 221 extracts from the user DB 25 the tape corresponding to the user ID in the print log (S12). That is, the CPU 221 extracts from the user DB 25 the purchase information corresponding to the user ID in the print log, i.e., the tape serial number. This allows the tape owned by the person who printed to be extracted.

[0071] The CPU 221 identifies the tape used for printing (S13). For example, the CPU 221 identifies the tape model number for each serial number extracted in S12. If the print log includes a tape model number, the CPU 221 acquires a tape model number that matches the tape model number in the print log from among the tape model numbers identified from the serial number. On the other hand, if the print log does not include either the serial number or the tape model number, the CPU 221 reads out label size information and label color information from the label DB 27 for each tape model number identified from the serial number. The CPU 221 extracts a combination that matches or is close to the combination of the label size information and label color information in the print log from among the combinations of the read label size information and label color information, and acquires a tape model number corresponding to the extracted combination. The CPU 221 selects a tape with a serial number that matches the acquired tape model number from among the tapes acquired in S12, and identifies the selected tape as the tape used for printing. Note that if there is no matching or close combination, the CPU 221 cannot identify the tape used for printing.

[0072] For example, a user may purchase multiple tapes of the same tape model number and register them in the label management server 22 at the same time. In this case, when the tape model number is acquired as described above and a tape is identified from the acquired tape model number, multiple tapes are identified. In this case, the CPU 221 limits the number of tapes to one based on a specific condition for identifying one from among the multiple tapes. For example, even if tapes of the same tape model number are purchased, only one tape can be used in the label printer 11B. Therefore, the specific condition may be the tape with the largest accumulated print volume. Also, for example, if the user DB 25 stores the purchase date and time for each purchased tape, the specific condition may be the tape with the oldest purchase date and time. Also, for example, if the user DB 25 stores the update date and time of the accumulated print volume, the specific condition may be the tape with the most recent update date and time of the accumulated print volume.

[0073] The CPU 221 judges whether or not the tape used for printing has been identified (S14). If the tape used for printing has not been identified (S14: NO), the CPU 221 ends the purchase information update process.

[0074] If the CPU 221 is able to identify the tape used for printing (S14: YES), it acquires the label length from the label size information in the received print log (S15). The CPU 221 accesses the user DB 25 and adds the tape length calculated in S15 to the cumulative print amount associated with the serial number of the identified tape (S16). This updates the cumulative print amount for the tape used by the print user B for printing.

[0075] The CPU 221 judges whether the cumulative print amount updated in S16 exceeds a threshold value (S17). For example, the server program 228 stores a threshold value used in S17 for each tape model number. The CPU 221 acquires a threshold value corresponding to the tape model number of the identified tape and uses it in S17. The threshold value may be common to all tapes or may be different for each tape model number. For example, a smaller threshold value is set for a tape with a long overall length than for a tape with a short overall length. For example, the threshold value may be information indicating the overall length of the tape used for printing. The overall length of the tape can be acquired, for example, by identifying the tape model number from the serial number of the usage information and collating the identified tape model number with the label DB 26. Note that the threshold value does not necessarily have to match the overall length, and may be a value between 90% and 100% of the overall length, that is, a value close to the used state. S17 is an example of a "used state detection process".

[0076] If the cumulative print volume updated in S16 exceeds the threshold value (S17: YES), it is highly likely that the tape used for printing has already been used and cannot be resumed. Therefore, CPU 221 deletes the serial number corresponding to the tape used for printing from user DB 25 (S18). Furthermore, CPU 221 deletes the cumulative print volume and the number of notifications associated with the deleted serial number from user DB 25. Thereafter, CPU 221 ends the purchase information update process. As a result, tapes that cannot be resumed because they have been used are excluded from the target of recommendation processing, which will be described later.

[0077] On the other hand, if the cumulative print amount updated in S16 does not exceed the threshold (S17: NO), the tape used for printing is likely not already used. Therefore, the CPU 221 does not delete the tape used for printing from the purchasing information and ends the purchasing information update process.

[0078] Returning to FIG. 7, if the client application 13B determines that printing has failed based on the print result (D01, alt: failure), it notifies the user of an error (D05) without registering the print log or updating the purchase information.

[0079] (Recommendation processing) The recommendation process will be described with reference to Fig. 9. For example, as shown in Fig. 9(A), the client application 13 can accept a user ID and password through a user operation and use them to log in to the label management server 22 (H10). Also, for example, the client application 13 can store the user ID 17 and password used at the previous login in the terminal 12 and use them at the next startup to automatically log in to the label management server 22 (H10).

[0080] The client application 13 outputs a consumable use frequency confirmation request to the label management server 22 at the time of logging in or after a certain period of time has elapsed since logging in (H11). The consumable use frequency confirmation request is a request for the logged-in user to confirm the usage frequency of a consumable item (tape in this embodiment) that the logged-in user has purchased. The consumable use frequency confirmation request is accompanied by the user ID 17 of the logged-in user. The consumable use frequency confirmation request is an example of a "specific request". The consumable use frequency confirmation request may be output by the client application 13 in response to a user operation of a consumable use frequency confirmation button provided by the client application 13.

[0081] When the label management server 22 receives a request to check the frequency of use of consumables using the network IF 225 (H11), it acquires a print log corresponding to the user ID 17 of the logged-in user from the print log DB 30 (H12). By acquiring the print log from the print log DB 30, the label management server 22 can reduce the communication load with the terminal 12. If the requesting terminal 12 stores a print log, the label management server 22 may acquire the print log from that terminal 12. This allows the label management server 22 to limit the print logs used to detect unused tapes to the print logs of the user who uses that terminal 12, making it easier to detect unused tapes. H11 is an example of an "acquisition process".

[0082] After that, the label management server executes unused item detection processing (H13). The unused item detection processing is processing for detecting unused tapes among the tapes purchased by the user.

[0083] For example, as shown in the unused item detection process in FIG. 10, the CPU 221 of the label management server 22 acquires the most recent printing date and time for each tape purchased by the logged-in user (S40).

[0084] Specifically, for example, the CPU 221 extracts the print log in which the tape purchased by the logged-in user was used from the print log acquired in H12. That is, the CPU 221 reads the purchase information associated with the user ID of the logged-in user from the user DB 25, and acquires the serial number of the tape purchased by the logged-in user.

[0085] The CPU 221 extracts the print log including the serial number stored in the purchase information from the print logs acquired in H12, thereby identifying the print log using the tape purchased by the logged-in user.

[0086] Some print logs do not store serial numbers. Therefore, the CPU 221 identifies the tape model number for each serial number stored in the purchase information. The CPU 221 extracts print logs that include the identified tape model number from the print logs that do not store serial numbers. The CPU 221 estimates each extracted print log as a print log that includes the serial number from which the tape model number was identified.

[0087] Some print logs do not store serial numbers or tape model numbers. On the other hand, the label data to be printed always stores label width, tape color, and character color. Therefore, the CPU 221 acquires a combination of label size information and label color information for each identified tape model number from the tape DB 27. The CPU 221 extracts print logs including combinations that match the acquired combinations and print logs including combinations that are close to the acquired combinations from print logs that do not store serial numbers or tape model numbers. The CPU 221 identifies a tape model number for each acquired combination based on the tape DB 27, and associates each identified tape model number with a serial number in the purchase information. The CPU 221 estimates each extracted print log as a print log including a serial number associated with the identified tape model number.

[0088] The CPU 221 acquires the most recent date and time for each serial number based on the identified or estimated print date and time 309 of the print log, thereby acquiring the most recent print date and time for each purchased tape.

[0089] It should be noted that the serial numbers of used tapes have been deleted from the purchase information in the purchase information update process, so in the process of S40, the most recent print date and time is acquired for tapes other than used tapes.

[0090] Thereafter, the CPU 221 determines whether there is a consumable (tape in this embodiment) that has not been used for a certain period of time (S41). S41 is an example of a "detection process." The certain period can be, for example, three months, six months, or one year. The certain period can be the same for all tapes, or can be a different period for each type of tape. For example, for seasonal tapes such as Christmas, one year and a month is used, and for general-purpose tapes used for business, etc., three months is used.

[0091] For example, if the most recent print dates and times acquired for each serial number in S40 are not all a certain period ago, the CPU 221 determines that there is no tape that has not been used for a certain period. In this case (S41: NO), the CPU 221 ends the unused item detection process.

[0092] On the other hand, if there is at least one printing date and time that is more than a certain period before the present among the most recent printing dates and times acquired for each serial number in S40, the CPU 221 determines that there is a tape that has not been used for a certain period of time. In this case (S41: YES), the CPU 221 determines whether or not there is a tape whose notification count does not exceed a threshold among the tapes that have not been used for a certain period of time (S42). For example, the CPU 221 reads out the notification count 256 associated with the serial number of the tape that has not been used for a certain period of time from the user DB 25. The CPU 221 compares the read notification count 256 with a threshold. If all the read notification counts are equal to or greater than the threshold, the CPU 221 determines that there is no tape whose notification count does not exceed the threshold among the tapes that have not been used for a certain period of time. In this case (S42: NO), the CPU 221 ends the unused item detection process.

[0093] On the other hand, if even one of the read notification counts does not exceed the threshold, the CPU 221 determines that among the tapes that have not been used for a certain period of time, there is a tape whose notification count does not exceed the threshold. In this case (S42: YES), the CPU 221 further narrows down the tapes that have not been used for a certain period of time to tapes whose notification count does not exceed the threshold (S43). This excludes tapes that have already been notified several times from tapes that are not being used, and prevents the user from feeling annoyed by the same notification being repeatedly made.

[0094] The CPU 221 determines whether there are multiple applicable consumables (tapes in this embodiment) (S44). If there is only one applicable tape (S44: NO), the CPU 221 generates notification information indicating the tape (S45) and ends the unused item detection process.

[0095] On the other hand, if there are multiple applicable tapes (S44: YES), the CPU 221 narrows down the tapes to those that meet the notification conditions (S46). The notification conditions may be, for example, a condition for notifying one tape, a condition for notifying several tapes, or a condition for notifying all tapes. When notifying one tape, for example, the tape with the oldest last print date and time may be notified, or the tape with the largest remaining amount may be notified. When notifying several tapes, for example, several tapes with the least number of notifications may be notified, or several tapes with the oldest last print date and time may be notified. The notification conditions may include a condition that specifies the notification order of the multiple tapes. The notification order is, for example, in order of popularity based on the number of purchases or the number of views. The CPU 221 generates notification information indicating the tapes narrowed down in S51 (S45), and ends the unused item detection process.

[0096] The label management server 22 may, for example, identify the tape model number corresponding to the serial number of the tape that has been finally narrowed down, read a record that stores the identified tape model number from the tape DB 27, and include the information contained in the read record in the notification information.

[0097] 9(A), the label management server 22, which has finished the unused item detection process, accesses the label DB 26 and acquires some label data that can use the tapes finally narrowed down in the unused item detection process (H14). For example, the label management server 22 identifies the tape model number that corresponds to the serial number of the finally narrowed down tape, and acquires label data including the identified tape model number from the label DB 26.

[0098] The label management server 22 excludes label data including the user ID associated with the consumable use frequency confirmation request from the label data acquired in H13 (H15). In other words, it limits the label data to those posted by users other than the user who sent the consumable use frequency confirmation request (requester). The label management server 22 generates proposed label information indicating the limited label data (H16). The proposed label information includes, for example, a thumbnail image of the acquired label data and a URL for a download screen.

[0099] After that, the label management server 22 responds to the consumables use frequency confirmation request of H11 (H17). The response includes notification information and proposed label information generated by the label management server 22. H17 is an example of "notification processing" and "label notification processing". After sending the notification information, the label management server 22 accesses the user DB 25 and adds 1 to the number of notifications associated with the user ID associated with the consumables use frequency confirmation request and the tape serial number indicated by the notification information (H21). H21 is an example of "counting processing".

[0100] The client application 13 causes the terminal 12 to display a recommendation screen proposing use of the tape indicated in the notification information, based on the notification information and the proposed label information received together with the response (H18). For example, a recommendation screen 240 shown in Fig. 9(B) includes an unused notification area 241 that notifies of unused tapes, based on the notification information, and a label data proposal area 242 that proposes label data corresponding to unused tapes.

[0101] In the unused notification area 241, for example, tape information of the tape indicated by the notification information is displayed. The tape information is, for example, an image, tape model number, tape width, tape type, tape color, and text color. This allows the user to easily notice the existence of a tape that has been purchased but is not being used, which promotes the reuse of tapes. In addition, the user can specifically know the specifications of the unused tape.

[0102] In the label data proposal area 242, for example, thumbnail images 243a, 243b, 243c of the label data included in the proposed label information are displayed. This prompts the user to download label data that uses a tape that has been purchased but not used. In addition, a link 244 to a download screen is provided in the label data proposal area 242. This allows the user to download label data on the recommendation screen 240 with fewer operations, encouraging the use of label data. The client application 13 can close the recommendation screen 240 by operating an OK button 245.

[0103] As described above, the label management server 22 executing the server program 228 of the first embodiment registers tape purchase information for each user in the user DB 25. The label management server 22 detects tapes that have been purchased but not used based on the printing history of label data, and notifies the user who purchased the detected tape of notification information indicating the tape. This makes it easier for the user who purchased the tape indicated in the notification information to notice that the tape has not been used. As a result, it is expected that the tape will not be left wasted but will be used. Therefore, according to the technology disclosed in the first embodiment, it is possible to suggest suitable uses of tapes in the system 100 that aims to share label data.

[0104] In response to a request to check the frequency of use of consumables from a terminal 12 (client application 13), the label management server 22 of the first embodiment notifies the terminal 12 of information on unused tapes for a user who is using the client application 13. This allows the user to check the notification on unused tapes at the timing when using the client application 13.

[0105] Second embodiment Next, a system according to the second embodiment will be described in detail with reference to the accompanying drawings. In the second embodiment, notification information is pushed to the terminal 12. This is different from the first embodiment in which notification information is sent to the terminal 12 in response to a request from the client application 13. Here, the same reference numerals are used to designate the same configurations and processes as those in the first embodiment, and descriptions thereof will be omitted as appropriate.

[0106] As shown in FIG. 11, every time the client application 13 of the terminal 12 instructs the label printer 11 to print label data, the client application 13 stores a print log relating to the printing in a memory (not shown) of the terminal 12 (J01).

[0107] When a predetermined execution requirement is met (J11), the label management server 22 requests the terminal 12 to send a print log (J12). The predetermined execution condition is, for example, a specified time such as the beginning of the month, or a predetermined number of print histories. The predetermined execution condition may be common to all users, or may be specified for each user.

[0108] When the label management server 22 acquires the print log from the terminal 12 (J13), it executes unused item detection processing (J14). J13 is an example of an "acquisition processing". Note that J12 to J13 may be processing for acquiring the print log from the print log DB 30.

[0109] After acquiring the print log, the label management server 22 performs the processes of H13 to H16 in the same manner as in the first embodiment, and generates notification information and label proposal information. The label management server 22 pushes the notification information and label management information to the terminal of the user who purchased the tape that has not been used for a certain period of time (J21). The client application 13 displays a recommendation screen based on the push-notified notification information and label management information (H18).

[0110] As described above, the label management server 22 of the second embodiment detects an unused tape when a predetermined execution condition defined in the label management server 22 is satisfied, and by pushing notification information to the terminal 12 of the user who purchased the detected tape, it is possible to notify the user of information about a tape that has been purchased but not used, even if the user is not using the client application 13.

[0111] It should be noted that the embodiments disclosed in this specification are merely examples and do not limit the present invention in any way. Therefore, the technology disclosed in this specification can be naturally improved and modified in various ways without departing from the scope of the invention. For example, the consumables may be consumables other than tape.

[0112] For example, S40 in Fig. 10 may detect consumables that have never been used since purchase. However, there is a possibility that a user has forgotten about a tape that has not been used for a certain period of time. Therefore, the label management server 22 detects a consumable that has not been used for a certain period of time as an unused consumable and notifies the user of its existence, so that the user can expect to resume use of the tape that he or she has forgotten.

[0113] For example, S42 and S43 in Fig. 10 may be omitted. However, if the same notification is repeated many times, the user may feel annoyed. Therefore, it is preferable not to notify the user of consumables for which the number of notifications is equal to or exceeds a threshold value.

[0114] For example, the purchase information update process shown in D04 of Fig. 7 may be omitted. However, there is a possibility that a new consumable item has been purchased for the consumable item that has been used. Therefore, the label management server 22 deletes the serial number of the used tape from the purchase information and excludes the used consumable item from the notification target, thereby avoiding the inconvenience of notifying the user of the used product and causing the user to feel annoyed.

[0115] For example, the label management server 22 may set a used flag indicating that the tape has been used, instead of deleting the serial number of the used tape from the purchase information in S18 of Fig. 8. Then, in S40 of Fig. 10, unused tapes may be detected from among serial numbers for which the used flag is not set.

[0116] For example, when there is a used consumable item, if the user has not purchased the same type of consumable item, the label management server 22 may notify the user to purchase the consumable item. This makes it possible to prompt the user to purchase a new consumable item when there is a used consumable item.

[0117] For example, H14 to H16 in Fig. 9 and Fig. 11 may be omitted. However, the label management server 22 also notifies the user of label data that can use the detected consumables and enables the user to download the label data, thereby promoting the use of the consumables.

[0118] For example, H15 in Figures 9 and 11 may be omitted. However, the label management server 22 obtains label data corresponding to unused tapes from the label DB 26 and excludes from it the label data posted by the user (requester) who made the consumable use frequency confirmation request, which makes it easier for the user to use label data created by another user, and promotes the use of label data.

[0119] 9(B) does not need to include thumbnail images 243a, 243b, 243c of the label data or link 244. However, including thumbnail images 243a, 243b, 243c makes it easier for the user to visualize a label created using an unused tape, encouraging downloading of the label data. Also, including link 244 reduces the number of operations required to download label data.

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

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

[0122] 11. Label Printer 12 Terminal 21 Internet connection 22 Label Management Server 25 User DB 100 Label Data Sharing System 221 CPU 228 Server Programs

Claims

1. a program executable by a server, the server being capable of accessing a purchase information database, the purchase information database being capable of registering, for each user ID, purchase information indicating a purchased consumable for printing label data, the consumable; A computer of the server, when receiving the purchase information associated with a user ID, executing a registration process for registering the received purchase information in the purchase information database in association with the user ID associated with the received purchase information; The server computer further comprises: a process for acquiring a print history relating to printing of the label data, the print history including usage information indicating consumables used to print the label data; The server computer further comprises: a detection process for detecting unused consumables among the consumables indicated in the purchase information registered in the purchase information database based on the print history acquired in the acquisition process; a notification process for notifying a user who purchased the consumable detected in the detection process of notification information indicating the consumable detected in the detection process; It is possible to execute A program that is configured to:

2. The program according to claim 1, The printing history includes the date and time when printing was performed, In the detection process, detecting consumables that have not been used for printing for a certain period of time from among the consumables indicated in the purchase information registered in the purchase information database based on the print history acquired in the acquisition process; A program that is configured to:

3. The program according to claim 1, A computer of the server, When a predetermined execution condition defined in the server is satisfied, the detection process and the notification process are executed; In the notification process, a push notification of the notification information indicating the consumable detected in the detection process to a terminal of a user who purchased the consumable detected in the detection process; A program that is configured to:

4. The program according to claim 1, A computer of the server, executes the detection process and the notification process in response to receiving a specific request associated with a user ID from an information processing device connected to the server; In the detection process, detecting unused consumables among the consumables indicated in the purchase information registered in the purchase information database, the purchase information corresponding to the user ID associated with the specific request, based on the print history acquired in the acquisition process; In the notification process, notifying the information processing device that transmitted the specific request of notification information indicating the consumable detected in the detection process; A program that is configured to:

5. The program according to claim 4, A computer of the server, executes the acquisition process, the detection process, and the notification process in response to receiving the specific request associated with a user ID from the information processing device connected to the server; In the acquisition process, a printing history is acquired by requesting the information processing device to transmit a printing history and receiving the printing history from the information processing device, and each time a command to print label data is issued, the information processing device stores the printing history relating to that printing in a memory of the information processing device; A program that is configured to:

6. The program according to claim 1, the server is capable of accessing a print history database, and the print history that is output each time an instruction to print label data is issued from an information processing device is registered in the print history database; In the acquisition process, acquiring the print history by reading the print history from the print history database; A program that is configured to:

7. The program according to claim 1, A computer of the server, executes a used-up detection process for detecting used consumables among the consumables indicated in the purchase information registered in the purchase information database based on the print history acquired in the acquisition process; In the detection process, detecting unused consumables other than the consumables detected in the used detection process, among the consumables indicated in the purchase information registered in the purchase information database, based on the print history acquired in the acquisition process; A program that is configured to:

8. The program according to claim 1, the server is capable of accessing a label database, a plurality of label data can be registered in the label database, the label data includes consumables information indicating usable consumables, A computer of the server, when a download request is received specifying one of the label data registered in the label database, a transmission process is executed to transmit the specified label data to a source of the download request; The server computer further comprises: executing a label notification process for notifying a user who has purchased the consumable detected in the detection process of the label data that can be used with the consumable detected in the detection process from the label database when the notification information is notified in the notification process; A program that is configured to:

9. The program according to claim 8, A computer of the server, an upload reception process is executed to receive a request to upload label data, the upload request being associated with a user ID; The server computer further comprises: when the upload request is accepted in the upload acceptance process, a label registration process is executed to receive posted label data which is label data uploaded from a request source of the upload request, associate the received posted label data with the user ID associated with the upload request, and register the associated data in the label database; In the label notification process, notifying a user who purchased the consumable detected in the detection process of the label data that can be used for the consumable detected in the detection process and that is associated with a user ID other than the user ID of the user who purchased the consumable detected in the detection process from the label database; A program that is configured to:

10. The program according to claim 1, A computer of the server, executing a counting process for counting the number of notifications by the notification process for each consumable detected by the detection process; In the notification process, notifying a user who purchased the consumable detected in the detection process of notification information indicating the consumable detected in the detection process when the number of notifications corresponding to the consumable detected in the detection process does not exceed a threshold value; A program that is configured to:

11. A server connectable to an information processing device via a network, The server, a purchase information database is accessible, and purchase information indicating a purchased consumable for printing label data can be registered in the purchase information database for each user ID; Furthermore, the server When receiving the purchase information associated with a user ID from the information processing device, a registration process is executed to register the received purchase information in the purchase information database in association with the user ID associated with the received purchase information; The server further comprises: a process for acquiring a print history relating to printing of the label data, the print history including usage information indicating consumables used to print the label data; The server further comprises: a detection process for detecting unused consumables among the consumables indicated in the purchase information registered in the purchase information database, the purchase information corresponding to a user ID of the user of the information processing device, based on the print history acquired in the acquisition process; a notification process of notifying the information processing device of notification information indicating the consumables detected in the detection process; It is possible to carry out It is configured as follows.

12. A system including an information processing device and a server, the information processing device being connectable to the server via a network, The server, a purchase information database is accessible, and purchase information indicating a purchased consumable for printing label data can be registered in the purchase information database for each user ID; The information processing device includes: The purchase information is associated with a user ID of the user of the information processing device and transmitted to the server; The server, when receiving the purchase information from the information processing device, registering the received purchase information in the purchase information database in association with the user ID associated with the received purchase information; The server further comprises: A printing history relating to printing of the label data can be obtained, the printing history including usage information indicating consumables used to print the label data, The server further comprises: Detecting unused consumables among the consumables indicated in the purchase information registered in the purchase information database, the purchase information corresponding to a user ID of the user of the information processing device, based on the acquired print history; notifying the information processing device of notification information indicating the detected consumable; The information processing device includes: when the notification information is received from the server, suggesting the use of the consumable item indicated in the received notification information; The system is configured as follows:

Images