Management system, management method, and management program

Abstract

A management system according to the present disclosure is provided with a processing unit that records recipe data including cooking recording data in which a cooking process is recorded and, with respect to the recorded recipe data, registers and manages rights information relating to rights to use the recipe data.

Description

Management system, management method and management program

[0001] FIELD Embodiments of the present invention relate to a management system, a management method, and a management program.

[0002] BACKGROUND ART Conventionally, a cooking assistance system has been known that records the cooking process of a top chef and enables even a cook with no cooking experience to reproduce the dish by digitizing the cooking process.

[0003] This cooking assistance system defines a target state using target parameters based on sensor data that can be measured during cooking, and allows for the reproduction of cooking using recipe data that includes this data. This recipe data is stored in a central server or on a recording medium in the cooking assistance system. When performing a reproduction cooking, the reproducing cook selects the recipe data for the dish to be reproduced from the recipe data stored in the central server or cooking assistance system.

[0004] The cooking assistance system uses images and audio to navigate the user and provide information on the cooking process based on the selected recipe data. This allows the recreating cook to receive instructions on adding ingredients and stirring. The cooking assistance system also automatically adjusts the heat according to the cooking process based on the selected recipe data, allowing even cooks with no cooking experience to create highly accurate dishes.

[0005] International Publication No. 2023 / 182197

[0006] However, the above-mentioned conventional technologies have the problem that it is difficult to protect recipe data as a right. For example, recipe data is simply managed on the cooking assistance system or a central server, and anyone who uses the cooking assistance system can easily use it. Therefore, it is difficult for the creator of recipe data to utilize the rights of the recipe data, such as granting the right to use the recipe data (hereinafter also referred to as the playback right) to anyone who pays a fee, thereby allowing them to reproduce cooking using the recipe data.

[0007] Therefore, the present disclosure proposes a management system, a management method, and a management program that can manage the right to use recipe data.

[0008] It should be noted that the above problem or object is merely one of multiple problems or objects that can be solved or achieved by multiple embodiments disclosed in this specification.

[0009] The management system of the present disclosure includes a processing unit that records recipe data including cooking record data that records cooking steps, and registers and manages rights information regarding the rights to use the recorded recipe data.

[0010] FIG. 1 is an explanatory diagram outlining management of playback rights using a management system according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating a specific configuration example of a cooking assistance system. FIG. 3 is a block diagram illustrating an example configuration of a management system according to an embodiment of the present disclosure. FIG. 4 is a block diagram illustrating an example configuration of a cooking assistance system. FIG. 5 is a block diagram illustrating an example configuration of a center server. FIG. 6 is a block diagram illustrating an example configuration of a blockchain server. FIG. 7 is a block diagram illustrating an example configuration of a portable terminal. FIG. 8 is a flowchart illustrating an example operation of a management system according to an embodiment of the present disclosure. FIG. 9 is a flowchart illustrating an example operation of a management system according to an embodiment of the present disclosure. FIG. 10 is a flowchart illustrating an example operation of a management system according to an embodiment of the present disclosure. FIG. 11 is a hardware configuration diagram illustrating an example of a computer.

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0012] Furthermore, in this specification and drawings, similar components of the embodiments may be distinguished by adding at least one different alphabet and / or number after the same reference numeral. However, when there is no need to particularly distinguish between similar components, the same reference numeral will be used. For example, multiple components having substantially the same functional configuration may be distinguished as necessary, such as a cooking assistance system (recording side) 10R and a cooking assistance system (playback side) 10P (see FIG. 1). For example, when there is no need to particularly distinguish between the cooking assistance system (recording side) 10R and the cooking assistance system (playback side) 10P, they will simply be referred to as the cooking assistance system 10 (see FIGS. 2, 3, and 4).

[0013] One or more embodiments (including examples, modifications, and application examples) described below can be implemented independently. However, at least a portion of the embodiments described below may be implemented in appropriate combination with at least a portion of another embodiment. These embodiments may include novel features that are different from each other. Therefore, these embodiments may contribute to solving different purposes or problems and may produce different effects from each other.

[0014] (Outline of Management of Playback Rights) First, an outline of management of the right to use recipe data (playback rights) will be described. Fig. 1 is an explanatory diagram illustrating an outline of management of playback rights using a management system according to an embodiment of the present disclosure.

[0015] As shown in Figure 1, in the management system 1, the creator who records cooking using the cooking assistance system 10 is referred to as Creator H1. In Figure 1, Creator H1 is an individual, but a group or corporation can also be registered as the creator. The cooking record data in which Creator H1 records the cooking steps using the cooking assistance system (recording side) 10R is stored as recipe data in the center server 20.

[0016] Specifically, Creator H1 creates a recipe for a dish and performs record cooking using the cooking assistance system (recording side) 10R. As shown in the illustrated example, Creator H1 performs record cooking using the cooking assistance system (recording side) 10R as indicated by the arrow, thereby generating recipe data. The recipe data includes cooking record data that records the cooking steps performed by Creator H1. The recipe data including the cooking record data is transmitted from the cooking assistance system (recording side) 10R to the center server 20 as indicated by the arrow, and is managed by the center server 20.

[0017] Recipe data for various dishes is managed by the center server 20. As will be described later, cooking record data included in the recipe data is data including time-series data of sensor data measured at each step of the recorded cooking performed by Creator H1 according to the recipe. Note that a dish refers to a finished product after cooking. Cooking refers to the process of cooking a dish or the act (task) of cooking a dish.

[0018] Based on the recipe data stored in the center server 20, the reproducing chef H2 can reproduce the dish provided by Creator H1 using a cooking support system (reproducing side) 10P installed in a restaurant, cloud kitchen, apartment lounge, etc.

[0019] Specifically, the recipe data managed by the center server 20 is transmitted to the cooking assistance system (playback side) 10P, as indicated by the arrow, and is used to recreate the dish. In the cooking assistance system (playback side) 10P, each cooking step is performed according to the recipe data, and the dish created by Creator H1 is recreated. Cooking in the cooking assistance system (playback side) 10P is performed so as to recreate each step of the recorded cooking based on the cooking record data included in the recipe data.

[0020] In this way, cooking is recorded on the cooking assistance system (recording side) 10R side. Cooking performed on the cooking assistance system (playback side) 10P side is reproduction cooking, which reproduces the dish. The cooking assistance system (recording side) 10R is a device with a recording cooking function, and the cooking assistance system (playback side) 10P is a device with a reproduction cooking function. When there is no need to distinguish between the cooking assistance system (recording side) 10R and the cooking assistance system (playback side) 10P, they are collectively referred to as the cooking assistance system 10.

[0021] Here, in the management system 1, recipe data including cooking record data that records the cooking steps is converted into an NFT (Non-Fungible Token) by the blockchain server 30. Specifically, the management system 1 issues a proof of creation to Creator H1 by giving the recipe data a distinguishable identifier and converting it into an NFT. Then, the management system 1 registers (sets) and manages the transaction history of the NFT-converted recipe data, i.e., the rights information related to the playback rights, in the blockchain of the blockchain server 30.

[0022] In this way, when playback rights are set for NFT-converted recipe data, the eater H3 presents the certification information required to grant the playback rights (such as a food and drink record proving eating at a designated restaurant or location information such as a GPS (Global Positioning System)) via a mobile terminal 40 or the like. The blockchain server 30 compares the certification information presented by the eater H3 with the playback rights set for the NFT-converted recipe data, and based on the comparison results, notifies the center server 20 whether or not the recipe data is being used. Based on the notification from the blockchain server 30, the center server 20 outputs the stored recipe data to the cooking assistance system (playback side) 10P.

[0023] This allows the cooking support system (playback side) 10P to reproduce cooking using the recipe data of Creator H1. Furthermore, by determining the use of recipe data based on location information, the management system 1 can, for example, enable eater H3 of a reproduced dish to obtain a reproduction right by eating the reproduced dish provided by the reproduction cook H2. Alternatively, eater H3 can obtain a reproduction right by experiencing the corresponding dish at a restaurant run by Creator H1 without using the cooking support system (playback side) 10P.

[0024] (Cooking support system) For the cooking support system 10, it is possible to use a system similar to the systems described in Japanese Patent Application Nos. 2021-168046 and 2022-048036 filed by the present applicant. FIG. 2 is a diagram showing a specific configuration example of the cooking support system 10.

[0025] The cooking assistance system 10 is a so-called smart cooking appliance. The cooking assistance system 10 assists in cooking using cooking utensils such as pots and frying pans. Note that cooking utensils are appliances used by cooks, such as pots, frying pans, and spatulas. In addition to cooking utensils, cooking appliances also include electrically driven appliances such as induction cookers.

[0026] The cooking assistance system 10 is configured by connecting an LCD tablet 121, a speaker 122, a camera 123, a microphone 124, an environmental measuring device 125, and a router 126 to an induction cooktop 111. Each device is connected to the induction cooktop 111 by wired communication or by wireless communication such as a wireless LAN (Local Area Network).

[0027] The IH stove 111 is an electromagnetic cooker that heats cooking equipment 112 such as a pot or frying pan. In the following description, the cooking equipment 112 will be mainly assumed to be a pot.

[0028] 2, the induction cooker 111 incorporates a processor 131, a temperature sensor 132, a pressure sensor 133, an acoustic sensor 134, and a storage 135. The processor 131 and the storage 135 may be mounted on an external computer connected to the induction cooker 111.

[0029] The processor 131 is a computing unit that controls the heating of the cooking appliances 112. For example, the processor 131 corresponds to the processor unit 101 in Fig. 4. The processor 131 controls each device that constitutes the cooking assistance system 10 and communicates with external devices, the server 127, etc. Communication with the server 127 is performed via the router 126.

[0030] The processor 131 also detects operations input by the chef using input UI (user interface) devices such as the liquid crystal tablet 121 and the microphone 124. The processor 131 also controls the photography of the camera 123.

[0031] Temperature sensor 132 measures the temperature of the pot or the temperature of the food being cooked in the pot. In this case, the pot serves as the heating medium, and the food in the pot serves as both the food being cooked and the heated object. Temperature sensor 132 may be, for example, a radiation thermometer (infrared sensor) that is highly responsive and capable of non-contact measurement. Temperature sensor 132 may also be configured to measure both the temperature of the pot and the temperature of the food being cooked.

[0032] The pressure sensor 133 measures the weight of the food to be cooked in the pot. For example, a force gauge is used as the pressure sensor 133. The pressure sensor 133 is provided, for example, below the top plate of the induction cooker 111.

[0033] The acoustic sensor 134 detects various sounds that occur during cooking, such as sounds emitted by the food being cooked and sounds emitted by the pot.

[0034] 5 is configured with temperature sensor 132, pressure sensor 133, and acoustic sensor 134. As a variation of the physical configuration, sensor devices such as temperature sensor 132 and pressure sensor 133 may be built into the pot, which is the heating medium.

[0035] The storage 135 records data used for various processes by the processor 131. The storage 135 corresponds to the memory unit 103 in FIG.

[0036] The GPS 136 uses the GPS to acquire location information of the cooking assistance system 10. The GPS 136 corresponds to the positioning unit 104 in FIG.

[0037] The liquid crystal tablet 121 displays various screens under the control of the processor 131. For example, the liquid crystal tablet 121 is provided near the induction cooker 111. Various information is presented to the cooks (Creator H1, reproduction cook H2) using the liquid crystal tablet 121. Instead of the liquid crystal tablet 121, a UI device such as a display and a mouse may be used.

[0038] The speaker 122 outputs audio guidance required for navigation. A liquid crystal tablet with a built-in speaker may be used instead of the speaker 122. The liquid crystal tablet 121 and the speaker 122 constitute the operation and display unit 106 in FIG. 4 .

[0039] The camera 123 captures an image of the food being cooked in the pot. The camera 123 is installed, for example, above the induction cooktop 111 with its angle of view facing the pot. The image captured by the camera 123 is transmitted in real time to the processor 131. For example, a normal visible light camera is used as the camera 123. In addition to a visible light camera, a thermography camera or a hyperspectral camera can also be installed as the camera 123.

[0040] The microphone 124 detects the voice of the cook. Various inputs by the cook are made using voice. The cook can operate the cooking assistance system 10 by speaking into the microphone 124. The cooking assistance system 10 is also equipped with a voice recognition function. The microphone 124 is also a device that constitutes the sensor unit 105 in FIG. 4.

[0041] The environment measuring instrument 125 measures the cooking environment. The environment measuring instrument 125 is a sensor device equipped with a temperature sensor 141, a humidity sensor 142, an air pressure sensor 143, and an acoustic sensor 144. The environment measuring instrument 125 is also a device that constitutes the sensor unit 105 in FIG. 4 .

[0042] The router 126 communicates with servers 127 on the network, including the center server 20. The router 126 corresponds to the communication unit 102 in FIG.

[0043] (System Configuration) Fig. 3 is a block diagram showing an example configuration of a management system 1 according to an embodiment of the present disclosure. As shown in Fig. 3, a cooking assistance system 10, a center server 20, a blockchain server 30, and a mobile terminal 40 are connected to each other so as to be able to communicate with each other via a network NW such as the Internet.

[0044] (Functional Configuration of Cooking Assistance System) FIG. 4 is a block diagram showing an example configuration of a cooking assistance system.

[0045] As shown in FIG. 4, the cooking assistance system 10 includes a processor unit 101, a communication unit 102, a storage unit 103, a positioning unit 104, a sensor unit 105, and an operation and display unit 106.

[0046] The processor unit 101 is a so-called computer system, and is configured by, for example, a general-purpose computing device such as a central processing unit (CPU), a graphics processing unit (GPU), or a digital signal processor (DSP), or a dedicated computing device specialized for AI-related processing.

[0047] By executing a predetermined program, the processor unit 101 realizes a processor unit 101-1, a processor unit 101-2, a processor unit 101-3, a processor unit 101-4, a processor unit 101-5, and a processor unit 101-6.

[0048] The processor unit 101-1 acquires the memory unit 103-1 selected by the chef who will perform the reproduction cooking from the memory unit 103 or from the center server 20.

[0049] The processor unit 101-2 measures the cooking environment during the recorded cooking using various devices of the positioning unit 104. The cooking environment is also measured during the reproduced cooking.

[0050] The processor unit 101-3 corrects the storage unit 103-1 used for the reproduction cooking. The correction of the storage unit 103-1 is performed before the start of the reproduction cooking, for example, based on sensor data of the cooking environment measured using various devices of the positioning unit 104.

[0051] During recording cooking, the processor unit 101-4 provides the center server 20 with cooking record data that records the cooking process using the processor unit 101-1.

[0052] When the processor unit 101-5 obtains the playback right and performs a re-creation cooking, it presents the contents of the cooking record data to the cook based on the corrected storage unit 103-1. For example, information such as the temperature and weight of the ingredients and pot at each stage of the cooking process, and the sounds made during cooking, is presented. In this way, the processor unit 101-5 provides cooking navigation using images, audio, and the like, thereby supporting the work of re-creating the cooking process so that even people who have not received specialized training at a cooking school or the like can accurately recreate the dish.

[0053] The processor unit 101-6 updates information related to the reproduction recipe, such as the number of times the reproduction recipe has been performed based on the memory unit 103-1, the number of memory units 103-1 used for the reproduction recipe, etc. Specifically, when the processor unit 101-6 obtains the playback right and performs the reproduction recipe, it requests the blockchain server 30 to update the management information of the reproduction right.

[0054] 4 is a device that has a cooking recording function in the cooking assistance system (recording side) 10R and a cooking reproduction function in the cooking assistance system (playback side) 10P. The recording cooking function is realized by, for example, processor units 101-2 and 101-4. The reproduction cooking function is realized by, for example, processor units 101-1, 101-2, 101-3, 101-5, and 101-6.

[0055] The recording cooking function of the cooking assistance system (recording side) 10R and the reproducing cooking function of the cooking assistance system (playback side) 10P may be realized by devices in different housings.

[0056] The communication unit 102 is configured by an interface for a network such as the Internet, and communicates with external devices such as the center server 20 via the network NW.

[0057] The storage unit 103 is configured by a recording device such as a memory, storage, etc. As shown in Fig. 4, the storage unit 103 stores a storage unit 103-1, a storage unit 103-2, a storage unit 103-3, and a storage unit 103-4.

[0058] The storage unit 103-1 stores cooking record data that records the cooking steps. The storage unit 103-2 is used when changing the cooking time, etc., during a reproduction cooking depending on the cooking environment. The number of recipe reproductions in the storage unit 103-3 is updated by the processor unit 101-6 each time a reproduction cooking is performed. The storage unit 103-4 stores information about the person who reproduced the recipe (Creator H1, reproduction cook H2). Specifically, the storage unit 103-4 stores attributes of the person who reproduced the recipe (name, gender, age, etc.), a facial image of the reproducer, information about the store run by the reproducer, etc.

[0059] The positioning unit 104 measures the position of the cooking assistance system 10 based on the GPS 136 and acquires position information.

[0060] The sensor unit 105 is composed of various sensor devices used to measure the cooking environment and the state of ingredients to be cooked.

[0061] The sensor unit 105 is composed of an operation unit used by a user such as a chef to operate the system, and a presentation unit such as a display used to present information to the chef.

[0062] (Functional Configuration of Center Server) FIG. 5 is a block diagram showing an example of the configuration of the center server 20. As shown in FIG.

[0063] As shown in FIG. 5, the center server 20 includes a processor unit 201 , a communication unit 202 , a storage unit 203 , and an operation and display unit 204 .

[0064] The processor unit 201 is a so-called computer system. The processor unit 201 is configured, for example, by a general-purpose computing device such as a CPU / GPU / DSP, or a dedicated computing device specialized for AI-related processing. By executing a predetermined program, the processor unit 201 realizes processor units 201-1, 201-2, and 201-3. The processor unit 201 functions as an information processing unit that manages the storage unit 203-1.

[0065] The processor unit 201-1 is a processing unit that registers certification information for granting playback rights to the storage unit 203-1. Specifically, the processor unit 201-1 associates the certification information with the NFT-enabled processor unit 201-1 (details will be described later).

[0066] The processor unit 201-2 is a processing unit that requests the blockchain server 30 to change the certification information, etc., for granting playback rights to the processor unit 201-1, based on an instruction from the portable terminal 40, etc. Specifically, when a change to the certification information associated with the NFT-enabled processor unit 201-1 is made by the portable terminal 40, etc., the processor unit 201-2 accepts the creator certificate for the processor unit 201-1 and verifies the legitimacy of the instruction. If the instruction is legitimate, the processor unit 201-2 requests the blockchain server 30 to change the certification information, etc., associated with the NFT-enabled processor unit 201-1, based on an instruction from the portable terminal 40, etc.

[0067] The processor unit 201-3 is a processing unit that queries the creator of the processor unit 201-1. Specifically, the processor unit 201-3 queries the blockchain server 30 for and acquires creator information associated with the NFT-enabled processor unit 201-1.

[0068] The communication unit 202 is configured by an interface for a network such as the Internet. The communication unit 202 communicates with external devices such as the cooking assistance system 10, the blockchain server 30, and the mobile terminal 40 via the network NW.

[0069] The storage unit 203 is configured by a recording device such as a memory, storage, etc. As shown in Fig. 5, the storage unit 203 records information in the storage units 203-1, 203-2, 203-3, 203-4, 203-5, and 203-6.

[0070] Regarding the main information, the storage units 203-1 and 203-2 store the same data as the storage units 103-1 and 103-2.

[0071] Storage unit 203-3 stores data indicating cooking condition standards. Storage unit 203-4 stores data indicating the number of times each menu item in storage unit 203-1 has been played. Storage unit 203-5 stores video information indicating the cooking process recorded using camera 123 when recording cooking for storage unit 203-1. Storage unit 203-6 stores certification information for granting playback rights to storage unit 203-1.

[0072] The operation and display unit 204 is composed of an operation unit used by the administrator of the center server 20 and a presentation unit such as a display used to present information to the administrator.

[0073] (Functional Configuration of Blockchain Server) FIG. 6 is a block diagram showing an example configuration of the blockchain server 30.

[0074] The blockchain server 30 shown in Figure 6 is a server that manages a database configured by a blockchain network. The blockchain database is realized by multiple servers managing various types of data such as recipe data in a distributed manner. Various types of information are transmitted and received between the blockchain server 30 and the center server 20 via the network NW.

[0075] As shown in FIG. 6 , the blockchain server 30 has a processor unit 301 , a communication unit 302 , a memory unit 303 , and an operation / display unit 304 .

[0076] The processor unit 301 is a so-called computer system. The processor unit 301 is configured, for example, by a general-purpose computing device such as a CPU / GPU / DSP, or a dedicated computing device specialized for AI-related processing. By executing a predetermined program, the processor unit 301 realizes processor unit 301-1, processor unit 301-2, processor unit 301-3, processor unit 301-4, and processor unit 301-5.

[0077] The processor unit 301-1 is a processing unit that generates an NFT for the memory unit 303-1 based on a notification (registration request) from the center server 20 for the memory unit 303-1 and assigns a distinguishable identifier (also called a token ID) to the memory unit 303-1.

[0078] That is, the processor unit 301-1 converts the storage unit 303-1, which has been requested to register in the blockchain, into an NFT. This identifier is uniquely assigned to the storage unit 303-1 obtained by record cooking, and can therefore be used as proof information to certify the creator of the storage unit 303-1.

[0079] The processor unit 301-2 issues a storage unit 303-3 related to the storage unit 303-1 based on the identifier obtained by NFTing the processor unit 301-1.

[0080] The processor unit 301-3 is a processing unit that grants playback rights to the NFT-enabled processor unit 301-1. Specifically, the processor unit 301-3 registers information about the playback rights of the NFT-enabled processor unit 301-1 in the blockchain.

[0081] The processor unit 301-4 is a processing unit that queries the certification information for granting the playback right, which is associated with the NFT-enabled processor unit 301-1. Specifically, the processor unit 301-4 acquires the certification information registered in the blockchain in association with the NFT-enabled processor unit 301-1.

[0082] The processor unit 301-5 is a processing unit that associates the processor unit 301-1 that has been converted into an NFT and registers and updates information relating to the playback right and certification information for granting the playback right.

[0083] The communication unit 302 is configured by an interface for a network such as the Internet. The communication unit 302 communicates with external devices such as the cooking assistance system 10, the center server 20, and the portable terminal 40 via the network NW.

[0084] The memory unit 303 is configured with a recording device such as a memory or storage. As shown in Fig. 6, the memory unit 303 records information of memory unit 303-1, memory unit 303-2, memory unit 303-3, memory unit 303-4, memory unit 303-5, memory unit 303-6, and memory unit 303-7 managed on the blockchain.

[0085] Regarding the main information, storage unit 303-1 contains the same data as storage units 103-1 and 203-1. Storage unit 303-2 contains information related to the creator (Creator H1) of storage unit 303-1 through recorded cooking. Specifically, storage unit 303-2 contains attributes and facial information of Creator H1 that were input and set by Creator H1 via the cooking assistance system (recording side) 10R, etc., during recorded cooking.

[0086] The storage unit 303-3 stores information that proves the creator of the processor unit 301-1, such as an identifier obtained by converting the processor unit 301-1 into an NFT through record cooking.

[0087] The storage unit 303-4 stores location information indicating the location of the store related to the processor unit 301-1. Specifically, the storage unit 303-4 stores location information obtained from the cooking assistance system (recording side) 10R when the processor unit 301-1 was created by recording cooking.

[0088] The storage unit 303-5 stores information indicating an event venue where the reproduction recipes of the processor unit 301-1 will be provided. Specifically, the storage unit 303-5 stores a QR code (registered trademark) indicating the event venue, location information of the event venue, and the like.

[0089] The storage unit 303-6 is a QR code assigned to the processor unit 301-1. Specifically, the storage unit 303-6 is a QR code indicating an identifier assigned to the processor unit 301-1.

[0090] The storage unit 303-7 stores management information related to the playback rights of the NFT processor unit 301-1. Specifically, the storage unit 303-7 stores information related to the playback rights of the NFT processor unit 301-1, such as user identification information indicating users who are permitted to use the NFT processor unit 301-1, the number of times the processor unit can be used, and the period during which the processor unit can be used. The storage unit 303-7 also stores certification information for granting the playback rights.

[0091] The operation / display unit 304 is composed of an operation unit used by the administrator of the blockchain server 30, and a presentation unit such as a display used to present information to the administrator.

[0092] (Functional Configuration of Portable Terminal) FIG. 7 is a block diagram showing an example of the configuration of the portable terminal 40. As shown in FIG.

[0093] As shown in FIG. 7, the portable terminal 40 includes a processor unit 401 , a communication unit 402 , a storage unit 403 , a positioning unit 404 , and an operation / display unit 405 .

[0094] The processor unit 401 is a so-called computer system. The processor unit 401 is configured, for example, by a general-purpose computing device such as a CPU / GPU / DSP, or a dedicated computing device specialized for AI-related processing. By executing a predetermined program, the processor unit 401 realizes processor unit 401-1, processor unit 401-2, processor unit 401-3, processor unit 401-4, and processor unit 401-5.

[0095] Processor unit 401-1 is a processing unit that registers storage unit 403-1, storage unit 403-2, and storage unit 403-3, which have been consumed by the user of portable terminal 40, in storage unit 403. Specifically, processor unit 401-1 registers identification information indicating the menu read from a receipt or the like when the menu is consumed as storage unit 403-1 in storage unit 403. Here, storage unit 403-1 contains not only the name of the menu, but also creator information indicating the creator of the menu, a creator certificate, a QR code assigned to the menu, and the like. Processor unit 401-1 also registers the date and time when storage unit 403-1 was registered as storage unit 403-2 in storage unit 403. When processor unit 401-1 registered storage unit 403-1, processor unit 401-1 also registers storage unit 403-3, which was acquired using GPS or the like, in storage unit 403.

[0096] Processor unit 401-2 is a processing unit that registers storage unit 403-4, which indicates the purchase history of the user of portable terminal 40, in storage unit 403. Specifically, processor unit 401-2 registers purchase details (store, purchase date and time, ingredients, quantity, price, etc.) read from receipts or the like when the user of portable terminal 40 makes a purchase, in storage unit 403 as storage unit 403-4.

[0097] The processor unit 401-3 is a processing unit that receives a notification of the playback right for the recipe data from the blockchain server 30. The processor unit 401-4 is a processing unit that transmits a request to the blockchain server 30 to use the playback right for the recipe data.

[0098] The processor unit 401-5 is a processing unit that reads the QR code. Specifically, the processor unit 401-5 reads the QR code attached to the menu.

[0099] The communication unit 402 is configured by an interface for a network such as the Internet. The communication unit 402 communicates with external devices such as the cooking assistance system 10, the center server 20, and the blockchain server 30 via the network NW.

[0100] The storage unit 403 is configured by a recording device such as a memory, storage, etc. As shown in Fig. 7, the storage unit 403 records information in the storage units 403-1, 403-2, 403-3, and 403-4.

[0101] The positioning unit 404 is a processing unit that measures the position of the portable terminal 40 using GPS etc. The positioning unit 404 records the position information 403-3 obtained by the positioning in the storage unit 403.

[0102] The operation and display unit 405 is made up of an operation unit used by the user of the portable terminal 40 and a presentation unit such as a display used to present information to both parties.

[0103] (Operation of Cooking Assistance System) Fig. 8 is a flowchart showing an example of operation of the management system 1 according to an embodiment of the present disclosure. Specifically, Fig. 8 shows an example of a process for creating recipe data for recorded cooking, converting the created recipe data into an NFT, and registering it in a blockchain.

[0104] The timing of registration on the blockchain does not necessarily have to be the timing shown in this flow. For example, the processes of S14 to S23 may be performed on stored recipe data at any timing.

[0105] 8, the cooking assistance system (recording side) 10R accepts input of basic information about a recipe through operation of the operation / display unit 106 (S10). The basic information accepted here includes the ingredients and quantities used in the recipe, as well as information about the creator of the recipe (attributes, store). Note that the ingredients used in the recipe may also include detailed information, such as product names, that is necessary when purchasing the ingredients.

[0106] Next, in the cooking support system (recording side) 10R, the processor unit 101-2 etc. is used to record the cooking performed by Creator H1 (S11). Next, in the cooking support system (recording side) 10R, the processor unit 101-4 creates recipe data describing the contents of the recorded cooking and notifies the center server 20.

[0107] The center server 20 stores the recipe data from the recorded cooking of the cooking assistance system (recording side) 10R in the storage unit 203 (S13). At this time, the center server 20 also acquires video information of the cooking taken by the camera 123 during the recorded cooking together with the recipe data, and stores this in the storage unit 203 (S17).

[0108] The recipe data stored in the center server 20 is notified by the processor unit 201-1 to the blockchain server 30. The blockchain server 30 protects the notified recipe data using blockchain technology that decentralizes and manages data transaction history as a ledger.

[0109] Specifically, the processor unit 301-1 of the blockchain server 30 receives notification of the recipe data from the center server 20 and starts managing the recipe data on the blockchain (S14).

[0110] Specifically, the processor unit 301-1 of the blockchain server 30 generates an NFT of the notified recipe data and assigns a distinguishable identifier to the recipe data (converts it to an NFT) (S15).

[0111] Next, the communication unit 302 of the blockchain server 30 issues a storage unit 303-3 for the recipe data based on the assigned identifier (S16).

[0112] Next, the processor unit 301-1 of the blockchain server 30 links the NFT-converted recipe data with video information taken during cooking of the recipe data (S18).

[0113] Next, the processor unit 201-1 of the center server 20 starts the process of registering certification information for granting the playback right to the recipe data converted into NFT (S19).

[0114] Specifically, when the processor unit 201-1 generates recipe data for recorded cooking, it links the GPS information (location information) acquired from the cooking assistance system (recording side) 10R to the NFT-converted recipe data as one piece of proof information for granting playback rights (S21). Note that the location information linked as one piece of proof information for granting playback rights is not limited to the GPS information acquired from the cooking assistance system (recording side) 10R, and may be, for example, location information arbitrarily set by the user.

[0115] Furthermore, the processor unit 201-1 links the QR code issued in correspondence with the NFT recipe data to the NFT recipe data as one piece of certification information for granting the playback right (S22).

[0116] The authentication information that the processor unit 201-1 associates with the NFTed recipe data is not limited to the above example. For example, the processor unit 201-1 may associate creator information included in the basic recipe information of S10 with the NFTed recipe data as one piece of authentication information. The processor unit 201-1 may also associate recipe ingredient information included in the basic recipe information of S10 with the NFTed recipe data as one piece of authentication information.

[0117] If Creator H1 or the operator of the center server 20 or blockchain server 30 wants to impose restrictions on the chef who can reproduce the recipe using the recipe data, the number of times the recipe can be reproduced, etc., the center server or cooking assistance system registers certification information for granting the reproduction right. This allows the management system 1 to grant the reproduction right only to the reproduction chef who owns the certification information.

[0118] For example, if Creator H1 grants playback rights only to those who dine at a restaurant where Creator H1 is the chef, the store's location information is registered as proof information for granting playback rights. In this case, the registered store's GPS information, etc., is linked to the NFT. If it is assumed that multiple stores will be set up at an event venue, not only location information but also QR codes, etc., to be installed at each store may be registered. Furthermore, Creator H1 and businesses, etc., who have creator certification, can add, modify, or delete this playback rights proof information at any time via the processor unit 201-2.

[0119] 9 is a flowchart showing an example of the operation of the management system 1 according to an embodiment of the present disclosure. Specifically, FIG. 9 shows an example of a process in which the reproduction cook H2 and the eater H3 obtain the playback right.

[0120] In the processing example shown in Figure 9, the reproduction cook H2 and the eater H3 obtain the playback right for the target recipe via the mobile terminal 40. As shown in Figure 9, the processor unit 401-4 of the mobile terminal 40 transmits a memory unit 403-1 indicating that the target recipe was eaten to the blockchain server 30 (S31). The processor unit 401-4 also transmits a memory unit 403-3 indicating the location where the target recipe was eaten to the blockchain server 30 (S32).

[0121] Furthermore, if eater H3 obtains the playback right, the processor unit 401-4 presents the user's (eater H3's) identification information (user ID number) to the cooking support system (playback side) 10P of the re-creation chef H2 (S33). The processor unit 101-1 of the cooking support system (playback side) 10P notifies the blockchain server 30 of the playback information (location information indicating the playback location) of the target recipe played by Creator H1, along with the presented user ID number (S34). This allows the blockchain server 30 to compare the memory unit 403-3 of the location where eater H3 ate with the location where the target recipe was played to determine whether playback rights have been granted.

[0122] In addition, the center server 20 may send certification information for the target recipe to the center server 20, and receive reproduction information (recipe data) for the target recipe from the blockchain server 30 (S35).

[0123] The blockchain server 30 collects certification information based on notifications from external devices (such as the mobile terminal 40, the cooking assistance system (playback side) 10P, and the center server 20) (S30). Next, the processor unit 301-3 of the blockchain server 30 compares the collected certification information with the certification information linked to the target recipe on the blockchain. Based on the comparison result, the processor unit 301-3 determines whether the collected certification information is certification information that can grant playback rights (S36).

[0124] Specifically, the processor unit 301-3 determines whether at least one of the creator information, location information (e.g., eating location), and code information (e.g., QR code) contained in the collected certification information matches that contained in the certification information linked to the target recipe.

[0125] In addition, the processor unit 301-3 may determine whether the location information notified by the portable terminal 40 matches the playback location information notified by the cooking support system (playback side) 10P, which indicates the location where the NFT-converted recipe data was played back.

[0126] If there is no match in S36 (No), the processor unit 301-3 of the blockchain server 30 does not grant the playback right (S40). If there is a match (S36: Yes), the processor unit 301-3 grants the playback right for the target recipe.

[0127] Specifically, the processor unit 301-3 sets the number of times and period of use of the playback right based on the storage unit 303-7 (S37). Next, the processor unit 301-3 registers information about the set playback right in the blockchain and grants the playback right for the recipe data (S38). Next, the processor unit 301-3 notifies the portable terminal 40 that the playback right for the target recipe has been granted (S39).

[0128] When the processor unit 301-3 receives the identification information (user ID number) of the user (eater H3), the processor unit 301-3 may set the user ID number as the user who can use the recipe data.

[0129] The management system 1 may distinguish between cases where a user has acquired the playback right as a eater H3 based on whether or not the user ID number is set. For example, if eater H3 of a re-creation cook H2 acquires the playback right, this eater H3 may become the re-creation cook H2. In such a case, the number of playback right holders may increase in a chain reaction, which may infringe on the rights of the creator H1 of the target recipe. In contrast, if eater H3 with a set user ID number cooks a re-creation, the granting of the playback right may not be permitted, thereby preventing a chain reaction of an increase in the number of playback right holders.

[0130] If Creator H1 or the operator of the center server 20 or blockchain server 30 sets it so that playback rights are granted by eating at a specific restaurant, when the re-creation chef H2 eats at the specific restaurant, he or she sends the menu item eaten and the restaurant's location information (GPS information) from the mobile terminal 40 to the blockchain server 30 as proof of the playback right. This allows the re-creation chef H2 to obtain the playback right for the target recipe. This playback right includes playback right management information such as the number of times the recipe can be played and the playback period.

[0131] Proof of playback rights, such as the menu eaten and the store's location information, can be obtained from barcodes or QR codes printed on receipts issued by the store, QR codes placed in the store or on the menu, date and time information and location information (GPS information, etc.) of the portable terminal 40 owned by the eater, etc.

[0132] Furthermore, when a business operator provides a reproduced recipe using the cooking support system (playback side) 10P at a chain store or event venue and grants playback rights to the consumer, the playback rights can be granted by linking the consumer's service usage ID with playback information of the cooking support system and sending it to the blockchain server. In this case, the location information may be GPS information installed in the cooking support system.

[0133] 10 is a flowchart illustrating an example of the operation of the management system 1 according to an embodiment of the present disclosure. Specifically, FIG. 10 illustrates an example of a process in which the reproduction chef H2 provides a reproduced dish using a playback right.

[0134] As shown in Figure 10, the re-creation chef H2 operates the operation / display unit 106 of the cooking support system (playback side) 10P to refer to the memory unit 203-1 stored in the center server 20, searches for the recipe he or she wants to recreate (S50), and selects the recipe to recreate (S51).

[0135] If a playback right is set for the reproduction recipe, based on a request operation by the reproduction cook H2 to use the playback right for the target menu, the processor unit 401-4 notifies the blockchain server 30 of a request for the playback right for the target menu (S52). This request for the playback right for the target menu includes, for example, identification information indicating the target menu, identification information indicating the user, and location information of the mobile terminal 40.

[0136] The processor unit 301-3 receives a request to use the playback right from the portable terminal 40 (S53), and determines whether or not to permit the reproduction cooking by referring to information about the playback right of the target menu (S54).

[0137] Specifically, the processor unit 301-3 determines whether to permit the reproduction cooking based on whether there are any remaining uses of the target recipe included in the information about the playback right. The processor unit 301-3 also determines whether to permit the reproduction cooking based on whether the period for using the target recipe included in the information about the playback right satisfies the conditions. The processor unit 301-3 also determines whether to permit the reproduction cooking based on whether the location information of the portable terminal 40 satisfies the conditions for the location for using the target recipe included in the information about the playback right. The processor unit 301-3 also determines whether to permit the reproduction cooking based on whether the identification information identifying the user matches the user identification information included in the information about the playback right.

[0138] If the reproduction cooking is not permitted (S54: No), the processor unit 301-3 determines to cancel the reproduction cooking (S55) and notifies the cooking assistance system (playback side) 10P that the reproduction cooking is not permitted. As a result, the management system 1 does not perform the reproduction cooking using the recipe data.

[0139] If the reproduction cooking is permitted (S54: Yes), the processor unit 301-3 notifies the cooking assistance system (playback side) 10P of the permission for the reproduction cooking. As a result, the cooking assistance system (playback side) 10P performs the reproduction cooking using the recipe data (S56), and the dish reproduced from the recipe data is served (S57).

[0140] The center server 20, which has received the notification after the reproduction cooking has been completed (notification of the use of the recipe data), updates the number of reproductions data for the target recipe (S58). Similarly, the processor unit 301-5 of the blockchain server 30, which has received the notification after the reproduction cooking has been completed, updates the storage unit 303-7 for the target recipe for which the usage notification has been received. Specifically, the processor unit 301-5 decrements the number of uses contained in the storage unit 303-7 according to the number of uses for which the notification has been received.

[0141] In this way, the reproduction chef H2 selects the dish he or she wants to reproduce from the recipe data on the center server 20 through the cooking support system (reproduction side) 10P. If a reproduction right is set in the recipe data, the reproduction chef H2 issues a request for the reproduction right to the blockchain server 30 via the mobile terminal 40. After receiving the request for the reproduction right, the blockchain server 30 verifies that the number of times the dish can be reproduced, the period during which the dish can be reproduced, and so on are within the usable range, and if there are no problems, the reproduction cooking can be performed using the cooking support system (reproduction side) 10P.

[0142] Furthermore, upon completion of the reproduction cooking process, the storage unit 303-7 on the blockchain server, such as the number of times the food can be reproduced, is updated. Furthermore, since the reproduction cooking is performed using the cooking assistance system (reproduction side) 10P, it is possible to grant new reproduction rights to the person who eats the reproduced dish. In this case, the location where the reproduction cooking was performed can be registered in the center server 20 through the business operator, and the location where the reproduction cooking was performed can be used as proof information for granting the reproduction right.

[0143] The place where the regenerative cooking is performed is not limited to a restaurant or kitchen studio, but may also be an apartment lounge, a shared house, an exhibition hall, a conference room, a classroom, a campsite, or the like, where the cooking support system (regenerative side) 10P is installed.

[0144] Furthermore, playback conditions can be set for playback rights according to the certification information. If a re-creation cook obtains playback rights by eating at a specific restaurant, it is possible to set such that if one person uses the food, playback is possible for four people, but if a family of three uses the food, playback is possible for ten people. Playback conditions include the number of times playback is possible, the period during which playback is possible, the amount of playback per re-creation, the location where the re-creation is performed, etc.

[0145] By using the management system 1 disclosed herein, Creator H1 can reproduce the recipe only in areas away from his / her own store, which can also prevent a decrease in the number of customers at the restaurant where the recipe was provided.

[0146] Besides GPS, the proof information for granting the playback right may be a barcode or QR code printed on a receipt issued by a store, a QR code placed in the store or on a menu, a photo of the store taken from a specific location (with date information), a photo of you and a registered store clerk, a photo of you eating a registered dish, a receipt (with date) for purchasing a souvenir, etc. Furthermore, the playback right may be granted not only for eating at a restaurant or event venue, but also for purchase records at product fairs, antenna shops, department stores, etc., cumulative purchase records of specific ingredients, admission records at fan events, visit records to designated locations (completion of stamp rallies), etc.

[0147] In addition, since the playback rights themselves are managed as NFTs on the blockchain server, they can be bought and sold, and the transfer of management is managed as a transaction history on the blockchain.

[0148] (Variation) In the management system 1 of the present disclosure, in addition to playback rights, discount coupons and the like can be provided to the re-creation cook H2 and the eater H3 of the re-creation dish through the re-creation cooking and eating experience in the cooking support system (playback side) 10P. After the re-creation cooking in the cooking support system (playback side) 10P, the re-creation cook H2 can receive incentives such as discount coupons and points by sending a re-creation completion report to the blockchain server 30. Furthermore, the re-creation cook H2 can send either or both of the re-creation cooking experience information and the re-creation cooking experience information of the eater of the re-creation dish to the blockchain server 30, allowing the eater of the re-creation dish to receive incentives such as discount coupons. Furthermore, the re-creation cook may receive incentives such as discount coupons by granting playback rights for a menu item before it is served at a restaurant and providing feedback on information obtained when the re-creation cook serves the dish to a friend or the like.

[0149] The incentives offered include discount coupons and points that can be used at Creator H1 restaurants, discount coupons and points that can be used when traveling to specific areas, and discount coupons and points for purchasing specific ingredients.

[0150] The management system 1 may also be applied to a restaurant franchise. For example, a franchisor (headquarters) may manage the use of reproduction rights by franchisees (affiliated stores) for recipe data that the franchisor has created.

[0151] (Effects) As described above, in the management system 1, recipe data including cooking record data that records cooking steps is recorded in the blockchain server 30, and rights information relating to the rights to use the recorded recipe data is registered and managed. This allows the management system 1 to manage the rights to use the recipe data.

[0152] Furthermore, when a request for use of recipe data is made via the mobile terminal 40 or the like, the management system 1 notifies whether or not the recipe data is to be used based on the registered rights information. This allows the management system 1 to manage whether or not the recipe data is to be used based on the registered rights information.

[0153] Furthermore, when the management system 1 notifies the use of recipe data in response to a request for use of recipe data, the management system 1 updates the rights information in response to the notification of use. This allows the management system 1 to update the rights information in response to the use of recipe data.

[0154] The rights information also includes user identification information that indicates the user who will use the recipe data. The management system 1 notifies the user whether the recipe data will be used based on the result of comparing the user identification information notified in response to a recipe data use request with the user identification information included in the rights information. This allows the management system 1 to manage whether the recipe data will be used based on the user identification information.

[0155] The rights information also includes the number of times the recipe data is to be used. When a request to use the recipe data is made, the management system 1 notifies the user whether or not the recipe data is to be used based on the number of times the recipe data is to be used, which allows the management system 1 to manage whether or not the recipe data is to be used based on the number of times the recipe data is to be used.

[0156] The rights information also includes a period during which the recipe data is to be used. When a request to use the recipe data is made, the management system 1 notifies the user whether or not the recipe data is to be used based on the period of use included in the rights information. This allows the management system 1 to manage whether or not the recipe data is to be used based on the period of use of the recipe data.

[0157] The rights information also includes the location where the recipe data will be used. The management system 1 notifies whether the recipe data will be used based on the result of comparing the location where the recipe data usage request was made with the usage location included in the rights information. This allows the management system 1 to manage whether the recipe data will be used based on the location where the recipe data will be used.

[0158] The rights information also includes code information that identifies the recipe data. The management system 1 notifies whether the recipe data is being used based on the result of comparing the code information notified in response to a request to use the recipe data with the code information included in the rights information. This allows the management system 1 to manage whether the recipe data is being used based on the code information that identifies the recipe data.

[0159] Furthermore, the management system 1 associates video information of the cooking process with the recorded recipe data and registers it, thereby enabling the management system 1 to associate and manage the recorded recipe data with video information of the cooking process.

[0160] Furthermore, when notifying recipe data in response to a request to use the recorded recipe data, the management system 1 also notifies video information registered in association with the recipe data, which allows the management system 1 to reproduce cooking using video information along with the recipe data.

[0161] Furthermore, the management system 1 associates and registers location information indicating the cooking location with the recorded recipe data, thereby enabling the management system 1 to manage the recorded recipe data in association with location information indicating the cooking location.

[0162] Furthermore, the management system 1 registers the rights information when the location information notified together with the rights information registration request matches the location information registered in association with the recorded recipe data. This allows the management system 1 to register the rights information based on the location information, and can, for example, not register the rights information when the location information does not match.

[0163] Furthermore, the management system 1 registers the rights information when the location information notified together with the rights information registration request matches the playback location information indicating the location where the recorded recipe data was played. This allows the management system 1 to register rights information regarding the use of the recipe data in response to a request from a person at the location where the NFT-converted recipe data was played.

[0164] Furthermore, the management system 1 associates the issued code information with the recorded recipe data and registers it, thereby enabling the management system 1 to manage the recorded recipe data in association with the code information.

[0165] Furthermore, the management system 1 registers the rights information when the code information notified together with the rights information registration request matches the code information registered in association with the recorded recipe data. This allows the management system 1 to register the rights information based on the code information, and can prevent the rights information from being registered when the code information does not match, for example.

[0166] Furthermore, the management system 1 associates creator information about the creator of the recipe data with the recorded recipe data and registers it, thereby enabling the management system 1 to manage the recorded recipe data in association with the creator information.

[0167] Furthermore, the management system 1 registers the rights information when the creator information notified together with the rights information registration request matches the creator information registered in association with the recorded recipe data. This allows the management system 1 to register the rights information based on the creator information, and can, for example, not register the rights information if the creator information is not notified.

[0168] Furthermore, the management system 1 converts recipe data into a non-fungible token (NFT) and registers rights information in a blockchain for the NFT recipe data. By managing the rights information in a blockchain for the NFT recipe data, the management system 1 can prevent tampering with the rights information.

[0169] (Other) The above-described series of processes can be executed by hardware or software. When the series of processes is executed by software, the program constituting the software is installed from a program recording medium into a computer incorporated in dedicated hardware, or into a general-purpose personal computer, etc.

[0170] (Hardware Configuration Example) The information devices (cooking assistance system 10, center server 20, blockchain server 30, and portable terminal 40) in the management system 1 described above are realized by a computer 1000 configured as shown in FIG. 11, for example. FIG. 11 is a hardware configuration diagram showing an example of a computer. The computer 1000 has a CPU 1100, a RAM 1200, a ROM (Read Only Memory) 1300, an SSD (Solid State Drive) 1400, a communication interface 1500, and an input / output interface 1600. The various components of the computer 1000 are connected by a bus 1050.

[0171] The CPU 1100 operates and controls each component based on programs stored in the ROM 1300 or the SSD 1400. For example, the CPU 1100 loads the programs stored in the ROM 1300 or the SSD 1400 into the RAM 1200 and executes processing corresponding to the various programs.

[0172] The ROM 1300 stores boot programs such as a Basic Input Output System (BIOS) that is executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000 .

[0173] The SSD 1400 is a computer-readable recording medium that non-temporarily records programs executed by the CPU 1100 and data used by such programs. Specifically, the SSD 1400 is a recording medium that records a communication program according to the present disclosure, which is an example of the program data 1450. The SSD 1400 may be another non-temporary recording medium, such as a hard disk drive (HDD).

[0174] The communication interface 1500 is an interface for connecting the computer 1000 to an external network 1550 (e.g., the Internet). For example, the CPU 1100 receives data from other devices and transmits data generated by the CPU 1100 to other devices via the communication interface 1500.

[0175] The input / output interface 1600 is an interface for connecting the input / output device 1650 and the computer 1000. For example, the CPU 1100 receives data from input devices such as a touch panel, keyboard, mouse, microphone, and camera via the input / output interface 1600. The CPU 1100 also transmits data to output devices such as a display, speaker, and printer via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading programs and the like recorded on a predetermined recording medium. Examples of media include optical recording media such as DVDs (Digital Versatile Discs) and PDs (Phase Change Rewritable Disks), magneto-optical recording media such as MOs (Magneto-Optical Disks), tape media, magnetic recording media, and semiconductor memories.

[0176] For example, when the computer 1000 functions as the cooking assistance system 10, the center server 20, the blockchain server 30, and the portable terminal 40 according to the embodiment, the CPU 1100 of the computer 1000 realizes the functions of a processor unit, etc., by executing a communication program loaded onto the RAM 1200. The communication program according to the present disclosure and data in the RAM 1200 are stored in the SSD 1400. The CPU 1100 reads and executes the program data 1450 from the SSD 1400, but as another example, the CPU 1100 may obtain these programs from another device via an external network 1550.

[0177] In this disclosure, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all of the components are in the same housing. Thus, both multiple devices housed in separate housings and connected via a network, and a single device with multiple modules housed in a single housing, are systems.

[0178] The present technology can also be configured as follows. (1) A management system comprising: a processing unit that records recipe data including cooking record data that records cooking steps; and registers and manages right information related to a right to use the recorded recipe data for the recipe data. (2) The management system according to (1), wherein, when a request to use the recipe data is made, the processing unit notifies whether the recipe data is being used based on the right information registered for the recipe data. (3) The management system according to (2), wherein, when notifying use of the recipe data in response to the request to use the recipe data, the processing unit updates the right information in response to the notification of use. (4) The management system according to any one of (1) to (3), wherein the right information includes user identification information indicating a user who will use the recipe data, and the processing unit notifies whether the recipe data is being used based on a result of comparing the user identification information notified in response to the request to use the recipe data with the user identification information included in the right information. (5) The management system according to any one of (1) to (4), wherein the rights information includes the number of times the recipe data is to be used, and the processing unit, at the time of a request to use the recipe data, notifies whether the recipe data is to be used based on the number of times of use included in the rights information. (6) The management system according to any one of (1) to (5), wherein the rights information includes a period during which the recipe data is to be used, and the processing unit, at the time of a request to use the recipe data, notifies whether the recipe data is to be used based on the period of use included in the rights information. (7) The management system according to any one of (1) to (6), wherein the rights information includes a location where the recipe data is to be used, and the processing unit notifies whether the recipe data is to be used based on a comparison result between the location where the request to use the recipe data was made and the location of use included in the rights information.(8) The management system according to any one of (1) to (7), wherein the rights information includes recipe identification information that identifies the recipe data, and the processing unit notifies whether the recipe data is to be used based on a comparison between the recipe identification information notified in response to a request to use the recipe data and the recipe identification information included in the rights information. (9) The management system according to any one of (1) to (8), wherein the processing unit registers video information of the cooking steps in association with the recorded recipe data. (10) The management system according to (9), wherein the processing unit notifies the video information registered in association with the recipe data when notifying the recipe data in response to a request to use the recipe data. (11) The management system according to any one of (1) to (10), wherein the processing unit registers location information indicating a location of the cooking steps in association with the recorded recipe data. (12) The management system according to (11), wherein the processing unit registers the rights information when location information notified together with the rights information registration request matches location information registered in association with the recipe data. (13) The management system according to any one of (1) to (12), wherein the processing unit registers the rights information when location information notified together with the rights information registration request matches playback location information indicating a location where the recipe data is played back. (14) The management system according to any one of (1) to (13), wherein the processing unit registers issued code information in association with the recorded recipe data. (15) The management system according to (14), wherein the processing unit registers the rights information when code information notified together with the rights information registration request matches code information registered in association with the recipe data. (16) The management system according to any one of (1) to (15), wherein the processing unit registers creator information regarding a creator of the recipe data in association with the recorded recipe data.(17) The management system according to (16), wherein the processing unit registers the rights information when creator information notified together with the rights information registration request matches creator information registered in association with the recipe data. (18) The management system according to any one of (1) to (17), wherein the processing unit converts the recipe data into an NFT (Non Fungible Token), and registers the rights information on a blockchain for the NFT-converted recipe data. (19) A management method, wherein a computer records recipe data including cooking record data that records cooking steps, and executes a process to register and manage rights information relating to a right to use the recipe data for the recorded recipe data. (20) A management program, wherein a computer records recipe data including cooking record data that records cooking steps, and executes a process to register and manage rights information relating to a right to use the recipe data for the recorded recipe data.

[0179] 1...Management system 10...Cooking assistance system 10P...Cooking assistance system (playback side) 10R...Cooking assistance system (recording side) 20...Center server 30...Blockchain server 40...Portable terminal 101...Processor unit 101-1...Recipe data acquisition unit 101-2...Cooking environment measurement unit 101-3...Recipe data correction unit 101-4...Cooking data provision unit 101-5...Cooking navigation unit 101-6...Recipe playback information update unit 102...Communication unit 103...Memory unit 103-1...Recipe data 103-2...Cooking environment correction value 103-3...Number of recipe playbacks 103-4...Recipe playback person information 104...Positioning unit 105...Sensor unit 106...Operation / display unit 111...IH stove 112...Cooking utensils 121...LCD tablet 122...Speaker 123...Camera 124...Microphone 125...Environment measuring instrument 126...Router 127...Server 131...Processor 132...Temperature sensor 133...Pressure sensor 134...Acoustic sensor 135...Storage 136...GPS 141...Temperature sensor 142...Humidity sensor 143...Atmospheric pressure sensor 144...Acoustic sensor 201...Processor unit 201-1...Playback right certification information registration unit 201-2...Certification information change request unit 201-3...Creator inquiry unit 202...Communication unit 203...Storage unit 203-1...Recipe data 203-2...Cooking environment correction value 203-3...Cooking condition reference data 203-4...Number of plays of each menu 203-5...Video information at the time of recording 203-6...Playback right grant certification information 204...Operation / display unit 301...Processor unit 301-1...Identifier assignment unit 301-2... Creator certificate issuing unit 301-3... Playback right granting unit 301-4... Certification information inquiry unit 301-5... Playback right management information updating unit 302... Communication unit 303... Storage unit 303-1... Recipe data 303-2... Creator information 303-3... Creator certificate 303-4... Store location information 303-5... Event venue information 303-6... QR code 303-7... Playback right management information 304... Operation and display unit 401... Processor unit 401-1... Eating information registration unit 401-2... Purchase information registration unit 401-3... Playback right receiving unit 401-4... Playback right request sending unit 401-5... QR code reading unit 402... Communication unit 403... Storage unit 403-1... Eating menu information 403-2... Eating date and time information 403-3...location information403-4...Purchase history information 404...Positioning unit 405...Operation and display unit 1001...CPU 1002...ROM 1003...RAM 1004...Bus 1005...Input / output interface 1006...Input unit 1007...Output unit 1008...Storage unit 1009...Communication unit 1010...Drive 1011...Removable media H1...Creator H2...Reproducer cook H3...Eater NW...Network

Claims

1. A management system comprising a processing unit that records recipe data including cooking record data that records cooking steps, and registers and manages rights information regarding the rights to use the recorded recipe data.

2. The management system according to claim 1, wherein, when a request for use of the recipe data is received, the processing unit notifies whether or not the recipe data is to be used based on rights information registered for the recipe data.

3. The management system according to claim 2, wherein the processing unit, when notifying the use of the recipe data in response to a request for use of the recipe data, updates the rights information in response to the notification of the use.

4. The management system described in claim 1, wherein the rights information includes user identification information indicating the user who will use the recipe data, and the processing unit notifies whether the recipe data will be used or not based on the result of comparing the user identification information notified in response to a request to use the recipe data with the user identification information included in the rights information.

5. The management system of claim 1, wherein the rights information includes the number of times the recipe data is to be used, and the processing unit notifies whether or not the recipe data is to be used based on the number of times the recipe data is to be used included in the rights information when a request to use the recipe data is made.

6. The management system according to claim 1, wherein the rights information includes a period for using the recipe data, and the processing unit notifies whether or not the recipe data will be used based on the period for using the recipe data included in the rights information when a request to use the recipe data is made.

7. The management system of claim 1, wherein the rights information includes a location where the recipe data is to be used, and the processing unit notifies whether the recipe data is to be used or not based on a comparison result between the location where the recipe data is requested to be used and the location of use included in the rights information.

8. The management system of claim 1, wherein the rights information includes recipe identification information that identifies the recipe data, and the processing unit notifies whether or not the recipe data is being used based on a comparison result between the recipe identification information notified in response to a request to use the recipe data and the recipe identification information included in the rights information.

9. The management system according to claim 1, wherein the processing unit registers video information of the cooking process in association with the recorded recipe data.

10. The management system according to claim 9, wherein the processing unit notifies video information registered in association with the recipe data when notifying the recipe data in response to a request to use the recipe data.

11. The management system according to claim 1, wherein the processing unit associates location information indicating the location of the cooking process with the recorded recipe data and registers it.

12. The management system described in claim 11, wherein the processing unit registers the rights information when the location information notified along with the request to register the rights information matches the location information registered in association with the recipe data.

13. The management system of claim 1, wherein the processing unit registers the rights information when location information notified together with the request to register the rights information matches playback location information indicating the location where the recipe data was played.

14. The management system according to claim 1, wherein the processing unit registers the issued code information in association with the recorded recipe data.

15. The management system according to claim 14, wherein the processing unit registers the rights information when the code information notified together with the request to register the rights information matches the code information registered in association with the recipe data.

16. The management system according to claim 1, wherein the processing unit registers creator information relating to the creator of the recipe data in association with the recorded recipe data.

17. The management system described in claim 16, wherein the processing unit registers the rights information when the creator information notified along with the request to register the rights information matches the creator information registered in association with the recipe data.

18. The management system according to claim 1, wherein the processing unit converts the recipe data into an NFT (Non-Fungible Token) and registers the rights information in a blockchain for the NFT-converted recipe data.

19. A management method in which a computer records recipe data including cooking record data that records cooking steps, and executes a process to register and manage rights information regarding the rights to use the recorded recipe data.

20. A management program that causes a computer to execute a process of recording recipe data including cooking record data that records cooking steps, and registering and managing rights information regarding the rights to use the recorded recipe data.

Images