Program, server, and label data sharing system

Abstract

The present invention provides a technique for promoting use of content in a system which facilitates use of label data.　A label management server 22 registers, in a post label database 25, post label data uploaded from a terminal (poster) 12A in association with a content ID indicating content included in the uploaded post label data. When a content item registered in a content database 26 has been selected by a terminal (purchaser) 12B, the label management server 22 executes: extraction processing for extracting, from the post label database 25, post label data items associated with a content ID indicating the selected content item, from among the post label data registered in the post label database; and presentation processing for presenting, to the terminal (purchaser) 12B, at least one of the post label data items extracted in the extraction processing.

Description

Program, server, and label data sharing system

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

[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 that utilize label data used to print labels with label printers have been under consideration. Label data can be combined with various content, allowing users to create a wide variety of label data by utilizing the content. In order to promote the use of label data in such systems, it is desirable to encourage many users to utilize the content available in the label data. Patent Document 1 does not mention anything about promoting the use of content, leaving room for improvement.

[0006] The technology disclosed in this specification aims to realize a technology that promotes the use of content in a system that aims to use label data.

[0007] and a presentation process for presenting at least one of the label data extracted in the extraction process to the second information processing device. The program is designed to solve the above-mentioned problem and is executable by a server, the server having access to a label database in which a plurality of label data can be registered and a content database in which a plurality of contents can be registered, the label data being data that can be printed by a label printer and the content being usable by the label data. The program is configured to: cause a computer of the server, when label data is uploaded from a first information processing device, to perform a registration process for registering the uploaded label data in the label database, associating the uploaded label data with content information indicating the content included in the uploaded label data; further cause the computer of the server, when one of the contents registered in the content database is selected from a second information processing device, to perform an extraction process for extracting, from the label data registered in the label database, the label data associated with the content information indicating the selected content; and a presentation process for presenting at least one of the label data extracted in the extraction process to the second information processing device; and further cause the computer of the server, when an instruction to download the selected content is received from the second information processing device, to perform a content transmission process for transmitting the selected content to the second information processing device.

[0008] According to the technology disclosed in this specification, label data uploaded by various users is registered in a label database in association with content information of the content contained in the label data. When a selection to download content is received from a certain user, the label data containing the selected content is extracted from the label database and presented. This makes it easier for the user who selected the content to imagine how the content will be used based on the label data created by other users, thereby encouraging downloading of the content.

[0009] A server for realizing the functions of the above-mentioned device and a label data sharing system are also novel and useful.

[0010] According to the technology disclosed in this specification, a technology is realized that promotes the use of content in a system that aims to use label data.

[0011] 1 is an explanatory diagram schematically showing a label data sharing system of the present embodiment. FIG. 1 is a schematic explanatory diagram showing the electrical configurations of a label management server and a print log server. (A) An explanatory diagram showing an example of user-related information stored in a user database. (B) An explanatory diagram showing an example of posted label-related information stored in a posted label database. (C) An explanatory diagram showing an example of content-related information stored in a content database. (D) An explanatory diagram showing an example of print log-related information stored in a print log database. FIG. 2 is a sequence diagram showing an example of the procedure for a label posting process provided to a user by a label management server program of a label management server, including the operation of a client application of the terminal. FIG. 3 is an explanatory diagram schematically showing a terminal when a new posted label is posted. FIG. 4 is a sequence diagram showing an example of the procedure for a content data download process provided to a user by a label management server program of a label management server, including the operation of a client application of the terminal. (A) An explanatory diagram schematically showing a terminal when content data is downloaded. (B) An explanatory diagram schematically showing a terminal when content data is downloaded. FIG. 11 is a sequence diagram showing an example of the procedure for downloading content data provided to a user by a label management server program of a label management server, including the operations of a printer app of a printer and a client app of a terminal, according to a second embodiment.

[0012] First Embodiment A label data sharing system 100 according to the present embodiment will be described in detail below with reference to the drawings. FIG.

[0013] 1 , the label data sharing system 100 of this embodiment is a system provided to users by the vendors (manufacturers) of the printers 11A and 11B. In the label data sharing system 100 of this embodiment, owners or users (hereinafter referred to as users) of the printers 11A and 11B can post label data to be printed by the printers 11A and 11B from their own terminals 12A and 12B, i.e., upload the label data to the label management server 22. In the label data sharing system 100 of this embodiment, the users of the printers 11A and 11B can download label data from the label management server 22 to their own terminals 12A and 12B, and then create labels by printing based on the label data using the printers 11A and 11B connected to the terminals 12A and 12B. The terminal 12A is an example of a first information processing device, and the terminal 12B is an example of a second information processing device.

[0014] Terminals 12A and 12B are configured as smartphones owned by the users, but may also be configured as tablets or personal computers. Terminals 12A and 12B also store various application programs (hereinafter referred to as apps), such as client apps 13A and 13B provided to users by the vendors of printers 11A and 11B. The client apps 13A and 13B have functions for creating and editing labels on terminals 12A and 12B. The client apps 13A and 13B also have a function for uploading created label data to the label management server 22.

[0015] The client applications 13A and 13B also have a function for downloading label data from the label management server 22. The client applications 13A and 13B also have a function for printing label data created on the terminals 12A and 12B or downloaded label data using the printers 11A and 11B. The printers 11A and 11B may be collectively referred to as the "printer 11" when there is no need to distinguish between them. The terminals 12A and 12B may be collectively referred to as the "terminal 12" when there is no need to distinguish between them. The client applications 13A and 13B may be collectively referred to as the "client application 13" when there is no need to distinguish between them.

[0016] Printers 11A and 11B also store printer applications 14A and 14B for controlling printing by printers 11A and 11B. Tape cassettes 15A and 15B are installed in printers 11A and 11B, and long tapes (not shown) for printing labels are wound in tape cassettes 15A and 15B. The printers are an example of label printers, and tape is an example of print media.

[0017] The printer 11 is configured as a label printer capable of printing labels, but may also be an inkjet printer or laser printer. The 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). The printer 11 and terminal 12 may also be connected via a wired connection using the USB communication standard.

[0018] Next, the label management server 22 and print log server 23 that make up the label data sharing system 100 of this embodiment will be described. The label management server 22 and print log server 23 are each connected to a large number of terminals 12 via an Internet line 21. The label management server 22 and print log server 23 may be connected via the Internet line 21, or via a wired LAN line 27. A user database 24, a submitted label database 25, and a content database 26 are also connected to the label management server 22 so that they can access it. A print log database 28 is also connected to the print log server 23 so that they can access it. The label management server is an example of a server.

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

[0020] The storage device 224 is configured by, for example, an HDD, a flash memory, or the like, and stores a label management server program 228 and various processing programs.

[0021] The CPU 221 executes various processes in accordance with programs read from the ROM 222 or the storage device 224 .

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

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

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

[0025] 2, the print log server 23 has a CPU 231, a ROM 232, a RAM 233, a storage device 234, a network interface 235, an operation display unit 236, and an interface 237. The ROM 232 stores a startup program for starting the print log server 23. The RAM 233 is used as a work area when various processes are executed, or as a storage area for temporarily storing data.

[0026] The storage device 234 is configured by, for example, an HDD, a flash memory, or the like, and stores a print log server program 238 and various processing programs.

[0027] The CPU 231 executes various processes in accordance with programs read from the ROM 232 or the storage device 234 .

[0028] In this embodiment, the network interface 235 is configured by an interface conforming to the wired LAN communication standard. Alternatively, the network interface 235 may be, for example, an interface conforming to the wireless LAN communication standard such as Wi-Fi, an interface conforming to the USB communication standard, or an interface conforming to the short-range wireless communication standard such as Bluetooth. The network interface 235 is connected to the network interface 225 of the label management server 22 via the wired LAN line 27.

[0029] The operation display unit 236 is configured by, for example, a display device and a touch panel arranged on the display device, etc. The display device displays necessary information, and the touch panel accepts inputs from the user.

[0030] In this embodiment, the interface 237 is configured by an interface conforming to the communication standard of a wired LAN, and is connected to the print log database 28. The print log database 28 may be included in the print log server 23.

[0031] The user database 24 stores user-related information 30 shown in Fig. 3A as a table. The user-related information 30 is composed of a user ID 301, a user name 302, point information 303, a password 304, acquired content information 305, etc. for each user.

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

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

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

[0035] The password 304 is a password set by each user stored in the user name 302. The acquired content information 305 stores the content ID of the content purchased by the user.

[0036] 3B is stored as a table. The posted label database 25 stores posted label related information 40 shown in Fig. 3B. For each label data posted in the label data sharing system 100 of this embodiment, the posted label related information 40 includes a label ID 401, a user ID 402, a download count 403, a print count 404, posted label data 405, a content ID 406, tape size information 407, tape color information 408, a posting date 409, model number information (not shown) of the printer set to print the posted label data, and version information (not shown) of the client application 13 of the terminal 12 that created the posted label data.

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

[0038] Posted label data 405 is posted label data, and indicates the configuration of the label. Specifically, label data is composed of fonts, pictograms, character images, decorative images, frames, content, and layout information thereof. Content ID 406 stores the content ID of the content included in the posted label data 405. The content ID is an example of content information.

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

[0040] The content database 26 stores content-related information 50 shown in FIG. 3C as a table. The content-related information 50 is composed of a content ID 501, content information 502, etc. The content ID 501 is a serial number assigned sequentially to each piece of content registered in the content database 26 in the label data sharing system 100 of this embodiment. The content information 502 stores content data provided to users by the vendors (manufacturers) of the printers 11A and 11B. Note that the content data may be submitted by users using the label data sharing system 100 of this embodiment. The content data is composed of art such as special fonts, pictograms, special frames, character images, and decorative images.

[0041] The print log database 28 stores print log-related information 60 shown in Fig. 3D as a table. The print log-related information 60 includes a print date and time 601, a user ID (purchaser) 602, a label ID 603, paper print size information 604, and the number of prints 605.

[0042] The print date and time 601 is the date and time when the label was printed by the printer 11 in the label data sharing system 100 of this embodiment. The user ID (purchaser) 602 is the user ID 301 of the user who printed the label using the printer 11. The label ID 603 is the label ID 401 of the label printed by the printer 11. The paper print size information 604 is print size information of the print paper (label) when the user printed using the printer 11 in the label data sharing system of this embodiment, that is, in this embodiment, information on the width and length of the print paper. The number of prints 605 is the number of labels printed by the printer 11.

[0043] In the label data sharing system 100 of this embodiment, the number of prints 404 in the posted label related information 40 is updated based on the label ID 603 and number of prints 605 in the print log related information 60. The update may be performed periodically at predetermined intervals, or may be performed every time the print log related information 60 is updated.

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

[0045] Note that each processing step in this embodiment basically indicates processing by the CPU 221 in accordance with instructions written in programs such as the label management server program 228. Processing by the CPU 221 also includes hardware control using the API of the OS. In this specification, detailed description of the OS will be omitted and the operation of each program will be explained.

[0046] In the label posting process of this embodiment, a user (hereinafter referred to as the poster) who wishes to post label data first launches the client application 13A on the terminal (poster) 12A. Then, on the terminal (poster) 12A, the client application 13A displays an editing screen for creating label data 31, such as that shown in FIG. 5 , and accepts the creation of the label data 31 (step 11 (hereinafter referred to as T11)). The label data 31 shown in FIG. 5 is composed of content data 32 that the poster has already purchased and text data 33 that the poster has manually entered on the terminal (poster) 12A. The content data 32 that the poster has already purchased is composed of art such as special fonts, pictograms, character images, and decorative images. The text data 33 may also be content composed of special fonts that the poster has already purchased.

[0047] In addition, the terminal (contributor) 12A displays a "Tape Color" button 121 for setting the tape color information of the label data 31 created by the contributor, a "Tape Length" button 122 for setting the tape length of the label data 31, and the like.

[0048] Therefore, the contributor can set the color of the tape for the label data 31 by touching the "Tape Color" button 121. Also, the contributor can set the length of the tape for the label data 31 by touching the "Tape Length" button 122.

[0049] Thereafter, when the poster touches the "New Post" button 123 displayed on the terminal (contributor) 12A, the client application 13A of the terminal (contributor) 12A sends the poster's user ID, the submitted label data which is the label data 31 created by the poster, tape size information suitable for printing the label data 31 as set by the poster, tape color information of the label data 31 as set by the poster, etc. to the label management server 22 (T12). For example, the label management server program 228 provides a web page for submission, and the web page is displayed by the browser function of the client application 13A. The user enters his / her user ID when logging in to the label management server 22 via the web page, and then enters an instruction to send the label data 31 via the web page, whereby the submitted label data, etc. are uploaded to the label management server 22. Note that before sending the label data 31, a screen for attaching explanatory text about the label data 31 and / or a photo image of an example of use of the label data 31 may be displayed, and the received supplementary data may be sent together with the label data 31.

[0050] Then, the label management server 22, which has received the label data 31 etc. sent from the terminal (contributor) 12A, stores the received label data 31 etc. in the posted label database 25 (T13). Hereinafter, the label data stored in the posted label database 25 will also be referred to as posted label data.

[0051] Specifically, the label management server 22 creates a new label ID and stores it in the posted label database 25 as a new label ID 401 of the posted label-related information 40. Thereafter, in the table of the posted label-related information 40 corresponding to the new label ID 401, the following are stored: the user ID 301 of the receiving poster as user ID (creator) 402, the received posted label data as posted label data 405, the content ID of the content data included in the received posted label data as content ID 406, the received tape size information as tape size information 407, the received tape color information as tape color information 408, and the posting date as posting date 409. Note that if supplementary data is received along with the posted label data, the supplementary data is stored in association with the label ID of the posted label data.

[0052] Next, the label management server 22 sends a "registration complete" to the terminal (contributor) 12A (T14). Then, upon receiving the "registration complete" message, the terminal (contributor) 12A displays on its display unit a message that the registration of the submitted label data has been completed, thereby notifying the contributor (T15). This lets the contributor know that the submitted label data 31 has been registered in the label data sharing system.

[0053] (Content data download process) Next, an example of the procedure for the download process of content data provided to the user by the label management server program 228 of the label management server 22, including the operation of the client application 13B of the terminal 12B in this embodiment, will be described with reference to the sequence diagram of Figure 6.

[0054] In the content data download process of this embodiment, first, a user (hereinafter referred to as the purchaser) who wishes to download content data starts the client application 13B of the terminal (purchaser) 12B, and then touches the "Point Content" tab 125 (see FIG. 7) displayed on the terminal (purchaser) 12B by the client application 13B of the terminal (purchaser) 12B (T21). The terminal (purchaser) 12B then requests the label management server 22 to display a list of content data (T22). For example, the label management server program 228 provides a web page for login, and the web page is displayed by the browser function of the client application 13B. The user ID is entered via the web page, and the user ID is transmitted. After the login is approved, when the user touches the "Point Content" tab 125 displayed on the terminal (purchaser) 12B, the label management server 22 receives a request to display a list of content data.

[0055] Next, the label management server 22, which has received the request to display a list of content data, extracts from the content database 26 the content data stored as content information 502 in the content-related information 50, together with the content ID stored as the content ID 501. At this time, if the extracted content ID is already stored in the acquired content information 305 corresponding to the purchaser in the user-related information 30 shown in Fig. 3(A), the label management server 22 excludes the content data and content ID (T23).

[0056] In this manner, in this embodiment, if the extracted content ID at T23 is already stored in the acquired content information 305 corresponding to the purchaser as shown in Fig. 3A, the content data and content ID are excluded, thereby preventing the purchaser from mistakenly being presented with content data that the purchaser has already acquired. In other words, it is possible to prevent the purchaser from purchasing content data twice.

[0057] At this time, in T23, the extracted content data and content IDs may be sorted in descending order of the number of times of printing based on the number of times of printing 404 and the content ID stored in content ID 406 of the post label related information 40 shown in Figure 3 (B), and presented to the purchaser.

[0058] In this case, it is also acceptable to sort using the download count 403 instead of the print count 404, or to sort using a combined value of the download count 403 and the print count 404.

[0059] In this manner, in this embodiment, if the content data and content ID extracted in T23 are sorted based on the number of downloads 403 and the number of prints 404 of the post label related information 40 shown in FIG. 3(B), content data that is popular with the purchaser can be presented to the purchaser on the terminal (purchaser) 12B in order of priority, thereby improving convenience.

[0060] Thereafter, the label management server 22 transmits a list screen showing a list of the content data extracted in T23 to the terminal (purchaser) 12B (T24).

[0061] In this case, in this embodiment, the content data list screen sent to the terminal (purchaser) 12B may display thumbnail data and points required for purchase in addition to the title of the content data.

[0062] Next, the terminal (purchaser) 12B that has received the content data list screen displays the received list screen on the display unit of the terminal (purchaser) 12B (T25). For example, the label management server program 228 provides a web page for selecting content data, and the web page is displayed by the browser function of the client application 13B, and the list screen of the content data 32 is displayed via the web page.

[0063] 7A, for example, a plurality of content data 32 are displayed on the display unit of the terminal (purchaser) 12B together with thumbnails and titles of the content data 32. Also, below each content data 32, the number of points 34 required to purchase the content data 32 is displayed.

[0064] When the purchaser selects one of the plurality of content data 32 displayed on the display unit of the terminal (purchaser) 12B, the user ID of the downloader (purchaser) and the content ID of the selected content data 32 are input from the terminal (purchaser) 12B to the label management server 22, and a detailed display of the content data corresponding to the selected content data 32 is requested (T26).

[0065] Then, the label management server 22, which has received the request to display details of the content data, extracts, from the content database 26, a record of the content data stored in the content information 502 for the requested content data based on the requested content ID. The label management server 22 also searches the posted label database 25 based on the requested content ID, and, for posted label data whose content ID stored in content ID 406 matches the content ID of the requested content data, extracts posted label data 405, the posted label data stored in label ID 401, and the label ID (T27). In other words, posted label data in which the requested content data is used is extracted from the posted label database 25. T27 is an example of an extraction process.

[0066] Next, the label management server 22 sorts the extracted posted label data and label IDs in descending order of the number of prints based on the number of prints 404 in the posted label related information 40 shown in Fig. 3(B) (T28). Note that in this case, sorting may be done using the number of downloads 403 instead of the number of prints 404, or may be done using a combined value of the number of downloads 403 and the number of prints 404. Note that the number of downloads and the number of prints are examples of evaluation values.

[0067] Furthermore, the number of downloads 403 and the number of prints 404 may be limited to a certain period, and for example, each time the terminal 12 prints label data, a record associating the label ID of the label data with the date and time of printing is registered as the print history in the print log database 28. Therefore, the print log database 28 may be referenced to use the number of prints for each label data item over the past week or past year.

[0068] In this way, in this embodiment, posted label data that has been downloaded or printed many times can be said to be popular posted label data, and is likely to be a suitable example of content data. Therefore, by presenting the extracted posted label data in order of popularity, it becomes easier for purchasers to imagine a more suitable form of use for the content data.

[0069] Next, the label management server 22 limits the sorted post label data and label IDs to post label data whose length is equal to or less than a threshold based on the tape length information stored in the tape size information 407 of the post label related information 40 shown in Fig. 3 (B) (T29). In other words, of the sorted post label data and label IDs, post label data whose length exceeds the threshold is excluded. The threshold can be any value, such as 100 mm or 80 mm, depending on the screen size of the terminal (purchaser) 12B.

[0070] In this manner, in this embodiment, the sorted posted label data is limited to posted label data whose length is equal to or less than the threshold, so long posted label data is not posted. If the length of the posted label data is long, it will not fit on the screen of the terminal (purchaser) 12B, making it difficult for the user to check, so by excluding such posted label data from the list of items to be posted, it becomes easier for the purchaser to check the usage pattern of the posted label data.

[0071] Furthermore, the label management server 22 can limit the number of posted label data after the limiting process in T29 to N in order of popularity. Note that the number N can be any value, such as 10 or 20, depending on the screen size and functions of the terminal (purchaser) 12B. The number N may also be a value set by the purchaser.

[0072] In this way, in this embodiment, by limiting the number of posted label data presented to the top N most popular items, it becomes easier for the purchaser to confirm the usage pattern of the content data. In other words, if a large number of posted label data are presented, the display on the screen of terminal (purchaser) 12B becomes cluttered, making it difficult for the purchaser to confirm the usage pattern of the content data. In this embodiment, by setting an upper limit on the number of posts, such a problem can be resolved.

[0073] In this embodiment, the label management server 22 is configured to limit the number of posted label data items to N in order of popularity after limiting the sorted posted label data items to those whose length is equal to or less than a threshold in the process of T29, but this is not limitative. For example, it goes without saying that the label management server 22 may be configured to limit the number of posted label data items to N in order of popularity without executing the process of limiting the posted label data items to those whose length is equal to or less than a threshold. Furthermore, the processes of T28 and T29 may be performed in the reverse order.

[0074] Next, the label management server 22 transmits to the terminal (purchaser) 12B a details screen including information indicating the content data for which the detailed display request was made, posted label data limited to N in order of popularity, label IDs, etc. (T30). If an example image of use is associated with the content data for which the detailed display request was made and registered in the posted label database 25, the example image of use may also be read out and included in the details screen. The processing of T30 is an example of a presentation process.

[0075] On the other hand, the terminal (purchaser) 12B that has received the details screen from the label management server 22 displays the details screen on its display unit (T31), for example, as shown in Fig. 7(B) , and then accepts the download, i.e., purchase, of the selected content data.

[0076] Specifically, the display unit of the terminal (purchaser) 12B displays the selected content data 32, the number of points 34 required to purchase the content data 32, and the number of points 35 currently held by the purchaser. Also, below the "Exchange" button 36, thumbnails of the posted label data 31 extracted by T27 are displayed. Multiple pieces of posted label data 31 may be displayed simultaneously, or may be displayed sequentially in accordance with a scroll operation. Furthermore, if a usage example image is associated with the extracted posted label data 31, a usage example image 37 of the posted label data 31 is displayed to the left of the displayed label data 31.

[0077] In this manner, in this embodiment, the posted label data 31 using the selected content data 32 and an example image 37 of how to use the posted label data 31 are displayed together with the selected content data 32, making it easier for the purchaser to imagine how the content data 32 will be used, which encourages the purchase of the content data.

[0078] Next, when the purchaser touches the "Exchange" button 36, the terminal (purchaser) 12B transmits a request to download the selected content data 32 to the label management server 22 (T32).

[0079] Next, when a download is requested, the label management server 22 transmits the selected content data 32 to the terminal (purchaser) 12B (T33). The processing of T33 is an example of content transmission processing. Furthermore, for a user whose user ID 301 in the user-related information 30 shown in FIG. 3A matches the received user ID, the label management server 22 subtracts the number of points required for the point exchange processing from the number of points stored in the point information 303. Furthermore, the label management server 22 stores the content ID of the content data 32 for which points have been exchanged this time in the acquired content information 305 (T34).

[0080] Furthermore, the terminal (purchaser) 12B that has received the content data stores the content data 32 in a non-volatile storage unit (not shown) (T35).

[0081] In this embodiment, the content data 32 is purchased by a point exchange process using points owned by the downloader (purchaser), but it goes without saying that it may also be purchased by cash.

[0082] In this manner, in this embodiment, the posted label data 31 is registered in the posted label database 25 in association with the content ID of the content data 32 included in the posted label data 31, and when a selection to download the content data 32 is received, the posted label data 31 including the selected content data 32 is extracted from the posted label database 25 and presented, making it easier for the purchaser to imagine how the content data 32 will be used, and promoting the downloading of the content data 32.

[0083] 7(B) , while the posted label data 31 extracted in T27 is displayed, the displayed posted label data 31 may be made available for download. In this case, the label management server 22 may be configured to accept a download instruction via the details screen when one or more posted label data 31 are selected from the posted label data 31, and when the download instruction is received from the purchaser (T36), the label management server 22 transmits the posted label data of the selected one or more label data 31 to the terminal (purchaser) 12B (T37), and the terminal (purchaser) 12B stores the received posted label data in a storage unit (T38). In this case, being able to download the displayed label data 31 can promote the use of content data including the target content.

[0084] Second Embodiment Next, an example of the procedure for downloading content data provided to a user by the label management server program 228 of the label management server 22, including the operations of the printer application 14B of the printer 11B and the client application 13B of the terminal 12B, will be described with reference to the sequence diagram of Fig. 8. In this description, the same components as those in the first embodiment will be denoted by the same reference numerals.

[0085] That is, in this embodiment, the label management server 22 restricts the posted label data and its label ID extracted in the process of T27 based on the printer information acquired from the printer 11B connected to the terminal (purchaser) 12B in the process of T45.

[0086] In FIG. 8, when the label management server 22 receives a request for details of the content data corresponding to the selected content data 34 in the process of T26, it requests printer information from the terminal (purchaser) 12B (T41).

[0087] Next, the terminal (purchaser) 12B that has received the request for printer information requests the printer information from the printer 11B connected thereto (T42).

[0088] Next, upon receiving the request for printer information, printer 11B collects information such as the tape width information of the tape wound in tape cassette 15B set in itself, tape color information, and printer 11B model number information, and then transmits this information as printer information to terminal (purchaser) 12B (T43).

[0089] Next, the terminal (purchaser) 12B that has received the printer information sent from the printer 11B sends the received printer information to the label management server 22, and the label management server 22 receives the printer information (T44). The processing in T44 is an example of width acquisition processing.

[0090] Next, the label management server 22 that has received the printer information restricts the submitted label data and its label ID extracted in the process of T27 based on the printer information acquired from the printer 11B connected to the terminal (purchaser) 12B (T45).

[0091] Specifically, in T45, the label management server 22 can limit the submitted label data and its label ID extracted in the process of T27 to submitted label data whose width information matches the tape width information of the tape obtained from the printer 11B and is stored in the tape size information 407. Note that the width information stored in the tape size information is an example of first medium information, and the tape width information of the tape obtained from the printer is an example of second medium information.

[0092] In this case, if the tape width of the posting label data differs from the tape width of the tape set in printer 11B, it will be difficult for the purchaser to use the content. Therefore, by excluding posting labels that differ from the tape width of the tape set in printer 11B from the presented items, it becomes easier for the purchaser to imagine how the content will be used.

[0093] Furthermore, in the process of T45, the label management server 22 can limit the posted label data and its label ID extracted in the process of T27 to posted label data whose tape color information matches the tape color information obtained from the printer 11B and is stored in the tape color information 408. Note that the color information stored in the tape color information is an example of first medium information, and the tape color information obtained from the printer is an example of second medium information.

[0094] In this case, by excluding from the presented items the submitted label data that does not match the characteristics of the tape acquired from the terminal (purchaser) 12B, i.e., the color of the tape, more suitable label data can be presented to the user.

[0095] Furthermore, in the process of T45, the label management server 22 can limit the posted label data and its label ID extracted in the process of T27 to posted label data for which model number information that matches the characteristics of the model number information of printer 11B obtained from printer 11B is stored in the posted label database 25. Note that the model number information stored in the posted label database is an example of first printer information, and the printer model number information obtained from the posted label data printer is an example of second printer information.

[0096] In this case, by excluding from the presented list any posted label data that does not contain features that match the printer features acquired from the terminal (purchaser) 12B, more suitable posted label data can be presented to the purchaser. Note that the model number information of the printer 11B may be the model number information of the printer 11B set in the client application 13B of the terminal (purchaser) 12B. The model number of the printer 11B in the client application 13B of the terminal (purchaser) 12B can be set after touching the "Print Settings" button 124.

[0097] Furthermore, in the process of T45, the label management server 22 can limit the posted label data and its label ID extracted in the process of T27 to posted label data whose version information matches the characteristics of the client application 13B acquired from the terminal (purchaser) 12B, for example, the version information, stored in the posted label database 25. Note that the version information stored in the posted label database is an example of first app information, and the version information of the client application is an example of second app information.

[0098] In this case, by excluding from the presented items posted label data that does not contain features that match the version information acquired from the terminal (purchaser) 12B, more suitable posted label data can be presented to the purchaser.

[0099] In this embodiment, by using any one or a combination of the printer information, such as tape width information of the tape wound in the tape cassette 15B, tape color information, and model number information of the printer 11B, the label management server 22 can restrict the submitted label data and its label ID extracted in the process of T27 in the process of T45.

[0100] Furthermore, in this embodiment, the label management server 22 may execute the process of T29 in the first embodiment in the process of T45, i.e., the process of limiting the length of the posted label data to posted label data that is equal to or less than a threshold value, based on the tape length information stored in the tape size information 407 of the posted label-related information 40 shown in FIG. 3(B), for the sorted posted label data and label IDs.

[0101] As explained in detail above, in the label data sharing system 100 of the embodiment, uploaded post label data 31 is registered in the post label database 25 in association with content information of the content data 32 included in the post label data 31, and when a selection to download the content data 32 is accepted, the post label data 31 including the selected content data 32 is extracted from the post label database 25 and presented to the purchaser. This makes it easier for the purchaser to imagine how the content will be used, and encourages downloading of the content.

[0102] 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 of the invention. Furthermore, the number of printers connected to the terminal is not limited to the illustrated example, and may be two or more.

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

[0104] Furthermore, in this embodiment, when the label management server 22 receives a request for details of the content data corresponding to the selected content data 32 in the process of T26, it is configured to request printer information from the terminal (purchaser) 12B. However, it may also be configured so that when the purchaser selects one of the multiple content data 32 displayed on the display unit of the terminal (purchaser) 12B (T25), the terminal (purchaser) 12B transmits the printer information to the label management server 22 together with the user ID of the downloader (purchaser) and the content ID of the selected content data 32.

[0105] In addition, in this embodiment, the posted label database 25 stores posted label data posted by the poster, but the posted label database 25 may also store label data prepared in advance by the vendor (manufacturer) of the printer 11A and the printer 11B.

[0106] Furthermore, in this embodiment, the content data is composed of art such as special fonts, pictograms, character images, and decorative images, but it may also be a function for changing the number of label data that can be saved on the terminal 12. In this case, by touching and purchasing the "Change number of saved data" button 38 shown in FIG. 7(A), it is possible to increase the number of label data that can be saved on the terminal 12.

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

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

[0109] 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 be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method.

[0110] 100 Label data sharing system 11B Printer 12B Terminal (purchaser) 22 Label management server 23 Print log server 24 User database 25 Posted label database 26 Content database 31 Label data 32 Content data 33 Font data

Claims

1. A program executable by a server, the server having access to a label database in which a plurality of label data can be registered and a content database in which a plurality of contents can be registered, the label data being data that can be printed by a label printer, and the contents being usable by the label data; causing a computer of the server to: when label data is uploaded from a first information processing device, execute a registration process of registering the uploaded label data in the label database in association with content information indicating the content included in the uploaded label data; further causing the computer of the server to: when one of the contents registered in the content database is selected from a second information processing device, execute an extraction process of extracting, from the label data registered in the label database, the label data associated with the content information indicating the selected content; and a presentation process of presenting at least one of the label data extracted in the extraction process to the second information processing device; and further causing the computer of the server to execute a content transmission process of transmitting the selected content to the second information processing device when a download instruction for the selected content is received from the second information processing device.

2. A program as claimed in claim 1, wherein the label data registered in the label database is associated with an evaluation value serving as an index of popularity, and in the presentation process, the plurality of label data extracted in the extraction process are arranged in order of popularity based on the evaluation value associated with the extracted label data, and presented to the second information processing device.

3. A program as described in claim 2, wherein the presentation process is configured to arrange up to N pieces of the label data extracted in the extraction process in order of popularity based on the evaluation values ​​associated with the extracted label data, and present them to the second information processing device.

4. A program as claimed in claim 1, wherein the extraction process is configured to extract, from the label data registered in the label database, label data associated with content information indicating the selected content and which satisfies extraction conditions for limiting the presentation targets.

5. A program as claimed in claim 4, wherein the extraction condition is that the length of the label indicated in the label data is shorter than a threshold value.

6. A program as claimed in claim 4, configured to cause the computer to execute a width acquisition process for acquiring a label width from the second information processing device, and the extraction condition being that the label width indicated in the label data matches the width acquired in the width acquisition process.

7. A program as described in claim 4, wherein the label data includes first medium information indicating characteristics of the print medium, and the computer is caused to execute a medium acquisition process to acquire second medium information indicating characteristics of the print medium from the second information processing device, and the extraction condition is that the characteristics indicated in the first medium information included in the label data match the characteristics indicated in the second medium information acquired in the medium acquisition process.

8. A program as recited in claim 4, wherein the label data includes first printer information indicating printer characteristics, and the computer is caused to execute a printer acquisition process to acquire second printer information indicating printer characteristics from the second information processing device, and the extraction condition is that the characteristics indicated in the first printer information included in the label data match the characteristics indicated in the second printer information acquired in the printer acquisition process.

9. A program as recited in claim 4, wherein the label data includes first app information indicating characteristics of an editing app, which is an application program capable of editing label data; and the computer is caused to execute an app acquisition process for acquiring second app information indicating the characteristics of the editing app from the second information processing device; and the extraction condition is that the characteristics indicated in the first app information included in the label data match the characteristics indicated in the second app information acquired in the app acquisition process.

10. A program as recited in claim 1, configured to cause the computer to execute a label transmission process that receives an instruction to download the presented label data while the label data is being presented to the second information processing device by the presentation process, and transmits the presented label data to the second information processing device when the instruction to download the label data presented by the presentation process is received from the second information processing device.

11. A server connectable to a first information processing device and a second information processing device via a network, the server having access to a label database in which a plurality of label data can be registered and a content database in which a plurality of contents can be registered, the label data being data that can be printed by a label printer, and the contents being usable by the label data; when label data is uploaded from the first information processing device, the server executes a registration process for registering the uploaded label data in the label database in association with content information indicating the content included in the uploaded label data; when one of the contents registered in the content database is selected from the second information processing device, the server executes an extraction process for extracting, from the label data registered in the label database, the label data associated with the content information indicating the selected content, and a presentation process for presenting at least one of the label data extracted in the extraction process to the second information processing device; and when an instruction to download the selected content is received from the second information processing device, the server executes a content transmission process for transmitting the selected content to the second information processing device.

12. 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 a plurality of label data can be registered, and a content database in which a plurality of contents can be registered, the label data being data that can be printed by a label printer, and the content being usable by the label data, the first information processing device being able to upload the label data stored in the first information processing device to the server, the server being able to associate the label data uploaded from the first information processing device with content information indicating the content included in the uploaded label data, and registering the associated label data in the label database, the second information processing device being able to select one of the contents registered in the content database, the server being able to, when the content is selected from the second information processing device, extract the label data associated with the content information indicating the selected content from the label data registered in the label database, and present at least one of the extracted label data to the second information processing device, the second information processing device being able to and wherein the selected content is downloadable from the server.

Images