Data utilization method, data management device and program

The method facilitates sharing of nail printer design data among users, enhancing convenience by associating purchased design data with multiple users through a management server, thus reducing individual purchase requirements.

JP2026043018APending Publication Date: 2026-03-11CASIO COMPUTER CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2026-01-14
Publication Date
2026-03-11

AI Technical Summary

Technical Problem

Conventional nail printers require each user to separately purchase design data for matching designs, which is inconvenient for multiple users.

Method used

A data utilization method that allows a first user to associate design data with one or more second users, enabling them to use the design data without separate purchase through a management server that manages user information and design data availability.

Benefits of technology

Enhances convenience by allowing multiple users to share design data, improving user experience and reducing the need for individual purchases.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026043018000001_ABST
    Figure 2026043018000001_ABST
Patent Text Reader

Abstract

To improve convenience when multiple people use data. [Solution] The data usage method generates usage information that associates the design set with the first user and the second user by setting at least one second user (e.g., user B, user C) who will be a user of a design set that includes at least one type of design data and is purchased by a first user (e.g., user A) based on the operation of the first user, and controls the design set so that at least one type of design data included in the design set is made available to at least the second user based on the usage information.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a data utilization method, a data management device, and a program. [Background technology]

[0002] Conventionally, printing devices (nail printers) that print various designs on fingernails have been known. With these nail printers, the finger corresponding to the nail to be printed is placed on a finger rest, and printing is performed on the nail using an inkjet method or the like.

[0003] Generally, nail printers print based on designs that users own or have purchased in advance. Patent Document 1 discloses a print support server that manages the purchase, settlement, and usage rights of paid nail design data. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6481066 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in a system such as the above-described conventional technology, for example, in order for friends to use matching paid design data, each user must purchase the design data separately, which is inconvenient.

[0006] The present invention has been made in consideration of the problems in the conventional technology described above, and aims to provide a data usage method, data management device, and program that improve convenience when multiple people use data. [Means for solving the problem]

[0007] In order to solve the above problems, the data utilization method of the present invention comprises: The computer generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; Based on the usage information, control is performed to make the at least one type of design data included in the design set available to at least the second user. It is characterized by: [Effects of the Invention]

[0008] According to the present invention, it is possible to improve convenience when multiple people use data. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating a system configuration of a printing system and a control configuration of a management server according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram showing an outline of an idea according to the present invention. [Figure 3] 1A is a diagram showing an example of the data structure of a design data table, and FIG. 1B is a diagram showing an example of the data structure of a design set table. [Figure 4] 1A is a diagram showing an example of the data configuration of a user availability table, FIG. 1B is a diagram showing an example of the data configuration of a print history table, and FIG. 1C is a diagram showing an example of the data configuration of a print schedule table. [Figure 5] 1A is a diagram illustrating the control configuration of a printing device, and FIG. 1B is a diagram illustrating the control configuration of a user terminal. [Figure 6] 10 is a flowchart showing a design purchasing process. [Figure 7] 10 is an example of a design purchase screen displayed on a user terminal. [Figure 8]10 is a flowchart showing a sharing destination setting process. [Figure 9] 10 is an example of a purchased design list screen displayed on a user terminal. [Figure 10] 10 is an example of a sharing destination setting screen displayed on a user terminal. [Figure 11] 10 is a flowchart showing a process for determining whether a design can be used; [Figure 12] 10 is a flowchart showing a print history display process. [Figure 13] 10 is an example of a print history screen displayed on a user terminal. [Figure 14] 10 is a flowchart showing a print schedule display process. [Figure 15] 10 is an example of a print schedule screen displayed on a user terminal. [Figure 16] 10 is a flowchart showing highlighting processing in Modification 1. [Figure 17] 10 is an example of a design list screen including highlighting displayed on a user terminal. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of a data utilization method, a data management device, and a program according to the present invention will be described with reference to the drawings. It should be noted that the embodiments described below are subject to various limitations that are technically preferable for carrying out the present invention, but the scope of the present invention is not limited to the following embodiments and illustrated examples.

[0011] [Printing system configuration] FIG. 1 is a diagram showing the system configuration of a printing system 100 and the control configuration of a management server 1 serving as a data management device. 1, the printing system 100 is configured to include a management server 1, a printing device 2, a user terminal 3, and a payment server 4. The management server 1 is capable of data communication with the printing device 2, the user terminal 3, and the payment server 4 via a network N such as the Internet. Furthermore, data communication is possible between the printing device 2 and the user terminal 3 via the network N or directly. 1 shows one printing device 2 and one user terminal 3, the number of printing devices 2 and user terminals 3 is not limited. The management server 1 can manage multiple printing devices 2, and each user can use their own user terminal 3.

[0012] The management server 1 is a server that manages information about designs to be printed by the printing device 2 and information about users who use the printing device 2. The designs managed by the management server 1 are available to users for use, either for a fee or free of charge.

[0013] The printing device 2 is a nail printer that prints nail designs onto the nails of the user's fingers. An opening (not shown) is formed in the printing device 2, and a finger rest (not shown) is provided inside the opening on which the finger having the nail to be printed is placed.

[0014] The printing device 2 is intended to be installed in a store such as a nail salon or beauty salon, but may also be used in a user's home or the like. In this embodiment, the printing device 2 will be described taking as an example a case where the printing target is fingernails, but the printing target of the printing device 2 is not limited to fingernails. For example, the printing target may be toenails, or the printing target may be something other than nails, such as nail tips or the surfaces of various accessories.

[0015] The user terminal 3 functions exclusively as a user interface, and is, for example, a mobile terminal such as a smartphone, a tablet, a mobile phone, or a personal computer. Each user can operate the user terminal 3 to register user information on the management server 1, view and purchase designs, and make settings related to sharing designs with other users. The user terminal 3 is not particularly limited as long as it is capable of communicating with the printing device 2 and the management server 1, and may be, for example, a laptop or stationary personal computer, a game terminal device, or the like.

[0016] In cases where a user uses a printing device 2 in a store, the user terminal 3 and the printing device 2 must be housed in separate housings. On the other hand, when the user uses the printing device 2 at home, the printing device 2 and the user terminal 3 may be integrated into one unit.

[0017] The payment server 4 is a server device managed by a service company that provides payment services, and performs payment processing when a user purchases a paid design. The payment server 4 associates a user ID with a payment method for each user. The payment method can be selected from payment by credit card, payment by debit from a bank account, payment by pre-charged amount, etc. When a design purchase operation is performed from the user terminal 3, the payment server 4 performs payment processing for the corresponding user in accordance with the purchase processing by the management server 1.

[0018] [Idea summary] FIG. 2 shows an overview of the idea according to the present invention. Paid design data is included among the design data managed by the management server 1 and available to the printing device 2. By purchasing the paid design data, the user can use the printing device 2 to print using the design data. For each paid design data, the maximum number of users (users other than the purchasing user) that can be set as sharing destinations (2, 3, 5, 10, etc.) is predetermined. A user (first user) who has purchased sharable design data can specify users (second users) with whom the design data will be shared.

[0019] In this embodiment, a first user sets a second user as a user, which allows both the first and second users to use the design data, and therefore the state in which certain design data is available to multiple users is expressed as "sharing" the design data.

[0020] Furthermore, design data can be purchased individually (one type) or as a set containing multiple types of design data. When purchasing a design set, sharing destinations can be set for the design set. For example, design data for 20 fingers can be designed so that all the designs can be completed by two users. Note that even for one type of design data, the portion for the purchasing user and the portion for the sharing user can be referred to as a "design set."

[0021] Information about users who share designs (design data / design sets) is managed by the management server 1. Users designated as sharing destinations can use the design data without purchasing it.

[0022] Whether or not a user using the printing device 2 can use paid design data is determined using usage information managed in the management server 1 (details will be described later) and identification information (user ID, etc.) of the user using the printing device 2. In the example shown in Figure 2, first, user A purchases a design set called the Sho-Take-Ume set. The Sho-Take-Ume set includes pine design data, bamboo design data, and plum design data. Here, the maximum number of users that can be set as sharing destinations for the Sho-Take-Ume set is set to "2." User A can specify two sharing destinations, allowing a total of three people to share the data. If user A sets user B and user C as sharing destinations for the Sho-Take-Ume set, user B and user C will be able to use the design data of the Sho-Take-Ume set free of charge.

[0023] [Administration Server Configuration] As shown in FIG. 1, the management server 1 includes a control device 10, a communication unit 13, a clock unit 14, and the like. The control device 10 is a computer including a control unit 11 having a processor such as a CPU (Central Processing Unit), and a storage unit 12 having a ROM (Read Only Memory), a RAM (Random Access Memory), and the like.

[0024] The control unit 11 comprehensively controls the operation of each unit of the management server 1. The control unit 11 realizes various functions for operating the management server 1 in cooperation with programs stored in the storage unit 12, etc.

[0025] The storage unit 12 stores various programs and various data for operating each unit of the management server 1. The storage unit 12 has a design database 121 and a user database 122.

[0026] A plurality of design data, which is information on nail designs, is stored in the design database 121. The design database 121 includes a design data table T1 and a design set table T2.

[0027] The design data table T1 is a table for managing design data. 3A shows an example of the data configuration of the design data table T1. In the design data table T1, a design data ID, a design data name, a maximum number of sharing destinations, etc. are stored in association with each piece of design data. The "design data ID" field stores identification information (design data ID) for identifying the design data. The "design data name" field stores the name of the design data. The "Maximum number of sharing destinations" field stores the maximum number of users who can be set as sharing destinations of the design data (users other than the purchasing user).

[0028] A collection of multiple pieces of design data is treated as a design set. The design set table T2 is a table for managing the correspondence between design sets and the design data included in the set. 3(b) shows an example of the data structure of the design set table T2. In the design set table T2, for each design data included in a design set, the design set ID, design set name, design data ID, maximum number of sharing destinations, etc. are stored in association with each other. The "design set ID" field stores identification information (design set ID) for identifying the design set that includes the corresponding design data. The "design set name" field stores the name of the design set that includes the corresponding design data. The "design data ID" field stores the design data ID of the corresponding design data. The "Maximum number of sharing destinations" field stores the maximum number of users (users other than the purchasing user) that can be set as sharing destinations of the design set that includes the corresponding design data.

[0029] The user database 122 stores user information (user ID, user name, etc.) for each user registered in the printing system 100. The user ID is identification information for identifying a user, and is set when the user registers for a service provided by the management server 1. The user name is the name of the user. The user database 122 stores the correspondence between the user ID and the user name. The user database 122 includes a user availability table T3, a print history table T4, and a print schedule table T5.

[0030] The user availability table T3 is a table for managing information on availability of design data or design sets for each user. 4(a) shows an example of the data configuration of the user availability table T3. The user availability table T3 stores user IDs, user names, design data IDs / design set IDs, availability, etc. in association with each other. The "user ID" field stores the user ID of the user who purchased the design (the user who set the sharing destination) or the user ID of the user who was set as the sharing destination. The "user name" field stores the user name of the user corresponding to the "user ID." The "Design Data ID / Design Set ID" field stores the design data ID of the design data or the design set ID of the design set that is the target of purchase / sharing settings.

[0031] The "Availability" field stores information indicating the reason why the user corresponding to the "User ID" can use the design data or design set corresponding to the "Design Data ID / Design Set ID." Specifically, "Availability" can be "Purchased" or "Shared with XX." "Purchased" indicates that the user corresponding to the "User ID" has purchased the design data or design set corresponding to the "Design Data ID / Design Set ID" and therefore can use the design data or design set. "Shared with XX" indicates that the user corresponding to the "User ID" can use the design data or design set corresponding to the "Design Data ID / Design Set ID" because another user (the setting user) has set the user corresponding to the "User ID" as a sharing destination. Note that the "XX" in "Shared with XX" is replaced with the user ID of the setting user. Thus, the usage information managed in the User Availability Table T3 includes information indicating whether at least one type of design data can be used by the first user (the setting user) and the second user (the sharing destination user).

[0032] The print history table T4 is a table for managing information on the print history of each user. 4B shows an example of the data configuration of the print history table T4. In the print history table T4, the user ID, user name, print date and time, design data ID, etc. are stored in association with each print history. The "user ID" field stores the user ID of the user who performed the printing (nail print). The "user name" field stores the user name of the user corresponding to the "user ID." The "printing date and time" field stores the date and time when printing (nail printing) was performed. The "design data ID" field stores the design data ID of the design data used by the user corresponding to the "user ID."

[0033] The print schedule table T5 is a table for managing information about print schedules for each user. 4(c) shows an example of the data configuration of the print schedule table T5. In the print schedule table T5, a user ID, a user name, a scheduled print date and time, a design data ID, etc. are stored in association with each print schedule. The "user ID" field stores the user ID of the user who will be performing printing (nail printing). The "user name" field stores the user name of the user corresponding to the "user ID." The "scheduled printing date and time" field stores the date and time when printing (nail printing) is scheduled to be performed. The "design data ID" field stores the design data ID of the design data to be used by the user corresponding to the "user ID."

[0034] The communication unit 13 performs wired or wireless data communication via the network N, etc. However, the communication method of the communication unit 13 is not particularly limited as long as data communication with external devices such as the printing device 2, the user terminal 3, and the payment server 4 is possible, and a method that matches the communication standard of the external device is applied.

[0035] The timekeeping unit 14 has a timekeeping circuit (RTC: Real Time Clock), and measures the current date and time using this timekeeping circuit and outputs it to the control unit 11.

[0036] The control unit 11 performs a purchasing process for a design set including at least one type of design data based on the operation of the first user (purchasing user) from the user terminal 3. Hereinafter, when a design set is composed of one type of design data, it may be simply referred to as "design data."

[0037] The control unit 11 generates usage information that associates the design set with the first and second users by setting at least one second user (shared user) who will be the user of the design set purchased by the first user, including at least one type of design data, based on the operation of the first user (setting user) from the user terminal 3. Specifically, in the user usage availability table T3, associating the "design data ID" or "design set ID" corresponding to the design purchased by the first user with the "user ID" and "user name" of the second user and the "usability" information "shared with (first user's user ID)" corresponds to generating usage information.

[0038] Based on the usage information, the control unit 11 controls the system so that at least one type of design data included in the design set is available to at least a second user. Specifically, the control unit 11 permits at least the second user to use at least one type of design data included in the design set. The control unit 11 allows the second user to use at least one type of design data included in the design set free of charge.

[0039] Furthermore, the control unit 11 controls the first user to use at least one type of design data included in the design set based on the usage information. In this embodiment, a case will be described in which the first user can also use at least one type of design data included in the design set, but the first user may not be able to use the design data.

[0040] Control unit 11 stores print history information as usage history information based on the design data used by each of the first and second users in storage unit 12. Specifically, when design data is used, control unit 11 associates the user ID, user name, print date and time, and design data ID of the design data of the user who used the design data with each other and stores them in print history table T4. In print history table T4, at least the correspondence between the user ID and the design data ID corresponds to print history information (usage history information).

[0041] [Printing device configuration] Fig. 5(a) is a diagram showing the control configuration of the printing device 2. As shown in Fig. 5(a), the printing device 2 includes a control device 20, an operation unit 23, a display unit 24, a communication unit 25, a printing unit 26, and a photographing unit 27.

[0042] The operation unit 23 is configured to allow various inputs, settings, etc. to be performed in response to user operations, and an input signal corresponding to the operation received by the operation unit 23 is sent to the control device 20. The operation unit 23 includes, for example, an operation button for turning on / off the power of the printing device 2. However, the specific configuration of the operation unit 23 is not particularly limited, and for example, various operation buttons, a keyboard, a pointing device, a touch panel, etc. may be provided as the operation unit 23.

[0043] The display unit 24 is configured with a liquid crystal display (LCD), an organic electroluminescence display (OLED), other flat displays, etc., and displays various information in response to a display command from the control device 20. In addition, various indicators, etc. may be provided as the display unit 24. The printing device 2 may operate in accordance with an operation signal input from an external device such as the user terminal 3, and in this case, the printing device 2 may not be provided with the operation unit 23 or the display unit 24.

[0044] The communication unit 25 performs wired or wireless data communication via the network N, etc. However, the communication method of the communication unit 25 is not particularly limited as long as it is capable of data communication with the user terminal 3 or the management server 1, and may be, for example, a method using a network line such as the Internet, or a method performing wireless communication based on a short-range wireless communication standard such as Bluetooth (registered trademark) or Wi-Fi (registered trademark).

[0045] The printing unit 26 is a printing means that prints on the nails that are the printing target. The printing unit 26 includes a print head 261 that performs the printing operation, a head moving mechanism 262 that moves the print head 261, and the like. The print head 261 prints a design on the nail and is capable of ejecting ink of various colors, such as cyan (C; CYAN), magenta (M; MAGENTA), and yellow (Y; YELLOW). The print head 261 is not particularly limited, but is an inkjet head that can perform fine printing by spraying fine droplets of ink (liquid) from an ink ejection surface onto the nail surface. Note that the types of ink that the print head 261 can eject are not limited to this, and it may be capable of ejecting ink of other colors. Furthermore, the type and number of print heads 261 are also not particularly limited, and for example, another print head that prints a base ink may be installed alongside. The head moving mechanism 262 is driven to move the print head 261 relative to the surface of the nail of the finger placed on the finger rest.

[0046] The photographing unit 27 is disposed above the finger rest inside the printing device 2. The photographing unit 27 photographs the surface of the nail (finger including the nail) and acquires the image (image of the finger including the nail). The photographing unit 27 includes an imaging camera 271, a lighting lamp 272, and the like. The imaging camera 271 is a small camera that includes a solid-state imaging element such as a CCD (Charge Coupled Device) type or a CMOS (Complementary Metal Oxide Semiconductor) type having 2 million or more pixels, a lens, and the like. The illumination lamp 272 is a light source that is disposed to the side of the imaging camera 271 and illuminates the nail to be photographed, and is, for example, a white LED.

[0047] The control device 20 includes a control unit 21 having a processor such as a CPU, and a storage unit 22 having a ROM, a RAM, and the like. The storage unit 22 stores various programs and various data for operating the printing device 2. Specifically, the ROM of the storage unit 22 stores various programs such as a printing program for performing printing processing. The control unit 21 loads a program stored in the ROM of the storage unit 22 into the work area of ​​the RAM and executes it, thereby comprehensively controlling the operation of each unit of the printing device 2. In other words, the control unit 21 works in cooperation with the program to realize various functions that allow the printing device 2 to perform printing processes, etc.

[0048] For example, the control unit 21 controls communication between the communication unit 25 and the user terminal 3 and the management server 1. Furthermore, the control unit 21 controls the imaging camera 271 and the illumination lamp 272 of the photographing unit 27 to photograph an image of the nail of the finger placed on the finger rest using the imaging camera 271. The control unit 21 extracts a nail region from the photographed image and generates nail information representing the shape of the nail region.

[0049] Furthermore, the control unit 21 generates print data based on the design data and nail information transmitted from the management server 1. The control unit 21 outputs a control signal to the printing unit 26 based on the print data, and controls the printing unit 26 to perform printing in accordance with the print data.

[0050] [User device configuration] Fig. 5(b) is a diagram showing the control configuration of the user terminal 3. As shown in Fig. 5(b), the user terminal 3 includes a control device 30, an operation unit 33, a display unit 34, a communication unit 35, and the like.

[0051] The operation unit 33 is capable of performing various inputs, settings, etc. in response to user operations, and an input signal corresponding to the operation received by the operation unit 33 is transmitted to the control device 30. A touch panel serving as the operation unit 33 is integrally provided on the surface of the display unit 34, and the user can perform various inputs, settings, etc. by touching the touch panel. Note that the operation unit 33 is not limited to a touch panel, and various operation buttons, a keyboard, a pointing device, etc. may be provided as the operation unit 33, for example.

[0052] The display unit 34 is configured with an LCD, an organic ELD, or other flat display, and displays various information in response to a display command from the control device 30.

[0053] The communication unit 35 performs wired or wireless data communication via the network N, etc. However, the communication method of the communication unit 35 is not particularly limited as long as data communication with the printing device 2 and the management server 1 is possible, and a method that matches the communication standards of the printing device 2 and the management server 1 is applied.

[0054] The control device 30 is a computer including a control unit 31 having a processor such as a CPU, and a storage unit 32 having a ROM, a RAM, and the like. The control unit 31 comprehensively controls the operation of each unit of the user terminal 3. The control unit 31 cooperates with programs stored in the storage unit 32 to realize various functions for operating the user terminal 3. The storage unit 32 stores various programs and various data for operating each unit of the user terminal 3. Specifically, the storage unit 32 stores various programs, such as an operating program for overall control of each unit of the user terminal 3, as well as a nail print application program for performing nail printing using the printing device 2, and the control unit 31 controls the user terminal 3 by expanding and executing these programs in the work area of ​​the storage unit 32.

[0055] [Operation in the printing system] Next, the operation of the printing system 100 will be described.

[0056] (Design purchase process) 6 is a flowchart showing the design purchasing process executed in the management server 1. The design purchasing process is a process performed when a first user (purchasing user) operates the user terminal 3 to purchase a design (design data or design set).

[0057] First, when the control unit 31 of the user terminal 3 accesses the management server 1 in response to the user's operation on the operation unit 33, the control unit 11 of the management server 1 generates data for the user ID input screen and transmits the data for the user ID input screen to the user terminal 3 via the communication unit 13. A user ID input screen is displayed on the display unit 34 of the user terminal 3. When the user operates the operation unit 33 to input his or her own user ID, the control unit 31 of the user terminal 3 transmits the input user ID to the management server 1 via the communication unit 35. The control unit 11 of the management server 1 acquires a user ID from the user terminal 3 via the communication unit 13 (step S1).

[0058] In addition, the correspondence between the user terminal 3 and the user ID may be registered in advance in the management server 1, and the management server 1 may identify the user terminal 3 that has accessed the management server 1, thereby obtaining the user ID corresponding to the user terminal 3.

[0059] Next, the control unit 11 of the management server 1 displays a list of the design data and design sets on the display unit 34 of the user terminal 3 (step S2). Specifically, the control unit 11 reads out the various design data registered in the design data table T1 and the various design sets registered in the design set table T2, generates data for a design purchase screen including a list of the design data and design sets, and transmits the data for the design purchase screen to the user terminal 3 via the communication unit 13. A design purchase screen is displayed on the display unit 34 of the user terminal 3.

[0060] 7 shows an example of a design purchase screen 341 displayed on the display unit 34 of the user terminal 3. The design purchase screen 341 includes a design data display area 51, a design set display area 52, a purchase button 53, and the like. In the design data display area 51, a list of design data is displayed. The design set display area 52 displays a list of design sets. The purchase button 53 is a button for issuing an instruction to purchase design data or a design set after the design data or the design set has been selected.

[0061] When a user operates the operation unit 33 of the user terminal 3 to select one of the design data or design sets to purchase from the list of design data and design sets on the design purchase screen, the control unit 31 of the user terminal 3 sends information indicating the selected design data or design set (design data ID or design set ID) to the management server 1 via the communication unit 35. The control unit 11 of the management server 1 acquires information (design data ID or design set ID) indicating the design data or design set selected by the user for purchase from the user terminal 3 via the communication unit 13 (step S3).

[0062] Next, the control unit 11 of the management server 1 performs a purchase process for the selected design data or design set (step S4). Specifically, the control unit 11 causes the payment server 4 to perform a payment process for the user (purchasing user) of the user terminal 3 to pay a predetermined amount for the selected design data or design set. The payment server 4 executes the payment process according to the payment method associated with the user ID of the purchasing user. The control unit 11 of the management server 1 may display a payment method selection screen on the display unit 34 of the user terminal 3, and allow the user to select a payment method on the spot.

[0063] Next, upon receiving a payment processing completion notification from the payment server 4, the control unit 11 of the management server 1 associates the purchasing user with the selected design data or design set and registers them in the user usage permission table T3 (step S5). Specifically, the control unit 11 stores the "user ID" acquired in step S1 in the "user ID" field, stores the "user name" corresponding to the user ID in the "user name" field, stores the "design data ID" or "design set ID" acquired in step S3 in the "design data ID / design set ID" field, and stores "Purchased" in the "Usability" field as a new record in the user usage permission table T3. This completes the design purchasing process.

[0064] (Sharing destination setting process) 8 is a flowchart showing a share destination setting process executed in the management server 1. The share destination setting process is a process performed when a first user (setting user) operates the user terminal 3 to set a second user (share destination user).

[0065] First, the control unit 11 of the management server 1 acquires a user ID from the user terminal 3 via the communication unit 13 (step S11). Details of the process are the same as step S1 of the design purchasing process (see FIG. 6).

[0066] Next, the control unit 11 of the management server 1 acquires the design data and design set purchased by the user corresponding to the user ID acquired in step S11 (step S12). Specifically, the control unit 11 acquires, from the user availability table T3, the "design data ID" or "design set ID" included in a record whose "user ID" field is the "user ID" acquired in step S11 and whose "availability" field is "purchased." The control unit 11 then acquires, from the design data table T1, the "design data name" and "maximum number of sharing destinations" corresponding to the acquired "design data ID." The control unit 11 also acquires, from the design set table T2, the "design set name" and "maximum number of sharing destinations" corresponding to the acquired "design set ID."

[0067] Next, the control unit 11 of the management server 1 displays a list of the purchased design data and design sets on the display unit 34 of the user terminal 3 (step S13). Specifically, the control unit 11 generates data for a design list screen including a list of the purchased design data and design sets, and transmits the data for the purchased design list screen to the user terminal 3 via the communication unit 13. The display unit 34 of the user terminal 3 displays a list screen of designs that have already been purchased.

[0068] 9 shows an example of a purchased design list screen 342 displayed on the display unit 34 of the user terminal 3. The purchased design list screen 342 includes a design display area 54. The design display area 54 displays a list of purchased design data and design sets.

[0069] When a user operates the operation unit 33 of the user terminal 3 to select the design data or design set to be shared from the purchased design list screen, the control unit 31 of the user terminal 3 sends information indicating the selected design data or design set (design data ID or design set ID) to the management server 1 via the communication unit 35. The control unit 11 of the management server 1 acquires information (design data ID or design set ID) indicating the design data or design set to be set as the sharing destination selected by the user from the user terminal 3 via the communication unit 13 (step S14).

[0070] Next, the control unit 11 of the management server 1 causes the display unit 34 of the user terminal 3 to display a share destination setting screen for the selected design data or design set (step S15). Specifically, the control unit 11 generates data for the share destination setting screen and transmits the data for the share destination setting screen to the user terminal 3 via the communication unit 13. A share destination setting screen is displayed on the display unit 34 of the user terminal 3.

[0071] 10 shows an example of a share destination setting screen 343 displayed on the display unit 34 of the user terminal 3. The share destination setting screen 343 includes a design display area 55, a share destination setting area 56, a confirm button 57, and the like. The name of the selected design data or design set is displayed in the design display area 55. Also, the maximum number of sharing destinations field 58 in the design display area 55 displays the maximum number of sharing destinations for the selected design data or design set. The share destination setting area 56 is an area for setting users who will be share destinations, and is provided with input boxes 59 and 60 equal to the maximum number of share destinations. Note that before users who will be share destinations are set, the input boxes 59 and 60 are blank. The confirm button 57 is a button for confirming the settings of the sharing destination user.

[0072] When a user operates the operation unit 33 of the user terminal 3 to input a sharing destination user on the sharing destination setting screen, the control unit 31 of the user terminal 3 transmits information indicating the input user (user name) to the management server 1 via the communication unit 35. The control unit 11 of the management server 1 acquires information indicating the sharing destination user (user name) input by the user from the user terminal 3 via the communication unit 13, and identifies the user ID corresponding to this username (step S16).

[0073] Next, the control unit 11 of the management server 1 reflects information indicating the setting user and information indicating the sharing destination user for the selected design data or design set in the user usage permission table T3 (step S17). Specifically, as a new record in the user usage permission table T3, the control unit 11 stores the "user ID" of the sharing destination user in the "user ID" field, stores the "user name" of the sharing destination user in the "user name" field, stores the "design data ID" of the design data or the "design set ID" of the design set acquired in step S14 in the "design data ID / design set ID" field, and stores "shared with (user ID of setting user)" in the "usability" field. The (user ID of setting user) is the user ID acquired in step S11. In this way, the control unit 11 generates usage information that associates the selected design data or design set with the setting user (first user) and the sharing destination user (second user). This completes the sharing destination setting process.

[0074] (Design usage availability determination process) 11 is a flowchart showing the design usability determination process executed in the management server 1. The design usability determination process is a process for determining whether or not each user is permitted to use design data.

[0075] The processing in steps S21 and S22 is the same as the processing in steps S1 and S2 of the design purchasing processing (see FIG. 6). However, in step S22, the list of design data and design sets displayed on the display unit 34 of the user terminal 3 is intended to allow the user to select the print target.

[0076] The user operates the operation unit 33 of the user terminal 3 to select one of the design data to be printed from the list of design data and design sets displayed on the display unit 34. When selecting design data included in a design set, the user first selects one of the design sets, and then selects one of the design data from the design data included in the selected design set. The control unit 31 of the user terminal 3 transmits information indicating the selected design data (design data ID) to the management server 1 via the communication unit 35. The control unit 11 of the management server 1 acquires information (design data ID) indicating the design data to be printed selected by the user from the user terminal 3 via the communication unit 13 (step S23).

[0077] Next, the control unit 11 of the management server 1 acquires the availability information of the selected design data from the user availability table T3 (step S24). Specifically, the control unit 11 extracts from the user availability table T3 records whose "user ID" field is the "user ID" acquired in step S21 and whose "design data ID / design set ID" field is the "design data ID" acquired in step S23 or the "design set ID" of the design set including the design data corresponding to the design data ID. If the selected design data has not been purchased or shared with others, the user availability table T3 does not contain any records that satisfy the above conditions, and therefore the design data cannot be used.

[0078] Next, the control unit 11 of the management server 1 determines whether the target user has already purchased the design data to be printed (step S25). Specifically, the control unit 11 determines whether the "Usability" field of the record extracted from the user usage permission table T3 is "Purchased."

[0079] If the target user has not yet purchased the design data to be printed (step S25; NO), the control unit 11 of the management server 1 determines whether the design data to be printed has been shared with other users (step S26). Specifically, the control unit 11 determines whether the "Usability" field of the record extracted from the user availability table T3 is "Shared with XX."

[0080] In step S25, if the target user has already purchased the design data to be printed (step S25; YES), or in step S26, if the design data to be printed has been shared with other users (step S26; YES), the control unit 11 of the management server 1 determines that the design data is available for use (step S27).

[0081] Next, the control unit 11 of the management server 1 displays a selection screen on the display unit 34 of the user terminal 3 to select whether to print immediately or at a later date, and accepts the user's selection operation on the operation unit 33 (step S28).

[0082] If printing is to be performed immediately (step S28; YES), the control unit 11 of the management server 1 transmits the selected design data to the printing device 2 used by the user via the communication unit 13 (step S29). The printing device 2 used by the user may be identified by being stored in advance in association with the user ID, or may be specified by the user on the spot.

[0083] The printing device 2 performs nail printing on the fingernails of the user's fingers based on the design data received from the management server 1. Specifically, the control unit 21 of the printing device 2 controls the photographing unit 27 to photograph an image of the fingernail placed on the finger rest, extracts a nail area from the photographed image, and generates nail information representing the shape of the nail area. The control unit 21 then generates print data based on the design data and the nail information, and controls the printing unit 26 to print on the fingernails of the user's fingers based on the print data.

[0084] Next, when the control unit 11 of the management server 1 receives a print completion notification from the printer 2, it registers the print history information in the print history table T4 (step S30). Specifically, the control unit 11 associates the "user ID" acquired in step S21, the "user name" corresponding to this user ID, the "print date and time," the "design data ID" acquired in step S23, etc., and stores them in the print history table T4. Note that when the control unit 11 receives a print completion notification from the printer 2, it acquires the current date and time from the clock unit 14 and sets this current date and time as the print date and time.

[0085] Next, the control unit 11 of the management server 1 notifies users in the same sharing group (the setting user and the shared users) that the shared design data has been used (step S31). For example, a push notification may be sent on an application on each user's user terminal 3, or an email may be sent to each user's email address. Users in the same sharing group include the setting user (purchasing user) who set the sharing destination for the design data to be printed or the design set including the design data, and the sharing destination user who was set as the sharing destination.

[0086] If the user ID acquired in step S21 is that of the purchasing user, the control unit 11 refers to the user availability table T3 and identifies the "user ID" and "user name" contained in the record whose "design data ID / design set ID" field is the "design data ID" acquired in step S23 or the "design set ID" of the design set containing the design data corresponding to the design data ID, and whose "availability" field is "shared with (user ID acquired in step S21)," as those of the sharing user.

[0087] If the user ID acquired in step S21 belongs to a sharing user, the control unit 11 refers to the user accessibility table T3 and identifies the purchasing user from "Shared with (the purchasing user's user ID)" in the "Accessibility" field included in a record whose "User ID" field is the "User ID" acquired in step S21 and whose "Design Data ID / Design Set ID" field is the "Design Data ID" acquired in step S23 or the "Design Set ID" of a design set including design data corresponding to the design data ID. The control unit 11 also refers to the user accessibility table T3 and identifies, as belonging to another sharing user, the "User ID" and "User Name" included in a record whose "Design Data ID / Design Set ID" field and "Accessibility" field are common to the record of the "User ID" acquired in step S21.

[0088] In step S28, if printing is not to be performed immediately (step S28; NO), that is, if printing is to be performed at a later date, the control unit 11 of the management server 1 displays an input screen for inputting the print schedule information on the display unit 34 of the user terminal 3, and accepts input operations from the user on the operation unit 33. Then, when the print schedule information is input on the user terminal 3, the control unit 11 of the management server 1 acquires the input print schedule information (scheduled print date and time, etc.) via the communication unit 13 (step S32).

[0089] Next, the control unit 11 of the management server 1 registers the print schedule information in the print schedule table T5 (step S33). Specifically, the control unit 11 associates the "user ID" acquired in step S21, the "user name" corresponding to this user ID, the "scheduled print date and time" included in the print schedule information acquired in step S32, the "design data ID" acquired in step S23, etc., and stores them in the print history table T4. At this point, users in the same sharing group (the setting user and the shared users) may be notified that they plan to use the shared design data.

[0090] In step S26, if the design data to be printed is not shared with other users (step S26; NO), the control unit 11 of the management server 1 determines that the design data is not available (step S34).

[0091] After step S31, step S33 or step S34, the design usability determination process ends.

[0092] In the design usage availability determination process, when design data is used and print history information is registered in print history table T4, in step S31 users in the same sharing group are notified that the shared design data has been used, but the notification does not have to be at this timing. For example, users in the same sharing group may be notified of updated print history information once a day at a predetermined time. Similarly, for print schedule information, updated print schedule information within the same sharing group may be notified once a day at a predetermined time.

[0093] Furthermore, the user may register the print schedule information from the user terminal 3 as described above, or, in the case of using the store's printing device 2, the print schedule information may be registered in the management server 1 at the same time as reserving use of the store's printing device 2.

[0094] (Print history display process) 12 is a flowchart showing the print history display process executed in the management server 1. The print history display process is a process performed when a user operates the user terminal 3 to view the print history of users in the same sharing group. Apart from the process of step S31 of the design usage availability determination process (see FIG. 11), the user can check the print history at any time they wish.

[0095] First, the control unit 11 of the management server 1 acquires a user ID from the user terminal 3 via the communication unit 13 (step S41). Details of the process are the same as step S1 of the design purchasing process (see FIG. 6).

[0096] Next, the control unit 11 of the management server 1 acquires information on design data and design sets available to the user operating the user terminal 3 from the user availability table T3 (step S42). Specifically, the control unit 11 acquires from the user availability table T3 the "design data ID" or "design set ID" included in a record whose "user ID" field is the "user ID" acquired in step S41 and whose "availability" field is "purchased" or "shared with XX."

[0097] Next, the control unit 11 of the management server 1 refers to the user availability table T3 for each design (design data and design set) available to the user operating the user terminal 3 to identify users in the same sharing group, and acquires print history information of users in the same sharing group from the print history table T4 (step S43). Users in the same sharing group include the setting user (purchasing user) who set the sharing destination for the design to be processed, and the sharing destination user who was set as the sharing destination.

[0098] Next, the control unit 11 of the management server 1 causes the display unit 34 of the user terminal 3 to display the print history information of the users in the same sharing group (step S44). Specifically, the control unit 11 generates data for a print history screen for displaying the print history information of the users in the same sharing group, and transmits the data to the user terminal 3 via the communication unit 13. The display unit 34 of the user terminal 3 displays a print history screen.

[0099] 13 shows an example of a print history screen 344 displayed on the display unit 34 of the user terminal 3. The print history screen 344 includes a print history display area 61 and the like. In the print history display area 61, the design data name, user name, and print date and time are displayed for users in the same sharing group who have a print history. This completes the print history display process.

[0100] By disclosing to users in the same sharing group when design data was used, users in the same sharing group can know each other's usage status.

[0101] (Print schedule display process) 14 is a flowchart showing the print schedule display process executed in the management server 1. The print schedule display process is a process performed when a user operates the user terminal 3 to view print schedules of users in the same sharing group.

[0102] The processes in steps S51 and S52 are the same as the processes in steps S41 and S42 in the print history display process (see FIG. 12).

[0103] Next, the control unit 11 of the management server 1 refers to the user availability table T3 for each design (design data and design set) available to the user operating the user terminal 3 to identify users in the same sharing group, and acquires print schedule information for users in the same sharing group from the print schedule table T5 (step S53). Users in the same sharing group include the setting user (purchasing user) who set the sharing destination for the design to be processed, and the sharing destination users who were set as sharing destinations.

[0104] Next, the control unit 11 of the management server 1 causes the display unit 34 of the user terminal 3 to display the print schedule information of the users in the same sharing group (step S54). Specifically, the control unit 11 generates data for a print schedule screen for displaying the print schedule information of the users in the same sharing group, and transmits the data to the user terminal 3 via the communication unit 13. The display unit 34 of the user terminal 3 displays a print schedule screen.

[0105] 15 shows an example of a print schedule screen 345 displayed on the display unit 34 of the user terminal 3. The print schedule screen 345 includes a print schedule display area 62 and the like. In the print schedule display area 62, the design data name, user name, and print schedule date and time are displayed for users in the same sharing group who have print schedules. This completes the print schedule display process.

[0106] By publishing the planned use date of design data to users in the same sharing group, users in the same sharing group can check each other's planned use. By referencing the planned use dates of users in the same sharing group, users can, for example, use matching nail designs (with a similar theme) on the same day.

[0107] As described above, according to this embodiment, by setting the users with whom design data or design sets purchased by one user will be shared, each user does not need to purchase the design data or design sets individually, improving the convenience of using data among multiple users. By allowing multiple users to use the data, each user can enjoy using the printing system 100, which promotes sales of design data and revitalizes the community. It also makes it easier for users to take the action of "My friend recommended (shared) a matching design with me, so I'll try it too." It also makes it easier to sell not only single design data, but also multiple types of design data as a set.

[0108] Furthermore, by permitting the purchasing user and the shared users to use the design data or the design data included in the design set, each user can use the shared data.

[0109] Furthermore, the number of share destination users can be set up to a predetermined maximum number for the design data or design set.

[0110] Furthermore, print history table T4 stores print history information (usage history information) based on the design data used by each user, including the purchasing user and the sharing user, so that each user can leave a history of using the design data. Furthermore, users in the same sharing group can share print history information and print schedule information.

[0111] [Variation 1] Next, a description will be given of Modification 1. In Modification 1, the description of the same configurations and processes as those in the above embodiment will be omitted, and only the configurations and processes that are characteristic of Modification 1 will be described. In variant example 1, after usage information (correspondence between design set, purchasing user, and shared user) is generated, when using design data contained in the design set related to this usage information, the management server 1 makes suggestions based on the printing history information (usage history information).

[0112] When at least one type of design data is used by a first user (purchasing user / setting user) and a second user (shared user), the control unit 11 of the management server 1 highlights and presents to each of the first and second users, based on the print history information (usage history information), design data included in the design set other than the selected design data.

[0113] (Highlighting processing) In Modification 1, instead of the processes of steps S21 and S22 of the design usage availability determination process (see FIG. 11), a highlighting process shown in FIG. 16 is performed. The highlighting process is a process preceding the user operating the user terminal 3 to select design data to be printed.

[0114] The processing of steps S61 to S63 is the same as the processing of steps S41 to S43 of the print history display processing (see FIG. 12), and therefore a description thereof will be omitted. However, since this processing targets a design set including multiple design data, in step S62, information on design sets available to the user operating the user terminal 3 is acquired.

[0115] After step S63, the control unit 11 of the management server 1 extracts design data that has not been selected by other users from the design data included in the design set available to the user, based on the print history information of users in the same sharing group (step S64). Specifically, the control unit 11 identifies design data that has been used by users other than the user of the user terminal 3 (user ID acquired in step S61) from the print history information of users in the same sharing group, and references the design set table T2 to extract design data that has not yet been used by users other than the user of the user terminal 3 from the design data included in the design set related to this sharing group.

[0116] Next, the control unit 11 of the management server 1 highlights and displays the extracted design data that has not been selected by other users on the display unit 34 of the user terminal 3 (step S65). Specifically, the control unit 11 generates data for a design list screen including content that presents the design data that has not been selected by other users in a manner that allows them to be distinguished from other design data, and transmits the data to the user terminal 3 via the communication unit 13. The display unit 34 of the user terminal 3 displays a design list screen including a highlighted display.

[0117] 17 shows an example of a design list screen 346 including highlighting displayed on the display unit 34 of the user terminal 3. The design list screen 346 includes a design display area 63, a highlight mark 64, and a message 65. The design display area 63 displays the design data names of the design data included in the available design set and the user names of the users who have used the design data. For example, if three people share a design set of pine, bamboo, and plum, and the other two (User A and User B) are using the pine design data and the bamboo design data, respectively, the remaining user will be presented with the plum design data highlighted.

[0118] The highlighting mark 64 is a mark that indicates the design data to be highlighted (plum design data in FIG. 17) so as to highlight it. Message 65 is a message indicating that the design data to be highlighted is not being used by other users.

[0119] The subsequent processing is the same as the processing from step S23 onwards in the design usability determination processing (see FIG. 11). However, since the processing from step S24 to step S27 is unnecessary, it is possible to move from step S23 to step S28.

[0120] According to Modification 1, by storing print history information (usage history information) for each user, including the purchasing user and the shared users, it is possible to highlight and present design data other than the selected design data included in the design set to the target user, thereby encouraging each of the multiple users to use different design data from the shared design set.

[0121] [Variation 2] Next, a description will be given of Modification 2. In Modification 2, the description of the same configurations and processes as those in the above embodiment will be omitted, and only the configurations and processes that are characteristic of Modification 2 will be described. In the second modification, when design data or a design set is purchased, designs that match the preferences of the purchasing user or the sharing destination user are presented as recommendations.

[0122] In the design data table T1 (see FIG. 3(a)) in the design database 121 stored in the storage unit 12 of the management server 1, in addition to the design data ID, design data name, and maximum number of sharing destinations, genre information of the design data is stored in association with each other. The genre information is information indicating a plurality of classification categories for the design data, and is classified from the viewpoint of impression (natural, elegant, cute, cool, etc.), color, etc. In addition, the design set table T2 (see Figure 3(b)) in the design database 121 stored in the memory unit 12 of the management server 1 stores, for each design data included in the design set, the design set ID, design set name, design data ID, maximum number of sharing destinations, as well as genre information of the design data, all associated with each other.

[0123] The print history information (usage history information) also includes genre information for the design data used by each user. That is, in print history table T4 (see FIG. 4(b)) in user database 122 stored in storage unit 12 of management server 1, in addition to the user ID, user name, print date and time, and design data ID, genre information for the design data is stored in association with each print history.

[0124] In Modification 2, the design purchase process (see FIG. 6) is performed after the second user (shared user) is set in the shared destination setting process (see FIG. 8). In this case, steps S12 to S14 are omitted in the shared destination setting process, and the shared destination is set in steps S15 and S16 without any design data or design set being selected.

[0125] Thereafter, a purchasing process (design purchasing process) for a design set including at least one type of design data is performed based on the operation of the first user (setting user). In the design purchasing process, the control unit 11 of the management server 1 recommends design sets according to the genre information of the design data used by the first user (setting user) or the second user (shared user) on a selection screen for purchasing the design set based on the print history information (usage history information).

[0126] Specifically, in step S2 of the design purchasing process, when a list of design data and design sets is displayed on the display unit 34 of the user terminal 3, the control unit 11 of the management server 1 refers to the print history table T4 to acquire print history information of the user currently operating the user terminal 3 (the setting user) and the shared user. The control unit 11 estimates the design data preferences of the setting user and the shared user (or, if there are multiple shared users, the multiple shared users) based on the genre information included in the print history information of the setting user and the shared user. If there is matching genre information between the setting user and the shared user, the control unit 11 extracts design data or design sets corresponding to the genre information and displays the extracted design data or design sets as recommendations on the display unit 34 of the user terminal 3. The control unit 11 of the management server 1 may also extract design data or design sets corresponding to genre information included in the print history information of either the setting user or the shared user and recommend the extracted design data or design sets.

[0127] Next, the control unit 11 of the management server 1 performs the same processes as steps S3 to S5 of the design purchasing process, and also performs the same process as step S17 of the sharing destination setting process.

[0128] According to Variation 2, recommendations can be presented on the design data or design set purchase (selection) screen based on the print history information of the user or the shared user. Also, the degree of match between the preferences of the setting user and the shared user may be displayed based on genre information of design data used in the past by the setting user and the shared user.

[0129] [Variation 3] Next, a description will be given of Modification 3. In Modification 3, the description of the same configurations and processes as those in the above embodiment will be omitted, and only the configurations and processes that are characteristic of Modification 3 will be described. In the third modification, when design data or a design set is purchased, designs are recommended according to the number of sharing users.

[0130] In Modification 3, as in Modification 2, the design purchase process (see FIG. 6) is performed after the second user (shared user) is set in the shared destination setting process (see FIG. 8). That is, in the shared destination setting process, steps S12 to S14 are omitted, and in steps S15 and S16, the shared destination is set in a state where no design data or design set has been selected.

[0131] Thereafter, a design purchase process (design purchase process) for a design set including at least one type of design data is performed based on the operation of the first user (setting user). In the design purchase process, the control unit 11 of the management server 1 recommends design sets according to the number of second users (shared users) set in the sharing destination setting process.

[0132] Specifically, in step S2 of the design purchasing process, when a list of design data and design sets is displayed on the display unit 34 of the user terminal 3, the control unit 11 of the management server 1 extracts, from the various design data registered in the design data table T1 and the various design sets registered in the design set table T2, those whose "maximum number of sharers" is equal to the number of sharer users. Then, the control unit 11 generates data for a design purchase screen including a list of design data and design sets whose "maximum number of sharers" is equal to the number of sharer users, and transmits the data for the design purchase screen to the user terminal 3 via the communication unit 13. A list of design data and design sets whose "maximum number of sharing destinations" is equal to the number of sharing destination users is displayed as a design purchase screen on the display unit 34 of the user terminal 3. For example, if the number of sharing destination users is "2", a design set for three people (a design set including three types of design data) including the set user is recommended.

[0133] Next, the control unit 11 of the management server 1 performs the same processes as steps S3 to S5 of the design purchasing process, and also performs the same process as step S17 of the sharing destination setting process.

[0134] According to variant example 3, the management server 1 displays design data or design sets according to the number of shared users set as purchase candidates and allows the set user to select from them, thereby preventing the complexity of design selection when the number of shared users increases.

[0135] In the third modification, design sets are recommended according to the number of second users (shared users), but only design sets corresponding to the number of second users may be available for purchase. That is, after a second user is set, when a purchase process for a design set including at least one type of design data is performed based on the operation of the first user (setting user), the control unit 11 of the management server 1 makes only design sets corresponding to the number of second users available for purchase. For example, the control unit 11 displays only design sets corresponding to the number of second users as purchase candidates on the display unit 34 of the user terminal 3 operated by the first user, and allows the first user to select from among them. This method, as with the third modification, can prevent the complexity of design selection when the number of shared users increases.

[0136] [Variation 4] Next, a description will be given of Modification 4. In Modification 4, the description of the same configurations and processes as those in the above embodiment will be omitted, and only the configurations and processes that are characteristic of Modification 4 will be described. In the explanation so far, the design set purchased by the first user (purchasing user) is used free of charge by the second user (shared user), and the design set is given to the shared user by the purchasing user. However, since it would be a large burden if one person paid for the design set every time, it would be convenient if multiple people could share the purchase cost and have other users pay the fee. In Variation 4, the design set is provided to the second user for a fee. In other words, the second user also pays the fee when using the design set.

[0137] Based on the usage information, the control unit 11 of the management server 1 controls the management server 1 to make at least one type of design data included in the design set available to at least a second user. The control unit 11 allows the second user to use at least one type of design data included in the design set for a fee. For example, the fee can be split between the first and second users, allowing the second user to also pay for the use of the design set.

[0138] Specifically, after one user purchases a design set, other users designated as sharing recipients can later share in the purchase cost. (1) First, one person (user A) pays the full amount of the design set fee. The control unit 11 of the management server 1 causes the payment server 4 to perform payment processing for user A.

[0139] (2) Next, the person designated to share the design set (User B) pays their share. If the maximum number of sharers is "5," the cost is divided among six people, including the designated user, with User B paying one-sixth of the total amount. The control unit 11 of the management server 1 causes the payment server 4 to perform payment processing for User B.

[0140] (3) Next, the amount paid by user B is refunded to user A. The control unit 11 of the management server 1 causes the payment server 4 to perform the refund process for user A. Note that the refund to user A is not limited to cash, and may be made in the form of points equivalent to cash or the like.

[0141] (4) Furthermore, if user C is a sharing party, he / she will be required to pay the share amount in the same manner as user B. In addition, the amount paid by user C will be refunded to user A. The control unit 11 of the management server 1 causes the payment server 4 to perform payment processing for user C and to perform refund processing for user A.

[0142] (5) If you set up the maximum number of sharing parties (5 people) and each person pays their share, the result will be similar to splitting the bill.

[0143] According to the fourth modification, the sharing destination users are allowed to use the design data or design set for a fee, so that the setting user can avoid bearing the full cost alone.

[0144] The designated sharing party (e.g., User B) may be required to pay a share to use the design set. Alternatively, the designated sharing party may be allowed to use the design set without paying a share, and may voluntarily pay a share if they like it. Furthermore, it is not necessary for all of the setting user and shared users to bear the cost of purchasing the design set equally, and the amount to be paid by each user may be weighted.

[0145] [Variation 5] Next, a description will be given of Modification 5. In Modification 5, the description of the same configurations and processes as those in the above embodiment will be omitted, and only the configurations and processes that are characteristic of Modification 5 will be described. In the fifth modification, restrictions on use, such as the number of times printing can be performed or the expiration date, are imposed on the design data or design set for which a sharing destination has been set.

[0146] For example, it is possible to set usage restrictions such as an upper limit on the number of prints, a usage period, etc. in the user usage permission table T3 shown in Fig. 4(a). These usage restrictions may be determined according to the price of the design data or design set, or may be specified by the setting user (purchasing user).

[0147] In addition to the determinations made in steps S25 and S26 of the design usage availability determination process (see FIG. 11), the conditions for determining whether the design data is available in step S27 include that the usage period is within the expiration date and that the number of times the design data has been printed is less than the upper limit.

[0148] Specifically, the control unit 11 of the management server 1 compares the usage period set for the design data to be printed or the design set containing the design data with the current date and time obtained from the timing unit 14, and determines whether the usage period is within the period. The control unit 11 also refers to the print history table T4 to obtain the number of times the target user has used the design data to be printed or a design set including that design data, and determines whether the number of times the target user has printed is less than the upper limit set for the design data to be printed or the design set including that design data.

[0149] If the current date and time is within the usage period and the number of times printing has been performed up to now is less than the upper limit, the control unit 11 determines that the design data is usable. On the other hand, if the current date and time is past the expiration date, or if the number of times the design data has been printed has reached the upper limit, the control unit 11 determines that the design data cannot be used.

[0150] According to the fifth modification, it is possible to set an upper limit on the number of times that the design data or design set to be shared can be printed and a usage period can be set. In the fifth variation, users designated as sharing destinations can try out the design data, but if they want to continue using it beyond the expiration date or the limit on the number of prints, they must purchase it.

[0151] Although the embodiments and modifications of the present invention have been described above, it goes without saying that the present invention is not limited to such embodiments and modifications, and various modifications are possible without departing from the spirit of the present invention. For example, characteristic processes of the embodiment and each modification may be combined.

[0152] Additionally, the shared user set for a design set may be changed later. In this case, users who are no longer shared will be unable to use the design. However, in the case of a specification where the shared user is responsible for paying for the purchase of a design set, as in Variation 4, it is preferable that the shared user cannot be changed later.

[0153] In addition, if a design set containing multiple types of design data is purchased and not all types of design data are used within the same sharing group (the setting user and the shared user) (for example, if only three types of design data are used out of a design set containing four types of design data), a refund may be made in proportion to the amount of unused design data.

[0154] Although the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and its equivalents. The inventions described in the claims originally attached to this application are as follows. The claim numbers described in the appendix are the same as those of the claims originally attached to this application. [Note] <Claim 1> The computer generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; Based on the usage information, control is performed to make the at least one type of design data included in the design set available to at least the second user. A data utilization method characterized by: <Claim 2> the use information includes at least information indicating whether the first user and the second user are permitted to use the at least one type of design data; 2. The data utilization method according to claim 1, wherein: <Claim 3> The maximum number of second users that can be set as users is determined for each design set. 3. The data utilization method according to claim 1 or 2. <Claim 4> The computer allowing the second user to use the at least one type of design data free of charge; 4. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system. <Claim 5> The computer allowing the second user to use the at least one type of design data for a fee; 4. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system. <Claim 6> The computer storing usage history information based on the design data used by each of the first user and the second user in a storage unit; 6. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system. <Claim 7> The computer When the at least one type of design data is used by the first user and the second user, design data other than the selected design data among the design data included in the design set are highlighted and presented to each of the first user and the second user based on the usage history information. 7. The data utilization method according to claim 6. <Claim 8> The usage history information includes genre information of the design data used by each user, The computer After the second user is set, when a purchase process for a design set including at least one type of design data is performed based on an operation by the first user, Based on the usage history information, a design set corresponding to the genre information of the design data used by each user is recommended on a selection screen for purchasing the design set. 7. The data utilization method according to claim 6. <Claim 9> The computer After the second user is set, when a purchase process for a design set including at least one type of design data is performed based on an operation by the first user, Recommending a design set according to the number of second users; 9. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system. <Claim 10> The computer After the second user is set, when a purchase process for a design set including at least one type of design data is performed based on an operation by the first user, Only design sets corresponding to the number of second users can be purchased. 9. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system. <Claim 11> a means for generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; a means for controlling the use of the at least one type of design data included in the design set to at least the second user based on the use information; Equipped with A data management device characterized by: <Claim 12> Computer, a means for generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; a means for controlling the use of the at least one type of design data included in the design set to at least the second user based on the usage information; A program to function as a [Explanation of symbols]

[0155] 1 Management Server 10 Control device 11 Control section 12 Storage section 121 Design Database T1 Design Data Table T2 Design Set Table 122 User Database T3 User Availability Table T4 Print History Table T5 Print Schedule Table 13 Communications Department 14 Timing section 2 Printing device 20 Control device 21 Control section 22 Memory section 26 Printing Department 3. User terminal 30 Control device 31 Control Unit 32 Storage section 33 Operation section 34 Display section 35 Communications Department 4. Payment Server 100 Printing Systems N Network

Claims

1. The computer generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; and controlling the at least one type of design data included in the design set to be made available to at least the second user based on the usage information. A data utilization method characterized by:

2. the use information includes at least information indicating whether the first user and the second user are permitted to use the at least one type of design data; 2. The data utilization method according to claim 1.

3. The maximum number of second users that can be set as users is determined for each design set.

3. The data utilization method according to claim 1 or 2.

4. The computer allowing the second user to use the at least one type of design data free of charge; 4. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system.

5. The computer allowing the second user to use the at least one type of design data for a fee; 4. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system.

6. The computer storing usage history information based on the design data used by each of the first user and the second user in a storage unit; 6. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system.

7. The computer When the at least one type of design data is used by the first user and the second user, design data other than the selected design data among the design data included in the design set is highlighted and presented to each of the first user and the second user based on the usage history information.

7. The data utilization method according to claim 6.

8. The usage history information includes genre information of the design data used by each user, The computer After the second user is set, when a purchase process for a design set including at least one type of design data is performed based on an operation by the first user, Based on the usage history information, a design set corresponding to genre information of the design data used by each user is recommended on a selection screen for purchasing the design set.

7. The data utilization method according to claim 6.

9. The computer After the second user is set, when a purchase process for a design set including at least one type of design data is performed based on an operation by the first user, recommending a design set according to the number of second users; 9. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system.

10. The computer After the second user is set, when a purchase process for a design set including at least one type of design data is performed based on an operation by the first user, Only design sets corresponding to the number of second users can be purchased.

9. The data utilization method according to claim 1, wherein the data utilization method is a data utilization method for a data processing system.

11. a means for generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; a control means for controlling the use of the at least one type of design data included in the design set to at least the second user based on the use information; Equipped with A data management device characterized by:

12. Computer, a means for generating usage information that associates the design set with the first user and the second user by setting at least one second user who will be a user of the design set, which includes at least one type of design data and is purchased by the first user, based on an operation by the first user; a means for controlling, based on the usage information, making the at least one type of design data included in the design set available to at least the second user; A program to function as a

Citation Information

Patent Citations

  • Connection system for multi-processor

    JP1989081066A