JP2003087337A - Gateway device and control method thereof - Google Patents

Abstract

(57) [Summary] (with correction) [PROBLEMS] To allow a mobile phone or a personal computer connected to the Internet to always access a non-IP device in a home using the same IPv6 address. A non-IP device is configured to hold an interface ID defined by IPv6. Using this interface ID, the gateway 110 generates and holds an IPv6 address of the non-IP device 100. Then, the mobile phone 13 connected to the Internet
0 or a packet addressed to the non-IP device 100 from the personal computer 140 is converted into a protocol of the network to which the non-IP device 100 is
The data is transmitted to the device 100.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a gateway device for converting a communication protocol, and more particularly to a gateway device suitable for converting between different communication protocols having different address systems and a control method thereof.

[0002]

2. Description of the Related Art In recent years, in the field of communication, the IP protocol, which is the standard protocol of the Internet, has become the de facto standard protocol, and the IP protocol has come to be used even at home. However, there are many devices that do not support the IP protocol. There is a gateway device as a device for such a device to communicate with a device connected by the IP protocol, and an example thereof is Japanese Patent Application No. 11-177916. Japanese Patent Application No. 11-177916 discloses an IEEE standard.
HAVi (Hom connected by E1394 network
e Audio / Video Interoperab
device) and the device connected to the IP network can communicate with each other via the gateway device.

[0003]

In the above technique, a combination of an IP address and a port number is used as its IP identifier in order to make a HAVi device connected to a gateway appear as a virtual IP device. Further, since the IP address uses the IP address given to the gateway, the IP addresses of the identifiers of the HAVi devices connected to the same gateway are all the same, and they are to be distinguished only by the port number. Therefore, there is a problem in that the above-described technique requires management different from the standard in the IP network, such as distinguishing devices by the IP address assigned to each device and distinguishing services within the devices by port numbers.

That is, in the above technique, since the HAVi device connected to the gateway is made to appear as a virtual IP device, the combination of the IP address and the port number is used as its IP identifier.
Regardless of whether the i-device is connected or disconnected, there is a problem in that it is always recognized at the IP address level that the device is always connected, and the true connection or disconnection state cannot be known until access is made at the port level. Therefore, the object of the present invention is to
A separate IP address is assigned to a device (hereinafter, non-IP device) connected to a network other than the network function (hereinafter, non-IP network) so that the device can communicate with the device (hereinafter, IP device) connected to the IP network. It is to provide a gateway device.

Further, when communication is performed using a gateway between networks of communication protocols that use node addresses having different numbers of bits, an address with a small number of bits is transmitted from a device on the communication protocol side that uses an address with a large number of bits. It is easy to convert the destination address of the communication packet to the device on the communication protocol side that uses, but on the other hand, there is a possibility that the address may be duplicated.
There was a problem that it was not easy. Therefore, it is an object of the present invention to provide a gateway device and a control method thereof that enable easy communication between networks of communication protocols that use node addresses having different numbers of bits.

[0006]

In order to solve the above problems, the present invention provides a non-I network connected to a non-IP network.
In a system including a P device and a gateway device connected to both an IPv6 network and a non-IP network, a means for holding an IPv6 interface ID, the interface ID, and the non-IP device are connected to the non-IP device. A means for transmitting a network identifier, which is an identifier on the existing network, is provided. Then, the gateway device is provided with a device information acquisition means for receiving the interface ID and the network identifier transmitted from the non-IP device.
Further, the gateway device is provided with a network ID acquisition means for acquiring the network ID of the IP network to which the gateway device is connected, and the network ID acquired by the network ID acquisition means.
Then, the IPv6 address is generated from the interface ID acquired by the device information acquisition means. Then, an address conversion unit for managing the correspondence between the generated IPv6 address and the network identifier acquired by the device information acquisition unit is provided.

Further, the gateway device is provided with IPv6.
NDP (Neighbor Disc)
NS (Neighb) of overly Protocol
When the IPv6 address designated by the target address in the NS packet is present in the IPv6 address managed by the address translation means, when it is present, it is NA (Neighbor). Adve
rtimement) packet is returned.

Further, the gateway device converts the IP packet received from the IP network into a non-IP network protocol and sends it to the non-IP device, and converts the non-IP data received from the non-IP network into the IP protocol. A means for transmitting to the IP network is provided so that the non-IP device and the IP device can communicate with each other. At this time, the data to be communicated between the gateway device and the non-IP device is the IPv6 of the communication destination IP device.
By including the address, the IP device can be identified from the non-IP device. Further, in the present invention, non-I
When the non-IP device connected to the P network is deleted from the non-IP network, the correspondence between the IPv6 address managed by the address conversion unit and the network identifier acquired by the device information acquisition unit is deleted. .

Furthermore, in another invention, a non-IP device connected to the non-IP network, an IPv6 network,
In a system including a gateway device connected to both non-IP networks, a means for holding device identification information (device identification information), the device identification information, and the non-IP device are connected to the non-IP device. A means for transmitting a network identifier, which is an identifier on the existing network, is provided. Then, the gateway device is provided with a device information acquisition means for receiving the device identification information and the network identifier transmitted from the non-IP device. Furthermore, the gateway device is provided with a network ID acquisition means for acquiring the network ID of the IP network to which the gateway device is connected, and a plurality of IPv6 addresses are generated using the network ID acquired by the network ID acquisition means. I am trying to do it. Then, by using the device identification information acquired by the device information acquisition means, the generated IP
An address conversion means is provided for allocating one of the v6 addresses and managing the correspondence. The address conversion means always assigns the same IPv6 address to the devices having the same device identification information.

Further, the gateway device has an IPv6
NDP (Neighbor Disc)
NS (Neighb) of overly Protocol
When the IPv6 address designated by the target address in the NS packet is present in the IPv6 address managed by the address translation means, when it is present, it is NA (Neighbor). Adve
rtimement) packet is returned.

Further, the gateway device converts the IP packet received from the IP network into a non-IP network protocol and sends it to the non-IP device, and converts the non-IP data received from the non-IP network into the IP protocol. A means for transmitting to the IP network is provided so that the non-IP device and the IP device can communicate with each other. At this time, the data to be communicated between the gateway device and the non-IP device is the IPv6 of the communication destination IP device.
By including the address, the IP device can be identified from the non-IP device.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below with reference to the drawings. First, the outline of the present invention will be described with reference to FIG. In FIG. 1, 100 is a non-IP device. Here, the non-IP device is IPv6 (Internet).
A device that does not support et Protocol Version 6) but is connected to some network. As an example of the non-IP device 100, ECH
There are refrigerators and air conditioners connected to ONET. 1
Reference numeral 10 is a gateway. Gateway 110 is non-I
The P device 100 is connected to the non-IP network 200. As an example of the non-IP network 200, ECHON
I have an ET. Further, the gateway 110 is connected to the IPv6 router 120 via the IPv6 network 210. IPv6 router 120 is the Internet 22
Connected to 0. In addition, the gateway is IPv6
Home IPv6 device 1 via network 230
It is connected to 50. A personal computer is an example of the IPv6 device 150.

According to the present invention, in the system constituted by the above equipment and network, the Internet 22
0 (for example, mobile phone 130 or PC14)
0) or the IPv6 device 150 in the home and the non-IP device 100 (for example, a refrigerator, an air conditioner, a microwave oven, etc.) in the home are provided with a mechanism for communication. In addition, in the following embodiments, the gateway 110 and the IPv6 router 120 are described as separate devices, but there is no problem even if these two functions are put in one housing. In the following description, an air conditioner is used as the non-IP device 100 and ECHONET is used as the non-IP network 150. However, it goes without saying that the present invention does not limit non-IP devices and non-IP networks to these devices.

Next, the hardware configuration of each device will be described. The IPv6 router 120 and the mobile phone 13
0, the PC 140, and the IPv6 device 150 are general devices, and a description thereof will be omitted. First, regarding the hardware configuration of the non-IP device 100, FIG.
Will be explained. In the figure, reference numeral 101 denotes a CPU, which executes various programs related to peripheral control, data processing, and communication. 102 is a storage unit, for example, RO
M (Read Only Memory), RAM (Ra
access memory, flash memory. Various programs used in this embodiment and data such as an interface ID described later are stored. 103 is a communication control unit, such as ECHONET
Controls communication via the. An air-conditioner unit 104 controls the operation of the air-conditioner.

Next, the hardware configuration of the gateway 110 will be described with reference to FIG. In the figure, reference numeral 111 denotes a CPU, which controls various peripheral parts, processes data, and executes various programs related to communication. Reference numeral 112 denotes a main storage unit, for example, a ROM (Read Only Mem).
ory), RAM (Random Access Me)
memory), flash memory, hard disk, etc. It stores various programs used in this embodiment and data such as conversion tables described later. 103 is non-IP
A communication control unit, which controls communication via ECHONET, for example. Reference numeral 104 denotes an IP communication control unit, which is IPv6.
Communication control using 6 is performed.

Next, the interface ID 450 held by the non-IP device 100 will be described with reference to FIG. The interface ID is 64-bit data and is used to identify the device. In addition, the method of assigning the interface ID is based on the IEEE "Guidelines for 6".
4-bit Global Identifier
(EUI-64) Registration Aut
“Hority”. Non-IP device 100
Holds the interface ID 450 in the storage unit 102.

Next, the conversion table 400 held by the gateway will be described with reference to FIG. The conversion table 400 is used for associating the network identifier (local address) of the non-IP device 100 in the non-IP network 200 with the IPv6 address assigned to the non-IP device 100. Conversion table 40
0 is composed of one or more conversion records 410. Each translation record 410 has a local address 411.
And an IPv6 address 412. The local address 411 is an identifier for uniquely identifying a device connected to the non-IP network 200, and ECHON
In the case of ET, the ECHONET address corresponds to this.
The IPv6 address 412 has a 128-bit IPv6
The address is stored.

Next, the registration data 700 to be sent to the gateway 110 when the non-IP device 100 is connected to the non-IP network 200 (or at an arbitrary timing).
This will be described with reference to FIG. Registration data 700
Is a local address 701 and an interface ID 70
Consists of 2. The local address 701 is an identifier of the non-IP device 100 in the non-IP network 200, and in the case of ECHONET, the ECHONET address corresponds to this. The interface ID 702 is the same as the interface ID 450 held by the non-IP device 100.

Next, a registration process performed when the non-IP device 100 is connected to the non-IP network 200 (or at an arbitrary timing) will be described with reference to FIG.
The registration process includes an interface ID transmission process 510 in the non-IP device 100 and a conversion table registration process 500 in the gateway 110. Non-IP device 100
Is connected to a non-IP network (or at any timing), the interface ID transmission processing 510
I do. In the interface ID sending process 510, the interface ID 450 recorded in the storage unit 102 is read out and the interface ID 70 of the registration data 700 is read.
Set to 2. Further, the local address of the non-IP device 100 is acquired from the communication control unit 103, for example, and is set in the local address 701 of the registration data 700.
Then, the registration data 700 is transmitted to the gateway 110 (step 511).

In the gateway 110, the non-IP device 10
When the transmission of the interface ID from 0 is detected, the conversion table registration processing 500 is activated. In the conversion table registration process 500, first, the registration data 700 sent from the non-IP device 100 is received (step 501). Next, it is determined whether the network ID in IPv6 has already been acquired (step 502). If the network ID in IPv6 has not been acquired, IPv6
The network ID is acquired from the router 130, and the storage unit 1
Store in 12. If you have already obtained the network ID,
Go to step 504. From the interface ID 702 of the registration data 700 received in step 501 and the network ID acquired in step 503 or the network ID previously acquired and stored in the storage unit 112, the IP
Generate v6 address. Then, the conversion record 410 in which the local address 701 of the registration data 700 received in step 501 is set as the local address 411 and the generated IPv6 address is set as the IPv6 address 412 is added to the conversion table 400 (step 504).

Through the above processing, the gateway 110 can assign the IPv6 address to the non-IP device 100. At this time, since the interface ID is acquired from the non-IP device 100, the gateway 1
As long as 10 are connected to the same IP network (that is, as long as the network ID of the IP network to which the gateway 110 is connected does not change), it is possible to always assign the same IPv6.

Next, a process for transmitting and receiving data between the non-IP device 100 and the IPv6 device 150 in the home, the mobile phone 130 and the personal computer 140 connected to the Internet will be described. Data from the mobile phone 130 and the personal computer 140 connected to the Internet 220 reaches the IPv6 router 120.
A method for the router 120 to send data to the gateway 110 will be described. In addition, home IPv6 device 1
Even when 50 communicates with the non-IP device 100, IPv6
The method is similar to that of the router 120.

In the IPv6 communication data (IPv6 packet), the destination of the IPv6 address is designated.
Therefore, in order for the IPv6 router 120 to transmit data to the non-IP device 100 connected to the gateway 110, an IPv6 lower layer address (for example, an Ethernet (registered trademark) address) is required. In IPv6, NDP (Neighbor Discovery) is used as a method for obtaining an address of a lower layer of IPv6.
There is a Protocol). For more information on NDP,
RFC2461 Neighbor Discover
y for IP Version 6 (IPv6). When the gateway 110 responds to the NDP, the non-I connected to the gateway 110
The IPv6 packet addressed to the P device 100 is the gateway 1
It will reach 10.

Hereinafter, the gateway 110 relating to NDP
The NDP response process 530 will be described with reference to the flowchart of FIG. The NDP response process 530 is performed by the gateway 110 by using an NDP NS (neighbor so).
activation) is started when a packet is detected. In the NDP response process 530, first, an NS packet is received (step 531). Next, it is checked whether a translation record 410 having the same IPv6 address 412 as the IPv6 address designated by the target address of the NS packet exists in the translation table 400 (step 532). If present, the lower layer address of the IP communication control unit 104 of the gateway 110 is set to NA (nei
set to ghrb advitement and send to the sender of the NS packet (step 53).
3). If it does not exist, do nothing.

Through the above processing, the gateway 110 responds to the NDP instead of the non-IP device 100, and the IPv6 packet addressed to the non-IP device 100 becomes the gateway 110.
Will reach you. The gateway uses the protocol of the non-IP network 200 to enable the non-IP device 100 to
Send to. The protocol conversion process will be described below with reference to FIG.

A home IPv6 device 150, a mobile phone 130 and a personal computer 140 connected to the Internet,
When the non-IP device 100 communicates, the following two types of communication data are used. First, the first data, which is the local data packet 450 transmitted / received between the gateway 110 and the non-IP device 100, will be described. The local data packet 450 has a local header 451, IP
It is composed of a v6 address 452 and data 453. The local header 451 is information including, for example, an ECHONET header in ECHONET, a source address, and a destination address. The IPv6 address 452 is a device of a communication destination (for example, an IPv6 device 150 at home, a mobile phone 130 or a personal computer 1 connected to the Internet).
40) IPv6 address. The data 453 is data including information to be exchanged between the non-IP device 100 and the communication destination device.

Next, the second data, that is, the gateway 110, the IPv6 device 150, and the IPv6 router 130 are used.
The IPv6 data packet 460 transmitted / received by the device will be described. The IPv6 data packet 460 includes an IPv6 header 461 and data 462. The IPv6 header is a header defined by the IPv6 protocol and includes a destination IPv6 address and a source IPv6 address.
The data 462 is data including information to be exchanged with the device of the communication destination of the non-IP device 100.

In the protocol conversion process 540, the above two types of data are converted. That is, the local data packet 450 received from the non-IP network 200 is
It is converted into a Pv6 data packet 460 and sent to the IPv6 networks 210 and 230 (protocol conversion processing 550), or the IPv6 networks 210 and 23.
The IPv6 data packet 460 received from 0 is converted into a local data packet 450 and transmitted to the non-IP network 200 (protocol conversion process 560).

It should be noted that the IPv6 packet 460 and the local packet 450 do not necessarily have to correspond one to one. For example, HTTP (HyperText Tras)
HTTP Request of nfer Protocol)
st Message, HTTP Response
You may convert by the unit of Message. Further, the plurality of IPv6 data packets 460 may be one local data packet 450. Also, one IPv6
The 6 data packet 460 may be divided into a plurality of local data packets 450. Furthermore, the plurality of local data packets 450 may be one IPv6 data packet 460. Also, one local data packet 450 may be divided into a plurality of IPv6 data packets 460. Further, the data included in the IPv6 packet 460 and the local packet 450 may include processed data of each other.

Next, details of the protocol conversion processing 550 from the IPv6 data packet 460 to the local data packet 450 will be described with reference to the flowchart of FIG. The protocol conversion process 550 is activated when the gateway 110 receives the IPv6 data packet 460. In the protocol conversion process 550, first,
The arrived IPv6 data packet 460 is read (step 551). Next, the destination IP included in the IPv6 header 461 of the read IPv6 data packet 460.
A translation record 410 having the same IPv6 address 412 as the v6 address is searched for in the translation table 400, and the local address 411 of the translation record 410 is read (step 552). Next, the local address read in step 552 is set as the destination address in the local header 451 of the local data packet 450, and the source IPv6 address of the received IPv6 data packet 460 is set as the Iv6 address 452 of the local data packet 450. . Then, the data including at least a part of the data 462 of the IPv6 data packet 460 or the data obtained by processing the data 462 is stored in the data 453 of the local data packet 450 and sent to the non-IP network 200 (step 55).
3).

Next, details of the protocol conversion processing 560 from the local data packet 450 to the IPv6 data packet 460 will be described with reference to the flowchart of FIG. The protocol conversion process 560 is activated when the gateway 110 receives the local data packet 450.

In the protocol conversion process 560, first, the arrived local data packet 450 is read (step 561). Next, the IPv6 address 452 of the local data packet read in step 561 is set to IPv6.
The IPv6 header 461 of the six data packet 460 is set as the destination (step 562). Then, the data including at least a part of the data 453 of the local data packet 450 or the data obtained by processing the data 453 is stored in the data 462 of the IPv6 data packet,
It is sent to the IPv6 network 210 or 230 (step 563).

By the above processing, the non-IP network 2
The non-IP device 100 connected to 00, the IPv6 device 150 connected to the IPv6 network, the mobile phone 130 connected to the Internet, and the personal computer 140 can communicate with each other. At this time, the interface ID sending process 510 and the gateway 110
Since the same IPv6 address is always assigned to the non-IP device 100 by the conversion table registration process 500 in the above, the IPv6 device 150 connected to the IPv6 network and the mobile phone 13 connected to the Internet.
0, PC 140 to non-IPv6 device 1 at home
When accessing 00, there is an advantage that communication can always be performed using the same IPv6 address.

Next, the registration deletion process 570 executed by the gateway 110 when the non-IP device 100 connected to the non-IP network 200 is removed from the non-IP network 200 will be described with reference to FIG. In the registration deletion process 570, first, the removed non-IP device 1
00 local address is specified (step 57).
1). As a method of detecting the local address of the removed non-IP device 100, a method of checking whether the local addresses 411 of all the conversion records 410 in the conversion table 400 are connected to the non-IP network 200, or the non-IP device 100. Just before being removed from the non-IP network 200, there is a method of notifying the gateway that it will be removed. Next, the conversion record 410 having the local address specified in step 571 is deleted from the conversion table 400 (step 572).

By the above processing, the non-IP network 2
Since the information regarding the non-IP device 100 removed from 00 is deleted from the conversion table 400, the gateway 1
No data will be transmitted to the non-IP device 100 from which 00 is removed.

When the non-IP device connected to the non-IP network 200 is deleted, the registration deletion process 570.
Instead of the above, the gateway 110 may execute the re-registration request processing 580 described below with reference to FIG.

In the re-registration request processing 580, all conversion records 910 registered in the conversion table 400 are once deleted (step 581). All non-IP devices 100 connected to the non-IP network 200
A registration request is sent to. Upon receiving the registration request, the non-IP device 100 transmits the interface ID transmission process 510.
Is performed (step 583). Non-IP network 200
When the process of step 583 is performed for all the non-IP devices 100 connected to, the process ends (step 582).

In the above embodiment, the non-IP device 10
When 0 holds the interface ID 450 and is connected to the non-IP network 200, the non-IP device 100 executes the interface ID transmission process 510, and the gateway 110 performs the conversion table registration process 500, whereby the non-IP device 100 Although the example has been described in which the same IPv6 address is always assigned to each interface, in another embodiment of the present invention, the interface ID 4 is not always required.
It is not necessary to hold 50. An example will be described below.

First, a conversion table 900 used instead of the conversion table 400 will be described with reference to FIG. The conversion table 900 is composed of one or more conversion records 910. Each conversion record 910 is
It is composed of a local address 911, an IPv6 address 912, and a device identifier 913. Local address 9
11 is a conversion record 41 in the conversion table 400.
It is the same as the local address 411 of 0. The IPv6 address 912 is the same as the IPv6 address 411 of the conversion record 410 in the conversion table 400. The device identifier 913 is information for identifying the non-IP device 100. As the device identifier 913, for example, a maker code, a business place code defined by a device object super class property of ECHONET,
The product code and serial number.

A plurality of conversion records 910 are registered in the conversion table 900 in advance. At this time, each 4
The IPv6 address is entered in advance in the IPv6 address 912 of the 60 conversion record 910. The IPv6 address used here is created from the network ID of the IPv6 network 210 to which the gateway is connected and a random numerical value or an appropriate numerical value sequence. The registration of the conversion record in the conversion table 900 may be executed when the gateway 110 is activated.

Next, the registration data 710 used instead of the registration data 700 will be described with reference to FIG. The registration data 710 includes a local address 711 and a device identifier 712. Local address 71
1 is the local address 71 in the registration data 700
Same as 1. The device identifier 712 is information for identifying the non-IP device 100, and is, for example, ECHO.
Manufacturer code, business site code, product code, etc. defined in the NET device object super class property
The serial number.

Next, when connected to the non-IP network 200, the device information sending process 810 executed in the non-IP device 100 instead of the interface ID sending process 510, and the conversion table registration process 500 in the gateway 110. The conversion tail part registration process 800 to be executed will be described with reference to FIG.
The non-IP device 100 performs the device information transmission process 810 when connected to the non-IP network (or at any timing). In the device information transmission process 810,
The device identifier recorded in the storage unit 102 is read and set in the device identifier 712 of the registration data 710. In addition, the local address of the non-IP device 100 is
For example, the registration data 710 acquired from the communication control unit 103
Is set to the local address 711. Then, the registration data 710 is transmitted to the gateway 110 (step 811).

In the gateway 110, the non-IP device 10
When the transmission of the registration data 710 from 0 is detected, the conversion table registration processing 800 is started. In the conversion table registration process 800, first, the registration data 710 sent from the non-IP device 100 is received (step 801). Next, it is checked whether or not the conversion record 910 having the same device identifier 913 as the device identifier 712 of the registration data 710 received in step 801 is registered in the conversion table 900 (step 802). If registered, the device identifier 71 of the registration data 710
Conversion record 9 having the same device identifier 913 as 2
The local address 711 of the registration data 710 received in step 802 is set to the local address 911 of 10 (step 806). If you are not registered,
In the conversion table 900, the conversion record 910 in which the device identifier 913 is not set is searched, and the local address 711 of the registration data 710 received in step 801 is set to the local address 911 of the conversion record,
The device identifier 712 is set in the device identifier 913.

In the NDP response process 530,
The process of step 532 is modified to check whether the translation table 910 has the translation record 910 having the same IPv6 address 412 as the IPv6 address specified by the target address of the NS packet. Further, in the protocol conversion processing 550, step 552
The IPv6 of the read IPv6 data packet 460
The conversion record 910 having the same IPv6 address 412 as the destination IPv6 address included in the 6th header 461 is searched from the conversion table 900, and the conversion record 910 is searched.
The local address 911 is read.

Further, when the non-IP device 100 connected to the non-IP network 200 is removed from the non-IP network, in step 572 of the registration deletion process 570, the conversion record 910 having the local address specified in step 571. The local address 911 is invalidated. Alternatively, the re-registration request process 58
In step 581 of 0, all local addresses 911 of all conversion records 910 registered in the conversion table 900 are invalidated.

By the above processing, as in the above-described embodiment, the non-IP device 100 connected to the non-IP network 200 and the IPv6 connected to the IPv6 network.
6 devices 150 and mobile phones connected to the Internet 1
30 and the personal computer 140 can communicate with each other. At this time, the interface ID transmission processing 5
10 and the conversion table registration process 500 in the gateway 110, the non-IP device 100 always has the same IP.
Since the v6 address is assigned, the same IPv6 address is always used when accessing the non-IPv6 device 100 in the home from the IPv6 device 150 connected to the IPv6 network, the mobile phone 130 connected to the Internet, or the personal computer 140. There is an advantage that communication is possible.

Next, the gateway 110 described with reference to FIG.
Another embodiment will be described with reference to FIGS. 19 and 20. In the above embodiment, in the local data packet 450,
IPv6 address 4 of the IPv6 device 150 of the communication destination
By inserting 52, I
Although the Pv6 device 150 can be designated, in the local data packet 450a in this embodiment, the I
It does not include the Pv6 address 452. Further, as shown in FIG. 20, in this embodiment, a conversion table 2000 in which a connection identifier 2013 is added to the conversion table 400 is used. Furthermore, in this embodiment, the IP communication uses connection-oriented communication such as TCP.

The operation of the protocol conversion process 2150 from the IPv6 data packet 460 to the local data packet 450a in this embodiment will be described below with reference to the flowchart of FIG. First, the IPv6 that arrived
6 data packet 460 is read (step 215)
1). Next, it is checked whether or not the IPv6 data packet 460 read in step 2152 is a connection request, and if it is a connection request, step 2153 is executed, and if it is not a connection request, step 2154 is executed. In the step 2153, the IPv6 header 46 of the IPv6 data packet 460.
It is confirmed whether a conversion record 2010 having the same IPv6 address 412 as the destination IPv6 address included in 1 exists in the conversion table 2000, and if there is, a connection process is performed and the connection identifier 2013 is stored in the conversion record 2010. . On the other hand, in step 2154,
It is checked whether it is a disconnection request. If it is a disconnection request, in step 2155, the connection identifier 2 of the conversion record 2010 is determined.
Delete 013. If it is determined in step 2154 that the request is not a disconnection request, in step 2156 the connection identifier 2013 of the conversion record 2010 is checked to determine whether or not the connection has been completed. If it does not exist, the process ends, and if it exists, the step ends. Proceed to 2157. In step 2157, the local address 411 of the conversion record 2010 is read. Next, the local address 411 is set as the destination address in the local header 451 of the local data packet 450. Then, the data including at least a part of the data 462 of the IPv6 data packet 460 or the data obtained by processing the data 462 is converted into the data 4 of the local data packet 450a.
It is stored in 53 and sent to the non-IP network 200 (step 2158).

Next, the operation of the protocol conversion process 2250 from the local data packet 450a to the IPv6 data packet 460 in this embodiment will be described with reference to the flowchart of FIG. First, step 225
The local data packet 450a is read at 1 and the local address 411 of the local data packet 450a is acquired at step 2252. Then step 225
In step 3, the conversion record 2010 including the local address 411 is searched, and it is checked whether or not there is a connection identifier 2013 in the conversion record 2010. If not, it is determined that the connection has not been established, and the process ends. . on the other hand,
If there is a connection identifier 2013, the following step 2254
In step 2255, the IPv6 address 412 corresponding to the connection identifier 2013 is acquired.
Data is transmitted to the connection identified by 013 and the IPv6 address 412. At this time, the destination IPv6 address and the source IPv6 address 412 corresponding to the connection identifier are set in the IPv6 header 461.

As described above, in this embodiment, the I
When the Pv6 device 150 and the non-IP device 100 communicate with each other via the gateway 110, the
The six devices 150 and the gateway 110 are established by connection type IP communication. As a result, there is an effect that the non-IP network 200 having a narrower address space than the IPv6 and the IPv6 networks 210 and 230 having a wider address space can communicate with each other without causing a collision due to duplication of the translated address. Also, in the local data packet 450 on the non-IP communication side, the IPv6 address 45 of the communication destination is included.
2 is not necessary, and there is an effect that the existing non-IP communication protocol and application software and middle software using the existing non-IP communication protocol need not be changed.

Next, the program structure and operation of the gateway 110 will be described in detail with reference to FIG. 1
Reference numeral 73 is a lower communication difference absorption unit, which is a non-I of a different type.
A process of absorbing the difference in the P communication control unit 103 and sharing the upper interface is performed. A non-IP communication middleware 172 performs protocol processing such as data transmission / reception of non-IP communication and node detection. An IP protocol stack 175 performs protocol processing for IPv6 communication, protocol processing for TCP connection, connection management, and the like. In this embodiment, the IP protocol stack 175
Operates as a plurality of independent processes or threads for each IP address. An IP routing control unit 176 receives the IPv6 received from the IP communication control unit 104.
The IP address stored in the header of the 6 packets is checked, and the IP packet is passed to the IP protocol stack 175 corresponding to the IP address. 54
0n is the above-described protocol conversion processing 540 or protocol conversion processing 540a. A plug-and-play control unit 174 detects connection / disconnection of the non-IP device 100 to / from the non-IP network 200 and performs settings necessary for the protocol conversion process 540n.

The plug-and-play control unit 174 is
When the connection of the non-IP device 100 to the non-IP network 200 is detected via the non-IP communication middleware, the IPv6 address 412 is obtained by the means described in the above embodiment.
Or 912, and the conversion record 410 of the conversion table 400, the conversion record 910 of the conversion table 900, or the conversion table 2000.
The conversion record 2010 is added. After the addition, the process or thread of the protocol conversion process 540n is activated. The protocol conversion process 540n
Is the generated IPv6 address 412 or 912.
The process or thread of the IP protocol stack 175 corresponding to is activated and put into a connection waiting state. On the other hand, the non-IP from the non-IP network 200
When the disconnection of the device 100 is detected via the non-IP communication middleware, the connection waiting state is released, the process or thread of the IP protocol stack 175 is terminated, and the process or thread of the protocol conversion process 540n is terminated. To do. Then, the conversion record 410 of the conversion table 400, the conversion record 910 of the conversion table 900, or the conversion record 2010 of the conversion table 2000 is deleted. By these processes, the connection / disconnection state of the non-IP device 100 to the non-IP network 200 is
From the v6 network 230 side, there is an effect that it looks as if the IPv6 equipment 150 is connected / disconnected.

The above-mentioned protocol conversion processing 540n may be a program common to all the non-IP devices 100, or may be a different program when the conversion contents differ depending on the type of the non-IP device 100. Also, the processes and threads do not necessarily have to be separated.

In addition, the gateway 110 itself has an IP
Allocate v6 address and IPv6 network 230
FIG. 18 shows an example in which the gateway 110 can be controlled by accessing from the side. 175a is an IP protocol stack for processing an IPv6 packet to the IPv6 address of the gateway 110 itself, and 177 is for controlling the gateway 110 or transmitting the status of the gateway 110 according to the data received from the IP protocol stack 175a. It is a gateway management program for

In the embodiments described above, IPv6 and ECHONET are described as different communication protocols, but the first communication protocol using a destination address and a source address of n bits and m bits of m <n are used. It is obvious that the above embodiment can be easily applied as a gateway between the second communication protocols using the destination address and the source address.

In the above embodiment, the transmission medium for communication is the IPv6 network 230, the non-IP network 2
Although 00 has been described as a physically separated figure, it is also apparent that the above-described embodiment can be applied as a gateway between communication packets of different protocols that flow on the same transmission path.

[0057]

As described above, according to the present invention,
Through the gateway, a non-IP device (for example, an air conditioner connected to a home Echonet) and a mobile phone or a personal computer connected to the Internet can communicate using the IPv6 protocol. At this time, non-IP
The device has an advantage that the IPv6 network IPv6 address to be connected is always the same address as long as the gateway to which the non-IP device is connected does not change, so that the device can be easily identified. Further, there is an effect that a mobile phone or a personal computer can always communicate with a non-IP device by using the same IPv6 address.

[Brief description of drawings]

FIG. 1 is an explanatory diagram showing an outline of an embodiment of the present invention.

FIG. 2 is a block diagram showing a hardware configuration of a non-IP device according to the embodiment of the present invention.

FIG. 3 is a block diagram showing a hardware configuration of a gateway in the embodiment of the present invention.

FIG. 4 is an interface ID according to the embodiment of the present invention.
It is explanatory drawing which showed the data structure of.

FIG. 5 is an explanatory diagram showing a data structure of a conversion table in the embodiment of the present invention.

FIG. 6 is an explanatory diagram showing a data structure of registration data in the embodiment of the present invention.

FIG. 7 is a flowchart showing a registration process in the embodiment of the present invention.

FIG. 8 is a flowchart showing NDP response processing according to the embodiment of the present invention.

FIG. 9 is an explanatory diagram showing an outline of protocol conversion processing in the embodiment of the present invention.

FIG. 10 is a flowchart showing a protocol conversion process in the embodiment of the present invention.

FIG. 11 is a flowchart showing a protocol conversion process in the embodiment of the present invention.

FIG. 12 is a flowchart showing a registration deletion process according to the embodiment of the present invention.

FIG. 13 is a flowchart showing a re-registration request process according to the embodiment of the present invention.

FIG. 14 is an explanatory diagram showing a data structure of a conversion table in the example of the present invention.

FIG. 15 is an explanatory diagram showing a data structure of registration data according to the embodiment of the present invention.

FIG. 16 is a flowchart showing a registration process according to the embodiment of the present invention.

FIG. 17 is an explanatory diagram showing a program structure of a gateway according to an embodiment of the present invention.

FIG. 18 is an explanatory diagram showing a program structure of a gateway according to an embodiment of the present invention.

FIG. 19 is an explanatory diagram showing an outline of protocol conversion processing in the embodiment of the present invention.

FIG. 20 is an explanatory diagram showing a data structure of a conversion table in the example of the present invention.

FIG. 21 is a flowchart showing a protocol conversion process in the embodiment of the present invention.

FIG. 22 is a flowchart showing a protocol conversion process in the embodiment of the present invention.

[Explanation of symbols]

100 non-IP equipment 110 gateway 120 IPv6 router 130 mobile phone 140 personal computers 150 IPv6 equipment 200 non-IP network 210, 230 IPv6 network 220 Internet

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Tomoya Ozaki             292 Yoshida-cho, Totsuka-ku, Yokohama-shi, Kanagawa             Ceremony Hitachi Digital Media Development Book             Department (72) Inventor Teiji Kuwahara             292 Yoshida-cho, Totsuka-ku, Yokohama-shi, Kanagawa             Ceremony Hitachi Digital Media Development Book             Department (72) Inventor Kazuo Nakagawa             292 Yoshida-cho, Totsuka-ku, Yokohama-shi, Kanagawa             Ceremony Hitachi Digital Media Development Book             Department F-term (reference) 5B089 GA31 GB01 KB06 KF05                 5K030 GA14 HA08 HB21 HC01 HC13                       HD03 HD10 JA02 KA04 LB07                       LB15 MA06 MD08                 5K034 AA20 DD03 EE10 FF01 FF11                       HH61

Claims (8)

[Claims] 1. A first information processing apparatus implementing a first network communication protocol using an n-bit destination address and a source address, and a first information processing apparatus using an m-bit destination address and a source address with m <n. A gateway device for enabling communication with a second information processing device implementing the second network communication protocol, comprising:
Virtual address allocating means for allocating an n-bit virtual address to the information processing device, and a connection type according to the first network communication protocol transmitted from the first information processing device to the virtual address And stores at least three of a means for establishing a communication connection, a connection identifier for identifying the communication connection, the virtual address, and an m-bit address of the second information processing device in association with each other. After the communication is established, the conversion table means receives data transmitted from the first information processing device with the virtual address as a destination in accordance with the first network communication protocol, and matches the second network communication protocol. The data is converted so that it is associated with the virtual address by the conversion table means. A bit address as a destination address of the second network communication protocol, and means for transmitting the converted data to the second information processing device according to the second network communication protocol. Gateway device to do. 2. A first information processing apparatus having a first network communication protocol using an n-bit destination address and a source address, and an m-bit destination address and a source address where m <n. A gateway device for enabling communication with a second information processing device implementing the second network communication protocol, comprising:
Virtual address allocating means for allocating an n-bit virtual address to the information processing device, and a connection type according to the first network communication protocol transmitted from the first information processing device to the virtual address And stores at least three of a means for establishing a communication connection, a connection identifier for identifying the communication connection, the virtual address, and an m-bit address of the second information processing device in association with each other. After the communication is established with the conversion table means, the m-bit address of the gateway is set as the destination from the second information processing device, the m-bit address of the second information processing device is set as the transmission source address, and the second network is used. The data transmitted according to the communication protocol is received, and the data is transmitted according to the first network communication protocol. The data is converted so that the conversion table means converts the connection for which the communication connection identified by the connection identifier associated with the m-bit address of the second information processing device is established. And a means for transmitting data to the first information processing apparatus according to the first network communication protocol. 3. A first information processing apparatus implementing a first network communication protocol using an n-bit destination address and a source address, and an m-bit destination address and a source address where m <n. A gateway device for enabling communication with a second information processing device implementing the second network communication protocol, comprising:
The data transmission from the information processing device to the first information processing device via the gateway device is performed in a state where a connection-type communication connection is established between the first information processing device and the gateway device. A gateway device characterized by being possible only. 4. A first information processing apparatus, which implements a first network communication protocol using an n-bit destination address and a source address, and an m-bit destination address and a source address where m <n. A gateway device for enabling communication with one or more second information processing devices implementing the second network communication protocol, wherein the gateway device is provided for each of the individual second information processing devices. Virtual address assigning means for assigning a unique n-bit virtual address that does not overlap with the n-bit address assigned to the second information processing device, and detection for detecting connection or disconnection of the second information processing device to the network. Means and when the detecting means detects a connection,
Means for activating the first network communication protocol processing means corresponding to the virtual address, and ending the first network communication protocol processing means corresponding to the virtual address when the detecting means detects disconnection. Means, and a gateway device. 5. A first information processing apparatus having a first network communication protocol that uses an n-bit node address as a destination address and a source address, an m-bit node address where m <n is a destination address, A gateway device for enabling communication with a second information processing device implementing a second network communication protocol used for a source address, which holds a plurality of the n-bit node addresses, Means for receiving and processing a packet according to the first network communication protocol having an address as a destination address, and the second means for holding only one m-bit node address and using the node address as a destination address Means for receiving and processing a packet according to the network communication protocol. Gateways apparatus. 6. A first information processing device implementing a first network communication protocol using an n-bit destination address and a source address, and a first information processing device using an m-bit destination address and a source address with m <n. A method of controlling a gateway device for enabling communication with a second information processing device, which implements the second network communication protocol, comprising: assigning an n-bit virtual address to the second information processing device. And a step of receiving a connection-type communication connection request from the first information processing device, the connection-type communication connection request being in accordance with the first network communication protocol, which is transmitted with the virtual address as a destination, and establishing the communication connection. At least three of a connection identifier for identifying the virtual address, the virtual address, and the m-bit address of the second information processing device. And storing the conversion table in association, after the communication is established, receives data transmitted in accordance with the first network communication protocol said virtual address as a destination from said first information processing apparatus,
The data is converted so as to match the second network communication protocol, and the m-bit address associated with the virtual address by the conversion table means is converted into the second data.
As the destination address of the network communication protocol of
And a step of transmitting the converted data to the second information processing device according to the second network communication protocol. 7. A first information processing device implementing a first network communication protocol using an n-bit destination address and a source address, and a first information processing device using an m-bit destination address and a source address with m <n. A method of controlling a gateway device for enabling communication with a second information processing device, which implements the second network communication protocol, comprising: assigning an n-bit virtual address to the second information processing device. And a step of receiving a connection-type communication connection request from the first information processing device, the connection-type communication connection request being in accordance with the first network communication protocol, which is transmitted with the virtual address as a destination, and establishing the communication connection. At least three of a connection identifier for identifying the virtual address, the virtual address, and the m-bit address of the second information processing device. And storing the conversion table in association, after the communication is established, the m-bit address of the gateway and the destination from the second information processing apparatus,
The data transmitted according to the second network communication protocol is received by using the m-bit address of the second information processing device as a source address, and the data is converted so as to match the first network communication protocol,
For the connection in which the communication connection identified by the connection identifier associated with the m-bit address of the second information processing device in the conversion table means is established, the converted data is converted into the first network communication. And a step of transmitting to the first information processing device according to a protocol. 8. A first information processing device implementing a first network communication protocol using an n-bit destination address and a source address, and a first information processing device using an m-bit destination address and a source address with m <n. A method for controlling a gateway device for enabling communication with a second information processing device implementing the second network communication protocol, comprising connection-type communication between the first information processing device and the gateway device. A method of controlling a gateway device, wherein data is transmitted from the second information processing device to the first information processing device via the gateway device only when a connection is established.