CN1601989A - Automatic configuration method for internet domain server in self-organizing net - Google Patents
Automatic configuration method for internet domain server in self-organizing net Download PDFInfo
- Publication number
- CN1601989A CN1601989A CN 200410083798 CN200410083798A CN1601989A CN 1601989 A CN1601989 A CN 1601989A CN 200410083798 CN200410083798 CN 200410083798 CN 200410083798 A CN200410083798 A CN 200410083798A CN 1601989 A CN1601989 A CN 1601989A
- Authority
- CN
- China
- Prior art keywords
- gateway
- server
- domain name
- message
- name server
- 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
Links
Images
Abstract
The disclosed method and gateway configuration method of mobile auto-organization network (MANET) are combined together to share common configuration process so as to reduce network additional load, including steps as following: gateway announces own information of gateway and configuration information of domain name server to MANET node periodically; node S added into MANET broadcasts to network or gateway through unicast a message for requesting domain name server; if a node of receiving the message finds that self can respond the message directly, then the node sends domain name service message to S; otherwise, the requesting message is forwarded; after receiving requesting message, gateway sends domain name service information generated based on own configuration information through unicast to S; after receiving message of domain name service, S configures own gateway and domain name server based on information in the received message.
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 internet domain server configuration in the automatic configuring technical of MANET.
Background technology
Mobile ad-hoc network (MANET) 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.Document [1] Ramanathan R, Redi J, " A Brief Overview of mobile Ad hocNetworks:Challenges and Directions ", IEEE Communications Magazine, 50
ThAnniversary Commemorative Issue[C], 2002.In order to alleviate the loaded down with trivial details of MANET user's manual configuration, make the quickly networking of MANET, flexible easy-to-use characteristic obtain must in MANET, using various automatic configuring technicals from a minute embodiment, comprising: address configuration automatically, domain name mapping and service discovery.[2]Jaehoon?Jeong，Jungsoo?Park，“AutoconfigurationTechnologies?for?IPv6?Multicast?Service?in?Mobile?Ad-hoc?Networks”，TheInternational?Conference?on?Information?Networking，2002。And the automatic configuration of internet domain server just belongs to a part of domain name mapping.
Summary of the invention
The object of the present invention is to provide the implementation method that disposes internet domain server in a kind of mobile ad-hoc network automatically.
Internet domain server is a node among the Internet, and it can provide the domain name mapping service for other node in the network.MANET (Mobile Ad Hoc Networks) 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, and 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.
The configuration internet domain server is exactly to find a server that the Internet domain name mapping can be provided in network in MANET, and this server is configured to the domain name resolution server of oneself.
The present invention has defined two kinds of message using in the name server layoutprocedure: name server request message and domain name service message.Message format is as follows:
The name server request message format
G replys sign: 0 expression intermediate node can be replied this request message;
1 expression can only be replied by gateway
The Reserved reserved field is changed to complete 0
The P protocol-identifier: 0 expression source IP address is the IPv4 address;
1 expression source IP address is the IPv6 address
Original IP Address sends the node IP address, source of this request: P is 0 o'clock, is 32
IPv4 address, position;
P is 1 o'clock, is 128 IPv6 addresses
The domain name service message format
Type 1
N gateway name server sign
0 expression gateway can not provide domain name service, and name server is by Nameserver
IP Address field provides; 1 expression gateway is exactly a name server, its
The address is provided by Gateway IP Address field, at this moment, does not have
Nameserver IP Address field
E type of error sign: 0 expression inerrancy; 1 expression " no name server "
The Reserved reserved field is changed to complete 0
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 life cycle of Lifetime gateway, one 16 integer
The IP address of Gateway IP Address gateway; N is 1 o'clock, represents name server simultaneously
The address
The IP address of Nameserver IP Address name server
The realization of internet domain server collocation method 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 broadcasting domain name service message, and 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:
Gateway is the node broadcasts domain name service information in MANET periodically, and the domain name service information-bearing is in DN_SERVER message.Gateway domain name service information broadcast idiographic flow as shown in Figure 1.
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 as shown in Figure 2.
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 DN_SERVER 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 as early as possible and reply.Gateway domain name service responding process as shown in Figure 4.
Domain name service message is arrival source node through intermediate node handles with after transmitting.After the source node is received this message, the first-selected name server that wherein name server is configured to oneself (for example, in linux operating system, the IP address of this name server can be added among file/etc/resolv.conf) start gateway timer life cycle T3 then, the clocking value of T3 is the Lifetime value in the domain name service message, overtime as T3, 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 and name server layoutprocedure are combined, transmission that can shared control messages message reduces the Internet resources that these messages of transmission are separately wasted, and makes 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) method of using the present invention to propose can be MANET node configuration gateway and name server apace, reduces the loaded down with trivial details of user's manual configuration, makes the user can visit Internet in time, easily.
The present invention has been used in the design of IPv6 MANET test envelope system of the Computer Department of the Chinese Academy of Science.
The invention technical scheme
Internet domain server method of automatic configuration in the mobile ad hoc network: name server configuration and gateway configuration are combined; Gateway periodically to MANET broadcasting domain name service message, is declared oneself gateway configuration and name server configuration information; The 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, allows intermediate node to reply if find this message, and gateway and name server configuration messages are arranged oneself, just sends domain name service message to the 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 node S; After requesting node S receives domain name service message, according to the gateway and the name server of wherein gateway information and domain name server information configuration oneself.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 a gateway domain name service information broadcast flow chart.
Fig. 2 is name server configuration flow figure.
Fig. 3 is an intermediate node Message Processing flow chart.
Fig. 4 is gateway domain name service responding process figure.
Embodiment
The method of automatic configuration of internet domain server in the MANET, gateway domain name service information broadcast handling process wherein is as follows:
Step S1: if gateway provides domain name service, perhaps gateway configuration has name server, and gateway address or first-selected domain name server address are kept among the name server record variable DN_SERVER, enters S2; Otherwise, put DN_SERVER for empty, wait for;
Step S2: start timer T1, periodically broadcast the name server configuration information, DN_SERVER is carried in the domain name service message;
Step S3:, new address is stored among the DN_SERVER, and periodically broadcasts new name server configuration information if node is found oneself IP address or first-selected name server IP address modification.
The treatment step of each incident is as follows among Fig. 1: (gateway domain name service information broadcast flow process)
S1.1: when gateways and starting configuration service module, judge whether oneself is name server, promptly oneself whether has moved domain name service program (as BIND) and provides the domain name mapping service for other network node,, enter S1.2 if gateway is a name server; Otherwise, forward S1.3 to;
S1.2: the IP address of gateway is kept among the name server record variable DN_SERVER, enters S1.6.
S1.3: judge 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),, forward S1.5 to if the name server configuration is arranged; Otherwise, enter S1.4;
S1.4: put DN_SERVER for empty, promptly do not have name server;
S1.5: put the IP address that DN_SERVER is the first-selected name server that gateway disposed (for example, in linux operating system, putting DN_SERVER is the IP address of article one nameserver record among file/etc/resolv.conf), enter S1.6;
S1.6: start timer T1, be used for periodically broadcasting the domain name service message, the time cycle of T1 is NS_BROADCAST_TIMEOUT (its value is according to the MANET network environment and the scale decision of reality), after T1 is overtime, restart timing next time immediately, timer T1 enters S1.7 after starting;
S1.7: DN_SERVER inserted in the domain name service message broadcast away, if gateway is exactly a name server, N is put 1, otherwise N is put 0; E position 0; P decides according to the employed IP protocol type of gateway; Lifetime is the life cycle of gateway, reads from the gateway configuration file; GatewayIP Address is the IP address of gateway, and N is 1 o'clock, is the IP address that DN_SERVER preserved; When N was 0, Nameserver IP Address was the IP address among the DN_SERVER.Enter S1.8;
S1.8: check whether IP address of oneself or first-selected name server IP address change,, enter S1.9 if change; If do not change, forward S1.10 to;
S1.9: putting DN_SERVER is new domain name server address, forwards S1.6 to;
S1.10: judge whether T1 is overtime,, enter S1.8 if not overtime; If T1 is overtime by the time, enter S1.7, periodically broadcast the domain name service message.
The method of automatic configuration of internet domain server in the MANET, name server configuration flow wherein is as follows:
Step S1: check in the routing table whether gateway information is arranged,, send the name server request message,, send the name server request message to Web broadcast if do not have to the gateway clean culture if gateway information is arranged;
Step S2: start domain name service Messages-Waiting timer T2, if before T2 is not overtime, received domain name service message, forward step S5 to, if T2 is overtime, do not receive domain name service message, just send the name server request message once more, and restart timer T2, wait for the arrival of domain name service message;
Step S3: if T2 overtime once more before, do not receive domain name service message yet, judge whether the name server request message sent is broadcasting, if broadcasting sends " no name server " indication to the user, finish; If clean culture to Web broadcast name server request message, and is restarted T2, if before T2 is overtime, received domain name service message, forward step S5 to;
Step S4: if T2 is overtime for the third time, just broadcast domain name server requests message once more, if T2 for the third time or the 4th time overtime before, all do not receive domain name service message, send " no name server " indication to the user, finish; Otherwise, enter step S5;
Step S5: after receiving domain name service message,, finish according to the gateway and the name server of wherein information configuration oneself.
The treatment step of each incident is as follows among Fig. 2: (name server configuration flow)
S2.1: when the name server configuration module starts, at first search routing table, check in the routing table whether gateway information is arranged, judge promptly whether the IP address that is designated gateway is arranged in the routing table,, forward S2.3 to if having; If do not have gateway information in the routing table, enter S2.2;
S2.2: the initial value of putting request counter Counter is 2, and broadcasting domain name server requests message forwards S2.5 then to; In the name server request message, decide according to network condition and acknowledgment strategy the G position; Decide according to the employed IP protocol type of node the P position; Original IP Address is the IP address (as the MANET home address) of node oneself;
S2.3: the initial value of putting request counter Counter is 0, enters S2.4;
S2.4: send the name server request message to the gateway clean culture, the gateway ip address of the destination address of IP head in routing table, finding.Enter S2.5;
S2.5: the value of 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 S2.6;
S2.6: 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 S2.10 to; If T2 is overtime, enter S2.7;
S2.7: whether the value of judging request counter Counter less than 2, if than 2 little, forward S2.4 to, once more clean culture name server request message; If the value of Counter is not less than 2, enter S2.8;
S2.8: whether the value of judging request counter Counter greater than 3, if than 3 big, enter S2.9; Otherwise, forward S2.2 to, broadcast domain name server requests message once more;
S2.9: based on following reason, system thinks do not have name server in this MANET network, just returns one " no name server " indication to the user; Reason: when in routing table, gateway information being arranged,, and do not receive the domain name service acknowledgement messaging to twice of gateway clean culture with to twice name server request message of Web broadcast; 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;
S2.10: when receiving the domain name service message of having carried DN_SERVER, judge at first whether oneself has disposed gateway,, enter S2.11 if gateway information is arranged; Otherwise, forward S2.12 to;
S2.11: judge whether the gateway address in the domain name service message is identical with the gateway address of own previous configuration, if identical, forwards S2.13 to; If different, enter S2.12;
S2.12: the gateway information in the domain name service message is configured to own current gateway, forwards S2.14 to;
S2.13: because new gateway is identical with former gateway, needn't change gateway configuration, directly enter S2.14;
S2.14: the first-selected name server that the domain name server address in the domain name service message is configured to oneself.
The method of automatic configuration of internet domain server in the MANET, intermediate node Message Processing flow process wherein is as follows:
Step S1: judge 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: transmit domain name service message to requesting node; Check the route that whether has in the routing table to gateway, if just do not set up a route to gateway; Finish;
Step S3: judge that the name server request message of receiving is that clean culture sends or broadcast transmission, if clean culture sends, forwards step S5 to; If broadcast transmission enters step S4;
Step S4: check the route that whether has in the routing table to requesting node,, set up a route to requesting node if do not have; Enter step S5;
Step S5: check whether this request message allows intermediate node to reply,, request message is forwarded, finish if do not allow; If allow, enter step S6;
Step S6: check whether gateway information and name server configuration information oneself are arranged,, request message is forwarded,, send domain name service message to requesting node if having if do not have; Finish.
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 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: IP source address changed into oneself IP address, transmit this domain name service message to destination node then, enter S3.3;
S3.3: check the route that oneself whether has to gateway,, enter S3.4 if do not have; Otherwise, forward S3.5 to;
S3.4: the route that is established to gateway: next hop address is the IP address of the neighbor node of this message of transmission, i.e. source IP address in the IP head; Route is the Lifetime in the domain name service message life cycle;
S3.5: because existing route to current gateway is not done any operation;
S3.6: judge whether this name server request message sends by clean culture, if forward S3.9 to; If, enter S3.7 by broadcast transmission;
S3.7: check the route that whether has to the node of this request of transmission,, forward S3.9 to if having; Otherwise, enter S3.8;
S3.8: owing to do not arrive the route of requesting node, set up a route, be used to transmit the domain name service acknowledgement messaging, enter S3.9 to requesting node;
S3.9: judge whether the G position in the name server request message is put 1, if, show and can only reply this message by gateway, forward S3.11 to; If the G position is 0, show that intermediate node can reply this message, enter S3.10;
S3.10: check that whether node oneself has gateway configuration and name server configuration, if having, forwards S3.12 to; If do not have, enter S3.11;
S3.11: the name server request message of receiving is forwarded.IP source address is changed the IP leading address into node oneself, and the IP head's address is constant;
S3.12: the name server request message is replied, and structure domain name service message message sends to requesting node with this message unicast then.
The method of automatic configuration of internet domain server in the MANET, gateway domain name service responding process wherein is as follows:
Step S1: check whether timer T1 will be soon overtime, if, wait for that T1 is overtime, send the domain name service information broadcast, finish; Otherwise, enter step S2;
Step S2: check whether name server record variable DN_SERVER is empty, if be not empty, sends domain name service message to the requesting node clean culture, if empty, sends " no name server " message to the requesting node clean culture; Finish.
The treatment step of each incident is as follows among Fig. 4: (gateway domain name service responding process)
S4.1: when gateway is received the name server request message, whether first-selected inspection timer T1 will be soon overtime, and whether the residue timeout value of promptly checking T1 is less than certain threshold value Delay_Reply_Time, and its value is decided according to network application environment, if T1 will be soon overtime, forward S4.5 to; Otherwise, enter S4.2;
S4.2: check the DN_SERVER variate-value of oneself,, enter S4.3 if be not empty; Otherwise, forward S4.4 to;
S4.3: send domain name service message to the requesting node clean culture, its form is identical with form in the domain name service information broadcast;
S4.4: send " no name server " message to requesting node, the N position of promptly putting in the domain name service message is 0, and the E position is 1, and Nameserver IP Address is empty;
S4.5: wait for that T1 is overtime, send the domain name service information broadcast.
Claims (9)
1. the method for automatic configuration of internet domain server in the mobile ad-hoc network is characterized in that, name server configuration and gateway configuration are combined; Gateway periodically to MANET broadcasting domain name service message, is declared oneself gateway configuration and name server configuration information; The 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, allows intermediate node to reply if find this message, and gateway and name server configuration messages are arranged oneself, just sends domain name service message to the 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 node S; After requesting node S receives domain name service message, according to the gateway and the name server of wherein gateway information and domain name server information configuration oneself.
2. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 1, gateway domain name service information broadcast handling process wherein is as follows:
Step S1: if gateway provides domain name service, perhaps gateway configuration has name server, and gateway address or first-selected domain name server address are kept among the name server record variable DN_SERVER, enters S2; Otherwise, put DN_SERVER for empty, wait for;
Step S2: start timer T1, periodically broadcast the name server configuration information, DN_SERVER is carried in the domain name service message;
Step S3:, new address is stored among the DN_SERVER, and periodically broadcasts new name server configuration information if node is found oneself IP address or first-selected name server IP address modification.
3. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 2, it is characterized in that gateway domain name service information broadcast handling process concrete steps are as follows:
S1.1: when gateways and starting configuration service module, judge 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,, enter S1.2 if gateway is a name server; Otherwise, forward S1.3 to;
S1.2: the IP address of gateway is kept among the name server record variable DN_SERVER, enters S1.6;
S1.3: judge whether oneself disposes name server,, forward S1.5 to if the name server configuration is arranged; Otherwise, enter S1.4;
S1.4: put DN_SERVER for empty, promptly do not have name server;
S1.5: put the IP address that DN_SERVER is the first-selected name server that gateway disposed, enter S1.6;
S1.6: start timer T1, be used for periodically broadcasting the domain name service message, the time cycle of T1 is NS_BROADCAST_TIMEOUT, after T1 is overtime, restarts timing next time immediately, and timer T1 enters S1.7 after starting;
S1.7: DN_SERVER inserted in the domain name service message broadcast away, if gateway is exactly a name server, N is put 1, otherwise N is put 0; E position 0; P decides according to the employed IP protocol type of gateway; Lifetime is the life cycle of gateway, reads from the gateway configuration file; GatewayIP Address is the IP address of gateway, and N is 1 o'clock, is the IP address that DN_SERVER preserved; When N was 0, Nameserver IP Address was the IP address among the DN_SERVER.Enter S1.8;
S1.8: check whether IP address of oneself or first-selected name server IP address change,, enter S1.9 if change; If do not change, forward S1.10 to;
S1.9: putting DN_SERVER is new domain name server address, forwards S1.6 to;
S1.10: judge whether T1 is overtime,, enter S1.8 if not overtime; If T1 is overtime by the time, enter S1.7, periodically broadcast the domain name service message.
4. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 1, name server configuration flow wherein is as follows:
Step S1: check in the routing table whether gateway information is arranged,, send the name server request message,, send the name server request message to Web broadcast if do not have to the gateway clean culture if gateway information is arranged;
Step S2: start domain name service Messages-Waiting timer T2, if before T2 is not overtime, received domain name service message, forward step S5 to, if T2 is overtime, do not receive domain name service message, just send the name server request message once more, and restart timer T2, wait for the arrival of domain name service message;
Step S3: if T2 overtime once more before, do not receive domain name service message yet, judge whether the name server request message that is sent is broadcasting, if broadcasting sends " no name server " indication to the user, finish: if clean culture, to Web broadcast name server request message, and restart T2, if before T2 is overtime, receive domain name service message, forwarded step S5 to;
Step S4: if T2 is overtime for the third time, just broadcast domain name server requests message once more, if T2 for the third time or the 4th time overtime before, all do not receive domain name service message, send " no name server " indication to the user, finish; Otherwise, enter step S5;
Step S5: after receiving domain name service message,, finish according to the gateway and the name server of wherein information configuration oneself.
5. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 4, it is characterized in that name server configuration flow concrete steps are as follows:
S2.1: when the name server configuration module starts, at first search routing table, check in the routing table whether gateway information is arranged, judge promptly whether the IP address that is designated gateway is arranged in the routing table,, forward S2.3 to if having; If do not have gateway information in the routing table, enter S2.2;
S2.2: the initial value of putting request counter Counter is 2, and broadcasting domain name server requests message forwards S2.5 then to; In the name server request message, decide according to network condition and acknowledgment strategy the G position; Decide according to the employed IP protocol type of node the P position; Original IP Address is the IP address of node oneself;
S2.3: the initial value of putting request counter Counter is 0, enters S2.4;
S2.4: send the name server request message to the gateway clean culture, the gateway ip address of the destination address of IP head in routing table, finding.Enter S2.5;
S2.5: the value of 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 S2.6;
S2.6: 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 S2.10 to; If T2 is overtime, enter S2.7;
S2.7: whether the value of judging request counter Counter less than 2, if than 2 little, forward S2.4 to, once more clean culture name server request message; If the value of Counter is not less than 2, enter S2.8;
S2.8: whether the value of judging request counter Counter greater than 3, if than 3 big, enter S2.9; Otherwise, forward S2.2 to, broadcast domain name server requests message once more;
S2.9: 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;
S2.10: when receiving the domain name service message of having carried DN_SERVER, judge at first whether oneself has disposed gateway,, enter S2.11 if gateway information is arranged; Otherwise, forward S2.12 to;
S2.11: judge whether the gateway address in the domain name service message is identical with the gateway address of own previous configuration, if identical, forwards S2.13 to; If different, enter S2.12;
S2.12: the gateway information in the domain name service message is configured to own current gateway.Forward S2.14 to;
S2.13: because new gateway is identical with former gateway, needn't change gateway configuration, directly enter S2.14;
S2.14: the first-selected name server that the domain name server address in the domain name service message is configured to oneself.
6. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 1, intermediate node Message Processing flow process wherein is as follows:
Step S1: judge 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: transmit domain name service message to requesting node; Check the route that whether has in the routing table to gateway, if just do not set up a route to gateway; Finish;
Step S3: judge that the name server request message of receiving is that clean culture sends or broadcast transmission, if clean culture sends, forwards step S5 to; If broadcast transmission enters step S4;
Step S4: check the route that whether has in the routing table to requesting node,, set up a route to requesting node if do not have; Enter step S5;
Step S5: check whether this request message allows intermediate node to reply,, request message is forwarded, finish if do not allow; If allow, enter step S6;
Step S6: check whether gateway information and name server configuration information oneself are arranged,, request message is forwarded,, send domain name service message to requesting node if having if do not have; Finish.
7. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 6, it is characterized in that intermediate node Message Processing flow process concrete steps are as follows:
S3.1: receive the name server configuration messages when the MANET 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: IP source address changed into oneself IP address, transmit this domain name service message to destination node then, enter S3.3;
S3.3: check the route that oneself whether has to gateway,, enter S3.4 if do not have; Otherwise, forward S3.5 to;
S3.4: the route that is established to gateway: next hop address is the IP address of the neighbor node of this message of transmission, i.e. source IP address in the IP head; Route is the Lifetime in the domain name service message life cycle;
S3.5: because existing route to current gateway is not done any operation;
S3.6: judge whether this name server request message sends by clean culture, if forward S3.9 to; If, enter S3.7 by broadcast transmission;
S3.7: check the route that whether has to the node of this request of transmission,, forward S3.9 to if having; Otherwise, enter S3.8;
S3.8: owing to do not arrive the route of requesting node, set up a route, be used to transmit the domain name service acknowledgement messaging, enter S3.9 to requesting node;
S3.9: judge whether the G position in the name server request message is put 1, if, show and can only reply this message by gateway, forward S3.11 to; If the G position is 0, show that intermediate node can reply this message, enter S3.10;
S3.10: check that whether node oneself has gateway configuration and name server configuration, if having, forwards S3.12 to; If do not have, enter S3.11;
S3.11: the name server request message of receiving is forwarded, and IP source address is changed the IP leading address into node oneself, and the IP head's address is constant;
S3.12: the name server request message is replied, and structure domain name service message message sends to requesting node with this message unicast then.
8. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 1, gateway domain name service responding process wherein is as follows:
Step S1: check whether timer T1 will be soon overtime, if, wait for that T1 is overtime, send the domain name service information broadcast, finish; Otherwise, enter step S;
Step S2: check whether name server record variable DN_SERVER is empty, if be not empty, sends domain name service message to the requesting node clean culture, if empty, sends " no name server " message to the requesting node clean culture; Finish.
9. according to the internet domain server method of automatic configuration in the mobile ad hoc network of claim 6, it is characterized in that gateway domain name service responding process concrete steps are as follows:
S4.1: when gateway is received the name server request message, whether first-selected inspection timer T1 will be soon overtime, and whether the residue timeout value of promptly checking T1 is less than certain threshold value Delay_Reply_Time, and its value is decided according to network application environment, if T1 will be soon overtime, forward S4.5 to; Otherwise, enter S4.2;
S4.2: check the DN_SERVER variate-value of oneself,, enter S4.3 if be not empty; Otherwise, forward S4.4 to;
S4.3: send domain name service message to the requesting node clean culture, its form is identical with form in the domain name service information broadcast;
S4.4: send " no name server " message to requesting node, the N position of promptly putting in the domain name service message is 0, and the E position is 1, and Nameserver IP Address is empty;
S4.5: wait for that T1 is overtime, send the domain name service information broadcast.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100837987A CN1323528C (en) | 2004-10-22 | 2004-10-22 | Automatic configuration method for internet domain server in self-organizing net |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100837987A CN1323528C (en) | 2004-10-22 | 2004-10-22 | Automatic configuration method for internet domain server in self-organizing net |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1601989A true CN1601989A (en) | 2005-03-30 |
| CN1323528C CN1323528C (en) | 2007-06-27 |
Family
ID=34667014
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100837987A Active CN1323528C (en) | 2004-10-22 | 2004-10-22 | Automatic configuration method for internet domain server in self-organizing net |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1323528C (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101400105B (en) * | 2007-09-25 | 2013-04-10 | 株式会社Ntt都科摩 | Adaptive gateway discovery method and gateway |
| CN105959428A (en) * | 2016-04-28 | 2016-09-21 | 武汉斗鱼网络科技有限公司 | Domain name resolution method and device based on Linux system |
| CN109274759A (en) * | 2018-10-19 | 2019-01-25 | 杭州和利时自动化有限公司 | Communication means and device between a kind of Distributed Control System and its node |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7209959B1 (en) * | 2000-04-04 | 2007-04-24 | Wk Networks, Inc. | Apparatus, system, and method for communicating to a network through a virtual domain providing anonymity to a client communicating on the network |
| EP1241859A1 (en) * | 2001-03-14 | 2002-09-18 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Method and system for obtaining domain name and IP-address resolution |
| CN1431802A (en) * | 2003-01-24 | 2003-07-23 | 东南大学 | Household information networks and gateways based on self-organization network structure and blue teeth technology |
-
2004
- 2004-10-22 CN CNB2004100837987A patent/CN1323528C/en active Active
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101400105B (en) * | 2007-09-25 | 2013-04-10 | 株式会社Ntt都科摩 | Adaptive gateway discovery method and gateway |
| CN105959428A (en) * | 2016-04-28 | 2016-09-21 | 武汉斗鱼网络科技有限公司 | Domain name resolution method and device based on Linux system |
| CN109274759A (en) * | 2018-10-19 | 2019-01-25 | 杭州和利时自动化有限公司 | Communication means and device between a kind of Distributed Control System and its node |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1323528C (en) | 2007-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1801764A (en) | Internet access method based on identity and location separation | |
| CN1697456A (en) | Communication method and device in mobile state having multi-interfaces | |
| CN1607783A (en) | Processing broadcast data in a mobile ac-hoc network | |
| CN1866863A (en) | Vicinage finding method and system for network apparatus | |
| CN1700668A (en) | Process for generating and updating a hierarchical tree in a manet multicast routing protocol ad hoc network | |
| CN1802013A (en) | Method and apparatus for realizing network service provider discovery | |
| CN101068203A (en) | Cluster self-organizing routing method and device | |
| CN1571326A (en) | Apparatus and method for retransmitting data packets in mobile ad hoc network environment | |
| CN1881935A (en) | Mobile Internet protocol route processing method and system and router | |
| CN1700647A (en) | Information processing apparatus and method for wireless network | |
| CN1852256A (en) | Method and system for data transmission in wireless net-like network | |
| CN1288881C (en) | Address automatic distributing method in mobile self organizing network | |
| CN1297111C (en) | Network connection apparatus, connection system, and networkconnection method | |
| CN1192576C (en) | Multicast business realizing method in mobile network | |
| CN1181655C (en) | Data packet transmission method in mobile IP | |
| CN1738269A (en) | Method to allocate protocol relay address table and server address pool for synchronization dynamic host machine | |
| CN1112014C (en) | Wireless network roaming method of cross IP domain | |
| CN1564540A (en) | Internet access method based on demanded route in mobile self-organizing net | |
| CN1601989A (en) | Automatic configuration method for internet domain server in self-organizing net | |
| CN101047637A (en) | Method for requiring local mobile anchor point information by access route and its application | |
| CN101043425A (en) | Method for establishing single topology adjacent relation from intermediate system to intermediate system routing protocol | |
| CN1870819A (en) | Method of route optimization for implementing IPv6 communication buddy supporting mobile IPv6 | |
| CN1314239C (en) | Method of carrying out field name system in moble self-organizing network | |
| CN1874301A (en) | Method and system for quick responding IP banding message | |
| CN101035087A (en) | Message forwarding method, system and device |
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 |