CN112468605A - Decentralized domain name updating system and method based on block chain - Google Patents

Decentralized domain name updating system and method based on block chain Download PDF

Info

Publication number
CN112468605A
CN112468605A CN201910845473.4A CN201910845473A CN112468605A CN 112468605 A CN112468605 A CN 112468605A CN 201910845473 A CN201910845473 A CN 201910845473A CN 112468605 A CN112468605 A CN 112468605A
Authority
CN
China
Prior art keywords
domain name
updated
chain
intelligent contract
updating request
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.)
Granted
Application number
CN201910845473.4A
Other languages
Chinese (zh)
Other versions
CN112468605B (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 Information Technology Jiangsu Co ltd
Original Assignee
Aowei Information Technology Jiangsu 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 Information Technology Jiangsu Co ltd filed Critical Aowei Information Technology Jiangsu Co ltd
Priority to CN201910845473.4A priority Critical patent/CN112468605B/en
Priority to PCT/CN2020/094211 priority patent/WO2021042787A1/en
Priority to FR2008901A priority patent/FR3100675A1/en
Publication of CN112468605A publication Critical patent/CN112468605A/en
Priority to FI20215453A priority patent/FI20215453A1/en
Application granted granted Critical
Publication of CN112468605B publication Critical patent/CN112468605B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

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

Landscapes

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

Abstract

The application provides a decentralized domain name updating system and method based on a block chain. The system comprises a public chain and a sub-chain consisting of partial nodes in the public chain. Wherein, a node in the public chain is configured with a root domain name intelligent contract; the nodes in the child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the sub-domain name intelligent contract in a competitive mode; acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node having ownership of the target domain name intelligent contract in the sub-chain; after sending the domain name updating request to the target node, the target node determines whether to accept the domain name updating request. The domain name updating system provided by the application is not controlled by ICANN any more, so that the risk that domain name updating in a DNS system is possibly limited and shielded by ICANN is avoided, and the network security of each party participating in and providing network service can be improved.

Description

Decentralized domain name updating system and method based on block chain
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a system and a method for decentralized domain name update based on 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, used to identify the geographical location of the computer at the time of data transmission. The domain names may be classified into different levels, including a root domain name, a top level domain name, and an application domain name. The root domain name is a domain name node at the highest level, for example, the 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 the top-level domain name; the application domain name refers to a domain name below the top-level domain name, and for example, the application domain name is the ". abc.com." or "www.abc.com." in the domain name.
Domain name updates are a common occurrence in the internet, and over time, service provider needs may change, and domain names may need to be updated accordingly. In The prior art, The service provider usually performs Domain Name update in a Domain Name System (DNS), but The DNS System, as a centralized System, is controlled by The Internet Name and number assignment mechanism (ICANN), i.e. The process of Domain Name update is also controlled by ICANN. This unified control by an organization violates the neutrality principle of the internet, and there is a risk that the parties involved in and providing web services may be restricted and shielded by ICANN, thereby affecting the network security of the parties involved in and providing web services.
Based on this, there is a need for a block chain-based decentralized domain name updating system and method, which are used to solve the problem that in the prior art, there is a risk that domain name updating in a DNS system may be limited and shielded by ICANN, thereby affecting network security of each party participating in and providing network services.
Disclosure of Invention
The application provides a block chain-based decentralized domain name updating system and method, which can be used for solving the technical problem that in the prior art, the risk that domain name updating is possibly limited and shielded by ICANN (independent component network) in a DNS (domain name system), so that the network security of each party participating in and providing network service is influenced.
In a first aspect, an embodiment of the present application provides a block chain-based decentralized domain name updating system, where the system includes a public chain composed of multiple nodes, and a sub-chain composed 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 child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode;
the nodes in the child chain are further configured to: acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node which has ownership of the target domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the domain name to be updated;
the target node is configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted.
Optionally, the sub-domain name intelligence contracts include a top level domain name intelligence contract and an application domain name intelligence contract.
Optionally, the nodes in the child chain are further configured to: a top-level domain name intelligence contract is generated by executing the root domain name intelligence contract, and/or an application domain name intelligence contract is generated by executing the top-level domain name intelligence contract.
Optionally, the root domain name intelligence contract is for managing a top-level domain name, and the top-level domain name intelligence contract is for managing an application domain name.
Optionally, the nodes in the child chain are further configured to: acquiring a domain name to be updated, and if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract; and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating a top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
Optionally, the nodes in the child chain are further configured to: acquiring a domain name to be updated, if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determining a target node in a sub-chain which has ownership of the top-level domain name intelligent contract; sending a domain name updating request to the target node, wherein the domain name updating request comprises the secondary domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating the application domain name intelligent contract corresponding to the secondary domain name to be updated if the domain name updating request is accepted.
Optionally, the nodes in the child chain are further configured to: acquiring a domain name to be updated, if the domain name to be updated is a third-level domain name to be updated, determining that a target domain name intelligent contract for managing the third-level domain name to be updated is an application domain name intelligent contract, and determining a target node which has ownership of the application domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the three-level domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating domain name system BNS data corresponding to the tertiary domain name to be updated if the domain name updating request is accepted.
Optionally, the target node is further configured to: and if the domain name updating request is rejected, the domain name to be updated fails to be updated.
Optionally, the nodes in the child chain are further configured to: acquiring a domain name to be updated sent by an initiating node;
the initiating node is configured to: and acquiring the domain name to be updated provided by the service provider.
In a second aspect, the present application provides a block chain based de-centralization domain name updating method, which is applied to the system described above, where the system includes a public chain composed of a plurality of nodes, and a sub-chain composed 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 child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode; the method comprises the following steps:
acquiring a domain name to be updated by a node in the sub-chain;
determining a target domain name intelligent contract for managing the domain name to be updated by the nodes in the sub-chain, and determining a target node which has the ownership of the target domain name intelligent contract in the sub-chain;
sending a domain name updating request to the target node by a node in the sub-chain, wherein the domain name updating request comprises the domain name to be updated;
the target node verifies the domain name updating request;
and the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated.
Optionally, the sub-domain name intelligence contracts include a top level domain name intelligence contract and an application domain name intelligence contract.
Optionally, the root domain name intelligence contract is for managing a top-level domain name, and the top-level domain name intelligence contract is for managing an application domain name.
Optionally, the determining, by a node in the child chain, a target domain name intelligent contract for managing the domain name to be updated includes:
if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract by a node in the sub-chain;
the method further comprises the following steps:
and the node in the sub-chain checks the domain name updating request, determines whether to accept the domain name updating request according to a check result, and updates the top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
Optionally, the determining, by a node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated and a target node in the sub-chain having ownership of the target domain name intelligent contract includes:
if the domain name to be updated is a secondary domain name to be updated, the node in the sub-chain determines that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract and determines a target node in the sub-chain having ownership of the application domain name intelligent contract
The target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated, including:
and the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract of the application domain name corresponding to the secondary domain name to be updated is updated.
Optionally, the determining, by a node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated and a target node in the sub-chain having ownership of the target domain name intelligent contract includes:
if the domain name to be updated is a third-level domain name to be updated, determining that a target domain name intelligent contract for managing the third-level domain name to be updated is an application domain name intelligent contract by the node in the sub-chain, and determining a target node which has ownership of the application domain name intelligent contract in the sub-chain;
the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated, including:
and the target node determines whether to accept the domain name updating request or not according to the checking result, and if the domain name updating request is accepted, the domain name system BNS data corresponding to the tertiary domain name to be updated is updated.
Optionally, the method further comprises:
and if the domain name updating request is rejected, the domain name to be updated fails to be updated.
Optionally, a node in the child chain acquires a domain name to be updated, including;
a node in the sub-chain acquires a domain name to be updated sent by an initiating node; the initiating node is used for acquiring a domain name to be updated provided by a service provider.
An apparatus is further provided in an embodiment of the present application, and the apparatus has a function of implementing the above-described block chain-based decentralized domain name update method. This function may be implemented by hardware executing corresponding software, and in one possible design, the apparatus includes: a processor, a transceiver, a memory; the memory is used for storing computer-executable instructions, the transceiver is used for realizing the communication between the device and 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 by the memory so as to enable the device to execute the block chain-based decentralized domain name updating method described above.
An embodiment of the present invention further provides a computer storage medium, where a software program is stored, and when the software program is read and executed by one or more processors, the software program implements the domain name de-centering method based on a blockchain described in the foregoing various possible implementation manners.
Embodiments of the present invention further provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the method for updating a decentralized domain name based on a blockchain described in the foregoing various possible implementations.
According to the above technical solution, the present application provides a decentralized domain name updating system based on a block chain, including: a public chain composed of a plurality of nodes, and a sub-chain composed of part of nodes in the public chain. Wherein, all nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode; acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node having ownership of the target domain name intelligent contract in the sub-chain; after sending the domain name updating request to the target node, the target node checks the domain name updating request, and determines whether to accept the domain name updating request according to the checking result, if so, the intelligent contract corresponding to the domain name to be updated is updated. According to the method and the system, the DNS system is deployed in the block chain network in a sub-chain mode, and complete decentralized deployment can be achieved. Compared with the existing DNS system, the domain name updating system provided by the application is not controlled by ICANN any more, so that the risk that domain name updating in the DNS system is possibly limited and shielded by ICANN is avoided, and the network security of each party participating in and providing network service can be improved.
Drawings
Fig. 1 is a schematic structural diagram of a block chain based decentralized domain name updating system according to an embodiment of the present application;
fig. 2 is a schematic flowchart illustrating a domain name updating process performed by a domain name updating system according to an embodiment of the present application;
fig. 3 is a schematic diagram of a domain name updating 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 updating process of a secondary domain name according to an embodiment of the present application;
fig. 5 is a schematic diagram of a domain name updating process of a third-level domain name according to an embodiment of the present application;
fig. 6 is a flowchart illustrating a method for updating a decentralized domain name based on a block chain according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
In the technical solution provided by the present application, a 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 inside the network. I.e., the blockchain network is a transaction platform that encompasses distributed technology, cryptography, P2P network architecture, and various consensus algorithms that may be applied.
In this application, the blockchain or blockchain data refers to accounting information generated according to transaction information when transactions occur in a blockchain network, that is, a plurality of transactions form a blockchain, and a plurality of blockchain data form a blockchain with a timestamp. The blockchain network comprises nodes which establish point-to-point network connection with each other, and each node is configured with a corresponding consensus mechanism, such as an intelligent contract, and has enough computing power to perform transaction verification and accounting procedures. The nodes also have interface specifications that conform to some uniform standard to enable access to more nodes or other types of blockchain networks through the interface specifications. The public link is a point-to-point network structure consisting of a plurality of nodes in a block link network, and each node has a distributed storage function and transaction and accounting functions; the nodes on the public link provide a uniform interface specification to the outside.
A possible system architecture to which the embodiments of the present application are applicable will be first described with reference to fig. 1.
Please refer to fig. 1, which schematically illustrates a structural diagram of a block chain based decentralized domain name updating system applicable to an embodiment of the present application. The system may include: the system comprises a public chain consisting of a plurality of nodes and a sub-chain consisting of partial nodes in the public chain. Obviously, in this embodiment, the nodes in the public chain may also be used as child chain nodes at the same time. The nodes in the sub-chain are composed of partial nodes in the public chain, so that the nodes are nodes in the sub-chain and nodes in the public 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 link may provide basic blockchain services in the network, such as transaction, authentication, storage, etc. The public link itself may not have any specific function corresponding to any field, but rather acts as a bridge to collect all sub-chains (or third party blockchain networks) accessing the public link into the same blockchain network, so that different access links can trade or transmit 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 updating registration service through executing the root domain name intelligent contract.
The nodes in the child chain may be configured to: and generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode. After a sub-chain node acquires ownership of a sub-domain name intelligent contract, the sub-chain node may serve as an owner of the sub-domain name intelligent contract, that is, the sub-chain node is configured with the sub-domain name intelligent contract.
Since the nodes constituting the sub-chain have the same intelligent contract as the nodes of the public chain, the nodes in the sub-chain can directly execute the root domain name intelligent contract, thereby generating the sub-domain name intelligent contract. The sub-domain Name intelligent contracts include top-level domain Name intelligent contracts, application domain Name intelligent contracts and domain Name System (BNS) data.
In the domain name system, domain names may be classified into root domain names, top-level domain names, and application domain names. Further, the application domain names can be divided into a second-level domain name, a third-level domain name, a fourth-level domain name and the like. A complete domain name consists of two or more parts, all parts are separated by English periods, and the endmost period is called a root domain name; the right portion of the first to last ". multidot.n" is called the Top Level Domain name (TLD), also called the Level one Domain name, containing a legal string, and a Domain name suffix; the left part of the character string of the top Level Domain name is called a Second Level Domain name (SLD) till the next "-"; the left part of the second-level domain name is called a third-level domain name, and so on, the domain name of each level controls the distribution of the domain name of the next level.
In the embodiment of the application, different intelligent contracts are provided for domain names of different levels. The root domain name can correspond to a root domain name intelligent contract, and the root domain name intelligent contract can be used for managing and maintaining the top-level domain name and generating the top-level domain name intelligent contract; the top-level domain name may correspond to a top-level domain name intelligence contract, which may be used to manage and maintain the application domain name (e.g., manage the secondary domain name), and generate the application domain name intelligence contract; the application domain name may correspond to an application domain name intelligence contract, which may be used to manage and maintain BNS data; BNS data can include information related to the third level domain name, information related to the fourth level domain name, and the like.
Further, the nodes in the child chain may be specifically configured to: a top-level domain name intelligence contract is generated by executing a root domain name intelligence contract.
Alternatively, the nodes in the child chain may be specifically 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 what is described above, the following describes the domain name update scenario in detail.
Fig. 2 schematically illustrates a flow chart of a domain name updating system for performing domain name updating according to an embodiment of the present application.
As shown in fig. 2, a node in the child chain (e.g., node 1 shown in fig. 2) may be further configured to: acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node (such as node 2 shown in fig. 2) having the ownership of the target domain name intelligent contract in the sub-chain; and sending a domain name updating request to the target node. The domain name updating request comprises a domain name to be updated.
Accordingly, the target node may be configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted.
According to the above technical solution, the present application provides a decentralized domain name updating system based on a block chain, including: a public chain composed of a plurality of nodes, and a sub-chain composed of part of nodes in the public chain. Wherein, all nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode; acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node having ownership of the target domain name intelligent contract in the sub-chain; after sending the domain name updating request to the target node, the target node checks the domain name updating request, and determines whether to accept the domain name updating request according to the checking result, if so, the intelligent contract corresponding to the domain name to be updated is updated. According to the method and the system, the DNS system is deployed in the block chain network in a sub-chain mode, and complete decentralized deployment can be achieved. Compared with the existing DNS system, the domain name updating system provided by the application is not controlled by ICANN any more, so that the risk that domain name updating in the DNS system is possibly limited and shielded by ICANN is avoided, and the network security of each party participating in and providing network service can be improved.
As can be seen from the illustration of fig. 2, the transaction request received by the node in the child chain (i.e., node 1) originates from node 0. Node 0 may be an initiating node of the domain name update transaction, that is, a node in the child chain (e.g., node 1 shown in fig. 2) may be further configured to: and acquiring the domain name to be updated sent by the initiating node.
In the embodiment of the present application, the operation of updating the domain name needs to be initiated by the owner corresponding to the domain name to be updated. That is, the originating node may be configured to: and acquiring the domain name to be updated provided by the service provider.
In an actual application environment, the initiating node may directly perform transaction or information interaction with the node in the sub-chain, that is, may directly send the domain name to be updated to the node in the sub-chain through the initiating node. That is, the originating node and the node in the sub-chain may be in a transaction in the same blockchain network, that is, the originating node is also a node in the domain name updating system.
Considering that the domain name to be updated in the present application may be a domain name of different levels, correspondingly, the target domain name intelligent contracts capable of managing the domain name to be updated are also different. The following describes in detail the domain name updating process of domain names to be updated at different levels by way of example.
Example one:
fig. 3 is a schematic diagram of a domain name update process of a top-level domain name according to an embodiment of the present application. The node in the child chain (e.g., node 1 shown in fig. 3) may be further configured to: acquiring a domain name to be updated, and if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract; and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating a top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
According to the relationship between the intelligent contract and the domain name, if the domain name to be updated is the top level domain name to be updated, obviously, the target intelligent contract for managing the top level domain name to be updated is the root intelligent contract; in the domain name updating system provided in the embodiment of the present application, all nodes in the public chain are configured with root domain name intelligent contracts, and nodes in the sub-chain are composed of part of nodes in the public chain, that is, all nodes in the sub-chain are also configured with root domain name intelligent contracts; therefore, the target node that the node in the sub-chain needs to determine is itself, and further, the node in the sub-chain may decide whether to accept the update request of the top-level domain name to be updated.
Example two:
fig. 4 is a schematic diagram of a domain name updating process of a secondary domain name provided in the embodiment of the present application. The node in the child chain (e.g., node 1 shown in fig. 4) may be further configured to: acquiring a domain name to be updated, if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determining a target node (such as a node 2 shown in fig. 4) in a sub-chain which has ownership of the top-level domain name intelligent contract; and sending a domain name updating request to the target node. The domain name updating request comprises a secondary domain name to be updated;
accordingly, the target node (e.g., node 2 shown in fig. 4) may be further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating the application domain name intelligent contract corresponding to the secondary domain name to be updated if the domain name updating request is accepted.
Example three:
fig. 5 is a schematic diagram of a domain name updating process of a third-level domain name provided in the embodiment of the present application. The node in the child chain (e.g., node 1 shown in fig. 5) may be further configured to: acquiring a domain name to be updated, if the domain name to be updated is a third-level domain name to be updated, determining that a target domain name intelligent contract for managing the third-level domain name to be updated is an application domain name intelligent contract, and determining a target node (such as a node 2 shown in fig. 5) having ownership of the application domain name intelligent contract in the sub-chain; and sending a domain name updating request to the target node. The domain name updating request comprises a third-level domain name to be updated;
the target node (e.g., node 2 shown in fig. 5) may be further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating domain name system BNS data corresponding to the third-level domain name to be updated if the domain name updating request is accepted.
It should be noted that if the domain name to be updated is a domain name with four levels or more, the method shown in fig. 5 can also be used to implement domain name update, and will not be described in detail here.
Based on the same inventive concept, the embodiment of the application also provides a decentralized domain name updating method based on the block chain. Fig. 6 is a schematic flow chart corresponding to a block chain based decentralized domain name updating method according to an embodiment of the present application. The method may be applied to the decentralized domain name updating system described above, which may include 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 child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the sub-domain name intelligent contract in a competitive mode; the method specifically comprises the following steps:
step 101, a node in a child chain acquires a domain name to be updated.
Step 102, determining a target domain name intelligent contract for managing the domain name to be updated by the nodes in the sub-chain, and determining a target node which has the ownership of the target domain name intelligent contract in the sub-chain.
Step 103, the nodes in the child chain send domain name update requests to the target node.
Wherein the domain name updating request comprises the domain name to be updated.
And 104, the target node checks the domain name updating request.
And 105, the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated.
By adopting the method, the DNS system is deployed in the block chain network in the form of the sub-chain, and complete decentralized deployment can be realized. Compared with the existing DNS system, the domain name updating method provided by the application is not controlled by ICANN any more, so that the risk that domain name updating in the DNS system is possibly limited and shielded by ICANN is avoided, and the network security of each party participating in and providing network service can be improved.
Acquiring a domain name to be updated by a node in the sub-chain;
determining a target domain name intelligent contract for managing the domain name to be updated by the nodes in the sub-chain, and determining a target node which has the ownership of the target domain name intelligent contract in the sub-chain;
sending a domain name updating request to the target node by a node in the sub-chain, wherein the domain name updating request comprises the domain name to be updated;
the target node verifies the domain name updating request;
and the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated.
Optionally, the sub-domain name intelligence contracts include a top level domain name intelligence contract and an application domain name intelligence contract.
Optionally, the root domain name intelligence contract is for managing a top-level domain name, and the top-level domain name intelligence contract is for managing an application domain name.
Optionally, the determining, by a node in the child chain, a target domain name intelligent contract for managing the domain name to be updated includes:
if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract by a node in the sub-chain;
the method further comprises the following steps:
and the node in the sub-chain checks the domain name updating request, determines whether to accept the domain name updating request according to a check result, and updates the top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
Optionally, the determining, by a node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated and a target node in the sub-chain having ownership of the target domain name intelligent contract includes:
if the domain name to be updated is a secondary domain name to be updated, the node in the sub-chain determines that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract and determines a target node in the sub-chain having ownership of the application domain name intelligent contract
The target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated, including:
and the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract of the application domain name corresponding to the secondary domain name to be updated is updated.
Optionally, the determining, by a node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated and a target node in the sub-chain having ownership of the target domain name intelligent contract includes:
if the domain name to be updated is a third-level domain name to be updated, determining that a target domain name intelligent contract for managing the third-level domain name to be updated is an application domain name intelligent contract by the node in the sub-chain, and determining a target node which has ownership of the application domain name intelligent contract in the sub-chain;
the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated, including:
and the target node determines whether to accept the domain name updating request or not according to the checking result, and if the domain name updating request is accepted, the domain name system BNS data corresponding to the tertiary domain name to be updated is updated.
Optionally, the method further comprises:
and if the domain name updating request is rejected, the domain name to be updated fails to be updated.
Optionally, a node in the child chain acquires a domain name to be updated, including;
a node in the sub-chain acquires a domain name to be updated sent by an initiating node; the initiating node is used for acquiring a domain name to be updated provided by a service provider.
In an exemplary embodiment, a computer-readable storage medium is further provided, in which a computer program or an intelligent contract is stored, and the computer program or the intelligent contract is loaded and executed by a node to implement the transaction processing method provided by the above-described embodiment. Alternatively, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Those skilled in the art will clearly understand that the techniques in the embodiments of the present application may be implemented by way of software plus a required general hardware platform. Based on such understanding, the technical solutions in the embodiments of the present application may be essentially implemented or a part contributing to the prior art may be embodied 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., and includes several instructions for enabling 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 variations, 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 will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A block chain based decentralized domain name updating system, characterized in that, the system comprises a public chain composed of a plurality of nodes, and a sub-chain composed 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 child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode;
the nodes in the child chain are further configured to: acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node which has ownership of the target domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the domain name to be updated;
the target node is configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted.
2. The system in accordance with claim 1, wherein the sub-domain name intelligence contracts comprise top-level domain name intelligence contracts and application domain name intelligence contracts.
3. The system of claim 2, wherein the nodes in the child chain are further configured to: a top-level domain name intelligence contract is generated by executing the root domain name intelligence contract, and/or an application domain name intelligence contract is generated by executing the top-level domain name intelligence contract.
4. The system in accordance with claim 3, wherein the root domain name intelligence contract is configured to manage a top-level domain name, and wherein the top-level domain name intelligence contract is configured to manage an application domain name.
5. The system of claim 4, wherein the nodes in the child chain are further configured to: acquiring a domain name to be updated, and if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract; and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating a top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
6. The system of claim 4, wherein the nodes in the child chain are further configured to: acquiring a domain name to be updated, if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determining a target node in a sub-chain which has ownership of the top-level domain name intelligent contract; sending a domain name updating request to the target node, wherein the domain name updating request comprises the secondary domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating the application domain name intelligent contract corresponding to the secondary domain name to be updated if the domain name updating request is accepted.
7. The system of claim 4, wherein the nodes in the child chain are further configured to: acquiring a domain name to be updated, if the domain name to be updated is a third-level domain name to be updated, determining that a target domain name intelligent contract for managing the third-level domain name to be updated is an application domain name intelligent contract, and determining a target node which has ownership of the application domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the three-level domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to a checking result, and updating domain name system BNS data corresponding to the tertiary domain name to be updated if the domain name updating request is accepted.
8. The system of claim 1, wherein the target node is further configured to: and if the domain name updating request is rejected, the domain name to be updated fails to be updated.
9. The system of any of claims 1-8, wherein a node in the child chain is further configured to: acquiring a domain name to be updated sent by an initiating node;
the initiating node is configured to: and acquiring the domain name to be updated provided by the service provider.
10. A block chain based decentralized domain name updating method, wherein the method is applied to the system of any one of claims 1 to 9, the system comprises a public chain composed of a plurality of nodes, and a sub-chain composed 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 child chain are configured to: generating a sub-domain name intelligent contract by executing the root domain name intelligent contract, and acquiring the ownership of the sub-domain name intelligent contract in a competitive mode; the method comprises the following steps:
acquiring a domain name to be updated by a node in the sub-chain;
determining a target domain name intelligent contract for managing the domain name to be updated by the nodes in the sub-chain, and determining a target node which has the ownership of the target domain name intelligent contract in the sub-chain;
sending a domain name updating request to the target node by a node in the sub-chain, wherein the domain name updating request comprises the domain name to be updated;
the target node verifies the domain name updating request;
and the target node determines whether to accept the domain name updating request according to the checking result, and if the domain name updating request is accepted, the intelligent contract corresponding to the domain name to be updated is updated.
CN201910845473.4A 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method Active CN112468605B (en)

Priority Applications (4)

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

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910845473.4A CN112468605B (en) 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method

Publications (2)

Publication Number Publication Date
CN112468605A true CN112468605A (en) 2021-03-09
CN112468605B CN112468605B (en) 2023-08-08

Family

ID=74806981

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910845473.4A Active CN112468605B (en) 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method

Country Status (4)

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

Citations (1)

* 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

Family Cites Families (5)

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

Patent Citations (1)

* 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

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
RODNEY PINTO: ""ETHREUM BASED DOMAIN NAME SYSTEM USING SMART CONTRACTS(BC-DNS)"", 《SACRAMENTO STATE STUDENT RESEACH》 *

Also Published As

Publication number Publication date
CN112468605B (en) 2023-08-08
FR3100675A1 (en) 2021-03-12
WO2021042787A1 (en) 2021-03-11
FI20215453A1 (en) 2021-04-16

Similar Documents

Publication Publication Date Title
US11995618B2 (en) Blockchain network interaction controller
US20240064014A9 (en) Methods and systems implemented in a network architecture with nodes capable of performing message-based transactions
US10505949B2 (en) Blockchain-based system, and electronic apparatus and method in the system
US10511593B2 (en) Cross cloud application access
US20150135277A1 (en) Methods for Generating and Using Trust Blueprints in Security Architectures
KR101937188B1 (en) Method for managing information using merkle tree based on blockchain, server and terminal using the same
CN112468602B (en) Block chain-based decentralised domain name registration system and method
US20180359242A1 (en) Cross Cloud Tenant Discovery
JP2024505692A (en) Data processing methods, devices and computer equipment based on blockchain networks
CN114567643B (en) Cross-blockchain data transfer method, device and related equipment
JP2021531707A (en) Domain name management system based on blockchain
JPWO2019142884A1 (en) Block verification device, block verification method, and program
Zhang et al. Blockchain‐Based DNS Root Zone Management Decentralization for Internet of Things
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
CN109842554A (en) Method for routing, device, equipment and the storage medium of device service
US11665067B2 (en) Managing reconfigurations of distributed computing systems
CN116126480A (en) Cross-region block chain processing method and device for transaction, intelligent equipment, medium and product
US20070195766A1 (en) Virtualized services system and method
KR20210027012A (en) Peer node and method for processing information thereof, and blockchain platform systems
CN111404885A (en) IPv6 domain name resolution method and system
CN114338669B (en) Block chain-based data transmission method, device, equipment and storage medium
CN111756678B (en) Information verification method, device and equipment
CN115208817B (en) Trusted cross-link routing method based on cross-link gateway and Floyd algorithm

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

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.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant