Program, server, and label data sharing system
Patent Information
- Application Number
- JP2023139808
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-08-30
- Publication Date
- 2025-03-13
AI Technical Summary
【0010】 本明細書に開示される技術によれば、ラベルデータの利用を図るシステムにおいて、コンテンツの利用が促進される技術が実現される。
Smart Images

Figure 2025033814000001_ABST
Abstract
Description
[Technical field]
[0001] The technical field disclosed in this specification relates to a program, an information processing device, and a label data sharing system used in a system that utilizes label data. [Background technology]
[0002] Conventionally, a system for utilizing content data is known in which a server for storing content data is provided on the Internet, content data is posted from a user's device, i.e., uploaded to the server, and the content data is then downloaded to another user's device.
[0003] An example of a document disclosing the above-mentioned system is Patent Document 1. In the point management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and purchased by User B's PC and downloaded from the WWW server, points are added to User B, the purchaser, according to the purchase amount, and further points are added to User A, the contributor, according to the data size of the photo data when the photo data is uploaded or downloaded. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2002-99746 A Summary of the Invention [Problem to be solved by the invention]
[0005] In recent years, systems that utilize label data used to print labels with a label printer have been considered. Label data can be combined with various contents, and users can create a wide variety of label data by using the contents. In order to utilize the label data in such a system, it is desirable for many users to utilize the contents available in the label data. Patent Document 1 does not include any description regarding the promotion of content utilization, so there is 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 utilize label data. [Means for solving the problem]
[0007] The present invention has been made to solve the above-mentioned problems, and is a program executable by a server, the server being able to access a label database in which a plurality of label data items can be registered, and a content database in which a plurality of contents items can be registered, the label data items being data that can be printed by a label printer, and the contents items being usable with the label data, A computer of the server, executing a registration process for, when label data is uploaded from a first information processing device, associating the uploaded label data with content information indicating content included in the uploaded label data and registering the associated data in the label database; Further, the computer of the server When one of the contents registered in the content database is selected from the second information processing device, 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; a presentation process of presenting at least one of the label data extracted in the extraction process to the second information processing device; Run the command, Further, the computer of the server when a download instruction for the selected content is received from the second information processing device, executing a content transmission process of transmitting the selected content to the second information processing device; It is structured as follows.
[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 including the selected content is extracted from the label database and presented, making 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 promoting downloading of the content.
[0009] A server for implementing the functions of the above-mentioned device and a label data sharing system are also novel and useful. Effect of the Invention
[0010] According to the technology disclosed in this specification, a technology is realized that promotes the use of content in a system that aims to utilize label data. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 is an explanatory diagram illustrating a label data sharing system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a schematic explanatory diagram showing the electrical configuration of a label management server and a print log server. [Diagram 3](A) is an explanatory diagram showing an example of user-related information stored in a user database, (B) is an explanatory diagram showing an example of posted label-related information stored in a posted label database, (C) is an explanatory diagram showing an example of content-related information stored in a content database, and (D) is an explanatory diagram showing an example of print log-related information stored in a print log database. [Figure 4] FIG. 11 is a sequence diagram showing an example of a procedure of a process for posting a label provided to a user by a label management server program of the label management server, including the operation of a client application of the terminal. [Diagram 5] FIG. 11 is an explanatory diagram illustrating a schematic diagram of a terminal when a new post label is posted. [Figure 6] FIG. 11 is a sequence diagram showing an example of a procedure of a download process of content data provided to a user by a label management server program of the label management server, including the operation of a client application of the terminal; [Figure 7] 1A is an explanatory diagram showing a schematic diagram of a terminal when content data is downloaded, and FIG. 1B is an explanatory diagram showing a schematic diagram of a terminal when content data is downloaded. [Figure 8] FIG. 11 is a sequence diagram showing an example of a procedure of a download process of content data provided to a user by a label management server program of a label management server, including the operations of a printer application of a printer and a client application of a terminal according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] (First embodiment) An embodiment of a label data sharing system 100 according to the present invention will be described in detail below with reference to the drawings. FIG.
[0013] That is, as shown in FIG. 1, the label data sharing system 100 of this embodiment is a system provided to users by the vendors (manufacturers) of the printers 11A and 11B. In the label data sharing system 100 of this embodiment, the 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 the terminals 12A and 12B they own, that is, 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 create labels by downloading the label data from the label management server 22 to the terminals 12A and 12B they own, and then 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] The terminals 12A and 12B are configured by smartphones owned by the users, but may also be configured by tablets or personal computers. The terminals 12A and 12B also store various application programs (hereinafter referred to as apps), such as client applications 13A and 13B provided to the users by the vendors of the printers 11A and 11B. The client applications 13A and 13B have a function for creating and editing labels on the terminals 12A and 12B. The client applications 13A and 13B also have a function for uploading the 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 and 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 particular need to distinguish between them. The terminals 12A and 12B may be collectively referred to as the "terminal 12" when there is no particular 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 particular 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 attached to 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 a label printer, and the tape is an example of a print medium.
[0017] The printer 11 is configured as a label printer capable of printing labels, but may also be an inkjet printer or a laser printer. The printer 11 is connected to the terminal 12 by wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The printer 11 and the terminal 12 may also be connected by wire using the USB communication standard.
[0018] Next, the label management server 22 and the print log server 23 constituting the label data sharing system 100 of this embodiment will be described. The label management server 22 and the print log server 23 are each connected to a large number of terminals 12 via an Internet line 21. The label management server 22 and the print log server 23 may be connected via the Internet line 21 or via a wired LAN line 27. A user database 24, a submitted label database 25, and a content database 26 are connected to the label management server 22 so as to be accessible. A print log database 28 is connected to the print log server 23 so as to be accessible. 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, a HDD, a flash memory, etc., and stores a label management server program 228 and various processing programs.
[0021] The CPU 221 executes various processes according to programs read from the ROM 222 or the storage device 224 .
[0022] In this embodiment, the network interface 225 is configured by an interface conforming to a wired LAN communication standard. In addition, the network interface 225 may be, for example, an interface conforming to a wireless LAN communication standard such as Wi-Fi, an interface conforming to a USB communication standard, or an interface conforming to a short-range wireless communication standard such as Bluetooth. The network interface 225 is connected to the Internet line 21.
[0023] The operation display unit 226 is composed of, for example, a display device and a touch panel arranged on the display device, etc. The display device displays necessary information, and the touch panel accepts inputs by the user.
[0024] In this embodiment, the interface 227 is configured by an interface conforming to a 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 up the print log server 23. The RAM 233 is used as a working area when various processes are executed, or as a storage area for temporarily storing data.
[0026] The storage device 234 is configured, for example, with a 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 according to 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 a wired LAN communication standard. In addition, the network interface 235 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 235 is connected to the network interface 225 of the label management server 22 via a wired LAN line 27.
[0029] The operation display unit 236 is composed of, for example, a display device and a touch panel arranged on the display device, etc. The display device displays necessary information, and the touch panel accepts inputs 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 server 23 may have the print log database 28.
[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 group (corporation) of the user to whom the label sharing service of this embodiment is provided. Note that when a label is posted for the first time using the label data sharing system 100 of this embodiment, a user ID for identifying the user posting is newly set and additionally stored in the user ID 301. Furthermore, when posting, the user name, etc. entered by the user on the terminal 12 is additionally stored in the user name 302 corresponding to the newly set user ID.
[0033] The point information 303 is information indicating owned points, which are points in the label data sharing system 100 of this embodiment and are points currently owned by the user. Note that owned points can be used in place of cash when purchasing content, printing paper, etc. using the label data sharing system 100 of this embodiment.
[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 increment method will be omitted, the increment of the value of the point information 303 is performed based on the user ID 402, the number of downloads 403, the number of prints 404, etc. of the posted label related information 40 described later.
[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] 3(B) is stored as a table in the posted label database 25. The posted label related information 40 is composed of, for each label data posted in the label data sharing system 100 of this embodiment, a label ID 401, a user ID 402, a download count 403, a print count 404, posted label data 405, a content ID 406, tape size information 407, tape color information 408, 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 sequentially assigned to each piece of label data registered in the posted label database 25 in the label data sharing system 100 of this embodiment. The user ID (creator) 402 is the user ID 301 of the user who posted the label data using the label data sharing system 100 of this embodiment. The download count 403 is the number of times the label data posted by the user has been downloaded. The print count 404 is the number of times the label data posted by the user has been printed.
[0038] Posted label data 405 is posted label data, and is data indicating the composition of a label. Specifically, label data is composed of fonts, pictograms, character images, decoration images, frames, content, and layout information thereof. Content ID 406 stores the content ID of the content included in 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 label data was posted by the user.
[0040] The content database 26 stores content-related information 50 shown in Fig. 3(C) as a table. The content-related information 50 is composed of a content ID 501, content information 502, etc. The content ID 501 is a serial number sequentially assigned to each piece of content registered in the content database 26 in the label data sharing system 100 of this embodiment. The content information 502 stores content data provided to users by the vendors (manufacturers) of the printers 11A and 11B. 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 print date and time 601, user ID (purchaser) 602, label ID 603, paper print size information 604, number of prints 605, etc.
[0042] 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. User ID (purchaser) 602 is the user ID 301 of the user who printed the label by the printer 11. Label ID 603 is the label ID 401 of the label printed by the printer 11. Paper print size information 604 is print size information of the print paper (label) when a 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. 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 the number of prints 605 in the print log related information 60. The timing of the update may be configured to be performed periodically at a predetermined interval, or may be configured to be performed every time the print log related information 60 is updated.
[0044] (Label posting process) Next, an example of the procedure of 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.
[0045] Each processing step in this embodiment basically indicates processing by the CPU 221 according to 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 described.
[0046] In the label posting process of this embodiment, first, a user (hereinafter, referred to as a contributor) who intends to post label data starts a client application 13A of a terminal (contributor) 12A, and then, on the terminal (contributor) 12A, the client application 13 of the terminal (contributor) 12A displays an editing screen for creating label data 31 as shown in FIG. 5, for example, 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 contributor has already purchased and text data 33 that the contributor has manually input on the terminal (contributor) 12A. The content data 32 that the contributor has already purchased is composed of art such as special fonts, pictograms, character images, and decorative images. The text data 33 may be content composed of special fonts that the contributor 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, etc.
[0048] Therefore, the contributor can set the color of the tape of the label data 31 by touching the "Tape Color" button 121. Also, the contributor can set the length of the tape of the label data 31 by touching the "Tape Length" button 122.
[0049] Thereafter, when the contributor touches the "New Post" button 123 displayed on the terminal (contributor) 12A, the client application 13A of the terminal (contributor) 12A transmits to the label management server 22 the contributor's user ID, the submitted label data which is the label data 31 created by the contributor, tape size information suitable for printing the label data 31 as set by the contributor, tape color information of the label data 31 as set by the contributor, etc. (T12). For example, the label management server program 228 provides a web page for submission, the web page is displayed by the browser function of the client application 13A, the user ID is entered when logging in to the label management server 22 via the web page, and then an instruction to transmit the label data 31 is input via the web page, whereby the submitted label data, etc. are uploaded to the label management server 22. Note that before transmitting the label data 31, a screen for attaching explanatory text about the label data 31 and a usage example image which is a photographic image using the label data 31 may be displayed, and the received supplementary data may be transmitted together with the label data 31.
[0050] Then, the label management server 22 that 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 is also 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. After that, in a 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 received 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 when supplementary data is received together 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 transmits "registration complete" to the terminal (contributor) 12A (T14). Then, the terminal (contributor) 12A that receives the "registration complete" displays on its display unit a message indicating that registration of the submitted label data is complete, and notifies the contributor (T15). This allows the contributor to know that the submitted label data 31 has been registered in the label data sharing system.
[0053] (Content data download processing) 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 operation of the client application 13B of the terminal 12B in this embodiment, will be described with reference to the sequence diagram of FIG. 6.
[0054] In the content data download process of this embodiment, first, a user (hereinafter, referred to as a purchaser) who wants 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 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, and the user ID is input via the web page, and the user ID is transmitted. After the login is approved, when the "Point Content" tab 125 displayed on the terminal (purchaser) 12B is touched, the label management server 22 accepts the request to display a list of content data.
[0055] Next, the label management server 22 that has accepted the request to display a list of content data extracts from the content database 26 the content data stored as the 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 in T23 is already stored in acquired content information 305 corresponding to the purchaser as shown in Fig. 3(A), the content data and content ID are excluded, so that it is possible to prevent the purchaser from erroneously presenting content data that the purchaser has already acquired. In other words, it is possible to prevent the purchaser from purchasing content data in duplicate.
[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 content IDs stored in the number of times of printing 404 and content ID 406 of the post label related information 40 shown in FIG. 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, and it is also acceptable 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 advance, thereby improving convenience.
[0060] After that, 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] At this time, in this embodiment, the list screen of the content data transmitted 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 list screen of the content data 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] 7(A), 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. In addition, 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 multiple 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 the record of the content data stored in the content information 502 from the content database 26 based on the requested content ID for the requested content data. 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 the content ID 406 matches the content ID of the requested content data, extracts the posted label data 405 and the posted label data stored in the label ID 401 and their label IDs (T27). In other words, the 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 performed using the number of downloads 403 instead of the number of prints 404, or may be performed 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 printing date and time is registered as the printing history in the print log database 28. Therefore, by referring to the print log database 28, the number of prints for each label data for the past week or the past year may be used.
[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 posted label data and label IDs to posted 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 posted label related information 40 shown in Fig. 3(B) (T29). In other words, for the sorted posted label data and label IDs, posted label data whose length exceeds the threshold is excluded. The threshold can be any value depending on the screen size of the terminal (purchaser) 12B, such as 100 mm or 80 mm.
[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 posting targets, it becomes easier for the purchaser to check the usage form 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. The number N can be any value, such as 10 or 20, depending on the screen size of the terminal (purchaser) 12B and the functions of the terminal (purchaser) 12B. The number N may also be a number set by the purchaser.
[0072] In this manner, in this embodiment, the number of posted label data presented is limited to the top N most popular data, making it easier for the purchaser to confirm how the content data will be used. In other words, if a large number of posted label data are presented, the display on the screen of the terminal (purchaser) 12B becomes cluttered, making it difficult for the purchaser to confirm how the content data will be used. In this embodiment, such a problem can be eliminated by setting an upper limit on the number of posts.
[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 length of the sorted posted label data items to those that are equal to or less than a threshold in the process of T29, but this is not limited to the above. 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 length of the posted label data items to those that are equal to or less than a threshold. Also, the order of T28 and T29 may be reversed.
[0074] Next, the label management server 22 transmits to the terminal (purchaser) 12B (T30) a details screen including information indicating the content of the content data that is the subject of the detailed display request, posted label data limited to N in order of popularity, label IDs, etc. If a usage example image is associated with the content data that is the subject of the detailed display request and registered in the posted label database 25, the usage example image 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 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 owned by the purchaser. In addition, a thumbnail of the posted label data 31 extracted by T27 is displayed below the "Exchange" button 36. A plurality of pieces of posted label data 31 may be displayed at the same time, or may be displayed sequentially in accordance with a scroll operation. In addition, 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 for downloading the selected content data 32 to the label management server 22 (T32).
[0079] Next, when the download is requested, the label management server 22 transmits the selected content data 32 to the terminal (purchaser) 12B (T33). The process of T33 is an example of a content transmission process. Furthermore, the label management server 22 subtracts the number of points required for the point exchange process from the number of points stored in the point information 303 for a user whose user ID 301 matches the received user ID in the user related information 30 shown in Fig. 3(A). Furthermore, the label management server 22 stores the content ID of the content data 32 for which the points have been exchanged this time in the acquired content information 305 (T34).
[0080] Moreover, 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 the content data 32 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 contained in the posted label data 31, and when a selection to download the content data 32 is accepted, 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] In this embodiment, while the posted label data 31 extracted in T27 is displayed on the details screen as shown in Fig. 7(B), it may be possible to accept a download of the displayed posted label data 31. In this case, the label management server 22 may be configured to accept a download instruction with one or more posted label data 31 selected from the posted label data 31 via the details screen, and when the download instruction is accepted 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, the use of content data including the target content can be promoted by being able to download the displayed label data 31.
[0084] Second embodiment Next, an example of the procedure of the download process of 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 in this embodiment, will be described with reference to the sequence diagram of Fig. 8. In this description, the same reference numerals will be used to denote the same parts as in the first embodiment.
[0085] That is, in this embodiment, the label management server 22 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 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 accepted 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 tape width information of the tape wound in tape cassette 15B set in itself, tape color information, and model number information of printer 11B, 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 process of T44 is an example of a width acquisition process.
[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 acquired 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 acquired from the printer is an example of second medium information.
[0092] In this case, if the tape width of the posted 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 posted labels that have a different tape width from 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 submitted label data and its label ID extracted in the process of T27 to submitted label data whose tape color information matches the tape color information acquired 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 acquired from the printer is an example of second medium information.
[0094] In this case, by excluding posted label data that does not match the characteristics of the tape acquired from the terminal (purchaser) 12B, that is, the color of the tape, from the presented items, 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 submitted label data and its label ID extracted in the process of T27 to submitted label data whose model number information matches the characteristics of the model number information of the printer 11B acquired from the printer 11B and is stored in the submitted label database 25. Note that the model number information stored in the submitted label database is an example of first printer information, and the printer model number information acquired from the submitted label data printer is an example of second printer information.
[0096] In this case, by excluding from the presented submitted label data that does not include features matching the printer features acquired from the terminal (purchaser) 12B, more suitable submitted 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 the first application information, and the version information of the client application is an example of the second application information.
[0098] In this case, by excluding from the presented post label data that does not include features that match the version information acquired from the terminal (purchaser) 12B, more suitable post 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 the tape width information of the tape wound in the tape cassette 15B, the tape color information, and the 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, in the process of T45, the label management server 22 may execute the process of T29 in the first embodiment, i.e., a process of limiting the length of the posted label data to posted label data that is equal to or shorter 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, the uploaded posted label data 31 is registered in the posted label database 25 in association with the content information of the content data 32 included in the posted label data 31, and when a selection to download the content data 32 is accepted, the posted label data 31 including the selected content data 32 is extracted from the posted label database 25 and presented to the purchaser. This makes it easier for the purchaser to imagine how the content will be used, promoting the downloading of the content.
[0102] The embodiments disclosed in this specification are merely examples and do not limit the present invention in any way. Naturally, the technology disclosed in this specification can be improved or modified in various ways without departing from the spirit of the technology. Furthermore, the number of printers connected to the terminal is not limited to the illustrated example, and may be two or more.
[0103] In addition, in this embodiment, the user database 24, the posted label database 25, and the content database 26 are accessible connected to the label management server 22, and the print log database 28 is accessible connected to the print log server 23, but the print log database 28 and any one of the user database 24, the posted label database 25, or the content database 26 may be accessible connected to the print log server 23.
[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 the posted label data posted by the contributor, but the posted label database 25 may store label data prepared in advance by the vendor (manufacturer) of the printer 11A and the printer 11B.
[0106] In addition, 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 terminal 12. In this case, it is possible to increase the number of label data that can be saved on terminal 12 by touching and purchasing the "Change number of saved data" button 38 shown in FIG. 7(A).
[0107] Furthermore, in this embodiment, the system is configured with the label management server 22 and the print log server 23, but these may be integrated into one server.
[0108] Furthermore, in any sequence diagram disclosed in the embodiments, any of a plurality of processes can be executed in a different order or in parallel as long as no contradiction occurs in the process contents.
[0109] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as ASIC, or a combination of these. The processes disclosed in the embodiments may be realized in various forms, such as a recording medium having a program for executing the processes recorded thereon, or a method. [Explanation of symbols]
[0110] 100 Label Data Sharing System 11B Printer 12B Terminal (Purchaser) 22 Label Management Server 23 Print Log Server 24 User Database 25 Post Label Database 26 Content Database 31 Label Data 32 Content Data 33 Font data
Claims
1. A program executable by a server, the server being capable of accessing a label database in which a plurality of label data items can be registered, and a content database in which a plurality of contents items can be registered, the label data items being data that can be printed by a label printer, and the contents items being usable with the label data, A computer of the server, executing a registration process for, when label data is uploaded from a first information processing device, associating the uploaded label data with content information indicating content included in the uploaded label data and registering the associated data in the label database; Further, the computer of the server When one of the contents registered in the content database is selected from the second information processing device, 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; a presentation process of presenting at least one of the label data extracted in the extraction process to the second information processing device; Run the command, Further, the computer of the server when a download instruction for the selected content is received from the second information processing device, executing a content transmission process of transmitting the selected content to the second information processing device; A program that is structured as follows.
2. The program according to claim 1, The label data registered in the label database is associated with an evaluation value that is an index of popularity, In the presentation process, arranging the plurality of labeled data extracted in the extraction process in order of popularity based on the evaluation value associated with the extracted labeled data, and presenting the result to the second information processing device. A program that is structured as follows.
3. The program according to claim 2, In the presentation process, among the plurality of label data extracted in the extraction process, up to the top N pieces of label data are arranged in order of popularity based on the evaluation values associated with the extracted label data, and are presented to the second information processing device. A program that is structured as follows.
4. The program according to claim 1, In the extraction process, extracting, from the label data registered in the label database, the label data associated with the content information indicating the selected content and satisfying an extraction condition for limiting the presentation target; A program that is structured as follows.
5. The program according to claim 4, the extraction condition is that the length of the label indicated in the label data is shorter than a threshold value; A program that is structured as follows.
6. The program according to claim 4, The computer includes: executes a width acquisition process for acquiring a label width from the second information processing device; The extraction condition is that the label width indicated in the label data matches the width obtained in the width obtaining process. A program that is structured as follows.
7. The program according to claim 4, The label data includes first medium information that indicates a characteristic of the print medium, The computer includes: executing a medium acquisition process for acquiring second medium information indicating characteristics of a print medium from the second information processing device; the extraction condition is that the feature indicated in the first medium information included in the label data matches the feature indicated in the second medium information acquired in the medium acquisition process; A program that is structured as follows.
8. The program according to claim 4, The label data includes first printer information indicating a characteristic of a printer, The computer includes: executes a printer acquisition process for acquiring second printer information indicating a printer characteristic from the second information processing device; the extraction condition is that the features indicated in the first printer information included in the label data match the features indicated in the second printer information acquired in the printer acquisition process; A program that is structured as follows.
9. The program according to claim 4, the label data includes first application information indicating a feature of an editing application, which is an application program capable of editing the label data; The computer includes: executing an application acquisition process for acquiring second application information indicating a feature of an editing application from the second information processing device; the extraction condition is that a feature indicated in the first application information included in the label data matches a feature indicated in the second application information acquired in the application acquisition process; A program that is structured as follows.
10. The program according to claim 1, The computer includes: while the label data is being presented to the second information processing device through the presentation process, an instruction to download the presented label data is accepted, and when the instruction to download the label data presented through the presentation process is accepted from the second information processing device, a label transmission process is executed to transmit the presented label data to the second information processing device. A program that is structured as follows.
11. A server connectable to a first information processing device and a second information processing device via a network, The server, 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 are accessible, the label data is data that can be printed by a label printer, and the content is usable with the label data, Furthermore, the server executing a registration process for registering, in the label database, the uploaded label data in association with content information indicating content included in the uploaded label data when the label data is uploaded from the first information processing device; Furthermore, the server When one of the contents registered in the content database is selected from the second information processing device, 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; a presentation process of presenting at least one of the label data extracted in the extraction process to the second information processing device; Run Furthermore, the server executing 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; It is configured as follows.
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, 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 are accessible, the label data is data that can be printed by a label printer, and the content is usable with the label data, The first information processing device, The label data stored in the first information processing device can be uploaded to the server, The server, registering the label data uploaded from the first information processing device in the label database in association with content information indicating content included in the uploaded label data; The second information processing device is It is possible to select one of the contents registered in the content database, The server, When the content is selected from the second information processing device, extracting the label data associated with the content information indicating the selected content from the label data registered in the label database; presenting at least one of the extracted label data to the second information processing device; The second information processing device is The selected content can be downloaded from the server. A label data sharing system configured to:
Citation Information
Patent Citations
Point managing method and device storage medium and point managing system
JP2002099746A