CN1314239C - Method of carrying out field name system in moble self-organizing network - Google Patents
Method of carrying out field name system in moble self-organizing network Download PDFInfo
- Publication number
- CN1314239C CN1314239C CNB2004100319460A CN200410031946A CN1314239C CN 1314239 C CN1314239 C CN 1314239C CN B2004100319460 A CNB2004100319460 A CN B2004100319460A CN 200410031946 A CN200410031946 A CN 200410031946A CN 1314239 C CN1314239 C CN 1314239C
- Authority
- CN
- China
- Prior art keywords
- domain
- node
- name
- domain name
- name information
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 19
- 230000004044 response Effects 0.000 claims abstract description 23
- 238000013507 mapping Methods 0.000 claims description 29
- 230000008569 process Effects 0.000 claims description 11
- 230000003068 static effect Effects 0.000 claims description 7
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000012986 modification Methods 0.000 claims description 5
- 230000004048 modification Effects 0.000 claims description 5
- 238000005516 engineering process Methods 0.000 abstract description 2
- 230000007246 mechanism Effects 0.000 description 15
- 238000012545 processing Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 241001071864 Lethrinus laticaudis Species 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention belongs to the technical field of a mobile automatic-organization network (MANET), a method of which comprises the steps: domain name information of an MANET node is noticed by the MANET node, and the domain name information is stored in a domain name information cache DN_INFO_CACHE after the node is received; a node used for analyzing a domain name D_NAME searches a record R of which the domain name item is D_NAME in DN_INFO_CACHE; if the record R exists, then the node singly broadcasts a domain name information request message DN_REQ to an IP address recorded in R; if R does not exist, then all nodes in MANET are broadcast with one DN_REQ; whether nodes receiving DN_REQ are requested nodes or not are automatically judged by the nodes; if true, then a domain name information response message DN_REP is sent to the requested nodes, else, DN_REQ is forwarded out. The nodes receiving DN_REP firstly update DN_INFO_CACHE, then whether DN_INFO_CACHE is requested DN_REP of the nodes or not is judged; if true, then DN_INFO_CACHE is received to be processed, else, DN_INFO_CACHE is forwarded to the requested nodes. The method uses a piggyback technology in DN_REQ and DN_REP, so related nodes can obtain domain name information as much as possible in a single request/response period.
Description
Technical field
The invention belongs to mobile ad-hoc network MANET (Mobile Ad Hoc Networks) technical field, is a kind of implementation method of the domain name system DNS (Domain NameSystem) in the automatic configuring technical of MANET.
Background technology
Mobile ad-hoc network is a kind of wireless multi-hop network that does not have the base station, be a kind of have that height dynamic topological structure, node move arbitrarily, point-to-point from establishment, self-organizing, from supervising the network.Document [1] Ramanathan R, Redi J, " A Brief Overview of mobile Ad hocNetworks:Challenges and Directions ", IEEE Communications Magazine, 50th Anniversary Commemorative Issue[C], 2002.Traditional DNS requires have a special name server to provide domain name service for other node in the network, Here it is centralized domain name service/resolution system.And in topological dynamic change, the unsettled MANET of Radio Link, be difficult to find a centralized name server, therefore traditional DNS can't operate as normal in MANET.Document [2] Jaehoon Jeong is also arranged, Jungsoo Park, HyoungjunKim, and Kishik Park, " Name Service in IPv6 Mobile Ad-hoc Network ", ICOIN 2003, Jeju, Korea, February 2003, point out to solve domain name mapping problem among the MANET with the mechanism that broadcast request/clean culture is replied, its operation principle is: the network node that needs domain name mapping is to inquiry packet of the whole network broadcasting, the node of receiving broadcasting compares the domain name of oneself and the domain name of request analysis, if identically just oneself IP address is returned to the source node as replying clean culture, otherwise inquiry packet is broadcasted away.Domain name mapping that this simple broadcast request/clean culture is replied mechanism be because each domain name mapping of each node all will start once broadcasting, makes that broadcasting is frequent in the network, and this just causes the utilance of broadcast storm, network sharply to descend easily.
Summary of the invention
The object of the present invention is to provide the implementation method of domain name system in a kind of mobile ad-hoc network.
The invention belongs to mobile ad-hoc network MANET (Mobile Ad Hoc Networks) field, proposed the new distribution type domain name system DMDNS (Distributed MANET Domain Name System) of a kind of MANET of being applicable to.DMDNS adopts and to declare in good time/to upgrade in time, information incidentally/the novel mechanism that domain name buffer memory, cache hit/validation of information, broadcast request/clean culture are replied reduces the number of broadcast times of domain name request, alleviate the extra load of bringing owing to Web broadcast, guaranteed the correctness of domain-name information simultaneously.Under the situation of IP address static configuration, DMDNS has reduced the domain-name information response time, and application program can in time be communicated.
DMDNS is a kind of distributed domain name system, and it can finish the conversion that domain name arrives IP address (IPv4 or IPv6) among the MANET.Implementation method is as follows:
DMDNS is made up of domain name service module and domain name mapping module, all nodes in the MANET all move this two modules simultaneously, the domain name mapping module starts the domain name mapping process and the domain name response message of receiving is handled, the domain name service module is monitored the arrival of domain name request, and the domain name request message of receiving is handled.
Required node domain name, life cycle, the IP address of domain name service module obtained in the following manner: (the requiring the domain name in the same MANET territory not repeat) of user's appointment or the domain name that produces by automatic generting machanism and be kept at life cycle in the domain name configuration file, and the domain name service module is obtained domain name and lifetime information from this configuration file; The IP address of network interface card is specified (static configuration) by hand or is produced (dynamic-configuration) by the automatic generting machanism in address by the user, and the domain name service module reads the current IP address of network interface card from the address information file of system.After being configured domain name and IP address, node just can provide domain name service to other node.
The node of operation DMDNS is being safeguarded a domain-name information tabulation (DN_REC_LIST), be also referred to as the domain name buffer memory, this list records the domain-name information known to this node, it comprises following several field: sequence number (sequence number), domain name (NAME), classification (CLASS), type (TYPE), IP address, life cycle (TTL), more new logo (RF:Refresh Flag), timer life cycle (TTL_Timer), reply waiting timer (Reply_wait_Timer).Sequence number is one 32 a signless integer, is used for identifying the order of the domain-name information that same node produces, and is used for other node and upgrades the own domain-name information of being preserved; Sequence number is generated by node oneself and safeguard that a part that is used as domain-name information is transmitted in network.Whether more the length of new logo is 1, be used to identify this domain-name information and be updated; More new logo only is present in the domain name buffer memory, and it does not belong to the domain-name information that transmits in the network; Life cycle, timer was used for carrying out timing to TTL is overtime; Replying waiting timer is used for domain-name information response message wait timeout is carried out timing.Other several fields are consistent with the field meaning of traditional DNS definition.Document [3] P.Mockapetris, " DOMAIN NAMES-IMPLEMENTATION AND SPECIFICATION ", RFC1035, November 1987.Domain-name information request among the DMDNS/response message form uses the form of RFC1035 definition, preceding 4 sequence numbers that byte is used for preserving domain-name information of RDATA item among the RR (Resource Record).
The working mechanism of DMDNS:
The maintenance of DN_REC_LIST
DN_REC_LIST will upgrade as follows:
When (1) DMDNS started, the domain-name information of node oneself was added into DN_REC_LIST.
(2) (when using the address to dispose automatically, the IP address of node is dynamic change) during the IP address modification of node, the record of preserving the domain-name information of node oneself among the DN_REC_LIST is updated.
When the domain name in the domain-name information of (3) receiving did not exist in DN_REC_LIST, this information was used as new record and adds DN_REC_LIST.
(4) domain-name information R1 that receives and the record of certain among DN_REC_LIST R2 compare:
If (the R1. domain name==the R2. domain name)
If (R1. sequence number＞R2. sequence number)
R2 is updated to record R1;
Else if ((the R1. sequence number==R2. sequence number) ﹠amp; ﹠amp; (R1.IP_P==R2.IP_P))
//IP_P={ classification, type, IP address }
If (R1. life cycle＞R2. life cycle)
R2. is updated to R1. life cycle life cycle;
The timeout value of R2.TTL_Timer is updated to R1.TTL.
}
}
}
(5) timer TTL_Timer life cycle of record R is overtime among the DN_REC_LIST: if R is the domain-name information of node oneself, R.RF is changed to " not upgrading " state, otherwise R is deleted.
The domain-name information declaration
The MANET node is when meeting the following conditions, the domain-name information record RS of oneself is added DN_REC_LIST, RS.RF is changed to " upgrading " state, and starts timer RS.TTL_Timer (initial timeout value is RS.TTL), and the domain-name information of oneself is broadcasted away.The form of domain-name information declaration bag is identical with domain-name information response packet (DN_REP), and just the destination address of IP head is a broadcast address.Broadcast conditional:
When (1) node starts DMDNS; Or
(2) during the IP address modification of node; Or
(3) node is received the domain-name information request (DN_REQ) that is broadcast to oneself, and the RF sign of this node domain-name information record RS is in " not upgrading " state among the DN_REC_LIST.
The generation of domain-name information request (DN_REQ)
When the domain name mapping module is received the domain name mapping request that application program sends, generate the domain-name information request message, and the value of putting request counter (Req_Counter) is 0 according to the mode of traditional DNS.
The transmission of DN_REQ
(1) value with Req_Counter adds 1, and the domain-name information of node oneself is added among the DN_REQ;
(2) in the own DN_REC_LIST that is safeguarded, search the domain name D_name that is asked,
If have corresponding domain-name information record R, be changed to " not upgrading " state just to R.ip clean culture DN_REQ, and with R.RF; If just do not exist DN_REQ is broadcasted away, and in DN_REC_LIST, add original records RI (domain name field of RI is D_name, and RF is changed to " not upgrading " state, and all the other fields are empty);
(3) start timer R (or RI) .Reply_wait_Timer, wait for the arrival of DN_REP.
Value=2*NODE_TRAVERSAL_TIME*NET_DIAMETER of Reply_wait_Timer;
NODE_TRAVERSAL_TIME: in the processing time that node E-Packets, be generally 40 milliseconds;
Maximum hop count among the NET_DIAMETER:MANET between two nodes, relevant with network size.
The processing of DN_REQ
Receive the node of DN_REQ, will handle as follows:
(1) sets up or is maintained into the route of source node (send DN_REQ node);
(2) domain name and the domain name of oneself (being the domain name of RS record among the DN_REC_LIST) of asking among the DN_REQ compared, if equate just to forward to (5); Otherwise, enter (3);
(3) judge whether DN_REQ is the unicast packet of issuing oneself, if just forward (6) to; Otherwise, enter (4);
(4) DN_REQ is broadcasted away, forward (7) then to;
(5) judge the value of RS.RF,, just start domain-name information declaration mechanism, forward (7) then to if be in " not upgrading " state; Otherwise, enter (6);
(6) to source node clean culture DN_REP;
(7), in DN_REC_LIST, increase or upgrade the record of corresponding (domain name of carrying among domain name and the DN_REQ is identical) according to the domain-name information of the source node that carries among the DN_REQ.
The processing of DN_REP
Receive the node of DN_REP, will handle as follows:
(1) sets up or is maintained into the route of the node R_node that sends DN_REP;
(2) destination address of DN_REP and the address of node oneself are compared,, and forward (6) to if unequally just forward to the purpose node; Otherwise, enter (3);
What (3) lost efficacy this domain name correspondence replys waiting timer Reply_wait_Timer, and the domain name D_name that domain name and the node of R_node are asked compares then, if just equate the IP address of R_node is returned to application program, and forwards (6) to; Otherwise, enter (4);
(4) in DN_REC_LIST, search the record R that domain name is D_name,, just forward (6) to if R.RF is in " upgrading " state; Otherwise, enter (5);
(5) deletion record R, and restart the domain-name information request mechanism;
(6), in DN_REC_LIST, increase or upgrade corresponding record according to the domain-name information among the DN_REP.
The maintenance of sequence number
Node is when sending DN_REP, and except following exception, the sequence number of domain-name information all will add 1, and sequence number is stored in the domain name configuration file.
Exception: node receives that clean culture gives the DN_REQ of oneself, but the domain name of being asked among current domain name of node and the DN_REQ does not wait.
Domain-name information among the DN_REP
When (1) destination address of DN_REP is broadcast address (being the domain-name information declaration), only comprise the domain-name information of node oneself among the DN_REP.
When (2) destination address of DN_REP was unicast address, all be added into DN_REP greater than all domain-name informations of Min_ttl (a predefined threshold value is decided according to the real network environment, can be kept in the domain name configuration file) life cycle among the DN_REC_LIST.
The more maintenance of new logo (RF) among the DN_REC_LIST
When (1) increasing the domain-name information record RS of node oneself in DN_REC_LIST, the RF position of RS is changed to " upgrading " state.
When (2) domain-name information was declared, the RF position of the domain-name information of node oneself record RS was changed to " upgrading " state among the DN_REC_LIST.
(3) in DN_REC_LIST, increase or when upgrading domain-name information among the DN_REP, the RF position of domain-name information record R is changed to " upgrading " state.
When (4) increasing the domain-name information original records RI of requesting node in DN_REC_LIST, the RF position of RI is changed to " not upgrading " state.
(5) the domain-name information request mechanism is when the R.ip clean culture sends DN_REQ, and the RF position of R is changed to " not upgrading " state.
(6) TTL_Timer of the domain-name information of node oneself record RS is overtime among the DN_REC_LIST, and the RF position of RS is changed to " not upgrading " state.
The processing of timer expiry
(1) if the TTL_Timer of the domain-name information of node oneself record RS is overtime among the DN_REC_LIST, the RF position of RS is changed to " not upgrading " state.
(2) if the TTL_Timer of the record R except that RS is overtime among the DN_REC_LIST, R is deleted.
(3) if the Reply_wait_Timer of record R is overtime among the DN_REC_LIST, then
if(Req_Counter＜＝2){
If (R.RF is in " not upgrading " state)
Deletion record R;
Start the domain-name information request mechanism;
}else{
Return " domain name does not exist " to application program;
}
The optimization of domain-name information request mechanism
When DMDNS is applied to the outstanding MANET network of dynamic characteristic, can adopt following optimization mechanism further to reduce the domain name mapping time:
When DMDNS receives the domain name mapping request of application program, in the own DN_REC_LIST that is safeguarded, search the domain name D_name that is asked, if there is corresponding domain-name information record R, not immediately to R.ip clean culture DN_REQ, but whether the residue timeout value of at first judging R.TTL_Timer is greater than the product of Ratio and R.TTL, if directly send R.ip to application program, if not, send DN_REQ to the R.ip clean culture.Ratio is the number between 0 to 1, decides according to the dynamic characteristic of network; When Ratio was 1, this mechanism deteriorated to the domain-name information request mechanism of not optimizing; When Ratio is 0, be applied to the static constant MANET network in IP address; Typically, the Ratio value is 1/2, is applied to the moderate MANET network of IP address change speed.
Fig. 1 is seen in above-mentioned description for the domain name mapping process, sees Fig. 2 for the description of domain name service and forwards process.
The treatment mechanism of DMDNS and the simple broadcast request/clean culture domain name system of replying relatively, we obviously as can be seen the present invention have the following advantages:
(1) alleviated the broadcasting load of network.Because it is standby that domain-name information is got up by the node buffer memory, when node needed domain name mapping, the domain-name information of very possible request in buffer memory, therefore only needed clean culture to confirm the accuracy of this information.Because DMDNS used piggy mechanism, domain name request/reply can be to message institute many domain-name informations of node reception and registration on the path, the probability that the domain name of request analysis is hit in buffer memory is very big.In addition, because network node carries out the domain-name information declaration in good time, the node of the adding domain name request/response message approach buffer memory of oneself that upgrades in time makes that the correctness of the domain-name information that hits is very high in buffer memory, that is to say that to need the probability of broadcast request very little.Therefore DMDNS has reduced the number of times of broadcasting to a great extent, thereby has alleviated the extra load that Web broadcast caused.
(2) when the static configuration of IP address, DMDNS can reduce the domain-name information response time.When the static configuration of IP address, the mapping between domain name and the IP address is fixed, and the domain-name information that therefore hits in buffer memory is accurately, does not need to verify that its correctness just can return domain-name information to application program and reply.In addition, if the domain name of request analysis is not hit in local cache, and hit in the node buffer memory of request message process, this node can replace the purpose node to return domain-name information immediately replying.This obviously can reduce the response time of domain-name information.
The present invention has been used in the design of the IPv6 MANET of Computer Department of the Chinese Academy of Science test clinical system.
The invention technical scheme
A kind of domain name service/analytic method of distributed domain name system, network node carry out the domain-name information declaration in good time, make the up-to-date domain-name information of the timely buffer memory declaration of other node node on the network; In domain name request/response message, use piggy mechanism, guarantee that junction associated is once obtaining domain-name information as much as possible in request/acknowledge cycle, make the domain name mapping request strengthen at the probability that local cache hits, thus the broadcasting load that alleviates network; Under the static configuration situation of IP address, but the domain-name information that hits in any network node buffer memory need not confirmed just immediate answer, can effectively reduce the domain name response time; Under the dynamic-configuration situation of IP address, utilize the correctness of clean culture affirmation process assurance domain-name information, when reducing broadcasting, guaranteed the validity of domain name mapping.
A kind of domain name service/analytic method of distributed domain name system, its concrete steps are as follows:
Step S1: when node starts this domain name system or IP address modification, other node broadcasting domain name information answer message DN_REP in MANET, the own current domain-name information of declaration;
Step S2: receive the node of domain-name information declaration, upgrade the domain-name information buffer memory DN_REC_LIST of oneself according to the domain-name information that carries among the DN_REP;
Step S3: require the node that domain name D_NAME resolves is searched the record R that the domain name item is D_NAME in the DN_REC_LIST of oneself, if there is record R, the IP address clean culture of just being write down in R sends a domain-name information request message DN_REQ; If there is not record R, just the node of all in MANET is broadcasted a DN_REQ;
Step S4: receive the node of DN_REQ, judge at first whether oneself is the node of being asked, upgrade DN REC_LIST according to domain-name information entrained among the DN_REQ then,,, otherwise DN_REQ is forwarded with regard to execution in step 5 if oneself be the node of being asked;
Step 5: node is replied the DN_REQ that receives, node judges at first whether the domain-name information of declaring oneself last time is out-of-date life cycle, if just DN_REP of the node of all in MANET broadcasting replys; If life cycle is not out-of-date as yet,, carry all the effective domain name information known to the node among the DN_REP just to asking DN_REP of node clean culture to reply;
Step S6: receive the node of DN_REP, judge at first whether it is the domain name response message of issuing oneself,, otherwise it is transmitted to the request node, upgrade DN_REC_LIST according to the domain-name information that carries among the DN_REP then if with regard to execution in step S7;
Step S7: judge whether the domain-name information that carries among the DN_REP is own institute information requested, if just return the pairing IP of D_NAME address to application program, otherwise delete original record R, and restart the domain name mapping process, after if twice domain name mapping process finished, node is not received the own DN_REP that is asked yet, just returns " domain name does not exist " to application program.
Description of drawings
Fig. 1 is the domain name mapping flow chart.
Fig. 2 is domain name service and forwards flow chart.
Embodiment
Fig. 1 is the domain name mapping flow chart, and the treatment step of each incident is as follows among the figure:
Step S1.1: after node is received the domain name mapping request of application program, in the domain name buffer memory of oneself, search the domain name D_name that is asked; And initialization domain name mapping trial counter Req_Counter, its initial value is 0.
Step S1.2: judge domain name cache lookup result, if the record R of existence domain D_name by name in the domain name buffer memory enters S1.3; If the record of existence domain D_name by name not in the domain name buffer memory enters S1.4.
Step S1.3: the IP address clean culture of being write down in R sends DN_REQ, in order to confirm the correctness of D_name and IP_addr mapping; The IP head's of DN_REQ message address is the IP that is write down among the R, enters S1.5.
Step S1.4: to DN_REQ of the whole network broadcasting, in order to the IP address of inquiry D_name; The IP head's of DN_REQ message address is a broadcast address, is the multicast address of all nodes in the predefined expression MANET in IPv6.
Step S1.5: start waiting timer, wait for the arrival of domain-name information response message DN_REP; The value of Req_Counter adds 1.
Step S1.6: if timer expiry just enters S1.7; Otherwise, wait for up to DN_REP always and arriving, enter S1.8.
Step S1.7: judge that whether this domain name mapping trial Req_Counter surpasses 2 times, just returns " domain name does not exist " to application program if surpass; Otherwise, enter S1.4, broadcast DN_REQ again.
Step S1.8: in the domain name buffer memory, add or upgrade corresponding record according to the domain-name information among the DN_REP.
Step S1.9: judge whether the domain name among the DN_REP that receives is the domain name of asking, if just return the IP address of this domain name correspondence to application program; Otherwise, illustrate the mapping error of D_name and IP_addr in the former domain name buffer memory to enter S1.10.
Step S1.10:, just enter S1.11 if the record R of mapping error still is present in the domain name buffer memory; Otherwise, enter S1.12.
Step S1.11: will write down R and from the domain name buffer memory, delete, and restart the domain name mapping process.
Step S1.12: abandon the DN_REP that receives, do not do any other processing.
Fig. 2 is domain name service and forwards flow chart, and the treatment step of each incident is as follows among Fig. 2:
Step S2.1: when starting the IP address modification of DMDNS or node oneself, node is declared own current domain-name information to other network node to domain-name information response message DN_REP of MANET broadcasting.
Step S2.2: upgrade the domain-name information buffer memory according to the domain-name information request of receiving/response message.
Step S2.3: when receiving domain-name information request/response message, judge the type of this message according to the QR sign position (seeing RFC1035) of message packet head, if the domain-name information request message just enters S2.4; If the domain-name information response message just enters S2.6.
Step S2.4: whether the domain name of judging oneself is whether the domain name or the IP address of oneself of being asked is the purpose IP address of DN_REQ, if just reply, otherwise DN_REQ is forwarded.
Step S2.5: nslookup declaration state, if the domain name of declaration is out-of-date life cycle, promptly node is in domain name and does not declare state, to MANET broadcasting DN_REP, promptly enters S2.1; If node is in domain name and has declared state, just enter S2.8.
Step S2.6: the address according to the IP head of the DN_REP that receives judges whether this DN_REP is the message of issuing this node, if just by receiving among Fig. 1 that the handling process after the domain-name information response message handles; If not, DN_REP is forwarded, promptly enter S2.7.
Step S2.7: the destination address according to message packet forwards this domain-name information request/response message to other node.
Step S2.8: send a domain-name information response message DN_REP to the clean culture of request node.
Claims (1)
1. domain name service/the analytic method of a distributed domain name system is characterized in that, this method comprises:
A, network node are when starting this domain name system or IP address modification, and other node broadcasting domain name information answer message DN_REP in mobile ad-hoc network MANET declares own current domain-name information;
B, receive the node of domain-name information declaration, upgrade the domain-name information buffer memory DN_REC_LIST of oneself according to the domain-name information that carries among the DN_REP;
C, requirement are searched the record R that the domain name item is D_NAME to the node that domain name D_NAME resolves in the DN_REC_LIST of oneself, if there is record R, the IP address clean culture of just being write down in R sends a domain-name information request message DN_REQ; If there is not record R, just the node of all in MANET is broadcasted a DN_REQ;
D, receive the node of DN_REQ, judge at first whether oneself is the node of being asked, upgrade DN_REC_LIST according to domain-name information entrained among the DN_REQ then,,, otherwise DN_REQ is forwarded with regard to execution in step E if oneself be the node of being asked;
E, node are replied the DN_REQ that receives, node judges at first whether the domain-name information of declaring oneself last time is out-of-date life cycle, if just DN_REP of the node of all in MANET broadcasting replys; If life cycle is not out-of-date as yet,, carry all the effective domain name information known to the node among the DN_REP just to asking DN_REP of node clean culture to reply;
F, receive the node of DN_REP, judge at first whether it is the domain name response message of issuing oneself,, otherwise it is transmitted to the request node, upgrade DN_REC_LIST according to the domain-name information that carries among the DN_REP then if with regard to execution in step G;
G, judge whether the domain-name information that carries among the DN_REP is own institute information requested, if just return the pairing IP of D_NAME address to application program, otherwise delete original record R, and restart the domain name mapping process, after if twice domain name mapping process finished, node is not received the own DN_REP that is asked yet, just returns " domain name does not exist " to application program;
H, under the static configuration situation of IP address, the domain-name information that hits in any network node buffer memory just need not confirm that can send the domain name response message to requesting node immediately reply.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100319460A CN1314239C (en) | 2004-03-31 | 2004-03-31 | Method of carrying out field name system in moble self-organizing network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100319460A CN1314239C (en) | 2004-03-31 | 2004-03-31 | Method of carrying out field name system in moble self-organizing network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1564539A CN1564539A (en) | 2005-01-12 |
| CN1314239C true CN1314239C (en) | 2007-05-02 |
Family
ID=34481274
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100319460A Expired - Fee Related CN1314239C (en) | 2004-03-31 | 2004-03-31 | Method of carrying out field name system in moble self-organizing network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1314239C (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8621086B2 (en) * | 2010-03-24 | 2013-12-31 | Alcatel Lucent | System and domain name server for ad-hoc networks |
| CN102469166A (en) | 2010-10-29 | 2012-05-23 | 国际商业机器公司 | Method for providing virtual domain name system (DNS) in local area network, terminal equipment and system |
| CN103905581A (en) * | 2014-02-26 | 2014-07-02 | 曾宪钊 | DNS high-speed analytical solution based on behavior differences and matched flow class attack resistance safety solution |
| CN105884633B (en) * | 2016-05-07 | 2017-12-26 | 浙江大学 | A kind of tetracycline stearic acid grafting and its preparation and application |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1209249A (en) * | 1996-02-20 | 1999-02-24 | 惠普公司 | Method for accessing target entity over communication network |
| EP1075113A2 (en) * | 1999-08-06 | 2001-02-07 | Sony Corporation | Exchange and address resolution method |
| CN1194502C (en) * | 2002-04-22 | 2005-03-23 | 华为技术有限公司 | System and method for managing access authority of network users |
-
2004
- 2004-03-31 CN CNB2004100319460A patent/CN1314239C/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1209249A (en) * | 1996-02-20 | 1999-02-24 | 惠普公司 | Method for accessing target entity over communication network |
| EP1075113A2 (en) * | 1999-08-06 | 2001-02-07 | Sony Corporation | Exchange and address resolution method |
| CN1194502C (en) * | 2002-04-22 | 2005-03-23 | 华为技术有限公司 | System and method for managing access authority of network users |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1564539A (en) | 2005-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1691798A (en) | Mobile node, mobile control node, packet communication system and mobile detection method | |
| CN1801764A (en) | Internet access method based on identity and location separation | |
| CN1315279C (en) | Apparatus and method for retransmitting data packets in mobile ad hoc network environment | |
| CN1697456A (en) | Communication method and device in mobile state having multi-interfaces | |
| CN1607783A (en) | Processing broadcast data in a mobile ac-hoc network | |
| CN1802013A (en) | Method and apparatus for realizing network service provider discovery | |
| CN1581836A (en) | Domain name service system and method | |
| CN1315314C (en) | Communication system and method therefor | |
| CN1866863A (en) | Vicinage finding method and system for network apparatus | |
| CN1852581A (en) | Method for transmitting data on downward link | |
| CN1929447A (en) | Method and device for searching address prefixion and message transfer method and system | |
| CN1802012A (en) | Method for realizing network service provider selection | |
| CN1929497A (en) | Method and system for obtaining moving nodes local proxy information | |
| CN101043698A (en) | Method for paging terminal of idle mode | |
| CN1288881C (en) | Address automatic distributing method in mobile self organizing network | |
| CN1700647A (en) | Information processing apparatus and method for wireless network | |
| CN1956417A (en) | Communication system, communication terminal, route control method and router | |
| CN1852256A (en) | Method and system for data transmission in wireless net-like network | |
| CN1192576C (en) | Multicast business realizing method in mobile network | |
| CN1314239C (en) | Method of carrying out field name system in moble self-organizing network | |
| CN1859766A (en) | Method for processing service bearing while communication system sponsor service request | |
| CN1946064A (en) | Message repeat method and device | |
| CN1564540A (en) | Internet access method based on demanded route in mobile self-organizing net | |
| CN101043700A (en) | Method for paging terminal under idle mode | |
| CN1181655C (en) | Data packet transmission method in mobile IP |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Assignee: Beijing Zhongke Jingshang Technology Co., Ltd. Assignor: Institute of Computing Technology, Chinese Academy of Sciences Contract record no.: 2011110000143 Denomination of invention: Method of carrying out field name system in moble self-organizing network Granted publication date: 20070502 License type: Exclusive License Open date: 20050112 Record date: 20110823 |
|
| EC01 | Cancellation of recordation of patent licensing contract | ||
| EC01 | Cancellation of recordation of patent licensing contract |
Assignee: Beijing Zhongke Polytron Technologies Inc Assignor: Institute of Computing Technology, Chinese Academy of Sciences Contract record no.: 2011110000143 Date of cancellation: 20181212 |
|
| EM01 | Change of recordation of patent licensing contract | ||
| EM01 | Change of recordation of patent licensing contract |
Change date: 20181212 Contract record no.: 2011110000143 Assignee after: Beijing Zhongke Polytron Technologies Inc Assignee before: Beijing Zhongke Jingshang Technology Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070502 Termination date: 20190331 |