CN100334861C - A method of Internet domain name access based on on-demand routing in self-organized network - Google Patents

A method of Internet domain name access based on on-demand routing in self-organized network Download PDF

Info

Publication number
CN100334861C
CN100334861C CNB2004100989566A CN200410098956A CN100334861C CN 100334861 C CN100334861 C CN 100334861C CN B2004100989566 A CNB2004100989566 A CN B2004100989566A CN 200410098956 A CN200410098956 A CN 200410098956A CN 100334861 C CN100334861 C CN 100334861C
Authority
CN
China
Prior art keywords
gateway
name server
domain name
node
message
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
Application number
CNB2004100989566A
Other languages
Chinese (zh)
Other versions
CN1633107A (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.)
Institute of Computing Technology of CAS
Original Assignee
Institute of Computing Technology of CAS
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 Computing Technology of CAS filed Critical Institute of Computing Technology of CAS
Priority to CNB2004100989566A priority Critical patent/CN100334861C/en
Publication of CN1633107A publication Critical patent/CN1633107A/en
Application granted granted Critical
Publication of CN100334861C publication Critical patent/CN100334861C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The present invention relates to a method of the access of Internet domain names on the basis of on-demand routes in mobile self-organized networks, which belongs to the technical field of mobile self-organized networks MANET. In the method, RREQ and RREP messages in AODV route protocols are used for loading the request information of a domain name server and the service information of domain names; route establishment, gateway configuration and the configuration of a domain name server of the Internet are combined together. The method comprises the steps: an MANET node S is added for unicasting the request information of a domain name server to a gateway or broadcasting the request information of a domain name server to a network; if the node receiving the request information discovers that the node can directly respond, the service information of domain names is transmitted to the S; otherwise, the request information is retransmitted; after a gateway receives the request information, the service information of domain names is generated according to the configuration information of the gateway; the service information of domain names is unicast and transmitted to the S; after the S receives the service information of domain names, a route table is updated according to the information, and the own gateway and the domain name server are configured.

Description

In a kind of MANET based on the method for Internet domain name access of route as required
Technical field
The invention belongs to mobile ad-hoc network MANET (Mobile Ad Hoc Networks) technical field, is a kind of implementation method of internet domain server configuration 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 topology, node move arbitrarily, point-to-point from establishment, self-organizing, from supervising the network [1] Ramanathan R, Redi J, " A Brief Overview of mobile Ad hoc Networks:Challenges and Directions ", IEEE Communications Magazine, 50 ThAnniversary Commemorative Issue[C], 2002.AODV (Ad hoc On-demandDistance Vector) is a kind of Routing Protocol [2] C.Perkins that drives as required among the MANET, " Adhoc On-Demand Distance Vector (AODV) Routing ", RFC3561, July 2003; AODV6 is a kind of AODV agreement of expansion, be used for using MANET [3] the Charles E.Perkins of IPv6, " Ad hoc On-Demand Distance Vector (AODV) Routingfor IP version 6 ", draft-perkins-manet-aodv6-01.txt, November 2000; The difference of AODV and AODV6 mainly is that the address size in the route control message is different, and in order to narrate conveniently, AODV and AODV6 are collectively referred to as AODV hereinafter.
The node of initiating the name server request in the MANET network is called as source node; The node of transmitting name server request or domain name service message in the MANET network is called as intermediate node.MANET node both can be used as the source node when oneself initiating the name server request, can be used as the intermediate node of other MANET node when initiating name server request again.
In order to alleviate the loaded down with trivial details of MANET user's manual configuration, MANET quickly networking, flexible easy-to-use characteristic are found full expression, must in MANET, use various automatic configuring technicals, comprise: address configuration automatically, domain name mapping and service discovery [4] Jaehoon Jeong, Jungsoo Park, " Autoconfiguration Technologies for IPv6 Multicast Service in MobileAd-hoc Networks ", The International Conference on Information Networking, 2002.And the automatic configuration of internet domain server just belongs to an important component part of domain name mapping, the MANET node configuration internet domain server, just can be by the node on the domain name access Internet.
Summary of the invention
The object of the present invention is to provide in a kind of mobile ad-hoc network based on the method for Internet domain name access of route (operation AODV Routing Protocol) as required.
Internet domain name is the domain name that can use in the Internet scope for the node configuration on the Internet.Internet domain server is a node among the Internet, and it can provide the domain name mapping service for other node in the network.The MANET network is connected with Internet by gateway, and the MANET node is by the node among the gateway access Internet.It is exactly name server that the present invention requires gateway itself, perhaps gateway configuration has internet domain server (gateway can carry out domain name mapping by this name server), otherwise can't be MANET node configuration internet domain server, also just can't the access the Internet domain name.The present invention requires MANET node operation AODV Routing Protocol.
Want access the Internet domain name (by domain name access Internet node), be necessary for MANET node configuration internet domain server, promptly in network, find a server that the Internet domain name mapping can be provided, and this server is configured to the domain name resolution server of MANET node.
The present invention is based on the AODV Routing Protocol, utilize route request information RREQ message and route replies message RREP message among the AODV to carry domain name server requests message and domain name service message respectively, the routing table of utilizing AODV to define creates a mechanism and finishes the internet domain server layoutprocedure.
It is the name server request message that the present invention revises RREQ message, and revising RREP message is domain name service message.Amended message format is as follows:
0 78 1314 2324 31
Type J R G D U I N M P Res Hop Count
RREQ ID
Destination IP Address
Destination Sequence Number
Originator IP Address
Originator Sequeuce Number
The name server request message
I gateway configuration request mark: 0 this message of expression is common AODV RREQ
1 expression request gateway configuration
N name server configuring request sign: 0 this message of expression is common AODV RREQ
1 this message of expression is the name server request message
N is 1 o'clock, and I must put 1
M replys sign: 0 expression can only be replied this request message by gateway;
1 expression intermediate node can be replied this message
The P protocol-identifier: 0 expression source IP address is the IPv4 address;
1 expression source IP address is the IPv6 address
All the other fields are consistent with the definition of AODV
0 78 1011 1617 23 24 31
Type R A I N E P Res Prefix Sz Hop Count
Destination IP Address
Destination Sequence Number
Originator IP Address
Lifetime
Name Server IP Address
Domain name service message
The I gateway configuration is replied sign: 0 this message of expression is common AODV EREP
1 this message of expression is that gateway configuration is replied
Sign is replied in the N domain name service: 0 this message of expression is common AODV RREP
1 this message of expression is domain name service message
N is 1 o'clock, and I must put 1
E type of error sign: 0 expression inerrancy; 1 expression " no name server "
The P protocol-identifier: the IP address in 0 this message of expression is the IPv4 address;
IP address in 1 this message of expression is the IPv6 address
The IP address of Name Server IP Address domain server
All the other fields are consistent with the definition of AODV
The realization of method of Internet domain name access proposed by the invention is made up of name server configuration module and configuration service module.The configuration service module operates on the gateway, is responsible for the name server request message of receiving is replied; The name server configuration module operates on the MANET node, is responsible for sending the name server request message, handles and transmit name server configuration messages (comprising domain name service message and name server request message).
The internet domain server configuration flow is as follows:
When a node adds the MANET network, start the name server layoutprocedure, send the name server request message to gateway.Source node name server configuration flow such as Fig. 1 show.
After intermediate node is received the name server request message, this message is handled, and to gateway forwards.Intermediate node also can be handled and transmit domain name service message.Intermediate node Message Processing idiographic flow as shown in Figure 3.
After gateway is received the name server request message, send domain name service message to the source requesting node and reply.The gateway domain name service is replied flow process as shown in Figure 2.
Domain name service message arrives source node through intermediate node handles with after transmitting.After source node is received this message, name server wherein is configured to the first-selected name server (for example, in linux operating system, the IP address of this name server can being added among file/etc/resolv.conf) of oneself.Start gateway timer life cycle T1 then, the clocking value of T1 is the Lifetime value in the domain name service message, and overtime as T1, the gateway configuration of node is changed to disarmed state, and the name server configuration is deleted.If this message is " no name server " message, promptly the E position in the message is 1, returns " no name server " indication to the user.
Name server layoutprocedure above analyzing, characteristics of the present invention as can be seen:
(1) gateway configuration process, name server layoutprocedure and AODV route being set up process combines, transmission that can shared control messages message, reduce and transmit the Internet resources that these messages are wasted separately, make the realization of whole M ANET system more unified simultaneously.
(2) allow intermediate node to name server request reply, not only reduced the shared network bandwidth of unnecessary transmission, and the source requesting node of making obtains domain name service information quickly, use domain name access Internet node more in time.
(3) use method that the present invention proposes can be apace for MANET node configuration gateway and name server, be established to the route of gateway, minimizing user manual configuration loaded down with trivial details makes the user can visit Internet in time, easily.
In the mobile ad hoc network based on the method for Internet domain name access of route as required: name server configuration, gateway configuration and route set up combine; The source node S that adds MANET sends the name server request message to gateway clean culture transmission or to Web broadcast, in order to obtain the configuration information of gateway and name server; Intermediate node is received the name server request message, according to this information updating routing table, if this message allows intermediate node to reply, and node oneself has gateway and name server configuration messages, just send domain name service message to the source node S clean culture, otherwise, the name server request message is forwarded; After gateway was received the name server request message, the name server configuration according to oneself generated domain name service message, sends to source node S; Intermediate node and source node S are received domain name service message, according to the gateway and the name server of wherein gateway information and domain name server information configuration oneself, are established to the route of gateway; Intermediate node also is responsible for domain name service message is transmitted to source node S.After configuring gateway and name server, the MANET node just can pass through the node on the domain name access Internet.
Description of drawings
Fig. 1 is name server configuration flow figure.
Fig. 2 is that flow chart is replied in the gateway domain name service.
Fig. 3 is an intermediate node Message Processing flow chart.
Embodiment
Based on the method for Internet domain name access of route as required, name server configuration flow wherein is as follows in the MANET:
Step S1: when source node is initiated the name server request, check in the routing table whether gateway information is arranged,, send nearly twice name server request message to the gateway clean culture if gateway information is arranged, if do not have, send nearly twice name server request message to Web broadcast;
Step S2: start the arrival that timer is waited for domain name service message, if twice of timer overtime after, do not receive domain name service message, enter step S3; If receive domain name service message, forward step S4 to;
Step S3: if preceding twice is that clean culture sends the name server request, nearly twice request of broadcasting again forwards step S2 to; Otherwise, send " no name server " indication, finish;
Step S4: after receiving domain name service message,, finish according to information updating routing table wherein, the gateway and the name server of configuration oneself.
The treatment step of each incident is as follows among Fig. 1: (name server configuration flow)
S1.1: when the name server configuration module that moves on the MANET source node S started, source node S was at first searched routing table, checked in the routing table whether gateway information is arranged, and judged promptly whether the IP address that is designated gateway is arranged in the routing table, if having, forwarded S1.4 to; If do not have gateway information in the routing table, enter S1.2;
S1.2: the initial value that source node S is put request counter Counter is 2, enters S1.3;
S1.3: source node S broadcasting domain name server requests message, forward S1.6 then to, in the name server request message: I position 1, N position 1, decide according to network condition and acknowledgment strategy the M position, and decide according to the employed IP protocol type of node the P position;
S1.4: the initial value that source node S is put request counter Counter is 0, enters S1.5;
S1.5: source node S sends the name server request message to the gateway clean culture, enter S1.6 then, in the name server request message: I position 1, N position 1, decide according to network condition and acknowledgment strategy the M position, decide according to the employed IP protocol type of node the P position, the gateway ip address of the destination address of IP head for finding in routing table;
S1.6: the value of source node S request counter Counter adds 1, and starts domain name service Messages-Waiting timer T2, waits for the arrival of domain name service acknowledgement messaging, and be DN_SERVER_WAIT_TIME the time-count cycle of T2, and its value is decided according to the network environment of reality.Enter S1.7;
S1.7: wait for that T2 is overtime, if in the not overtime process of T2, receive the domain name service message of issuing oneself, release timer T2 forwards S1.11 to; If T2 is overtime, enter S1.8;
S1.8: whether source node S judges the value of request counter Counter less than 2, if than 2 little, forward S1.5 to, once more clean culture name server request message; If the value of Counter is not less than 2, enter S1.9;
S1.9: whether source node S judges the value of request counter Counter greater than 3, if than 3 big, enter S1.10; Otherwise, forward S1.3 to, broadcast domain name server requests message once more;
S1.10: based on following reason, system thinks do not have name server in this MANET network, just return one " no name server " indication to the user, reason: when in routing table, gateway information being arranged, to twice of gateway clean culture with to twice name server request message of Web broadcast, and do not receive the domain name service acknowledgement messaging; In routing table, during no gateway information,, and do not receive the domain name service acknowledgement messaging to twice name server request message of Web broadcast;
S1.11: when source node S is received domain name service message, upgrade routing table, be established to the route of gateway, enter S1.12 according to the regulation of AODV;
S1.12: source node S is upgraded gateway configuration, and soon the Destination IPAddress in the domain name service message is set to the gateway of oneself, enters S1.13;
S1.13: source node S checks in the network whether there is not internet domain server, checks promptly whether the E position in the domain name service message is 1, if enter S1.14; Otherwise, forward S1.15 to;
S1.14: source node S configuration internet domain server is empty, forwards S1.10 to;
S1.15: source node S is configured to the Name Server IPAddress in the domain name service message the first-selected name server of oneself.
Based on the method for Internet domain name access of route as required, it is as follows that flow process is replied in gateway domain name service wherein in the MANET:
Step S1: whether gateway inspection oneself be name server or dispose name server, if, enter step S2, otherwise, forward step S3 to;
Step S2: gateway sends domain name service message to requesting node;
Step S3: gateway sends " no name server " message to requesting node or MANET network.
The treatment step of each incident is as follows among Fig. 2: (flow process is replied in the gateway domain name service)
S2.1: when gateway is received the name server request message, first-selection judges whether oneself is name server, be oneself whether to have moved domain name service program (as BIND) to provide the domain name mapping service,, enter S2.2 if gateway is a name server for other network node; Otherwise, forward S2.3 to;
S2.2: gateway places the Name Server IPAddress field of domain name service message with oneself IP address, forwards S2.5 to;
S2.3: gateway judges oneself whether to dispose name server (for example, in linux operating system, judging the IP address that whether disposes name server among file/etc/resolv.conf), if the name server configuration is arranged, enter S2.4, otherwise, forward S2.6 to;
S2.4: the at first name server IP address that gateway is disposed oneself places the Name Server IPAddress field of domain name service message, enters S2.5;
S2.5: gateway sends domain name service message to the requesting node clean culture, wherein: I position 1, N position 1, E position 0, P decides according to the employed IP version of node;
S2.6: whether gateway judges the broadcast interval time greater than threshold value Broadcast_Time_Interval (a predefined value is decided according to the real network situation), and promptly the current time deducts airtime last time whether greater than this threshold value, if enter S2.7; Otherwise, forward S2.8 to;
S2.7: gateway writes down this airtime, and broadcast transmission " no name server " is replied, and promptly sends the domain name service message of E position 1 to requesting node;
S2.8: the gateway clean culture sends " no name server " and replys, and promptly sends the domain name service message of E position 1 to requesting node.
Based on the method for Internet domain name access of route as required, intermediate node Message Processing flow process wherein is as follows in the MANET:
Step S1: intermediate node is judged the name server configuration messages type of being received, if domain name service message enters step S2; If the name server request message forwards step S3 to; Step S2: intermediate node is transmitted domain name service message to requesting node, upgrades routing table, gateway configuration and name server configuration;
Step S3: intermediate node upgrades routing table, checks whether this message allows intermediate node to reply, if allow, and intermediate node has effective gateway configuration, sends domain name service message to requesting node; Otherwise, the name server request message is forwarded.
The treatment step of each incident is as follows among Fig. 3: (intermediate node Message Processing flow process)
S3.1: receive the name server configuration messages when the MANET intermediate node, at first judge the type of this configuration messages, if the name server request message forwards S3.6 to; If domain name service message enters S3.2;
S3.2: intermediate node is transmitted domain name service message to requesting node, enters S3.3;
S3.3: intermediate node upgrades gateway configuration, and the Destination IPAddress in the domain name service message is set to the gateway of oneself, enters S3.4;
S3.4: intermediate node upgrades routing table according to the regulation of AODV, is updated to the route of gateway, enters S3.5;
S3.5: intermediate node upgrades the name server configuration, the NameServer IP Address in the domain name service message is configured to the at first name server of oneself;
S3.6: intermediate node upgrades routing table, is updated to the route of requesting node, enters S3.7;
S3.7: intermediate node judges whether this message allows intermediate node to reply, and checks promptly whether the M position in the name server request message puts 1, if forward S3.9 to; Otherwise, enter S3.8;
S3.8: intermediate node forwards the name server request message;
S3.9: intermediate node is searched routing table, whether has the route R of gateway, if find route R, forwards S3.11 to; Otherwise, enter S3.10;
S3.10: intermediate node forwards the broadcasting of name server request message;
S3.11: whether the Reply Sequence Number among the intermediate node comparison R is less than the Reply Sequence Number in the request message, if forward S3.13 to; Otherwise, enter S3.12;
S3.12: intermediate node judges whether oneself disposes internet domain server, if forward S3.14 to; Otherwise, enter S3.13;
S3.13: intermediate node is transmitted to gateway with the clean culture of name server request message;
S3.14: intermediate node sends domain name service message to the requesting node clean culture, wherein: I position 1, N position 1, E position 0, P decides according to the employed IP version of node, Name Server IPAddress is the domain name server address that node oneself is disposed, and all the other fields are consistent with the regulation of AODV.

Claims (4)

  1. In the mobile ad-hoc network based on the method for Internet domain name access of route as required, it is characterized in that this method comprises:
    RREQ message in the modification AODV Routing Protocol increases gateway configuration request mark I, name server configuring request sign N, replys sign M and protocol-identifier P as the name server request message in RREQ;
    RREP message in the modification AODV Routing Protocol is as domain name service message, and the increase gateway configuration is replied sign I in RREP, sign N, type of error sign E, protocol-identifier P and name server IP address field are replied in domain name service;
    Shared routing table foundation, gateway configuration and name server layoutprocedure;
    When source node S adds MANET, start the name server layoutprocedure, send the name server request message;
    After intermediate node is received the name server request message, upgrade routing table, and judge whether oneself can reply this request, if oneself have name server configuration information and source node S to allow intermediate node to reply, send domain name service message to source node S and reply, otherwise the name server request message is forwarded;
    After gateway is received the name server request message, send domain name service message to source node S and reply;
    After intermediate node is received domain name service message, upgrade routing table and gateway configuration, and this message is transmitted to source node S;
    After source node S is received domain name service message, according to wherein gateway and own gateway and the name server of domain name server information configuration, and the renewal routing table.
  2. According in the mobile ad hoc network of claim 1 based on the method for Internet domain name access of route as required, it is characterized in that described source node S configuration name server comprises the steps:
    S1.1: when the name server configuration module that moves on the MANET source node S started, source node S was at first searched routing table, checked in the routing table whether gateway information is arranged, and judged promptly whether the IP address that is designated gateway is arranged in the routing table, if having, forwarded S1.4 to; If do not have gateway information in the routing table, enter S1.2;
    S1.2: the initial value that source node S is put request counter Counter is 2, enters S1.3;
    S1.3: source node S broadcasting domain name server requests message, forward S1.6 then to, in the name server request message: I position 1, N position 1, decide according to network condition and acknowledgment strategy the M position, and decide according to the employed IP protocol type of node the P position;
    S1.4: the initial value that source node S is put request counter Counter is 0, enters S1.5;
    S1.5: source node S sends the name server request message to the gateway clean culture, enter S1.6 then, in the name server request message: I position 1, N position 1, decide according to network condition and acknowledgment strategy the M position, decide according to the employed IP protocol type of node the P position, the gateway ip address of the destination address of IP head for finding in routing table;
    S1.6: the value of source node S request counter Counter adds 1, and start domain name service Messages-Waiting timer T2, and wait for the arrival of domain name service acknowledgement messaging, be DN_SERVER_WAIT_TIME the time-count cycle of T2, its value is decided according to the network environment of reality, enters S1.7;
    S1.7: wait for that T2 is overtime, if in the not overtime process of T2, receive the domain name service message of issuing oneself, release timer T2 forwards S1.11 to; If T2 is overtime, enter S1.8;
    S1.8: whether source node S judges the value of request counter Counter less than 2, if than 2 little, forward S1.5 to, once more clean culture name server request message; If the value of Counter is not less than 2, enter S1.9;
    S1.9: whether source node S judges the value of request counter Counter greater than 3, if than 3 big, enter S1.10; Otherwise, forward S1.3 to, broadcast domain name server requests message once more;
    S1.10: based on following reason, system thinks do not have name server in this MANET network, just return one " no name server " indication to the user, reason: when in routing table, gateway information being arranged, to twice of gateway clean culture with to twice name server request message of Web broadcast, and do not receive the domain name service acknowledgement messaging; In routing table, during no gateway information,, and do not receive the domain name service acknowledgement messaging to twice name server request message of Web broadcast;
    S1.11: when source node S was received domain name service message, source node S was upgraded routing table according to the regulation of AODV, is established to the route of gateway, enters S1.12;
    S1.12: source node S is upgraded gateway configuration, and soon the Destination IPAddress in the domain name service message is set to the gateway of oneself, enters S1.13;
    S1.13: source node S checks in the network whether there is not internet domain server, checks promptly whether the E position in the domain name service message is 1, if enter S1.14; Otherwise, forward S1.15 to;
    S1.14: source node S configuration internet domain server is empty, forwards S1.10 to;
    S1.15: source node S is configured to the Name Server IP Address in the domain name service message the first-selected name server of oneself.
  3. According in the mobile ad hoc network of claim 1 based on the method for Internet domain name access of route as required, it is characterized in that, after described gateway is received the name server request message, send domain name service message to source node S and reply and comprise:
    S2.1: when gateway is received the name server request message, first-selectedly judging whether oneself is name server, promptly oneself whether has moved the domain name service program and provides the domain name mapping service for other network node, is name server as if gateway, enters S2.2; Otherwise, forward S2.3 to;
    S2.2: gateway places the Name Server IPAddress field of domain name service message with oneself IP address, forwards S2.5 to;
    S2.3: gateway judges whether oneself disposes name server, if the name server configuration is arranged, enters S2.4, otherwise, forward S2.6 to;
    S2.4: the at first name server IP address that gateway is disposed oneself places the Name Server IP Address field of domain name service message, enters S2.5;
    S2.5: gateway sends domain name service message to the requesting node clean culture, wherein: I position 1, N position 1, E position 0, P decides according to the employed IP version of node;
    S2.6: whether gateway judges the broadcast interval time greater than threshold value Broadcast_Time_Interval, and promptly the current time deducts airtime last time whether greater than this threshold value, if enter S2.7; Otherwise, forward S2.8 to;
    S2.7: gateway writes down this airtime, and broadcast transmission " no name server " is replied, and promptly sends the domain name service message of E position 1 to requesting node;
    S2.8: the gateway clean culture sends " no name server " and replys, and promptly sends the domain name service message of E position 1 to requesting node.
  4. According in the mobile ad hoc network of claim 1 based on the method for Internet domain name access of route as required, it is characterized in that, after described intermediate node is received domain name service message, upgrade routing table and gateway configuration, and this message is comprised the steps: to the source node S forwarding
    S3.1: receive the name server configuration messages when the MANET intermediate node, at first judge the type of this configuration messages, if the name server request message forwards S3.6 to; If domain name service message enters S3.2;
    S3.2: intermediate node is transmitted domain name service message to requesting node, enters S3.3;
    S3.3: intermediate node upgrades gateway configuration, and the Destination IPAddress in the domain name service message is set to the gateway of oneself, enters S3.4;
    S3.4: intermediate node upgrades routing table according to the regulation of AODV, is updated to the route of gateway, enters S3.5;
    S3.5: intermediate node upgrades the name server configuration, the NameServer IP Address in the domain name service message is configured to the at first name server of oneself;
    S3.6: intermediate node upgrades routing table, is updated to the route of requesting node, enters S3.7;
    S3.7: intermediate node judges whether this message allows intermediate node to reply, and checks promptly whether the M position in the name server request message puts 1, if forward S3.9 to; Otherwise, enter S3.8;
    S3.8: intermediate node forwards the name server request message;
    S3.9: intermediate node is searched routing table, whether has the route R of gateway, if find route R, forwards S3.11 to; Otherwise, enter S3.10;
    S3.10: intermediate node forwards the broadcasting of name server request message;
    S3.11: whether the Reply Sequence Number among the intermediate node comparison R is less than the Reply Sequence Number in the request message, if forward S3.13 to; Otherwise, enter S3.12;
    S3.12: intermediate node judges whether oneself disposes internet domain server, if forward S3.14 to; Otherwise, enter S3.13;
    S3.13: intermediate node is transmitted to gateway with the clean culture of name server request message;
    S3.14: intermediate node sends domain name service message to the requesting node clean culture, wherein: I position 1, N position 1, E position 0, P decides according to the employed IP version of node, Name ServerIP Address is the domain name server address that node oneself is disposed, and all the other fields are consistent with the regulation of AODV.
CNB2004100989566A 2004-12-17 2004-12-17 A method of Internet domain name access based on on-demand routing in self-organized network Active CN100334861C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2004100989566A CN100334861C (en) 2004-12-17 2004-12-17 A method of Internet domain name access based on on-demand routing in self-organized network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2004100989566A CN100334861C (en) 2004-12-17 2004-12-17 A method of Internet domain name access based on on-demand routing in self-organized network

Publications (2)

Publication Number Publication Date
CN1633107A CN1633107A (en) 2005-06-29
CN100334861C true CN100334861C (en) 2007-08-29

Family

ID=34847984

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2004100989566A Active CN100334861C (en) 2004-12-17 2004-12-17 A method of Internet domain name access based on on-demand routing in self-organized network

Country Status (1)

Country Link
CN (1) CN100334861C (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674215B (en) * 2008-09-12 2012-01-11 中国移动通信集团公司 Method, node and system of network access
US8621086B2 (en) * 2010-03-24 2013-12-31 Alcatel Lucent System and domain name server for ad-hoc networks
CN109302436B (en) * 2017-07-25 2020-11-06 比亚迪股份有限公司 Train gateway forwarding strategy configuration method and device
CN113300867B (en) * 2020-06-29 2022-06-14 阿里巴巴集团控股有限公司 CDN system, information processing method and device, and CDN node

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004001519A2 (en) * 2002-06-24 2003-12-31 Nokia Corporation Mobile mesh ad-hoc networking
WO2004028111A1 (en) * 2002-09-20 2004-04-01 Cisco Technology, Inc. Method and apparatus in a gateway for registering mobile routers of a mobile ad hoc network to respective home agents

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004001519A2 (en) * 2002-06-24 2003-12-31 Nokia Corporation Mobile mesh ad-hoc networking
WO2004028111A1 (en) * 2002-09-20 2004-04-01 Cisco Technology, Inc. Method and apparatus in a gateway for registering mobile routers of a mobile ad hoc network to respective home agents

Also Published As

Publication number Publication date
CN1633107A (en) 2005-06-29

Similar Documents

Publication Publication Date Title
KR100789773B1 (en) A mesh networking auto configuration method, virtual link setting method, packet transmission method and terminal for its in multi hop wireless lan
US7894408B2 (en) System and method for distributing proxying error information in wireless networks
KR101183342B1 (en) Route selection in wireless networks
CN101091357B (en) Method for controlling routing operations in a network, related network and computer program product thereof
JP5503643B2 (en) Network interface unit for nodes in a wireless multihop network and method for establishing a network path between nodes in a wireless multihop network
US20090279520A1 (en) Scalable WLAN Gateway
KR100562903B1 (en) Method for Automatically Configuring Network Address in Mobile Multi-Hop Netwrok
US20080040507A1 (en) Methods and systems for a routing protocol
WO2002021769A2 (en) Transmission-scheduling coordination among collocated internet radios
US8462806B2 (en) Path selection procedure in mesh network and format of path request frame therefor
CN107528721B (en) Automatic networking and data forwarding method by using MAC address in Android mobile terminal
US20090232119A1 (en) Method of updating proxy information
WO2006106658A1 (en) Path control method and home agent
JP4114939B2 (en) Node connection method, network identifier assignment method, computer-readable medium, and network system
JP4993185B2 (en) Wireless communication system
CN100425029C (en) Internet access method based on demanded route in mobile self-organizing net
CN100334861C (en) A method of Internet domain name access based on on-demand routing in self-organized network
JP4696318B2 (en) Wireless device and wireless communication network provided with the same
CN1323528C (en) Automatic configuration method for internet domain server in self-organizing net
JP5311889B2 (en) COMMUNICATION SYSTEM, MOBILE COMMUNICATION DEVICE, HOME AGENT, AND COMMUNICATION METHOD
JP4913208B2 (en) Address resolution method
JP4735202B2 (en) Mobile terminal and program for selecting routing protocol for ad hoc network
WO2006043503A1 (en) Communication system for mobile body
JP4415094B2 (en) Roaming system, roaming method and mobile terminal
KR20050121038A (en) Method and apparatus for configuring routing path in a mobile ad hoc network

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: A method of Internet domain name access based on on-demand routing in self-organized network

Granted publication date: 20070829

License type: Exclusive License

Open date: 20050629

Record date: 20110823

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

EC01 Cancellation 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.

EM01 Change of recordation of patent licensing contract