CN112822307B - Network identification data processing method and device - Google Patents
Network identification data processing method and device Download PDFInfo
- Publication number
- CN112822307B CN112822307B CN202110229285.6A CN202110229285A CN112822307B CN 112822307 B CN112822307 B CN 112822307B CN 202110229285 A CN202110229285 A CN 202110229285A CN 112822307 B CN112822307 B CN 112822307B
- Authority
- CN
- China
- Prior art keywords
- handle
- data
- converted
- name
- data area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/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]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and a device for processing network identification data, wherein the method comprises the following steps: acquiring a handle identifier to be converted; in a DNS analysis system, generating a prefix area corresponding to the naming authority of the handle identifier to be converted and generating a data area corresponding to the local name of the handle identifier to be converted; storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area. On the premise of not changing the DNS protocol and the handle protocol, the handle identifier is converted into the domain name identifier, and the handle identifier system does not need to be additionally constructed and maintained, so that the construction cost and the maintenance cost of the identifier system are reduced.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method and a device for processing network identification data.
Background
There are several identification systems around the world, such as the Handle system and the Domain Name Service (DNS) system. Among them, the Handle system has been deployed on the internet for more than 20 years, mainly for providing permanent and unique identification for digital content, while DNS is currently the most widely used service of the internet, mainly for mapping domain names to IP addresses for network routing.
At present, different identification systems cannot be fused, and the different identification systems need to operate independently, so that multiple sets of identification systems need to be built and maintained in practical application, and accordingly the construction cost is high and the maintenance cost is high.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for processing network identification data, so as to solve the problems of higher construction cost and higher maintenance cost in the current process of applying an identification system.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
the first aspect of the embodiments of the present invention discloses a method for processing network identification data, where the method includes:
acquiring a handle identifier to be converted;
in a Domain Name Service (DNS) analysis system, generating a prefix area corresponding to the naming authority of the handle identifier to be converted and generating a data area corresponding to the local name of the handle identifier to be converted;
storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area, wherein the data area information comprises: and the name of the data area corresponding to the data area and the address of the server.
Preferably, the method further comprises the following steps:
acquiring a handle identifier to be queried;
generating a prefix area name to be queried corresponding to the naming authority of the handle identifier to be queried;
acquiring data area information in a prefix area corresponding to the name of the prefix area to be queried from the DNS analysis system;
generating a name of the data area to be queried corresponding to the local name of the handle identifier to be queried;
determining a server address corresponding to the name of the prefix area to be queried by utilizing the data area information in the prefix area corresponding to the name of the prefix area to be queried;
and inquiring the handle identification data corresponding to the handle identification to be inquired from the corresponding server according to the name of the data area to be inquired and the server address corresponding to the name of the data area to be inquired.
Preferably, the storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area includes:
converting the naming authority of the handle identifier to be converted into DNS data by using a preset prefix protocol, and storing the DNS data and the data area information of the data area into the prefix area;
and converting the handle identification data corresponding to the handle identification to be converted into DNS data by using a preset data protocol, and storing the DNS data and the local name of the handle identification to be converted into the server corresponding to the data area.
Preferably, the generating a prefix area corresponding to the naming authority of the handle identifier to be converted and generating a data area corresponding to the local name of the handle identifier to be converted include:
judging whether the naming authority of the handle identifier to be converted meets a preset requirement, wherein the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and the domain name rule is met;
if the naming authority of the handle identifier to be converted meets the preset requirement, generating a prefix area corresponding to the naming authority of the handle identifier to be converted;
if the naming authority of the handle identifier to be converted does not meet the preset requirement, carrying out compression coding processing on the naming authority of the handle identifier to be converted and generating a corresponding prefix area;
judging whether the local name of the handle identifier to be converted meets the preset requirement or not;
if the local name of the handle identifier to be converted meets the preset requirement, generating a data area corresponding to the local name of the handle identifier to be converted;
and if the local name of the handle identifier to be converted does not meet the preset requirement, performing compression coding processing on the local name of the handle identifier to be converted and generating a corresponding data area.
Preferably, the process of generating the prefix region corresponding to the naming authority identified by the handle to be converted includes:
and exchanging the order of the authority levels of the naming authority of the handle identifier to be converted to generate a prefix area corresponding to the naming authority of the handle identifier to be converted.
Preferably, the obtaining, from the DNS resolution system, data area information in the prefix area corresponding to the prefix area name to be queried includes:
and carrying out TXT type query on the name of the prefix area to be queried in the DNS analysis system and analyzing to obtain the data area information in the corresponding prefix area.
Preferably, the querying, according to the server address corresponding to the name of the data area to be queried, handle identification data corresponding to the handle identification to be queried from a corresponding server includes:
and according to the name of the data area to be queried and the server address corresponding to the name, performing TXT type query and analysis on the corresponding server to obtain handle identification data corresponding to the handle identification to be queried.
A second aspect of the present invention discloses a device for processing network identification data, where the device includes:
the first obtaining unit is used for obtaining the handle identifier to be converted;
the first generating unit is used for generating a prefix area corresponding to the naming authority of the handle identifier to be converted and generating a data area corresponding to the local name of the handle identifier to be converted in a Domain Name Service (DNS) analysis system;
a storage unit, configured to store the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and store the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area, where the data area information includes: and the name of the data area corresponding to the data area and the address of the server.
Preferably, the apparatus further comprises:
the second obtaining unit is used for obtaining the handle identifier to be queried;
the second generating unit is used for generating a prefix area name to be queried corresponding to the naming authority of the handle identifier to be queried;
a third obtaining unit, configured to obtain, from the DNS resolution system, data area information in a prefix area corresponding to the prefix area name to be queried;
a third generating unit, configured to generate a name of the data area to be queried, where the name corresponds to the local name of the handle identifier to be queried;
a determining unit, configured to determine, by using data area information in a prefix area corresponding to the prefix area name to be queried, a server address corresponding to the prefix area name to be queried;
and the query unit is used for querying the handle identification data corresponding to the handle identification to be queried from the corresponding server according to the server address corresponding to the name of the data area to be queried.
Preferably, the storage unit is specifically configured to: converting the naming authority of the handle identifier to be converted into DNS data by using a preset prefix protocol, and storing the DNS data and the data area information of the data area into the prefix area; and converting the handle identification data corresponding to the handle identification to be converted into DNS data by using a preset data protocol, and storing the DNS data and the local name of the handle identification to be converted into the server corresponding to the data area.
Based on the foregoing method and apparatus for processing network identification data provided in the embodiments of the present invention, the method includes: acquiring a handle identifier to be converted; in a DNS analysis system, generating a prefix area corresponding to the naming authority of the handle identifier to be converted and generating a data area corresponding to the local name of the handle identifier to be converted; storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area. On the premise of not changing the DNS protocol and the handle protocol, the handle identifier is converted into the domain name identifier, and the handle identifier system does not need to be additionally constructed and maintained, so that the construction cost and the maintenance cost of the identifier system are reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for processing network identification data according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating a correspondence relationship between a prefix area and a data area according to an embodiment of the present invention;
fig. 3 is another flowchart of a method for processing network identification data according to an embodiment of the present invention;
fig. 4 is a flowchart of querying handle identification data according to an embodiment of the present invention;
fig. 5 is another flowchart of querying handle identification data according to an embodiment of the present invention;
fig. 6 is a block diagram of a processing apparatus for network identification data according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
As known from the background art, various identification systems exist around the world, such as a handle system and a Domain Name Service (DNS) system, but different identification systems cannot be fused and all the different identification systems need to operate independently, so that multiple sets of identification systems need to be built in practical application, which results in higher construction cost and higher maintenance cost.
Therefore, in the DNS resolution system, a prefix region corresponding to the naming authority of the handle identifier to be converted and a data region corresponding to the local name of the handle identifier to be converted are generated. Storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area. On the premise of not changing the DNS protocol and the handle protocol, the handle identifier is converted into the domain name identifier, and an additional construction and maintenance of a handle identifier system are not needed, so that the construction cost and the maintenance cost of the identifier system are reduced.
Referring to fig. 1, a flowchart of a processing method for network identification data according to an embodiment of the present invention is shown, where the processing method includes:
step S101: and acquiring a handle identifier to be converted.
In the process of specifically implementing the step S101, a handle identifier to be converted is obtained, where the handle identifier to be converted is a handle identifier that needs to be converted into a domain name identifier.
It should be noted that the handle identifier is mainly composed of two parts, which are respectively: a naming authority (also called a prefix) identified by a handle, and a unique local name (also called a suffix) under the naming authority.
The naming authority and local name of a handle identity are split by the "/" symbol of the ASCII character, so a handle identity can be defined as: < Handle > < Handle Name > "/" < Handle Local Name >.
Such as: "10.1045/january 99-bearman" is a handle identifier of an article in the D-Lib journal, the named authority of the handle identifier is "10.1045", and the local name of the handle identifier is "january 99-bearman".
Step S102: in the DNS analysis system, a prefix area corresponding to the naming authority of the handle identifier to be converted is generated, and a data area corresponding to the local name of the handle identifier to be converted is generated.
In the process of specifically implementing the step S102, in the DNS resolution system, the naming authority of the handle identifier to be converted is mapped to a prefix region of the DNS resolution service, and the local name of the handle identifier to be converted is mapped to a data region of the DNS resolution service, so that the handle identifier to be converted is converted into the domain name identifier.
It can be understood that, when a prefix region corresponding to the naming authority of the handle identifier to be converted and a data region corresponding to the local name are generated in the DNS resolution system, the naming authority and the local name need to meet a preset requirement, where the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and meets the domain name rule.
It should be noted that in the DNS protocol, the single-level length of the domain name cannot exceed 63 bytes, and characters such as "&" and ")" which do not conform to the domain name naming rule cannot appear, such as: www.123.com is a three-level domain name, where the level of "123" cannot exceed 63 bytes.
And in the specific process of generating the prefix area, judging whether the naming authority of the handle identifier to be converted meets the preset requirement, and if the naming authority of the handle identifier to be converted meets the preset requirement, generating the prefix area corresponding to the naming authority of the handle identifier to be converted.
And if the naming authority of the handle identifier to be converted does not meet the preset requirement, carrying out compression coding treatment on the naming authority of the handle identifier to be converted and generating a corresponding prefix area. That is, if the naming authority of the handle identifier to be converted does not meet the preset requirement, the naming authority of the handle identifier to be converted is compressed and encoded (i.e., integrated to generate a legal domain name) to make the naming authority meet the preset requirement, and then a processed prefix area corresponding to the naming authority is generated, where the prefix area has a corresponding prefix area name.
And similarly, in the process of specifically generating the data area, judging whether the local name of the handle identifier to be converted meets the preset requirement, if so, generating the data area corresponding to the local name of the handle identifier to be converted, and if not, performing compression coding processing on the local name of the handle identifier to be converted and generating a corresponding data area, wherein the data area has a corresponding data area name.
It should be noted that, in the handle system, naming authority has division of corresponding authority levels, and a tree structure is formed. Different from a DNS system, the authority level sequence of the naming authority of the handle system is from left to right, starts from the root node of the tree from top to bottom, and is connected to the label of the current node.
Therefore, when the prefix region of the DNS analysis service corresponding to the naming authority of the handle identifier to be converted is generated, the order of the authority levels of the naming authority of the handle identifier to be converted is exchanged, and the prefix region corresponding to the naming authority of the handle identifier to be converted is generated.
Such as: assuming that the handle to be converted is marked as '10.1045/january 99-bearrman' and the naming authority is '10.1045', when a prefix region corresponding to the naming authority of the handle is generated, firstly, the order of the authority levels of the naming authority is adjusted to '1045.10', then the prefix region corresponding to the authority levels is generated, and the name of the prefix region corresponds to the adjusted naming authority '1045.10'.
Step S103: storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area.
It should be noted that the data area corresponds to a server, and the server stores data corresponding to the data area, so the data area information of the data area includes: the data area name corresponding to the data area and the server address (IP address) of the server.
In the process of implementing step S103 specifically, after a prefix region corresponding to the naming authority of the handle identifier to be converted and a data region corresponding to the local name are generated, the specified information is stored in the prefix region and the data region according to the TXT data type of the DNS. The specific storage mode is as follows: and converting the naming authority of the handle identifier to be converted into DNS data by using a preset prefix protocol, and storing the DNS data and the data area information of the data area into a prefix area corresponding to the naming authority. That is, naming authority and data area information corresponding to a handle identifier may be stored in a prefix area corresponding to the handle identifier.
Similarly, the handle identification data corresponding to the handle identification to be converted is converted into DNS data by using a preset data protocol, and the DNS data and the local name of the handle identification to be converted are stored in the server corresponding to the data area (the data area corresponding to the local name). That is, the local name and the handle identification data corresponding to a handle identifier are stored in the server corresponding to the data area corresponding to the handle identifier.
It should be noted that the prefix protocol is a protocol for converting naming authority of the handle identifier into DNS data, and the data protocol is a protocol for converting the handle identifier data of the handle identifier into DNS data.
It can be understood that, in the process of storing the naming authority and the data area information corresponding to the handle identifier to be converted into the prefix area by using the prefix protocol, there may be a case where the prefix area names corresponding to a plurality of handle identifiers to be converted are the same, that is, a plurality of pieces of data may be stored in the prefix area, and each piece of data is composed of the naming authority and the data area information corresponding to the handle identifier to be converted.
Therefore, the specific contents of the prefix protocol are as follows: each piece of data stored in the prefix area consists of naming authority and data area information corresponding to the handle identifier to be converted, and the naming authority and the data area information are separated by a space. The data area information corresponding to each piece of data may include data area information corresponding to multiple data areas, and each piece of data in the prefix area is distinguished by a specified keyword (for example, the keyword src N, where N is a natural number). That is, the prefix protocol supports a combination of pieces of data, thereby solving a problem of collision of prefix region names due to an algorithm of compression encoding.
Such as: assuming that the naming authority identified by the handle to be converted is "10.1045", the data stored in the prefix region (prefix region name is "1045.10") corresponding to the naming authority is: 1045.10TXT 3600 "src 0: 10.1045 data-zone: IP1january99-bearman. local0; data-zone: ip2data1.local1 ".
Similarly, in the process of storing the local name and the handle identification data corresponding to the handle identification to be converted to the server corresponding to the data area by using the data protocol, the names of the data areas corresponding to a plurality of handle identifications to be converted may be the same, that is, a plurality of pieces of data may be stored in the server of the data area, and each piece of data is composed of the local name and the handle identification data corresponding to the handle identification to be converted.
Therefore, the specific contents of the data protocol are as follows: each piece of data corresponding to the data area and stored in the server corresponding to the data area is composed of a local name and handle identification data corresponding to a handle identification to be converted, and the local name and the handle identification data are separated by a space. The handle identification data may include handle identification data of multiple handle data types, and each piece of data corresponding to the data area is distinguished by a specified keyword (for example, the keyword srcN, where N is a natural number). That is, the data protocol supports a combination of a plurality of pieces of data, thereby solving a problem of collision of data area names due to an algorithm of compression encoding.
It can be understood that the handle identification data in each piece of data corresponding to the data area at least consists of an INDEX, a handle data type, a handle data life cycle, a handle data authority, a data format, specific data content and the like, and each part is separated by a space.
Such as: assuming that the local name of the handle identifier to be converted is "january 99-bearman. local", in the server corresponding to the data area corresponding to the local name, the stored data corresponding to the data area is: january99-bearman. localtxt 3600 "src 0: january 99-bearrmardata 0:1URL 36001110UTF 8http:// www.bearman.us data1:2EMAIL 36001110UTF 8admin @ test.
And converting the handle identifier to be converted into the domain name identifier through the prefix protocol and the data protocol.
To better explain the corresponding relationship between the prefix area and the data area, the corresponding relationship between the prefix area and the data area is illustrated by the schematic diagram of fig. 2.
In fig. 2, naming authority identified by a handle is mapped to a prefix region of DNS resolution service, a local name identified by the handle is mapped to a data region of DNS resolution service, data stored in the prefix region are data region names (names of data region 1 and data region 2 in fig. 2) and corresponding server addresses (IP 1 and IP2 in fig. 2), each data region corresponds to a corresponding server, for example, data region 1 in fig. 2 corresponds to a server with an address of IP1, and data region 2 corresponds to a server with an address of IP 2.
In the embodiment of the invention, in the DNS analysis system, a prefix area corresponding to the naming authority of the handle identifier to be converted and a data area corresponding to the local name of the handle identifier to be converted are generated. Storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area. On the premise of not changing the DNS protocol and the handle protocol, the handle identifier is converted into the domain name identifier, and the handle identifier system does not need to be additionally constructed and maintained, so that the construction cost and the maintenance cost of the identifier system are reduced.
To better explain the contents shown in fig. 1 of the above embodiment of the present invention, the contents shown in fig. 3 are used for example, and it should be noted that fig. 3 is used for example only.
Referring to fig. 3, another flowchart of a processing method for network identification data according to an embodiment of the present invention is shown, where the processing method includes:
step S301: and acquiring a handle identifier to be converted.
Step S302: and determining whether the naming authority of the handle identifier to be converted meets the preset requirement. If the naming authority meets the preset requirement, go to step S304, and if the naming authority does not meet the preset requirement, go to step S303.
It should be noted that the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and meets the domain name naming rule.
Step S303: and performing compression coding processing on the naming authority of the handle identifier to be converted, and executing the step S304.
Step S304: and generating a prefix area corresponding to the naming authority of the handle identifier to be converted.
Step S305: and determining whether the local name of the handle identifier to be converted meets the preset requirement. If the local name meets the preset requirement, go to step S307, and if the local name does not meet the preset requirement, go to step S306.
Step S306: and performing compression coding processing on the local name of the handle identifier to be converted, and executing step S307.
Step S307: and generating a data area corresponding to the local name of the handle identifier to be converted.
Step S308: and storing the naming authority of the handle identifier to be converted and the data area information of the data area into the corresponding prefix area by using a prefix protocol.
Step S309: and storing the handle identification data and the local name corresponding to the handle identification to be converted into the server corresponding to the data area by using a data protocol.
It should be noted that, the execution principle of step S301 to step S309 refers to the content shown in fig. 1 in the above embodiment of the present invention, and is not described herein again.
As can be seen from the contents shown in fig. 1 to fig. 3 in the above embodiments of the present invention, in the DNS resolution system, a handle identifier is converted into a domain name identifier, and similarly, handle identifier data corresponding to the handle identifier may also be queried in the DNS resolution system by using the naming authority and the local name of the handle identifier.
Preferably, referring to fig. 4, a flowchart of querying handle identification data provided by the embodiment of the present invention is shown, where the flowchart includes the following steps:
step S401: and acquiring a handle identifier to be queried.
In the process of specifically implementing step S401, a handle identifier to be queried is obtained, where the handle identifier to be queried is an identifier of handle identifier data that needs to be queried in the DNS resolution system, that is, the handle identifier is queried in the DNS resolution system.
Step S402: and generating a prefix area name to be queried corresponding to the naming authority of the handle identifier to be queried.
In the process of specifically implementing the step S402, the naming authority of the handle identifier to be queried is obtained, and it is determined whether the naming authority of the handle identifier to be queried meets a preset requirement, where the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and meets the domain name rule.
And if the naming authority of the handle identifier to be queried meets the preset requirement, generating a prefix area name to be queried (namely the name of the prefix area of the DNS analysis service) corresponding to the naming authority of the handle identifier to be queried.
And if the naming authority of the handle identifier to be queried does not meet the preset requirement, performing compression coding on the naming authority of the handle identifier to be queried and then generating a corresponding prefix area name to be queried.
Step S403: and acquiring data area information in the prefix area corresponding to the name of the prefix area to be inquired from the DNS analysis system.
In the process of implementing step S403 specifically, a prefix region name to be queried is utilized to perform TXT type query and resolution in the DNS resolution system, and data region information and naming authority in the prefix region corresponding to the prefix region name to be queried are acquired.
Preferably, in the process of performing TXT type query in the DNS resolution system by using the prefix area name to be queried, the data fed back by the DNS resolution system is resolved by using a prefix protocol (see the content in step S103 in fig. 1 in the embodiment of the present invention described above), so as to obtain corresponding data area information and naming authority, and at this time, it is determined whether the obtained naming authority is consistent with the naming authority identified by the handle to be queried.
And if the obtained naming authority is consistent with the naming authority of the handle identifier to be inquired, determining to acquire the data area information in the prefix area corresponding to the prefix area name to be inquired, and executing the subsequent steps.
And if the obtained naming authority is not consistent with the naming authority of the handle identifier to be inquired, ending the process.
That is, whether the query result is correct is verified by comparing the consistency of the naming authority of the handle identifier to be queried with the naming authority fed back by the DNS resolution system, the subsequent process is continuously executed if the query result is correct, and the process is terminated if the query result is incorrect.
Step S404: and generating a name of the data area to be queried corresponding to the local name of the handle identifier to be queried.
In the process of specifically implementing the step S404, the local name of the handle identifier to be queried is obtained, and it is determined whether the local name of the handle identifier to be queried meets a preset requirement.
And if the local name of the handle identifier to be queried meets the preset requirement, generating a name of the data area to be queried (namely the name of the data area of the DNS analysis service) corresponding to the local name of the handle identifier to be queried.
And if the local name of the handle identifier to be queried does not meet the preset requirement, performing compression coding processing on the local name of the handle identifier to be queried and then generating a corresponding name of the data area to be queried.
Step S405: and determining the server address corresponding to the name of the data area to be inquired by utilizing the data area information in the prefix area corresponding to the name of the prefix area to be inquired.
As can be seen from the content shown in fig. 1 in the embodiment of the present invention, the data area information stored in the prefix area includes the data area name and the server address of the server corresponding to the data area name, and in the process of the specific implementation step S405, corresponding data area information is obtained from the prefix area corresponding to the prefix area name to be queried, that is, the corresponding relationship between each data area name and the server address stored in the prefix area is obtained.
And determining the server address corresponding to the name of the data area to be inquired from the data area information acquired from the prefix area corresponding to the name of the prefix area to be inquired.
Step S406: and inquiring the handle identification data corresponding to the handle identification to be inquired from the corresponding server according to the name of the data area to be inquired and the server address corresponding to the data area to be inquired.
In the process of implementing step S406 specifically, according to the server address corresponding to the name of the data area to be queried, in combination with the name of the data area to be queried, a TXT class query is performed and analyzed from the server corresponding to the server address, and handle identification data and a local name corresponding to the handle identification to be queried are obtained. That is to say, a server corresponding to the server address corresponding to the name of the data area to be queried is determined, and then the handle identification data and the local name corresponding to the handle identification to be queried are obtained by querying the server by using the name of the data area to be queried.
Preferably, during the process of performing TXT type query from a corresponding server by using the name of the data area to be queried and the server address corresponding to the name of the data area to be queried, the data fed back by the server is analyzed by using a data protocol (see the content in step S103 in fig. 1 in the embodiment of the present invention described above), so as to obtain corresponding handle identification data and a local name, and at this time, it is determined whether the obtained local name is consistent with the local name identified by the handle to be queried.
And if the obtained local name is consistent with the local name of the handle identifier to be queried, determining to obtain the handle identifier data corresponding to the handle identifier to be queried.
And if the obtained local name is not consistent with the local name of the handle identifier to be inquired, ending the process.
That is to say, whether the query result is correct is verified by comparing the consistency between the local name identified by the handle to be queried and the local name fed back by the server.
It can be understood that after the handle identification data corresponding to the handle identification to be queried is obtained, the handle identification data of the specified handle data type can be selected according to actual requirements.
To better explain the contents of the above steps S401 to S406, a handle to be queried, which is "10.1045/january 99-bearman", is taken as an example, and is exemplified by the following procedures a1 to a 4.
And A1, generating a prefix area name "1045.10" to be queried corresponding to the naming authority (10.1045) identified by the handle to be queried. TXT type query is carried out in a DNS analysis system by utilizing '1045.10', data area information and naming authority in a prefix area corresponding to a prefix area name to be queried are obtained, and a query result fed back by the DNS analysis system is as follows: 1045.10TXT 3600 "src 0: 10.1045 data-zone: IP1january99-bearman. local0; data-zone: IP2data1.local1 ".
A2, verifying whether the naming authority fed back by the DNS analysis system is '10.1045', if so, continuing to execute the subsequent process, and if not, ending the process.
A3, generating a local name january99-bearman. local0 of the data area to be queried corresponding to the local name of the handle identifier to be queried, determining a server address corresponding to the january99-bearman. local0 in the data area information, performing TXT type query and analysis on the server corresponding to the server address by using the local name of the handle identifier to be queried, and obtaining the handle identifier data and the local name corresponding to the handle identifier to be queried, wherein the query result fed back by the server is as follows: january99-bearman. local0txt3600 "src 0: january 99-beararmandida 0:1URL 36001110UTF 8http:// www.bearman.us data1:2EMAIL 36001110UTF 8admin @ test.
A4, verifying whether the local name fed back by the server is 'january 99-bearman', if not, ending the process, if so, selecting handle identification data of a specified handle data type, such as URL data 'http:// www.bearman.us'.
In the embodiment of the invention, the handle identifier to be queried is utilized to perform handle query in the DNS analysis system, and the handle identifier data corresponding to the handle identifier to be queried is obtained, so that a handle identifier system does not need to be additionally built and maintained, the construction cost and the maintenance cost of the identifier system are reduced, the correctness of a query result is verified in the query process, and the consistency of query and feedback is ensured.
To better explain the embodiment of the present invention as shown in fig. 4, the embodiment is illustrated by the contents shown in fig. 5, and it should be noted that fig. 5 is only used for example.
Referring to fig. 5, another flowchart of querying handle identification data provided by the embodiment of the present invention is shown, including the following steps:
step S501: and acquiring the naming authority of the handle identifier to be queried.
Step S502: and if the naming authority of the handle identifier to be inquired meets the preset requirement, executing step S504, and if not, executing step S503.
It should be noted that the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and meets the domain name naming rule.
Step S503: and performing compression coding processing on the naming authority identified by the query handle, and executing step S504.
Step S504: and generating the name of the prefix area to be queried corresponding to the naming authority of the handle identifier to be queried.
Step S505: and carrying out TXT type query in the DNS by using the prefix area name to be queried.
Step S506: and verifying whether the naming authority of the handle identifier to be inquired is consistent with the naming authority fed back by the DNS analysis system, if so, executing the step S507, and if not, ending the process.
Step S507: and acquiring data area information in the prefix area corresponding to the name of the prefix area to be inquired.
Step S508: and (5) whether the local name of the handle identifier to be inquired accords with a preset requirement, if not, executing a step (S509), and if so, executing a step (S510).
Step S509: and performing compression coding processing on the local name identified by the handle to be queried, and executing step S510.
Step S510: and generating a name of the data area to be queried corresponding to the local name of the handle identifier to be queried.
Step S511: and determining the server address corresponding to the name of the data area to be inquired by utilizing the data area information in the prefix area corresponding to the name of the prefix area to be inquired.
Step S512: and carrying out TXT type query on the corresponding server according to the name of the data area to be queried and the server address corresponding to the name.
Step S513: and verifying whether the local name of the handle identifier to be queried is consistent with the local name fed back by the server, if so, executing the step S514, and if not, ending the process.
Step S514: and acquiring the handle identification data of the specified handle data type corresponding to the handle identification to be inquired.
It should be noted that, for the execution principle of steps S501 to S514, reference may be made to the content in fig. 4 in the above embodiment of the present invention, and details are not described herein again.
Corresponding to the method for processing network identification data provided in the foregoing embodiment of the present invention, referring to fig. 6, an embodiment of the present invention further provides a block diagram of a processing apparatus for network identification data, where the processing apparatus includes: a first acquisition unit 601, a first generation unit 602, and a storage unit 603;
the first obtaining unit 601 is configured to obtain a handle identifier to be converted.
The first generating unit 602 is configured to generate, in the DNS resolution system, a prefix region corresponding to a naming authority of a handle identifier to be converted, and generate a data region corresponding to a local name of the handle identifier to be converted.
In a specific implementation, the first generating unit 602 is specifically configured to: judging whether the naming authority of the handle identifier to be converted meets a preset requirement, wherein the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and the domain name naming rule is met; if the naming authority of the handle identifier to be converted meets the preset requirement, generating a prefix area corresponding to the naming authority of the handle identifier to be converted; if the naming authority of the handle identifier to be converted does not meet the preset requirement, carrying out compression coding processing on the naming authority of the handle identifier to be converted and generating a corresponding prefix area; judging whether the local name of the handle identifier to be converted meets the preset requirement or not; if the local name of the handle identifier to be converted meets the preset requirement, generating a data area corresponding to the local name of the handle identifier to be converted; and if the local name of the handle identifier to be converted does not meet the preset requirement, performing compression coding processing on the local name of the handle identifier to be converted and generating a corresponding data area.
In another specific implementation, the first generating unit 602, configured to generate the prefix region corresponding to the naming authority identified by the handle to be converted, is specifically configured to: and exchanging the order of the authority levels of the naming authority of the handle identifier to be converted to generate a prefix area corresponding to the naming authority of the handle identifier to be converted.
The storage unit 603 is configured to store the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and store the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area, where the data area information includes: and the name of the data area corresponding to the data area and the address of the server.
In a specific implementation, the storage unit 603 is specifically configured to: converting the naming authority of the handle identifier to be converted into DNS data by using a preset prefix protocol, and storing the DNS data and the data area information of the data area into a prefix area; and converting the handle identification data corresponding to the handle identification to be converted into DNS data by using a preset data protocol, and storing the DNS data and the local name of the handle identification to be converted into a server corresponding to the data area.
In the embodiment of the invention, in the DNS analysis system, a prefix area corresponding to the naming authority of the handle identifier to be converted and a data area corresponding to the local name of the handle identifier to be converted are generated. Storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area. On the premise that the DNS protocol and the handle protocol do not need to be changed, the handle identifier is converted into the domain name identifier, a handle identifier system does not need to be additionally built and maintained, and the construction cost and the maintenance cost of the identifier system are reduced.
Preferably, in combination with the content shown in fig. 6, the processing apparatus further includes: the second acquiring unit, the second generating unit, the third acquiring unit, the third generating unit, the determining unit and the inquiring unit have the following specific execution principles:
and the second obtaining unit is used for obtaining the handle identifier to be queried.
And the second generating unit is used for generating the prefix area name to be queried corresponding to the naming authority of the handle identifier to be queried.
And the third acquisition unit is used for acquiring the data area information in the prefix area corresponding to the name of the prefix area to be inquired from the DNS analysis system.
In a specific implementation, the third obtaining unit is specifically configured to: and carrying out TXT type query on the name of the prefix area to be queried and analyzing to obtain the data area information in the corresponding prefix area from the DNS analysis system.
And the third generating unit is used for generating the name of the data area to be queried corresponding to the local name of the handle identifier to be queried.
And the determining unit is used for determining the server address corresponding to the name of the prefix area to be inquired by utilizing the data area information in the prefix area corresponding to the name of the prefix area to be inquired.
And the query unit is used for querying the handle identification data corresponding to the handle identification to be queried from the corresponding server according to the server address corresponding to the name of the data area to be queried.
In a specific implementation, the query unit is specifically configured to: and according to the name of the data area to be inquired and the server address corresponding to the name, carrying out TXT type inquiry and analysis from the corresponding server to obtain handle identification data corresponding to the handle identification to be inquired.
In the embodiment of the invention, the handle identifier to be queried is utilized to perform handle query in the DNS analysis system, and the handle identifier data corresponding to the handle identifier to be queried is obtained, so that a handle identifier system does not need to be additionally constructed and maintained, and the construction cost and the maintenance cost of the identifier system are reduced.
In summary, embodiments of the present invention provide a method and an apparatus for processing network identifier data, in a DNS resolution system, a prefix region corresponding to a naming authority of a handle identifier to be converted is generated, and a data region corresponding to a local name of the handle identifier to be converted is generated. Storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area. On the premise that the DNS protocol and the handle protocol do not need to be changed, the handle identifier is converted into the domain name identifier, a handle identifier system does not need to be additionally built and maintained, and the construction cost and the maintenance cost of the identifier system are reduced.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for processing network identification data, the method comprising:
acquiring a handle identifier to be converted;
in a Domain Name Service (DNS) analysis system, generating a prefix area corresponding to the naming authority of the handle identifier to be converted and generating a data area corresponding to the local name of the handle identifier to be converted;
storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into a server corresponding to the data area, wherein the data area information comprises: and the name of the data area corresponding to the data area and the address of the server.
2. The method of claim 1, further comprising:
acquiring a handle identifier to be queried;
generating a prefix area name to be queried corresponding to the naming authority of the handle identifier to be queried;
acquiring data area information in a prefix area corresponding to the name of the prefix area to be queried from the DNS analysis system;
generating a name of the data area to be queried corresponding to the local name of the handle identifier to be queried;
determining a server address corresponding to the name of the prefix area to be queried by utilizing the data area information in the prefix area corresponding to the name of the prefix area to be queried;
and inquiring the handle identification data corresponding to the handle identification to be inquired from the corresponding server according to the name of the data area to be inquired and the server address corresponding to the name of the data area to be inquired.
3. The method according to claim 1, wherein the storing the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and storing the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area comprises:
converting the naming authority of the handle identifier to be converted into DNS data by using a preset prefix protocol, and storing the DNS data and the data area information of the data area into the prefix area;
and converting the handle identification data corresponding to the handle identification to be converted into DNS data by using a preset data protocol, and storing the DNS data and the local name of the handle identification to be converted into the server corresponding to the data area.
4. The method according to claim 1, wherein the generating a prefix region corresponding to the naming authority of the handle identifier to be converted and generating a data region corresponding to the local name of the handle identifier to be converted include:
judging whether the naming authority of the handle identifier to be converted meets a preset requirement, wherein the preset requirement is that the single-stage length of the domain name is less than or equal to 63 bytes and the domain name rule is met;
if the naming authority of the handle identifier to be converted meets the preset requirement, generating a prefix area corresponding to the naming authority of the handle identifier to be converted;
if the naming authority of the handle identifier to be converted does not meet the preset requirement, carrying out compression coding processing on the naming authority of the handle identifier to be converted and generating a corresponding prefix area;
judging whether the local name of the handle identifier to be converted meets the preset requirement or not;
if the local name of the handle identifier to be converted meets the preset requirement, generating a data area corresponding to the local name of the handle identifier to be converted;
and if the local name of the handle identifier to be converted does not meet the preset requirement, performing compression coding processing on the local name of the handle identifier to be converted and generating a corresponding data area.
5. The method according to claim 4, wherein the step of generating the prefix region corresponding to the naming authority identified by the handle to be converted includes:
and exchanging the order of the authority levels of the naming authority of the handle identifier to be converted to generate a prefix area corresponding to the naming authority of the handle identifier to be converted.
6. The method according to claim 2, wherein the obtaining, from the DNS resolution system, data area information in the prefix area corresponding to the prefix area name to be queried includes:
and carrying out TXT type query on the name of the prefix area to be queried in the DNS analysis system and analyzing to obtain the data area information in the corresponding prefix area.
7. The method according to claim 2, wherein the querying, according to the server address corresponding to the name of the data area to be queried, handle identification data corresponding to the handle identification to be queried from a corresponding server includes:
and according to the name of the data area to be queried and the server address corresponding to the name, performing TXT type query and analysis on the corresponding server to obtain handle identification data corresponding to the handle identification to be queried.
8. An apparatus for processing network identification data, the apparatus comprising:
the first obtaining unit is used for obtaining the handle identifier to be converted;
the domain name service DNS processing system comprises a first generation unit and a second generation unit, wherein the first generation unit is used for generating a prefix area corresponding to the naming authority of the handle identifier to be converted and a data area corresponding to the local name of the handle identifier to be converted in a domain name service DNS analysis system;
a storage unit, configured to store the naming authority of the handle identifier to be converted and the data area information of the data area into the prefix area, and store the handle identifier data and the local name corresponding to the handle identifier to be converted into the server corresponding to the data area, where the data area information includes: and the name of the data area corresponding to the data area and the address of the server.
9. The apparatus of claim 8, further comprising:
the second obtaining unit is used for obtaining the handle identifier to be queried;
the second generating unit is used for generating a prefix area name to be queried corresponding to the naming authority of the handle identifier to be queried;
a third obtaining unit, configured to obtain, from the DNS resolution system, data area information in a prefix area corresponding to the prefix area name to be queried;
a third generating unit, configured to generate a name of the data area to be queried, where the name corresponds to the local name of the handle identifier to be queried;
a determining unit, configured to determine, by using data area information in a prefix area corresponding to the prefix area name to be queried, a server address corresponding to the prefix area name to be queried;
and the query unit is used for querying the handle identification data corresponding to the handle identification to be queried from the corresponding server according to the server address corresponding to the name of the data area to be queried.
10. The apparatus according to claim 8, wherein the storage unit is specifically configured to: converting the naming authority of the handle identifier to be converted into DNS data by using a preset prefix protocol, and storing the DNS data and the data area information of the data area into the prefix area; and converting the handle identification data corresponding to the handle identification to be converted into DNS data by using a preset data protocol, and storing the DNS data and the local name of the handle identification to be converted into the server corresponding to the data area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110229285.6A CN112822307B (en) | 2021-03-02 | 2021-03-02 | Network identification data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110229285.6A CN112822307B (en) | 2021-03-02 | 2021-03-02 | Network identification data processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112822307A CN112822307A (en) | 2021-05-18 |
| CN112822307B true CN112822307B (en) | 2022-08-12 |
Family
ID=75862680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110229285.6A Active CN112822307B (en) | 2021-03-02 | 2021-03-02 | Network identification data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112822307B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116170403A (en) * | 2023-01-09 | 2023-05-26 | 中国互联网络信息中心 | Method and device for decentralized domain name resolution based on Handle system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2103035A1 (en) * | 2006-11-13 | 2009-09-23 | Telefonaktiebolaget LM Ericsson (PUBL) | Method and arrangement in an internet protocol multimedia subsystem |
| CN103491145A (en) * | 2013-09-09 | 2014-01-01 | 中国科学院计算机网络信息中心 | Analytic method and system of internet-of-things isomerism identification |
| CN112187967A (en) * | 2020-09-28 | 2021-01-05 | 中国互联网络信息中心 | Identification analysis method and device for whole networking |
-
2021
- 2021-03-02 CN CN202110229285.6A patent/CN112822307B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2103035A1 (en) * | 2006-11-13 | 2009-09-23 | Telefonaktiebolaget LM Ericsson (PUBL) | Method and arrangement in an internet protocol multimedia subsystem |
| CN103491145A (en) * | 2013-09-09 | 2014-01-01 | 中国科学院计算机网络信息中心 | Analytic method and system of internet-of-things isomerism identification |
| CN112187967A (en) * | 2020-09-28 | 2021-01-05 | 中国互联网络信息中心 | Identification analysis method and device for whole networking |
Non-Patent Citations (2)
| Title |
|---|
| Handle System Overview;S. Sun等;《IETF rfc3650》;20031130;全文 * |
| 王峰 ; 孙洵.Handle-DNS名字服务系统的设计与实现.《微电子学与计算机》.2004, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112822307A (en) | 2021-05-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11632353B2 (en) | Delegating DNS records to additional providers | |
| CN106933871B (en) | Short link processing method and device and short link server | |
| CN109981595B (en) | Resource acquisition method, resource return method, server and storage medium | |
| CN109729183B (en) | Request processing method, device, equipment and storage medium | |
| CN104283723B (en) | Network access log processing method and processing device | |
| JP2019507994A (en) | Method and apparatus for intelligent domain name system transfer | |
| KR20020082461A (en) | Network address server | |
| CN112347377B (en) | IP address field searching method, service scheduling method, device and electronic equipment | |
| CN1430749A (en) | System and methods of accessing network resources | |
| JP2004532538A (en) | Apparatus, method and system for directory quality assurance | |
| JP4975926B2 (en) | Network address server | |
| CN105554169B (en) | OID configuration and analysis method, ORS client, OID node and database thereof | |
| CN107786678B (en) | Domain name resolution method, device and system | |
| US20130311678A1 (en) | Method of encoding a data identifier | |
| CN112954089B (en) | Method, device, equipment and storage medium for analyzing data | |
| CN112887451B (en) | Domain name resolution method and device and computer equipment | |
| CN112822307B (en) | Network identification data processing method and device | |
| CN111010456B (en) | Main domain name acquisition and verification method | |
| CN109120740B (en) | Server, system and method for generating IPv6 address | |
| CN107733709A (en) | Date storage method, device and electronic equipment | |
| CN114978740B (en) | Identification association and verification analysis method based on block chain | |
| US20150039724A1 (en) | Methods and systems for recommending top level domains | |
| CN108366136B (en) | Domain name resolution method and device | |
| CN114039801B (en) | Short link generation method, short link analysis system, short link analysis equipment and storage medium | |
| CN114338630B (en) | Domain name access method, device, electronic equipment, storage medium and program product |
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 |