CN109561161B - Name registration and analysis method based on space-time constraint field - Google Patents
Name registration and analysis method based on space-time constraint field Download PDFInfo
- Publication number
- CN109561161B CN109561161B CN201710874886.6A CN201710874886A CN109561161B CN 109561161 B CN109561161 B CN 109561161B CN 201710874886 A CN201710874886 A CN 201710874886A CN 109561161 B CN109561161 B CN 109561161B
- Authority
- CN
- China
- Prior art keywords
- node
- name
- request
- resolution
- lrnj
- 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/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a name registration and analysis method based on a space-time constraint field, which comprises the following steps: according to the measurement index parameter set { Ti }; dividing the space of the network nodes, wherein each given Ti corresponds to a Ci-level container layer; for an entity name registration request with special time delay, selecting a node LRNj according to a spatial position, and performing field name registration on an analysis node of a C1 level container where the LRNj is located; for an entity registration request restricted to a domain, its field name registration is from the LRNj up the tree structure until the top container CI where the LRNj is located; directly entering the existing general system to carry out name registration for an unconstrained entity registration request; the name resolution request under the special time delay requirement completes the field name resolution processing in a bottom-layer C1 level container where the LRNj is located; the intra-domain name resolution request completes name resolution processing in a top-layer container CI where the LRNj is located; the unconstrained name resolution request directly enters the existing generic system to complete the name resolution process.
Description
Technical Field
The invention belongs to the technical field of network technology and communication information, and particularly relates to a name registration and analysis method based on a space-time constraint field.
Background
The TCP/IP internet system is difficult to adapt to the development trend of future networks, and particularly difficult to meet the development requirements of new applications such as mobile access, pervasive computing, distributed information processing, mass streaming media, and the like. In order to improve user experience, researchers propose an information-centric networking ICN, which decouples information names from network locations to enhance network performance in various aspects, including mobility, extensibility, real-time, and dynamic. In an information center network ICN, the information name is required to have aggregability and persistence so as to avoid the problem of expansion of a routing table and ensure that the information name does not change along with the position. At present, mobile network users reach three billion, video newly generated every day exceeds five billion, and billions of Internet of things equipment are accessed in the future. Storing and indexing trillion-level entity names, updating entity addresses instantly tens of thousands of times per second, querying entity current addresses millions of times per second, and having severe requirements on searching time delay, and the pressure on storing, querying and updating of a name registration and resolution system is far beyond a hierarchical distributed domain name system, which may cause serious performance problems.
The information center network ICN has the characteristic of physical distribution, whether a method for dividing and organizing information and resources according to domains can be provided according to the characteristic, a global address resolution system is divided into a plurality of subsystems according to needs to improve resolution rate, different QoS (quality of service) under different application scenes, especially time delay and reliability needs are met, and how to keep the characteristics of elasticity and autonomy of the information center network is a key problem to be solved urgently by the information center network ICN. Since in an information centric networking ICN, names are separated from locations. Registration and resolution is to register one or more dynamic network addresses with the name of the information or information provider and to resolve from the name of the information to the network address or location of the information provider. That is, the name resolution system is used to establish, maintain, and publish a mapping relationship between information names and addresses or information providers where the information is located, and all information names are mapped to the same namespace for identification. The basis of the name resolution system is a naming method which is mainly divided into two types: the hierarchical naming is the first one, and the flat naming is the second one.
The analytic process based on hierarchical naming guarantees the routing efficiency, but the expansibility is very limited. In the current internet, the equivalent of a name resolution system is DNS, which is a typical hierarchical naming system for multi-level domain names. Because the names are not evenly distributed across the top-level domain, the load on the resolution servers is not balanced. Meanwhile, the structure also has the security problems of DOS attack and the like which are difficult to avoid. The NDN is a typical hierarchical naming system, and in the hierarchical naming system, a parsing process generally starts from a root node, which brings great constraints to the parsing system. Some current research on DNS shows that the hierarchical naming system presents more and more problems under the condition of the growth of massive user requests.
The parsing process based on flat naming guarantees the extensibility and security of names, but poses more challenges to parsing and routing efficiency. In a flat naming system, a semantic independent naming method can ensure the decoupling of content and position and has advantages in a safety method. One possible solution to the problem of hierarchical resolution based on flattened naming is to use Distributed Hash Table (DHT) techniques, such as using a schema or Chord, for mapping content to name. In the DHT, the typical searching complexity is log (N), wherein N is the scale of the nodes in the network, and the method can effectively improve the searching efficiency and reduce the scale of the content required to be maintained by each node. However, because the DHT structure is a flat structure, when the content size is large, the amount of information to be maintained in the DHT routing table of the distributed hash table is very large, and especially in a mobile environment, when the content location changes, the maintenance process of the DHT structure of the distributed hash table may bring a large burden to the entire network.
Therefore, it is necessary to construct a name registration and analysis method based on a space-time constraint field, and implement efficient name-to-address query through security isolation for device registration and content distribution in different scenarios, so as to meet the requirements for QoS in different application scenarios, and solve the problems of scalability and security, so as to adapt to the development of future networks.
Disclosure of Invention
The invention aims to solve the problems of the existing name registration and analysis method, and provides a time-space constraint field-based name registration and analysis method, which solves the problems of expandability and safety of name analysis in an Information Center Network (ICN) so as to meet different requirements on QoS (quality of service) in different application scenes.
The method comprises the following steps:
according to a network measurement index parameter set { Ti }; wherein, Ti is less than Ti +1, I is more than or equal to 1 and less than or equal to I-1, and I is a constant; carrying out space division on network nodes, so that each given Ti corresponds to a container level and is marked as a Ci-level container;
from any local resolution node LRNj, the bottom-up nested space is divided into a C1-level container, a C2-level container, a … -level container and a CI-level container to form a tree structure;
the process of executing different field name registration aiming at three scenes of special time delay, intra-domain and unconstrained is as follows:
for any entity name registration request with special time delay, selecting a node LRNj according to the spatial position, and performing field name registration on an analysis node of a C1 level container where the node LRNj is located;
for an entity registration request restricted to a domain, its field name registration is from the node LRNj up the tree structure until the top container CI where the node LRNj is located; registering on an analysis node of a Ck level container where each LRNj is located, wherein k is more than or equal to 2 and less than or equal to I;
directly entering the existing general system to carry out name registration for an unconstrained entity registration request; the existing general system is an existing analytic system comprising direct mapping DMAP;
different name resolution processes are executed aiming at three scenes, namely special time delay, intra-domain and unconstrained scene, as follows:
the name resolution request under the special time delay requirement is subjected to field name resolution processing in a bottom-layer C1-level container where the LRNj is located;
the intra-domain name resolution request completes name resolution processing in a top-level CI (public interface) container where the LRNj is located;
the unconstrained name resolution request directly enters the existing generic system to complete the name resolution process.
In the above technical solution, the name registration and resolution for three scenarios, including special time delay, intra-domain, and unconstrained, specifically includes:
step 1) checking and determining the type of received request, the request type comprising: special time delay, intra-domain and unconstrained scenes;
step 2) judging whether the request type in the step 1) is a name resolution request or not and whether the request type is a name registration request or not; if the request type is a name resolution request and not a name registration request, turning to step 3); if the request type name registration request is not a name resolution request, directly jumping to the step 6);
step 3) judging whether the name resolution request in the step 2) is a name resolution request under the special time delay requirement: if the name resolution request under the special time delay requirement exists, executing a name resolution process under the special time delay requirement; if the name is not the name resolution request under the special time delay requirement, turning to the step 4);
step 4) judging whether the name resolution request in the step 3) is a name resolution request in the domain: if the request is the domain name resolution request, executing the domain name resolution process; if not, go to step 5);
step 5) executing the existing analysis process including direct mapping DMAP, wherein the process comprises the following steps: searching the mapping relation between the entity name and the network address by directly applying a consistent hash function to obtain a name resolution result, and returning the searched network address;
and 6) respectively executing different entity name registration processes aiming at three different scenes of special time delay, intra-domain and no constraint.
In the above technical solution, as shown in fig. 2, in step 3), the name resolution process under the special delay requirement specifically includes:
step 301) a local resolution node LRNj at a certain spatial position receives a name resolution request aiming at a certain entity unique identifier EUID under the special time delay requirement;
step 302) forwarding the name resolution request received in step 301) to a resolution node of a C1 level container where the local resolution node LRNj is located, and marking the name resolution request as C1-i;
step 303) querying the DHT in the resolution node C1-i in step 302); if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not queried, the query is failed, that is, the name resolution service under the special delay requirement cannot be provided.
And directly returning the result of the name resolution of the step 3) to the request sender in an iterative (iterative) mode, or indirectly returning the result of the name resolution of the step 3) to the request sender through the request forwarder in a recursive (recursive) mode.
In the above technical solution, the process of name resolution in the domain in step 4) specifically includes:
step 401) a local resolution node LRNj at a certain spatial position receives a name resolution request in a domain aiming at a certain entity unique identifier EUID, namely the name resolution request without special time delay requirement;
step 402) querying a distributed hash table DHT in the local resolution node LRNj: if the DHT in the local resolution node LRNj is inquired, directly returning to a network address NA corresponding to the local resolution node LRNj; if the DHT in the local resolution node LRNj is not queried, forwarding the name resolution request to a resolution node of a C2 level container where the local resolution node LRNj is located, and marking the resolution node as C2-i;
step 403) querying a bloom filter BF in the parsing node C2-i; if the bloom filter BF in the resolving node C2-i is inquired, the step 404) is carried out; if the bloom filter BF in the resolving node C2-i is not queried, forwarding the name resolving request to a resolving node of a C3-level container where the local resolving node LRNj is located, and marking the resolving node as C3-i;
by analogy, inquiring the analytic node of the Ck level container where the local analytic node LRNj is located, and marking as Ck-q, wherein k is more than or equal to 2 and is less than or equal to I; wherein q is the serial number of any Ck level container where the LRNj is located, and the value range is that q is more than or equal to 1; if the bloom filter BF in the analysis node Ck-q is inquired, turning to the step 404); if the bloom filter BF in the analysis node Ck-q is not inquired, forwarding the bloom filter BF to an analysis node CI-r of a certain CI-level container, and then jumping to the step 405);
step 404) querying a DHT in the parsing node C2-i; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, forwarding the name resolution request to a resolution node C3-r of a certain C3 level container, and turning to step 405);
in the same way, a distributed hash table DHT in an analytic node Ck-q in a Ck level container is inquired, wherein k is more than or equal to 2 and is less than or equal to I, and q; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, forwarding the network address NA to a resolution node CI-r of a certain CI-level container, and turning to the step 405);
step 405) inquiring a bloom filter BF in the analysis node CI-r; if the bloom filter BF in the analysis node CI-r is inquired, turning to step 406); if the bloom filter BF in the analysis node CI-r is not inquired, returning the failure of inquiry, namely the analysis service of the name in the domain can not be provided;
step 406) inquiring a DHT in the analysis node CI-r; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not queried, the query is returned to fail, namely the domain name resolution service cannot be provided.
The result of the name resolution of the step 4) is directly returned to the request sender in an iterative (iterative) mode, or the result of the name resolution of the step 4) is indirectly returned to the request sender through the request forwarder in a recursive (recursive) mode.
In the above technical solution, the process of entity registration in step 6) includes:
step 601) checking and confirming the type of the received entity name registration request, wherein a certain entity unique identifier corresponding to the name is recorded as EUID; wherein the name registration request types include: special time delay, intra-domain and unconstrained scenes;
step 602) determining whether the entity name registration request type in step 601) is an entity name registration request under a special time delay requirement; if the entity name registration request type is an entity name registration request under the special time delay requirement, registering in a local resolution node LRNj and a father node thereof, wherein the father node is a resolution node of a certain C1-level container and is marked as C1-i, and updating a local hash table HT in the local resolution node LRNj and a DHT in the father node C1-i; if the entity name registration request type is not the entity name registration request under the special time delay requirement, go to step 603);
step 603) judging whether the entity name registration request type is an entity name registration request in the domain; if the entity name registration request type is an entity name registration request in a domain, registering in a local resolution node LRNj and an grandfather node with an upward tree structure, wherein the grandfather node is a resolution node of a certain C2-level container and is marked as C2-j; updating a local hash table HT in the local resolution node LRNj, a bloom filter BF in the grandfather node C2-j and a distributed hash table DHT in the grandfather node C2-j until the bloom filter BF and the distributed hash table DHT of the resolution node of the CI-level container serving as the root node are updated; if the entity name registration request type is not the entity name registration request in the domain, go to step 604);
step 604) performing a generic entity name registration procedure including Direct Mapping (DMAP); the process is as follows: during registration, a consistent hash function is directly applied to form a mapping relation between entity names and network addresses.
The invention has the advantages that:
compared with the prior art, the name registration and analysis method meets the requirements on QoS in different application scenes by the safety isolation of equipment registration and content release in three different scenes of special time delay, intra-domain and no constraint. Specifically, the invention reduces the operation range of registration and analysis by space-time constraint field, realizes local nearby processing, and improves the response speed so as to meet the time delay requirement below ms level of a fifth generation mobile communication system (5G) and a future network; meanwhile, the inter-domain flow is reduced through the intra-domain isolation of the container, and the expandability of the information center network is enhanced.
Drawings
FIG. 1 is a schematic flow chart of a method for name registration and resolution based on space-time constraints according to the present invention;
FIG. 2 is a schematic diagram of the entity name registration process of the spatio-temporal constraint field-based name registration and resolution method in FIG. 1.
Detailed Description
The invention provides a space-time constraint field-based name registration and analysis method, which solves the problems of expandability and safety of name analysis in an Information Center Network (ICN) so as to meet different requirements on QoS (quality of service) in three different application scenes of special time delay, intra-domain and no constraint.
The method comprises the following steps:
according to a network measurement index parameter set { Ti }; wherein, Ti is less than Ti +1, I is more than or equal to 1 and less than or equal to I-1, and I is a constant; carrying out space division on network nodes, so that each given Ti corresponds to a container level and is marked as a Ci-level container;
from any local resolution node LRNj, the bottom-up nested space is divided into a C1-level container, a C2-level container, a … -level container and a CI-level container to form a tree structure;
the process of executing different field name registration aiming at three scenes of special time delay, intra-domain and unconstrained is as follows:
for any entity name registration request with special time delay, selecting a node LRNj according to the spatial position, and performing field name registration on an analysis node of a C1 level container where the node LRNj is located;
for an entity registration request restricted to a domain, its field name registration is from the node LRNj up the tree structure until the top container CI where the node LRNj is located; registering on an analysis node of a Ck level container where each LRNj is located, wherein k is more than or equal to 2 and less than or equal to I;
directly entering the existing general system to register names for the unconstrained entity name registration request; the existing general system is an existing analytic system comprising direct mapping DMAP;
different name resolution processes are executed aiming at three different scenes, namely special time delay, intra-domain and unconstrained scene, as follows:
the name resolution request under the special time delay requirement is subjected to field name resolution processing in a bottom-layer C1-level container where the LRNj is located;
the intra-domain name resolution request completes name resolution processing in a top-level CI (public interface) container where the LRNj is located;
the unconstrained name resolution request directly enters the existing generic system to complete the name resolution process.
In the above technical solution, as shown in fig. 1, the name registration and resolution for three scenarios including special time delay, intra-domain, and unconstrained specifically includes:
step 1) checking and determining the type of received request, the request type comprising: special time delay, intra-domain and unconstrained scenes;
step 2) judging whether the request type in the step 1) is a name resolution request or not and whether the request type is a name registration request or not; if the request type is a name resolution request and not a name registration request, turning to step 3); if the request type name registration request is not a name resolution request, directly jumping to the step 6);
step 3) judging whether the name resolution request in the step 2) is a name resolution request under the special time delay requirement: if the name resolution request under the special time delay requirement exists, executing a name resolution process under the special time delay requirement; if the name is not the name resolution request under the special time delay requirement, turning to the step 4);
step 4) judging whether the name resolution request in the step 3) is a name resolution request in the domain: if the request is the domain name resolution request, executing the domain name resolution process; if not, go to step 5);
step 5) executing the existing analysis process including direct mapping DMAP, wherein the process comprises the following steps: searching the mapping relation between the entity name and the network address by directly applying a consistent hash function to obtain a name resolution result, and returning the searched network address;
and 6) respectively executing different entity name registration processes aiming at three different scenes of special time delay, intra-domain and no constraint.
In the above technical solution, in step 3), the name resolution process under the special delay requirement specifically includes:
step 301) a local resolution node LRNj at a certain spatial position receives a name resolution request aiming at a certain entity unique identifier EUID under the special time delay requirement;
step 302) forwarding the name resolution request received in step 301) to a resolution node of a C1 level container where the local resolution node LRNj is located, and marking the name resolution request as C1-i;
step 303) querying the DHT in the resolution node C1-i in step 302); if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not queried, the query is failed, that is, the name resolution service under the special delay requirement cannot be provided.
And directly returning the result of the name resolution of the step 3) to the request sender in an iterative (iterative) mode, or indirectly returning the result of the name resolution of the step 3) to the request sender through the request forwarder in a recursive (recursive) mode.
In the above technical solution, the process of name resolution in the domain in step 4) specifically includes:
step 401) a local resolution node LRNj at a certain spatial position receives a name resolution request in a domain aiming at a certain entity unique identifier EUID, namely the name resolution request without special time delay requirement;
step 402) querying a distributed hash table DHT in the local resolution node LRNj: if the DHT in the local resolution node LRNj is inquired, directly returning to a network address NA corresponding to the local resolution node LRNj; if the DHT in the local resolution node LRNj is not queried, forwarding the name resolution request to a resolution node of a C2 level container where the local resolution node LRNj is located, and marking the resolution node as C2-i;
step 403) querying a bloom filter BF in the parsing node C2-i; if the bloom filter BF in the resolving node C2-i is inquired, the step 404) is carried out; if the bloom filter BF in the resolving node C2-i is not queried, forwarding the name resolving request to a resolving node of a C3-level container where the local resolving node LRNj is located, and marking the resolving node as C3-i;
by analogy, inquiring the analytic node of the Ck level container where the local analytic node LRNj is located, and marking as Ck-q, wherein k is more than or equal to 2 and is less than or equal to I; wherein q is the serial number of any Ck level container where the LRNj is located, and the value range is that q is more than or equal to 1; if the bloom filter BF in the analysis node Ck-q is inquired, turning to the step 404); if the bloom filter BF in the analysis node Ck-q is not inquired, forwarding the bloom filter BF to an analysis node CI-r of a certain CI-level container, and then jumping to the step 405);
step 404) querying a DHT in the parsing node C2-i; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, forwarding the name resolution request to a resolution node C3-r of a certain C3 level container, and turning to step 405);
in the same way, a distributed hash table DHT in an analytic node Ck-q in a Ck level container is inquired, wherein k is more than or equal to 2 and is less than or equal to I, and q; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, forwarding the network address NA to a resolution node CI-r of a certain CI-level container, and turning to the step 405);
step 405) inquiring a bloom filter BF in the analysis node CI-r; if the bloom filter BF in the analysis node CI-r is inquired, turning to step 406); if the bloom filter BF in the analysis node CI-r is not inquired, returning the failure of inquiry, namely the analysis service of the name in the domain can not be provided;
step 406) inquiring a DHT in the analysis node CI-r; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not queried, the query is returned to fail, namely the domain name resolution service cannot be provided.
The result of the name resolution of the step 4) is directly returned to the request sender in an iterative (iterative) mode, or the result of the name resolution of the step 4) is indirectly returned to the request sender through the request forwarder in a recursive (recursive) mode.
In the above technical solution, as shown in fig. 2, the process of entity registration in step 6) includes:
step 601) checking and confirming the type of the received entity name registration request, wherein a certain entity unique identifier corresponding to the name is recorded as EUID; wherein the name registration request types include: special time delay, intra-domain and unconstrained scenes;
step 602) determining whether the entity name registration request type in step 601) is an entity name registration request under a special time delay requirement; if the entity name registration request type is an entity name registration request under the special time delay requirement, registering in a local resolution node LRNj and a father node thereof, wherein the father node is a resolution node of a certain C1-level container and is marked as C1-i, and updating a local hash table HT in the local resolution node LRNj and a DHT in the father node C1-i; if the entity name registration request type is not the entity name registration request under the special time delay requirement, go to step 603);
step 603) judging whether the entity name registration request type is an entity name registration request in the domain; if the entity name registration request type is an entity name registration request in a domain, registering in a local resolution node LRNj and an grandfather node with an upward tree structure, wherein the grandfather node is a resolution node of a certain C2-level container and is marked as C2-j; updating a local hash table HT in the local resolution node LRNj, a bloom filter BF in the grandfather node C2-j and a distributed hash table DHT in the grandfather node C2-j until the bloom filter BF and the distributed hash table DHT of the resolution node of the CI-level container serving as the root node are updated; if the entity name registration request type is not the entity name registration request in the domain, go to step 604);
step 604) performing a generic entity name registration procedure including Direct Mapping (DMAP); the process is as follows: and searching the mapping relation between the entity name and the network address by directly applying a consistent hash function to obtain a name resolution result, and returning the searched network address.
Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present invention and are not limited. Although the present invention has been described in detail with reference to the embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (7)
1. A name registration and analysis method based on space-time constraint scene comprises the following steps:
according to a network measurement index parameter set { Ti }; wherein, Ti is less than Ti +1, I is more than or equal to 1 and less than or equal to I-1, and I is a constant; carrying out space division on network nodes, so that each given Ti corresponds to a container level and is marked as a Ci-level container;
from any local resolution node LRNj, the bottom-up nested space is divided into a C1-level container, a C2-level container, a … -level container and a CI-level container to form a tree structure;
the process of executing different field name registration aiming at three scenes of special time delay, intra-domain and unconstrained is as follows:
for any entity name registration request with special time delay, selecting a node LRNj according to the spatial position, and performing field name registration on an analysis node of a C1 level container where the node LRNj is located;
for an entity registration request restricted to a domain, its field name registration is from the node LRNj up the tree structure until the top container CI where the node LRNj is located; registering on an analysis node of a Ck level container where each LRNj is located, wherein k is more than or equal to 2 and less than or equal to I;
directly entering the existing general system to carry out name registration for an unconstrained entity registration request; the existing general system is an existing analytic system comprising direct mapping DMAP;
different name resolution processes are executed aiming at three scenes, namely special time delay, intra-domain and unconstrained scene, as follows:
the name resolution request under the special time delay requirement is subjected to field name resolution processing in a bottom-layer C1-level container where the LRNj is located;
the intra-domain name resolution request completes name resolution processing in a top-level CI (public interface) container where the LRNj is located;
the unconstrained name resolution request directly enters the existing generic system to complete the name resolution process.
2. The method for name registration and resolution based on space-time constraint field according to claim 1, wherein the name registration and resolution for three scenarios including special time delay, intra-domain and unconstrained specifically comprises:
step 1) checking and determining the type of received request, the request type comprising: special time delay, intra-domain and unconstrained scenes;
step 2) judging whether the request type in the step 1) is a name resolution request or not and whether the request type is a name registration request or not; if the request type is a name resolution request and not a name registration request, turning to step 3); if the request type name registration request is not a name resolution request, directly jumping to the step 6);
step 3) judging whether the name resolution request in the step 2) is a name resolution request under the special time delay requirement: if the name resolution request under the special time delay requirement exists, executing a name resolution process under the special time delay requirement; if the name is not the name resolution request under the special time delay requirement, turning to the step 4);
step 4) judging whether the name resolution request in the step 3) is a name resolution request in the domain: if the request is the domain name resolution request, executing the domain name resolution process; if not, go to step 5);
step 5) executing the existing analysis process including direct mapping DMAP, wherein the process comprises the following steps: searching the mapping relation between the entity name and the network address by directly applying a consistent hash function to obtain a name resolution result, and returning the searched network address;
and 6) respectively executing different entity name registration processes aiming at three different scenes of special time delay, intra-domain and no constraint.
3. The method for name registration and resolution based on spatiotemporal constraint field according to claim 2, wherein in step 3), the name resolution process under the special time delay requirement specifically includes:
step 301) a local resolution node LRNj at a certain spatial position receives a name resolution request aiming at a certain entity unique identifier EUID under the special time delay requirement;
step 302) forwarding the name resolution request received in step 301) to a resolution node of a C1 level container where the local resolution node LRNj is located, and marking the name resolution request as C1-i;
step 303) querying the DHT in the resolution node C1-i in step 302); if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not queried, the query is failed, that is, the name resolution service under the special delay requirement cannot be provided.
4. The method for name registration and resolution based on spatiotemporal constraint field as claimed in claim 3, wherein the result of name resolution of step 3) is directly returned to the request issuer in an iterative manner, or the result of name resolution of step 3) is indirectly returned to the request issuer through the request forwarder in a recursive manner.
5. The method for name registration and resolution based on spatio-temporal constraint field according to claim 2, wherein the domain name resolution process in step 4) specifically includes:
step 401) a local resolution node LRNj at a certain spatial position receives a name resolution request in a domain aiming at a certain entity unique identifier EUID, namely the name resolution request without special time delay requirement;
step 402) querying a distributed hash table DHT in the local resolution node LRNj: if the DHT in the local resolution node LRNj is inquired, directly returning to a network address NA corresponding to the local resolution node LRNj; if the DHT in the local resolution node LRNj is not queried, forwarding the name resolution request to a resolution node of a C2 level container where the local resolution node LRNj is located, and marking the resolution node as C2-i;
step 403) querying a bloom filter BF in the parsing node C2-i; if the bloom filter BF in the resolving node C2-i is inquired, the step 404) is carried out; if the bloom filter BF in the resolving node C2-i is not inquired, forwarding the name resolving request to a resolving node of a C3-level container where the local resolving node LRNj is located, and marking as C3-i;
by analogy, inquiring the analytic node of the Ck level container where the local analytic node LRNj is located, and marking as Ck-q, wherein k is more than or equal to 2 and is less than or equal to I; wherein q is the serial number of any Ck level container where the LRNj is located, and the value range is that q is more than or equal to 1; if the bloom filter BF in the analysis node Ck-q is inquired, turning to the step 404); if the bloom filter BF in the analysis node Ck-q is not inquired, forwarding the bloom filter BF to an analysis node CI-r of a certain CI-level container, and then jumping to the step 405);
step 404) querying a DHT in the parsing node C2-i; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, forwarding the name resolution request to a resolution node C3-r of a certain C3 level container, and turning to step 405);
in the same way, a distributed hash table DHT in an analytic node Ck-q in a Ck level container is inquired, wherein k is more than or equal to 2 and is less than or equal to I, and q; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, forwarding the network address NA to a resolution node CI-r of a certain CI-level container, and turning to the step 405);
step 405) inquiring a bloom filter BF in the analysis node CI-r; if the bloom filter BF in the analysis node CI-r is inquired, turning to step 406); if the bloom filter BF in the analysis node CI-r is not inquired, returning the failure of inquiry, namely the analysis service of the name in the domain can not be provided;
step 406) inquiring a DHT in the analysis node CI-r; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, directly returning to the network address NA; if the network address NA corresponding to the entity unique identifier EUID in the name resolution request is not queried, the query is returned to fail, namely the domain name resolution service cannot be provided.
6. The method for name registration and resolution based on spatiotemporal constraint field as claimed in claim 5, wherein the result of name resolution of step 4) is directly returned to the request issuer in an iterative manner, or the result of name resolution of step 4) is indirectly returned to the request issuer through the request forwarder in a recursive manner.
7. The spatio-temporal constraint field-based name registration and resolution method according to claim 2, wherein the process of entity registration in step 6) comprises:
step 601) checking and confirming the type of the received entity name registration request, wherein a certain entity unique identifier corresponding to the name is recorded as EUID; wherein the name registration request types include: special time delay, intra-domain and unconstrained scenes;
step 602) determining whether the entity name registration request type in step 601) is an entity name registration request under a special time delay requirement; if the entity name registration request type is an entity name registration request under the special time delay requirement, registering in a local resolution node LRNj and a father node thereof, wherein the father node is a resolution node of a certain C1-level container and is marked as C1-i, and updating a local hash table HT in the local resolution node LRNj and a DHT in the father node C1-i; if the entity name registration request type is not the entity name registration request under the special time delay requirement, go to step 603);
step 603) judging whether the entity name registration request type is an entity name registration request in the domain; if the entity name registration request type is an entity name registration request in a domain, registering in a local resolution node LRNj and an grandfather node upwards in a tree structure of the local resolution node LRNj, wherein the grandfather node is a resolution node of a certain C2-level container and is marked as C2-j; updating a local hash table HT in the local resolution node LRNj, a bloom filter BF in the grandfather node C2-j and a distributed hash table DHT in the grandfather node C2-j until the bloom filter BF and the distributed hash table DHT of the resolution node of the CI-level container serving as the root node are updated; if the entity name registration request type is not the entity name registration request in the domain, go to step 604);
step 604) performing a generic entity name registration procedure including direct mapped DMAP; the process is as follows: during registration, a consistent hash function is directly applied to form a mapping relation between entity names and network addresses.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710874886.6A CN109561161B (en) | 2017-09-25 | 2017-09-25 | Name registration and analysis method based on space-time constraint field |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710874886.6A CN109561161B (en) | 2017-09-25 | 2017-09-25 | Name registration and analysis method based on space-time constraint field |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109561161A CN109561161A (en) | 2019-04-02 |
| CN109561161B true CN109561161B (en) | 2020-05-26 |
Family
ID=65862223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710874886.6A Active CN109561161B (en) | 2017-09-25 | 2017-09-25 | Name registration and analysis method based on space-time constraint field |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109561161B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242421A (en) * | 2008-03-19 | 2008-08-13 | 中国科学院计算技术研究所 | Application-oriented name registration system and its service method under multi-layer NAT environment |
| CN102185935A (en) * | 2011-04-27 | 2011-09-14 | 北京交通大学 | Resource-oriented hierarchical name resolution system |
| CN104596588A (en) * | 2015-02-04 | 2015-05-06 | 测绘遥感信息工程国家重点实验室深圳研发中心 | Environmental status time-space model generation method and system based on digital measurable images |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6760746B1 (en) * | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
| US20090222541A1 (en) * | 2005-11-08 | 2009-09-03 | Nortel Networks Limited | Dynamic sensor network registry |
| US20170236123A1 (en) * | 2016-02-16 | 2017-08-17 | Blockstack Inc. | Decentralized processing of global naming systems |
-
2017
- 2017-09-25 CN CN201710874886.6A patent/CN109561161B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242421A (en) * | 2008-03-19 | 2008-08-13 | 中国科学院计算技术研究所 | Application-oriented name registration system and its service method under multi-layer NAT environment |
| CN102185935A (en) * | 2011-04-27 | 2011-09-14 | 北京交通大学 | Resource-oriented hierarchical name resolution system |
| CN104596588A (en) * | 2015-02-04 | 2015-05-06 | 测绘遥感信息工程国家重点实验室深圳研发中心 | Environmental status time-space model generation method and system based on digital measurable images |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109561161A (en) | 2019-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111611613B (en) | ICN-based industrial Internet identification analysis system and data access method | |
| US10706029B2 (en) | Content name resolution for information centric networking | |
| US9231903B2 (en) | System and method for resolving a DNS request using metadata | |
| CN111373704B (en) | Method, system and storage medium for supporting multimode identification network addressing progressive-entry IP | |
| TWI657682B (en) | Method and system for realizing precise dispatch request on content distribution network (CDN) | |
| EP3043585A1 (en) | Systems and methods for providing iot services | |
| US9525659B1 (en) | Request routing utilizing point of presence load information | |
| US11824829B2 (en) | Methods and systems for domain name data networking | |
| US10956501B2 (en) | Network-wide, location-independent object identifiers for high-performance distributed graph databases | |
| US20160255047A1 (en) | Methods and systems for determining domain names and organization names associated with participants involved in secured sessions | |
| US11368424B2 (en) | Enhanced domain name system (DNS) server | |
| Hesselman et al. | Increasing DNS security and stability through a control plane for top-level domain operators | |
| US20170041422A1 (en) | Method and system for retrieving a content manifest in a network | |
| US11102166B2 (en) | Explicit service function chaining (SFC) using DNS extensions | |
| CN109947764B (en) | Query enhancement system and method for constructing elastic site based on time delay | |
| CN109561161B (en) | Name registration and analysis method based on space-time constraint field | |
| JP2023508447A (en) | Content delivery system using embedded requestor information | |
| CN116566945A (en) | Access method and device for decentralised application, electronic equipment and storage medium | |
| US10404659B2 (en) | Optimization of resource URLs in machine-to-machine networks | |
| CN109495525B (en) | Network component, method of resolving content identification, and computer-readable storage medium | |
| US11303606B1 (en) | Hashing name resolution requests according to an identified routing policy | |
| CN109831542B (en) | Flat fixed-length name processing method and system | |
| Shi et al. | Blockchain-based content name search mechanism in ndn | |
| CN114268605B (en) | Intelligent DNS realization method and device and computer storage medium | |
| WO2016074148A1 (en) | Method and system for domain name load balancing |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220929 Address after: Room 1601, 16th Floor, East Tower, Ximei Building, No. 6 Changchun Road, High-tech Industrial Development Zone, Zhengzhou City, Henan Province, 450000 Patentee after: Zhengzhou xinrand Network Technology Co.,Ltd. Address before: 100190, No. 21 West Fourth Ring Road, Beijing, Haidian District Patentee before: INSTITUTE OF ACOUSTICS, CHINESE ACADEMY OF SCIENCES Patentee before: BEIJING ZHONGKE HAILI TECHNOLOGY Co.,Ltd. |