CN112468602B - Block chain-based decentralised domain name registration system and method - Google Patents

Block chain-based decentralised domain name registration system and method Download PDF

Info

Publication number
CN112468602B
CN112468602B CN201910842298.3A CN201910842298A CN112468602B CN 112468602 B CN112468602 B CN 112468602B CN 201910842298 A CN201910842298 A CN 201910842298A CN 112468602 B CN112468602 B CN 112468602B
Authority
CN
China
Prior art keywords
domain name
registered
intelligent contract
chain
sub
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201910842298.3A
Other languages
Chinese (zh)
Other versions
CN112468602A (en
Inventor
白杰
李冬云
吴先锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aowei Co ltd
Original Assignee
Aowei 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 Aowei Co ltd filed Critical Aowei Co ltd
Priority to CN201910842298.3A priority Critical patent/CN112468602B/en
Priority to FI20215063A priority patent/FI20215063A1/en
Priority to PCT/CN2020/094210 priority patent/WO2021042786A1/en
Priority to FR2008784A priority patent/FR3100634B1/en
Publication of CN112468602A publication Critical patent/CN112468602A/en
Application granted granted Critical
Publication of CN112468602B publication Critical patent/CN112468602B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • 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]
    • 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—Systems or methods specially adapted for 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
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • 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/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
    • 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/3297—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps
    • 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

Landscapes

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

Abstract

The application provides a block chain-based decentralised domain name registration system and a block chain-based decentralised domain name registration method. The system comprises a public chain and a sub-chain consisting of partial nodes in the public chain. Wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the steps of obtaining a domain name to be registered, determining a target domain name intelligent contract for managing the domain name to be registered, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; after the domain name registration request is sent to the target node, the target node decides whether to accept the domain name registration request. The domain name registration system provided by the application is not controlled by the ICANN any more, and the risk that domain name registration in the DNS system is possibly limited and shielded by the ICANN is avoided, so that the network security of each party participating in and providing network services can be improved.

Description

Block chain-based decentralised domain name registration system and method
Technical Field
The application relates to the technical field of blockchains, in particular to a system and a method for registering a decentralised domain name based on a blockchain.
Background
A domain name is the name of a computer or group of computers on the internet consisting of a string of names separated by dots, which is used to identify the geographical location of the computer during data transmission. The domain names may be divided into different levels including root domain names, top-level domain names, and application domain names. Wherein the root domain name is the highest level domain name node, e.g., domain name "+" is the root domain name; the top-level domain name includes a national top-level domain name and an international top-level domain name, for example, the domain name ". Com." is a top-level domain name; an application domain name refers to a domain name below a top-level domain name, e.g. "abc.com." or "www.abc.com." in a domain name is an application domain name.
Domain name registration is a method used in the internet to solve address correspondence problems. In the prior art, registrants typically perform domain name registration in a domain name system (Domain Name System, DNS) system, but DNS systems are a centralized multi-level system that is essentially controlled by the internet name and number address assignment authority (The Internet Corporation for Assigned Names and Numbers, ICANN), that is, the domain name registration process is also essentially controlled by ICANN. This unified control by an organization violates the neutral principle of the internet, and there is a risk that parties participating in and providing network services may be limited and shielded by ICANN, thereby affecting the network security of parties participating in and providing network services.
Based on this, there is a need for a system and a method for decentralized domain name registration based on blockchain, which are used for solving the problem that in the prior art, domain name registration in a DNS system is possibly limited and shielded by ICANN, thereby affecting the network security of each party participating in and providing network services.
Disclosure of Invention
The application provides a block chain-based decentralization domain name registration system and a block chain-based decentralization domain name registration method, which can be used for solving the technical problem that in the prior art, domain name registration in a DNS system is possibly limited and shielded by ICANN, so that network security of all parties participating in and providing network services is affected.
In a first aspect, an embodiment of the present application provides a blockchain-based decentralised domain name registration system, the system including a public chain composed of a plurality of nodes, and a sub-chain composed of some nodes in the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner;
the nodes in the sub-chain are further configured to: acquiring a domain name to be registered, determining a target domain name intelligent contract for managing the domain name to be registered, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; sending a domain name registration request to the target node, wherein the domain name registration request comprises the domain name to be registered;
the target node is configured to: and determining whether to accept the domain name registration request, and if so, generating an intelligent contract corresponding to the domain name to be registered.
Optionally, the subdomain name intelligent contracts include a top-level domain name intelligent contract and an application domain name intelligent contract.
Optionally, the nodes in the sub-chain are further configured to: generating a top-level domain name intelligent contract by executing the root domain name intelligent contract, and/or generating an application domain name intelligent contract by executing the top-level domain name intelligent contract.
Optionally, the root domain name intelligent contract is used for managing a top-level domain name, and the top-level domain name intelligent contract is used for managing an application domain name.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be registered, and if the domain name to be registered is a top-level domain name to be registered, determining that a target domain name intelligent contract for managing the top-level domain name to be registered is a root domain name intelligent contract; determining whether to accept the registration request of the top-level domain name to be registered, and if so, generating a top-level domain name intelligent contract corresponding to the top-level domain name to be registered according to the root domain name intelligent contract.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be registered, if the domain name to be registered is a secondary domain name to be registered, determining that a target domain name intelligent contract for managing the secondary domain name to be registered is a top-level domain name intelligent contract, and determining a target node with ownership of the top-level domain name intelligent contract in a sub-chain; sending a domain name registration request to the target node, wherein the domain name registration request comprises the secondary domain name to be registered;
the target node is further configured to: and if the domain name registration request is accepted, generating an application domain name intelligent contract corresponding to the to-be-registered second-level domain name according to the top-level domain name intelligent contract.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be registered, if the domain name to be registered is a tertiary domain name to be registered, determining that a target domain name intelligent contract for managing the tertiary domain name to be registered is an application domain name intelligent contract, and determining a target node with ownership of the application domain name intelligent contract in a sub-chain; sending a domain name registration request to the target node, wherein the domain name registration request comprises the tertiary domain name to be registered;
the target node is further configured to: and if the domain name registration request is accepted, generating domain name system BNS data corresponding to the domain name to be registered according to the application domain name intelligent contract.
Optionally, the target node is further configured to: and if the domain name registration request is refused, the domain name registration to be registered fails.
Optionally, the nodes in the sub-chain are further configured to: and acquiring the domain name to be registered, which is sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
In a second aspect, an embodiment of the present application provides a method for decentralizing domain name registration based on a blockchain, where the method is applied to the system described above, and the system includes a public chain composed of a plurality of nodes, and a sub-chain composed of some nodes in the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the following steps:
the nodes in the sub-chain acquire domain names to be registered;
the nodes in the sub-chain determine a target domain name intelligent contract for managing the domain name to be registered, and determine target nodes in the sub-chain, which have ownership of the target domain name intelligent contract;
the node in the sub-chain sends a domain name registration request to the target node, wherein the domain name registration request comprises the domain name to be registered;
and the target node decides whether to accept the domain name registration request, and if so, generates an intelligent contract corresponding to the domain name to be registered.
Optionally, the subdomain name intelligent contracts include a top-level domain name intelligent contract and an application domain name intelligent contract.
Optionally, the root domain name intelligent contract is used for managing a top-level domain name, and the top-level domain name intelligent contract is used for managing an application domain name.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be registered, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be registered is a top-level domain name to be registered, determining that a target domain name intelligent contract for managing the top-level domain name to be registered is a root domain name intelligent contract by the nodes in the sub-chains;
the method further comprises the steps of:
and the nodes in the sub-chain determine whether to accept the registration request of the top-level domain name to be registered, and if the registration request of the top-level domain name to be registered is accepted, the top-level domain name intelligent contract corresponding to the top-level domain name to be registered is generated according to the root domain name intelligent contract.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be registered, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be registered is a secondary domain name to be registered, the node in the sub-chain determines that a target domain name intelligent contract for managing the secondary domain name to be registered is a top-level domain name intelligent contract, and determines a target node in the sub-chain, which has ownership of the top-level domain name intelligent contract;
the target node decides whether to accept the domain name registration request, and if so, generates an intelligent contract corresponding to the domain name to be registered, including:
and if the domain name registration request is accepted, the target node generates an application domain name intelligent contract corresponding to the to-be-registered secondary domain name according to the top-level domain name intelligent contract.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be registered, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be registered is a tertiary domain name to be registered, determining that a target domain name intelligent contract for managing the tertiary domain name to be registered is an application domain name intelligent contract by a node in the sub-chain, and determining that the target node in the sub-chain has ownership of the application domain name intelligent contract;
the target node decides whether to accept the domain name registration request, if so, generates an intelligent contract corresponding to the domain name to be registered, including
And if the domain name registration request is accepted, the target node generates BNS data corresponding to the domain name to be registered according to the application domain name intelligent contract.
Optionally, the method further comprises:
and if the domain name registration request is refused, the domain name registration to be registered fails.
Optionally, the obtaining, by the node in the sub-chain, the domain name to be registered includes:
and the node in the sub-chain acquires the domain name to be registered, which is sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
The embodiment of the application also provides a device with the function of realizing the block chain-based decentralization domain name registration method. The functions may be implemented by hardware executing corresponding software, and in one possible design, the apparatus comprises: a processor, transceiver, memory; the memory is used for storing computer-executable instructions, the transceiver is used for enabling the device to communicate with other communication entities, the processor is connected with the memory through the bus, and when the device runs, the processor executes the computer-executable instructions stored in the memory so that the device executes the block chain-based decentralization domain name registration method.
Embodiments of the present application also provide a computer storage medium having stored therein a software program that, when read and executed by one or more processors, implements the blockchain-based decentralised domain name registration method described in the various possible implementations described above.
Embodiments of the present application also provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the blockchain-based decentralised domain name registration method described in the various possible implementations described above.
As can be seen from the above technical scheme, the present application provides a block chain-based decentralised domain name registration system, comprising: a common chain composed of a plurality of nodes, and a sub-chain composed of partial nodes in the common chain. Wherein, all nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the steps of obtaining a domain name to be registered, determining a target domain name intelligent contract for managing the domain name to be registered, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; after the domain name registration request is sent to the target node, the target node decides whether to accept the domain name registration request, and if so, an intelligent contract corresponding to the domain name to be registered is generated. According to the application, the DNS system is deployed in the blockchain network in a form of the sub-chain, so that complete decentralization deployment can be realized. Compared with the prior DNS system, the domain name registration system provided by the application is not controlled by the ICANN any more, and the risk that domain name registration is limited and shielded by the ICANN in the DNS system is avoided, so that the network security of each party participating in and providing network services can be improved.
Drawings
FIG. 1 is a block chain based de-centralized domain name registration system architecture for use with embodiments of the present application;
fig. 2 is a schematic flow chart of domain name registration by a domain name registration system according to an embodiment of the present application;
fig. 3 is a schematic diagram of a domain name registration process of a top-level domain name according to an embodiment of the present application;
fig. 4 is a schematic diagram of a domain name registration process of a secondary domain name according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a domain name registration process for a three-level domain name according to an embodiment of the present application;
fig. 6 is a schematic flow diagram corresponding to a method for decentralizing domain name registration based on blockchain according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
In the technical scheme provided by the application, the blockchain network refers to a point-to-point network with a decentralised application architecture, and the blockchain network can perform distributed storage, public consensus, digital encryption, transaction accounting and verification inside the network. I.e., blockchain networks, are transaction platforms that cover distributed technology, cryptography, P2P network architecture, and various consensus algorithms that may be applied.
In the application, the blockchain or blockchain data refers to billing information generated according to transaction information when transactions occur in a blockchain network, namely, a plurality of transactions form one blockdata, and the blockdata form one blockchain with a time stamp. The blockchain network includes nodes that establish point-to-point network connections with each other, each configured with a corresponding consensus mechanism, such as a smart contract, and with sufficient computing power to perform transaction verification and accounting procedures. The nodes also have interface specifications thereon that conform to a unified standard to enable access to more nodes or other types of blockchain networks via the interface specifications. The public chain is a point-to-point network structure formed by a plurality of nodes in the blockchain network, and each node has a distributed storage function and a transaction and accounting function; the nodes on the public chain provide unified interface specifications to the outside.
A possible system architecture to which the embodiment of the present application is applicable will be described first with reference to fig. 1.
Referring to fig. 1, a schematic diagram of a block chain-based decentralised domain name registration system is shown for use in an embodiment of the present application. The system may include: a common chain composed of a plurality of nodes, and a sub-chain composed of a part of the nodes in the common chain. Obviously, in this embodiment, the nodes in the common chain may also be used as child link points at the same time. And the nodes in the sub-chain are composed of partial nodes in the common chain, so that the nodes are both the nodes in the sub-chain and the nodes in the common chain. That is, the nodes that make up the child chain have the same intelligent contracts and functions as the nodes of the public chain.
In practice, the public chain may provide basic blockchain services in the network, such as transaction, authentication, storage, etc. The public chain itself may not have any specific function corresponding to the field, but rather serves as a bridge to aggregate all sub-chains (or third party blockchain networks) accessing the public chain into the same blockchain network, so that different access chains may trade or transfer information with each other.
In the technical scheme provided by the application, the nodes in the public chain are all configured with root domain name intelligent contracts. The intelligent contract is a consensus mechanism program agreed based on blockchain transaction, and transaction operation of various functions can be realized through the intelligent contract. In the embodiment of the application, through the root domain name intelligent contract, the node can complete domain name registration service by executing the root domain name intelligent contract.
The nodes in the sub-chain may be configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner. After a certain sub-link node obtains ownership of the sub-domain name intelligent contract, the sub-link node can serve as an owner of the sub-domain name intelligent contract, that is, the sub-link node is configured with the sub-domain name intelligent contract.
Since the nodes constituting the sub-chain have the same intelligent contracts as the nodes of the public chain, the nodes in the sub-chain can directly execute the root domain name intelligent contracts, thereby generating sub-domain name intelligent contracts. Wherein the subdomain name intelligence contracts include a top-level domain name intelligence contract, an application domain name intelligence contract, and domain name system (Blockchain Name System, BNS) data.
In the domain name system, domain names can be divided into root domain names, top-level domain names, and application domain names. Further, the application domain name can be further divided into a secondary domain name, a tertiary domain name, a quaternary domain name and the like. A complete domain name consists of two or more parts, each part is separated by English periods "," at the end of which is called root domain name; the right part of the penultimate "," is called the Top Level Domain (TLD), also called the primary Domain, containing a legal string, and a Domain suffix; the left part string of the top-level domain name is called the second-level domain name (Second Level Domain, SLD) until the next "; the left portion of the secondary domain name is referred to as the tertiary domain name, and so on, the domain name of each stage controls the assignment of its next-stage domain name.
In the embodiment of the application, different intelligent contracts are provided for domain names of different levels. The root domain name may correspond to a root domain name intelligence contract, which may be used to manage and maintain a top-level domain name, and to generate a top-level domain name intelligence contract; the top-level domain name may correspond to a top-level domain name intelligence contract that may be used to manage and maintain the application domain name (e.g., manage the second-level domain name), and to generate the application domain name intelligence contract; the application domain name may correspond to an application domain name intelligent contract, which may be used to manage and maintain BNS data; the BNS data can include information related to a tertiary domain name, information related to a quaternary domain name, and the like.
Further, the nodes in the sub-chain may be specifically configured to: a top-level domain name intelligent contract is generated by executing the root domain name intelligent contract.
Alternatively, the nodes in the sub-chain may in particular be further configured to: an application domain name intelligence contract is generated by executing a top-level domain name intelligence contract.
Based on the system architecture shown in fig. 1 and described above, the case of domain name registration is described in detail below.
Fig. 2 is a schematic flow chart of domain name registration by a domain name registration system according to an embodiment of the present application.
As shown in fig. 2, the nodes in the sub-chain (e.g., node 1 shown in fig. 2) may be further configured to: acquiring a domain name to be registered, determining a target domain name intelligent contract for managing the domain name to be registered, and determining a target node (such as node 2 shown in fig. 2) with ownership of the target domain name intelligent contract in a sub-chain; and sending a domain name registration request to the target node. Wherein the domain name registration request may include a domain name to be registered.
Accordingly, the target node may be configured to: determining whether to accept the domain name registration request, and if so, generating an intelligent contract corresponding to the domain name to be registered; if the domain name registration request is rejected, the domain name to be registered fails to register.
Further, after the target node generates the intelligent contract corresponding to the domain name to be registered, the node in the sub-chain can still acquire the ownership of the intelligent contract corresponding to the domain name to be registered in a competitive manner; meanwhile, the target node can also newly add a record of the domain name to be registered in the target domain name intelligent contract, and point to the intelligent contract corresponding to the domain name to be registered, thereby completing domain name registration.
As can be seen from the above technical scheme, the present application provides a block chain-based decentralised domain name registration system, comprising: a common chain composed of a plurality of nodes, and a sub-chain composed of partial nodes in the common chain. Wherein, all nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the steps of obtaining a domain name to be registered, determining a target domain name intelligent contract for managing the domain name to be registered, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; after the domain name registration request is sent to the target node, the target node decides whether to accept the domain name registration request, and if so, an intelligent contract corresponding to the domain name to be registered is generated. According to the application, the DNS system is deployed in the blockchain network in a form of the sub-chain, so that complete decentralization deployment can be realized. Compared with the prior DNS system, the domain name registration system provided by the application is not controlled by the ICANN any more, and the risk that domain name registration is limited and shielded by the ICANN in the DNS system is avoided, so that the network security of each party participating in and providing network services can be improved.
From what is shown in fig. 2, it can be seen that the transaction request received by the node in the sub-chain (i.e., node 1) originates from node 0. Node 0 may be the initiating node of the domain name registration transaction or a neighboring node of the node in the sub-chain (i.e., node 1). That is, the nodes in the sub-chain (e.g., node 1 shown in fig. 2) may be further configured to: and acquiring the domain name to be registered, which is sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
The transaction form between the initiating node and the nodes in the sub-chain is different according to the actual application environment. The nodes in the sub-chain may acquire the domain name to be registered sent by the initiating node in the following two cases.
One situation is that if the initiating node can directly transact or interact with a node in the sub-chain, the domain name to be registered can be sent to the node in the sub-chain directly through the initiating node. This approach is best suited for transactions where the initiating node is in the same blockchain network as the nodes in the sub-chain, i.e., the initiating node is also a node in the domain name registration system.
Alternatively, if the initiating node cannot directly transact or interact with a node in the sub-chain, the domain name to be registered may be broadcast by the initiating node. Specifically, the domain name to be registered may be broadcast to the neighboring node, and then the neighboring node determines whether to receive the domain name to be registered or continue broadcasting until the node in the sub-chain receives the domain name to be registered in combination with its role.
The situation that the node in the sub-chain receives the domain name to be registered sent by the adjacent node of the node in the sub-chain corresponds to the situation that the transaction initiating node is not aware of the position information of the core node, the domain name to be registered is sent in the blockchain in a broadcast mode, and thus, along with information diffusion, the core node can receive the domain name to be registered through the adjacent node.
It should be noted that the above two cases are only illustrative, and in other possible examples, if the originating node is a node adjacent to a node in the sub-chain, the node in the sub-chain may also be regarded as directly receiving the domain name to be registered sent by the originating node.
In consideration of the fact that the domain name to be registered can be different levels of domain names in the method, the intelligent contracts of the target domain names capable of managing the domain name to be registered are correspondingly different. The domain name registration flow of the domain name to be registered at different levels is described in detail below by way of example.
Example one:
fig. 3 is a schematic diagram of a domain name registration process of a top-level domain name according to an embodiment of the present application. The nodes in the sub-chain (e.g., node 1 shown in fig. 3) may be further configured to: acquiring a domain name to be registered, and if the domain name to be registered is a top-level domain name to be registered, determining that a target domain name intelligent contract for managing the top-level domain name to be registered is a root domain name intelligent contract; determining whether to accept the registration request of the top-level domain name to be registered, and if so, generating a top-level domain name intelligent contract corresponding to the top-level domain name to be registered according to the root domain name intelligent contract.
According to the management and managed relation between the domain name intelligent contract and the domain name, if the domain name to be registered is the top-level domain name to be registered, it is obvious that the target domain name intelligent contract for managing the top-level domain name to be registered is the root domain name intelligent contract; in the domain name registration system provided by the embodiment of the application, the nodes in the public chain are all configured with root domain name intelligent contracts, and the nodes in the sub-chain are composed of partial nodes in the public chain, that is, the nodes in the sub-chain are also configured with root domain name intelligent contracts; therefore, the target node to be determined by the node in the sub-chain is itself, and further, the node in the sub-chain may decide whether to accept the registration request of the top-level domain name to be registered.
Example two:
fig. 4 is a schematic diagram of a domain name registration process of a secondary domain name according to an embodiment of the present application. The nodes in the sub-chain (e.g., node 1 shown in fig. 4) may be further configured to: acquiring a domain name to be registered, if the domain name to be registered is a secondary domain name to be registered, determining that a target domain name intelligent contract for managing the secondary domain name to be registered is a top-level domain name intelligent contract, and determining a target node (such as node 2 shown in fig. 4) having ownership of the top-level domain name intelligent contract in a sub-chain; and sending a domain name registration request to the target node. Wherein the domain name registration request may include the secondary domain name to be registered.
Accordingly, the target node may be further configured to: and if the domain name registration request is accepted, generating an application domain name intelligent contract corresponding to the to-be-registered second-level domain name according to the top-level domain name intelligent contract.
Example three:
fig. 5 is a schematic diagram of a domain name registration process of a three-level domain name according to an embodiment of the present application. The nodes in the sub-chain (e.g., node 1 shown in fig. 5) may be further configured to: acquiring a domain name to be registered, if the domain name to be registered is a tertiary domain name to be registered, determining that a target domain name intelligent contract for managing the tertiary domain name to be registered is an application domain name intelligent contract, and determining a target node (such as node 2 shown in fig. 5) having ownership of the application domain name intelligent contract in a sub-chain; and sending a domain name registration request to the target node. Wherein the domain name registration request may include the tertiary domain name to be registered.
Accordingly, the target node may be further configured to: and if the domain name registration request is accepted, generating BNS data corresponding to the three-level domain name to be registered according to the intelligent contract of the application domain name.
It should be noted that, if the domain name to be registered is a domain name of four or more levels, the domain name registration may be implemented by the method shown in fig. 5, and will not be described in detail herein.
Based on the same inventive concept, the embodiment of the application also provides a block chain-based decentralization domain name registration method. Fig. 6 is a schematic flow diagram corresponding to a method for decentralizing domain name registration based on blockchain according to an embodiment of the present application. The method may be applied to the decentralized domain name registration system described above, which may include a common chain consisting of a plurality of nodes, and a sub-chain consisting of some of the nodes in the common chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method specifically comprises the following steps:
step 101, the node in the sub-chain acquires the domain name to be registered.
Step 102, determining a target domain name intelligent contract for managing the domain name to be registered by the nodes in the sub-chain, and determining a target node having ownership of the target domain name intelligent contract in the sub-chain.
And step 103, the nodes in the sub-chain send domain name registration requests to the target node.
Wherein the domain name registration request includes the domain name to be registered.
Step 104, the target node decides whether to accept the domain name registration request, if so, the intelligent contract corresponding to the domain name to be registered is generated.
By adopting the method, the DNS system is deployed in the blockchain network in the form of the sub-chain, so that complete decentralization deployment can be realized. Compared with the prior DNS system, the domain name registration method provided by the application is not controlled by the ICANN any more, and avoids the risk that domain name registration in the DNS system is possibly limited and shielded by the ICANN, thereby improving the network security of all parties participating in and providing network services.
Optionally, the subdomain name intelligent contracts include a top-level domain name intelligent contract and an application domain name intelligent contract.
Optionally, the root domain name intelligent contract is used for managing a top-level domain name, and the top-level domain name intelligent contract is used for managing an application domain name.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be registered, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be registered is a top-level domain name to be registered, determining that a target domain name intelligent contract for managing the top-level domain name to be registered is a root domain name intelligent contract by the nodes in the sub-chains;
the method further comprises the steps of:
and the nodes in the sub-chain determine whether to accept the registration request of the top-level domain name to be registered, and if the registration request of the top-level domain name to be registered is accepted, the top-level domain name intelligent contract corresponding to the top-level domain name to be registered is generated according to the root domain name intelligent contract.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be registered, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be registered is a secondary domain name to be registered, the node in the sub-chain determines that a target domain name intelligent contract for managing the secondary domain name to be registered is a top-level domain name intelligent contract, and determines a target node in the sub-chain, which has ownership of the top-level domain name intelligent contract;
the target node decides whether to accept the domain name registration request, and if so, generates an intelligent contract corresponding to the domain name to be registered, including:
and if the domain name registration request is accepted, the target node generates an application domain name intelligent contract corresponding to the to-be-registered secondary domain name according to the top-level domain name intelligent contract.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be registered, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be registered is a tertiary domain name to be registered, determining that a target domain name intelligent contract for managing the tertiary domain name to be registered is an application domain name intelligent contract by a node in the sub-chain, and determining that the target node in the sub-chain has ownership of the application domain name intelligent contract;
the target node decides whether to accept the domain name registration request, if so, generates an intelligent contract corresponding to the domain name to be registered, including
And if the domain name registration request is accepted, the target node generates BNS data corresponding to the domain name to be registered according to the application domain name intelligent contract.
Optionally, the method further comprises:
and if the domain name registration request is refused, the domain name registration to be registered fails.
Optionally, the obtaining, by the node in the sub-chain, the domain name to be registered includes:
and the node in the sub-chain acquires the domain name to be registered, which is sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
In an exemplary embodiment, there is also provided a computer-readable storage medium having stored therein a computer program or a smart contract that is loaded and executed by a node to implement the transaction method provided by the above embodiment. Alternatively, the above-mentioned computer readable storage medium may be a Read-Only Memory (ROM), a random-access Memory (Random Access Memory, RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, or the like.
It will be apparent to those skilled in the art that the techniques of embodiments of the present application may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present application may be embodied in essence or what contributes to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (7)

1. A blockchain-based decentralised domain name registration system, the system comprising a public chain of a plurality of nodes, and a sub-chain of partial nodes of the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner;
the nodes in the sub-chain are further configured to: acquiring a domain name to be registered;
if the domain name to be registered is a top-level domain name to be registered, determining that a target domain name intelligent contract for managing the top-level domain name to be registered is a root domain name intelligent contract; determining whether to accept the registration request of the top-level domain name to be registered, and if so, generating a top-level domain name intelligent contract corresponding to the top-level domain name to be registered according to the root domain name intelligent contract;
if the domain name to be registered is a secondary domain name to be registered, determining that a target domain name intelligent contract for managing the secondary domain name to be registered is a top-level domain name intelligent contract, and determining a target node with ownership of the top-level domain name intelligent contract in a sub-chain; sending a domain name registration request to the target node, wherein the domain name registration request comprises the secondary domain name to be registered; the target node is further configured to: if the domain name registration request is accepted, generating an application domain name intelligent contract corresponding to the to-be-registered second-level domain name according to the top-level domain name intelligent contract;
if the domain name to be registered is a tertiary domain name to be registered, determining that a target domain name intelligent contract for managing the tertiary domain name to be registered is an application domain name intelligent contract, and determining a target node with ownership of the application domain name intelligent contract in a sub-chain; sending a domain name registration request to the target node, wherein the domain name registration request comprises the tertiary domain name to be registered; the target node is further configured to: and if the domain name registration request is accepted, generating domain name system BNS data corresponding to the domain name to be registered according to the application domain name intelligent contract.
2. The system of claim 1, wherein the sub-domain name intelligence contracts include a top-level domain name intelligence contract and an application domain name intelligence contract.
3. The system of claim 2, wherein the nodes in the sub-chain are further configured to: generating a top-level domain name intelligent contract by executing the root domain name intelligent contract, and/or generating an application domain name intelligent contract by executing the top-level domain name intelligent contract.
4. The system of claim 3, wherein the root domain name intelligence contract is for managing top-level domain names, and wherein the top-level domain name intelligence contract is for managing application domain names.
5. The system of claim 1, wherein the target node is further configured to: and if the domain name registration request is refused, the domain name registration to be registered fails.
6. The system of any of claims 1-4, wherein the nodes in the sub-chain are further configured to: and acquiring the domain name to be registered, which is sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
7. A method of decentralised domain name registration based on blockchain, characterized in that it is applied to the system of any of the preceding claims 1 to 6, comprising a public chain consisting of a plurality of nodes, and a sub-chain consisting of some nodes of the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the following steps:
the nodes in the sub-chain acquire domain names to be registered;
if the domain name to be registered is a top-level domain name to be registered, determining that a target domain name intelligent contract for managing the top-level domain name to be registered is a root domain name intelligent contract by the nodes in the sub-chains; determining whether to accept the registration request of the top-level domain name to be registered, and if so, generating a top-level domain name intelligent contract corresponding to the top-level domain name to be registered according to the root domain name intelligent contract;
if the domain name to be registered is a secondary domain name to be registered, the node in the sub-chain determines that a target domain name intelligent contract for managing the secondary domain name to be registered is a top-level domain name intelligent contract, and determines a target node in the sub-chain, which has ownership of the top-level domain name intelligent contract; sending a domain name registration request to the target node, wherein the domain name registration request comprises the secondary domain name to be registered; if the target node receives the domain name registration request, generating an application domain name intelligent contract corresponding to the to-be-registered secondary domain name according to the top-level domain name intelligent contract;
if the domain name to be registered is a tertiary domain name to be registered, determining that a target domain name intelligent contract for managing the tertiary domain name to be registered is an application domain name intelligent contract by a node in the sub-chain, and determining that the target node in the sub-chain has ownership of the application domain name intelligent contract; sending a domain name registration request to the target node, wherein the domain name registration request comprises the tertiary domain name to be registered; and if the target node receives the domain name registration request, generating domain name system BNS data corresponding to the domain name to be registered according to the application domain name intelligent contract.
CN201910842298.3A 2019-09-06 2019-09-06 Block chain-based decentralised domain name registration system and method Active CN112468602B (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201910842298.3A CN112468602B (en) 2019-09-06 2019-09-06 Block chain-based decentralised domain name registration system and method
FI20215063A FI20215063A1 (en) 2019-09-06 2020-06-03 Blockchain-based decentralized domain name registration system and method
PCT/CN2020/094210 WO2021042786A1 (en) 2019-09-06 2020-06-03 Decentralized domain name registration system and method based on blockchain
FR2008784A FR3100634B1 (en) 2019-09-06 2020-08-28 SYSTEM AND METHOD FOR DECENTRALIZED DOMAIN NAME REGISTRATION BASED ON BLOCKCHAIN

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910842298.3A CN112468602B (en) 2019-09-06 2019-09-06 Block chain-based decentralised domain name registration system and method

Publications (2)

Publication Number Publication Date
CN112468602A CN112468602A (en) 2021-03-09
CN112468602B true CN112468602B (en) 2023-09-22

Family

ID=74807126

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910842298.3A Active CN112468602B (en) 2019-09-06 2019-09-06 Block chain-based decentralised domain name registration system and method

Country Status (4)

Country Link
CN (1) CN112468602B (en)
FI (1) FI20215063A1 (en)
FR (1) FR3100634B1 (en)
WO (1) WO2021042786A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113067836B (en) * 2021-04-20 2022-04-19 哈尔滨工业大学 Intelligent contract system based on decentralized DNS root zone management
CN113132384B (en) * 2021-04-20 2022-04-19 哈尔滨工业大学 Decentralized DNS root zone management system
CN113422767B (en) * 2021-06-21 2022-04-19 哈尔滨工业大学 Domain name registration management method and system based on block chain

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109672755A (en) * 2019-01-24 2019-04-23 中国互联网络信息中心 A kind of domain name record update method and system based on block chain
CN109756589A (en) * 2019-02-20 2019-05-14 中国互联网络信息中心 A kind of domain-name information maintenance system controlled altogether in many ways based on block chain
CN109819443A (en) * 2018-12-29 2019-05-28 东莞见达信息技术有限公司 Authentication registration method, apparatus and system based on block chain
CN110012126A (en) * 2019-04-02 2019-07-12 哈尔滨工业大学（深圳） A kind of DNS system based on block chain technology

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10230526B2 (en) * 2014-12-31 2019-03-12 William Manning Out-of-band validation of domain name system records
CN106796688B (en) * 2016-12-26 2020-12-18 深圳前海达闼云端智能科技有限公司 Permission control method, device and system of block chain and node equipment
CN108124502B (en) * 2017-03-31 2021-01-05 北京大学深圳研究生院 Top-level domain name management method and system based on alliance chain
WO2018191882A1 (en) * 2017-04-19 2018-10-25 北京大学深圳研究生院 Domain name resolution system based on block chain
CN109067930B (en) * 2018-06-26 2021-09-17 网宿科技股份有限公司 Domain name access method, domain name resolution method, server, terminal and storage medium
CN109919764A (en) * 2019-01-31 2019-06-21 中国互联网络信息中心 Domain name transaction monitoring and managing method and device based on block chain
CN110083462A (en) * 2019-04-17 2019-08-02 江苏全链通信息科技有限公司 Communication means, equipment and storage medium based on distributed application program

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109819443A (en) * 2018-12-29 2019-05-28 东莞见达信息技术有限公司 Authentication registration method, apparatus and system based on block chain
CN109672755A (en) * 2019-01-24 2019-04-23 中国互联网络信息中心 A kind of domain name record update method and system based on block chain
CN109756589A (en) * 2019-02-20 2019-05-14 中国互联网络信息中心 A kind of domain-name information maintenance system controlled altogether in many ways based on block chain
CN110012126A (en) * 2019-04-02 2019-07-12 哈尔滨工业大学（深圳） A kind of DNS system based on block chain technology

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Rodney Pinto.ETHEREUM BASED DOMAIN NAME SYSTEM USING SMART CONTRACTS(BC-DNS).《sacramento state student reseach》.2019,第1-43页. *
基于区块链的DNS根域名解析体系;庄天舒;刘文峰;李东;;电信科学(03);全文 *

Also Published As

Publication number Publication date
FI20215063A1 (en) 2021-03-07
WO2021042786A1 (en) 2021-03-11
FR3100634B1 (en) 2022-02-25
FR3100634A1 (en) 2021-03-12
CN112468602A (en) 2021-03-09

Similar Documents

Publication Publication Date Title
CN112468602B (en) Block chain-based decentralised domain name registration system and method
US11329995B2 (en) Blockchain-based system, and electronic apparatus and method in the system
CN108881187B (en) Cross-link data transmission method and device suitable for permission link scene
CN109246211B (en) Resource uploading and resource requesting method in block chain
CN110430162B (en) Method and device for sending authenticable message in cross-link mode
KR101937188B1 (en) Method for managing information using merkle tree based on blockchain, server and terminal using the same
US20080083009A1 (en) Policy fault
EP4318362A1 (en) Blockchain-based data processing method, apparatus and device, and storage medium
CN109493052B (en) Cross-chain contract system based on main chain and parallel multiple sub-chains
CN113259394B (en) Cross-domain user authentication method, system and equipment based on routing computation
CN113329081A (en) Block chain service access method, device and computer readable storage medium
CN108650244A (en) A kind of domain name analytic method, terminal and recurrence dns server
US11522995B2 (en) Number management system, number management method, and number management device
CN112468605B (en) Block chain-based decentralization domain name updating system and method
CN112468603B (en) Domain name query system and method based on block chain
CN108366136B (en) Domain name resolution method and device
US11665133B2 (en) Method for determining a delegation chain associated with a domain name resolution in a communication network
CN111404885B (en) IPv6 domain name resolution method and system
CN112070342B (en) Microservice evaluation method and device, electronic equipment and computer readable storage medium
CN112001800B (en) Method and device for processing business in block chain system
JP2018165951A (en) Security gateway device, method, and program
CN108769284A (en) A kind of domain name analytic method, server and system
KR20030040619A (en) Method of Identifying Account Session of RADIUS Server in Mobile Telephone Packet Data Network
CN111756678B (en) Information verification method, device and equipment
KR100535626B1 (en) Non-interactive Mobile Authentification Method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 210000 A-002, building D4, No.15 Wanshou Road, Nanjing area, China (Jiangsu) pilot Free Trade Zone, Nanjing City, Jiangsu Province

Applicant after: Aowei Co.,Ltd.

Address before: 210000 A-002, building D4, No.15 Wanshou Road, Nanjing area, China (Jiangsu) pilot Free Trade Zone, Nanjing City, Jiangsu Province

Applicant before: Jiangsu Aowei Holding Co.,Ltd.

Address after: 210000 A-002, building D4, No.15 Wanshou Road, Nanjing area, China (Jiangsu) pilot Free Trade Zone, Nanjing City, Jiangsu Province

Applicant after: Jiangsu Aowei Holding Co.,Ltd.

Address before: Room 309, 3 / F, building B, No.9 Xinghuo Road, Jiangbei new district, Nanjing City, Jiangsu Province, 210000

Applicant before: Aowei information technology (Jiangsu) Co.,Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant