CN112468603A - Domain name query system and method based on block chain - Google Patents

Domain name query system and method based on block chain Download PDF

Info

Publication number
CN112468603A
CN112468603A CN201910842305.XA CN201910842305A CN112468603A CN 112468603 A CN112468603 A CN 112468603A CN 201910842305 A CN201910842305 A CN 201910842305A CN 112468603 A CN112468603 A CN 112468603A
Authority
CN
China
Prior art keywords
domain name
node
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.)
Granted
Application number
CN201910842305.XA
Other languages
Chinese (zh)
Other versions
CN112468603B (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.)
Chen Yunzhe
Nanjing Aowei Holdings 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 CN201910842305.XA priority Critical patent/CN112468603B/en
Priority to PCT/CN2020/094212 priority patent/WO2021042788A1/en
Priority to FR2008785A priority patent/FR3100633A1/en
Publication of CN112468603A publication Critical patent/CN112468603A/en
Application granted granted Critical
Publication of CN112468603B publication Critical patent/CN112468603B/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/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/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
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441—Countermeasures against malicious traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/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)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • General Health & Medical Sciences (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Computing Systems (AREA)
  • Primary Health Care (AREA)
  • Software Systems (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Bioethics (AREA)
  • Game Theory and Decision Science (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The application provides a domain name query 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 queried, and determining a first domain name intelligent contract corresponding to the domain name to be queried; and if the first domain name intelligent contract is configured, calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired. Compared with the prior art that the domain name inquiry system manages the domain names of different levels by the fixed server, the domain name inquiry system is higher in flexibility and not easy to attack, improves the stability of the whole system, and further can improve the network safety of all parties participating in and providing network services.

Description

Domain name query 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 querying a 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, 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 query is a necessary step in a Domain Name resolution process, and currently, a Domain Name System (DNS) System is generally used for Domain Name resolution, but the DNS System is a multi-level System with high dependency between different levels, and once a certain level fails or receives an attack, the whole System is at risk of breakdown.
Based on this, there is a need for a domain name query system based on a block chain, which is used to solve the problem that once a certain level in the existing DNS system fails or is attacked, the whole system is easily crashed.
Disclosure of Invention
The application provides a domain name query system and a domain name query method based on a block chain, which can be used for solving the technical problem that once a certain level in the existing DNS system fails or is attacked, the whole system is easy to crash.
In a first aspect, an embodiment of the present application provides a domain name query system based on a block chain, 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 queried, and determining a first domain name intelligent contract corresponding to the domain name to be queried; and if the first domain name intelligent contract is configured, calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired.
Optionally, the nodes in the child chain are further configured to: if the first domain name intelligent contract is not configured, determining a second domain name intelligent contract for managing the domain name to be inquired; if the second domain name intelligent contract is configured, calling the second domain name intelligent contract to inquire a first node having ownership of the first domain name intelligent contract; sending a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node is configured to: calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returning the address information of the domain name to be inquired to the node in the sub-chain.
Optionally, the nodes in the child chain are further configured to: if the second domain name intelligent contract is not the root domain name intelligent contract and is not configured with the second domain name intelligent contract, calling the root domain name intelligent contract to inquire a second node having ownership of the second domain name intelligent contract; sending a contract invoking request to the second node, wherein the contract invoking request comprises the second domain name intelligent contract;
the second node is configured to: invoking the second domain name smart contract to query a first node that owns ownership of the first domain name smart contract, and returning the first node to a node in the child chain;
the nodes in the child chain are further configured to: sending a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node is configured to: calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returning the address information of the domain name to be inquired to the node in the sub-chain.
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 intelligent contract is used for managing a top-level domain name, the top-level domain name intelligent contract is used for managing a second-level domain name, and the application domain name intelligent contract is used for managing domain names with three levels or more.
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 nodes in the child chain are further configured to: and if the address information of the domain name to be inquired is not inquired by calling the first domain name intelligent contract, the domain name inquiry is failed.
Optionally, the nodes in the child chain are further configured to: and acquiring the domain name to be inquired sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
In a second aspect, the present application provides a domain name query method based on a block chain, 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 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 inquired by a node in the sub-chain;
determining a first domain name intelligent contract corresponding to the domain name to be inquired by a node in the sub-chain;
and if the node is configured with the first domain name intelligent contract, the node in the sub-chain calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired.
Optionally, the method further comprises:
and if the node in the sub-chain calls the first domain name intelligent contract to not inquire the address information of the domain name to be inquired, the domain name inquiry is failed.
Optionally, the method further comprises:
if the node is not configured with the first domain name intelligent contract, the node in the sub-chain determines a second domain name intelligent contract for managing the domain name to be inquired;
if the node is configured with the second domain name intelligent contract, the node in the sub-chain calls the second domain name intelligent contract to inquire a first node having ownership of the first domain name intelligent contract;
a node in the sub-chain sends a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returns the address information of the domain name to be inquired to the node in the sub-chain.
Optionally, the method further comprises:
if the second domain name intelligent contract is not a root domain name intelligent contract and is not configured with the second domain name intelligent contract, the node in the sub-chain calls the root domain name intelligent contract to inquire a second node having ownership of the second domain name intelligent contract;
sending, by a node in the child chain, a contract invocation request to the second node, the contract invocation request including the second domain name intelligent contract;
the second node querying a first node that owns the ownership of the first domain name intelligence contract with the second domain name intelligence contract and returning the first node to the nodes in the child chain;
a node in the sub-chain sends a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returns the address information of the domain name to be inquired to the node in the sub-chain.
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 intelligent contract is used for managing a top-level domain name, the top-level domain name intelligent contract is used for managing a second-level domain name, and the application domain name intelligent contract is used for managing domain names with three levels or more.
Optionally, the obtaining, by a node in the child chain, a domain name to be queried includes:
and the nodes in the sub chain acquire the domain names to be inquired, which are sent by the initiating node or the adjacent nodes corresponding to the nodes in the sub chain.
The embodiment of the present application further provides an apparatus, which has a function of implementing the above-described domain name query method based on the blockchain. 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 execution 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 execution instructions stored in the memory so as to enable the device to execute the domain name inquiry method based on the block chain.
An embodiment of the present invention further provides a computer storage medium, where a software program is stored in the storage medium, and when the software program is read and executed by one or more processors, the domain name query method based on a block chain described in the foregoing various possible implementation manners is implemented.
Embodiments of the present invention further provide a computer program product containing instructions, which when run on a computer, enable the computer to execute the domain name query method based on a block chain described in the foregoing various possible implementations.
According to the above technical solution, the present application provides a domain name query 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 queried, and determining a first domain name intelligent contract corresponding to the domain name to be queried; and if the first domain name intelligent contract is configured, calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired. 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, in the domain name query system provided by the application, domain names of different levels are managed by different intelligent contracts, and ownership of the intelligent contracts is acquired by nodes in the sub-chains in a competition mode.
Drawings
Fig. 1 is a schematic structural diagram of a domain name querying system based on a block chain, which is applicable to the embodiment of the present application;
fig. 2 is a schematic flowchart of a domain name query system according to an embodiment of the present application;
fig. 3 is a schematic flowchart of performing domain name query by another domain name querying system according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a domain name query system for performing domain name query according to an embodiment of the present application;
fig. 5 is a schematic diagram of a domain name query process of a top-level domain name according to an embodiment of the present application;
fig. 6 is a schematic diagram of a domain name query process of a secondary domain name according to an embodiment of the present application;
fig. 7 is a schematic flowchart corresponding to a domain name querying method 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.
Referring to fig. 1, a schematic structural diagram of a domain name querying system based on a blockchain to which an embodiment of the present application is applicable is exemplarily shown. 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 inquiry and 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 case of domain name query in detail.
Fig. 2 schematically illustrates a flow chart of a domain name query system for performing domain name query 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 queried, and determining a first domain name intelligent contract corresponding to the domain name to be queried; and if the first domain name intelligent contract is configured, calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired.
Further, if the address information of the domain name to be queried is not queried by calling the first domain name intelligent contract, the domain name query fails.
According to the above technical solution, the present application provides a domain name query 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 queried, and determining a first domain name intelligent contract corresponding to the domain name to be queried; and if the first domain name intelligent contract is configured, calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired. 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, in the domain name query system provided by the application, domain names of different levels are managed by different intelligent contracts, and ownership of the intelligent contracts is acquired by nodes in the sub-chains in a competition mode.
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 the initiating node of the domain name erasing transaction, or may be a neighboring node of the node (i.e., node 1) in the child chain. 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 inquired sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
According to different practical application environments, the transaction forms between the initiating node and the nodes in the sub-chain are different. The following two situations may be possible in which a node in the child chain acquires a domain name to be queried sent by the originating node.
One scenario is that if the originating node can directly perform transaction or information interaction with the nodes in the sub-chain, the domain name to be queried can be sent to the nodes in the sub-chain directly through the originating node. This approach is best suited for transactions where the originating node is in the same blockchain network as the nodes in the child chain, i.e., the originating node is also a node in the domain name query system.
Another scenario is that if the originating node cannot directly perform transaction or information interaction with the nodes in the child chain, the domain name to be queried may be broadcast by the originating node. Specifically, the domain name to be queried may be broadcast to the neighboring node, and the neighboring node determines whether to receive the domain name to be queried or continue to broadcast in combination with its own role until the node in the sub-chain receives the domain name to be queried.
The situation that the node in the sub-chain receives the domain name to be queried sent by the neighboring node of the node in the sub-chain corresponds to the situation that the initiating node does not know the position information of the core node and sends the domain name to be queried in the block chain in a broadcasting mode, so that the node in the sub-chain can receive the domain name to be queried through the neighboring node along with the diffusion of information.
It should be noted that the above two cases are only exemplary, and in other possible examples, if the initiating node is a neighboring node of a node in the sub-chain, the node in the sub-chain may also be regarded as directly receiving the domain name to be queried sent by the initiating node.
In this embodiment, it is considered that the nodes in the sub-chain acquire ownership of the sub-domain intelligent contract in a competitive manner, that is, when a node in the sub-chain acquires a domain name to be queried, a situation may occur that the node does not acquire ownership of the first domain intelligent contract corresponding to the domain name to be queried in a competitive manner, that is, the node is not configured with the first domain intelligent contract. Based on this, fig. 3 exemplarily shows a schematic flowchart of another domain name querying system for domain name querying according to an embodiment of the present application.
As shown in fig. 3, a node in the child chain (e.g., node 1 shown in fig. 3) may be further configured to: acquiring a domain name to be queried sent by an initiating node (such as node 0 shown in fig. 3), and determining a first domain name intelligent contract corresponding to the domain name to be queried; if the intelligent contract is not configured with the first domain name intelligent contract, determining a second domain name intelligent contract for managing the domain name to be inquired; if the second domain name intelligent contract is configured, calling the second domain name intelligent contract to inquire a first node (such as a node 2 shown in figure 3) having the ownership of the first domain name intelligent contract; sending a domain name query request to the first node. The domain name query request comprises a domain name to be queried.
Accordingly, a first node (e.g., node 2 shown in fig. 3) may be configured to: calling a first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returning the address information of the domain name to be inquired to the node in the sub-chain.
Based on the same consideration, in the embodiment of the present application, a situation may occur that nodes in a child chain do not compete to acquire ownership of the second domain name intelligent contract, that is, the nodes themselves are not configured with the second domain name intelligent contract. Based on this, fig. 4 exemplarily shows a flowchart of a domain name query system for performing domain name query according to an embodiment of the present application.
As shown in fig. 4, a node in the child chain (e.g., node 1 shown in fig. 4) may be further configured to: acquiring a domain name to be queried sent by an initiating node (such as a node 0 shown in fig. 4), and determining a first domain name intelligent contract corresponding to the domain name to be queried; if the intelligent contract is not configured with the first domain name intelligent contract, determining a second domain name intelligent contract for managing the domain name to be inquired; if the second domain name intelligent contract is not the root domain name intelligent contract and is not configured with the second domain name intelligent contract, calling the root domain name intelligent contract to inquire a second node (such as a node 3 shown in the figure 4) having the ownership of the second domain name intelligent contract; and sending a contract invoking request to the second node. Wherein the contract invocation request includes a second domain name intelligent contract.
In the domain name query system provided by the embodiment of the application, all nodes in a public chain are configured with root domain name intelligent contracts, and nodes in a 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; thus, when a node in the child chain determines that it is not itself configured with a second domain name intelligence contract, the root domain name intelligence contract may be invoked directly.
Accordingly, a second node (e.g., node 3 shown in fig. 4) may be configured to: invoking the second domain name intelligence contract queries a first node (e.g., node 2 shown in fig. 4) that owns the ownership of the first domain name intelligence contract, and returns the first node to the nodes in the child chain.
In turn, the node in the child chain (e.g., node 1 shown in fig. 4) may be further configured to: sending a domain name query request to the first node. The domain name query request comprises a domain name to be queried.
As such, a first node (e.g., node 2 shown in fig. 4) may be configured to: calling a first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returning the address information of the domain name to be inquired to the node in the sub-chain.
Considering that the domain names to be queried in the present application may be domain names of different levels, the domain name intelligent contracts called are correspondingly different. The following describes in detail a domain name query process of domain names to be queried at different levels by way of example.
Example one:
fig. 5 is a schematic diagram of a domain name query 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. 5) may be further configured to: acquiring a top-level domain name to be queried, which is sent by an initiating node (such as a node 0 shown in fig. 5), and determining a top-level domain name intelligent contract corresponding to the top-level domain name to be queried; if the top-level domain name intelligent contract is configured, calling the top-level domain name intelligent contract to inquire the address information of the top-level domain name to be inquired; if the top-level domain name intelligent contract is not configured, calling the root domain name intelligent contract to inquire a node (such as a node 2 shown in figure 5) having ownership of the top-level domain name intelligent contract, and sending a contract calling request to the node, wherein the contract calling request comprises the top-level domain name intelligent contract.
The node that owns this top-level domain name intelligent contract ownership (e.g., node 2 shown in fig. 5) may be configured to: and calling a top-level domain name intelligent contract to inquire the address information of the top-level domain name to be inquired, and returning the address information of the top-level domain name to be inquired to the node in the sub-chain.
Example two:
fig. 6 is a schematic diagram of a domain name query 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. 6) may be further configured to: acquiring a secondary domain name to be queried sent by an initiating node (such as a node 0 shown in fig. 6), and determining an application domain name intelligent contract corresponding to the secondary domain name to be queried; if the application domain name intelligent contract is configured, calling the application domain name intelligent contract to inquire the address information of the secondary domain name to be inquired; and if the application domain name intelligent contract is not configured, determining to manage the top level domain name intelligent contract of the second level domain name to be inquired. If the top-level domain name intelligent contract is configured, calling the top-level domain name intelligent contract to inquire a first node (such as a node 2 shown in fig. 6) having ownership of the application domain name intelligent contract, and sending a domain name inquiry request to the first node; if the top-level domain name intelligent contract is not configured, the root domain name intelligent contract is called to inquire a second node (such as a node 3 shown in figure 6) having the ownership of the top-level domain name intelligent contract, and a contract calling request is sent to the second node.
A first node (e.g., node 2 shown in fig. 6) may be configured to: calling the intelligent contract of the application domain name to inquire the address information of the secondary domain name to be inquired, and returning the address information of the secondary domain name to be inquired to the node in the sub-chain.
The second node (e.g., node 3 shown in fig. 6) may be configured to: invoking the top level domain name intelligent contract to inquire a first node having the ownership of the application domain name intelligent contract, and returning the first node to the nodes in the sub-chain.
It should be noted that, if the domain name to be queried is a domain name with three or more levels, the method shown in fig. 6 can also be used to implement domain name querying, and will not be described in detail here.
Based on the same inventive concept, the embodiment of the application also provides a domain name query method based on the block chain. Fig. 7 is a schematic flowchart corresponding to a domain name querying method based on a block chain according to an embodiment of the present application. The method can be applied to the domain name query system described above, and the system can include a public chain composed of a plurality of nodes and a sub-chain composed of part of 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 queried.
Step 102, a node in the sub-chain determines a first domain name intelligent contract corresponding to the domain name to be queried.
Step 103, if the node is configured with the first domain name intelligent contract, the node in the sub-chain calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired.
Further, after step 103, step 104 may be further included, that is, the node in the child chain may also return address information of the domain name to be queried to the originating node.
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, in the domain name query method provided by the application, domain names of different levels are managed by different intelligent contracts, and ownership of the intelligent contracts is acquired by nodes in the sub-chains in a competition mode.
Optionally, the method further comprises:
and if the node in the sub-chain calls the first domain name intelligent contract to not inquire the address information of the domain name to be inquired, the domain name inquiry is failed.
Optionally, the method further comprises:
if the node is not configured with the first domain name intelligent contract, the node in the sub-chain determines a second domain name intelligent contract for managing the domain name to be inquired;
if the node is configured with the second domain name intelligent contract, the node in the sub-chain calls the second domain name intelligent contract to inquire a first node having ownership of the first domain name intelligent contract;
a node in the sub-chain sends a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returns the address information of the domain name to be inquired to the node in the sub-chain.
Optionally, the method further comprises:
if the second domain name intelligent contract is not a root domain name intelligent contract and is not configured with the second domain name intelligent contract, the node in the sub-chain calls the root domain name intelligent contract to inquire a second node having ownership of the second domain name intelligent contract;
sending, by a node in the child chain, a contract invocation request to the second node, the contract invocation request including the second domain name intelligent contract;
the second node querying a first node that owns the ownership of the first domain name intelligence contract with the second domain name intelligence contract and returning the first node to the nodes in the child chain;
a node in the sub-chain sends a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returns the address information of the domain name to be inquired to the node in the sub-chain.
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 intelligent contract is used for managing a top-level domain name, the top-level domain name intelligent contract is used for managing a second-level domain name, and the application domain name intelligent contract is used for managing domain names with three levels or more.
Optionally, the obtaining, by a node in the child chain, a domain name to be queried includes:
and the nodes in the sub chain acquire the domain names to be inquired, which are sent by the initiating node or the adjacent nodes corresponding to the nodes in the sub chain.
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 domain name inquiry system based on a block chain is 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 queried, and determining a first domain name intelligent contract corresponding to the domain name to be queried; and if the first domain name intelligent contract is configured, calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired.
2. The system of claim 1, wherein the nodes in the child chain are further configured to: if the first domain name intelligent contract is not configured, determining a second domain name intelligent contract for managing the domain name to be inquired; if the second domain name intelligent contract is configured, calling the second domain name intelligent contract to inquire a first node having ownership of the first domain name intelligent contract; sending a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node is configured to: calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returning the address information of the domain name to be inquired to the node in the sub-chain.
3. The system of claim 2, wherein the nodes in the child chain are further configured to: if the second domain name intelligent contract is not the root domain name intelligent contract and is not configured with the second domain name intelligent contract, calling the root domain name intelligent contract to inquire a second node having ownership of the second domain name intelligent contract; sending a contract invoking request to the second node, wherein the contract invoking request comprises the second domain name intelligent contract;
the second node is configured to: invoking the second domain name smart contract to query a first node that owns ownership of the first domain name smart contract, and returning the first node to a node in the child chain;
the nodes in the child chain are further configured to: sending a domain name query request to the first node, wherein the domain name query request comprises the domain name to be queried;
the first node is configured to: calling the first domain name intelligent contract to inquire the address information of the domain name to be inquired, and returning the address information of the domain name to be inquired to the node in the sub-chain.
4. 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.
5. The system of claim 4, wherein the root domain name intelligence contract is configured to manage a top level domain name, the top level domain name intelligence contract is configured to manage a secondary domain name, and the application domain name intelligence contract is configured to manage domain names of three levels and more.
6. The system of claim 4, 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.
7. The system of claim 1, wherein the nodes in the child chain are further configured to: and if the address information of the domain name to be inquired is not inquired by calling the first domain name intelligent contract, the domain name inquiry is failed.
8. The system of any of claims 1-7, wherein a node in the child chain is further configured to: and acquiring the domain name to be inquired sent by the initiating node or the adjacent node corresponding to the node in the sub-chain.
9. A domain name query method based on a block chain, wherein the method is applied to the system of any one of claims 1 to 8, 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 inquired by a node in the sub-chain;
determining a first domain name intelligent contract corresponding to the domain name to be inquired by a node in the sub-chain;
and if the node is configured with the first domain name intelligent contract, the node in the sub-chain calls the first domain name intelligent contract to inquire the address information of the domain name to be inquired.
10. The method of claim 9, further comprising:
and if the node in the sub-chain calls the first domain name intelligent contract to not inquire the address information of the domain name to be inquired, the domain name inquiry is failed.
CN201910842305.XA 2019-09-06 2019-09-06 Domain name query system and method based on block chain Active CN112468603B (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201910842305.XA CN112468603B (en) 2019-09-06 2019-09-06 Domain name query system and method based on block chain
PCT/CN2020/094212 WO2021042788A1 (en) 2019-09-06 2020-06-03 Blockchain-based domain name query system and method
FR2008785A FR3100633A1 (en) 2019-09-06 2020-08-28 Blockchain-based domain name query system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910842305.XA CN112468603B (en) 2019-09-06 2019-09-06 Domain name query system and method based on block chain

Publications (2)

Publication Number Publication Date
CN112468603A true CN112468603A (en) 2021-03-09
CN112468603B CN112468603B (en) 2022-01-11

Family

ID=74807120

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910842305.XA Active CN112468603B (en) 2019-09-06 2019-09-06 Domain name query system and method based on block chain

Country Status (3)

Country Link
CN (1) CN112468603B (en)
FR (1) FR3100633A1 (en)
WO (1) WO2021042788A1 (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106210171A (en) * 2016-07-25 2016-12-07 宁圣金融信息服务（上海）有限公司 A kind of block chain domain name analysis system
CN107613041A (en) * 2017-09-22 2018-01-19 中国互联网络信息中心 DNS management system, domain name management method and domain name analytic method based on block chain
CN108064444A (en) * 2017-04-19 2018-05-22 北京大学深圳研究生院 A kind of domain name analysis system based on block chain
CN108429765A (en) * 2018-05-28 2018-08-21 北京奇虎科技有限公司 A kind of method, server and system for realizing domain name mapping based on block chain
CN108833603A (en) * 2018-05-28 2018-11-16 北京奇虎科技有限公司 A kind of method, server and system for realizing domain name mapping based on block chain
CN109819443A (en) * 2018-12-29 2019-05-28 东莞见达信息技术有限公司 Authentication registration method, apparatus and system based on block chain
CN110061838A (en) * 2019-04-28 2019-07-26 广州大学 A kind of the decentralization storage system and its realization, information retrieval method of DNS resource record

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3049089B1 (en) * 2016-03-21 2018-02-16 Sebastien Jean Serge Dupont METHOD FOR MANAGING VALIDATIONS OF MESSAGE CHANNEL-RELATED MESSAGES THROUGH A DECENTRALIZED VALIDATION NETWORK
CN109067930B (en) * 2018-06-26 2021-09-17 网宿科技股份有限公司 Domain name access method, domain name resolution method, server, terminal and storage medium
CN109784761A (en) * 2019-01-31 2019-05-21 中国互联网络信息中心 Domain name ranking method, device, electronic equipment and storage medium based on block chain

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106210171A (en) * 2016-07-25 2016-12-07 宁圣金融信息服务（上海）有限公司 A kind of block chain domain name analysis system
CN108064444A (en) * 2017-04-19 2018-05-22 北京大学深圳研究生院 A kind of domain name analysis system based on block chain
CN107613041A (en) * 2017-09-22 2018-01-19 中国互联网络信息中心 DNS management system, domain name management method and domain name analytic method based on block chain
CN108429765A (en) * 2018-05-28 2018-08-21 北京奇虎科技有限公司 A kind of method, server and system for realizing domain name mapping based on block chain
CN108833603A (en) * 2018-05-28 2018-11-16 北京奇虎科技有限公司 A kind of method, server and system for realizing domain name mapping based on block chain
CN109819443A (en) * 2018-12-29 2019-05-28 东莞见达信息技术有限公司 Authentication registration method, apparatus and system based on block chain
CN110061838A (en) * 2019-04-28 2019-07-26 广州大学 A kind of the decentralization storage system and its realization, information retrieval method of DNS resource record

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
FR3100633A1 (en) 2021-03-12
WO2021042788A1 (en) 2021-03-11
CN112468603B (en) 2022-01-11

Similar Documents

Publication Publication Date Title
CN112862612B (en) Method and device for transmitting resources across chains
CN109246211B (en) Resource uploading and resource requesting method in block chain
JP5841177B2 (en) Method and system for synchronization mechanism in multi-server reservation system
US20200177388A1 (en) Cross-blockchain resource transmission
US11632390B2 (en) Systems and methods of propagating data packets in a network of nodes
CN112468602B (en) Block chain-based decentralised domain name registration system and method
US20080083009A1 (en) Policy fault
US20200403899A1 (en) Blockchain-based methods and device for propagating data in a network
KR101937188B1 (en) Method for managing information using merkle tree based on blockchain, server and terminal using the same
CN111245910B (en) Block chain light node multi-copy deployment method
CN112468525A (en) Domain name management system based on block chain
CN113329081A (en) Block chain service access method, device and computer readable storage medium
US20110153826A1 (en) Fault tolerant and scalable load distribution of resources
US20190372825A1 (en) Communication apparatus, communication method, and recording medium
CN112468603B (en) Domain name query system and method based on block chain
US7543300B2 (en) Interface for application components
CN112468605B (en) Block chain-based decentralization domain name updating system and method
CN116361172A (en) Development joint debugging method and system
CN109842554A (en) Method for routing, device, equipment and the storage medium of device service
CN112615919B (en) Resource allocation method, resource allocation device and block chain
CN114064317A (en) Node calling method in distributed system and related device
CN112001800A (en) Method and device for processing service in block chain system
Dabrowski et al. A model-based analysis of first-generation service discovery systems
CN107707383B (en) Put-through processing method and device, first network element and second network element
US20070195766A1 (en) Virtualized services system and 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
GR01 Patent grant
GR01 Patent grant
CP01 Change in the name or title of a patent holder

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

Patentee 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

Patentee before: Jiangsu Aowei Holding Co.,Ltd.

CP01 Change in the name or title of a patent holder
CP03 Change of name, title or address

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

Patentee 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

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

CP03 Change of name, title or address
CP03 Change of name, title or address

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

Patentee after: Nanjing Aowei Holdings Co.,Ltd.

Country or region after: China

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

Patentee before: Aowei Co.,Ltd.

Country or region before: China

CP03 Change of name, title or address
TR01 Transfer of patent right

Effective date of registration: 20240408

Address after: 528000, Unit 2301, Building 6, Zijin Street, Zhonghai Wanjin Haoyuan, No. 8 Jinyuan Road, Guicheng, Nanhai District, Foshan City, Guangdong Province

Patentee after: Chen Yunzhe

Country or region after: China

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

Patentee before: Nanjing Aowei Holdings Co.,Ltd.

Country or region before: China

TR01 Transfer of patent right