CN109561161A - A kind of name registration and analytic method based on space-time restriction scene - Google Patents

A kind of name registration and analytic method based on space-time restriction scene Download PDF

Info

Publication number
CN109561161A
CN109561161A CN201710874886.6A CN201710874886A CN109561161A CN 109561161 A CN109561161 A CN 109561161A CN 201710874886 A CN201710874886 A CN 201710874886A CN 109561161 A CN109561161 A CN 109561161A
Authority
CN
China
Prior art keywords
name
node
request
lrnj
name resolution
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201710874886.6A
Other languages
Chinese (zh)
Other versions
CN109561161B (en
Inventor
盛益强
王劲林
程钢
叶晓舟
邓浩江
王玲芳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhengzhou Xinrand Network Technology Co ltd
Original Assignee
Institute of Acoustics CAS
Beijing Hili Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Institute of Acoustics CAS, Beijing Hili Technology Co Ltd filed Critical Institute of Acoustics CAS
Priority to CN201710874886.6A priority Critical patent/CN109561161B/en
Publication of CN109561161A publication Critical patent/CN109561161A/en
Application granted granted Critical
Publication of CN109561161B publication Critical patent/CN109561161B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/30Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015Name registration, generation or assignment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping

Abstract

The present invention relates to a kind of name registrations and analytic method based on space-time restriction scene, comprising: according to measurement index parameter sets { Ti };Network node space is divided, each a corresponding Ci grades of container level of given Ti;For the physical name registration request of special time delay, node LRNj is chosen according to spatial position, and carries out live name registration on the parsing node of the C1 grade container where the LRNj;For the registers entities request being limited in domain, live name registration be from LRNj along tree construction upwards until the top level container CI where the LRNj;Unconfined registers entities are requested, existing general-purpose system is directly entered and carries out name registration;Name resolution request under special delay requirement will complete live name resolving process in C1 grades of containers of bottom where LRNj;Name resolution request will complete name resolving process in the top level container CI where LRNj in domain;Existing general-purpose system is directly entered without constraint name resolution request to complete name resolving process.

Description

A kind of name registration and analytic method based on space-time restriction scene
Technical field
The invention belongs to network technologies and logical information technology field, and in particular to a kind of name based on space-time restriction scene Registration and analytic method.
Background technique
TCP/IP Generation Internet has been difficult to adapt to the development trend of future network, is especially difficult to meet mobile connect Enter, general fit calculation, distributed information processing, the new opplications such as magnanimity Streaming Media growth requirement.In order to promote user experience, study Personnel propose information centre network ICN, and information name and network site are decoupled, to enhance the network performance of various aspects, packet Include mobility, scalability, real-time and dynamic etc..In the information in heart network ICN, it is desirable that name of the information has polymerizable Property and persistence guarantee name of the information not with position change to avoid routing table expansion issues.Mobile network user has reached at present 3000000000, daily newly generated video is more than 5,000,000,000, following to have hundred billion grades of internet of things equipment to access.Storage and index ten thousand The name of hundred million magnitude entities, hundreds of thousands of secondary immediate updating physical address per second and millions of secondary query entity current addresses per second, And the far super stratification of pressure point to the rigors for searching time delay, to the storage of name registration resolution system, inquiry, update The domain name system of cloth may cause serious performance issue.
Can the massive information of information centre network ICN has the characteristic of physical distribution formula, propose one kind according to the characteristic It is divided by domain, the method for organizational information and resource, the division of global formula address resolution system is divided into multiple subsystems on demand, with Improve how parsing rate keeps believing to meet QoS different under different application scene, especially time delay and reliability requirement Elasticity, the autonomous characteristic for ceasing central network, are information centre network ICN critical issues urgently to be resolved.Due to the heart in the information In network ICN, name is separated with position.The effect of registration and parsing is exactly to information name or informant's registration one A or multiple dynamic network address, and from the name resolution of information to network address or the position of informant.Also It is to say, name resolution system is for establishing, safeguarding, between the name that releases news and locational information location or informant Mapping relations, all information names are mapped under the same NameSpace and are identified.The basis of name resolution system is Naming method is broadly divided into two classes: first is that stratification is named, second is that flattening is named.
Based on the resolving of stratification name, although ensure that router efficiency, scalability is very limited.? It is DNS with name resolution system equivalent action in current internet, wherein DNS is the level of a typical multistage domain name Type naming system.Since name is not to be evenly distributed in top level domain, so the load of resolution server and unbalanced.Meanwhile The structure also has the safety problems such as the dos attack being difficult to avoid that.NDN is exactly a typical stratification naming system, in level Change in naming system, for resolving generally all since root node, this brings very big constraint to resolution system.It is current About DNS's studies have shown that stratification naming system towards mass users request increase under conditions of emerge it is more and more out The problem of.
Based on the resolving of flattening name, the scalability and safety of name ensure that, still, to parsing and road Bigger challenge is proposed by efficiency.In flattening naming system, semantic unrelated naming method can ensure content and position The decoupling set, and in security method menu also advantage.Aiming at the problem that stratification parsing named based on flattening, one Feasible solution is such as to use Pastry or Chord using distributed hashtable (DHT) technology, Lai Jinhang from content to The mapping of name.In distributed hashtable DHT, typical complexity of searching is log (N), and wherein N is the node rule in network Mould, this method can effectively improve search efficiency, reduce the scale for the content safeguarded required for each node.But due to DHT Structure is compressed structure, and when content is larger, the information content to be safeguarded can be non-in distributed hashtable DHT routing table It is often huge, especially in a mobile environment, when location of content, which exists, to be changed, the maintenance process of distributed hashtable DHT structure Larger burden can be brought to whole network.
Therefore, it is necessary to construct a kind of name registration and analytic method based on space-time restriction scene, pass through different scenes Under security isolation that facility registration and content are issued, the efficient inquiry of name to address is realized, to meet different applied fields To the demand of QoS under scape, scalability and safety issue are solved, to adapt to the development of future network.
Summary of the invention
It is an object of the present invention in order to solve existing name registration and analytic method, there are the above problem, the present invention A kind of name registration and analytic method based on space-time restriction scene is provided, name solution in information centre's network (ICN) is solved The scalability and safety issue of analysis, to meet the different demands under different application scene to QoS.
This method comprises:
According to network measure index parameter set { Ti };Wherein, Ti < Ti+1,1≤i≤I-1, I are constant;To network section Point carries out space division, so that each corresponding container level of given Ti, is denoted as Ci grades of containers;
Since any local parsing node LRNj, it is C1 grades of containers, C2 grades of appearances that bottom-up nesting space, which divides, Device ..., CI grades of containers, form a tree construction;
For in special time delay, domain, without constraint three kinds of scenes execute different live name registrations process it is as follows:
For there is any physical name registration request of special time delay, node LRNj is chosen according to spatial position, and at this Live name registration is carried out on the parsing node of C1 grade container where node LRNj;
For the registers entities request being limited in domain, live name registration is from node LRNj along tree construction Upwards until the top level container CI where node LRNj;On the parsing node of the Ck grade container where each LRNj It is registered, wherein 2≤k≤I;
Unconfined registers entities are requested, existing general-purpose system is directly entered and carries out name registration;It is described existing General-purpose system be existing resolution system including directly mapping DMAP;
It is as follows for different name resolution processes is executed in special time delay, domain, without three kinds of scenes of constraint:
Name resolution request under special delay requirement will complete scene in C1 grades of containers of bottom where node LRNj Name resolving process;
Name resolution request will complete name resolving process in CI grades of containers of top layer where node LRNj in domain;
Existing general-purpose system is directly entered without constraint name resolution request to complete name resolving process.
In the above-mentioned technical solutions, in special time delay, domain, without three kinds of scenes of constraint name registration and parsing, tool Body includes:
Step 1), which checks, simultaneously determines the request type that receives, the request type include: special time delay, in domain, without about Three kinds of scenes of beam;
Step 2) judgment step 1) in request type whether be name analysis request and whether be name registration request;If The request type is name resolution request, and is not name registration request, then goes to step 3);If the request type name Registration request, and be not name resolution request, then jump directly to step 6);
Step 3) judgment step 2) name resolution request whether be under special delay requirement name resolution request: if Name resolution request under special delay requirement, then execute the name resolution process under special delay requirement;If not when special Prolong the name resolution request under demand, then goes to step 4);
Step 4) judgment step 3) name resolution request whether be in domain name resolution request: if the name in domain Analysis request then executes the name resolution process in domain;If not the name resolution in domain is requested, then step 5) is gone to;
Step 5) executes the existing process of analysis including directly mapping DMAP, process are as follows: by directly applying one Cause property hash function, to search the mapping relations between physical name and network address, to obtain name resolution as a result, and returning The network address found;
Step 6) for special time delay, in domain, execute different physical name registrations respectively without three kinds of different scenes of constraint Process.
In the above-mentioned technical solutions, as shown in Fig. 2, in step 3), the name resolution process under special delay requirement is specific Include:
The local parsing node LRNj of some spatial position of step 301) is received for some entity unique identifier Name resolution request under the special delay requirement of EUID;
The name resolution received in step 301) request is forwarded to local parsing node LRNj institute by step 302) C1 grade container parsing node, be denoted as C1-i;
Step 303) query steps 302) in parsing node C1-i in distributed hashtable DHT;If inquiring described Network address NA corresponding to entity unique identifier EUID in name resolution request, then directly return to the network address NA;If not inquiring network address NA corresponding to the entity unique identifier EUID in the name resolution request, return Inquiry failure is returned, i.e., the name resolution service under special delay requirement cannot be provided.
The result of the name resolution of step 3) is directly returned to request sender in a manner of iteration (iterative), Or the result of the name resolution of step 3) is turned originator and returns to indirectly to ask by request in a manner of recurrence (recursive) Seek sender.
In the above-mentioned technical solutions, the name resolution process in the domain in step 4) specifically includes:
The local parsing node LRNj of some spatial position of step 401) is received for some entity unique identifier Name resolution request in the domain of EUID, i.e., request without the name resolution under special delay requirement;
Step 402) inquires the distributed hashtable DHT in the local parsing node LRNj: if inquiring the local The distributed hashtable DHT in node LRNj is parsed, then with directly returning to network corresponding to the local parsing node LRNj Location NA;If not inquiring the distributed hashtable DHT in the local parsing node LRNj, the name resolution is asked The parsing node for seeking the C2 grade container where being forwarded to the local parsing node LRNj, is denoted as C2-i;
The grand filter BF of cloth in step 403) the inquiry parsing node C2-i;If inquiring the parsing node C2- The grand filter BF of cloth in i, then go to step 404);If not inquiring the grand filter of cloth in the parsing node C2-i Name resolution request is then forwarded to the parsing node of the C3 grade container where the local parsing node LRNj, note by BF For C3-i;
And so on, the parsing node of the Ck grade container where the local parsing node LRNj is inquired, is denoted as Ck-q, 2 ≤k≤I;Wherein, q is the sequence number of any Ck grades of containers where LRNj, and value range is q >=1;If inquiring the solution The grand filter BF of cloth in node Ck-q is analysed, then goes to step 404);If not inquiring the cloth in the parsing node Ck-q Grand filter BF, then be forwarded to the parsing node CI-r of some CI grades of container, then gos to step 405);
Distributed hashtable DHT in step 404) the inquiry parsing node C2-i;If inquiring the name resolution Network address NA corresponding to entity unique identifier EUID in request, then directly return to the network address NA;If no Network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, then by the name solution Analysis request is forwarded to the parsing node C3-r of some C3 grades of container, and goes to step 405);
And so on, inquire the distributed hashtable DHT, 2≤k in the parsing node Ck-q in some Ck grades of container ≤ I, q;If inquiring network address NA corresponding to the entity unique identifier EUID in the name resolution request, directly Return to the network address NA;If not inquiring corresponding to the entity unique identifier EUID in the name resolution request Network address NA, then be forwarded to the parsing node CI-r of some CI grades of container, and goes to step 405);
The grand filter BF of cloth in step 405) the inquiry parsing node CI-r;If inquiring the parsing node CI- The grand filter BF of cloth in r, then go to step 406);If not inquiring the grand filter of cloth in the parsing node CI-r BF then returns to inquiry failure, i.e., cannot provide the analysis service of the name in domain;
Distributed hashtable DHT in step 406) the inquiry parsing node CI-r;If inquiring the name resolution Network address NA corresponding to entity unique identifier EUID in request, then directly return to the network address NA;If no Network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, then returns to inquiry and loses It loses, i.e., the name resolution service in domain cannot be provided.
The result of the name resolution of step 4) is directly returned to request sender in a manner of iteration (iterative), Or the result of the name resolution of step 4) is turned originator and returns to indirectly to ask by request in a manner of recurrence (recursive) Seek sender.
In the above-mentioned technical solutions, the process of the registers entities in step 6), comprising:
Step 601) reviews and validate the physical name registration request type received, corresponding to name therein some Entity unique identifier, is denoted as EUID;Wherein, the name registration request type include: special time delay, in domain, without constraint three Kind scene;
Step 602) judgment step 601) in the physical name registration request type whether be under special delay requirement Physical name registration request;If the physical name registration request type is that the physical name registration under special delay requirement is asked It asks, is then registered in local parsing node LRNj and its father node, the father node is the parsing node of some C1 grades of container, note For C1-i, and update in the local Hash table HT and the father node C1-i in the local parsing node LRNj distributed breathes out Uncommon table DHT;If the physical name registration request type is not the physical name registration request under special delay requirement, go to Step 603);
Step 603) judges whether the physical name registration request type is physical name registration request in domain;If institute Stating physical name registration request type is the physical name registration request in domain, then in local parsing node LRNj and its tree knot It is registered in the upward grandparent node of structure, the grandparent node is the parsing node of some C2 grades of container, is denoted as C2-j;And it updates and is somebody's turn to do The grand filter BF of cloth in local Hash table HT, the grandparent node C2-j, grandfather section in local parsing node LRNj Distributed hashtable DHT in point C2-j updates always the grand filtering of cloth to the parsing node of the CI grade container as root node Device BF and distributed hashtable DHT;If the physical name registration request type is not the physical name registration request in domain, Go to step 604);
Step 604) executes the general physical name register flow path including directly mapping (DMAP);Its process are as follows: In registration, consistency hash function is applied, directly to form the mapping relations between physical name and network address.
The present invention has the advantages that
Compared with prior art, name registration and analytic method of the invention, by special time delay, domain, without constraint Under three kinds of different scenes, to the security isolation that facility registration and content are issued, the need under different application scenarios to QoS are met It asks.Specifically, the present invention reduces the opereating specification of registration and parsing by space-time restriction scene, realize local just nearby Reason improves response speed, to meet the ms grade delay requirement below of the 5th Generation Mobile Communication System (5G) and future network;Together When, flow between domain is reduced by being isolated in the domain of container, enhances the scalability of information centre's network.
Detailed description of the invention
Fig. 1 is a kind of flow diagram of name registration and analytic method based on space-time restriction scene of the invention;
Fig. 2 is a kind of physical name of name registration and analytic method based on space-time restriction scene of the invention in Fig. 1 Word register flow path schematic diagram.
Specific embodiment
The present invention provides a kind of name registrations and analytic method based on space-time restriction scene, solve information centre's network (ICN) scalability and safety issue of name resolution in, to meet special time delay, in domain, without three kinds of different applications of constraint To the different demands of QoS under scene.
This method comprises:
According to network measure index parameter set { Ti };Wherein, Ti < Ti+1,1≤i≤I-1, I are constant;To network section Point carries out space division, so that each corresponding container level of given Ti, is denoted as Ci grades of containers;
Since any local parsing node LRNj, it is C1 grades of containers, C2 grades of appearances that bottom-up nesting space, which divides, Device ..., CI grades of containers, form a tree construction;
For in special time delay, domain, without constraint three kinds of scenes execute different live name registrations process it is as follows:
For there is any physical name registration request of special time delay, node LRNj is chosen according to spatial position, and at this Live name registration is carried out on the parsing node of C1 grade container where node LRNj;
For the registers entities request being limited in domain, live name registration is from node LRNj along tree construction Upwards until the top level container CI where node LRNj;On the parsing node of the Ck grade container where each LRNj It is registered, wherein 2≤k≤I;
For unconfined physical name registration request, it is directly entered existing general-purpose system and carries out name registration;It is described Existing general-purpose system is the existing resolution system including directly mapping DMAP;
It is as follows for different name resolution processes is executed in special time delay, domain, without three kinds of different scenes of constraint:
Name resolution request under special delay requirement will complete scene in C1 grades of containers of bottom where node LRNj Name resolving process;
Name resolution request will complete name resolving process in CI grades of containers of top layer where node LRNj in domain;
Existing general-purpose system is directly entered without constraint name resolution request to complete name resolving process.
In the above-mentioned technical solutions, as shown in Figure 1, for the name registration in special time delay, domain, without three kinds of scenes of constraint And its parsing, it specifically includes:
Step 1), which checks, simultaneously determines the request type that receives, the request type include: special time delay, in domain, without about Three kinds of scenes of beam;
Step 2) judgment step 1) in request type whether be name analysis request and whether be name registration request;If The request type is name resolution request, and is not name registration request, then goes to step 3);If the request type name Registration request, and be not name resolution request, then jump directly to step 6);
Step 3) judgment step 2) name resolution request whether be under special delay requirement name resolution request: if Name resolution request under special delay requirement, then execute the name resolution process under special delay requirement;If not when special Prolong the name resolution request under demand, then goes to step 4);
Step 4) judgment step 3) name resolution request whether be in domain name resolution request: if the name in domain Analysis request then executes the name resolution process in domain;If not the name resolution in domain is requested, then step 5) is gone to;
Step 5) executes the existing process of analysis including directly mapping DMAP, process are as follows: by directly applying one Cause property hash function, to search the mapping relations between physical name and network address, to obtain name resolution as a result, and returning The network address found;
Step 6) for special time delay, in domain, execute different physical name registrations respectively without three kinds of different scenes of constraint Process.
In the above-mentioned technical solutions, in step 3), the name resolution process under special delay requirement is specifically included:
The local parsing node LRNj of some spatial position of step 301) is received for some entity unique identifier Name resolution request under the special delay requirement of EUID;
The name resolution received in step 301) request is forwarded to local parsing node LRNj institute by step 302) C1 grade container parsing node, be denoted as C1-i;
Step 303) query steps 302) in parsing node C1-i in distributed hashtable DHT;If inquiring described Network address NA corresponding to entity unique identifier EUID in name resolution request, then directly return to the network address NA;If not inquiring network address NA corresponding to the entity unique identifier EUID in the name resolution request, return Inquiry failure is returned, i.e., the name resolution service under special delay requirement cannot be provided.
The result of the name resolution of step 3) is directly returned to request sender in a manner of iteration (iterative), Or the result of the name resolution of step 3) is turned originator and returns to indirectly to ask by request in a manner of recurrence (recursive) Seek sender.
In the above-mentioned technical solutions, the name resolution process in the domain in step 4) specifically includes:
The local parsing node LRNj of some spatial position of step 401) is received for some entity unique identifier Name resolution request in the domain of EUID, i.e., request without the name resolution under special delay requirement;
Step 402) inquires the distributed hashtable DHT in the local parsing node LRNj: if inquiring the local The distributed hashtable DHT in node LRNj is parsed, then with directly returning to network corresponding to the local parsing node LRNj Location NA;If not inquiring the distributed hashtable DHT in the local parsing node LRNj, the name resolution is asked The parsing node for seeking the C2 grade container where being forwarded to the local parsing node LRNj, is denoted as C2-i;
The grand filter BF of cloth in step 403) the inquiry parsing node C2-i;If inquiring the parsing node C2- The grand filter BF of cloth in i, then go to step 404);If not inquiring the grand filter of cloth in the parsing node C2-i Name resolution request is then forwarded to the parsing node of the C3 grade container where the local parsing node LRNj, note by BF For C3-i;
And so on, the parsing node of the Ck grade container where the local parsing node LRNj is inquired, is denoted as Ck-q, 2 ≤k≤I;Wherein, q is the sequence number of any Ck grades of containers where LRNj, and value range is q >=1;If inquiring the solution The grand filter BF of cloth in node Ck-q is analysed, then goes to step 404);If not inquiring the cloth in the parsing node Ck-q Grand filter BF, then be forwarded to the parsing node CI-r of some CI grades of container, then gos to step 405);
Distributed hashtable DHT in step 404) the inquiry parsing node C2-i;If inquiring the name resolution Network address NA corresponding to entity unique identifier EUID in request, then directly return to the network address NA;If no Network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, then by the name solution Analysis request is forwarded to the parsing node C3-r of some C3 grades of container, and goes to step 405);
And so on, inquire the distributed hashtable DHT, 2≤k in the parsing node Ck-q in some Ck grades of container ≤ I, q;If inquiring network address NA corresponding to the entity unique identifier EUID in the name resolution request, directly Return to the network address NA;If not inquiring corresponding to the entity unique identifier EUID in the name resolution request Network address NA, then be forwarded to the parsing node CI-r of some CI grades of container, and goes to step 405);
The grand filter BF of cloth in step 405) the inquiry parsing node CI-r;If inquiring the parsing node CI- The grand filter BF of cloth in r, then go to step 406);If not inquiring the grand filter of cloth in the parsing node CI-r BF then returns to inquiry failure, i.e., cannot provide the analysis service of the name in domain;
Distributed hashtable DHT in step 406) the inquiry parsing node CI-r;If inquiring the name resolution Network address NA corresponding to entity unique identifier EUID in request, then directly return to the network address NA;If no Network address NA corresponding to the entity unique identifier EUID in the name resolution request is inquired, then returns to inquiry and loses It loses, i.e., the name resolution service in domain cannot be provided.
The result of the name resolution of step 4) is directly returned to request sender in a manner of iteration (iterative), Or the result of the name resolution of step 4) is turned originator and returns to indirectly to ask by request in a manner of recurrence (recursive) Seek sender.
In the above-mentioned technical solutions, as shown in Fig. 2, the process of the registers entities in step 6), comprising:
Step 601) reviews and validate the physical name registration request type received, corresponding to name therein some Entity unique identifier, is denoted as EUID;Wherein, the name registration request type include: special time delay, in domain, without constraint three Kind scene;
Step 602) judgment step 601) in the physical name registration request type whether be under special delay requirement Physical name registration request;If the physical name registration request type is that the physical name registration under special delay requirement is asked It asks, is then registered in local parsing node LRNj and its father node, the father node is the parsing node of some C1 grades of container, note For C1-i, and update in the local Hash table HT and the father node C1-i in the local parsing node LRNj distributed breathes out Uncommon table DHT;If the physical name registration request type is not the physical name registration request under special delay requirement, go to Step 603);
Step 603) judges whether the physical name registration request type is physical name registration request in domain;If institute Stating physical name registration request type is the physical name registration request in domain, then in local parsing node LRNj and its tree knot It is registered in the upward grandparent node of structure, the grandparent node is the parsing node of some C2 grades of container, is denoted as C2-j;And it updates and is somebody's turn to do The grand filter BF of cloth in local Hash table HT, the grandparent node C2-j, grandfather section in local parsing node LRNj Distributed hashtable DHT in point C2-j updates always the grand filtering of cloth to the parsing node of the CI grade container as root node Device BF and distributed hashtable DHT;If the physical name registration request type is not the physical name registration request in domain, Go to step 604);
Step 604) executes the general physical name register flow path including directly mapping (DMAP);Its process are as follows: By directly applying consistency hash function, to search the mapping relations between physical name and network address, to obtain name Parsing result, and return to the network address found.
It should be noted last that the above examples are only used to illustrate the technical scheme of the present invention and are not limiting.Although ginseng It is described the invention in detail according to embodiment, those skilled in the art should understand that, to technical side of the invention Case is modified or replaced equivalently, and without departure from the spirit and scope of technical solution of the present invention, should all be covered in the present invention Scope of the claims in.

Claims (7)

1. a kind of name registration and analytic method based on space-time restriction scene, this method comprises:
According to network measure index parameter set { Ti };Wherein, Ti < Ti+1,1≤i≤I-1, I are constant;To network node into Row space divides, so that each corresponding container level of given Ti, is denoted as Ci grades of containers;
Since any local parsing node LRNj, it is bottom-up nesting space divide be C1 grades of containers, C2 grades of containers ..., CI grades of containers form a tree construction;
For in special time delay, domain, without constraint three kinds of scenes execute different live name registrations process it is as follows:
For there is any physical name registration request of special time delay, node LRNj is chosen according to spatial position, and in the node Live name registration is carried out on the parsing node of C1 grade container where LRNj;
For the registers entities request being limited in domain, live name registration is upward along tree construction from node LRNj Until top level container CI where node LRNj;It is carried out on the parsing node of the Ck grade container where each LRNj Registration, wherein 2≤k≤I;
Unconfined registers entities are requested, existing general-purpose system is directly entered and carries out name registration;It is described existing logical With the existing resolution system that system is including directly mapping DMAP;
It is as follows for different name resolution processes is executed in special time delay, domain, without three kinds of scenes of constraint:
Name resolution request under special delay requirement will complete live name in C1 grades of containers of bottom where node LRNj Dissection process;
Name resolution request will complete name resolving process in CI grades of containers of top layer where node LRNj in domain;
Existing general-purpose system is directly entered without constraint name resolution request to complete name resolving process.
2. the name registration and analytic method according to claim 1 based on space-time restriction scene, which is characterized in that be directed to Name registration and parsing in special time delay, domain, without three kinds of scenes of constraint, specifically include:
Step 1), which checks, simultaneously determines the request type that receives, the request type include: special time delay, in domain, without constraint three Kind scene;
Step 2) judgment step 1) in request type whether be name analysis request and whether be name registration request;If described Request type is name resolution request, and is not name registration request, then goes to step 3);If the request type name registration Request, and be not name resolution request, then jump directly to step 6);
Step 3) judgment step 2) name resolution request whether be under special delay requirement name resolution request: if special Name resolution request under delay requirement, then execute the name resolution process under special delay requirement;If not special time delay needs Name resolution request under asking, then go to step 4);
Step 4) judgment step 3) name resolution request whether be in domain name resolution request: if the name resolution in domain Request, then execute the name resolution process in domain;If not the name resolution in domain is requested, then step 5) is gone to;
Step 5) executes the existing process of analysis including directly mapping DMAP, process are as follows: by directly applying consistency Hash function, to search the mapping relations between physical name and network address, to obtain name resolution as a result, and return find Network address;
Step 6) executes different physical name register flow paths in special time delay, domain, without three kinds of different scenes of constraint respectively.
3. the name registration and analytic method according to claim 1 based on space-time restriction scene, which is characterized in that step 3) in, the name resolution process under special delay requirement is specifically included:
The local parsing node LRNj of some spatial position of step 301) is received for some entity unique identifier EUID's Name resolution request under special delay requirement;
The name resolution received in step 301) request is forwarded to where the local parsing node LRNj by step 302) The parsing node of C1 grades of containers, is denoted as C1-i;
Step 303) query steps 302) in parsing node C1-i in distributed hashtable DHT;If inquiring the name Network address NA corresponding to entity unique identifier EUID in analysis request, then directly return to the network address NA;If Network address NA corresponding to the entity unique identifier EUID in the name resolution request is not inquired, then returns to inquiry Failure, i.e., cannot provide the name resolution service under special delay requirement.
4. the name registration and analytic method according to claim 3 based on space-time restriction scene, which is characterized in that with repeatedly The result of the name resolution of step 3) is directly returned to request sender for the mode of iterative, or with recurrence The result of the name resolution of step 3) is turned originator by request and returns to request sender indirectly by the mode of recursive.
5. the name registration and analytic method according to claim 1 based on space-time restriction scene, which is characterized in that step 4) the name resolution process in the domain in specifically includes:
The local parsing node LRNj of some spatial position of step 401) is received for some entity unique identifier EUID's Name resolution request in domain, i.e., request without the name resolution under special delay requirement;
Step 402) inquires the distributed hashtable DHT in the local parsing node LRNj: if inquiring the local parsing Distributed hashtable DHT in node LRNj then directly returns to network address NA corresponding to the local parsing node LRNj; If not inquiring the distributed hashtable DHT in the local parsing node LRNj, the name resolution is requested to forward To the parsing node of the C2 grade container where the local parsing node LRNj, it is denoted as C2-i;
The grand filter BF of cloth in step 403) the inquiry parsing node C2-i;If inquiring in the parsing node C2-i The grand filter BF of cloth, then go to step 404);It, will if not inquiring the grand filter BF of cloth in the parsing node C2-i The name resolution request is forwarded to the parsing node of the C3 grade container where the local parsing node LRNj, is denoted as C3-i;
And so on, the parsing node of the Ck grade container where the local parsing node LRNj is inquired, is denoted as Ck-q, 2≤k≤ I;Wherein, q is the sequence number of any Ck grades of containers where LRNj, and value range is q >=1;If inquiring the parsing node The grand filter BF of cloth in Ck-q, then go to step 404);If not inquiring the grand filtering of cloth in the parsing node Ck-q Device BF, then be forwarded to the parsing node CI-r of some CI grades of container, then gos to step 405);
Distributed hashtable DHT in step 404) the inquiry parsing node C2-i;If inquiring the name resolution request In entity unique identifier EUID corresponding to network address NA, then directly return to the network address NA;If not inquiring To network address NA corresponding to the entity unique identifier EUID in name resolution request, then the name resolution is asked The parsing node C3-r for being forwarded to some C3 grades of container is sought, and goes to step 405);
And so on, inquire distributed hashtable DHT, 2≤k≤I, q in the parsing node Ck-q in some Ck grades of container; If inquiring network address NA corresponding to the entity unique identifier EUID in the name resolution request, directly return institute State network address NA;If with not inquiring network corresponding to the entity unique identifier EUID in the name resolution request Location NA, then be forwarded to the parsing node CI-r of some CI grades of container, and goes to step 405);
The grand filter BF of cloth in step 405) the inquiry parsing node CI-r;If inquiring in the parsing node CI-r The grand filter BF of cloth, then go to step 406);If not inquiring the grand filter BF of cloth in the parsing node CI-r, return Inquiry failure is returned, i.e., the analysis service of the name in domain cannot be provided;
Distributed hashtable DHT in step 406) the inquiry parsing node CI-r;If inquiring the name resolution request In entity unique identifier EUID corresponding to network address NA, then directly return to the network address NA;If not inquiring To network address NA corresponding to the entity unique identifier EUID in name resolution request, then inquiry failure is returned to, i.e., Name resolution service in domain cannot be provided.
6. the name registration and analytic method according to claim 5 based on space-time restriction scene, which is characterized in that with repeatedly The result of the name resolution of step 4) is directly returned to request sender for the mode of iterative, or with recurrence The result of the name resolution of step 4) is turned originator by request and returns to request sender indirectly by the mode of recursive.
7. the name registration and analytic method according to claim 1 based on space-time restriction scene, which is characterized in that step 6) process of the registers entities in, comprising:
Step 601) reviews and validate the physical name registration request type received, some entity corresponding to name therein Unique identifier is denoted as EUID;Wherein, the name registration request type include: special time delay, in domain, without three kinds of fields of constraint Scape;
Step 602) judgment step 601) in the physical name registration request type whether be reality under special delay requirement The request of body name registration;If the physical name registration request type is the physical name registration request under special delay requirement, It is then registered in local parsing node LRNj and its father node, the father node is the parsing node of some C1 grades of container, is denoted as C1-i, and update the distributed hash in the local Hash table HT and the father node C1-i in the local parsing node LRNj Table DHT;If the physical name registration request type is not the physical name registration request under special delay requirement, step is gone to It is rapid 603);
Step 603) judges whether the physical name registration request type is physical name registration request in domain;If the reality Body name registration request type is the physical name registration request in domain, then upward in local parsing node LRNj and its tree construction Grandparent node in register, the grandparent node be some C2 grades of container parsing node, be denoted as C2-j;And update local solution Analyse the local Hash table HT in node LRNj, the grand filter BF of cloth, the grandparent node C2-j in the grandparent node C2-j In distributed hashtable DHT, always update to as root node CI grade container parse node the grand filter BF of cloth with Distributed hashtable DHT;If the physical name registration request type is not the physical name registration request in domain, step is gone to It is rapid 604);
Step 604) executes the general physical name register flow path including directly mapping DMAP;Its process are as follows: registering When, consistency hash function is applied, directly to form the mapping relations between physical name and network address.
CN201710874886.6A 2017-09-25 2017-09-25 Name registration and analysis method based on space-time constraint field Active CN109561161B (en)

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 true CN109561161A (en) 2019-04-02
CN109561161B 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 (6)

* Cited by examiner, † Cited by third party
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
US20090222541A1 (en) * 2005-11-08 2009-09-03 Nortel Networks Limited Dynamic sensor network registry
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
US20150201039A1 (en) * 1999-09-01 2015-07-16 Esdr Network Solutions Llc Method, product, and apparatus for processing a data request
US20170236123A1 (en) * 2016-02-16 2017-08-17 Blockstack Inc. Decentralized processing of global naming systems

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150201039A1 (en) * 1999-09-01 2015-07-16 Esdr Network Solutions Llc Method, product, and apparatus for processing a data request
US20090222541A1 (en) * 2005-11-08 2009-09-03 Nortel Networks Limited Dynamic sensor network registry
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
US20170236123A1 (en) * 2016-02-16 2017-08-17 Blockstack Inc. Decentralized processing of global naming systems

Also Published As

Publication number Publication date
CN109561161B (en) 2020-05-26

Similar Documents

Publication Publication Date Title
WO2021218068A1 (en) Icn-based industrial internet identifier analysis system and data access method
CN108090064A (en) A kind of data query method, apparatus, data storage server and system
CN105224609B (en) Index query method and device
CN103957282B (en) Terminal user&#39;s domain name mapping acceleration system and its method in a kind of domain
US20160036640A1 (en) Internet protocol network mapper
US20160255047A1 (en) Methods and systems for determining domain names and organization names associated with participants involved in secured sessions
US9842140B2 (en) Dynamic input streams handling in DSMS
Hesselman et al. Increasing DNS security and stability through a control plane for top-level domain operators
CN108205569A (en) For updating the method and apparatus of configuration management database
CN116055448A (en) Identification data management platform for electric power operation
CN105357334B (en) A kind of storage of the address IPV6 and method for quickly querying based on the division of the address IPV6
CN112738297B (en) IP address positioning data acquisition method, device, server and storage medium
CN109561161A (en) A kind of name registration and analytic method based on space-time restriction scene
WO2019052075A1 (en) Query enhancement system and method for constructing elastic field based on time delay
CN115622976A (en) Domain name management system, domain name registration and resolution method, device, equipment and medium
Ma et al. An algorithm of street-level landmark obtaining based on yellow pages
CN109408479A (en) Daily record data adding method, system, computer equipment and storage medium
CN109831542A (en) A kind of flat fixed length name word processing method and system
Gómez-Cárdenas et al. A resource identity management strategy for combined fog-to-cloud systems
Kim et al. Implementation of a front-end and back-end NDN system for climate modeling application
US8014397B1 (en) Correlating packets in a data-communications environment
Liu et al. A dht-based discovery service for rfid network
CN105791461A (en) Operation method based on error domain name flow
CN105933470B (en) Stratification Service Source parses mapping method and system
CN107180042B (en) Search engine flow statistical method, device and system

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

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.

TR01 Transfer of patent right