Program, information processing device, and label data sharing system

Abstract

This invention makes it easy to use label data including for-fee content or for-fee function setting, in a system for utilizing label data.　A label management server 3 connectable to a terminal 1 stores a plurality of pieces of label data, and additionally stores, for each user ID, purchase information indicating the presence / absence of a purchase for for-fee content and function. The terminal 1: executes a client application 41 to acquire, in a state of being logged in to a label management server 3, purchase information corresponding to a user ID of a log-in user from the label management server 3; determines, on the basis of the acquired purchase information, whether or not the selected label data includes for-fee content or function setting that has not been purchased; and if for-fee content or function setting that has not been purchased is included, reports that the selected label data includes the for-fee content or function setting that has not been purchased.

Description

Program, information processing device, 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 in label printing with label printers have been under consideration. Label data can be configured by combining various content and functions, some of which require payment. Label data can also include settings related to the paid content and functions.

[0006] In order for a user who has downloaded label data containing settings for paid content or paid functions to use the data, the user must have purchased the paid content or paid functions. However, it is difficult for the user who has downloaded the data, i.e., the user who uses the label data, to know that there is content or functions that have not yet been purchased. Since Patent Document 1 does not mention paid content or functions, there is room for improvement.

[0007] The program that has been made to solve the above-mentioned problems is a program that can be executed by a computer of an information processing device that can be connected to a server, the server being capable of storing a plurality of label data, the label data being data that can be printed by a label printer, and the label data being capable of including settings for paid content or paid functions, the server being capable of accessing a purchase information database that stores purchase information indicating whether or not paid content and functions have been purchased for each user ID, the computer being capable of performing a login process that associates the user ID with the server and requests login to the server, and a program that downloads at least one of the label data stored in the server from the server while logged in to the server and stores it in memory of the information processing device. The computer can be further configured to execute an acquisition process for acquiring the purchase information corresponding to the user ID of the logged-in user via the server while logged in to the server, a selection process for selecting the label data to be used, and a determination process for determining whether the label data selected in the selection process includes settings for paid content or functions that have not been purchased, based on the purchase information acquired in the acquisition process. If it is determined in the determination process that the label data includes settings for content or functions that have not been purchased, the computer can be further configured to execute a notification process for notifying on a user interface of the information processing device that the label data selected in the selection process includes settings for content or functions that have not been purchased.

[0008] When paid content or a function included in selected label data has not yet been purchased, an information processing device equipped with the program executes the program to notify the user that the selected label data contains unpurchased content or a function. This makes it easier for the logged-in user using the program to notice that the unpurchased content or function exists. As a result, the user is encouraged to purchase the unpurchased content or a function.

[0009] An information processing device, a label data sharing system, a control method, and a computer-readable storage medium storing the program for realizing the functions of the program are also novel and useful.

[0010] The technology disclosed in this specification makes it easy to use label data that includes paid content or paid function settings in a system that attempts to use label data.

[0011] FIG. 1 is an explanatory diagram that shows an outline of a label data sharing system. FIG. 2 is an explanatory diagram that shows an example of the structure of a user database and a label database. FIG. 3 is a sequence diagram that explains an example of the procedure of a content purchasing process. FIG. 4 is a diagram that explains an example of screen transitions. FIG. 5 is a sequence diagram that explains an example of the procedure of a purchase information acquisition process. FIG. 6 is a sequence diagram that explains another example of the procedure of a purchase information acquisition process. FIG. 7 is a sequence diagram that explains an example of the procedure of a label posting process. FIG. 8 is a sequence diagram that explains the procedure of a download process. FIG. 9 is a diagram that explains an example of screen transitions. FIG. 10 is a sequence diagram that explains the procedure of a label data usage process.

[0012] Hereinafter, an information processing device used in a label data sharing system according to an embodiment will be described in detail with reference to the accompanying drawings. This specification discloses an information processing device that downloads and uses posted label data.

[0013] As shown in FIG. 1 , a label data sharing system 100 (hereinafter abbreviated as "system 100") of this embodiment is a system provided to a user by, for example, a label printer vendor. The system 100 comprises a terminal 1 and a label management server 3, which are connected via an internet line 4. The terminal 1 is owned by the owner or user of the label printer (hereinafter referred to as "user"). The terminal 1 can be connected to a label printer 2. The label management server 3 is an example of a "server." The internet line 4 is an example of a "network." Note that although only one terminal 1 is shown in FIG. 1 , in reality, many terminals 1 are connected to the label management server 3.

[0014] The label printer 2 is a printing device that includes, for example, a thermal transfer print head and prints on a roll of tape while unwinding it. Based on a print job received from the terminal 1, for example, the label printer 2 prints an image on the stored tape and feeds the tape, causing the printed portion to protrude outside the machine. A label having a predetermined label length and label width is created using the tape protruded outside the machine. The label length is the length in the direction in which the label is ejected from the label printer 2. The label width is the length in the direction perpendicular to the label length. Depending on the model, the label printer 2 can be used with multiple types of tape.

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

[0016] The label management server 3 is a device that has at least a storage function and a communication function. The label management server 3 can perform various functions by executing a server program 31. The label management server 3 has a web server function that provides web pages in response to requests from the terminal 1. The label management server 3 has a function to accept label data submissions and send submitted label data to the terminal 1. The label management server 3 has a function to manage the purchase of paid content or functions for each user ID. Each function will be described later.

[0017] The label management server 3 is connected to, for example, a user database (hereinafter referred to as "user DB") 6, a label database (hereinafter referred to as "label DB") 7, and a content database (hereinafter referred to as "content DB") 8 so that they can be accessed. The user DB 6 is an example of a "purchase information database." The label management server 3 may be connected to each of the DBs 6, 7, and 8 via a wired connection 35 or wirelessly. The DBs 6, 7, and 8 may be located in the label management server 3 or in a server separate from the label management server 3. The user DB 6 and label DB 7 may be configured as a single integrated database. The user DB 6, label DB 7, and content DB 8 may be located inside the label management server 3 or externally.

[0018] As shown in FIG. 2A, the user DB 6 can register a record for each user who uses the terminal 1, the record consisting of a user ID 61, a user name 62, a password 63, and purchase information 64.

[0019] The user ID 61 is identification information for identifying a user who can use the system 100, and specifies the user who uses the terminal 1. The user name 62 is, for example, the name or nickname of an individual or group (corporation) of a user who uses the label data sharing system 100 of this embodiment. The password 63 is a password set by each user stored in the user name 62.

[0020] The purchase information 64 is information indicating paid content and functions purchased by each user stored in the user name 62. Paid content includes, for example, special fonts, pictograms, character images, decorative images, and special frames. Paid functions include, for example, text color inversion, left-right inversion, repeated printing, and database printing. Content or functions are assigned content IDs for identifying them. The purchase information 64 stores paid content IDs for paid content or functions purchased by a user corresponding to the user ID. In addition, personal information such as an email address, address, and telephone number may be registered in the user DB 6 for each user.

[0021] The label DB 7 stores multiple pieces of label data that can be printed by a label printer. The label data may be label data uploaded, i.e., posted, from the terminal 1 to the label management server 3 by a user of the label data sharing system 100 of this embodiment (hereinafter referred to as "posted label data"), or label data registered in the label management server 3 by the vendor (manufacturer) of the label printer 2. As shown in FIG. 2(B) , the label DB 7 can register, for each piece of label data, a record consisting of a label ID 71, a user ID (creator) 72, label data 73, a paid content list 74, supplemental information 75, and a posting date 76. The user ID (creator) 72 may be a user name (creator).

[0022] In the system 100 of this embodiment, the label ID 71 is a serial number assigned sequentially to each piece of label data registered in the label management server 3. The user ID (creator) 72 is the user ID 61 of the user who posted the data using the system 100. The user ID (creator) 72 for label data created by someone other than the user may store the ID of the administrator, the ID of the vendor who created the data, or be left blank.

[0023] The label data 73 is label data stored in the label management server 3. The label data 73 stores the type, function, and layout of objects included in the label indicated by the label data 73, and further stores information about specific content when that content is used. The content or function used in the label data 73 may be either paid or free. The label data may also include tape information such as the tape model number, and printer information.

[0024] The paid content list 74 is a list created by the label management server 3. The paid content list 74 stores paid content IDs of paid content or functions stored in the label data 73. The supplemental information 75 stores information supplemented when the label data 73 is posted to the label management server 3. The posting date 76 is information indicating the date and time when the label data was registered in the label DB 7.

[0025] The content DB 8 stores configurable content or functions for each type of object. For example, the content DB 8 stores paid content IDs and paid content information indicating the types of paid content or functions. The paid content information may include information indicating the content configuration. The content DB 8 may also store free content or functions.

[0026] 1, the terminal 1 is an information processing device having a communication function, a storage function, a display function, and an operation function. The terminal 1 in this embodiment is configured as a smartphone, but may also be configured as a tablet or a personal computer.

[0027] The terminal 1 has a controller 10 including a CPU 11 and a memory 12, to which a communication interface (hereinafter referred to as "communication IF") 13 and a user interface (hereinafter referred to as "user IF") 14 are electrically connected. The terminal 1 is an example of an "information processing device." The CPU 11 is an example of a "computer." The controller 10 may also be an example of a "computer." Note that the controller 10 in FIG. 1 is a general term that collectively refers to hardware and software used to control the terminal 1, and does not necessarily represent a single piece of hardware that actually exists in the terminal 1.

[0028] The CPU 11 of the terminal 1 executes various processes in accordance with programs read from the memory 12 and based on user operations. The memory 12 stores various programs, such as a client application program (hereinafter referred to as a "client app") 41. The memory 12 can store various data, such as label data 42, login information 44, purchase information 45, and paid content information 46. The memory 12 is also used as a work area when various processes are executed. The buffer provided by the CPU 11 is also an example of memory. Note that the memory 12 is not limited to a ROM, RAM, HDD, etc. built into the terminal 1, but may also be a storage medium readable and writable by the CPU 11, such as a CD-ROM, DVD-ROM, USB memory, or other recording medium.

[0029] The client application 41 has a function to create or edit label data. The client application 41 has a function to cause the label printer 2 to print the label data. The client application 41 has a function to store label data 42 downloaded from the label management server 3 in the memory 12. The client application 41 has a function to accept a login operation when logging in to the label management server 3. The client application 41 has a browser function and can display web pages provided by the label management server 3.

[0030] The client application 41 has a function to store paid content information 46 of paid content or functions purchased from the label management server 3 in the memory 12. The client application 41 has a function to obtain purchase information 45 corresponding to a login ID from the label management server 3 and store it in the memory 12. The client application 41 has a function to determine whether or not the label data to be used includes unpurchased paid content or functions, based on the purchase information 45 obtained from the label management server 3 and corresponding to the login ID. Each function will be described later. The client application 41 is an example of a "program".

[0031] The communication IF 13 includes hardware that controls communication with external devices such as the label printer 2 and label management server 3. The user IF 14 includes hardware that displays a screen to notify the user of information and hardware that accepts user operations. Note that the user IF 14 may be a combination of a display that can display information and a mouse or keyboard that has an input acceptance function, or may be a touch panel that has both a display function and an input acceptance function.

[0032] Next, the operation of the terminal 1 in the label data sharing system 100 will be described. Each processing step in this embodiment basically indicates processing by the CPU 11 in accordance with instructions written in programs such as the client application 41. The processing by the CPU 11 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.

[0033] (Content Purchase Processing) An example of the procedure for the content purchase processing will be described with reference to FIG. 3 . For example, the label management server 3 prepares a content purchase screen for a user to purchase paid content or functions. A URL is assigned to the content purchase screen. The client application 41 accesses the label management server 3 based on the URL of the content purchase screen and can display the content purchase screen on the user IF 14 of the terminal 1 (G01). For example, as described below, the client application 41 can receive web page information for a label search screen from the label management server 22 and display the label search screen on the terminal 1. The label search screen includes a point content tag associated with the URL of the content purchase screen. When the point content tab is operated, the client application 41 can receive web page information for the content purchase screen from the label management server 3 and display it on the terminal 1.

[0034] The content purchase screen displays selectable paid content and functions that can be downloaded to the terminal 1. Each paid content and function is associated with a paid content ID. The client application 41 logs in to the label management server 3 (G02), and when paid content or a function is selected on the content purchase screen and the purchase execution button on the content purchase screen is pressed, the client application 41 sends a content purchase request to the label management server 3 (G03). This request includes the paid content ID corresponding to the selected paid content or function. Free content and functions may also be selectably displayed on the content purchase screen.

[0035] When the payment procedure is complete, the label management server 3 reads from the content DB 8 the paid content information 46 corresponding to the content ID associated with the paid content or function selected on the content purchase screen (G04). The label management server 3 transmits the read paid content information 46 to the terminal 1 that output the content purchase request (G05). The terminal 1 receives the paid content information 46 using the communication IF 13 and stores it in the memory 12 (G06). Having transmitted the paid content information 46, the label management server 3 accesses the user DB 6 and updates the purchase information for the record containing the user ID of the logged-in user according to the purchased content.

[0036] A user can access the label management server 3 and purchase content or functions by entering the URL of the content purchase screen into a program other than the client application 41, such as a browser, on one terminal 1. A user can also purchase content or functions by logging in to the label management server 3 from multiple terminals 1 using their own user ID and password. In this case as well, the label management server 3 updates the user DB 6.

[0037] (Purchase Information Acquisition Process) When a user uses label data that includes paid content or a function, the user must have purchased the paid content or function. However, the purchase of paid content or a function differs from user to user.

[0038] The label management server 3 manages purchase information for each user in the user DB 6. Therefore, the label management server 3 determines whether or not content or functions that the logged-in user has not purchased are included in the label data based on the purchase information corresponding to the login ID, and if it determines that the content or functions are included, does not send the label data to the terminal 1, thereby restricting the user from using label data that includes content or functions that the logged-in user has not purchased.

[0039] However, when multiple people share one terminal 1, a user other than the user who downloaded the label data can access the label data on the terminal 1, even if they have not purchased the paid content or functions included in the label data. Also, when label data is shared among multiple terminals 1 using the sharing function, a user other than the user who downloaded the label data can use the sharing function to access the label data from another terminal 1, even if they have not purchased the paid content or functions included in the label data. Use through these accesses cannot be restricted by the label management server 3. Therefore, it is preferable that the terminal 1 also be able to determine, based on the purchase information, whether the label data includes unpurchased paid content or functions.

[0040] Therefore, the client application 41 acquires the purchase information from the label management server 3 while logged in to the label management server 3. The login method may be manual or automatic.

[0041] The procedure for acquiring purchase information will be described with reference to Figures 4 and 5. For example, when the client application 41 is started up in a state where the login information 44 is not stored in the memory 12, the client application 41 displays the home screen 200 shown in Figure 4(A) on the user IF 14 of the terminal 1 in a state where the user is not logged in to the label management server 3.

[0042] For example, when the client application 41 accepts an operation of the server use button 203 displayed on the home screen 200, it accesses the label management server 3 and displays a label search screen 300 shown in FIG. 4(B) provided by the label management server 3 on the user IF 14. The label search screen 300 can accept the selection of label data to be downloaded from the label DB 7. When the client application 41 accepts an operation of the user button 312 displayed on the label search screen 300, it displays a login confirmation screen 401 shown in FIG. 4(C) provided by the label management server 3 on the terminal 1.

[0043] When the client application 41 accepts the operation of the login button 402 displayed on the login confirmation screen 401, it causes the terminal 1 to display the login screen 411 shown in Fig. 4(D) provided by the label management server 3. As shown in Fig. 5(A), the client application 41 accepts the login operation by accepting the operation of the sign-in button 414 on the login screen 411 in a state in which the user ID and password of the user who will use the terminal 1 have been entered in the user ID input field 412 and password input field 413 displayed on the login screen 411. In this case (A01), the client application 41 sends a login request to the label management server 3 (A02). A01 to A02 are examples of "login processing".

[0044] When the label management server 3 receives the login request, it performs login authentication based on the user ID and password entered on the login screen 411 (A03), and if the login is successful, it sends a login completion notification to the terminal 1 (A13). Furthermore, as shown in Fig. 4 (E), the label management server 3 closes the login screen 411 and causes the terminal 1 to display the label search screen 300.

[0045] 5A, when the client application 41 receives a login completion notification via the communication IF 13, it resets the purchase information 45 stored in the memory 12 (A14). This prevents the client application 41 from determining whether unpurchased paid content and functions are included in the label data based on the purchase information corresponding to the user ID of the previously logged-in user, thereby improving the accuracy of the determination.

[0046] The client application 41 also stores the user ID and password used for logging in as login information 44 in the memory 12 (A15). This allows the client application 41 to know that it is logged in to the label management server 3. Note that the client application 41 may also know whether it is logged in or not by a method other than the presence or absence of the login information 44, such as a flag.

[0047] Furthermore, the client application 41 executes a purchase information acquisition process (A16). A16 is an example of an "acquisition process." Specifically, as shown in FIG. 5B, the client application 41 requests the label management server 3 to transmit purchase information (A21). This request includes the user ID included in the login information 44 stored in the memory 12, i.e., the user ID of the logged-in user.

[0048] The label management server 3 accesses the user DB 6 and reads out the purchase information 45 corresponding to the received user ID (A22). That is, the label management server 3 reads out the purchase information 45 corresponding to the user ID of the logged-in user. The purchase information 45 includes the paid content IDs of the paid content and functions that the logged-in user has purchased. The label management server 3 sends the read purchase information 45 to the client application 41 (A23). The client application 41 stores the received purchase information 45 in the memory 12 (A24). This allows the client application 41 to obtain the purchase information 45 corresponding to the user ID of the logged-in user.

[0049] Next, referring to FIG. 6 , a procedure for acquiring purchase information when automatically logging in at startup will be described. For example, when the client application 41 starts up (A31), it determines whether it ended in the previous login state (A32). If the login information 44 is stored in the memory 12, the client application 41 determines that it ended in the previous login state. In this case (alt: end), the client application 41 sends a login request to the label management server 3 (A33). The login request includes the login information 44 stored in the memory 12.

[0050] The label management server 3 performs login authentication by comparing the received login information 44 with the user DB 6 (A34). The label management server 3 sends the authentication result to the client application 41 (A35). If the login is successful (alt: login successful), the client application 41 executes a purchase information acquisition process based on the user ID included in the login information 44 stored in the memory 12, i.e., the user ID of the previously logged-in user (A16). The purchase information acquisition process has been described above, so a detailed description will be omitted. As a result, the client application 41 acquires purchase information corresponding to the user ID of the previously logged-in user. Thereafter, the client application 41 displays the home screen 200 on the user IF 14 while the client application 41 is logged in to the label management server 3 (A37).

[0051] On the other hand, when the client application 41 is started in a state where the login information 44 is not stored in the memory 12 (A31), it determines that the previous login state has not been terminated. In this case, the client application 41 does not acquire purchase information from the label management server 3, and causes the user IF 14 to display the home screen 200 in a state where the client application 41 is not logged in to the label management server 3 (A37).

[0052] It should be noted that there is a possibility that a user may access the label management server 3 from a program or device other than the client application 41 and purchase paid content and functions. Therefore, the client application 41 of this embodiment executes the purchase information acquisition process shown in Fig. 5(B) even when, for example, the server use button 203 shown in Fig. 4(E) is operated using the user IF 14. In this case, the client application 41 acquires purchase information from the label management server 3 using the user ID included in the login information 44 stored in the memory 12, i.e., the user ID of the logged-in user at the time the server use button 203 was operated.

[0053] Furthermore, when label data stored in the label management server 33 is selected and the selected label data is opened while logged in to the label management server 33, the client application 41 of this embodiment also executes the purchase information acquisition process shown in Fig. 5(B), which will be described later.

[0054] (Label Posting Process) Next, the procedure for the label posting process will be described with reference to FIG. 7. Here, an example will be described in which user A (hereinafter referred to as "contributor A") posts label data using terminal 1A. For ease of explanation, the terminal 1 used by contributor A and its components will be given the suffix "A." Terminal 1A is an example of a "first information processing device."

[0055] As shown in Fig. 7(A), contributor A launches client application 41A on terminal 1A and creates and saves label data 42 to be posted on terminal 1A (H01). For example, as shown in Fig. 7(B), contributor A selects a text object on an editing screen provided by client application 41 and inputs the character string "niju20" into label data 42. Contributor A inputs a special pictogram of an airplane before the character string, and further selects the character string "20" and sets a special font. This creates label data 42 including paid content 421 of the special pictogram and paid content 422 of the special font.

[0056] When contributor A has completed creating label data 42, he or she operates the save button on the editing screen to save the created label data 42 in memory 12A. Specifically, when saving label data 42, client application 41A stores information constituting the label indicated in label data 42. The information constituting the label includes, for example, the object type "text object," the position of the text object, the special emoticon entered in the text object, the character string "niju20," and the special font set for the character string "20." Client application 41A stores the paid content ID of the paid content included in label data 42 in the label data. This makes it possible to easily identify the paid content ID of the paid content and function set in label data 42 from the label data.

[0057] For example, after the label data 42 is saved in the memory 12A by the poster A, when the client application 41A accepts an operation of the Use Server button 203 displayed on the home screen 200 shown in Fig. 4(A), the client application 41A causes the user IF 14 to display the label search screen 300 shown in Fig. 4(B) provided by the label management server 3. When the client application 41A logs in to the label management server 3 and accepts an operation of the Post button 323 displayed on the label search screen 300, the client application 41A causes the terminal 1A to display a post screen (not shown) provided by the label management server 3. The process of logging in by the terminal 1A is an example of a "first login process".

[0058] The client application 41A accepts the selection of label data 42 to be posted from the label data stored on the terminal 1A on a posting screen (not shown), and also accepts input of predetermined supplemental information. The supplemental information is, for example, the label name, category, label description, and an image showing an example of how the label is used. The client application 41A accepts an upload instruction (H02) as shown in FIG. 7(A) by operating the new post button displayed on the posting screen (not shown), and uploads the label data 42 to be uploaded to the label management server 3 (H03). The uploaded label data 42 is assigned the user ID of the logged-in user, i.e., the user ID "aaa1" of poster A, and the supplemental information entered on the posting screen (not shown). H03 is an example of the "upload process."

[0059] The label management server 3 reads the paid content ID from the received label data 42 and creates a paid content list (H04). For example, the label management server 3 extracts the paid content ID "cnt1" of the special pictogram and the paid content ID "cnt4" of the special font from the posted label data 42 and adds them to the paid content list.

[0060] The label management server 3 stores the received posted label data 42 and the created paid content list in the label DB 7 (H05). Specifically, the label management server 3 creates a new label ID "ddd1" and stores it as a new label ID 71 in the label DB 7 of FIG. 2(B). The label management server 3 stores the received user ID "aaa1" of poster A, the posted label data 42, and the supplemental information as a user ID (creator) 72, label data 73, and supplemental information 75, respectively, as a record corresponding to the new label ID 71. The label management server 3 stores the paid content list created in H04 as a paid content list 74. The label management server 3 stores the year, month, and date of the posting date as a posting date 76. As a result, the posted label data 42 uploaded by poster A from the terminal 1A to the label management server 3 is registered in the label DB 7, and the label management server 3 becomes able to provide the posted label data 42 in response to requests from poster A and other users.

[0061] When the registration of the posted label data 42 is complete, the label management server 3 notifies the client application 41 of this fact (H07). The client application 41A displays a message indicating that the registration is complete on the user IF 14A of the terminal 1A (H07). This allows the poster A to know that the registration of the posted label data 42 is complete.

[0062] (Label Data Download Process) Next, the procedure for the download process for downloading label data will be described. Here, an example will be described in which poster A and another user B download and use posted label data 42 on terminal 1A and another terminal 1B. For ease of explanation, the terminal 1 used by user B and its components will be given the suffix "B." User B is an example of a "first logged-in user." Terminal 1B is an example of a "second information processing device." Note that the object to be downloaded is not limited to posted label data, and may also be label data provided by a label printer vendor or the like.

[0063] For example, User B starts the client application 41B and logs in to the label management server 3 using User B's user ID "aaa2". The process in which User B logs in to the label management server 3 is an example of a "second login process". As shown in FIG. 4(E), the label management server 3 displays a label search screen 300 on the terminal 1B while User B is logged in to the label management server 3. The label search screen 300 displays selectable image images or thumbnail images of label data stored in the label DB 7. The client application 41B accepts an operation to select an image image or thumbnail image 331 corresponding to the posted label data 42 on the label search screen 300, thereby accepting the selection of label data to be downloaded (B11), as shown in FIG. 8.

[0064] When the client application 41B accepts the selection of the download target, it causes the user IF 14B to display a download screen provided by the label management server 3 (B12). The download screen has a download execution button. When the client application 41B accepts the operation of the download execution button, it accepts a download instruction (B22) and requests the label management server 3 to transmit the selected label data (B23). The download request includes the label ID "ddd1" of the selected posted label data 42 and the user ID "aaa2" of user B who instructed to download the posted label data 42. Note that the number of label data selected to be downloaded is not limited to one, and may be multiple.

[0065] When the label management server 3 receives the download instruction, it accesses the label DB 7 and reads out the posted label data 42 from the label data 73 associated with the received label ID "ddd1" (B24). The label management server 3 sends the read out posted label data 42 to the client application 41B (B25).

[0066] When the client application 41B receives the posted label data 42 using the communication IF 13B, it stores the data in the memory 12B (B26). As shown in FIG. 2(B), the posted label data 42 includes the paid content IDs "cnt1" and "cnt4." As shown in FIG. 2(A), the paid content IDs "cnt1" and "cnt4" are included in user B's purchase information. In other words, user B has already purchased the paid content 421 with the special pictogram and the paid content 422 with the special font that are set in the selected posted label data 42. Therefore, user B can use the posted label data 42 downloaded to terminal 1B.

[0067] (Label Data Usage Process) Next, the procedure for the process of using label data will be described. Here, an example will be described in which user C uses terminal 1B, which is shared with user B, to use posted label data 42 downloaded by user B to terminal 1B. For ease of explanation, the terminal 1 used by user C and its components will be given the suffix "B." User C is an example of a "second logged-in user."

[0068] For example, user C starts the client application 41B and logs in to the label management server 3 using the user ID "aaa3" of user C. In this case, the client application 41B obtains from the label management server 3 the purchase information corresponding to the user ID "aaa3" of user C who uses the posted label data 42.

[0069] For example, when the client application 41B accepts an operation on the file button 202 displayed on the home screen 200 of Fig. 9(A), the client application 41B displays an edited label display screen 700 shown in Fig. 9(B) on the user IF 14B of the terminal 1B. The edited label display screen 700 displays selectable sample images 701 and 702 of label data stored on the terminal 1B and usable using the client application 41B. The label data usable using the client application 41B may be label data created or edited by the client application 41B, or may be label data downloaded from the label management server 3. For example, the sample image 701 corresponds to the posted label data 42 downloaded by user B from the label management server 3.

[0070] When the client application 41B receives the operation to select the sample image 701, it receives the selection of label data (D11) and then receives an instruction to open the selected label data (D12), as shown in Fig. 10. D11 is an example of a "selection process." The client application 41B then determines whether the user is logged in (D13).

[0071] If login information 44 is not stored in memory 12B, client application 41B determines that the user is not logged in (alt: not logged in). In this case, client application 41B has not acquired purchase information corresponding to the user ID of the logged-in user, and therefore causes terminal 1B to display login notification screen 511 shown in FIG. 9(C) (D41). Login notification screen 511 includes message 512 notifying the user that login is required and OK button 514. D41 is an example of a "login notification process."

[0072] The client application 41B also restricts the use of the selected posted label data 42 (D42). Restrictions on the use of the selected label data include not being able to open the selected label data, not being able to edit the selected label data even if it is opened, and not being able to print the selected label data. "Making it impossible to open" the label data 42 may mean not accepting an instruction to open the data while the label data is selected, or, even if it is possible to accept the instruction, notifying an error and canceling the process to open the label data. The same applies to "making it impossible to print" and "making it impossible to edit" the label data 42. This prevents user C from using label data that cannot be determined to include paid content or functions that user C has not yet purchased. D42 is an example of a "paid label restriction process."

[0073] On the other hand, if login information 44 is stored in memory 12B, client application 41B determines that the user is logged in (alt: logged in). In this case, client application 41B resets purchase information 45 stored in memory 12B (D20) and executes purchase information acquisition processing (A16). The procedure for the purchase information acquisition processing has been described above, so a detailed description will be omitted. This allows client application 41B to store purchase information 45 corresponding to login user C's user ID "aaa3" in memory 12B immediately before opening posted label data 42, thereby improving the accuracy of determining whether or not there is any paid content or function that has not yet been purchased.

[0074] 10 , the client application 41B acquires (D21) the paid content ID of the paid content or function set in the selected posted label data 42. For example, the client application 41B acquires the paid content ID from the selected posted label data 42. The client application 41B acquires, from the memory 12B, the purchase information 45 corresponding to the user ID of user C (D22).

[0075] The client application 41B compares the paid content IDs of the posted label data 42 acquired in D21 with the purchase information 45 acquired in D22 (D23) and determines whether unpurchased paid content and functions are included in the selected posted label data 42 (D24). If at least one of the paid content IDs acquired in D21 is not included in the purchase information 45 acquired in D22, the client application 41B determines that unpurchased paid content and functions are included in the selected posted label data 42, and if all of the paid content IDs acquired in D21 are included in the purchase information 45 acquired in D22, the client application 41B determines that unpurchased paid content and functions are not included in the selected posted label data 42. D24 is an example of a "determination process."

[0076] In this embodiment, as shown in FIG. 2(B), the posted label data 42 with the label ID "ddd1" includes the paid content IDs "ctn1" and "ctn4." On the other hand, as shown in FIG. 2(A), the purchase information 45 corresponding to user C's user ID "aaa3" does not include the paid content IDs "cnt1" and "cnt4." Therefore, the paid content ID of the paid content or function set in the posted label data 42 is not included in the purchase information 45 of logged-in user C. In this case, the client application 41B determines that the selected posted label data 42 includes paid content or a function that user C has not yet purchased (alt: present), and notifies the user that the selected posted label data 42 includes the unpurchased content or function (D31). D31 is an example of a "notification process."

[0077] The client application 41B of this embodiment displays a non-purchase notification screen 501 shown in FIG. 9D on the user IF 14B of the terminal 1B. For example, the non-purchase notification screen 501 includes a non-purchase notification message 502, a purchase suggestion message 503, a purchase button 504, and a "Do not purchase" button 505. The non-purchase notification message 502 includes a message notifying the user that the selected label data contains unpurchased content or function. The non-purchase notification message 502 may include a message notifying the user that the selected label data cannot be used because the selected label data contains unpurchased content or function. The purchase suggestion message 503 includes a message suggesting the purchase of the unpurchased content or function. The "Purchase" button 504 is an operation object that accepts a purchase instruction to purchase the unpurchased content or function. The "Do not purchase" button 505 is an operation object that accepts a purchase instruction not to purchase the unpurchased content or function.

[0078] For example, a URL corresponding to a content purchase screen is associated with the purchase button 504. When the client application 41B receives a purchase instruction in response to the operation of the purchase button 504 (D32: YES), the client application 41B accesses the URL and requests the purchase of the content (D33).

[0079] The label management server 3 performs the purchase process (D34). For example, the label management server 3 provides a content purchase screen to terminal 1B and causes client application 41B to display it. If unpurchased paid content IDs "cnt1" and "cnt4" are stored in the received URL query, the label management server 3 may display the content purchase screen with the paid content corresponding to the paid content IDs "cnt1" and "cnt4" automatically selected.

[0080] According to this, for example, user C can operate the server use button 203 to display the label search screen 300 on terminal 1B, and then tap the point content tab 322 displayed on the label search screen 300 as shown in FIG. 4(E) to switch the label search screen to a content purchase screen. Instead of performing such an operation procedure, user C can simply tap the purchase button 504 to display the content purchase screen on terminal 1B. Thus, client application 41B can reduce the operations required to purchase unpurchased content or functions, and encourage user C to purchase paid content.

[0081] 10 , when the purchase process is complete, the label management server 3 reads the paid content information 46 corresponding to the paid content IDs "cnt1" and "cnt4" from the content DB 8 and sends it to the client application 41B (D35). The client application 41B receives the paid content information 46 using the communication IF 13B and stores it in the memory 12B (D36). The label management server 3 also updates the user DB 6 (D40) in the same manner as in G07 of FIG. 3. Thereafter, the client application 41B opens the selected posted label data 42 (D37). For example, the client application 41B can open the contents of the posted label data 42 on an editing screen and edit the posted label data 42, or send the posted label data 42 to a label printer for printing.

[0082] On the other hand, if the client application 41B receives an operation of the "Do not purchase" button 505, it does not receive the purchase instruction (D32: NO). In this case, the client application 41B restricts the use of the posted label data 42, as in D42 (D38). D38 is an example of a "selected label restriction process."

[0083] If all of the paid content IDs in the posted label data 42 acquired in D21 are included in the purchase information 45 acquired in D22, the client application 41B determines that the selected label data does not contain any unpurchased paid content or functions (D24, alt: none). In this case, the client application 41B, for example, opens the selected label data (D39). D39 is the same process as D37, so its description is omitted.

[0084] When users B and C share posted label data 42 using the sharing function, user C can access and use the posted label data 42 downloaded by user B using terminal 1B from another terminal 1C.

[0085] However, by executing the process shown in Figure 10, the client application 41C of terminal 1C can obtain purchase information corresponding to user C's user ID before selecting and opening the posted label data 42, determine that the posted label data 42 contains paid content that user C has not yet purchased, and notify user C of this fact or restrict the use of the posted label data 42.

[0086] As described above in detail, when paid content or functions included in selected label data 42 have not yet been purchased, the terminal 1 equipped with the client application 41 of this embodiment executes the client application 41 to notify the user that the selected label data 42 includes unpurchased content or functions. This makes it easier for the logged-in user using the client application 41 to notice that the unpurchased content or functions are present. This also encourages the user to purchase the unpurchased content or functions. Thus, this embodiment realizes a technology that makes it easy to use label data that includes settings for paid content or functions in a system that attempts to use label data.

[0087] The embodiments disclosed in this specification are merely examples and do not limit the present invention in any way. Therefore, the technology disclosed in this specification can naturally be improved and modified in various ways without departing from the spirit and scope of the invention. Furthermore, the number of printers connected to the terminal is not limited to the illustrated example, and may be two or more. The various notifications described in the above embodiments may be combined with a warning sound or voice in addition to a displayed message. Purchase information may be periodically acquired while the client application 41 is running.

[0088] The process of D38 shown in Fig. 10 may be omitted. However, by restricting the use of label data that includes unpurchased content or functions, the logged-in user can be prompted to purchase the unpurchased content or functions.

[0089] 5A may be omitted. However, if the login is successful, the client application 41 can obtain the purchase information of the logged-in user, thereby determining whether the logged-in user has already purchased the paid content or function included in the selected label data while in the logged-in state.

[0090] 6 may be omitted. Furthermore, when the server use button 203 is operated, it is not necessary to acquire purchase information from the label management server 3. However, by performing the purchase information acquisition process even when the application is restarted while logged in or when an operation to use the label management server 3 is accepted after successful login, the client application 41 can acquire purchase information that reflects the purchase details from the label management server 3 and update the purchase information it holds, even if paid content or a function is purchased using another program or another device after successful login. This allows the client application 41 to accurately determine whether paid content, etc. has been purchased.

[0091] The processing from D13 onward in Fig. 10 may be omitted. However, by acquiring purchase information corresponding to the login ID when an instruction to open selected label data is given, the purchase information is updated immediately before determining whether or not paid content, etc. has been purchased, allowing for highly accurate determination of whether or not paid content, etc. has been purchased. In particular, compared to executing the purchase information acquisition process when login is successful or when login is already completed at the time of rebooting as shown in Figs. 5A and 6, purchasing information acquired more recently immediately before the determination process results in higher accuracy. On the other hand, by acquiring purchase information when login is successful or when login is already completed at the time of rebooting as shown in Figs. 5A and 6, it takes less time to open the label data than executing the purchase information acquisition process when opening label data as shown in Fig. 10.

[0092] The unpurchased notification screen 501 may notify only that there is unpurchased paid content and functions, omitting the purchase suggestion message 503, the Purchase button 504, and the Decline button 505. However, the client application 41 can also purchase unpurchased content and the like via the unpurchased notification screen 501, thereby reducing the effort required for purchasing.

[0093] 10 may be omitted. However, if the user is not logged in to the label management server 3, it is not possible to identify the user and to determine whether or not paid content or functions have been purchased. Therefore, if the client application 41 receives selection of label data for which paid content or functions are set when the user is not logged in, it notifies the user that logging in is required. This makes it easier for the user to notice that they are not logged in, and can prompt the user to perform the login operation.

[0094] The process of D42 in Fig. 10 may be omitted. However, when not logged in to the label management server 3, the use of label data that includes paid content or functions can be restricted, thereby preventing users who have not purchased the label data from using the label data.

[0095] The client application 41 may provide a print button on the edited label display screen 700 shown in Fig. 9(B) and, for example, accept a print instruction without opening the label data 42 by accepting an operation of the print button with the sample image 701 selected. In this case, the client application 41 may change D12 in Fig. 10 to a process for accepting a print instruction, D37 and D39 to a process for sending print data, and D38 and D42 to a process for not sending print data. This allows the client application 41 to accurately determine the presence or absence of unpurchased paid content or functions immediately before printing the label data, and to issue a notification or restrict printing if it determines that such content or functions exist.

[0096] The label DB 7 may be stored in multiple databases. For example, label data may be stored in a database separate from the label DB 7, and the URLs assigned to each piece of label data may be stored in the label DB 7 instead of the label data 73. Also, an object management database that manages objects that can be used for label data may be provided separate from the label DB 7, and paid content IDs may not be stored in the label data. The label management server 3 may compare paid content or functions set in label data with the object management database to create a paid content list.

[0097] 8 , the label management server 3 can transmit the label data to be downloaded to the terminal 1B even if the label data to be downloaded includes content or functions that the logged-in user has not yet purchased. In contrast, the label management server 3 may have a function to determine whether the label data to be downloaded includes content or functions that the logged-in user has not yet purchased, based on the logged-in user's purchase information. For example, at B24 in FIG. 8 , the label management server 3 reads the label data and paid content list associated with the received label ID from the label DB 7. The label management server 3 also reads the purchase information corresponding to the received user ID from the user DB 6.

[0098] If all of the paid content IDs included in the read paid content list are included in the read purchase information, the label management server 3 determines that the posted label data to be downloaded does not contain any unpurchased content or functions, and sends the read label data to the client application 41 B. On the other hand, if the read purchase information does not contain at least one of the paid content IDs included in the read paid content list, the label management server 3 determines that the label data to be downloaded contains any unpurchased content or functions, and does not send the read label data to the client application 41 B. This makes it possible to prevent label data including unpurchased paid content or functions from being downloaded to the terminal 1 B and used.

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

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

[0101] 100 Label management system 1 Terminal 2 Label printer 3 Label management server 6 User DB

Claims

1. A program executable by a computer of an information processing device connectable to a server, the server being capable of storing a plurality of label data, the label data being data that can be printed by a label printer, the label data being capable of including settings for paid content or paid functions, the server being further capable of accessing a purchase information database, the purchase information database storing purchase information indicating whether or not paid content and functions have been purchased for each user ID, the computer being capable of executing: a login process for requesting login to the server in association with the user ID; and a download process for downloading at least one of the label data stored in the server from the server and storing it in a memory of the information processing device while logged in to the server, the computer being further capable of executing: an acquisition process for acquiring the purchase information corresponding to the user ID of the logged-in user via the server while logged in to the server, a selection process for selecting the label data to be used, and a determination process for determining whether or not settings for paid content or functions that have not been purchased are included in the label data selected in the selection process based on the purchase information acquired in the acquisition process, the computer being further capable of executing: a program configured to execute a notification process for notifying a user interface of the information processing device that the label data selected in the selection process includes settings for unpurchased content or functions when the determination process determines that the label data includes settings for unpurchased content or functions.

2. A program as described in claim 1, further configured to cause the computer to execute a selection label restriction process for restricting the use of the label data selected in the selection process when it is determined in the determination process that the label data includes settings for unpurchased content or functions.

3. A program as recited in claim 2, wherein the selected label restriction process restricts the use of the label data selected in the selection process by making it impossible to open the label data.

4. A program as recited in claim 2, wherein the selected label restriction process restricts the use of the label data selected in the selection process by making it impossible to print the label data.

5. A program as recited in claim 2, wherein the selected label restriction process restricts the use of the label data selected in the selection process by making the label data selected in the selection process uneditable.

6. The program according to claim 1, configured to cause the computer to execute the acquisition process when login to the server is successful in the login process.

7. A program as recited in claim 6, configured to cause the computer to execute the login process when the program is started after the program is terminated while the user remains logged in to the server, and to execute the acquisition process when login to the server is successful in the login process.

8. A program as described in claim 6, configured to cause the computer to execute the acquisition process even when a specified operation for using the server is received via the user interface of the information processing device after successfully logging in to the server in the login process.

9. A program as recited in claim 1, configured to cause the computer to execute the acquisition process before executing the determination process when an instruction to open the label data selected in the selection process is received.

10. A program as recited in claim 1, wherein the notification process is capable of accepting a purchase instruction for unpurchased content or function included in the label data selected in the selection process, and when the purchase instruction is accepted, causes the computer to execute a purchase process to purchase the unpurchased content or function.

11. A program as recited in claim 1, configured to cause the computer to execute a login notification process that notifies the user interface of the information processing device that login is required when label data including paid content or function settings is selected while the user is not logged in to the server.

12. The program according to claim 11, further configured to cause the computer to execute a paid label restriction process for restricting the use of selected label data when label data including paid content or function settings is selected while the user is not logged in to the server.

13. A program as recited in claim 1, wherein a second logged-in user different from the first logged-in user can access the label data downloaded by a first logged-in user in the download process, and wherein, in the selection process, the label data stored in the memory in the download process and downloaded from the server by a user different from the logged-in user can be selected.

14. A program as recited in claim 1, configured to be capable of sharing the label data stored in a device other than the information processing device, and to be capable of selecting, in the selection process, the label data stored in the other device and downloaded by the other device from the server.

15. An information processing device connectable to a server, the label data being data that can be printed by a label printer, the server being capable of storing a plurality of label data, the label data being capable of including settings for paid content or paid functions, the server being further capable of accessing a purchase information database, the purchase information database storing purchase information indicating whether or not paid content and functions have been purchased for each user ID, the information processing device being capable of executing: a login process for requesting login to the server in association with a user ID; and a download process for downloading at least one of the label data stored in the server from the server and storing the label data in a memory of the information processing device while logged in to the server, the information processing device being further capable of executing: an acquisition process for acquiring the purchase information corresponding to the user ID of the logged-in user via the server while logged in to the server, a selection process for selecting the label data to be used, and a determination process for determining whether or not settings for paid content or functions that have not been purchased are included in the label data selected in the selection process based on the purchase information acquired in the acquisition process, the information processing device being further When it is determined in the determination process that the setting of a content or function that has not been purchased is included, a notification process is executed to notify a user interface of the information processing device that the label data selected in the selection process includes a content or function that has not been purchased.

16. 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, wherein the server, when a login is requested, executes a login process based on a user ID associated with the login request, the server is further capable of storing label data in association with the user ID, the label data being data that can be printed by a label printer, and the label data can include settings for paid content or paid functions, the server is further capable of accessing a purchase information database, and purchase information indicating whether or not paid content and functions have been purchased is stored for each user ID, the first information processing device is capable of executing a first login process to request a login to the server in association with the user ID, and an upload process to upload posted label data, which is the label data held by the first information processing device, to the server in association with the user ID of the logged-in user, while logged in to the server, the server, The posted label data uploaded from the first information processing device is stored in association with the user ID associated with the uploaded posted label data, and the second information processing device is capable of executing: a second login process for requesting login to the server in association with a user ID; and a download process for downloading at least one of the posted label data stored in the server from the server and storing the data in a memory of the second information processing device while logged in to the server; and the second information processing device further executes: an acquisition process for acquiring the purchase information corresponding to the user ID of the logged-in user via the server while logged in to the server; and a selection process for selecting the posted label data to be used;a determination process for determining whether or not the posted label data selected in the selection process includes settings for unpurchased paid content or functions based on the purchase information acquired in the acquisition process; and the second information processing device is further configured to execute a notification process for notifying, on a user interface of the information processing device, that the posted label data selected in the selection process includes settings for unpurchased content or functions when it is determined in the determination process that the posted label data includes settings for unpurchased content or functions.

Images