WO2022149722A1 - Procédé et système de service de facturation de contenu prépayé en fonction d'une chaîne de blocs - Google Patents

Procédé et système de service de facturation de contenu prépayé en fonction d'une chaîne de blocs Download PDF

Info

Publication number
WO2022149722A1
WO2022149722A1 PCT/KR2021/017587 KR2021017587W WO2022149722A1 WO 2022149722 A1 WO2022149722 A1 WO 2022149722A1 KR 2021017587 W KR2021017587 W KR 2021017587W WO 2022149722 A1 WO2022149722 A1 WO 2022149722A1
Authority
WO
WIPO (PCT)
Prior art keywords
billchain
content
user
bill
server
Prior art date
Application number
PCT/KR2021/017587
Other languages
English (en)
Korean (ko)
Inventor
고승곤
Original Assignee
(주) 오스리움
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by (주) 오스리움 filed Critical (주) 오스리움
Publication of WO2022149722A1 publication Critical patent/WO2022149722A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G06Q20/123—Shopping for digital content
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/28—Pre-payment schemes, e.g. "pay before"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash

Definitions

  • the user terminal after the user terminal logs in to the content providing server, the user terminal transmits the billchain user DID together to the content providing server and pays for the payment details that have filled the corresponding content provider cache requesting cancellation; transmitting, by the content providing server, the result to the billchain server after approving the payment cancellation request for the payment details in which the user terminal has charged the cache;
  • the billchain server requests and receives the billchain cash credential corresponding to the payment cancellation from the user terminal, requests the public key of the transferred billchain cash credential to the billchain DID blockchain, and billchain cash performing billchain cache credential signature verification using the public key obtained from the DID document (including public key and service access address); receiving, by the billchain server, a result of the balance deduction after updating the billchain billing block chain by requesting the billchain billing block chain to deduct the balance of the user's content provider cache by the amount of the payment canceled by the user terminal; when the balance is normally deducted, the billchain server requesting billchain cash credential cancellation to the billchain D
  • FIG. 1 is a system configuration block diagram for explaining a blockchain-based prepaid content charging service system according to the present invention
  • FIG. 2 is a module configuration block diagram of a blockchain-based prepaid content charging service system according to the present invention
  • FIG. 3 is a block diagram of a block chain configuration of a block chain-based prepaid content billing service system according to the present invention.
  • the user terminal 100 is an intelligent terminal capable of accessing the content providing server 200 and adding computer support functions such as Internet communication and information search, and a plurality of application programs desired by the user (that is, , application) may be a mobile communication terminal, such as a mobile phone, smart phone, tablet, smart watch, wearable terminal, laptop, etc.
  • a mobile communication terminal such as a mobile phone, smart phone, tablet, smart watch, wearable terminal, laptop, etc.
  • the user terminal 100 in this embodiment is provided in the form of a mobile app, and after passing the smartphone biometric authentication to run the app, the app execution and credentials are provided.
  • DID Decentralized IDentifier
  • identification includes the user's name, age, personally identifiable information, and authentication information
  • the DID document is the public DID, public key, and service access address of the relevant institution.
  • the Billchain DID wallet application 120 generates and communicates with a private DID (Private DID or Pairwise DID), public key, and secret key for each connection in order to exchange identity certificates with the identity certificate issuing authority and verification authority.
  • Billchain server 300 receives the credentials of the affiliate DID stored in the user terminal 100 through the affiliate DID operator when the user selects to join through the affiliate DID when the user requests for user subscription through the content providing server 200. Verification, and when a new subscription is selected, user registration is performed through the Billchain SSO module 310 after user confirmation through real-name authentication. When the subscription is successful, the billchain SSO issuer 312 issues the billchain SSO credential generated based on the user information provided at the time of subscription to the user terminal 100 .
  • the billchain server 300 includes a billchain SSO module 310 , a billchain bill module 320 and a billchain cache module 330 .
  • the user's Billchain DID wallet application 120 When a user signs up for a new Billchain server 300, on the signup screen, after verifying the real name and email for affiliate DID verification or self-subscription processing, the user's Billchain DID wallet application 120 is registered as a smartphone biometric and Billchain SSO issue the credentials. And the user's Billchain DID wallet application 120 generates the user's public DID, public key, and private key and registers the Billchain user DID document (including public key and service access address) in the Billchain DID blockchain 400 And, the billchain DID wallet application 120 of the user terminal 100 stores a secret key to be signed when the billchain credentials are transmitted to the content providing server 200 .
  • the billchain bill module 320 generates a public DID, a public key, and a private key in the billchain bill issuer 322 when the billchain service provider installs the billchain DID block chain and stores the billchain in the billchain DID block chain 400.
  • a bill DID document (including public key and service access address) is registered, and a private key to be signed when bill chain bill credentials are issued is stored in the server wallet of the bill chain bill issuer 322.
  • the billchain cache module 330 generates a public DID, public key, and private key from the billchain cash issuer 332 when the billchain service provider installs the billchain DID block chain, and stores it in the billchain DID block chain 400.
  • a cache DID document (including public key and service access address) is registered, and the server wallet of the BillChain Cash Issuer 332 stores the private key to be signed when issuing the BillChain Cash Credential.
  • the billchain cash issuer 332 registers the billchain cache credential definition (including the cache schema and additional items of the billchain cache module) in the billchain DID blockchain 400 .
  • BillChain DID Blockchain 400 is based on Hyperledger Indy Blockchain, which can be said to be the global industry standard, Billchain Billing Blockchain 500 becomes Trustee and Steward the Billchain DID Blockchain
  • Billchain DID blockchain 400 is a steward, providing content from billchain SSO module 310, billchain bill module 320, billchain cash module 330, and content providers subscribed to billchain service
  • the servers 200 By designating the servers 200 as trust anchors, an issuer/verifier function capable of issuing or verifying credentials is given.
  • the BillChain service provider registers the schema in the BillChain DID blockchain 400, and the trust anchors generate public DID, public key, and private key.
  • the schema is searched in the Billchain DID blockchain 400 to find the necessary items. After creating a credential definition by adding it, it is registered in the Billchain DID blockchain 400. Issuers sign the credential with the issuer's private key and issue it to the user, and the verifiers obtain the issuer's DID document (including public key and service access address) from the Billchain DID blockchain 400 and submit the corresponding credential submitted by the user. The credential is signed and verified with the public key of the issuer's DID document.
  • Billchain DID blockchain 400 (Hyperledger Indy) is a DID trustee, steward (decentralized to store/read DID-related data in the blockchain, create trust anchors, and act as issuer/verifier for each trust anchor) ), and consists of trust anchor nodes.
  • the BillChain Issuer sends the BillChain Issuer's DID document required for signature verification to the BillChain DID blockchain 400. Save.
  • BillChain issuer issues zero-knowledge proof-based credentials, can be verified by the BillChain verifier, and can safely revocation the issued credentials.
  • the Billchain Billing Blockchain 500 is based on the Hyperledger Fabric Blockchain, which can be said to be a global industry standard, and configures a fabric node using the servers of Billchain service providers and content providers, By providing a content provider channel by tying the Billchain service provider node and individual content provider nodes into a channel, it provides trust in data for each content provider and ensures that data between content providers is isolated and stored.
  • Billchain billing blockchain 500 becomes a trustee and appoints Billchain DID blockchain 400 as a steward, and Billchain DID blockchain 400 serves as a steward, Billchain SSO module 310, Billchain Bill module ( 320), the billchain cache module 330, and the content providing servers 200 of content providers subscribed to the billchain service are designated as trust anchors to give an issuer/verifier function that can issue or verify credentials.
  • Billchain DID blockchain 400 registers the schema to be used for credential definition by trust anchors as stewards.
  • the issuer of the billchain server 300 signs the corresponding credential with the issuer's private key and issues it to the user, and the verifier of the content providing server 200 sends the issuer's DID document (including public key and service access address) to the billchain Obtained from the DID block chain 400 and verify the signature of the credential submitted by the user with the public key of the DID document of the issuer.
  • the issuer's DID document including public key and service access address
  • the SSO schema includes user ID (e-mail), name, date of birth, gender, phone number, address, payment information (at least one of information for payment such as credit card and account number), billchain user DID Information is included, and the Billchain SSO definition may include issuer information, SSO schema, signature type, tag, and revocation information.
  • FIG. 6 is a diagram for explaining an example of a bill schema and bill chain bill credential definition in a blockchain-based prepaid content billing service system according to an embodiment of the present invention.
  • the cache schema includes user ID (e-mail), content provider ID, payment agency ID, charging method (credit card, account transfer, mobile phone, coin), recharge amount, balance, billchain user DID information, Payment ID is included, and billchain cache definition may include issuer information, cache schema, signature type, tag, and revocation information.
  • FIG. 8 is a signal flow diagram for explaining a user's new subscription method in the blockchain-based prepaid content billing service system according to an embodiment of the present invention.
  • the user terminal 100 accesses the content providing server 200 through an application for providing a content service and performs user registration and login.
  • the affiliate DID verifier 311 of the Billchain SSO module 310 returns the affiliate DID credentials to the user.
  • the public key of the credential of the affiliated DID provided from the user terminal 100 is requested from the affiliated DID operator, and the affiliated DID operator Upon receiving the public key response for the credential of the affiliate DID, the signature of the credential of the affiliate DID is verified.
  • the billchain SSO module 310 obtains user information (name, phone number, date of birth, gender, nationality, expiration date) from the verified credential of the affiliate DID, and then requests additional information of the user from the user terminal 100 and receives and stores additional information (e-mail, address) of the user from the user terminal 100 .
  • the Billchain SSO module 310 displays the user information (name, phone number, date of birth, gender, nationality, E-mail and address) are requested and input, and the user is verified and signed up using e-mail authentication and telecommunication company real-name authentication (required to check whether an adult is an adult in zero-knowledge authentication).
  • the Billchain SSO module 310 of the Billchain server 300 informs the user terminal 100 of the successful registration and the Billchain DID wallet application 120 installation, and then the Billchain server ( 300), the billchain SSO issuer 312 issues a billchain SSO credential and provides it to the user terminal 100 to complete the user subscription.
  • the content providing server 200 provides a web site login QR code to the user terminal 100 as shown in FIG. 11 .
  • the user terminal 100 provides the billchain user DID to the billchain verifier 210 of the content providing server 200 by using the service access address (URI) obtained from the DID document of the content providing server 200 . .
  • URI service access address
  • the user terminal 100 provides the managed billchain SSO credential to the content providing server 200 after performing identity verification.
  • the user terminal 100 may perform user identification through terminal pin number, pattern, and biometric (fingerprint, face, iris) authentication.
  • the content providing server 200 stores the user's login history (Access log) through the billchain verifier 210 in the billchain billing block chain 500, The login of the web site of the content providing server 200 to the user terminal 100 is approved.
  • the content providing server 200 requests charging to the billchain cache module 330 of the billchain server 300 with the billchain user DID of the user who requested the charge.
  • the billchain cache module 330 of the billchain server 300 provides a cache charging window for the corresponding content providing server 200 to the user terminal 100 as shown in FIG. 13 .
  • the cache charging window as shown in FIG. 13 , the name of the content provider, user ID information, cache balance information of the corresponding content providing server, the amount to be charged and the payment method requested by the content providing server so as to access the payment agency information is included.
  • the payment method a credit card, account transfer, mobile phone, coin, etc. may be used. If the user selects a coin, it is linked to a coin payment agency.
  • the user selects one of the payment methods displayed on the user terminal 100 and performs payment.
  • the payment result is provided to the billchain cache module 330 of the billchain server 300 directly by the payment agency.
  • the user In order for the user to purchase content through the user terminal 100 connected to the content providing server 200 , the user requests the content providing server 200 to purchase the content through the user terminal 100 . If the user is not logged in or is not subscribed, the content providing server performs the above registration and login process first, and in the case of adult content, adult authentication is performed through zero-knowledge proof.
  • the bill chain bill module 320 opens the billing window for the content providing server to the user terminal 100 that has requested billing in the same way as a pop-up to request billing selection information.
  • the user terminal 100 transmits the billing selection information according to the user's selection (eg, 1000 CP cache per case, 10000 won CP cache for a fixed amount ...) to the billchain bill module 320 of the billchain server 300. .
  • the billchain bill module 320 updates the user's cash balance in the billchain billing block chain 500, and stores the user's cash deduction details.
  • the billchain billing blockchain 500 transmits the balance deduction result to the billchain bill module 320 of the billchain server 300 .
  • the content providing server 200 transmits the BillChain user DID document (including public key and service access address) and BillChain Bill DID document (including public key and service access address) through the BillChain verifier 210.
  • the BillChain Bill Credential is signed with the private key of the BillChain Bill Issuer 322 in the BillChain Bill Issuer 322 and the user in the BillChain DID Wallet Application 120 of the User Confirm that it is signed with the private key of
  • the content providing server 200 stores the user's content access log in the bill chain billing block chain 500 through the bill chain verifier 210, and the content is provided to the user terminal 100 .
  • the content providing server 200 uses the billchain DID block chain 400 through the billchain verifier 210 to prevent continuous use of the content when the content is normally provided by the content providing server 200. Executes a bill credential revocation request.
  • the bill chain bill issuer 322 acquires the bill chain user DID document from the bill chain DID block chain 400 using the bill chain user DID, and uses the service access address therein to use the bill chain
  • the bill credential is requested to the bill chain DID wallet application 120 of the user terminal 100 .
  • the content providing server 200 provides the billchain DID for the billchain bill credential delivered through the billchain verifier 210 A cancellation is requested to the blockchain 400 , and a validation error message (eg, the subscription period has expired) is transmitted to the user terminal 100 .
  • 17 is a signal flow diagram for explaining a purchase cancellation method in a blockchain-based prepaid content billing service system according to an embodiment of the present invention.
  • the user requests the content providing server 200 to cancel the purchase of the content purchased through the user terminal 100 .
  • the content providing server 200 obtains and verifies the Billchain user DID from the user terminal 100 through the login process, and uses the Billchain user DID. Notifies the bill chain bill module 320 of the bill chain server 300 of the purchase cancellation approval for the content purchase history.
  • the bill chain bill issuer 322 sends the bill of the content canceled by the user to the bill chain DID wallet application 120 of the user terminal 100 through the smartphone push method according to the request of the bill chain bill module 320.
  • the bill chain bill credential is provided from the bill chain DID wallet application 120 of the user terminal 100 .
  • the BillChain bill issuer 322 requests the BillChain user DID document (including the public key and service access address) and the BillChain Bill DID document (including the public key and the service access address) to the Billchain DID blockchain 400.
  • the public key of the user from the billchain user DID document responded from the billchain DID blockchain 400, and the public key of the billchain bill module 320 from the billchain bill DID document.
  • the billchain bill credential is signed with the private key of the billchain bill issuer 322 in the billchain bill issuer 322 and signed with the user's private key in the user's billchain DID wallet application 120, , request the BillChain DID blockchain 400 to cancel the BillChain Bill Credentials.
  • the billchain DID blockchain 400 revokes the billchain bill credential, and transmits the cancellation result to the billchain bill issuer 322 .
  • the user's purchase of the corresponding content is canceled and the bill chain bill credential is invalidated, so that the corresponding content of the content providing server 200 can no longer be used.
  • the billchain bill module 320 requests the billchain billing blockchain 500 to charge the user's content provider cache balance by the amount of purchase cancellation approved by the content providing server 200 . It is impossible to cancel the purchase of content charged per case, but in the case of flat-rate billing content, the amount can be deducted by the number of days of use, and the remaining amount can be charged back to the user's content provider cache balance of the billchain billing block chain 500 .
  • the billchain billing block chain 500 updates the user's content provider cache balance, stores the user's content provider cache charge history as a cash charge by canceling a purchase rather than a general payment, and then returns the balance charge result to the billchain It passes to the bill module 320 .
  • the billchain bill module 320 makes a request to the billchain cache module 330 so that the billchain cash issuer 332 issues the billchain cash credentials. This is different from the cash recharge through the payment of the payment agency in FIG. 12.
  • the customer center receives a request to cancel the purchase of the content purchased by the user, the amount used for the content is deducted from the purchase amount after processing the purchase cancellation. It is a way to deal with the customer's mistake or change of mind by charging the remaining amount after doing so.
  • the BillChain Cash Issuer 332 In response to the request for issuing the BillChain Cash Credential, the BillChain Cash Issuer 332 issues the BillChain Cash Credential and delivers it to the BillChain DID Wallet Application 120 of the user terminal 100 .
  • the billchain cash module 330 transmits the purchase cancellation result to the user terminal 100 and displays it to the user.
  • FIG. 18 is a signal flow diagram for explaining a payment cancellation method in a blockchain-based prepaid content billing service system according to an embodiment of the present invention.
  • the BillChain Cash Issuer 332 requests the BillChain user DID document (including public key and service access address) and BillChain Cash DID document (including public key and service access address) to the Billchain DID blockchain 400.
  • the public key of the user is obtained from the Billchain user DID document responded from the Billchain DID block chain 400, and the public key of the Billchain Cash issuer 332 is obtained from the Billchain Cash DID document.
  • the billchain cash credential is signed with the private key of the billchain cash issuer 332 at the billchain cash issuer 332 and signed with the user's private key at the user's billchain DID wallet application 120 .
  • the billchain cache module 330 requests the billchain billing block chain 500 to deduct the balance. If the user's content provider cache balance is less than the payment cancellation amount, since the user has already used the cache charged with the corresponding payment, the user terminal 100 notifies the user terminal 100 that payment cannot be canceled due to insufficient content provider cache balance, and the procedure ends.
  • the BillChain DID blockchain 400 revokes the BillChain Cash Credential and then transmits the BillChain Cash Credential Revocation result to the BillChain Cash Issuer 332 .
  • 19 is a signal flow diagram illustrating a content provider cache refund method in a blockchain-based prepaid content billing service system according to an embodiment of the present invention.
  • the user requests the content provider cache refund to the content providing server 200 through the user terminal 100 .
  • the content providing server 200 performs a login process to obtain a billchain user DID from the user terminal 100, and charge the billchain user DID. Notifies billchain cache module 330 of approval of refund for one user's content provider cache balance.
  • the billchain cash issuer 332 sends the billchain DID blockchain 400 to the billchain DID block chain 400 according to the request of the billchain cache module 330. Request cancellation.
  • the billchain cash module 330 deposits the refund amount into the user's account.
  • the payment agency receives the amount paid by the user, deposits it into the account of the billchain service provider, and delivers the deposit details to the billchain cash module 330 .
  • the billchain cache module 330 of the billchain server 300 updates the billchain billing block chain 500 with the settlement details calculated by the pre-contracted fee between the billchain service provider and the content provider, and the content providing server (200) Deposit the settlement amount to the account of the content provider operating.
  • the content provider checks the settlement details between the billchain service provider and the content provider in the billchain billing blockchain.
  • the user uses the Billchain DID wallet application 120 of the user terminal 100 to check the billchain SSO credential for checking the subscription identification information, and the charge identification information for checking the It is possible to check the credentials issued to the user by the billchain server 300 through the billchain bill credential for verifying the billchain cash credential and billing identification information.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente invention concerne un système destiné à un service de facturation de contenu prépayé en fonction d'une chaîne de blocs. La présente invention concerne un procédé qui permet de fournir un service de contenu prépayé, le procédé comprenant les étapes consistant : à authentifier, au moyen d'un serveur de chaîne de facturation, un utilisateur qui souhaite recevoir un service de contenu prépayé ; à fournir, au moyen du serveur de chaîne de facturation à un terminal utilisateur, un justificatif d'identité SSO de chaîne de facturation pour une chaîne de blocs comprenant un utilisateur de chaîne de facturation DID de l'utilisateur authentifié.
PCT/KR2021/017587 2021-01-05 2021-11-26 Procédé et système de service de facturation de contenu prépayé en fonction d'une chaîne de blocs WO2022149722A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2021-0000910 2021-01-05
KR1020210000910A KR102582904B1 (ko) 2021-01-05 2021-01-05 블록체인 기반 선불형 콘텐츠 과금 서비스 방법 및 시스템

Publications (1)

Publication Number Publication Date
WO2022149722A1 true WO2022149722A1 (fr) 2022-07-14

Family

ID=82357174

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/017587 WO2022149722A1 (fr) 2021-01-05 2021-11-26 Procédé et système de service de facturation de contenu prépayé en fonction d'une chaîne de blocs

Country Status (2)

Country Link
KR (1) KR102582904B1 (fr)
WO (1) WO2022149722A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110029306A (ko) * 2009-09-15 2011-03-23 엘지전자 주식회사 네트워크 임베디드 시스템 및 컨텐츠 과금 방법
KR20120075563A (ko) * 2010-12-15 2012-07-09 사단법인 금융결제원 고객 전용 네트워크 계좌 운용 방법 및 시스템
KR20140084126A (ko) * 2011-10-04 2014-07-04 퀄컴 인코포레이티드 크리덴셜 노출로부터 단일 사인-온 도메인을 보호하기 위한 방법 및 장치
KR20160140969A (ko) * 2014-12-16 2016-12-07 페이스북, 인크. 당일 결제 거래의 용이화
KR101996840B1 (ko) * 2018-12-07 2019-07-05 아콘소프트 주식회사 마이크로서비스 스토어 운영시스템
KR102139645B1 (ko) * 2020-04-13 2020-07-30 주식회사 한국정보보호경영연구소 블록체인 기반의 신원증명 시스템 및 그 구동방법
KR102160915B1 (ko) * 2019-10-08 2020-10-05 (주)드림시큐리티 무매체 신원 확인을 통한 상품 구매 서비스 제공 장치 및 방법

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110029306A (ko) * 2009-09-15 2011-03-23 엘지전자 주식회사 네트워크 임베디드 시스템 및 컨텐츠 과금 방법
KR20120075563A (ko) * 2010-12-15 2012-07-09 사단법인 금융결제원 고객 전용 네트워크 계좌 운용 방법 및 시스템
KR20140084126A (ko) * 2011-10-04 2014-07-04 퀄컴 인코포레이티드 크리덴셜 노출로부터 단일 사인-온 도메인을 보호하기 위한 방법 및 장치
KR20160140969A (ko) * 2014-12-16 2016-12-07 페이스북, 인크. 당일 결제 거래의 용이화
KR101996840B1 (ko) * 2018-12-07 2019-07-05 아콘소프트 주식회사 마이크로서비스 스토어 운영시스템
KR102160915B1 (ko) * 2019-10-08 2020-10-05 (주)드림시큐리티 무매체 신원 확인을 통한 상품 구매 서비스 제공 장치 및 방법
KR102139645B1 (ko) * 2020-04-13 2020-07-30 주식회사 한국정보보호경영연구소 블록체인 기반의 신원증명 시스템 및 그 구동방법

Also Published As

Publication number Publication date
KR102582904B1 (ko) 2023-09-27
KR20220099194A (ko) 2022-07-13

Similar Documents

Publication Publication Date Title
WO2018208105A1 (fr) Procédé reposant sur une chaîne de blocs pour effectuer un paiement pour un dispositif de l'internet des objets, et serveur, terminal de fourniture de service, et portefeuille électronique d'utilisateur l'utilisant
WO2018208106A1 (fr) Procédé de réalisation de paiement pour dispositif internet des objets au moyen d'une base de données de chaîne de blocs et d'une structure d'arbre de merkle en interfonctionnement avec cette dernière, serveur, terminal fournisseur de service et portefeuille électronique d'utilisateur l'utilisant
WO2017022917A1 (fr) Système d'émission de certificat basé sur une chaîne de blocs
WO2019208861A1 (fr) Dispositif et procédé pour fournir un service de transaction de cryptomonnaie au moyen d'un portefeuille électronique
WO2017104899A1 (fr) Système d'authentification de certificat sur la base d'une chaîne de blocs et procédé d'authentification l'utilisant
WO2018008800A1 (fr) Système d'authentification de certificat accrédité basé sur une chaîne de blocs, et procédé d'authentification de certificat accrédité basé sur une chaîne de blocs, utilisant ce système
WO2017222128A1 (fr) Procédé et serveur pour fournir un service de carte à la place d'une société émettrice de carte
WO2014189281A1 (fr) Procédé pour générer de l'argent binaire intangible géré en tant que données et système pour fournir des services le concernant
WO2017171165A1 (fr) Système d'émission de certificat public en fonction d'une chaîne de blocs et procédé d'émission de certificat public en fonction d'une chaîne de blocs utilisant ledit système
WO2018194379A1 (fr) Procédé d'approbation de l'utilisation d'une carte à l'aide d'un identificateur de jeton sur la base d'une chaîne de blocs et structure en arbre de merkle associée à celui-ci, et serveur l'utilisant
WO2018124718A1 (fr) Procédé de fourniture de service de point intégré par gestion d'une base de données de solde pour chaque bloc d'une chaîne de blocs et serveur l'utilisant
WO2020189926A1 (fr) Procédé et serveur permettant de gérer une identité d'utilisateur en utilisant un réseau à chaîne de blocs, et procédé et terminal d'authentification d'utilisateur utilisant l'identité d'utilisateur basée sur un réseau à chaîne de blocs
WO2020189927A1 (fr) Procédé et serveur de gestion de l'identité d'un utilisateur à l'aide d'un réseau de chaîne de blocs, et procédé et terminal d'authentification d'utilisateur à l'aide d'une identité d'utilisateur sur la base d'un réseau de chaîne de blocs
WO2012130035A1 (fr) Procédé d'authentification et d'autorisation d'utilisateur, et système pour sa mise en œuvre
WO2019017688A1 (fr) Procédé permettant de réaliser un paiement anticipé de comptes recevables
WO2020022531A1 (fr) Procédé et système de connexion de chaîne basée sur un retard temporel dynamique dans une chaîne de blocs à base de pop
WO2018124716A1 (fr) Procédé pour fournir un service de point intégré en utilisant une arborescence merkle dans un protocole basé sur utxo, et serveur d'appui l'utilisant
WO2013168861A1 (fr) Système et procédé d'intermédiation des paiements
WO2022169130A1 (fr) Système et procédé de service d'utilisation d'adhésion basée sur une cryptomonnaie
WO2012115490A2 (fr) Procédé pour acheter et vendre des marchandises, et système de support d'achat prenant en charge ce procédé
WO2019019245A1 (fr) Procédé et système d'achat de portefeuille de fonds, et support d'informations
WO2020189800A1 (fr) Procédé et système d'authentification de données générées dans une chaîne de blocs
WO2020189993A1 (fr) Procédé et système de prévention de perte de cryptomonnaie
WO2020141783A1 (fr) Procédé et serveur de gestion d'identité d'utilisateur à l'aide d'un réseau à chaîne de blocs, et procédé et terminal d'authentification d'utilisateur à l'aide d'une identité d'utilisateur basée sur un réseau à chaîne de blocs
WO2020153798A1 (fr) Système de paiement ou procédé de paiement utilisant une carte de crédit pouvant être liée à une url dans une transaction en ligne

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21917884

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21917884

Country of ref document: EP

Kind code of ref document: A1