JP2004356679A - Ad hoc network address providing system - Google Patents

Ad hoc network address providing system Download PDF

Info

Publication number
JP2004356679A
JP2004356679A JP2003148494A JP2003148494A JP2004356679A JP 2004356679 A JP2004356679 A JP 2004356679A JP 2003148494 A JP2003148494 A JP 2003148494A JP 2003148494 A JP2003148494 A JP 2003148494A JP 2004356679 A JP2004356679 A JP 2004356679A
Authority
JP
Japan
Prior art keywords
terminal
address
correspondence table
ipv4
address correspondence
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.)
Pending
Application number
JP2003148494A
Other languages
Japanese (ja)
Inventor
Tatsuaki Nagafune
辰昭 長船
Michiro Yamazaki
道郎 山▲崎▼
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.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Priority to JP2003148494A priority Critical patent/JP2004356679A/en
Publication of JP2004356679A publication Critical patent/JP2004356679A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

<P>PROBLEM TO BE SOLVED: To enable communication including the IPv4 by automatically constituting an ad hoc network. <P>SOLUTION: An IP address providing system is disclosed which is constituted in such a manner that terminals taking part in the ad hoc network generate IPv6 addresses on the basis of IPv6 link local addresses to constitute a network, IPv4 addresses are made to correspond to the IPv6 addresses of the network to thereby automatically constitute the network for the IPv4 addresses. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

【0001】
【発明の属する技術分野】
本発明はアドホックネットワークのアドレスに関する。
【0002】
【従来の技術】
ネットワーク上の端末へのIPアドレス付与は、IPv4プロトコルでは、有線LANおよび無線LANでDHCPサーバの存在する場合は、DHCPサーバから付与できる(例えば、非特許文献1参照)。しかし、アドホックネットワークでは個別に設定する必要があった。IPv6プロトコルでは、有線LANおよび無線LANの場合はルータおよびDHCPサーバから付与でき、アドホックネットワークでも、重複のないリンクローカルアドレス(端末がMACアドレスを持つ場合)を持つことができる(例えば、非特許文献2参照)。
【0003】
【非特許文献1】
R.Droms、RFC1541 Dynamic Host Configuration Protocol[online]、October 1993、The Internet Engineering Task Force、[平成15年2月7日検索]、インターネット<URL:http://www.ietf.org/rfc/rfc1541.txt?number=1541>
【非特許文献2】
T.Narten、E.Nordmark、W.Simpson、RFC2641 Neighbor Discovery for IP Version 6 (IPv6)、[online]、December 1998、The Internet Engineering Task Force、[平成15年2月7日検索]、インターネット<URL:http://www.ietf.org/rfc/rfc2461.txt?number=2461>
【0004】
【発明が解決しようとする課題】
プロアクティブに経路情報を交換するアドホックネットワーク上の端末に自動的にIPv4アドレスを付与し、IPv4もしくはIPv4/IPv6混在のネットワークを構成することが課題である。
【0005】
本発明の目的は、アドホックネットワークを自動的に構成し、IPv4を含む通信を可能とすることである。
【0006】
【課題を解決するための手段】
本発明のIPアドレス付与方式では、アドホックネットワークに参加する端末がIPv6リンクローカルアドレスをもとにIPv6アドレスを作成してネットワークを構成し、このネットワークのIPv6アドレスにIPv4アドレスを対応させ、自動的にIPv4アドレスのネットワークを構成する。
【0007】
【発明の実施の形態】
以下、本発明の実施形態を図面により説明する。
【0008】
図1は、本発明の設備および機能を示すシステムの構成図である。すでにアドホックネットワークを構成している端末A(1)、端末B(2)、端末C(3)、および新たにこのアドホックネットワークに加わる端末D(4)から構成され、無線LANで通信を行う。新たに加わる端末D(4)は、IPv6ルーティングプロトコルにより、端末A(1)、B(2)、C(3)とのIPv6での通信を確立する(401)。すでにアドホックネットワークを構成する端末A(1)、B(2)、C(3)は、IPv6−IPv4のアドレス対応表(11,21,31)を持ち、端末D(4)はこれを受け取り(201)、あらかじめ定められているIPv4アドレスの範囲の空き番号を取得して他端末に宣言する(402)ことにより、IPv4アドレスの自動割当が行われる。対応表取得、IPv4アドレス宣言はすべての方法を含む。
【0009】
図2は、1台のアドレス対応表を持つ端末A(1)に1台の端末B(2)が接続する動作を示す図であり、図7は、その通信手順である。端末B(2)はIPv6による接続手順のあと、IPv6プロトコルにより、端末A(1)にアドレス対応表(12)を要求する(211)。端末A(1)は要求に応じてアドレス対応表(12)を端末B(2)に通知する(121)。端末B(2)はアドレス対応表(12)から、未使用のIPv4アドレスを選択し、登録したアドレス対応表(23)を作成し、端末A(1)に通知する(231)。
【0010】
図3は、端末A(1)、B(2)のネットワークに対し、端末C(3)が端末A(1)と接続することによりアドホックネットワークに参加する動作を示す図であり、図8は、その通信手順である。端末C(3)はIPv6による接続手順のあと、IPv6プロトコルにより、端末B(2)にアドレス対応表(23)を要求する(311)。端末A(1)は要求に応じてアドレス対応表(13)を端末C(3)に通知する(131)。端末C(3)はアドレス対応表(13)から、未使用のIPv4アドレスを選択し、登録したアドレス対応表(34)を作成し、端末A(1)に通知する(341)。端末A(1)は受け取ったアドレス対応表(34)により、自分のアドレス対応表(14)を更新する。端末A(1)はこれを端末B(2)に通知し(141)、A(1)、B(2)、C(3)の端末がアドレス対応表を共有できる。
【0011】
図4は、端末A(1)、B(2)、C(3)のネットワークに対し、端末D(4)が端末B(2)と接続することによりアドホックネットワークに参加する動作を示す図であり、図9は、その通信手順である。端末D(4)はIPv6による接続手順のあと、IPv6プロトコルにより、端末B(2)にアドレス対応表(24)を要求する(411)。端末B(2)は要求に応じてアドレス対応表(24)を端末D(4)に通知する(241)。端末D(4)はアドレス対応表(24)から、未使用のIPv4アドレスを選択し、登録したアドレス対応表45を作成し、端末B(2)に通知する(451)。端末B(2)は受け取ったアドレス対応表45により、自分のアドレス対応表(25)を更新する。端末B(2)はこれを端末A(1)に通知する(251)。端末A(1)は、自分のアドレス対応表(15)を更新し、端末C(3)に通知し(151)、A(1)、B(2)、C(3)、D(4)の端末がアドレス対応表を共有できる。
【0012】
図5は、図4のケースでアドレス重複の発生するケースの図であり、図10,11は、その通信手順である。端末B(2)が端末D(4)にアドレス対応表を通知した(231)時点では、端末A(1)からの端末C(3)参加のアドレス対応表(14)を未受信であり、かつ端末D(4)がアドレス対応表を作成して端末B(2)に通知した(442)時点では、アドレス対応表(14)を受信していた場合である。端末B(2)は端末A(1)、B(2)、C(3)のアドレス対応表と端末A(1)、B(2)、D(4)のアドレス対応表をもとに新たなアドレス対応表(28)を更新する。ここで整合性を判定し(291)、重複がなければ端末A(1)、B(2)、C(3)、D(4)のアドレス対応表を作成する。C(3)とD(4)のIPv4アドレス重複が有った場合は、あらかじめ定められたルール(例えばIPv6アドレスの大小)に従って、一方(この場合は端末D(4))にアドレスの再選択を指示する(292)。端末D(4)では再度IPv4アドレスを選択し、アドレス対応表(44)を更新し、端末B(2)にアドレス対応表を通知する(442)。端末B(2)で重複無しと判断できれば、図4と同様に他端末に新しいアドレス対応表を通知する(281,282,181)。
【0013】
図6は、アドレス対応表の例で、IPv6アドレスとIPv4アドレスの対応、および対象となるIPv4アドレス一覧を含む。
【0014】
図12は、1台の端末がアドホックネットワークから離脱する例の図であり、図13は、その通信手順である。端末D(4)が停止または当該アドホックネットワークの通信範囲外に移動した場合で、B(2)が端末D(4)からのメッセージを受け取れなくなった(202)場合、直ちに、もしくは定められた規則による時間の後、他端末に連絡を行う(242,243)。他端末からも端末D(4)のメッセージが確認できないと判明した場合(191,291)、アドレス対応表から端末D(4)を削除し、他端末に通知する(232,233)。他端末のいずれかがD(4)のメッセージを確認できた場合は、アドレス対応表の変更は行わない。
【0015】
図14は、同じ対象IPv4アドレスを持つ2つのアドホックネットワークが接続した場合に、互いのアドレス対応表を更新、必要ならアドレス再割り当てを行う場合の図であり、図15,16は、その通信手順である。端末A(1)、端末C(3)を含むネットワークX(100)と端末B(2)、端末D(4)を含むネットワークY(200)が通信範囲を共有し、端末A(1)と端末B(2)が通信を開始する(101)。定められた規則により端末から他方の端末にアドレス対応表を通知する(ここでは端末A(1)から端末B(2)にアドレス対応表(17)を通知)(171)。端末B(2)で保有していたアドレス対応表(27)を更新し、整合性を確認し(293)、重複アドレスの優先度を判定し(ここではC(3)とD(4)が重複し、C(3)が優先とする)、端末B(2)からD(4)に変更指示(294)を行う。端末D(4)でアドレス対応表(47)を再作成し、端末D(4)でからアドレス対応表(47)を端末B(2)に通知(472)、端末B(2)で作成したアドレス対応表(28)を端末A(1)およびネットワークY(200)の他端末に通知する(281,282)。以下、重複が消滅するまで同様の処理を行う。
【0016】
ここで、以上の通信手順を実現するため、各端末で、CPUがプログラムを実行することにより具現化されるプロセスを図17〜19で説明する。
【0017】
図17は、システム起動時などの起動時のプロセスを表したフローチャートで、タイマ割込み(51)後、IPv6経路情報受信待ち(52)状態となり、経路情報を受信したら経路情報からルーティングテーブル書込み(53)を行い、IPv4プロセスが未起動であればIPv4アドレス取得プロセス起動(55)処理を行い、IPv6経路情報受信待ち(52)状態に戻る。タイマ割込みルーチン(51)では、IPv6経路情報の送信(511)とタイマ設定(512)を行う。
【0018】
図18は、IPv4アドレス取得プロセス起動(55)を表したフローチャートで、アドレス対応表取得要求送信(551)を行い、アドレス対応表受信待ち(552)で受信した後、対応表に基づいてIPv4アドレス書込み(553)を行い、更新後のアドレス対応表送信(554)を行い、IPv4アドホックネットワークプロセス起動(6)処理を行う。その後、パケット受信待ち(555)状態となり、受信後にパケット解析(556)を行い、アドレス対応表送信、アドレス更新要求、アドレス対応表送信要求の3種類の要求を判定する。アドレス対応表送信の場合、アドレス対応表更新(557)を行い、整合性に問題のある場合はアドレス更新要求送信(558)を行い、パケット受信待ち(555)に戻る。アドレス更新要求の場合、アドレス対応表再作成(561)を行い、更新後のアドレス対応表送信(562)を行い、自身のIPv4アドレスが変更されたのでIPv4アドホックネットワークプロセス起動(6)処理を行い、パケット受信待ち(555)に戻る。アドレス対応表送信要求の場合は、アドレス対応表送信(571)を行い、パケット受信待ち(555)に戻る。
【0019】
図19は、IPv4アドホックネットワークプロセス起動(6)を表したフローチャートで、タイマ割込み(61)後、IPv4経路情報受信待ち(62)状態となり、IPv4経路情報を受信したら経路情報からルーティングテーブル書込み(63)を行い、IPv4経路情報受信待ち(62)状態に戻る。タイマ割込みルーチン(61)では、IPv4経路情報の送信(611)とタイマ設定(612)を行う。
【0020】
以上、本発明について具体的に記述したが、本発明は上記実施例に示したものに限られるものではない。
【0021】
【発明の効果】
DHCPサーバのようなアドレス付与設備を持たないアドホックネットワークにおいて、IPv4アドレスの自動的な、割り当て、追加、削除、再割り当てを可能にする。また、IPv6、IPv4両方のアプリケーションに対応できる。
【図面の簡単な説明】
【図1】概要。
【図2】端末追加時のアドレス割り当て動作の例(1台+1台)。
【図3】端末追加時のアドレス割り当て動作の例(2台+1台)。
【図4】端末追加時のアドレス割り当て動作の例(3台+1台)。
【図5】端末追加時のアドレス割り当て動作の例(アドレス重複)。
【図6】アドレス対応表の例。
【図7】図2の通信手順。
【図8】図3の通信手順。
【図9】図4の通信手順。
【図10】図5の通信手順。
【図11】図10の通信手順の2。
【図12】端末離脱と対応表更新の例。
【図13】図12の通信手順。
【図14】アドホックネットワークの接続とアドレス再割り当ての例。
【図15】図14の通信手順。
【図16】図15の通信手順の2。
【図17】起動時のプロセスのフローチャート。
【図18】IPv4アドレス取得プロセス起動のフローチャート。
【図19】IPv4アドホックネットワークプロセス起動のフローチャート。
【符号の説明】
1…端末(A)、2…端末(B)、3…端末(C)、4…端末(D)、11…アドレス対応表、21…アドレス対応表、31…アドレス対応表、41…アドレス対応表、201…対応表取得、401…IPv6ルーティングプロトコル、402…IPv4アドレス宣言。
[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to addresses in ad hoc networks.
[0002]
[Prior art]
In the IPv4 protocol, when a DHCP server exists in a wired LAN and a wireless LAN, an IP address can be assigned to a terminal on a network from the DHCP server (for example, see Non-Patent Document 1). However, in the ad hoc network, it was necessary to set individually. In the IPv6 protocol, a wired LAN and a wireless LAN can be assigned from a router and a DHCP server, and an ad hoc network can have a unique link-local address (when a terminal has a MAC address) (for example, see Non-Patent Document). 2).
[0003]
[Non-patent document 1]
R. Droms, RFC1541 Dynamic Host Configuration Protocol [online], October 1993, The Internet Engineering Task Force, [Retrieved February 7, 2003], Internet <URL: http: // www. ief. org / rfc / rfc1541. txt? number = 1541>
[Non-patent document 2]
T. Narten, E .; Nordmark, W.C. Simpson, RFC2641 Neighbor Discovery for IP Version 6 (IPv6), [online], December 1998, The Internet Engineering Task Force, [Search on February 7, 2003: w. ief. org / rfc / rfc2461. txt? number = 2461>
[0004]
[Problems to be solved by the invention]
The problem is to automatically assign an IPv4 address to a terminal on an ad hoc network that proactively exchanges route information, and to configure an IPv4 or a mixed IPv4 / IPv6 network.
[0005]
An object of the present invention is to automatically configure an ad hoc network and enable communication including IPv4.
[0006]
[Means for Solving the Problems]
In the IP address assignment method according to the present invention, a terminal participating in an ad hoc network creates an IPv6 address based on an IPv6 link local address to form a network, associates an IPv4 address with the IPv6 address of the network, and automatically creates an IPv4 address. Configure a network with an IPv4 address.
[0007]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0008]
FIG. 1 is a configuration diagram of a system showing the equipment and functions of the present invention. It is composed of a terminal A (1), a terminal B (2), a terminal C (3), and a terminal D (4) which newly join the ad hoc network, and communicates with a wireless LAN. The newly added terminal D (4) establishes IPv6 communication with the terminals A (1), B (2) and C (3) according to the IPv6 routing protocol (401). The terminals A (1), B (2) and C (3) which have already formed the ad hoc network have the IPv6-IPv4 address correspondence table (11, 21, 31), and the terminal D (4) receives this ( 201), an IPv4 address is automatically assigned by acquiring a free number in a predetermined IPv4 address range and declaring it to another terminal (402). The correspondence table acquisition and the IPv4 address declaration include all methods.
[0009]
FIG. 2 is a diagram showing an operation of connecting one terminal B (2) to a terminal A (1) having one address correspondence table, and FIG. 7 shows a communication procedure thereof. After the connection procedure based on IPv6, the terminal B (2) requests the address correspondence table (12) from the terminal A (1) using the IPv6 protocol (211). The terminal A (1) notifies the terminal B (2) of the address correspondence table (12) in response to the request (121). The terminal B (2) selects an unused IPv4 address from the address correspondence table (12), creates a registered address correspondence table (23), and notifies the terminal A (1) of the address (231).
[0010]
FIG. 3 is a diagram illustrating an operation in which the terminal C (3) joins the ad hoc network by connecting to the terminal A (1) with respect to the networks of the terminals A (1) and B (2). The communication procedure. After the connection procedure based on IPv6, the terminal C (3) requests the address correspondence table (23) from the terminal B (2) using the IPv6 protocol (311). The terminal A (1) notifies the address correspondence table (13) to the terminal C (3) in response to the request (131). The terminal C (3) selects an unused IPv4 address from the address correspondence table (13), creates a registered address correspondence table (34), and notifies the terminal A (1) of the address (341). The terminal A (1) updates its own address correspondence table (14) with the received address correspondence table (34). The terminal A (1) notifies this to the terminal B (2) (141), and the terminals A (1), B (2) and C (3) can share the address correspondence table.
[0011]
FIG. 4 is a diagram showing an operation in which the terminal D (4) joins the ad hoc network by connecting to the terminal B (2) with respect to the networks of the terminals A (1), B (2) and C (3). FIG. 9 shows the communication procedure. After the connection procedure based on IPv6, the terminal D (4) requests the address correspondence table (24) from the terminal B (2) according to the IPv6 protocol (411). The terminal B (2) notifies the address correspondence table (24) to the terminal D (4) in response to the request (241). The terminal D (4) selects an unused IPv4 address from the address correspondence table (24), creates a registered address correspondence table 45, and notifies the terminal B (2) (451). The terminal B (2) updates its own address correspondence table (25) with the received address correspondence table 45. The terminal B (2) notifies this to the terminal A (1) (251). The terminal A (1) updates its own address correspondence table (15) and notifies the terminal C (3) (151), and A (1), B (2), C (3), D (4). Of terminals can share the address correspondence table.
[0012]
FIG. 5 is a diagram showing a case where address duplication occurs in the case of FIG. 4, and FIGS. 10 and 11 show the communication procedure. At the time point when the terminal B (2) notifies the terminal D (4) of the address correspondence table (231), the address correspondence table (14) for the terminal C (3) participation from the terminal A (1) has not been received, At the time when the terminal D (4) creates the address correspondence table and notifies the terminal B (2) (442), the address correspondence table (14) has been received. Terminal B (2) is newly based on the address correspondence table of terminals A (1), B (2) and C (3) and the address correspondence table of terminals A (1), B (2) and D (4). The updated address correspondence table (28) is updated. Here, the consistency is determined (291), and if there is no overlap, an address correspondence table of terminals A (1), B (2), C (3) and D (4) is created. If there is an IPv4 address overlap between C (3) and D (4), the address is reselected to one (in this case, terminal D (4)) according to a predetermined rule (eg, the size of the IPv6 address). (292). The terminal D (4) selects the IPv4 address again, updates the address correspondence table (44), and notifies the terminal B (2) of the address correspondence table (442). If the terminal B (2) can determine that there is no duplication, it notifies another terminal of a new address correspondence table as in FIG. 4 (281, 282, 181).
[0013]
FIG. 6 is an example of an address correspondence table, which includes correspondence between IPv6 addresses and IPv4 addresses and a list of target IPv4 addresses.
[0014]
FIG. 12 is a diagram illustrating an example in which one terminal leaves the ad hoc network, and FIG. 13 illustrates a communication procedure thereof. If the terminal D (4) stops or moves out of the communication range of the ad hoc network and the terminal B (2) cannot receive the message from the terminal D (4) (202), immediately or in accordance with a prescribed rule After the time according to (2), the terminal is contacted to another terminal (242, 243). When it is determined that the message of the terminal D (4) cannot be confirmed from the other terminal (191, 291), the terminal D (4) is deleted from the address correspondence table and notified to the other terminal (232, 233). If any of the other terminals can confirm the message of D (4), the address correspondence table is not changed.
[0015]
FIG. 14 is a diagram illustrating a case where two ad hoc networks having the same target IPv4 address are connected, the address correspondence table is updated, and if necessary, addresses are reassigned. FIGS. It is. Network X (100) including terminal A (1) and terminal C (3) and network Y (200) including terminal B (2) and terminal D (4) share a communication range. The terminal B (2) starts communication (101). A terminal notifies the other terminal of an address correspondence table according to a predetermined rule (here, terminal A (1) notifies terminal B (2) of address correspondence table (17)) (171). The address correspondence table (27) held by the terminal B (2) is updated, the consistency is confirmed (293), and the priority of the duplicate address is determined (here, C (3) and D (4) Duplicate, C (3) has priority), and terminal B (2) issues a change instruction (294) to D (4). The terminal D (4) re-creates the address correspondence table (47), and the terminal D (4) notifies the terminal B (2) of the address correspondence table (47) (472) and creates the address correspondence table (47). The terminal A (1) and the other terminal of the network Y (200) are notified of the address correspondence table (28) (281, 282). Hereinafter, the same processing is performed until the duplication disappears.
[0016]
Here, in order to realize the above communication procedure, a process embodied by a CPU executing a program in each terminal will be described with reference to FIGS.
[0017]
FIG. 17 is a flowchart showing a process at the time of startup such as system startup. After a timer interrupt (51), the system enters a state of waiting for receiving IPv6 route information (52). When route information is received, the routing table is written from the route information (53). ) Is performed, and if the IPv4 process has not been started, the IPv4 address acquisition process is started (55), and the process returns to the waiting state for receiving IPv6 route information (52). In the timer interrupt routine (51), transmission of IPv6 route information (511) and timer setting (512) are performed.
[0018]
FIG. 18 is a flowchart showing the start of the IPv4 address acquisition process (55). After transmitting the address correspondence table acquisition request (551) and receiving the request in the address correspondence table reception wait (552), the IPv4 address is acquired based on the correspondence table. The writing (553) is performed, the updated address correspondence table is transmitted (554), and the IPv4 ad hoc network process activation (6) processing is performed. Thereafter, a packet reception wait state (555) is entered, and after reception, packet analysis (556) is performed to determine three types of requests: address correspondence table transmission, address update request, and address correspondence table transmission request. In the case of transmitting the address correspondence table, the address correspondence table is updated (557). If there is a problem with the consistency, the address update request is transmitted (558), and the process returns to the packet reception wait (555). In the case of an address update request, the address correspondence table is re-created (561), the updated address correspondence table is transmitted (562), and since the own IPv4 address has been changed, the IPv4 ad hoc network process activation (6) processing is performed. Then, the process returns to waiting for packet reception (555). In the case of the address correspondence table transmission request, the address correspondence table is transmitted (571), and the process returns to the packet reception waiting (555).
[0019]
FIG. 19 is a flowchart showing the start of the IPv4 ad hoc network process (6). After the timer interrupt (61), the process enters a waiting state for receiving IPv4 route information (62). When the IPv4 route information is received, the routing table is written from the route information (63). ), And returns to the waiting state for receiving IPv4 route information (62). In the timer interrupt routine (61), transmission of IPv4 route information (611) and timer setting (612) are performed.
[0020]
As described above, the present invention has been specifically described. However, the present invention is not limited to the above embodiments.
[0021]
【The invention's effect】
It enables automatic assignment, addition, deletion, and reassignment of IPv4 addresses in an ad hoc network that does not have address provision equipment such as a DHCP server. Also, it can support both IPv6 and IPv4 applications.
[Brief description of the drawings]
FIG. 1 Overview.
FIG. 2 shows an example of an address assignment operation when a terminal is added (one unit + 1).
FIG. 3 is an example of an address assignment operation when adding a terminal (2 + 1).
FIG. 4 shows an example of address assignment operation when adding a terminal (3 + 1).
FIG. 5 is an example of an address assignment operation when a terminal is added (address duplication).
FIG. 6 is an example of an address correspondence table.
FIG. 7 is a communication procedure of FIG. 2;
FIG. 8 is a communication procedure of FIG. 3;
FIG. 9 is a communication procedure of FIG. 4;
FIG. 10 is a communication procedure of FIG. 5;
FIG. 11 shows a second communication procedure of FIG.
FIG. 12 shows an example of terminal disconnection and correspondence table update.
FIG. 13 is a communication procedure of FIG.
FIG. 14 shows an example of connection of an ad hoc network and reallocation of addresses.
FIG. 15 is a communication procedure of FIG. 14;
FIG. 16 shows a second communication procedure of FIG.
FIG. 17 is a flowchart of a process at the time of activation.
FIG. 18 is a flowchart of starting an IPv4 address acquisition process.
FIG. 19 is a flowchart of starting an IPv4 ad hoc network process.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Terminal (A), 2 ... Terminal (B), 3 ... Terminal (C), 4 ... Terminal (D), 11 ... Address correspondence table, 21 ... Address correspondence table, 31 ... Address correspondence table, 41 ... Address correspondence Table, 201: Correspondence table acquisition, 401: IPv6 routing protocol, 402: IPv4 address declaration.

Claims (3)

アドホックネットワークにおいて、IPv4アドレスの割り当て、追加、削除、再割り当てを行う、ネットワークアドレス付与方式。A network address assignment method for assigning, adding, deleting, and reassigning IPv4 addresses in an ad hoc network. 請求項1において、クライアント端末のみで自動的に行うネットワークアドレス付与方式。2. The network address assignment method according to claim 1, wherein the network address is automatically assigned only to the client terminal. 請求項1において、IPv6アドレスをもとにIPv4アドレスを割り当て、IPv6、IPv4両方のネットワークに対応するアドレス付与方式。2. The address assignment method according to claim 1, wherein an IPv4 address is assigned based on the IPv6 address, and the IPv6 address is compatible with both IPv6 and IPv4 networks.
JP2003148494A 2003-05-27 2003-05-27 Ad hoc network address providing system Pending JP2004356679A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2003148494A JP2004356679A (en) 2003-05-27 2003-05-27 Ad hoc network address providing system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2003148494A JP2004356679A (en) 2003-05-27 2003-05-27 Ad hoc network address providing system

Publications (1)

Publication Number Publication Date
JP2004356679A true JP2004356679A (en) 2004-12-16

Family

ID=34044843

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2003148494A Pending JP2004356679A (en) 2003-05-27 2003-05-27 Ad hoc network address providing system

Country Status (1)

Country Link
JP (1) JP2004356679A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100338920C (en) * 2005-01-27 2007-09-19 中国科学院计算技术研究所 Method for building emergent communicating system by hierarchical self-organized network
JP2008165672A (en) * 2007-01-04 2008-07-17 Hitachi Ltd Population dynamics management system
US7899054B2 (en) 2005-07-05 2011-03-01 Brother Kogyo Kabushiki Kaisha Management device and program

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100338920C (en) * 2005-01-27 2007-09-19 中国科学院计算技术研究所 Method for building emergent communicating system by hierarchical self-organized network
US7899054B2 (en) 2005-07-05 2011-03-01 Brother Kogyo Kabushiki Kaisha Management device and program
JP2008165672A (en) * 2007-01-04 2008-07-17 Hitachi Ltd Population dynamics management system

Similar Documents

Publication Publication Date Title
JP3425192B2 (en) Address information automatic setting processing method and address information setting device
JP4226553B2 (en) Routing in data communication networks
JP4705650B2 (en) Communication node
US8103784B2 (en) Communication device and communication control method using efficient echonet address determination scheme
JP2003348116A (en) Address automatic setting system for in-home network
JP3885585B2 (en) Router device and network system using the same
US20090213792A1 (en) Apparatus and method for setting a default gateway address in a mobile communication system
CN101873320B (en) Client information verification method based on DHCPv6 relay and device thereof
JP4114939B2 (en) Node connection method, network identifier assignment method, computer-readable medium, and network system
US7289471B2 (en) Mobile router, position management server, mobile network management system, and mobile network management method
US8291111B1 (en) Responding to a DHCPLEASEQUERY message
JP4186733B2 (en) Communication system, terminal, and address generation method
JP4549055B2 (en) Setting method of network address in wireless personal area network
JP2006157609A (en) Communication control apparatus and communication control method
JP2004356679A (en) Ad hoc network address providing system
JP2006148813A (en) Analysis apparatus management system, and program and analysis apparatus for analysis apparatus management server
JP4940707B2 (en) IP address assignment system and IP address assignment method
JP2001308909A (en) Method for assigning logical network address and terminal
KR20020055848A (en) Dynamic ip address management method using radius server
JP2006211347A (en) Radio communication system
JP6714294B2 (en) Relay device
JP2005210554A (en) Dhcp substitute server
JP5691612B2 (en) Communication system, router, switching hub, and program
JP2003309596A (en) Mobile communication network system, external agent router, address server and packet delivery method used for the same
JP2004266415A (en) Connection apparatus