Blockchain-based live commerce service system

Abstract

A blockchain-based live commerce service system according to an embodiment of the present invention includes: a live commerce service server which transmits a live commerce broadcast including product information and stores product purchase information received from a customer terminal to which the live commerce broadcast is transmitted in a database; a blockchain management server for obtaining a hash value by hashing the product purchase information, and converting the product purchase information and the hash value into transaction data; and a blockchain network for recording the transaction data in a ledger according to a consensus algorithm and returning a transaction key enabling access to the transaction data.

Description

Blockchain-based live commerce service system

[0001] The present invention relates to a blockchain-based live commerce service system.

[0002]

[0003] Online e-commerce has grown rapidly alongside the development of the Internet. Recently, with the rapid advancement of mobile Internet and smartphone technology, the e-commerce market is rapidly reorganizing into a mobile environment.

[0004] Live commerce refers to a form of e-commerce that introduces and sells products to viewers through real-time video streaming. Combining the "live" and "e-commerce," it can be defined as a combination of online shopping and broadcasting.

[0005] Consumers can access product information while watching online broadcasts, and hosts and viewers can exchange opinions. Furthermore, they can purchase products directly from the broadcast page.

[0006] Live commerce involves sellers selling products, sales intermediaries planning the live commerce experience, and customers watching the live commerce experience. Because of this multifaceted nature, live commerce has raised concerns about the potential for data generated from live commerce to be distorted or compromised.

[0007]

[0008] The present invention is intended to solve the above-described problem, and its purpose is to provide a blockchain-based live commerce service system.

[0009] In addition, it is obvious that the technical tasks are not limited to the technical tasks described above, and other technical tasks may be derived from the following description.

[0010]

[0011] A blockchain-based live commerce service system according to one embodiment of the present invention is characterized by including: a live commerce service server that transmits live commerce including product information and stores product purchase information received from a customer terminal to which the live commerce is transmitted in a database; a blockchain management server that hashes the product purchase information to obtain a hash value and converts the product purchase information and the hash value into transaction data; and a blockchain network that records the transaction data in a ledger according to a consensus algorithm and returns a transaction key that can access the transaction data.

[0012] In addition, the live commerce service server is characterized in that it stores the product purchase information in the database by mapping it with the returned transaction key.

[0013] In addition, the live commerce service server generates a verification request for the first product purchase information, and the blockchain management server transmits a verification API for verifying the first product purchase information to the live commerce service server according to the generated verification request.

[0014] In addition, the live commerce service server inputs the first product purchase information and the first transaction key mapped to the first product purchase information into the verification API, and the blockchain management server obtains first transaction data from the blockchain network using the first transaction key input into the verification API, hashes the first product purchase information to generate a first hash value, and compares the generated first hash value with the hash value included in the first transaction data.

[0015] In addition, the blockchain management server is characterized in that, if the first hashing value and the hashing value included in the first transaction data match, the first product purchase information is determined to be true.

[0016] In addition, the blockchain management server generates an electronic contract using seller information including a DID, name, and ID received from a seller terminal, product information including a product name, product ID, and product price, and sales agent information including a DID, name, and ID received from a sales agent terminal, transmits the generated electronic contract to the seller terminal and the sales agent terminal to perform an electronic signature request, and determines that the electronic contract has been concluded when each electronic signature from the seller terminal and the sales agent terminal is recorded on the electronic contract, and the live commerce service server is characterized in that, when it is determined that the electronic contract has been concluded, it transmits the live commerce.

[0017] In addition, the live commerce service server is characterized in that, when a request for confirmation of the first product information is received from the customer terminal, a verification request for the first product information is generated, a verification API is received, and the first product information and a second transaction key mapped to the first product information are input into the received verification API to determine whether the first product information is authentic.

[0018]

[0019] The present invention has the effect of not only fundamentally preventing data distortion or damage by incorporating a blockchain network with a decentralized data recording method that is difficult to alter or manipulate into a live commerce service system, but also improving data reliability by clearly identifying the source and movement path of the data.

[0020] In addition, since the effects of the present invention described as such are naturally exerted by the composition of the described contents regardless of whether the inventor is aware of them, the above-described effects are only a few effects according to the described contents and should not be recognized as describing all effects that the inventor has recognized or actually existed.

[0021] In addition, the effects of the present invention should be additionally understood by the entire description of the specification, and even if not explicitly described in sentences, if a person with ordinary knowledge in the technical field to which the described content belongs can recognize such effects through this specification, then it should be regarded as an effect described in this specification.

[0022]

[0023] FIG. 1 is a diagram showing the configuration of a blockchain-based live commerce service system according to one embodiment of the present invention.

[0024] Figure 2 is a diagram showing a process for storing data.

[0025] Figure 3 is a diagram showing the process of verifying data.

[0026] Figure 4 is a diagram showing the execution of an electronic contract between a seller and a sales agent.

[0027] FIG. 5 is a diagram showing the process of creating a DID (Decentralized Identifier), a DID document, a VC (Verifiable Credential), and a VP (Verifiable Presentation) of a seller terminal (400) and a sales agent terminal (450) according to one embodiment of the present invention.

[0028]

[0029] When adding reference numbers to components of each drawing in this specification, it should be noted that identical components are given the same numbers as much as possible even if they are shown in different drawings.

[0030] Meanwhile, the meanings of terms described in this specification should be understood as follows. Singular expressions should be understood to include plural expressions unless the context clearly defines otherwise, and terms such as "first" and "second" are intended to distinguish one component from another, and the scope of rights should not be limited by these terms. Terms such as "include" or "have" should be understood to not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0031] The term "at least one" should be understood to include all combinations that can be represented from one or more of the associated items. For example, "at least one of the first, second, and third items" means any combination of items that can be represented from two or more of the first, second, and third items, as well as each of the first, second, and third items.

[0032] FIG. 1 is a diagram illustrating the configuration of a blockchain-based live commerce service system according to one embodiment of the present invention. As illustrated in FIG. 1, the blockchain-based live commerce service system includes a live commerce service server (100), a blockchain management server (200), a blockchain network (300), a seller terminal (400), a sales agent terminal (450), and a customer terminal (500).

[0033] The live commerce service server (100) transmits live commerce. Specifically, the live commerce service server (100) transmits live commerce containing product information to the customer terminal (500). Live commerce refers to a video of a product being sold in real time.

[0034] The live commerce service server (100) may provide a product purchase information input window to the customer terminal (500). When product purchase information is entered into the product purchase information input window provided by the customer, the customer terminal (500) transmits the product purchase information to the live commerce service server (100). The product purchase input window may include a product name, product quantity, delivery address, payment link, etc. Here, the payment link is linked to a payment API that enables payment through an external payment server. When a customer makes a payment, the payment amount is deposited into an account accessible to the live commerce service server (100).

[0035] The live commerce service server (100) receives product purchase information from a customer terminal (500) and transmits the product purchase information to a seller terminal (400) and a sales agent terminal (450).

[0036] When a product is delivered based on the received product purchase information, the seller terminal (400) transmits delivery information to the live commerce service server (100). The delivery information may include the delivery completion date, etc.

[0037] When delivery information is received, the live commerce service server (100) transmits the delivery information to the customer terminal (500). When delivery completion information is received from the customer terminal (500), the live commerce service server (100) determines that delivery is complete. If delivery completion information is not received from the customer terminal (500) within a predetermined period from the delivery completion date, the live commerce service server (100) may determine that delivery is complete. In addition, if delivery incomplete information is received from the customer terminal (500), the live commerce service server (100) may determine that delivery is not complete.

[0038] In one embodiment, if the live commerce service server (100) determines that delivery is complete, it may request a deposit from the bank server to divide the deposited amount according to predetermined criteria and distribute the divided amount to the seller and sales agent's accounts. The predetermined criteria may be established based on the contractual relationship between the seller and sales agent.

[0039]

[0040] -Example 1: Data storage

[0041] Figure 2 is a diagram illustrating the data storage process. The blockchain-based live commerce service system according to the present invention stores all generated data on the blockchain network (300). For convenience, the description will assume that product purchase information is stored on the blockchain network (300).

[0042] The live commerce service server (100) stores product purchase information received from the customer terminal (500) in a database (150).

[0043] The live commerce service server (100) transmits the stored product purchase information to the blockchain management server (200).

[0044] The blockchain management server (200) receives product purchase information transmitted by the live commerce service server (100) and records the product purchase information in the blockchain network (200).

[0045] Specifically, the blockchain management server (200) hashes product purchase information to obtain a hash value, and converts the product purchase information and hash value into transaction data. The blockchain management server (200) transmits the transaction data to the blockchain network (300) and records the transaction data on the blockchain network (300).

[0046] The blockchain network (300) records transaction data transmitted by the blockchain management server (200) in a ledger. Specifically, the blockchain network (300) records transaction data in the ledger according to a preset consensus algorithm.

[0047] A blockchain network (300) includes multiple nodes, and when transaction data is received, a transaction is generated to be recorded in a ledger and the transaction data is propagated to multiple nodes. If more than half of the nodes participating in the blockchain network (300) approve the recording of the transaction data, the blockchain network (300) creates a block linked to a previously stored block, records the transaction data, and propagates the recorded block so that the corresponding block is recorded in the ledger of each node.

[0048] When a block containing transaction data is recorded in the ledger of each node, the blockchain network (300) returns a transaction key that can access the block to the blockchain management server (200).

[0049] The blockchain management server (200) transmits the returned transaction key to the live commerce service server (100). The live commerce service server (100) maps the transmitted transaction key with the corresponding product purchase information and stores it in the database (150).

[0050]

[0051] -Example 2: Data Verification

[0052] Figure 3 is a diagram illustrating a data verification process. The blockchain-based live commerce service system according to the present invention can verify the authenticity of all data stored in the blockchain network (300). For convenience, the explanation will focus on verifying product purchase information.

[0053]

[0054] The live commerce service server (100) can verify the authenticity of stored product purchase information.

[0055] To this end, the live commerce service server (100) generates a verification request for the first product purchase information and transmits the verification request for the first product purchase information to the blockchain management server (200). At this time, the verification request may be generated by the live commerce service server (100) according to a predetermined cycle, or may be generated by a seller terminal (400), a sales agent terminal (450), or a customer terminal (500).

[0056] The blockchain management server (200) transmits a verification API that verifies the first product purchase information according to the transmitted verification request to the live commerce service server (100).

[0057] The live commerce service server (100) extracts the first transaction key mapped to the first product purchase information from the database (150) and inputs the first product purchase information and the first transaction key into the verification API.

[0058] In this case, the blockchain management server (200) receives the first product purchase information and the first transaction key entered into the verification API and verifies the first product purchase information.

[0059] Specifically, the blockchain management server (200) obtains first transaction data from the blockchain network (300) using the first transaction key. Upon receiving the first transaction key from the blockchain management server (200), the blockchain network (300) searches for a block accessible using the first transaction key and returns the first transaction data included in the searched block to the blockchain management server (200).

[0060] The blockchain management server (200) can hash the first product purchase information to generate a first hash value, and verify the authenticity of the first product purchase information by comparing the generated first hash value with the hash value included in the acquired first transaction data.

[0061] The blockchain management server (200) can determine that the first product purchase information is authentic if the first hash value matches the hash value included in the first transaction data. If the first hash value does not match the hash value included in the first transaction data, the blockchain management server (200) can determine that the first product purchase information is not authentic.

[0062] The blockchain management server (200) returns the judgment result to the live commerce service server (100) through the verification API.

[0063]

[0064] Additionally, when a request for confirmation of first product information is received from a customer terminal (500), the live commerce service server (100) generates a request for verification of the first product information, receives a verification API, and inputs the first product information and a second transaction key mapped to the first product information into the received verification API to determine whether the first product information is authentic.

[0065] This is to ensure product reliability by allowing customers to directly check product information.

[0066] In addition, since the first product information can be verified in the same way as the first product purchase information in the above-described embodiment, a detailed description thereof will be omitted.

[0067]

[0068] -Example 3: Electronic contract between seller and sales agent

[0069] Meanwhile, the above explanation assumes that an electronic contract has been executed between the seller and the sales agent. Below, we will describe the execution of an electronic contract between the seller and the sales agent.

[0070] Figure 4 is a diagram showing the execution of an electronic contract between a seller and a sales agent.

[0071] First, the blockchain management server (200) requests seller information and product information from the seller terminal (400). Here, seller information may include a Decentralized Identifier (DID), name, seller ID, etc. The DID is a decentralized identifier, and the DID issuance process will be described later. Here, product information may include a product name, product ID, product price, etc.

[0072] The blockchain management server (200) requests sales agent information from the sales agent terminal (450). The sales agent information may include a DID, name, ID, etc.

[0073] The blockchain management server (200) creates an electronic contract using seller information, product information, and sales agent information. The electronic contract includes pre-established contract terms, seller information, product information, sales agent information, and an electronic signature. Once the electronic signature is recorded, the contract is concluded.

[0074] An electronic signature is recorded in the electronic contract by hashing the electronic contract to obtain an electronic contract hash value, encrypting the electronic contract hash value with the private keys held by the seller terminal (400) and the sales agent terminal (450), respectively. Here, the seller terminal (400) and the sales agent terminal (450) have private keys and public keys generated, which will be described later.

[0075] The blockchain management server (200) decrypts the electronic signatures of each seller and sales agent using their respective public keys and verifies whether the decrypted value matches the electronic contract hash value. If the decrypted value matches the electronic contract hash value, the blockchain management server (200) determines that the electronic signature is authentic. If the decrypted value does not match the electronic contract hash value, the blockchain management server (200) determines that the electronic signature is not authentic.

[0076] The blockchain management server (200) determines that an electronic contract has been concluded if both the electronic signatures of the seller and the sales agent are determined to be true.

[0077] The blockchain management server (200) records the concluded electronic contract in the blockchain network (300).

[0078] Specifically, the blockchain management server (200) hashes the electronic contract to obtain an electronic contract hash value, and converts the electronic contract and the electronic contract hash value into transaction data. The blockchain management server (200) transmits the transaction data to the blockchain network (300) and records the transaction data on the blockchain network (300).

[0079] The blockchain network (300) records transaction data transmitted by the blockchain management server (200) in a ledger. Specifically, the blockchain network (300) records transaction data in the ledger according to a preset consensus algorithm.

[0080] A blockchain network (300) includes multiple nodes, and when transaction data is received, a transaction is generated to be recorded in a ledger and the transaction data is propagated to multiple nodes. If more than half of the nodes participating in the blockchain network (300) approve the recording of the transaction data, the blockchain network (300) creates a block linked to a previously stored block, records the transaction data, and propagates the recorded block so that the corresponding block is recorded in the ledger of each node.

[0081] When a block containing transaction data is recorded in the ledger of each node, the blockchain network (300) returns a transaction key that can access the block to the blockchain management server (200).

[0082] The blockchain management server (200) transmits the returned transaction key to the live commerce service server (100). The live commerce service server (100) maps the transmitted transaction key to the corresponding electronic contract and stores it in the database (150).

[0083] The live commerce service server (100) may transmit live commerce if it determines that an electronic contract has been concluded. If it determines that an electronic contract has not been concluded, the live commerce service server (100) may block the transmission of live commerce.

[0084] Here, the live commerce service server (100) can determine that the electronic contract has been concluded after verifying the electronic contract as in Example 2 described above using the electronic contract and transaction key stored in the database (150).

[0085]

[0086] -Example 4: Issuing private keys, public keys, and DID, VC, and VP

[0087] Meanwhile, in the above-described embodiment, it is assumed and explained that the private key, public key, and DID are issued to the seller terminal (400) and the sales agent terminal (450). Below, the process of issuing the private key, public key, DID, VC, and VP of the seller terminal (400) and the sales agent terminal (450) will be described.

[0088] FIG. 5 is a diagram showing the process of creating a DID (Decentralized Identifier), a DID document, a VC (Verifiable Credential), and a VP (Verifiable Presentation) of a seller terminal (400) and a sales agent terminal (450) according to one embodiment of the present invention.

[0089] First, the seller terminal (400) and the sales agent terminal (450) request the blockchain management server (200) to issue a private key, public key, DID, VC, and VP.

[0090] The blockchain management server (200) generates a private key and a public key, and creates a DID and a DID document (DIDDoc) linked to the DID. The blockchain management server (200) records the public key in the DID document (DIDDoc) and requests registration of the DID document (DIDDoc) to the VC issuing server. Here, the VC issuing server is a server authorized to issue VCs.

[0091] At this time, the VC issuing server performs challenge verification, and the blockchain management server (200) transmits a value (challenge) corresponding to the challenge verification to the VC issuing server. The data transmitted by the blockchain management server (200) to the VC issuing server includes a DID, a DID document (DIDDoc), and a value (challenge) corresponding to the challenge verification.

[0092] The VC issuing server transmits the DID and DID document (DIDDoc) to the blockchain network (300) so that the DID and DID document (DIDDoc) are registered in the blockchain network (300).

[0093] In a blockchain network (300), when a DID and a DID document (DIDDoc) are transmitted, a smart contract (Contract) is executed, and the smart contract (Contract) generates a transaction (Tx) to create a block in the ledger according to the consensus (CBC, Consensus-Based Commitment) of the participating nodes, thereby recording the DID and DID document (DIDDoc) of the seller terminal (400) and the sales agent terminal (450).

[0094] The blockchain network (300) transmits the identifier (TxID) of the generated transaction to the blockchain management server (200).

[0095] Thereafter, the blockchain management server (200) provides the DID to the VC issuing server to perform a VC issuance request (Credential). At this time, the VC issuing server performs challenge verification, and the blockchain management server (200) transmits a value (challenge) corresponding to the challenge verification to the VC issuing server. The data that the blockchain management server (200) transmits to the VC issuing server includes the VC issuance request (Credential), DID, and a value (challenge) corresponding to the challenge verification.

[0096] When challenge verification is completed, the VC issuance server generates a VC for the seller terminal (400) and the sales agent terminal (450), and transmits the DID and the identifier (VCID) of the generated VC to the blockchain network (300) by electronically signing them (Sig).

[0097] A smart contract (Contract) of a blockchain network (300) is executed, the smart contract (Contract) verifies an electronic signature (Sig), and when verification is completed, a transaction (Tx) is generated and a block is created in the ledger according to the consensus (CBC, Consensus-Based Commitment) of the participating nodes, thereby recording the DID of the seller terminal (400) and the sales agent terminal (450), and the identifier (VCID) of the VC.

[0098] Thereafter, the blockchain network (300) transmits the identifier (TxIDdid) of the generated transaction to the VC issuing server. The VC issuing server transmits the generated VC and the identifier (TxIDdid) of the transaction to the blockchain management server (200).

[0099] The blockchain management server (200) creates a VP using the created VC, and transmits the created VP, DID, DID document, and pre-created public key and private key (Key Pair) to the seller terminal (400) and the sales intermediary terminal (450).

[0100]

[0101] Those skilled in the art will appreciate that the present invention described above can be implemented in other specific forms without changing the technical idea or essential features thereof.

[0102] Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included within the scope of the present invention.

[0103] [National Research and Development Project Supporting This Invention]

[0104] [Assignment Number] H402-23-1012

[0105] [Ministry Name] Ministry of Science and ICT

[0106] [Name of Project Management (Specialist) Agency] National IT Industry Promotion Agency

[0107] [Research Project Name] Blockchain Technology Verification (PoC) and Overseas Expansion Support Project

[0108] [Research Project Name] Web3.0-based Live Commerce Platform

[0109] [Contribution rate] 1 / 1

[0110] [Name of the project performing organization] Root Lab Co., Ltd.

[0111] Research Period: June 9, 2023 - December 31, 2023

Claims

1. A live commerce service server that transmits live commerce containing product information and stores product purchase information received from a customer terminal to which the live commerce is transmitted in a database; A blockchain management server that hashes the above product purchase information to obtain a hash value and converts the above product purchase information and hash value into transaction data; and A blockchain-based live commerce service system characterized by including a blockchain network that records the transaction data in a ledger according to a consensus algorithm and returns a transaction key that can access the transaction data.

2. In paragraph 1, The above live commerce service server, A blockchain-based live commerce service system characterized in that the product purchase information is mapped to the returned transaction key and stored in the database.

3. In paragraph 1, The above live commerce service server, Create a verification request for the first product purchase information, The above blockchain management server, A blockchain-based live commerce service system characterized in that a verification API for verifying the first product purchase information according to the generated verification request is transmitted to the live commerce service server.

4. In paragraph 3, The above live commerce service server, Enter the first product purchase information and the first transaction key mapped to the first product purchase information into the verification API, The above blockchain management server, A blockchain-based live commerce service system characterized by obtaining first transaction data from the blockchain network using the first transaction key entered into the verification API, hashing the first product purchase information to generate a first hash value, and comparing the generated first hash value with the hash value included in the first transaction data.

5. In paragraph 4, The above blockchain management server, A blockchain-based live commerce service system characterized in that if the first hashing value and the hashing value included in the first transaction data match, the first product purchase information is determined to be true.

6. In paragraph 1, The above blockchain management server, An electronic contract is created using seller information including a DID, name, and ID received from a seller terminal, product information including a product name, product ID, and product price, and sales agent information including a DID, name, and ID received from a sales agent terminal, and the created electronic contract is transmitted to the seller terminal and the sales agent terminal to perform an electronic signature request, and when each electronic signature from the seller terminal and the sales agent terminal is recorded on the electronic contract, it is determined that the electronic contract is concluded. The above live commerce service server, A blockchain-based live commerce service system characterized by transmitting the live commerce when the above electronic contract is determined to have been concluded.

7. In paragraph 1, The above live commerce service server, A blockchain-based live commerce service system characterized in that when a request for confirmation of the first product information is received from the customer terminal, a verification request for the first product information is generated, a verification API is received, and the first product information and a second transaction key mapped to the first product information are input into the received verification API to determine the authenticity of the first product information.

Images