WO2021042785A1 - Système de gestion de nom de domaine fondé sur un contrat intelligent - Google Patents

Système de gestion de nom de domaine fondé sur un contrat intelligent Download PDF

Info

Publication number
WO2021042785A1
WO2021042785A1 PCT/CN2020/094209 CN2020094209W WO2021042785A1 WO 2021042785 A1 WO2021042785 A1 WO 2021042785A1 CN 2020094209 W CN2020094209 W CN 2020094209W WO 2021042785 A1 WO2021042785 A1 WO 2021042785A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
contract
nodes
level
node
Prior art date
Application number
PCT/CN2020/094209
Other languages
English (en)
Chinese (zh)
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 南京瑞祥信息技术有限公司
Priority to FI20215009A priority Critical patent/FI20215009A1/en
Publication of WO2021042785A1 publication Critical patent/WO2021042785A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • 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]
    • 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
    • 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/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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • 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/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • 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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names
    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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
    • 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/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • 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
    • 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/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories

Definitions

  • This application relates to the field of blockchain network technology, and in particular to a domain name management system based on smart contracts.
  • the domain name management system also known as the basic service of the Domain Name System (DNS, Domain Name System) Internet, provides the function of resolving domain names into real IP addresses, making network interconnection possible.
  • DNS Domain Name System
  • the root domain name server of DNS is controlled by ICANN, that is, DNS is a centralized multi-level system that violates the neutrality principle of the network.
  • ICANN ICANN
  • the main task of blockchain technology is to create a relatively objective non-repudiation digital environment in accordance with the requirements of the decentralized system and based on public consensus. Based on blockchain technology, the authenticity of network information can be guaranteed.
  • a decentralized domain name system can be built based on blockchain technology.
  • the blockchain-based domain name system (Blockchain Name System) adopts smart contract mechanisms or domain name protocol mechanisms to achieve a decentralized, open and scalable domain name system , Such as ENS based on Ethereum and Handshake based on UTXO model.
  • ENS reduces the complexity of the infrastructure by running on the dotted layer name system of the domain.
  • Handshake enables each participating node to verify and manage the root zone, so that the domain name resolution server will point to an authoritative server, thereby submitting the requirements to the blockchain network instead of certificate authorization mechanism.
  • This application provides a domain name management system based on smart contracts to solve the problem of slow response speed of the blockchain domain name system.
  • This application provides a domain name management system based on smart contracts, including a blockchain network composed of multiple nodes. Some of the nodes are equipped with smart contracts to form a domain name sub-chain network by executing the smart contracts to complete domain name services ;
  • the smart contract is a multi-level hierarchical structure, including root domain name contract, top-level domain name contract and application domain name contract;
  • the root domain name contract is configured in all nodes that make up the domain name sub-chain network, and some nodes in the domain name sub-chain network manage and maintain the top-level domain name contract by executing the root domain name contract;
  • the top-level domain name contract is configured in all nodes constituting the domain name sub-chain network, and the node configured with the top-level domain name contract manages and maintains the application domain name contract by executing the top-level domain name contract;
  • the application domain name contract is configured in all nodes that make up the domain name sub-chain network, and the node configured with the application domain name contract manages and maintains domain name data by executing the application domain name contract, and reports to the blockchain network Any node provides domain name data query function.
  • some nodes in the domain name sub-chain network execute the root domain name contract to create the top-level domain name contract, and configure the top-level domain name contract to all nodes in the domain name sub-chain network;
  • Part of the nodes configured with the top-level domain name contract creates the application domain name contract by executing the top-level domain name contract, and configures the application domain name contract to all nodes in the domain name sub-chain network.
  • all nodes in the domain name sub-chain network provide the top-level domain name contract routing by executing the root domain name contract;
  • the node configured with the top-level domain name contract provides the application domain name contract routing by executing the top-level domain name contract.
  • some nodes in the domain name sub-chain network execute the root domain name contract to generate and manage the top-level domain name contract;
  • the node where the root domain name contract is deployed is further configured to: receive a registration transaction, and initiate a voting transaction to a plurality of nodes where the root domain name contract is deployed according to the registration transaction;
  • the multiple nodes where the root domain name contract is deployed are further configured to return voting results according to the voting transaction, and accept or reject the newly added domain name corresponding to the registration transaction according to the statistical voting results.
  • the node where the root domain name contract is deployed is further configured to: generate a top-level domain name contract according to the registration transaction, and add record data corresponding to the registration transaction in the root domain name contract, and add the top-level domain name contract to The domain name contract and record data are entered into the sub-chain block.
  • some nodes in the domain name sub-chain network may be configured as storage nodes for storing the domain name data
  • the node configured with the smart contract receives the data query transaction by executing the corresponding smart contract, and obtains domain name information from the storage node according to the data query transaction.
  • application domain name data is cached
  • the node configured with the application domain name contract traverses the cached application domain name data according to the query transaction;
  • the node configured with the application domain name contract initiates the query transaction to the node configured with the top-level domain name contract.
  • the top-level domain name data is cached
  • the node configured with the top-level domain name contract traverses the cached top-level domain data according to the query transaction;
  • the node configured with the top-level domain name contract initiates the query transaction to the node that executes the root domain name contract.
  • the node configured with the application domain name contract is further configured to: receive an update transaction; and, according to the update transaction, execute the application domain name contract to update the domain name data.
  • the domain name sub-chain network includes at least one DNS node
  • the DNS node is configured with the root domain name contract, the top-level domain name contract, and the application domain name contract at the same time;
  • the DNS node is configured to interface with the DNS system, so that the nodes in the DNS system can query the domain name data in the domain name sub-chain through the DNS node; and, the nodes in the blockchain network pass the DNS node Query the domain name data in the DNS system.
  • this application provides a domain name management system based on smart contracts, including a blockchain network composed of multiple nodes.
  • some of the nodes are equipped with smart contracts to form a domain name sub-chain network by executing the smart contracts to complete domain name services;
  • the smart contracts have a multi-level hierarchical structure, including root domain name contracts, top-level domain name contracts, and applications Domain name contract;
  • nodes configured with smart contracts can implement a domain name management system based on the blockchain network by executing their own configured smart contract types, and realize the decentralization of the DNS system.
  • the domain name management system provided by this application can execute multi-level and hierarchical smart contracts through some nodes to complete the domain name management process synchronously, and improve the response speed of the blockchain domain name system.
  • Figure 1 is a schematic diagram of the application for a domain name management system based on smart contracts
  • Figure 2 is a schematic diagram of the multi-level hierarchical structure of the application smart contract
  • Figure 3 is a schematic diagram of the process of applying for a domain name management system to query a domain name
  • Figure 4 is a schematic diagram of the process of applying for domain name registration in the domain name management system
  • Figure 5 is a schematic diagram of the process of applying for domain name update of the domain name management system
  • Figure 6 is a schematic diagram of the structure of the domain name management system with DNS nodes in this application.
  • the blockchain network refers to a point-to-point network with a decentralized application architecture, and the blockchain network can perform distributed storage, public consensus, digital encryption, transaction accounting, and verification. That is, the blockchain network is a trading platform that covers distributed technology, cryptography, P2P network architecture, and various consensus algorithms that may be applied.
  • blockchain or blockchain data refers to the accounting information generated according to the transaction information when a transaction occurs in the blockchain network, that is, multiple transactions form one block of data, and multiple block data form one Blockchain with timestamp.
  • the blockchain network includes nodes that establish a peer-to-peer network connection with each other. Each node is equipped with a corresponding consensus mechanism, such as a smart contract, and has sufficient computing power to perform transaction verification and accounting procedures.
  • the node also has an interface specification that conforms to a certain unified standard to realize access to more nodes or other types of blockchain networks through the interface specification.
  • the public chain is a point-to-point network structure composed of multiple nodes in the blockchain network, and each node has a distributed storage function and transaction and accounting functions; the nodes on the public chain provide a unified interface specification to the outside.
  • the domain name management system based on smart contracts provided by this application includes a blockchain network composed of multiple nodes.
  • the blockchain network refers to a network established based on the principles of the blockchain, which may include a unified consensus mechanism, so that when a transaction occurs, the transaction can be verified and stored.
  • the blockchain network composed of multiple nodes in this application may be a public chain network constructed based on the principle of CNWW3 (ChainNetWork Web3.0).
  • some nodes may be based on the form of a public chain network.
  • Form various sub-chain networks to have different business functions.
  • the security, scalability and decentralization of the decentralized blockchain network are ensured, which greatly improves the processing of transactions per unit time on the network. Therefore, it can effectively support the transfer of traditional centralized applications to decentralized platforms, and complete the dual upgrade of business and technology.
  • the nodes are equipped with smart contracts to form a domain name sub-chain network by executing the smart contracts to complete the domain name service.
  • the smart contract is a consensus mechanism program based on blockchain transactions. Through smart contracts, various functional transaction operations can be realized. For example, through the root domain name smart contract, the node can complete domain name registration by executing the root domain name smart contract. , Query and update services.
  • the smart contract has a multi-level hierarchical structure, including a root domain name contract, a top-level domain name contract, and an application domain name contract.
  • the domain name resolution server will request the corresponding domain name information from the root domain name server.
  • the root domain name server does not directly return the corresponding domain name information to the domain name resolution server, but will forward the request to the corresponding top-level domain name server (TLD) based on the requested domain name information.
  • TLD domain name servers such as .com and .cn.
  • Each TLD server such as .com, .cn, etc., has a series of servers to provide corresponding query services. However, similar to the root domain name server, it does not actually correspond to the detailed information of the domain name. Instead, it acts as a proxy server that forwards the user's request to the authoritative domain name server corresponding to the domain name.
  • the TLD server will forward the request to the authoritative domain name server responsible for this specific domain based on the content of the request (such as second-level domain name information).
  • These authoritative name servers know all the information about the requested domain name, which is stored in their own DNS records.
  • the domain name resolution server obtains the information corresponding to the request from the authoritative domain name server, and caches it locally according to the TTL (Time-to-Live) of the information. Before the TTL expires, If there are other resolution requests for the same domain name, the cached information will be returned directly. At the same time, the domain name resolution server can also update the local cache information by repeating the steps (3), (4), (5) through the active refresh mechanism before the timeout.
  • TTL Time-to-Live
  • the root domain name contract is configured in all nodes that make up the domain name sub-chain network, and some nodes in the domain name sub-chain network manage and maintain the top-level domain name contract by executing the root domain name contract.
  • Domain name contract It can be seen that in this application, the root domain name contract is configured in all the nodes of the domain name sub-chain network, and some nodes complete the functions corresponding to the root domain name server by executing the root domain name smart contract.
  • the root domain name contract can also be used to manage and maintain the top-level domain name contract. It should be noted that the management and maintenance of the top-level domain name contract refers to the implementation of the root domain name contract.
  • the root domain name contract is the highest level, followed by the top-level domain name contract, and finally the application smart contract. Therefore, the top-level domain name contract is configured in all nodes that make up the domain name sub-chain network, and the node configured with the top-level domain name contract manages and maintains the application domain name contract by executing the top-level domain name contract; the application domain name contract It is configured in all nodes that make up the domain name sub-chain network, and the node configured with the application domain name contract manages and maintains domain name data by executing the application domain name contract, and provides domain name data to any node in the blockchain network Query function.
  • any node in the blockchain network can initiate a domain name query transaction to the domain name sub-chain network. After the domain name query transaction is initiated, the node that executes the application domain name contract first searches for the corresponding domain name in the query transaction. Data to complete the domain name query function. It should be noted that, according to the structure of the domain name data, the application domain name contract can be further divided into multiple levels in order to reduce the amount of query data.
  • some nodes in the domain name sub-chain network are configured as storage nodes for storing the domain name data.
  • all nodes in the domain name sub-chain network have data storage capabilities, but in this application, some nodes in the domain name sub-chain network can be configured as storage-only nodes according to the actual amount of data.
  • the storage capacity and data read and write capacity of this storage node are relatively strong.
  • the node configured with the smart contract executes the corresponding smart contract, receives data query transactions, and obtains domain name information from the storage node according to the data query transactions.
  • S101 Receive a query transaction sent by a domain name query node
  • S104 Send the extracted DNS information to the domain name query node.
  • the application domain name data is cached in the nodes configured with the application domain name contract. If the domain name information corresponding to the query transaction is not obtained in the cached application domain name data, the node configured with the application domain name contract initiates the query transaction to the node configured with the top-level domain name contract.
  • the node configured with the application domain name contract traverses the cached application domain name data according to the query transaction; the application domain name data is the next level of the top-level domain name, such as ".wikip edia. org" second-level domain name or third-level and fourth-level domain name information below the second level.
  • the domain name data includes other information. Take the third-level domain name related information as an example, including owner information, blockchain address, such as public key information, smart contract address or other addresses, TTL information, verification authentication information, or Store the storage address of the DNS root domain file in the IPFS network, etc.
  • the node configured with the top-level domain name contract has cached top-level domain data; the node configured with the top-level domain name contract, after receiving the query transaction, traverses the cached top-level domain data according to the query transaction; If the domain name information corresponding to the query transaction is not obtained in the cached top-level domain name data, the node configured with the top-level domain name contract initiates the query transaction to the node that executes the root domain name contract.
  • some nodes in the domain name sub-chain network provide the top-level domain name contract routing by executing the root domain name contract; the nodes configured with the top-level domain name contract execute The top-level domain name contract provides routing of the application domain name contract.
  • some nodes in the domain name sub-chain network execute the root domain name contract, create the top-level domain name contract, and configure the top-level domain name contract in the domain name sub-chain network
  • Part of the nodes configured with the top-level domain name contract executes the top-level domain name contract to create the application domain name contract, and configure the application domain name contract to all nodes in the domain name sub-chain network.
  • a node wants to have the ability to manage and maintain a top-level domain name contract, it needs to execute a root domain name smart contract, and in management and maintenance, create a top-level domain name contract and configure the top-level domain name contract to the node to be managed and maintained, thereby Deploy the subordinate relationship.
  • some nodes can create a top-level domain name contract by executing a root domain name contract, and some nodes can also create an application domain name contract by executing a top-level domain name contract, which can implement the deployment of new node roles and the registration of new domain names.
  • some nodes in the domain name sub-chain network execute the root domain name contract to generate and manage the top-level domain name contract.
  • the node deployed with the root domain name contract is further configured to: receive registration transactions, and initiate voting transactions to multiple nodes deployed with the root domain name contract according to the registration transaction; multiple nodes deployed with the root domain name contract
  • the node is further configured to: return a voting result according to the voting transaction, and accept or reject the newly added domain name corresponding to the registration transaction according to the statistical voting result.
  • the node where the root domain name contract is deployed is further configured to: generate a top-level domain name contract according to the registration transaction, and add record data corresponding to the registration transaction in the root domain name contract, and set the top-level domain name contract And record data into the sub-chain block.
  • domain name registration includes the following steps:
  • S201 Initiate a registration transaction to the root domain name smart contract to trigger the execution of the root domain name smart contract;
  • S202 According to the registration transaction, feedback a registration voting result by executing the root domain name smart contract, and the registration voting result includes accepting or rejecting the addition of the domain name in the registration transaction;
  • the node to be registered in the domain name management system can first initiate a registration transaction to the root domain name contract to trigger the root domain name contract to be executed by the corresponding node. After the node executes the root domain name contract, it can vote based on the registration transaction and feedback the voting result. When the feedback voting result meets the preset registration requirements, it indicates that the current server domain name can be registered in the system. Therefore, the top-level domain name contract can be generated through the root domain name contract, and a point to the newly generated top-level domain name contract can be added to the root domain name contract. The record of the domain name contract.
  • the preset registration requirements include that the feedback of registration voting results is that the number of accepted votes is greater than or equal to the value of the first vote; or, within the preset voting period, the feedback of registration voting results is that the number of accepted votes is greater than or equal to the second value. The value of the number of votes.
  • TLD top-level domain name service
  • the execution of the root domain name contract can be triggered by initiating a transaction to the root domain name contract; the owner of the root domain name contract can then decide through voting or other methods Whether to accept the addition of the TLD domain name; the root domain name contract owner, by initiating a transaction to the root domain name contract, choose to accept or reject the addition of the TLD domain name; if the registration is accepted, the new transaction is successful, and the root domain name contract is generated and deployed A new TLD contract, and a corresponding record is added to the root domain name contract at the same time, pointing to the new TLD contract to complete the new work.
  • the domain name management system needs to update the adjusted domain name information.
  • the node configured with the application domain name contract is further configured to: receive an update transaction; and, according to the update transaction, execute the application domain name contract to update the domain name data.
  • the update transaction includes the following steps:
  • S301 Initiate an update transaction to the upper-level domain name smart contract that executes the smart contract of the update node, and trigger the execution of the upper-level domain name smart contract to perform the update service;
  • S302 Verify the update data in the update transaction through the upper-level domain name smart contract; and, after the verification is passed, call the executed smart contract;
  • the contract owner node includes: the follower node that executes the root domain name contract, the top owner node that executes the top-level domain name contract, and the application owner node that executes the application domain name contract.
  • the upper-level domain name contract corresponding to the application owner node is the root domain name contract;
  • the upper-level domain name contract corresponding to the top-level owner node is the root domain name contract;
  • the upper-level domain name contract corresponding to the application owner node is the top-level domain name contract and/or Root domain name contract.
  • the owner of the TLD domain name that needs to be updated first calls the root domain name contract to update through transactions; then verifies the root domain name contract and passes the update to call the existing TLD contract , To update the corresponding information so that the TLD contract completes the corresponding update and returns the corresponding result; finally, the root domain name contract records the corresponding update result to complete the update operation.
  • the domain name management system based on smart contracts includes a blockchain network composed of multiple nodes.
  • some of the nodes are equipped with smart contracts to form a domain name sub-chain network by executing the smart contracts to complete domain name services;
  • the smart contracts have a multi-level hierarchical structure, including root domain name contracts, top-level domain name contracts, and applications Domain name contract;
  • nodes configured with smart contracts can implement a domain name management system based on the blockchain network by executing their own configured smart contract types, and realize the decentralization of the DNS system.
  • the domain name management system provided by this application can execute multi-level and hierarchical smart contracts through some nodes to complete the domain name management process synchronously, and improve the response speed of the blockchain domain name system.
  • this application can further optimize and adjust the public chain architecture, such as: node role division, node grouping, partition verification, etc. Since the domain name sub-chain network is composed of some nodes in the public chain, it can completely inherit the ability of the public chain, and also inherit the ability of the public chain to quickly verify and process high concurrent transactions.
  • the related smart contracts complete the registration, query, update and other operations of the domain name through transactions and transaction verification.
  • the standard blockchain network consensus algorithm guarantees the data of the entire network. consistency. Therefore, the high concurrency and fast transactions of the public chain network and its transaction verification capabilities can ensure that the domain name sub-chain network network also has corresponding capabilities, thereby effectively improving the lack of existing network performance.
  • the domain name management system based on the blockchain network can replace the traditional DNS system with its completely decentralized characteristics.
  • the blockchain network since the blockchain network is in the early stage of development, most of the network servers are registered In the traditional DNS system, therefore, in order to adapt to the characteristics of the current DNS and realize an effective transition, in some embodiments of the present application, as shown in FIG. 6, the domain name sub-chain network includes at least one DNS node.
  • the DNS node is transformed from a node in the traditional DNS system, so that it has both the traditional DNS network function and the current domain name sub-chain network function. Therefore, the DNS node is also configured with the root domain name contract, Top-level domain name contracts and application domain name contracts.
  • the DNS node is configured to connect to the DNS system, so that the nodes in the DNS system query the domain name data in the domain name sub-chain through the DNS node; and, the nodes in the blockchain network Query the domain name data in the DNS system through the DNS node.
  • the DNS system can be added to the domain name sub-chain network node in the form of one (or more) domain name sub-chain network nodes.
  • the DNS node can be the entire DNS system or a node in the DNS system, and the DNS system can interact with the outside world through this node. It can be seen that in this application, the DNS node has a DNS authoritative domain name server function, a domain name resolution server function, and a node having a domain name sub-chain network function to complete the two-way compatibility with the traditional DNS system.
  • the sub-domain name contract includes a top-level domain name contract and an application domain name contract; some of the nodes that make up the domain name sub-chain network and the DNS node are configured to: execute the top-level domain name contract. Domain name contract, complete top-level domain name services, including management and maintenance of second-level domain name information. Part of the nodes constituting the domain name sub-chain network and the DNS nodes are configured to complete application domain name services by executing the application domain name contract, including management and maintenance of domain name information above the second level.
  • DNS nodes can be set up to conveniently complete the query operation of the blockchain network domain name; at the same time, in the application of the blockchain network, if you need to access the network in the DNS system, The traditional DNS resolution work can be conveniently completed through the DNS nodes in the domain name sub-chain network.
  • the domain name sub-chain network in terms of phases, in the domain name sub-chain network, the current TLD top-level domain name registration in ICANN will not be opened, but through the DNS node and the IPFS of the blockchain public chain Network, the distributed mirroring service of the DNS system can be performed in the domain name sub-chain network, and the relevant DNS data can be backed up and stored, so as to avoid the problem of inaccessibility due to the failure of the DNS network.
  • the domain name sub-chain network can be used as an upgrade and replacement network of the existing DNS network. Whether it is a traditional DNS system or a blockchain-based domain name management system, the domain name sub-chain network can provide the corresponding service.

Landscapes

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

Abstract

La présente invention concerne un système de gestion de nom de domaine fondé sur un contrat intelligent et comprenant un réseau de chaînes de blocs constitué de multiples nœuds. Des contrats intelligents sont configurés dans certains des nœuds, de telle sorte qu'un réseau de sous-chaînes de nom de domaine est formé par exécution des contrats intelligents pour terminer un service de nom de domaine ; les contrats intelligents sont d'une structure hiérarchique multi-niveau et comprennent un contrat de nom de domaine racine, un contrat de nom de domaine de niveau supérieur et un contrat de nom de domaine d'application ; les nœuds, dans lesquels les contrats intelligents sont configurés, peuvent mettre en œuvre un système de gestion de nom de domaine fondé sur le réseau de chaîne de blocs en exécutant leurs propres types de contrats intelligents configurés, pour réaliser la décentralisation d'un système de nom de domaine (DNS). De plus, des processus tels que l'enregistrement, la demande et la mise à jour de nom de domaine sont réalisés par l'ouverture d'une transaction. Selon le système de gestion de nom de domaine fourni par la présente invention, certains des nœuds peuvent exécuter respectivement des contrats intelligents ayant une structure hiérarchique multi-niveau, pour terminer de manière synchrone un processus de gestion de nom de domaine, ce qui permet d'améliorer la vitesse de réponse d'un DNS à chaîne de blocs.
PCT/CN2020/094209 2019-09-06 2020-06-03 Système de gestion de nom de domaine fondé sur un contrat intelligent WO2021042785A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
FI20215009A FI20215009A1 (en) 2019-09-06 2020-06-03 Smart contract-based domain name management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910842956.9A CN112468309B (zh) 2019-09-06 2019-09-06 基于智能合约的域名管理系统
CN201910842956.9 2019-09-06

Publications (1)

Publication Number Publication Date
WO2021042785A1 true WO2021042785A1 (fr) 2021-03-11

Family

ID=74807212

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094209 WO2021042785A1 (fr) 2019-09-06 2020-06-03 Système de gestion de nom de domaine fondé sur un contrat intelligent

Country Status (4)

Country Link
CN (1) CN112468309B (fr)
FI (1) FI20215009A1 (fr)
FR (1) FR3100676B1 (fr)
WO (1) WO2021042785A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113438214A (zh) * 2021-06-10 2021-09-24 国网河北省电力有限公司信息通信分公司 一种域名管理系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113112140B (zh) * 2021-04-07 2022-04-19 中国电子科技网络信息安全有限公司 一种适应于区块链基础设施服务的链码应用智能合约id管理方法
CN113132384B (zh) * 2021-04-20 2022-04-19 哈尔滨工业大学 一种去中心化dns根区管理系统
CN113067836B (zh) * 2021-04-20 2022-04-19 哈尔滨工业大学 一种基于去中心化dns根区管理的智能合约系统
CN114697071A (zh) * 2022-01-27 2022-07-01 南京第三极区块链科技有限公司 一种基于区块链的分布式命名服务系统及其使用方法
CN115150246B (zh) * 2022-04-14 2023-06-30 北京邮电大学 基于新型嵌套链架构的面向海量实时物联网的上链方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108064444A (zh) * 2017-04-19 2018-05-22 北京大学深圳研究生院 一种基于区块链的域名解析系统
WO2018162789A1 (fr) * 2017-03-06 2018-09-13 Nokia Technologies Oy Système de nom de domaine décentralisé sécurisé
CN109919764A (zh) * 2019-01-31 2019-06-21 中国互联网络信息中心 基于区块链的域名交易监管方法及装置
CN110012126A (zh) * 2019-04-02 2019-07-12 哈尔滨工业大学（深圳） 一种基于区块链技术的dns系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170132621A1 (en) * 2015-11-06 2017-05-11 SWFL, Inc., d/b/a "Filament" Systems and methods for autonomous device transacting
CN106161674A (zh) * 2016-07-25 2016-11-23 宁圣金融信息服务（上海）有限公司 一种区块链域名解析装置
CN108833603A (zh) * 2018-05-28 2018-11-16 北京奇虎科技有限公司 一种基于区块链实现域名解析的方法、服务器和系统
CN109903159A (zh) * 2019-01-31 2019-06-18 中国互联网络信息中心 基于区块链的域名交易方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018162789A1 (fr) * 2017-03-06 2018-09-13 Nokia Technologies Oy Système de nom de domaine décentralisé sécurisé
CN108064444A (zh) * 2017-04-19 2018-05-22 北京大学深圳研究生院 一种基于区块链的域名解析系统
CN109919764A (zh) * 2019-01-31 2019-06-21 中国互联网络信息中心 基于区块链的域名交易监管方法及装置
CN110012126A (zh) * 2019-04-02 2019-07-12 哈尔滨工业大学（深圳） 一种基于区块链技术的dns系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113438214A (zh) * 2021-06-10 2021-09-24 国网河北省电力有限公司信息通信分公司 一种域名管理系统
CN113438214B (zh) * 2021-06-10 2023-04-18 国网河北省电力有限公司信息通信分公司 一种域名管理系统

Also Published As

Publication number Publication date
CN112468309B (zh) 2022-04-05
FR3100676A1 (fr) 2021-03-12
FI20215009A1 (en) 2021-03-07
CN112468309A (zh) 2021-03-09
FR3100676B1 (fr) 2022-06-10

Similar Documents

Publication Publication Date Title
WO2021042785A1 (fr) Système de gestion de nom de domaine fondé sur un contrat intelligent
US11657436B2 (en) Managing storage volume in a virtual computing infrastructure
WO2021042784A1 (fr) Système de gestion de noms de domaine utilisant une chaîne de blocs
CN108064444B (zh) 一种基于区块链的域名解析系统
WO2018176406A1 (fr) Procédé et système de gestion de noms de domaine de premier niveau basés sur une chaîne d'alliances
US20200007508A1 (en) On premises, remotely managed, host computers for virtual desktops
JP2008533564A (ja) データ管理のための方法および装置
WO2022067888A1 (fr) Procédé et dispositif basés sur une chaîne de gouvernance conjointe pour résolution de noms de domaines
CN111200642B (zh) 权威dns服务器信息分发方法及系统
WO2009015527A1 (fr) Système p2p et procédé servant à rechercher une ressource utilisée avec le système p2p
US7673143B1 (en) JXTA rendezvous as certificate of authority
CN111193816A (zh) 权威dns服务器信息更新方法及系统
US11558343B2 (en) Method and apparatus for resolving domain name based on co-governance chain
Xiong et al. LEA-DNS: DNS Resolution Validity and Timeliness Guarantee Local Authentication Extension with Public Blockchain
EP4256431A1 (fr) Gestion d'état et stockage avec application de politique dans un réseau informatique en nuage distribué
Zhao et al. Hierarchical P2P based RFID code resolution network: structure, tools and application
Wang Seamless transition of domain name system (DNS) authoritative servers
Deegan The Main Name System
Tri et al. Scalable and Self-configurable Eduroam by using Distributed Hash Table

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: 20859928

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: 20859928

Country of ref document: EP

Kind code of ref document: A1