CN1633107A - 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 PDFInfo
- Publication number
- CN1633107A CN1633107A CN200410098956.6A CN200410098956A CN1633107A CN 1633107 A CN1633107 A CN 1633107A CN 200410098956 A CN200410098956 A CN 200410098956A CN 1633107 A CN1633107 A CN 1633107A
- Authority
- CN
- China
- Prior art keywords
- name server
- domain name
- gateway
- message
- node
- 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
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
This invention relates to an Internet domain name access method based on required routes in a mobile self-organization network, which utilizes the RREQ and RREP message loading domain name server required information and service information to combine the set up of route, gateway configuration and Internet domain name server to carry out the following steps: the node S joining in MANET broadcast name server required information, if the node receiving the information finds that it can answer it directly, then it sends the service information to S, or it asks to forward the information, after the gateway receives it, it generates domain name service information to be cast to S, S refreshes the route list, arranges its own gate and the server.
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 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, 50thAnniversary 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, " Ad hoc On-Demand Distance Vector (AODV) Routing ", RFC3561, July2003; 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) Routing forIP 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.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, " 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 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???????????7?8????????13??14???????????????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?Sequence?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?????????7?8????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 RREP
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 is arrival source node through intermediate node handles with after transmitting.After the 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.
The invention technical scheme
In the mobile ad hoc network based on the method for Internet domain name access of route as required: it is characterized in that name server configuration, gateway configuration and route set up and combine; 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, 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 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; Intermediate node and S receive 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 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: check in the routing table whether gateway information is arranged,, send nearly twice name server request message,, send nearly twice name server request message to Web broadcast if do not have to the gateway clean culture if gateway information is arranged;
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 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 S1.4 to if having; If do not have gateway information in the routing table, enter S1.2;
S1.2: the initial value of putting request counter Counter is 2, enters S1.3;
S1.3: 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 of putting request counter Counter is 0, enters S1.5;
S1.5: send 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 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 the value of judging 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 the value of judging 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 receiving 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: upgrade gateway configuration, soon the Destination IP Address in the domain name service message is set to the gateway of oneself, enters S1.13;
S1.13: whether do not have internet domain server in the network, check promptly whether the E position in the domain name service message is 1, if enter S1.14; Otherwise, forward S1.15 to;
S1.14: the configuration internet domain server is empty, forwards S1.10 to;
S1.15: the first-selected name server that the Name Server IP Address in the domain name service message is configured to 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: check oneself whether to be name server or to dispose name server, if, enter step S2, otherwise, forward step S3 to;
Step S2: send domain name service message to requesting node;
Step S3: send " 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: oneself IP address is placed the Name Server IP Address field of domain name service message, forward S2.5 to;
S2.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),, enter S2.4 if the name server configuration is arranged, otherwise, forward S2.6 to;
S2.4: the at first name server IP address that oneself is disposed places the Name Server IP Address field of domain name service message, enters S2.5;
S2.5: send 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 judge the broadcast interval time greater than threshold value Broadcast_Time_Interval (a predefined value is decided according to the real network situation), 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: write down this airtime, broadcast transmission " no name server " is replied, and promptly sends the domain name service message of E position 1 to requesting node;
S2.8: 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: 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, upgrade routing table, gateway configuration and name server configuration;
Step S3: upgrade routing table, check 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 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: transmit domain name service message to requesting node, enter S3.3;
S3.3: upgrade gateway configuration, the Destination IP Address in the domain name service message is set to the gateway of oneself, enters S3.4;
S3.4: according to the regulation of AODV, upgrade routing table, be updated to the route of gateway, enter S3.5;
S3.5: upgrade the name server configuration, the Name Server IPAddress in the domain name service message is configured to the at first name server of oneself;
S3.6: upgrade routing table, be updated to the route of requesting node, enter S3.7;
S3.7: judge 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: the name server request message is forwarded;
S3.9: search routing table, whether have the route R of gateway,, forward S3.11 to if find route R; Otherwise, enter S3.10;
S3.10: the broadcasting of name server request message is forwarded;
S3.11: relatively whether the Reply Sequence Number among the R is less than the Reply Sequence Number in the request message, if forward S3.13 to; Otherwise, enter S3.12;
S3.12: judge whether oneself disposes internet domain server, if forward S3.14 to; Otherwise, enter S3.13;
S3.13: the clean culture of name server request message is transmitted to gateway;
S3.14: send 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, and Name Server IP Address is the domain name server address that node oneself is disposed, and all the other fields are consistent with the regulation of AODV.
Claims (7)
- In the mobile ad-hoc network based on the method for Internet domain name access of route as required, it is characterized in that revising RREQ in the AODV Routing Protocol and RREP message respectively as name server request message and domain name service message, shared routing table is set up, gateway configuration and name server layoutprocedure, when node S adds MANET, start the name server layoutprocedure, send the name server request message, intermediate node handles, reply or transmit this request message, after gateway is received this message, sending domain name service message to S replys, S disposes oneself gateway and name server according to gateway and domain name server information wherein, and upgrades routing table.
- According in the mobile ad hoc network of claim 1 based on the method for Internet domain name access of route as required, name server configuration flow wherein is as follows:Step S1: check in the routing table whether gateway information is arranged,, send nearly twice name server request message,, send nearly twice name server request message to Web broadcast if do not have to the gateway clean culture if gateway information is arranged;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.
- According in the mobile ad hoc network of claim 2 based on the method for Internet domain name access of route as required, it is characterized in that name server configuration flow concrete steps are as follows:S1.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 S1.4 to if having; If do not have gateway information in the routing table, enter S1.2;S1.2: the initial value of putting request counter Counter is 2, enters S1.3;S1.3: 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 of putting request counter Counter is 0, enters S1.5;S1.5: send 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 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 the value of judging 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 the value of judging 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 receiving 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: upgrade gateway configuration, soon the Destination IP Address in the domain name service message is set to the gateway of oneself, enters S1.13;S1.13: whether do not have internet domain server in the network, check promptly whether the E position in the domain name service message is 1, if enter S1.14; Otherwise, forward S1.15 to;S1.14: the configuration internet domain server is empty, forwards S1.10 to;S1.15: the first-selected name server that the Name Server IP Address in the domain name service message is configured to oneself.
- 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 as follows that flow process is replied in gateway domain name service wherein:Step S1: check oneself whether to be name server or to dispose name server, if, enter step S2, otherwise, forward step S3 to;Step S2: send domain name service message to requesting node;Step S3: send " no name server " message to requesting node or MANET network.
- According in the mobile ad hoc network of claim 4 based on the method for Internet domain name access of route as required, it is characterized in that it is as follows that the flow process concrete steps are replied in the gateway domain name service: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: oneself IP address is placed the Name Server IP Address field of domain name service message, forward S2.5 to;S2.3: judge whether oneself disposes name server,, enter S2.4 if the name server configuration is arranged, otherwise, forward S2.6 to;S2.4: the at first name server IP address that oneself is disposed places the Name Server IP Address field of domain name service message, enters S2.5;S2.5: send 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 judge the broadcast interval time greater than threshold value Broadcast_Time_Interval, 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: write down this airtime, broadcast transmission " no name server " is replied, and promptly sends the domain name service message of E position 1 to requesting node;S2.8: clean culture sends " no name server " and replys, and promptly sends the domain name service message of E position 1 to requesting node.
- According in the mobile ad hoc network of claim 1 based on the method for Internet domain name access of route as required, 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, upgrade routing table, gateway configuration and name server configuration;Step S3: upgrade routing table, check 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.
- According in the mobile ad hoc network of claim 5 based on the method for Internet domain name access of route as required, 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: transmit domain name service message to requesting node, enter S3.3;S3.3: upgrade gateway configuration, the Destination IP Address in the domain name service message is set to the gateway of oneself, enters S3.4;S3.4: according to the regulation of AODV, upgrade routing table, be updated to the route of gateway, enter S3.5;S3.5: upgrade the name server configuration, the Name Server IPAddress in the domain name service message is configured to the at first name server of oneself;S3.6: upgrade routing table, be updated to the route of requesting node, enter S3.7;S3.7: judge 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: the name server request message is forwarded;S3.9: search routing table, whether have the route R of gateway,, forward S3.11 to if find route R; Otherwise, enter S3.10;S3.10: the broadcasting of name server request message is forwarded;S3.11: relatively whether the Reply Sequence Number among the R is less than the Reply Sequence Number in the request message, if forward S3.13 to; Otherwise, enter S3.12;S3.12: judge whether oneself disposes internet domain server, if forward S3.14 to; Otherwise, enter S3.13;S3.13: the clean culture of name server request message is transmitted to gateway;S3.14: send 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, and Name Server IP Address is the domain name server address that node oneself is disposed, and all the other fields are consistent with the regulation of AODV.
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 true CN1633107A (en) | 2005-06-29 |
| CN100334861C 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) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101674215B (en) * | 2008-09-12 | 2012-01-11 | 中国移动通信集团公司 | Method, node and system of network access |
| CN102823220A (en) * | 2010-03-24 | 2012-12-12 | 阿尔卡特朗讯公司 | System and domain name server for AD-HOC networks |
| CN109302436A (en) * | 2017-07-25 | 2019-02-01 | 比亚迪股份有限公司 | Train gateway forwards tactics configuring method and device |
| CN113300867A (en) * | 2020-06-29 | 2021-08-24 | 阿里巴巴集团控股有限公司 | CDN system, information processing method and device, and CDN node |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6879574B2 (en) * | 2002-06-24 | 2005-04-12 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
| US6850532B2 (en) * | 2002-09-20 | 2005-02-01 | Cisco Technology, Inc. | Arrangement in a gateway for registering mobile routers of a mobile ad hoc network to respective home agents |
-
2004
- 2004-12-17 CN CNB2004100989566A patent/CN100334861C/en active Active
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101674215B (en) * | 2008-09-12 | 2012-01-11 | 中国移动通信集团公司 | Method, node and system of network access |
| CN102823220A (en) * | 2010-03-24 | 2012-12-12 | 阿尔卡特朗讯公司 | System and domain name server for AD-HOC networks |
| CN109302436A (en) * | 2017-07-25 | 2019-02-01 | 比亚迪股份有限公司 | Train gateway forwards tactics configuring method and device |
| CN113300867A (en) * | 2020-06-29 | 2021-08-24 | 阿里巴巴集团控股有限公司 | CDN system, information processing method and device, and CDN node |
| CN113300867B (en) * | 2020-06-29 | 2022-06-14 | 阿里巴巴集团控股有限公司 | CDN system, information processing method and device, and CDN node |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100334861C (en) | 2007-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1926820A (en) | Method, communication device and system for checking neighbor node using NDP in wireless multi-hop network | |
| WO2017101575A1 (en) | Wireless ad hoc network routing method and device | |
| CN1700668A (en) | Process for generating and updating a hierarchical tree in a manet multicast routing protocol ad hoc network | |
| CN1607783A (en) | Processing broadcast data in a mobile ac-hoc network | |
| CN1719802A (en) | Method and apparatus for controlling mobile network | |
| CN1801764A (en) | Internet access method based on identity and location separation | |
| CN1726679A (en) | Arrangement in a router of a mobile network for optimizing use of messages carrying reverse routing headers | |
| CN1628437A (en) | System and method for communicating between coordinated multipoint wireless networks | |
| CN1453963A (en) | Method of bluetooth routing according to request and network formation and communication method of bluetooth group network | |
| CN1435027A (en) | Mobile IP for mobile hoc networks | |
| CN107528721B (en) | Automatic networking and data forwarding method by using MAC address in Android mobile terminal | |
| CN1700647A (en) | Information processing apparatus and method for wireless network | |
| US20110019686A1 (en) | Path selection procedure in mesh network and format of path request frame therefor | |
| CN1288881C (en) | Address automatic distributing method in mobile self organizing network | |
| CN1778071A (en) | Method and base station for the transmission of information in a cellular radio communication system extended by means of ad-hoc connections | |
| CN1852256A (en) | Method and system for data transmission in wireless net-like network | |
| CN101047673A (en) | Method and system for acquiring terminal address correlation information | |
| CN1564540A (en) | Internet access method based on demanded route in mobile self-organizing net | |
| CN1112014C (en) | Wireless network roaming method of cross IP domain | |
| CN1222180C (en) | Method for constructing stabilized self-adaption self-organization network terminal | |
| CN1181655C (en) | Data packet transmission method in mobile IP | |
| CN1633107A (en) | A method of Internet domain name access based on on-demand routing in self-organized network | |
| CN1437367A (en) | Multicast business realizing method in mobile network | |
| CN1977510A (en) | Telecommunications | |
| CN1302651C (en) | A service universal block radio business supporting internodel communication method |
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 |