FI20215453A1 - Blockchain-based decentralized domain name update system and method - Google Patents

Blockchain-based decentralized domain name update system and method Download PDF

Info

Publication number
FI20215453A1
FI20215453A1 FI20215453A FI20215453A FI20215453A1 FI 20215453 A1 FI20215453 A1 FI 20215453A1 FI 20215453 A FI20215453 A FI 20215453A FI 20215453 A FI20215453 A FI 20215453A FI 20215453 A1 FI20215453 A1 FI 20215453A1
Authority
FI
Finland
Prior art keywords
domain
domain name
smart contract
updated
node
Prior art date
Application number
FI20215453A
Other languages
Finnish (fi)
Swedish (sv)
Inventor
Jie Bai
Original Assignee
Nanjing Ruixiang Information Tech Co Ltd
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 Nanjing Ruixiang Information Tech Co Ltd filed Critical Nanjing Ruixiang Information Tech Co Ltd
Publication of FI20215453A1 publication Critical patent/FI20215453A1/en

Links

Classifications

    • 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/3236—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 using cryptographic hash functions
    • H04L9/3239—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 using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015—Name registration, generation or assignment
    • H04L61/302—Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or 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
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Bioethics (AREA)
  • General Engineering & Computer Science (AREA)
  • Primary Health Care (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The present application provides a blockchain-based decentralized domain name update system and method. The system includes a public chain and a subchain constituted by some of the nodes in the public chain. A root domain smart contract is configured in the node in the public chain. The node in the subchain is configured to: generate a sub domain smart contract through executing the root domain smart contract, and obtain ownership of the sub domain smart contract through contention; obtain a to-be-updated domain name (S101), determine a target domain smart contract for managing the to-be-updated domain name, and determine a target node having ownership of the target domain smart contract in the subchain (S102); and send a domain name update request to the target node (S103), so that the target node decides whether to accept the domain name update request. In the domain name update system provided in the present application, domain name update is free of being controlled by ICANN, which avoids a risk of being restricted and shielded by ICANN during domain name update in a DNS system, thereby improving cyber security of parties participating in and providing network services.

Description

BLOCKCHAIN-BASED DECENTRALIZED DOMAIN NAME UPDATE SYSTEM AND METHOD
[0001] The present application claims priority to Chinese Patent Application No.
201910845473.4, entitled "BLOCKCHAIN-BASED DECENTRALIZED DOMAIN NAME UPDATE SYSTEM AND METHOD", filed with the China National Intellectual Property Administration on September 6, 2019, which is incorporated herein by reference in its entirety.
TECHNICAL FIELD
[0002] The present application relates to a field of blockchain technologies, and in particular, to a blockchain-based decentralized domain name update system and method.
BACKGROUND OF THE INVENTION
[0003] A domain name is a name of a computer or a computer group on the Internet, which includes a string of names separated by dots, and is used to identify a geographic location of the computer during data transmission. The domain name may be classified into different levels, including a root domain, a top-level domain, and an application domain. Among them, the root domain is a node indicating a highest-level domain. For example, a domain name "." indicates a root domain. The top-level domain includes a national top-level domain and an N international top-level domain. For example, a domain name ".com." indicates a N top-level domain. The application domain name is a domain name below the S 25 top-level domain. For example, a domain name ".abc.com." or "www.abc.com." e indicates an application domain. E [0004] Domain name update often occurs in the Internet. As time goes by, a 2 demand of a service provider may change. Accordingly, a domain name needs to 5 be updated. In the prior art, service providers usually perform domain name O 30 update in a domain name system (Domain Name System, DNS). However, as a centralized system, the DNS system is essentially controlled by the Internet Corporation for Assigned Names and Numbers (ICANN) In other words, a process of domain name update is essentially controlled by ICANN. This method of centralized control by one organization violates a neutrality principle of the Internet. For each of parties participating in and providing network services, there is a risk of being restricted and shielded by ICANN, which affects cyber security of each of the parties participating in and providing network services.
[0005] Based on this, currently, there is an urgent need for a blockchain-based decentralized domain name update system and method, to resolve the problem in the prior art that there is a risk of being restricted and shielded by ICANN during domain name update in a DNS system, which affects cyber security of parties participating in and providing network services.
SUMMARY OF THE INVENTION
[0006] The present application provides a blockchain-based decentralized domain name update system and method, to resolve a technical problem in the prior art that there is a risk of being restricted and shielded by ICANN during domain name update in a DNS system, which affects cyber security of parties participating in and providing network services.
[0007] According to a first aspect, an embodiment of the present application provides a blockchain-based decentralized domain name update system, where the system includes a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain; a root domain smart contract is configured in the node in the public chain; and the node in the subchain is configured to: generate a sub domain smart contract through executing the root domain smart contract, and obtain ownership of the sub domain N 25 smart contract through contention; 5 the node in the subchain is further configured to: obtain a to-be-updated 2 domain name, determine a target domain smart contract for managing the > to-be-updated domain name, and determine a target node having ownership of the & target domain smart contract in the subchain; and send a domain name update O 30 request to the target node, where the domain name update request includes the = to-be-updated domain name; and the target node is configured to: check the domain name update request, decide whether to accept the domain name update request based on a check result, and update a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request.
[0008] Optionally, the sub domain smart contract includes a top-level domain smart contract and an application domain smart contract.
[0009] Optionally, the node in the subchain is further configured to: generate the top-level domain smart contract through executing the root domain smart contract, and/or generate the application domain smart contract through executing the top-level domain smart contract.
[0010] Optionally, the root domain smart contract is configured to manage a top-level domain, and the top-level domain smart contract is configured to manage an application domain.
[0011] Optionally, the node in the subchain is further configured to: obtain the to-be-updated domain name, and determine the target domain smart contract for managing the to-be-updated top-level domain to be the root domain smart contract if the to-be-updated domain name is a to-be-updated top-level domain; and check the domain name update request, decide whether to accept the domain name update reguest based on a check result, and update the top-level domain smart contract corresponding to the to-be-updated top-level domain if accepting the domain name update reguest.
[0012] Optionally, the node in the subchain is further configured to: obtain the —to-be-updated domain name, and if the to-be-updated domain name is a to-be-updated second-level domain, determine the target domain smart contract for managing the to-be-updated second-level domain to be the top-level domain smart contract, and determine the target node having ownership of the top-level domain smart contract in the subchain; and send the domain name update request N 25 to the target node, where the domain name update request includes the 5 to-be-updated second-level domain; and 2 the target node is further configured to: check the domain name update > request, decide whether to accept the domain name update request based on a & check result, and update the application domain smart contract corresponding to O 30 the to-be-updated second-level domain if accepting the domain name update = request.
[0013] Optionally, the node in the subchain is further configured to: obtain the to-be-updated domain name, and if the to-be-updated domain name is a to-be-updated third-level domain, determine the target domain smart contract for managing the to-be-updated third-level domain to be the application domain smart contract, and determine the target node having ownership of the application domain smart contract in the subchain; and send the domain name update request to the target node, where the domain name update request includes the to-be-updated third-level domain; and the target node is further configured to: check the domain name update request, decide whether to accept the domain name update request based on a check result, and update blockchain name system BNS data corresponding to the to-be-updated third-level domain if accepting the domain name update request.
[0014] Optionally, the target node is further configured to reject the domain name update request, and then update of the to-be-updated domain name fails.
[0015] Optionally, the node in the subchain is further configured to: obtain the to-be-updated domain name sent by an initiator node; and the initiator node is configured to: obtain the to-be-updated domain name offered by a service provider.
[0016] According to a second aspect, an embodiment of the present application provides a blockchain-based decentralized domain name update method, where the method is applicable to the system described above, and the system includes a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain; a root domain smart contract is configured in the node in the public chain; the node in the subchain is configured to: generate a sub domain smart contract through executing the root domain smart contract, and obtain ownership of the sub domain smart contract through contention; and the method includes: N 25 obtaining, by the node in the subchain, a to-be-updated domain name; 5 determining, by the node in the subchain, a target domain smart contract 2 for managing the to-be-updated domain name, and determining a target node - having ownership of the target domain smart contract in the subchain; & sending, by the node in the subchain, a domain name update reguest to O 30 the target node, where the domain name update reguest includes the = to-be-updated domain name; checking, by the target node, the domain name update request; and deciding, by the target node, whether to accept the domain name update request based on a check result, and updating a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request.
[0017] Optionally, the sub domain smart contract includes a top-level domain smart contract and an application domain smart contract.
[0018] Optionally, the root domain smart contract is configured to manage a 5 top-level domain, and the top-level domain smart contract is configured to manage an application domain.
[0019] Optionally, the determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name includes: determining, by the node in the subchain, the target domain smart contract for managing the to-be-updated top-level domain to be the root domain smart contract if the to-be-updated domain name is a to-be-updated top-level domain; and the method further includes: checking, by the node in the subchain, the domain name update request, deciding whether to accept the domain name update request based on a check result, and updating the top-level domain smart contract corresponding to the to-be-updated top-level domain if accepting the domain name update request.
[0020] Optionally, the determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name, and determining a target node having ownership of the target domain smart contract in the subchain includes: determining, by the node in the subchain, the target domain smart contract for managing the to-be-updated second-level domain to be the top-level domain smart contract if the to-be-updated domain name is a to-be-updated N 25 second-level domain, and determining the target node having ownership of the 5 top-level domain smart contract in the subchain; and 2 the deciding, by the target node, whether to accept the domain name > update request based on a check result, and updating a smart contract & corresponding to the to-be-updated domain name if accepting the domain name O 30 update request includes: = deciding, by the target node, whether to accept the domain name update request based on a check result, and updating the application domain smart contract corresponding to the to-be-updated second-level domain if accepting the domain name update request.
[0021] Optionally, the determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name, and determining a target node having ownership of the target domain smart contract in the subchain includes: determining, by the node in the subchain, the target domain smart contract for managing the to-be-updated third-level domain to be the application domain smart contract if the to-be-updated domain name is a to-be-updated third-level domain, and determining the target node having ownership of the application domain smart contract in the subchain; and the deciding, by the target node, whether to accept the domain name update request based on a check result, and updating a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request includes: deciding, by the target node, whether to accept the domain name update request based on a check result, and updating blockchain name system BNS data corresponding to the to-be-updated third-level domain if accepting the domain name update request.
[0022] Optionally, the method further includes: if the domain name update request is rejected, update of the —to-be-updated domain name fails.
[0023] Optionally, the obtaining, by the node in the subchain, a to-be-updated domain name includes: obtaining, by the node in the subchain, the to-be-updated domain name sent by an initiator node, where the initiator node is configured to obtain the N 25 —to-be-updated domain name offered by a service provider. 3 [0024] An embodiment of the present application further provides an apparatus. © The apparatus has a function of implementing the blockchain-based decentralized domain name update method described above. The function may be implemented & by hardware executing corresponding software. In a possible design, the O 30 apparatus includes: a processor, a transceiver, and a memory. The memory is = configured to store a computer-executable instruction. The transceiver is configured to implement communication between the apparatus and another communication entity. The processor is connected to the memory through a bus. When the apparatus runs, the processor executes the computer-executable instruction stored in the memory, so that the apparatus performs the blockchain-based decentralized domain name update method described above.
[0025] An embodiment of the present invention further provides a computer storage medium. A software program is stored in the storage medium. When read and executed by one or more processors, the software program implements the blockchain-based decentralized domain name update method described in the possible implementations.
[0026] An embodiment of the present invention further provides a computer program product including an instruction. When the instruction is run on a computer, the computer performs the blockchain-based decentralized domain name update method described in the possible implementations.
[0027] It can be learned from the foregoing technical solutions that the present application provides a blockchain-based decentralized domain name update system, including a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain. A root domain smart contract is configured in each of the nodes in the public chain. The node in the subchain is configured to: generate a sub domain smart contract through executing the root domain smart contract, and obtain ownership of the sub domain smart contract through contention; obtain a to-be-updated domain name, determine a target domain smart contract for managing the to-be-updated domain name, and determine a target node having ownership of the target domain smart contract in the subchain; and send a domain name update request to the target node, so that the target node checks the domain name update reguest, decides whether to accept the domain name update reguest based on a check result, and updates a N 25 smart contract corresponding to the to-be-updated domain name if accepting the 3 domain name update request. In the present application, a DNS system is © deployed in a blockchain network in a form of a subchain, to implement complete decentralized deployment. Compared with a prior DNS system, in the domain & name update system provided in the present application, domain name update is O 30 free of being controlled by ICANN, which avoids a risk of being restricted and = shielded by ICANN during domain name update in a DNS system, thereby improving cyber security of parties participating in and providing network services.
BRIEF DESCRIPTION OF THE DRAWINGS
[0028] FIG. 1 is a schematic structural diagram of a blockchain-based decentralized domain name update system according to an embodiment of the present application;
[0029] FIG. 2 is a schematic flowchart of domain name update by a domain name update system according to an embodiment of the present application;
[0030] FIG. 3 is a schematic diagram of a domain name update process for a top-level domain according to an embodiment of the present application;
[0031] FIG. 4 is a schematic diagram of a domain name update process for a second-level domain according to an embodiment of the present application;
[0032] FIG. 5 is a schematic diagram of a domain name update process for a third-level domain according to an embodiment of the present application; and
[0033] FIG. 6 is a schematic flowchart of a blockchain-based decentralized domain name update method according to an embodiment of the present application.
DETAILED DESCRIPTION OF THE EMBODIMENTS
[0034] In the technical solutions provided in the present application, a blockchain network is a point-to-point network of a decentralized application architecture. Inside the blockchain network, distributed storage, public consensus, digital encryption, and transaction accounting and verification can be performed. In other words, the blockchain network is a transaction platform that covers a distributed technology, cryptography, a P2P network architecture, and a variety of consensus algorithms that may be applied. N 25 [0035] In the present application, a blockchain or blockchain data is accounting 5 information generated based on transaction information when a transaction occurs 2 in the blockchain network. Specifically, a plurality of transactions constitute a block > data, and a plurality of block data constitute a blockchain with a timestamp. The & blockchain network includes nodes that establish a point-to-point network O 30 connection with one another. Each of the nodes is configured with a corresponding = consensus mechanism, for example, a smart contract of the nodes, and has a sufficient operating capability to perform transaction verification and accounting processes. The node further has a standardized interface specification, so as to access more nodes or other types of blockchain networks through the interface specification. A public chain is a point-to-point network structure constituted by a plurality of nodes in the blockchain network, where each of the nodes has a distributed storage function and a transaction and accounting function. The nodes on the public chain provide a uniform interface specification to the outside.
[0036] A possible system architecture to which an embodiment of the present application is applicable is described first with reference to FIG. 1 bellow.
[0037] For example, FIG. 1 is a schematic structural diagram of a blockchain-based decentralized domain name update system according to an embodiment of the present application. The system may include a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain. Obviously, in this embodiment, a node in the public chain may also be serve as a subchain node. Because the subchain is constituted by some of the nodes in the public chain, a node in the subchain is also a node in the public chain. In other words, the nodes constituting the subchain have the same smart contract and function as the nodes of the public chain.
[0038] In actual application, the public chain may provide basic blockchain services, for example, transactions, verification, and storage, in the network. The public chain itself may not have a specific function corresponding to any field, but acts as a bridge to bring together all subchains (or third-parties blockchain networks) connected to the public chain into a same blockchain network, so that transactions or information transfer may occur among different chains connected thereto.
[0039] In the technical solutions provided in the present application, a root domain smart contract is configured in each of the nodes in the public chain. The N 25 smart contract is a consensus mechanism program agreed based on a blockchain 5 transaction. Transaction operations of various functions can be implemented 2 through using the smart contract. In this embodiment of the present application, a - domain name update service may be completed by a node through executing the & root domain smart contract. O 30 [0040] The node in the subchain may be configured to: generate a sub domain = smart contract through executing the root domain smart contract, and obtain ownership of the sub domain smart contract through contention. After a subchain node obtains ownership of a sub domain smart contract, the subchain node may act as an owner of the sub domain smart contract. In other words, the sub domain smart contract is configured in the subchain node.
[0041] Because the node in the subchain has the same smart contract as the node in the public chain, the node in the subchain can directly execute the root domain smart contract to generate a sub domain smart contract. The sub domain smart contract includes a top-level domain smart contract, an application domain smart contract, and blockchain name system (Blockchain Name System, BNS) data.
[0042] In the blockchain name system, a domain name may be classified into a root domain, a top-level domain, and an application domain. Further, the application domain may be classified into a second-level domain, a third-level domain, a fourth-level domain, and the like. A complete domain name is constituted by two or more parts, and the parts are separated by periods ".", where the last "." is referred to as a root domain. A part on the right of the first "." from the last "." is referred to as a top-level domain (Top-Level Domain, TLD), or referred to as a first-level domain, including a valid character string and a domain suffix. A character string part from the left of the top-level domain to a next "." is referred to as a second-level domain (Second-Level Domain, SLD). A part on the left of the second-level domain is referred to as a third-level domain, and so on. Each level of domain controls assignment of a next-level domain.
[0043] In this embodiment of the present application, different smart contracts are provided for different levels of domains. A root domain may correspond to a root domain smart contract, where the root domain smart contract may be configured to manage and maintain a top-level domain, and generate a top-level domain smart contract. The top-level domain may correspond to the top-level N 25 domain smart contract, wherein the top-level domain smart contract may be 3 configured to manage and maintain an application domain (for example, manage a © second-level domain), and generate an application domain smart contract. The application domain may correspond to the application domain smart contract, & wherein the application domain smart contract may be configured to manage and O 30 maintain BNS data. The BNS data may include information on a third-level domain, = information on a fourth-level domain, and the like.
[0044] Further, the node in the subchain specifically may be configured to: generate the top-level domain smart contract through executing the root domain smart contract.
[0045] Alternatively, the node in the subchain specifically may be further configured to: generate the application domain smart contract through executing the top-level domain smart contract.
[0046] Domain name update is described in detail below based on the system architecture shown in FIG. 1 and the content described above.
[0047] For example, FIG. 2 is a schematic flowchart of domain name update by a domain name update system according to an embodiment of the present application.
[0048] As shown in FIG. 2, the node (for example, a node 1 shown in FIG. 2) in the subchain may be further configured to: obtain a to-be-updated domain name, determine a target domain smart contract for managing the to-be-updated domain name, and determine a target node (for example, a node 2 shown in FIG. 2) having ownership of the target domain smart contract in the subchain; and send a domain name update request to the target node. The domain name update request includes the to-be-updated domain name.
[0049] Correspondingly, the target node may be configured to: check the domain name update request, decide whether to accept the domain name update request based on a check result, and update a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request.
[0050] It can be learned from the foregoing technical solutions that the present application provides a blockchain-based decentralized domain name update system, including a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain. A root domain smart contract is configured in each of the nodes in the public chain. The node in the subchain is N 25 — configured to: generate a sub domain smart contract through executing the root 5 domain smart contract, and obtain ownership of the sub domain smart contract 2 through contention; obtain a to-be-updated domain name, determine a target > domain smart contract for managing the to-be-updated domain name, and & determine a target node having ownership of the target domain smart contract in O 30 the subchain; and send a domain name update request to the target node, so that = the target node checks the domain name update request, decides whether to accept the domain name update request based on a check result, and updates a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request. In the present application, a DNS system is deployed in a blockchain network in a form of a subchain, to implement complete decentralized deployment. Compared with a prior DNS system, in the domain name update system provided in the present application, domain name update is free of being controlled by ICANN, which avoids a risk of being restricted and shielded by ICANN during domain name update in a DNS system, thereby improving cyber security of parties participating in and providing network services.
[0051] It can be learned from the content shown in FIG. 2 that a transaction request received by the node (the node 1) in the subchain comes from a node O. The node O may be an initiator node for a current domain name update transaction. In other words, the node (for example, the node 1 shown in FIG. 2) in the subchain may be further configured to: obtain the to-be-updated domain name sent by the initiator node.
[0052] In this embodiment of the present application, a domain name update operation needs to be initiated by an owner corresponding to a to-be-updated domain name. In other words, the initiator node may be configured to: obtain the to-be-updated domain name offered by a service provider.
[0053] In an actual application environment, if an initiator node can perform a transaction or exchange information directly with the node in the subchain, the initiator node can send a to-be-updated domain name directly to the node in the subchain. In other words, the initiator node and the node in the subchain may be on a transaction in a same blockchain network, that is, the initiator node is also a node in the domain name update system.
[0054] Considering that the to-be-updated domain name in the present application may be different levels of domains, correspondingly, the target domain N 25 smart contract that can manage the to-be-updated domain name may vary. 5 Domain name update processes for different levels of to-be-updated domain 2 names are described in detail below through examples. > [0055] Example 1: & [0056] FIG. 3 is a schematic diagram of a domain name update process for a O 30 top-level domain according to an embodiment of the present application. The node = (for example, a node 1 shown in FIG. 3) in the subchain may be further configured to: obtain the to-be-updated domain name, and determine the target domain smart contract for managing the to-be-updated top-level domain to be the root domain smart contract if the to-be-updated domain name is a to-be-updated top-level domain; and check the domain name update request, decide whether to accept the domain name update request based on a check result, and update the top-level domain smart contract corresponding to the to-be-updated top-level domain if accepting the domain name update request.
[0057] According to a management relationship between a domain smart contract and a domain name, if the to-be-updated domain name is a to-be-updated top-level domain, obviously, the target domain smart contract for managing the to-be-updated top-level domain is the root domain smart contract. Since in the domain name update system provided in the embodiments of the present application, the root domain smart contract is configured in each of the nodes in the public chain, and the nodes in the subchain are constituted by some of the nodes in the public chain, that is to say, the root domain smart contract is also configured in each of the nodes in the subchain, the target node to be determined by the node in the subchain is actually the node in the subchain itself, and accordingly the node in the subchain may decide whether to accept an update request for the to-be-updated top-level domain.
[0058] Example 2:
[0059] FIG. 4 is a schematic diagram of a domain name update process for a second-level domain according to an embodiment of the present application. The node (for example, a node 1 shown in FIG. 4) in the subchain may be further configured to: obtain the to-be-updated domain name, and determine the target domain smart contract for managing the to-be-updated second-level domain to be the top-level domain smart contract if the to-be-updated domain name is a to-be-updated second-level domain, and determine the target node (for example, N 25 anode 2 shown in FIG. 4) having ownership of the top-level domain smart contract 5 in the subchain; and send the domain name update request to the target node. 2 The domain name update reguest includes the to-be-updated second-level > domain.
& [0060] Correspondingly, the target node (for example, the node 2 shown in FIG. O 30 4) may be further configured to: check the domain name update reguest, decide = whether to accept the domain name update request based on a check result, and update the application domain smart contract corresponding to the to-be-updated second-level domain if accepting the domain name update request.
[0061] Example 3:
[0062] FIG. 5 is a schematic diagram of a domain name update process for a third-level domain according to an embodiment of the present application. The node (for example, a node 1 shown in FIG. 5) in the subchain may be further configured to: obtain the to-be-updated domain name, and if the to-be-updated domain name is a to-be-updated third-level domain, determine the target domain smart contract for managing the to-be-updated third-level domain to be the application domain smart contract, and determine the target node (for example, a node 2 shown in FIG. 5) having ownership of the application domain smart contract in the subchain; and send the domain name update request to the target node. The domain name update request includes the to-be-updated third-level domain.
[0063] The target node (for example, the node 2 shown in FIG. 5) may be further configured to: check the domain name update request, decide whether to accept the domain name update request based on a check result, and update blockchain name system BNS data corresponding to the to-be-updated third-level domain if accepting the domain name update request.
[0064] It should be noted that, if the to-be-updated domain name is a fourth-level or higher-level domain, domain name update may be implemented also through using the method shown in FIG. 5. Description of details is omitted herein.
[0065] Based on a same invention concept, an embodiment of the present application further provides a blockchain-based decentralized domain name update method. FIG. 6 is a schematic flowchart of a blockchain-based decentralized domain name update method according to an embodiment of the S 25 present application. The method may be applied to the decentralized domain + name update system described above, and the system may include a public chain 2 constituted by a plurality of nodes and a subchain constituted by some of the > nodes in the public chain. The node in the public chain is configured with a root & domain smart contract. The node in the subchain is configured to: generate a sub O 30 domain smart contract through executing the root domain smart contract, and = obtain ownership of the sub domain smart contract through contention. The method may specifically include the following steps:
[0066] S101. Obtaining, by the node in the subchain, a to-be-updated domain name.
[0067] S102. Determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name, and determining a target node having ownership of the target domain smart contract in the subchain.
[0068] S103. Sending, by the node in the subchain, a domain name update request to the target node.
[0069] The domain name update request includes the to-be-updated domain name.
[0070] S4. Checking, by the target node, the domain name update request.
[0071] S5. Deciding, by the target node, whether to accept the domain name update request based on a check result, and updates a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request.
[0072] With the method, a DNS system is deployed in a blockchain network by a form of a subchain, to implement complete decentralized deployment. Compared — with a prior DNS system, in the domain name update method provided in the present application, domain name update is free of being controlled by ICANN, which avoids a risk of being restricted and shielded by ICANN during domain name update in a DNS system, thereby improving cyber security of parties participating in and providing network services.
[0073] The node in the subchain obtains a to-be-updated domain name; the node in the subchain determines a target domain smart contract for managing the to-be-updated domain name, and determines a target node having ownership of the target domain smart contract in the subchain; the node in the subchain sends a domain name update reguest to the N 25 target node, where the domain name update reguest includes the to-be-updated 5 domain name; 2 the target node checks the domain name update reguest; and > the target node decides whether to accept the domain name update & reguest based on a check result, and updates a smart contract corresponding to O 30 the to-be-updated domain name if accepting the domain name update request. = [0074] Optionally, the sub domain smart contract includes a top-level domain smart contract and an application domain smart contract.
[0075] Optionally, the root domain smart contract is configured to manage a top-level domain, and the top-level domain smart contract is configured to manage an application domain.
[0076] Optionally, the determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name includes: determining, by the node in the subchain, the target domain smart contract for managing the to-be-updated top-level domain to be the root domain smart contract if the to-be-updated domain name is a to-be-updated top-level domain; and the method further includes: checking, by the node in the subchain, the domain name update request, deciding whether to accept the domain name update request based on a check result, and updating the top-level domain smart contract corresponding to the to-be-updated top-level domain if accepting the domain name update request.
[0077] Optionally, the determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name, and determining a target node having ownership of the target domain smart contract in the subchain includes: determining, by the node in the subchain, the target domain smart contract for managing the to-be-updated second-level domain to be the top-level domain smart contract if the to-be-updated domain name is a to-be-updated second-level domain, and determining the target node having ownership of the top-level domain smart contract in the subchain; and the deciding, by the target node, whether to accept the domain name update request based on a check result, and updating a smart contract corresponding to the to-be-updated domain name if accepting the domain name S 25 update request includes: & deciding, by the target node, whether to accept the domain name update © request based on a check result, and updating the application domain smart - contract corresponding to the to-be-updated second-level domain if accepting the & domain name update reguest. O 30 [0078] Optionally, the determining, by the node in the subchain, a target domain = smart contract for managing the to-be-updated domain name, and determining a target node having ownership of the target domain smart contract in the subchain includes: determining, by the node in the subchain, the target domain smart contract for managing the to-be-updated third-level domain to be the application domain smart contract, and determining the target node having ownership of the application domain smart contract in the subchain if the to-be-updated domain name is a to-be-updated third-level domain; and the deciding, by the target node, whether to accept the domain name update request based on a check result, and updating a smart contract corresponding to the to-be-updated domain name if accepting the domain name update request includes: deciding, by the target node, whether to accept the domain name update request based on a check result, and updating blockchain name system BNS data corresponding to the to-be-updated third-level domain if accepting the domain name update request.
[0079] Optionally, the method further includes: if the domain name update request is rejected, update of the to-be-updated domain name fails.
[0080] Optionally, the obtaining, by the node in the subchain, a to-be-updated domain name includes: obtaining, by the node in the subchain, the to-be-updated domain name sent by an initiator node, where the initiator node is configured to obtain the to-be-updated domain name sent by a service provider.
[0081] In an exemplary embodiment, a computer-readable storage medium is further provided. A computer program or a smart contract is stored in the storage medium, and is loaded and executed by a node to implement the transaction processing method provided in the foregoing embodiments. Optionally, the S 25 computer-readable storage medium may be a read-only memory (Read-Only < Memory, ROM), a random access memory (Random Access Memory, RAM), a 2 CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, or the I like. & [0082] Persons skilled in the art may clearly understand that, the technologies in O 30 the embodiments of the present application may be implemented by software in = combination with a necessary general hardware platform. Based on such an understanding, the technical solutions in the embodiments of the present application essentially, or the part contributing to the prior art may be implemented in the form of a software product. The computer software product may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, or an optical disc, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in the embodiments of the present application.
[0083] Persons skilled in the art may readily figure out other implementation solutions of the present application by considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, purposes, or adaptations of the present application, which are in accordance with the general principle of the present application and include common general knowledge or conventional technical means in the art that are not disclosed in the present application. The specification and the embodiments are merely for an illustration purpose, and the true scope and spirit of the present application are subject to the following claims. It will be appreciated that the present application is not limited to the exact construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present application is subject to the appended claims.
N O
N <+ <Q
O
I a a
O
LO <t
LO N O N

Claims (10)

1. A blockchain-based decentralized domain name update system, comprising a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain, wherein the node in the public chain is configured with a root domain smart contract; and the node in the subchain is configured to: generate a sub domain smart contract through executing the root domain smart contract, and obtain ownership of the sub domain smart contract through contention; the node in the subchain is further configured to: obtain a to-be-updated domain name, determine a target domain smart contract for managing the to-be-updated domain name, and determine a target node having ownership of the target domain smart contract in the subchain; and send a domain name update request to the target node, wherein the domain name update request comprises the to-be-updated domain name; and the target node is configured to: check the domain name update request, decide whether to accept the domain name update request based on a check result, and update a smart contract corresponding to the to-be-updated domain name if accepting the domain name update reguest.
2. The system according to claim 1, wherein the sub domain smart contract comprises a top-level domain smart contract and an application domain smart contract.
3. The system according to claim 2, wherein the node in the subchain is S 25 further configured to: generate the top-level domain smart contract through + executing the root domain smart contract, and/or generate the application domain 2 smart contract through executing the top-level domain smart contract. z E 4. The system according to claim 3, wherein the root domain smart O 30 contract is configured to manage a top-level domain, and the top-level domain 5 smart contract is configured to manage an application domain.
N
5. The system according to claim 4, wherein the node in the subchain is further configured to: obtain the to-be-updated domain name, and determine the target domain smart contract for managing the to-be-updated top-level domain to be the root domain smart contract if the to-be-updated domain name is a to-be-updated top-level domain; and check the domain name update request, decide whether to accept the domain name update request based on a check result, and update the top-level domain smart contract corresponding to the to-be-updated top-level domain if accepting the domain name update reguest.
6. The system according to claim 4, wherein the node in the subchain is further configured to: obtain the to-be-updated domain name, determine the target domain smart contract for managing the to-be-updated second-level domain to be the top-level domain smart contract if the to-be-updated domain name is a to-be-updated second-level domain, and determine the target node having ownership of the top-level domain smart contract in the subchain; and send the domain name update request to the target node, wherein the domain name update request comprises the to-be-updated second-level domain; and the target node is further configured to: check the domain name update request, decide whether to accept the domain name update request based on a check result, and update the application domain smart contract corresponding to the to-be-updated second-level domain if accepting the domain name update request.
7. The system according to claim 4, wherein the node in the subchain is S 25 further configured to: obtain the to-be-updated domain name, determine the target + domain smart contract for managing the to-be-updated third-level domain to be the 2 application domain smart contract if the to-be-updated domain name is a > to-be-updated third-level domain, and determine the target node having ownership E of the application domain smart contract in the subchain; and send the domain O 30 name update request to the target node, wherein the domain name update request = comprises the to-be-updated third-level domain; and i the target node is further configured to: check the domain name update reguest, decide whether to accept the domain name update reguest based on a check result, and update blockchain name system BNS data corresponding to the to-be-updated third-level domain if accepting the domain name update request.
8. The system according to claim 1, wherein the target node is further configured that if the target node rejects the domain name update request, then update of the to-be-updated domain name fails.
9. The system according to any one of claims 1 to 8, wherein the node in the subchain is further configured to: obtain a to-be-updated domain name sent by an initiator node; and the initiator node is configured to: obtain the to-be-updated domain name offered by a service provider.
10. A blockchain-based decentralized domain name update method, wherein the method is applicable to the system according to any one of claims 1 to 9, and the system comprises a public chain constituted by a plurality of nodes and a subchain constituted by some of the nodes in the public chain; the node in the public chain is configured with a root domain smart contract; the node in the subchain is configured to: generate a sub domain smart contract through executing the root domain smart contract, and obtain ownership of the sub domain smart contract through contention; and the method comprises: obtaining, by the node in the subchain, a to-be-updated domain name; determining, by the node in the subchain, a target domain smart contract for managing the to-be-updated domain name, and determining a target node S 25 — having ownership of the target domain smart contract in the subchain; + sending, by the node in the subchain, a domain name update request to 2 the target node, wherein the domain name update request comprises the > to-be-updated domain name; E checking, by the target node, the domain name update reguest; and O 30 deciding, by the target node, whether to accept the domain name update = request based on a check result, and updating a smart contract corresponding to i the to-be-updated domain name if accepting the domain name update request.
FI20215453A 2019-09-06 2021-03-11 Blockchain-based decentralized domain name update system and method FI20215453A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910845473.4A CN112468605B (en) 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method
PCT/CN2020/094211 WO2021042787A1 (en) 2019-09-06 2020-06-03 Blockchain-based decentralized domain-name update system and method

Publications (1)

Publication Number Publication Date
FI20215453A1 true FI20215453A1 (en) 2021-04-16

Family

ID=74806981

Family Applications (1)

Application Number Title Priority Date Filing Date
FI20215453A FI20215453A1 (en) 2019-09-06 2021-03-11 Blockchain-based decentralized domain name update system and method

Country Status (4)

Country Link
CN (1) CN112468605B (en)
FI (1) FI20215453A1 (en)
FR (1) FR3100675A1 (en)
WO (1) WO2021042787A1 (en)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190166085A1 (en) * 2017-04-19 2019-05-30 Peking University Shenzhen Graduate School Blockchain-based domain name resolution system
EP3631659A4 (en) * 2017-05-22 2021-03-17 Haventec PTY LTD System for blockchain based domain name and ip number register
CN109995888B (en) * 2018-01-02 2021-11-09 中国移动通信有限公司研究院 Data updating method and network node of block chain Domain Name System (DNS) system
MX2019004666A (en) * 2018-11-30 2019-08-21 Alibaba Group Holding Ltd Blockchain smart contract updates using decentralized decision.
CN109672755B (en) * 2019-01-24 2021-10-22 中国互联网络信息中心 Domain name record updating method and system based on block chain
CN109889382B (en) * 2019-02-20 2020-07-21 中国互联网络信息中心 Domain name information maintenance system based on block chain hybrid consensus

Also Published As

Publication number Publication date
CN112468605B (en) 2023-08-08
CN112468605A (en) 2021-03-09
FR3100675A1 (en) 2021-03-12
WO2021042787A1 (en) 2021-03-11

Similar Documents

Publication Publication Date Title
US11995618B2 (en) Blockchain network interaction controller
CN109492380B (en) Equipment authentication method and device and block link point
US9294391B1 (en) Managing network computing components utilizing request routing
US11388083B2 (en) Secure route identification method and apparatus
TWI393400B (en) Method and system for authenticating a requestor without providing a key
US7051107B2 (en) Distributed environment type computer system able to achieve high speed consecutive message communications by service layer
CN110348242A (en) Service request processing method and device
CN109246211A (en) Resource uploading and resource requesting method in block chain
CN101218577A (en) Unified architecture for remote network access
KR101937188B1 (en) Method for managing information using merkle tree based on blockchain, server and terminal using the same
CN112468602B (en) Block chain-based decentralised domain name registration system and method
EP4049425B1 (en) Email security in a multi-tenant email service
CN112468525A (en) Domain name management system based on block chain
CN111885031B (en) Fine-grained access control method and system based on session process
US11522995B2 (en) Number management system, number management method, and number management device
FI20215453A1 (en) Blockchain-based decentralized domain name update system and method
CN108366136B (en) Domain name resolution method and device
CN109842554A (en) Method for routing, device, equipment and the storage medium of device service
CN112968915B (en) Processing method, processing system and processing device for DNS (Domain name Server) attack
CN112468603B (en) Domain name query system and method based on block chain
CN110290215B (en) Signal transmission method and device
CN113824738A (en) Method and system for node communication management in block chain
US20070195766A1 (en) Virtualized services system and method
CN111756678B (en) Information verification method, device and equipment
US20180375733A1 (en) Control method for application feature rules and application feature server

Legal Events

Date Code Title Description
FD Application lapsed