Information processing system and information processing method

Abstract

Provided are an information processing system, an information processing method, and a computer program that enable easy setting and control of a paywall using blockchain technology. 【Solution means】The information processing system includes a server device that accepts creation and editing of content, a first client device of a content poster, a second client device of a content viewer, and a blockchain system. The first client device embeds a paywall script at an arbitrary location of the content to be created, and the smart contract of the blockchain system executes a cost payment process from the viewer's wallet address to the poster's wallet address by the script. When the server device can confirm a successful record of the payment process in the smart contract, it transmits the data of the target content after the paywall is lifted to the second client device.

Description

Technical Field

[0001] The present invention relates to an information processing system for controlling a paywall for text on the Web. and Information processing method by law is concerned.

Background Art

[0002] For some or all of the articles and blogs published on the Web, a paywall system is used to make them non-public except for regular subscribers and readers who have temporarily paid, and to enable recovery of profits for the content published on the Web (see Patent Document 1, etc.).

[0003] Regarding the data of the paid parts of articles and blogs, the article and blog platforms themselves or other operators register the content in a separate database, and there are methods such as readers purchasing from the platform or operator server.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When a platform provider or an operator storing content sells paid content, it is necessary to manage the paid content in the database without leakage. Furthermore, there are concerns such as the need to hold purchase funds from readers and pay funds to the article or blog poster, and security risks spreading to several places. Blog and article posters need to register as posters for the paywall function with platform providers or other operators in order to deposit content, which is troublesome.

[0006] The present invention aims to provide an information processing system that can easily set and control a paywall using blockchain technology. and Information processing method the law is provided.

Means for Solving the Problems

[0007] An information processing system according to an embodiment of the present disclosure includes a server device that provides a Web application for receiving creation and editing of content and distributes the created content, a first client device of a content poster who uses the Web application, a second client device of a viewer of the content distributed from the server device, and a blockchain system connected to the server device and the second client device. The first client device embeds a paywall script at an arbitrary location in the content to be created. When a request for paywall release is received from the second client device for the target content, the smart contract of the blockchain system executes a cost payment process from the viewer's wallet address to the poster's wallet address by the script. The server device transmits the data of the target content after paywall release to the second client device when it can confirm a successful record of the payment process in the smart contract.

[0008] In the information processing system, information processing method, and computer program of the present disclosure, a script for causing a smart contract to execute a cost payment process from a viewer's wallet address to a poster's wallet address when releasing a paywall can be embedded at an arbitrary location in the content.

Effects of the Invention

[0009] According to the present disclosure, it is possible to set and control a paywall using blockchain technology.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Embodiments for Carrying Out the Invention

[0011] The present disclosure will be specifically described with reference to the drawings showing its embodiments.

[0012] In the present disclosure, the "blockchain system" refers to a system that includes a plurality of computers capable of communicating with each other and a network connecting the plurality of computers, and creates a blockchain by distributed processing of the plurality of computers. In the blockchain, the required transactions are executed and the results are incorporated.

[0013] FIG. 1 is a schematic diagram of an information processing system 100 of the present disclosure. The information processing system 100 includes a first client device 1, a second client device 2, a server device 3, and a blockchain system 4. The first client device 1, the second client device 2, and the server device 3 can transmit and receive data to and from each other via a network N which is a so-called Internet. A wallet address in the blockchain system 4 is associated with each of the first client device 1, the second client device 2, and the server device 3. Secret keys for accessing the wallet addresses are individually managed by users or operators of the first client device 1, the second client device 2, and the server device 3.

[0014] The information processing system 100 is based on a content distribution service in which the server device 3 stores web content including text, images, videos, or audio posted by the first client device 1 in a content DB (Data Base) 310 and provides the web content in response to a request from the second client device 2. The web content may be a blog, a news site, or a corporate publicity page.

[0015] The control of the paywall in the information processing system 100 of the present disclosure is realized as an additional function for this content distribution service by a plugin program P1 that writes a control script for part or all of the web content from the first client device 1 and a smart contract (paywall release contract) 400 deployed in the blockchain system 4. The script embedded in the web content by the plugin program P1 shows a paywall to a viewer (site visitor) of the web content and causes each of the second client device 2, the server device 3, and the smart contract 400 to execute a procedure for releasing the paywall.

[0016] Here, for the use of the plugin program P1, neither the user of the first client device 1 (the poster of the web content) nor the user of the second client device 2 (the viewer of the web content) needs to register as a user of the system. Also, in the information processing system 100 of the present disclosure, assets (such as fiat currency and cryptocurrency) from the viewer who uses the second client device 2 to request the release of the paywall are not held by the operator side of the server device 3 or the smart contract 400. The smart contract 400 charges a fee for the payment of assets from the viewer to the poster for the release of the paywall, but does not take the mode of receiving from the viewer once and then paying to the poster. The smart contract 400 records that there has been a payment of assets for the release of the paywall from the second client device 2 to the first client device 1 and makes it referable.

[0017] Thus, the configuration and processing procedure of the information processing system 100 for realizing the setting or release of the paywall using the blockchain technology by the plugin program P1 will be described.

[0018] FIG. 2 is a block diagram showing the configuration of the first client device 1, and FIG. 3 is a block diagram showing the configuration of the second client device 2. Both the first client device 1 and the second client device 2 are desktop or laptop PCs (Personal Computers). The first client device 1 and the second client device 2 may also be smartphones, tablet terminals, etc. Hereinafter, the first client device 1 will be described. The second client device 2 will be given corresponding reference numerals to the configuration of the first client device 1 and detailed description thereof will be omitted.

[0019] The hardware configurations of the first client device 1 and the second client device 2 are equivalent as shown in FIGS. 2 and 3, and which one it is can be switched based on the position (account) in the content delivery service. For the web application for creating and editing web content, account registration is required to identify the poster. When logging in to the web application with that account and applying the plugin program P1, the general-purpose computer functions as the first client device 1. The computer for acquiring web content for viewing functions as the second client device 2.

[0020] The first client device 1 includes a processing unit 10, a storage unit 11, a communication unit 12, a display unit 13, and an operation unit 14. The processing unit 10 includes processors such as one or more CPUs (Central Processing Unit), MPUs (Micro-Processing Unit), and GPUs (Graphics Processing Unit). The processing unit 10 includes a memory which is a temporary storage medium such as SRAM (Static Random Access Memory) and DRAM (Dynamic Random Access Memory). The processing unit 10 may be configured as one piece of hardware (SoC: System On a Chip) integrating the processor, the memory, further the storage unit 11, and the communication unit 12.

[0021] The storage unit 11 is a relatively large-capacity non-volatile storage medium such as a hard disk or a flash memory. It stores a program (program product) necessary for the processing unit 10 to execute processing and reference setting data. The program product includes an OS (Operating System) program, a Web browser program P0 operating on the OS, and a plugin program P1 for this Web browser program P0. Here, the plugin program P1 is data for identifying the functions of the present disclosure added to the Web browser program P0, and its entity is temporarily stored in the memory of the processing unit 10 by the function of the Web browser program P0. The program product may include a special client program that exhibits their functions instead of the Web browser program P0 and the plugin program P1. The storage unit 11 may store the wallet address of the user who uses the first client device 1.

[0022] The program product including the Web browser program P0 and the plugin program P1 stored in the storage unit 11, or a specific client program substituting therefor, may be what the processing unit 10 reads out the program group (Web browser program P90 and plugin program P91) stored in the computer-readable non-volatile storage medium 9 and stores in the storage unit 11. The program product stored in the storage unit 11 may be what the processing unit 10 downloads from a download server via the communication unit 12 and stores in the storage unit 11.

[0023] The communication unit 12 is a communication device that realizes communication via the network N. The communication unit 12 may be any of a wired LAN network card, a communication device that realizes carrier communication via a carrier network, an optical communication device, and a communication device corresponding to a wireless network such as WiFi or Bluetooth (registered trademark). The communication unit 12 only needs to be capable of TCP (Transmission Control Protocol) communication for sending and receiving data of a Web application provided by the server device 3 and for sending and receiving content.

[0024] The display unit 13 uses a display such as a liquid crystal display or an organic EL (Electro Luminescence) display. The display unit 13 displays a Web page including characters and images by the processing of the processing unit 10. The display unit 13 may use a display with a built-in touch panel.

[0025] The operation unit 14 is a user interface such as a keyboard or a pointing device that receives operations from the user. The operation unit 14 may be a touch panel built into the display of the display unit 13 or a physical button. The operation unit 14 may be a voice input unit that receives voice operations by a voice recognition function. The operation unit 14 can notify the processing unit 10 of operation information by the user.

[0026] Figure 4 is a block diagram showing the configuration of the server device 3. The server device 3 is described as being composed of one server computer for the sake of simplicity in the following description, but it may be configured to distribute processing among a plurality of server computers. The server device 3 is managed by a content delivery service provider. The server device 3 includes a processing unit 30, a storage unit 31, and a communication unit 32.

[0027] The processing unit 30 includes one or more processors such as a CPU, MPU, or GPU. The processing unit 30 includes a memory that is a temporary storage medium such as SRAM or DRAM.

[0028] The storage unit 31 is a relatively large-capacity non-volatile storage medium such as a hard disk or a flash memory. The storage unit 31 stores data referenced by the processing unit 30. In the storage unit 31, a wallet address for the system of the present disclosure, which is assigned to the content delivery service provider who manages the server device 3, is registered. This wallet address is an address that can be used in the blockchain system 4, is dedicated for signature, and no assets such as cryptographic assets are associated with it. In the storage unit 31, a content DB 310 for storing the posted Web content is constructed in association with the user information (account) of the poster who is a user of the first client device 1. In the content DB 310, the Web content (also referred to as a post, an article, or a Web page) received by the Web application for content creation / editing provided by the server device 3 is stored in association with the identifier of the Web content, the account (the Web site domain of the poster), and the post ID. The content DB 310 stores, as poster information, data for the poster to receive cryptographic assets when the paywall is lifted for each poster's account, for example, the poster's wallet address, the network of the cryptographic assets, and the setting of the currency unit.

[0029] The communication unit 32 is a communication device that realizes communication via the network N. The mode of the communication unit 32 is not limited as long as it can communicate with communication devices such as the first client device 1.

[0030] FIG. 5 is a block diagram showing the configuration of the node 40 in the blockchain system 400. The node 40 may be a server computer, a desktop or laptop PC, or a communication terminal device such as a smartphone or a tablet terminal. The node 40 includes a processing unit 41, a storage unit 42, and a communication unit 43. Also, as long as the node 40 is a device including at least the processing unit 41 and the communication unit 43, a part or all of the node can be configured by a part of the processing unit 41.

[0031] The processing unit 41 uses a processor such as a CPU or GPU and a memory. The processing unit 41 may be configured as one piece of hardware integrating the processor, the memory, further the storage unit 42 and the communication unit 43. A secret key uniquely owned by each of the nodes 40 may be stored in the memory of the processing unit 41. Then, the processing unit 41 executes each process based on the node program stored in the storage unit 42, and causes a general-purpose computer to function as a node in the blockchain system 400.

[0032] The storage unit 42 uses a hard disk or a flash memory and stores programs and data referred to by the processing unit 41 including the node program. The storage unit 42 stores blocks constituting the blockchain. The node program includes a program P4 for causing the processing unit 41 (a smart contract that executes predetermined arithmetic processing for requests) 400 described later to function. The storage unit 42 may store a public key and an address based on the secret key.

[0033] The communication unit 43 is a communication module that realizes mutual communication between the nodes 40. The communication unit 43 uses a network card, an optical communication device, a wireless communication device, or the like.

[0034] The process of setting and releasing the paywall by the plugin program P1 and the smart contract 400 in the information processing system 100 configured as described above will be described.

[0035] First, a content poster who is a user of the first client device 1 creates web content via a web application for content creation / editing provided from the server device 3. If an operation of applying the plugin program P1 of the present disclosure to the poster's account is performed on the web application provided by the server device 3, it is possible to set a paywall that can be released by payment as described later.

[0036] FIG. 6 is a flowchart showing an example of a paywall setting procedure. Based on the web browser program and the plugin program P1, an editing page of web content provided from the server device 3 is displayed, and until an end operation is performed, the processing unit 10 of the first client device 1 executes the following processing.

[0037] The processing unit 10 accepts an edit or save operation on the displayed editing page (step S101). The processing unit 10 determines whether or not the embedding of the paywall provided by the plugin program P1 is selected for the web content to be edited (step S102). The editing page can accept editing such as text and image insertion for each editing unit in the web content, and can call a tool for accepting an external service cooperation function or the like. When the plugin program P1 is applied, as one of the tools, it is possible to set a paywall that cooperates with the smart contract 400 in the web content.

[0038] If it is determined in step S102 that the embedding of the paywall is not selected (S102: NO), the processing unit 10 returns the process to step S101 and continues to accept the operation until an end operation is performed on the editing page.

[0039] If it is determined in step S102 that the embedding of the paywall is selected (S102: YES), the processing unit 10 embeds the paywall script in the pointed-out location of the web content by the plugin program P1 (step S103), and displays an acceptance interface for selecting a price and a currency unit on the editing page (step S104). The script in step S103 includes code for displaying an interface including a link for activating the cooperation with the wallet during browsing, and defines identification data for calling the smart contract 400. In step S104, the processing unit 10 may also accept the setting of the affiliate reward.

[0040] The processing unit 10 saves it to the script embedded with the price received by the reception interface displayed in step S104 and the data of the selected currency unit (step S105). In step S105, the processing unit 10 stores it as a parameter of the script in the metadata within the non-public Web content. If it has already been received by the reception interface, the process of S105 may be omitted.

[0041] The processing unit 10 determines whether the public release (posting) of the Web content to be edited has been selected (step S106). If the public release has not been selected (S106: NO), the processing unit 10 transmits the data of the Web content to the server device 3 in a non-public state (step S107). Thereby, the Web content can be stored in the content DB 310 in the server device 3. The processing unit 10 returns the process to step S101 and continues the operation reception process until an end operation is performed on the page.

[0042] When the public release of the Web content in which the embedding of the paywall is selected is selected (S106: YES), the processing unit 10 creates setting data for the paywall (paywall setting data) (step S108). The paywall setting data created in step S108 includes the creation date and time, or the public release date and time, or the update date and time, an identifier using the ULID (Universally Unique Lexicographically Sortable Identifier) for the post, the post ID within the content delivery service, the price and currency unit described and held in step S105, and the affiliate reward setting. The paywall setting data is described in the Web content as a parameter of the paywall script embedded in the Web content. The paywall setting data itself can be inserted at an arbitrary timing during the editing of the Web content, and in step S108, it may only update the public release date and the like. The paywall setting data may be transmitted to the server device 3 as separate data that can be specified for each paywall.

[0043] The processing unit 10 transmits the data of the web content to the server device 3 in the public state (step S109), whereby the server device 3 stores the web content in the content DB 310. The processing unit 10 finishes the paywall setting process for the web content to be published. Before and after step S109, the processing unit 10 may transmit the paywall setting data created in step S108 to the server device 3 again.

[0044] By the process of FIG. 6, the web content including the paywall setting data is stored in the content DB 310 of the server device 3 in association with the user information (account or domain) of the poster and the post ID.

[0045] FIG. 7 is a diagram showing a display example of the paywall reception interface. FIG. 7 shows the web browser screen 130 displayed on the display unit 13 of the first client device 1. The web browser screen 130 of FIG. 7 shows the editing page 131 of the web content to be posted. On the editing page 131, the reception interface 132 is displayed because the embedding of the paywall at the editing location is selected. The reception interface 132 includes an input field 133 for receiving the input of numbers, a pull-down menu 134 for receiving the selection of currency units, and an update button 135. In the reception interface 132 of FIG. 7, 1000 yen is set as the legal currency. When the update button 135 is selected by the operation unit 14, the processing unit 10 executes the description of the data of the price and currency unit received in S105 above. In the example of FIG. 7, Ether (ETH) is selected as the currency unit and a numerical value is input.

[0046] The editing page 131 shown in FIG. 7 includes a public interface 136. When the public interface 136 is selected, the paywall setting data including the data of the price and currency unit selected at the reception interface 132 is created (S108), and the posted content to be edited becomes public.

[0047] Second, the process for viewing the web content embedded with the paywall as described above and releasing the paywall will be described. FIG. 8 is a diagram showing an example of the display of the paywall. FIG. 8 shows a web browser screen 230 displayed on the display unit 23 of the second client device 2 of the viewer of the web content. In the web browser screen 230 of FIG. 8, the posted web content is displayed, and after the mark "To read more", the interface 231 of the paywall is displayed by the embedded script. In the interface 231 of FIG. 8, based on the paywall setting data described in the web content (or referenced from the content DB 310), the price read by the web browser program P0 of the web content is displayed. The paywall setting data includes a post ID, price, currency unit, etc. for identifying the web content being displayed by the web browser program P0. In the interface 231, a button 232 linked with a link for activating the link to the viewer's user wallet is displayed by the web browser program P0 through a script.

[0048] The process when the button 232 in the web content displayed on the web browser screen 230 shown in FIG. 8 is selected by the operation unit 24 will be described below. FIGS. 9 - 11 are flowcharts showing an example of the paywall release procedure.

[0049] When an operation indicating the intention to release the paywall (here, the selection of the button 232) is received (step S201), based on the paywall script embedded in the web content and the web browser program P0, the processing unit 20 activates the user's wallet application of the viewer (step S202). The wallet application is a plugin program applied to the web browser program P0 of the second client device 2. The wallet application may be activated as a separate application.

[0050] Based on the same script, the processing unit 20 acquires the wallet address of the launched wallet application (step S203). If the launch of the wallet application fails in step S203, the processing unit 20 does not continue with the subsequent processing. In this case, the viewer using the second client device 2 cannot release the paywall.

[0051] The processing unit 20 accepts the selection of the cryptocurrency circulation network and currency unit available for payment from the acquired wallet address (step S204). In step S204, the processing unit 20 may acquire the network and currency unit of the cryptocurrency available for payment set in the poster information of the target web content by the script included in the web content, and accept a selection operation therefrom.

[0052] The processing unit 20 accepts a purchase operation from the interface displayed by the script included in the web content (step S205). When a purchase operation is accepted, the processing unit 20 transmits a request for information necessary for paywall release (content purchase) to the server device 3 by the same script (step S206).

[0053] When the processing unit 30 of the server device 3 receives a request from the second client device 2 (step S301), it reads out the information necessary for paywall release payment from the poster information in the content DB 310 for the request (step S302). The necessary information is, for example, the wallet address for the poster to receive, the signature used in the processing described later, and the like.

[0054] The processing unit 30 acquires the conversion rate between the price and currency unit of the paid part of the target web content included in the paywall setting data and the cryptocurrency network and currency unit included in the paywall release request at the time of receiving the request (step S303). The processing unit 30 calculates the payment amount in the currency unit of the cryptocurrency included in the paywall release request (step S304).

[0055] The processing unit 30 acquires the ULID at that time point and uses it as the ticket ID (step S305). Not limited to the ULID, other data sequences may be used as long as a unique identification number that includes the time stamp at that time point and is easy to sort can be obtained.

[0056] The processing unit 30 creates a signing message that includes the issued ticket ID, the receiving wallet address, the price, the currency unit, and the post ID as character strings (step S306). If the affiliate setting data is included, the processing unit 30 also includes this.

[0057] The processing unit 30 signs the created signing message with the private key corresponding to the signing wallet address stored in the storage unit 31 (step 307). The processing unit 30 stores, in association with the ticket ID, the identifier of the web content including time information, the data of the encrypted assets to be paid, and the signing message as ticket information (step S308).

[0058] The processing unit 30 returns the information necessary for paywall release, such as the data read in step S301, the payment amount information calculated in step S303, the signature data, the receiving wallet address, and the ticket ID, to the second client device 2 (step S309). The processing unit 30 may also include other information such as the signing wallet address. If the affiliate setting data is included, the processing unit 30 also includes this.

[0059] The processing unit 20 of the second client device 2 receives the information necessary to respond to the request (step S207).

[0060] Based on the received information, the processing unit 20 acquires the identification data of the smart contract 400 for paywall release by the script of the web content (step S208). The identification data of the smart contract is included as the metadata of the web content. Alternatively, the processing unit 20 may acquire the necessary information from the server device 3.

[0061] Based on the identification data obtained in step S208, the processing unit 20 calls the payment function of the smart contract 400 of the blockchain system 4 (step S209). The processing unit 20 provides the smart contract 400 with the signature data, ticket ID, receiving wallet address, payment amount, and data such as the post ID received from the server device 3 as necessary information (step S210). If the affiliate setting data is included, the processing unit 20 also provides it.

[0062] The smart contract 400 executes a check for contradictions in the data provided in step S210 (such as the validity / invalidity of the affiliate) and the expiration date obtained from the time information of the ticket ID (ULID) in the called payment function (step S401). As part of the check, the smart contract 400 creates a payment message that includes the provided ticket ID, receiving wallet address, price, currency unit, and post ID as a string (step S402). Based on the created payment message and the provided signature data, the smart contract 400 checks the correspondence with the signature message of the server device 3 (step S403). Since the message creation algorithm executed on the server device 3 and the message creation algorithm executed by the smart contract 400 are the same, if there are alterations such as price tampering or time tampering where the same message should be created, the check fails without correspondence. In step S403, the smart contract 400 may check the correspondence between the messages.

[0063] The smart contract 400 determines whether the checks in steps S401 and S403 are successful (step S404). If it is determined that the check has failed (S404: NO), the smart contract 400 does not perform the subsequent processing and returns an error for the call to the payment function (step S405).

[0064] By checking in steps S402 and S403, it is possible to check the correctness of the posted content to be unlocked from the paywall by the post ID, and including the price can also prevent price forgery. By including the affiliate setting data in the check target, it is also possible to prevent forgery of the affiliate reward rate.

[0065] If it is determined that the check is successful (S404: YES), the smart contract 400 causes a quantity of cryptocurrency corresponding to the payment amount to be transferred from the viewer's wallet address to the submitter's receiving wallet address via the smart contract (step S406). In step S406, the smart contract 400 collects a portion of the cryptocurrency paid by the viewer as a fee. If the viewer purchases web content via an affiliate, based on the affiliate settings configured for the target content, a portion of the cryptocurrency paid by the viewer is transferred to the affiliate as a referral fee. Also, the gas fee for the processing of the smart contract 400 in steps S401 - S406 and step S407 described below is borne by the viewer.

[0066] The smart contract 400 stores a record including the viewer's wallet address, an identifier containing the time information at the time of posting, the post ID, and the ticket ID in the storage (memory unit 42) as evidence that the viewer has paid cryptocurrency to unlock the paywall of the target web content (step S407). The record includes, for example, a non - zero value using the viewer's wallet address and the post ID as keys. The record does not necessarily require these data and may include other data as long as it can identify which viewer has paid for which post.

[0067] After calling the payment function, the second client device 2 determines whether the check was successful and whether a transaction record of the cryptocurrency transfer was recorded (step S211). If the check fails and it is determined that the transfer transaction was not recorded (S211: NO), the processing unit 20 aborts the paywall unlocking and ends the process.

[0068] When it is determined that the transfer transaction has been recorded (S211: YES), the processing unit 20 receives a signature corresponding to the viewer's wallet address for an arbitrary string (step S212). In step S212, for example, the processing unit 20 creates a signature based on the private key held by the wallet application started in step S202. The processing unit 20 transmits the message and the signature to the server device 3 by a script embedded in the content (step S213).

[0069] When the processing unit 30 of the server device 3 receives a signature by a script embedded in the Web content being displayed on the source second client device 2 (step S310), it makes an inquiry about the signature to the designated smart contract 400 (step S311). In step S311, the processing unit 30 makes an inquiry to identify whether the viewer has made a payment for the target post ID. For example, in step S311, the processing unit 30 designates the viewer's wallet address that can be calculated from the signature and the post ID, and inquires whether there is a purchase (payment record) for unlocking the paywall of the target Web content by the wallet address of the viewer who made the signature.

[0070] Here, when the signature of the viewer's wallet address is valid, it is determined whether there is a record with a non-zero value using the designated wallet address and post ID as keys as the record stored in step S407 in the smart contract 400. If the value is not zero, the smart contract responds that there is a record of a legitimate payment. That is, through the processing of the server device 3 and the smart contract 400, it is confirmed whether there is a record indicating that the viewer who made the signature has indeed made a payment for unlocking the paywall of the corresponding Web content. For this reason, a confirmation result is returned from the smart contract 400.

[0071] The processing unit 30 of the server device 3 determines whether, in response to an inquiry, a result indicating that there is a record of payment evidence from a viewer who has made a legitimate signature has been returned (step S312).

[0072] If the processing unit 30 determines that a result indicating that there is no record of payment evidence has been returned (S312: NO), it returns an error (step S313) and ends the process.

[0073] If the processing unit 30 determines that a result indicating that there is a record has been returned (S312: YES), it releases the paywall, reads the released web content from the content DB 310, and transmits it to the second client device 2 (step S314).

[0074] The processing unit 20 of the second client device 2 receives the result of the signature transmission in step S213 (step S214), displays a screen on the display unit 23 according to the result (step S215), and ends the process. In step S214, if the signature verification is successful at the server device 3 and it is determined that there is a payment record, the web content with the paywall released is displayed, and if it is determined that there is no record, an error is displayed.

[0075] In this way, a paywall that can be released using blockchain technology can be easily set by the operation of the poster. When releasing the paywall, the server device 3 on the side that distributes the content does not need to receive payment for the viewer's assets, nor does it need to separately hold it outside the server device 3 as paid content.

[0076] The embodiments disclosed as above are illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims, and includes all modifications within the meaning and scope equivalent to the claims.

Explanation of Reference Numerals

[0077] 1 First client device 10 Processing unit 11 Memory unit P1 Plug-in program (computer program) 2 Second client device 20 Processing unit 3 Server device 30 Processing unit 4 Blockchain system 400 Smart contract (computer program)

Claims

1. A server device that provides a web application for receiving content creation and editing and distributes the created content, A first client device of a content poster who uses the web application, A second client device of a viewer of content distributed from the server device, The server device and a blockchain system connected to the second client device Including, The first client device embeds a paywall script at an arbitrary location of the content to be created, When a request for paywall release is sent to the target content from the second client device by the script, the server device issues a ticket ID at the time of receiving the request, and the post ID, price, and currency unit of the cryptocurrency used for payment of the target content based on the paywall setting data set for the target content, and creates a signature message including the wallet address of the poster stored for the target content as a character string, The server device, Creates a signature based on the wallet address of the server device for the signature message, Sends the payment amount required for paywall release, the wallet address of the poster of the target content, the ticket ID, and the signature data to the second client device, The second client device, Calls the smart contract of the blockchain system based on the script, Provides the payment amount, the wallet address, the ticket ID, and the signature data to the smart contract, The smart contract determines whether to execute the payment process by verifying whether it can create a message corresponding to the signature message using the information given from the second client device and the signature data, If it is determined to execute the payment process, it executes the payment process of the cost from the viewer's wallet address to the poster's wallet address, When the server device can confirm the successful record of the payment process in the smart contract, it sends the data of the target content after paywall release to the second client device An information processing system.

2. The server device stores ticket information including the posting ID of the target content and the ticket ID. The server device transmits the ticket ID to the second client device. The payment process is executed by specifying the ticket ID. When the payment process is successful, the smart contract stores a record including the wallet address of the payer viewer and the posting ID of the payment target. The server device confirms the successful record based on the confirmation result of the record in the smart contract specified by the posting ID of the target content and the wallet address of the viewer. The information processing system according to claim 1.

3. By the script, the second client device displays an interface for starting the viewer's wallet application and receiving a designation of the currency unit of the cryptocurrency that can be paid with the wallet application. By the script, the server device acquires, at the timing when the request is made, the conversion rate between the designated currency unit and the currency unit of the cost set for the paywall. Calculate the payment amount of the cost at the conversion rate. The information processing system according to claim 1.

4. A server device that provides a Web application for receiving creation and editing of content and distributes the created content, A first client device of a content poster who uses the Web application, A second client device of a viewer of the content distributed from the server device, A blockchain system connected to the server device and the second client device In a system including The first client device embeds a paywall script at an arbitrary location in the content to be created. When a paywall release request for the target content is transmitted from the second client device based on the script, the server device creates a signing message including, in string form, the ticket ID issued at the time of receiving the request, the posting ID, price, and currency unit of the cryptocurrency used for payment of the target content obtained based on the paywall setting data set for the target content, and the wallet address of the poster stored for the target content. The server device Create a signature based on the wallet address of the server device for the signature message. Send the payment amount required for unlocking the paywall, the wallet address of the content submitter of the target content, the ticket ID, and the signature data to the second client device. The second client device Based on the script, call the smart contract of the blockchain system. Provide the payment amount, the wallet address, the ticket ID, and the signature data to the smart contract. The smart contract determines whether to execute the payment process by verifying whether it can create a message corresponding to the signature message using the information provided from the second client device and the signature data. If it is determined to execute the payment process, execute the payment process of the cost from the viewer's wallet address to the submitter's wallet address. When the server device can confirm the successful record of the payment process in the smart contract, send the data of the target content after unlocking the paywall to the second client device. Information processing method.

Images