WO2006095391A1 - パケット中継装置 - Google Patents
パケット中継装置 Download PDFInfo
- Publication number
- WO2006095391A1 WO2006095391A1 PCT/JP2005/003788 JP2005003788W WO2006095391A1 WO 2006095391 A1 WO2006095391 A1 WO 2006095391A1 JP 2005003788 W JP2005003788 W JP 2005003788W WO 2006095391 A1 WO2006095391 A1 WO 2006095391A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet
- group
- virtual
- address
- terminal
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1836—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with heterogeneous network architecture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/283—Processing of data at an internetworking point of a home automation network
- H04L12/2836—Protocol conversion between an external network and a home network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
Definitions
- the present invention relates to a packet relay apparatus that virtually groups a plurality of terminals connected to a network and provides a closed network for each group.
- IP Internet Protocol
- each device As the number of devices connected to the network naturally increases with the spread of such networks, it is desirable to manage each device in an integrated manner.
- this management method for example, a configuration is possible in which devices are grouped in arbitrary units so that only devices belonging to the group can communicate with each other.
- the search range can be narrowed down by searching within a predetermined group, and the processing amount and time required for the search can be reduced.
- each terminal identifies terminals that belong to a loop and terminals that do not, so that it is possible to secure security by limiting external access to members belonging to a predetermined group.
- each terminal when grouping communication partners distributed over a network, each terminal individually authenticates the communication partner and ensures security on the communication path.
- the communication services provided on the network are also diversified.
- the IP phone call service there are one-to-many and many-to-many group conference calls as well as one-to-one call services.
- communication between terminals is one-to-one. It is necessary to realize one-to-many or many-to-many communication.
- communication methods such as broadcast communication or multicast communication! /.
- Method 2 As a method of transferring multicast packets associated with multicast Z broadcast communication to other networks, a method of converting multicast packets into unicast packets and transferring them (method 1) ), A method of converting the IP address of the broadcast packet into the IP address of the forwarding broadcast packet (referred to as Method 2) has been proposed.
- the conventional technique using multicast requires router settings for multicast packet routing in the core network in communication via the Internet or a large-scale core network. This not only increases the management load of the multicast address, but also increases the routing processing at each relay device.
- Method 1 since multicast packets are converted into multicast packets and transferred by Z, in order to realize many-to-many communication, an address related to the destination terminal to which the packets are to be transferred. All the information needs to be managed, and the advantages of multicast communication are lost. Also in Method 2 above, since a given relay device converts a broadcast packet into a broadcast address for another network, it is not different from multipoint-to-multipoint communication. ,.
- Patent Document 1 Japanese Patent Laid-Open No. 2001-230774
- Patent Document 2 JP 2004-282199 A
- An object of the present invention is to provide a packet relay device that efficiently transfers communication packets transmitted from a plurality of terminals connected to a network.
- the present invention adopts the following configuration in order to solve the above-described problems. That is, the present invention is a network in which a plurality of local networks are connected via a global network, and is located at the boundary between the local network and the global network and receives a broadcast packet from a terminal in the local network; An acquisition unit that identifies a transmission source terminal from the broadcast packet and acquires group information regarding a group to which the identified terminal belongs, and converts the broadcast packet into a virtual multicast packet corresponding to the previously acquired group information A packet comprising: a conversion unit; and a transfer unit that is connected to the virtual multicast packet via the global network and transfers the virtual multicast packet to another relay device corresponding to the virtual multicast packet. It is for the splicing device.
- the packet relay device includes a virtual packet receiving unit that receives the virtual multicast packet, and packet conversion that converts the virtual multicast packet into an actual broadcast packet corresponding to the virtual multicast packet. And a transmission unit for transmitting the converted actual broadcast packet into the local network.
- a broadcast packet from a terminal is converted into a virtual multicast packet corresponding to each group and transferred to each group to which the terminal belongs. That is, when receiving a broadcast packet from a terminal, the packet relay apparatus according to the present invention knows all the groups to which the terminal belongs, and transfers the broadcast packet to a terminal group belonging to all the groups.
- the present invention can implement intra-group broadcast in a closed network in which terminals are grouped.
- each terminal that wants to transmit a broadcast packet is a member of all the groups to which the terminal belongs without being aware of where the terminals that are members in the group to which the terminal belongs are located on the network. Can send broadcast packets to wear.
- the virtual multicast packet converted based on the group information to which the terminal serving as the transmission source belongs is transferred to another packet relay device corresponding to the virtual multicast packet.
- the virtual multicast packet according to the present invention is connected to another terminal belonging to the same group as the group to which the identified terminal belongs as the destination address, and the boundary between the other local network and the global network.
- a multicast address may be set so that the other packet relay device located in can recognize that the broadcast packet for the group has been converted.
- the present invention is a network in which a plurality of local networks are connected via a global network, and is located at the boundary between the local network and the global network, and receives multicast packets from terminals in the local network.
- a receiving unit, a packet group acquiring unit that acquires group information corresponding to the multicast packet, and the terminal that is a transmission source is specified from the multicast packet, and group information relating to a group to which the specified terminal belongs is acquired.
- a group determination unit that determines a transmission destination group, and the previously received multicast packet
- a conversion unit that converts the virtual multicast packet corresponding to the destination group
- a transfer unit that transfers the virtual multicast packet to another relay device corresponding to the virtual multicast packet via the global network. It is also about the packet relay device.
- the packet relay apparatus includes a virtual packet receiving unit that receives the virtual multicast packet, and a packet conversion unit that converts the virtual multicast packet into an actual multicast packet corresponding to the virtual multicast packet. And a transmitter that transmits the converted real multicast packet into the local network. You may make it prepare.
- a transfer destination group is determined from group information corresponding to the multicast address of the multicast packet and group information to which the terminal that is the transfer source of the multicast packet belongs.
- the virtual multicast packet corresponding to the determined group is converted and transferred.
- the packet relay device receives a multicast packet from a terminal, and when the group to which the terminal belongs and the group corresponding to the multicast address of the multicast packet match, Forwarded to other packet relay devices
- the present invention can realize intra-group multicast within a closed network in which each terminal is grouped, and can eliminate multicast packets from outside the group.
- the present invention provides information on a terminal in a local network to which the terminal is connected, group information about a group to which the terminal belongs, and a broadcast packet from the terminal as a virtual multicast packet corresponding to the group.
- Information transmission unit for transmitting the conversion information for conversion into the virtual broadcast packet and the reverse conversion information for converting the virtual multicast packet into the actual broadcast packet to the other packet relay device, and from the other packet relay device
- an information update unit that updates the group information, conversion information, and reverse conversion information held by itself based on the group information, conversion information, and reverse conversion information.
- the present invention provides group information corresponding to a multicast packet from a terminal in the local network, second group information relating to a group to which the terminal belongs, and a virtual multicast packet corresponding to a destination group of the multicast packet.
- An information transmission unit for transmitting the conversion information for conversion into the virtual multicast packet and the reverse conversion information for converting the virtual multicast packet into a real multicast packet to another packet relay device;
- An information update unit that further comprises: Packet relay device.
- information regarding a group of terminals that are members of a target group is associated with the group information and exchanged between the packet relay apparatuses.
- address information and the like of these terminal groups are automatically synchronized in a network having a plurality of terminals, so that address management is automatically performed.
- efficient network operation is possible by automatically assigning numbers so that there is no duplication.
- the present invention may be a method for causing a computer to realize any of the functions described above. Further, the present invention may be a program for realizing any of the functions described above. In the present invention, such a program may be recorded in a computer-readable storage medium.
- FIG. 1 is a diagram showing a network configuration.
- FIG. 2 is a diagram showing an address form in a network.
- FIG. 3 is a functional configuration diagram of GW-A in the first embodiment.
- FIG. 4 is a functional configuration diagram of GW-B in the first embodiment.
- FIG. 5 is a diagram showing a GW-A routing table in the first embodiment.
- FIG. 6 is a diagram showing packet transfer in the first embodiment.
- FIG. 7 is a diagram showing a packet processing flow (Local ⁇ Global) in the first embodiment.
- FIG. 8 is a diagram showing a packet processing flow (Global ⁇ Local) in the first embodiment.
- FIG. 9 is a functional configuration diagram of GW-A in the second embodiment.
- FIG. 10 is a functional configuration diagram of GW-B in the second embodiment.
- FIG. 11 is a diagram showing a routing table of GW-A in the second embodiment.
- FIG. 12 is a diagram showing packet forwarding in the second embodiment.
- FIG. 13 is a diagram showing a packet processing flow (Local ⁇ Global) in the second embodiment.
- FIG. 14 is a diagram showing a packet processing flow (Global ⁇ Local) in the second embodiment.
- FIG. 15 is a functional configuration diagram of GW-A in the third embodiment.
- FIG. 16 is a diagram showing an inter-gateway synchronization sequence in the third embodiment.
- a gateway device (hereinafter referred to as a gateway) according to the first embodiment of the present invention will be described below.
- FIG. 1 is a diagram showing a network configuration in the first embodiment.
- the network in the first embodiment is an IP (Internet Protocol) network constituted by local networks A, B, C and D, and the core network 10.
- Local networks A, B, C, and D use IP and connect via the core network 10.
- the terminals in each of the local networks A, B, C, and D are connected to the core network 10 via the gateways GW-A, GW-B, GW-C, and GW-D, respectively. That is, the gateways GW—A, GW—B, GW—C, and GW—D are respectively packet relays provided between the local networks A, B, C, and D that they manage and the core network 10. Device.
- Each local network is connected to a device (hereinafter referred to as a terminal) having an IP communication function.
- Terminals 101 to 104 are connected to the local network A, and terminals 201 to 204 are connected to the local network B.
- Examples of these terminals include various devices such as various personal computers (PCs), televisions, audio devices, refrigerators, and the like.
- the number of terminals connected to each local network is not limited to the number shown in this embodiment.
- Each terminal is assigned an IP address.
- the destination and the source are specified by this IP address.
- the address form assigned to each terminal in the network shown in FIG. 1 will be described with reference to FIG. further, We will also explain how the terminals with these address forms are grouped together.
- the IP used in this embodiment is IPv4, and the IP address assigned to each terminal is also an IPv4 address.
- the present invention is not limited to IPv4 but can be used with IPv6.
- the IP address assigned to each terminal uses a local IP address that can be freely assigned in each local power network.
- the address assigned to each terminal is not limited to the local IP address, and a global IP address unique to the entire network may be assigned.
- FIG. 2 shows the local networks A and B among the networks shown in FIG.
- local network A is a network that is built at the home of a user who uses this network
- local network B is a network that is built at the home where the parents of this user live. ,.
- Each terminal connected to each local network is set with the following local IP addresses (the following IP addresses are examples).
- Noren network-B Terminal 204: "192. 150. 0. 14"
- the gateways GW-A and GW-B manage the virtual network in addition to the real network. This is to group and manage each terminal connected to each local network. In this virtual network, each terminal is assigned a different virtual IP address for each of the loops to which it belongs. Terminals 101, 102 and 104 in the local network A and terminals 201, 202 and 204 ⁇ in the low power network B Each shall belong to group 1. Terminals 103 and 203 do not belong to this group 1. Each terminal belonging to group 1 is assigned the virtual IP address for group 1 shown below and managed by each gateway.
- Gnole 1 Terminal 101: ⁇ 10. 20. 20. 10 ''
- Gnole 1 Terminal 102: ⁇ 10. 20. 20. 13 ''
- Gnole 1 Terminal 104: “10. 20. 20. 12”
- Gnole 1 Terminal 201: "10. 10. 10. 102"
- Gnole 1 Terminal 202: "10. 10. 10. 103"
- Gnole 1 Terminal 204: "10. 10. 10. 100"
- the terminal communicates with other terminals in the local network to which the terminal is connected and terminals in other local networks via the core network 10 by using the IP address assigned to each terminal. For example, when the terminal 101 communicates with the terminal 201 in the local network B, the terminal 101 transmits an IP packet set with the virtual IP address “10.10.10.102” of the terminal 201 as a destination. The transmitted IP packet is relayed to the gateway GW-A, the core network 10, and the gateway GW-B and received by the terminal 201.
- a destination address field (hereinafter referred to as a destination address or DA (Destination Address)) in which a destination IP address is set in the packet header part, and the packet's header
- DA Destination Address
- SA Source Address
- the terminal 201 that has received the IP packet can know the key from which terminal by referring to the source address in the IP packet.
- a broadcast address prepared for broadcasting and a multicast address force prepared for mano-recast are set to the transmission destination address of the packet header.
- the broadcast address is defined as an address in which all the bits corresponding to the host address are 1. (If the network address defined in class C is 192.168.1.0, the broadcast address is 192.168.1.255. ”).
- FIG. 3 is a block diagram showing a functional configuration of the gateway GW-A.
- FIG. 4 is a block diagram showing a functional configuration of the gateway GW-B.
- FIG. 5 is a diagram showing the routing table 142 of the gateway GW-A. Note that the gateways GW-A, GW-B, GW-C, and GW-D in the first embodiment have the same functional blocks because they are the same device.
- the gateway device in the present embodiment has a packet transmission / reception unit 131.
- group member list (Local ⁇ Global) management unit 132 (Corresponding to the forwarding unit and virtual packet receiving unit of the present invention), group member list (Local ⁇ Global) management unit 132, DNS processing unit 133, tunnel processing unit 134, tunnel setting management unit 1 35, NAT processing unit 136 ( (Acquisition unit, conversion unit, reception unit, packet conversion unit, transmission unit, virtual address extraction unit, virtual address acquisition unit, packet group acquisition unit, and group determination unit), routing processing unit 137, routing setting management 138, a routing table 142, and a group menolist (Global ⁇ Local) management unit 143 shown in FIG. That is, the gateway in this embodiment is configured by the configuration shown in FIG. 3 and the group member list (Global ⁇ Local) management unit 143 of FIG.
- each functional unit will be described. In the following description, the case where the gateway GW-B has the group member list (Global ⁇ Local) management unit 143 will be described as an example, and the case where the gateway GW-A has the other functional units will
- the group menolist (Local ⁇ Global) management unit 132 is a functional unit that manages various information about each terminal in the local network A managed (connected) by the gateway GW-A.
- the group mennolist (Local ⁇ Global) management unit 132 is used to relay an IP packet transmitted by a terminal in the local network A to another local network B-D.
- the group member list management unit 132 has a local list 140 and a global list 141.
- Local list 140 is a list of information about each terminal in local network A.
- the local list 140 holds the following information for each terminal.
- ⁇ Real IP address field The IP address actually set in the terminal.
- ⁇ Affiliation G field Group to which the terminal belongs.
- 'Broadcast Virtual Multicast Field Virtual multicast address used when forwarding a broadcast packet transmitted from a terminal in local network A to another gateway.
- the local list 140 holds information for each terminal in units of groups to which the terminal belongs. If a terminal belongs to more than one group, there will be more than one list in the role list 140 indicating the same terminal.
- the global list 141 holds information on terminals in other local networks (local networks, C and D) as transmission destinations, information on broadcast packets transmitted by terminals in the local network, and the like. That is, the Grono list 141 holds the following information in units of transmission destinations that can be designated by each terminal in the local network.
- DA-DNS Disposination Address-Domain Name System
- name field a management name composed of the host name and group name of the destination terminal.
- the host name and group name of the terminal are separated by “. (Period)” (for example, video.gl shown in FIG. 3).
- the DNS name is not limited to this embodiment, but should be managed so that the host name and the group name can be distinguished.
- ⁇ LOCAL-DA (Destination Address) field A destination virtual IP address that can be specified by each terminal in the local network A. It also includes the destination IP address for broadcast packets.
- Packet type field The packet type of the data packet specifying the destination virtual IP address. There are two types for broadcast communication (Unicast shown in Fig. 3) and broadcast communication (Broadcast shown in Fig. 3).
- ⁇ Affiliation G field Group information to which the above DNS name and destination specified address belong News.
- the group member list (Global ⁇ Local) management unit 143 is a functional unit that manages various types of information regarding each terminal in the local network managed (connected) by the gateway.
- the group mennolist (Global ⁇ Local) management unit 143 is used when a packet relayed from another gateway is relayed to a local network managed by itself.
- the group men list (Global ⁇ Local) management unit 143 has a local list 144.
- the local list 144 is a list of information regarding each terminal in the local network.
- the local list 144 holds the following information for each terminal.
- ⁇ Real IP address field IP address actually set in the terminal.
- ⁇ Affiliation G field Group to which the terminal belongs.
- the local list 144 holds information for each terminal in units of groups to which the terminal belongs. If a terminal belongs to more than one group, there will be more than one list in the role list 140 indicating the same terminal.
- the DNS processing unit 133 refers to the global list 141 of the group mennolist (Local ⁇ Global) management unit 132, and from the DNS name, specifies a destination IP address corresponding to the DNS name, and vice versa. Get the DNS name corresponding to the address.
- the DNS name here is a management name that combines the host name assigned to each terminal and the group name to which the terminal belongs.
- the management name “video.gl” shown in FIG. 3 is a combination of “video” that is the host name of the terminal and “gl” that is the group name to which the terminal belongs.
- the DNS name includes a name given for each broadcast address.
- the DNS name “Local—RAB” shown in FIG. 3 is for broadcasting. If each terminal wants to send a packet to all groups to which it belongs, it should ask the gateway GW-A for the DNS name “Local-RABJ! To know the corresponding broadcast address "192.168.0.255"
- the packet transmitting / receiving unit 131 is a functional unit that receives an IP packet from the core network 10 or transmits an IP packet from a terminal in the local network A to the core network 10.
- the packet transmission / reception unit 131 requests processing from another functional unit for each type of received IP packet.
- the packet transmission / reception unit 131 determines whether the received packet is an IP tunnel packet addressed to itself or a control IP packet addressed to itself. As a result, when it is determined that the port number is an IP port number (or protocol number) for the IP tunnel, the received IP packet is passed to the tunnel processing unit 134.
- the tunnel setting management unit 135 performs processing related to IP tunneling between gateways. When a new opposing gateway is set in the routing table 142, the tunnel setting management unit 135 establishes an IP tunnel with the opposing gateway. Conversely, when the opposite gateway set in the routing table 142 is deleted, the tunnel processing unit 134 deletes the constructed IP tunnel. The tunnel setting management unit 135 terminates the constructed IP tunnel.
- the tunnel processing unit 134 is a functional unit that extracts IP packets from data transmitted using the IP tunnel constructed by the tunnel setting management unit 135. For example, when IPSec is used as the IP tunneling technology, the tunnel processing unit 134 decrypts the encryption and extracts a desired IP packet. The IP bucket extracted by the tunnel processing unit 134 is passed to the routing processing unit 137.
- the tunnel processing unit 134 when the tunnel processing unit 134 receives the forwarding gateway information and the IP packet from the routing processing unit 137, the tunneling processing unit 134 transmits the IP packet using an IP tunnel established between the forwarding processing gateway. Therefore, the IP packet is covered (header addition etc.). The processed IP packet is transferred to the packet transmitting / receiving unit 131 and transmitted.
- the routing table 142 is a table used by the routing processing unit 137 to determine to which other gateway the received IP packet should be forwarded.
- the routing table 142 of the gateway GW-A has the following information as shown in FIG.
- ⁇ Input port field Whether the received IP packet is a packet from the local network A (LOCAL shown in FIG. 4) or whether it is a packet received from another gateway via the core network 10 ( GLOBAL side tunnel port).
- Destination address field Indicates the destination IP address specified as the destination of the received IP packet.
- ⁇ Output port field When the input port of the received IP packet is LOCAL, it is information indicating the opposite gateway to which the IP packet should be transferred.
- the routing processing unit 137 is a functional unit that determines whether the received IP packet is transferred into the local network A or to another gateway.
- the routing processing unit 137 refers to the routing table 142 in making the determination. For example, when the IP packet is a packet passed from the tunnel processing unit 134, the routing processing unit 137 has the input port field as the destination gateway and the destination address field as the IP packet from the routing table 142. Search for a record that has a destination IP address of. If the searched record exists as a result of the search, the routing processing unit 137 decides to transfer a copy of the IP packet to the gateway set in the output port field of the record.
- the routing processing unit 137 when the IP packet is a packet received from the local network, the routing processing unit 137 indicates that the input port field is LOCAL from the routing table 142 and the destination address field is the IP address. Searches for records that are packet destination IP addresses. If the searched record exists as a result of the search, the routing processing unit 137 displays the gate set in the output port field of the record. Decide to transfer the IP packet to the way. In this case, the routing processing unit 137 passes the gateway information set in the output port field of the retrieved record to the tunnel processing unit 134 together with the IP packet.
- the NAT processing unit 136 is a functional unit having a NAT (Network Address Translation) function for converting a destination IP address or a source IP address of an IP packet, and a filtering function of the IP packet.
- NAT Network Address Translation
- the NAT processing unit 136 performs address conversion processing according to the transfer direction of the IP packet.
- IP packet received from the tunnel processing unit 134 IP packet from the core network 10
- the NAT processing unit 136 refers to the local list 144 and sends the destination address of the IP packet. Convert (virtual IP address is set) to real IP address.
- the NAT processing unit 136 rewrites the destination address and the source address of the IP packet.
- the NAT processing unit 136 determines from the transmission destination address and the transmission source address of the received IP packet whether or not the IP packet is a packet that can be transferred. That is, the NAT processing unit 136 refers to the group member list management unit 132 based on the extracted address, and determines whether or not the transmission source IP address and the transmission destination IP address belong to the same group. Determine if it is a packet.
- this gateway is divided into a transfer operation when receiving a terminal power broadcast packet in the local network managed by itself and an operation when exchanging data between the gateways. After that, the detailed operation flow is explained.
- FIG. 6 is a diagram showing packet transfer when the gateway GW-A receives a broadcast packet from the terminal 101 in the local network A.
- Gateway GW—A receives broadcast packet 610 (destination address “192.168.0.255”, source address “192.168.0.5”) transmitted by terminal 101 (real IP address “192.168.0.5”). Then, the destination address “192.168.0.255” and the source address “192.168.0.5” of the packet are extracted.
- gateway GW-A determines whether the packet should be forwarded to the opposite gateway (in the direction of core network 10). When it is determined that the packet should be transferred, the gateway GW-A converts the destination address and source address of the packet into a virtual IP address.
- the virtual IP address to be converted is an address corresponding to the transfer destination group of the packet. In the example of FIG. 6, the broadcast address “192.168.0.255” is converted to the virtual multicast address “230.0.0.1”. Further, the source address “192.168.0.5” is converted to the virtual IP address “10.20.20.10” indicating the terminal 101 in the target group.
- the packet 611 thus address-translated is transferred to the gateway GW-B via the IP tunnel.
- the gateway GW-B When receiving the packet 611 transferred from the gateway GW-A, the gateway GW-B extracts the transmission destination address “230.0.0.1” and the transmission source address “10.20.20.10” of the packet. Gateway GW-B determines whether or not the packet should be transferred to local network B based on the extracted destination address and source address. If it is determined that the packet should be transferred, Gateway GW-B converts the destination address of the packet from the virtual IP address to the actual broadcast address “192.150.0.255” corresponding to local network B. The packet 612 whose address has been converted in this way is transmitted to the local network B and received by the terminal group (terminals 201 to 204) corresponding to the broadcast address.
- the gateway GW—A, GW—B, GW—C, and GW—D each forward a broadcast packet of local network power managed by the gateway GW to another network
- the gateway GW—A, GW—B, GW—C, and GW—D Forward to another gateway.
- IP tunneling technology is used for communication between the gateways. Examples of the IP tunneling technology include PPTP (Point to Point Tunneling Protocol) and I PSec (lP Security Protocol). In this way, by using the IP tunneling technology for communication between gateways, even when the core network 10 is a public communication network such as the Internet, it is possible to compensate for high security and communication.
- a terminal for example, the terminal 101
- the gateway GW-A communicates with the gateway GW-B.
- the routing processing unit 137 of each gateway acts on the packet transfer between the gateways.
- the routing processing unit 137 refers to the routing table 142 and determines whether or not the forwarded packet (a virtual multicast address is designated as a transmission destination) should be further forwarded to another gateway. If it is determined that the packet should be forwarded, a copy of the packet is forwarded using the IP tunnel with the opposite gateway set in the routing table 142. Using a copy is also a force that needs to be transferred within the local network.
- FIG. Fig. 7 is a diagram showing the packet processing flow of this gateway when a broadcast packet is transferred to the core network with local network power.
- the NAT processing unit 136 of the gateway GW—A transmits a broadcast packet (a destination address “192.168.0.255”, a source address “ 192.168.0.5 ”) is received (S701).
- the NAT processing unit 136 acquires the transmission destination address “192.168.0.255” and the transmission source address “192.168.0.5” of the packet.
- the NAT processing unit 136 searches for a record in which the acquired transmission destination address (broadcast address) “192.168.0.255” is set in the transmission destination designation address field of the global list 141 (S702). .
- the NAT processing unit 136 extracts the information set in the group field of the corresponding record (S703). In this case, since “ALL” is extracted as the information set in the belonging group field, the NAT processing unit 136 knows that the broadcast packet should be transferred to all groups. Note that if there is no corresponding record as a result of searching the global list 141 (S702; NO), the NAT processing unit 136 performs normal packet transfer processing (S709). Normal packet transfer means packet transfer that is not packet transfer with grouping according to the present invention.
- the NAT processing unit 136 sets the acquired source address “192.168.0.5” and belonging group information in the real IP address field and the belonging group field of the local list 140, respectively.
- a record is searched (S704).
- the NAT processing unit 136 determines that the broadcast packet should be transferred, and the virtual IP address is determined from the corresponding record. And a broadcast virtual multicast address is acquired.
- the group information acquired earlier is “ALL”, two records with “192.168.0.5” set in the real IP address field of the local list 140 are extracted.
- the virtual IP address “10.20.20.10” and broadcast virtual multicast address “230.0.0.1” in group 1 (G1) and the virtual IP address “10.15.8.7” in group 2 (G2) And the broadcast virtual multicast address “230.0.0.2” is acquired.
- the NAT processing unit 136 belongs to a group that can be transmitted by the terminal that is the transmission source of the packet.
- the broadcast packet is discarded (S708).
- the broadcast packet is transferred to each of the acquired two groups. Therefore, the NAT processing unit 136 generates a copy of the received broadcast packet.
- the NAT processing unit 136 uses one of the generated broadcast packets for group 1 and the other for group 2. Then, the NAT processing unit 136 converts the transmission destination address of the group 1 packet to “230.0.0.1”, and converts the transmission source address to “10.20.20.10”. Similarly, the NAT processing unit 136 converts the transmission destination address of the packet for group 2 to “230.0.0.2” and converts the transmission source address to “10.15.8.7”.
- the NAT processing unit 136 passes the address-converted group 1 packet and group 2 packet to the routing processing unit 137, respectively.
- the routing processing unit 137 extracts a transmission destination address from the delivered IP packet. Taking the group 1 packet as an example, “230.0.0.1” is acquired as the destination address.
- the routing processing unit 137 searches the routing table 142 for a record whose input port field is LOCAL and whose destination address field is “230.0.0.1”.
- the routing processing unit 137 passes the opposite gateway information (gateway GW-B) set in the output port field of the retrieved record and the packet for group 1 to the tunnel processing unit 134.
- the group 2 packet is processed in the same way.
- the tunnel processing unit 134 receives the gateway GW indicated by the received opposite gateway information.
- the packet for the group 1 is edited and passed to the packet transmitting / receiving unit 131.
- an IP tunnel is established between the gateway GW-B and the gateway GW-A by the tunnel setting management unit 13 5! The same processing is performed for group 2 packets.
- the packet transmitting / receiving unit 131 transmits the passed packet (for group 1 and group 2) toward the core network 10 (S707).
- FIG. Fig. 8 is a diagram showing the packet processing flow of this gateway when forwarding packets with core network power to the local network.
- the following shows a packet for group 1 (virtual multicast packet (destination address “230.0.0.1”, source address) sent by gateway GW-A described above. This is explained based on the operation when the gateway GW-B receives the service “10.20.20.10”)).
- the packet transmitting / receiving unit 131 of the gateway GW-B receives the virtual multicast packet (destination address “230.0.0.1”, source address “10.20.20.10”) from the opposite gateway GW-A (S801). .
- the packet transmitting / receiving unit 131 knows that the packet is a packet using an IP tunnel from the opposite gateway GWA, the packet transmitting / receiving unit 131 passes the packet to the tunnel processing unit 134.
- Tunnel processing unit 134 extracts a desired IP packet from a packet transferred using the IP tunnel, and extracts the extracted packet and counter gateway information (gateway GW— A) is passed to the routing processing unit 137.
- the routing processing unit 137 passes the passed IP packet to the NAT processing unit 136 as it is. On the other hand, the routing processing unit 137 determines whether to transfer the transferred IP packet to the other opposing gateways GW-C and GW-D. In this determination, the routing processing unit 137 extracts the transmission destination address “230.0.0.1” from the IP packet. The routing processing unit 137 searches the routing table 142 for a record whose input port field is gateway GW-A and whose destination address field is “230.0.0.1”. If there is a corresponding record as a result of the search, the routing processing unit 137 sends the opposite gateway information set in the output port field of the corresponding record and a copy of the IP packet to the tunnel processing unit 134. hand over. As a result, the IP packet is forwarded to another gateway.
- the NAT processing unit 136 acquires the transmission destination address "230.0.0.1" of the packet.
- the NAT processing unit 136 searches for a record in which the acquired transmission destination address “230.0.0.1” is set in the virtual IP address field of the local list 144 (S802).
- the NAT processing unit 136 determines that the packet should be transferred, and enters the real IP address field of the corresponding record. Get the set actual broadcast address “192.150.0.255”.
- the NAT processing unit 136 discards the packet (S805).
- the NAT processing unit 136 converts the destination address of the packet to “192.150.0.255” (S803).
- the NAT processing unit 136 forwards the packet with the translated address in the direction of the local network B (S804).
- the broadcast packet transmitted by the terminal 101 is transferred to all groups to which the terminal 101 belongs.
- the NAT processing unit 136 performs NAT processing at the time of this transfer.
- the gateway replaces the transmission source address and transmission destination address (broadcast address) with the virtual IP address and virtual multicast address managed for each transfer destination group for the broadcast packet from terminal 101. ,Send.
- the gateway when receiving an address-substituted packet, replaces the destination address of the packet with the actual broadcast address corresponding to the virtual multicast address set in the received packet, and forwards the packet. To do.
- the gateway according to the first embodiment can eliminate the complexity of address management in a large-scale network system in which only V and virtual IP addresses are managed in each local network. .
- the NAT processing unit 136 of the gateway knows all the groups to which the terminal 101 belongs by referring to the global list 141 and the local list 140, and Broadcast packets are forwarded to the terminals that are members of all groups.
- each terminal that wants to transmit a broadcast packet broadcasts the packet to all members of the group to which it belongs without being aware of where on the network the terminal group that is a member of the group to which it belongs. Can be sent.
- the NAT processing unit 136 of the gateway when receiving the broadcast packet from the terminal, does not transfer the broadcast packet to the group if the terminal does not belong. Furthermore, if the terminal does not belong to any group, the broadcast packet is not transferred.
- the gateway refers to the local list 144 and sends the packet. If the virtual multicast address set as the destination address does not exist in the list, the packet is discarded.
- this gateway can achieve high-security intra-group broadcast in a closed network in which terminals are grouped.
- the gateway in the first embodiment converts a broadcast packet from the local network into a virtual multicast packet and forwards it to another gateway.
- an IP tunnel constructed between the gateways is used, and a routing table 142 in each gateway is used.
- the transfer method according to the network form between the gateways can be taken by changing the setting of the routing table 142 in each gateway. That is, one gateway power When transferring the packet to other gateways, one gateway power also passes through other gateways without establishing a connection such as an IP tunnel between all other gateways. Finally, the packet can be transferred to all gateways.
- the gateway device according to the second embodiment of the present invention will be described below.
- the gateway device in the first embodiment described above has each function for realizing broadcast in a network in which each terminal is grouped.
- a gateway device that realizes intra-group multicast in addition to the broadcast will be described.
- the network configuration and address form are the same as in the first embodiment shown in FIG.
- FIG. 9 is a block diagram showing a functional configuration of the gateway GW-A in the second embodiment.
- FIG. 10 is a block diagram showing a functional configuration of the gateway GW-B in the second embodiment.
- FIG. 11 is a diagram showing the routing table 142 of the gateway GW-A in the second embodiment.
- the gateway in this state also includes the configuration shown in FIG. 9 and the group member list (Global ⁇ Local) management unit 143 shown in FIG.
- gateway GW-A is explained as an example. In the following description, the description of the same function as that of the first embodiment is omitted for each functional unit.
- the local lists 140 and 144 have the same configuration as that of the first embodiment, but as data to be held, a record in which a multicast address is set in the virtual IP address field is held. This is a record used to convert a virtual multicast address to a real multicast address.
- a virtual multicast field is added to the global list 141 in addition to the configuration of the first embodiment.
- the global list 141 also holds information about multicast packets transmitted by terminals in the local network. For example, “voMultil.gl” and “voMulti2.gl” set in the DA-DNS field of the Grono list 141 shown in FIG. 9 are for multicast.
- the DNS processing unit 133 when the DNS processing unit 133 is inquired about the terminal power DNS name and the DNS name is multicast, it returns a corresponding multicast address. According to the example in Fig. 9, when the DNS name “voMultil. Gl” is queried from the terminal, the corresponding multicast address “231.10.10.1” is returned.
- the routing table 142 holds information related to the routing of multicast packets in addition to the information held in the first embodiment.
- a record in which “230.0.10.1” and “230.0.10.2” are set in the transmission destination address field is information about the multicast packet.
- FIG. 12 is a diagram showing packet transfer when the gateway GW-A receives the multicast packet for the terminal 101 in the local network A as well.
- Gateway GW—A receives multicast packet 1210 (destination address “231.10.10.1”, source address “192.168.0.5”) sent by terminal 101 (real IP address “192.168.0.5”) Then, the destination address “231.10.10.1” and the source address “192.168.0.5” of the packet are extracted.
- gateway GW-A determines whether or not the packet should be forwarded to the opposite gateway (core network 10 direction). When it is determined that the packet should be transferred, the gateway GW-A converts the destination address and source address of the packet into a virtual IP address.
- the virtual IP address to be converted is an address corresponding to the transfer destination group of the packet. In the example of FIG. 12, the multicast address “231.10.10.1” is converted to the virtual multicast address “230.0.10.1”. Further, the source address “192.168.0.5” is converted to the virtual IP address “10.20.20.10” indicating the terminal 101 in the target group.
- the packet 1211 whose address is converted in this way is forwarded to the gateway GW-B by the IP tunnel.
- the gateway GW-B Upon receiving the packet 1211 transferred from the gateway GW-A, the gateway GW-B receives the packet destination address "230.0.10.1" and the source address "
- Gateway GW-B determines whether or not the packet should be transferred into local network B based on the extracted destination address and source address. If gateway GW-B determines that the packet should be forwarded, The destination address of the packet is converted from the virtual multicast address to the actual multicast address “232.10.10.1” corresponding to local network B. The packet 1212 whose address has been converted in this way is transmitted to the local network B and is received by the terminal group (terminals 201 and 202) corresponding to the converted multicast address.
- FIG. 13 is a diagram showing a packet processing flow of this gateway when a multicast packet is transferred to the core network with the local network power.
- the NAT processing unit 136 of the gateway GW—A sends a multicast packet (the destination address “231.10.10.1”, the source address “
- the NAT processing unit 136 extracts the transmission destination address “231.10.10.1” and the transmission source address “192.168.0.5” from the packet.
- the NAT processing unit 136 searches for a record in which the acquired destination address (multicast address) “231.10.10.1” is set in the LOCAL—DA (destination specified address) field of the global list 141. (S1302).
- the NAT processing unit 136 acquires the packet type set in the packet type field of the corresponding record.
- the NAT processing unit 136 sets the information “G1” set in the belonging group field of the corresponding record and the information “230.0” set in the virtual multicast address field. 10.1 "is extracted (S1304). In this case, since “G1” is extracted as the information set in the belonging group field, the NAT processing unit 136 knows that the multicast packet should be transferred to the group 1 (G1). Note that the NAT processing unit 136 performs normal packet transfer processing (S1311) when there is no corresponding record as a result of searching the glow list 141 (S1302; NO). Normal packet transfer means packet transfer, not packet transfer with grouping according to the present invention. The Also, when the packet type of the corresponding record is multicast or broadcast
- a transfer process corresponding to each type is performed (S1305).
- the broadcast transfer process described in the first embodiment is performed.
- the NAT processing unit 136 sets the acquired source address "192.168.0.5" and affiliated loop information "G1" in the real IP address field and the affiliated group field of the local list 140, respectively. Search for a record to be beaten (S 1306). As a result, if the corresponding record exists in the local list 140 (S1307; YES), the NAT processing unit 136 determines that the multicast packet should be transferred, and the corresponding record docker also indicates the terminal 101. Extract the virtual IP address.
- the NAT processing unit 136 searches the local list 140 and there is no corresponding record (S1307; NO), the NAT processing unit 136 belongs to a duplex that can be transmitted by the terminal that is the transmission source of the packet.
- the multicast packet is discarded (S1310
- the NAT processing unit 136 sets the destination address of this packet to the virtual multicast address “230.0.10.1” previously extracted from the global list 141. And the source address is converted to “10.20.20.10J (S1308). The NAT processing unit 136 passes the packet with the converted address to the routing processing unit 137.
- the routing processing unit 137 extracts the transmission destination address from the passed packet. Here, “230.0.10.1” is acquired as the destination address.
- the routing processing unit 137 searches the routing table 142 shown in FIG. 11 for a record having the input port field force LOCAL and the destination address field “230.0.10.1”.
- the routing processing unit 137 passes the counter gateway information (gateway GW-B) set in the output port field of the retrieved record and the packet to the tunnel processing unit 134.
- the tunnel processing unit 134 transmits the packet for the group 1 using the IP tunnel constructed with the gateway GW B indicated by the passed opposite gateway information. Is edited and passed to the packet transmission / reception unit 131. At this time, an IP tunnel is established between the gateway GW-B and the gateway GW-A by the tunnel setting management unit 135.
- the packet transmitting / receiving unit 131 transmits the passed packet (for group 1) toward the core network 10 (S 1309).
- FIG. 14 is a diagram showing a packet processing flow of the gateway when a packet received by the core network is transferred to the local network.
- gateway GW-B receives the packet for group 1 (virtual multicast packet (destination address “230.0.10.1”, source address “10.20.20.10”)) sent by gateway GW—A mentioned above An explanation will be given based on the operation performed.
- the packet transmission / reception unit 131 of the gateway GW-B receives the virtual multicast packet (destination address “230.0.10.1”, source address “10.20.20.10”) from the opposite gateway GW-A (S1401). .
- the packet transmission / reception unit 131 knows that the packet is a packet using the IP tunnel from the opposite gateway GW-A, the packet transmission / reception unit 131 passes the packet to the tunnel processing unit 134.
- Tunnel processing unit 134 extracts a desired IP packet from a packet transferred using the IP tunnel, and extracts the extracted packet and counter gateway information (gateway GW— A) is passed to the routing processing unit 137.
- the routing processing unit 137 passes the passed IP packet to the NAT processing unit 136 as it is. On the other hand, the routing processing unit 137 determines whether the transferred IP packet should be transferred to the other opposing gateways GW-C and GW-D. In this determination, the routing processing unit 137 extracts the transmission destination address “230.0.10.1” from the IP packet. The routing processing unit 137 searches the routing table 142 for a record whose input port field is the gateway GW-A and whose destination address field is “230.0.10.1”. Inspection If there is a corresponding record as a result of the search, the routing processing unit 137 passes the opposite gateway information set in the output port field of the corresponding record and a copy of the IP packet to the tunnel processing unit 134. . As a result, the IP packet is forwarded to another gateway.
- the NAT processing unit 136 that has received the IP packet from the tunnel processing unit 134 extracts the destination address “230.0.10.1” from the packet.
- the NAT processing unit 136 searches for a record in which the acquired destination address “230.0.10.1” is set in the virtual IP address field of the local list 144 (S1402). As a result, if the corresponding record exists in the local list 144 (S1402; YES), the NAT processing unit 136 determines that the packet should be transferred, and is set in the real IP address field of the corresponding record. The actual multicast address “232.10.10.1” is acquired. Note that if there is no corresponding record as a result of searching the local list 144 (S1402; NO), the NAT processing unit 136 discards the packet (S1405).
- the NAT processing unit 136 converts the transmission destination address of the packet to “232.10.10.1” (S 1403).
- the NAT processing unit 136 forwards the packet with the translated address in the direction of the local network B (S1404).
- the multicast packet transmitted from the terminal 101 is transferred to a terminal group that is a member of the group corresponding to the multicast address.
- the gateway performs NAT processing by the NAT processing unit 136 at the time of this transfer.
- the operation and effect of this gateway relating to this NAT processing are the same as in the first embodiment.
- the NAT processing unit 136 of the gateway When the NAT processing unit 136 of the gateway receives a multicast packet from the terminal 101, the NAT processing unit 136 refers to the global list 141 and the local list 140, and from the multicast address set in the multicast packet, Knows the group to which the multicast address belongs and forwards multicast packets to the terminals belonging to that group. [0141] Thus, each terminal that wants to transmit a multicast packet sets a multicast address corresponding to the group to which the multicast packet is to be sent and transmits the packet, thereby transmitting the multicast packet to the members belonging to the group. can do.
- the NAT processing unit 136 of the gateway when receiving the multicast packet from the terminal, does not transfer the multicast packet to the group if the terminal does not belong.
- this gateway refers to the local list 144. If the virtual multicast address set in the destination address of the packet does not exist in the list, the gateway Is discarded.
- this gateway can realize intra-group multicast with high security in a closed network in which terminals are grouped.
- the gateway in the first embodiment converts a multicast packet from within the local network into a virtual multicast packet and forwards it to another gateway.
- an IP tunnel constructed between the gateways is used, and a routing table 142 in each gateway is used.
- the gateway device according to the third embodiment of the present invention will be described below.
- the gateway devices in the first embodiment and the second embodiment described above have functions for realizing broadcast and multicast in a network in which each terminal is grouped.
- the local lists 140 and 144, the global list 141, and the list used for realizing the broadcast and multicast are related.
- a gateway device having inter-gateway synchronization processing in the setting table 142 will be described.
- the network configuration and address form are the same as in the first embodiment shown in FIG.
- the gateway device has a setting information management unit 145 (corresponding to the information transmission unit and the information update unit of the present invention), and otherwise the first embodiment and the second embodiment. Similar functional components are configured. However, the operation in each functional unit is slightly different.
- the setting information management unit 145 and functional units that operate differently from the first embodiment and the second embodiment will be described with reference to FIG.
- FIG. 15 is a block diagram showing a part of the functional configuration of the gateway GW-A in the third embodiment. Note that functional units not shown in FIG. 15 are the same as those in the first embodiment and the second embodiment.
- the gateways GW-A, GW-B, GW-C, and GW-D are the same device and have the same functional blocks.
- gateway GW-A is taken as an example.
- description is abbreviate
- the packet transmission / reception unit 131 transmits / receives a packet for inter-gateway synchronization processing.
- the packet transmission / reception unit 131 passes the packet to the tunnel processing unit 134. Also, when receiving a packet for inter-gateway synchronization processing from the tunnel processing unit 134, the packet is transferred to another gateway.
- the tunnel processing unit 134 checks the IP packet in order to transmit each piece of information notified from the setting information management unit 145 to another gateway as a transmission destination using the IP tunnel (such as adding a header). ). The processed IP packet is transferred to the packet transmitting / receiving unit 131 and transmitted. Further, the tunnel processing unit 134 extracts a desired IP packet from the packet for the inter-gateway synchronization processing that has also been transmitted by other gateways, and passes it to the setting information management unit 145.
- the setting information management unit 145 includes a group member list (Local ⁇ Global) management unit 132 and a group member list (Global ⁇ Local) management unit.
- 143 is a functional unit that updates the data held by 143.
- the setting information management unit 145 refers to the data held by the group member list (Local ⁇ Global) management unit 132 and the group mennolist (Global ⁇ Local) management unit 143 and desires to newly join the group.
- Another local network terminal determines a new virtual IP address so that it does not overlap with the IP address already used.
- the setting information management unit 145 packetizes the information about the terminals in order to send back information on the terminals related to the group to the gateway. To the tunnel processing unit 1 34.
- the setting information management unit 145 sets the virtual information for group 1 of the terminal. Determine the IP address and register it in your global list 141. The determined virtual IP address is transmitted to other gateways GW-A and GW-C. In addition, in order to notify the gateway GW-C of information related to the terminal group that is a member of the group 1, a packet for transmitting the information is created with reference to the geno list 141. In addition, when the setting information management unit 145 requests group registration of a terminal in the local network managed by itself to another gateway, the setting information management unit 145 obtains the virtual address information of the terminal to which other gateway power is also sent. Updates its own local lists 140 and 144.
- FIG. 16 is a diagram showing an inter-gateway synchronization sequence in the third embodiment.
- a group 1 virtual network is constructed between the gateway GW-A and the gateway GW-B as shown in FIG. 2, and the terminals in the local network C managed by the gateway GW-C are used.
- PDA joins group 1 Will be described as an example.
- the gateway GW-C first establishes an IP tunnel with the gateway GW-B in order to join the group 1 (S1602).
- Gateway GW-C and Gateway GW-B perform inter-gateway authentication and the like.
- gateway GW-C sends a host (terminal) list request
- the gateway GW-B that has received the request refers to the local list 140 and the global list 141, and gateways information on terminals in the local network B managed by itself and information on terminals in other networks. Reply to GW—C
- the gateway GW-C that has received the information on the plurality of terminals updates its global list 141 based on the information.
- the gateway GW-C transmits a group registration request for the terminal that is desired to participate in the group 1 to the gateway GW-B (S1605). In this transmission, the gateway GW-C may send it including the DNS name of the terminal!
- the gateway GW-B Upon receiving the group registration request from the gateway GW-C, the gateway GW-B synchronizes information on the newly participating terminals with the gateway GW-A and GW-C (S1606). .
- the gateway GW-B may determine the virtual IP address for the terminal in Group 1 so that it does not overlap with the virtual IP address already used for the newly participating terminal! ⁇ .
- the gateway GW-B transmits the determined virtual IP address to the gateway GW-A and the gateway GW-C.
- the duplication information, virtual IP address information, etc. regarding the newly participating terminals are registered in the global list 141 of the gateway GW-B and GW-A.
- the gateway GW-C updates the local lists 140 and 144 with the information.
- information regarding virtual multicast communication and virtual broadcast communication is synchronized with the gateways GW-A, GW-B, and GW-C (S1607).
- information such as the virtual multicast address for broadcast related to the broadcast packet described in the first embodiment and the virtual multicast address for the multicast packet described in the second embodiment is exchanged between the gateways.
- Information is synchronized.
- the gateway GW-B newly determines the broadcast virtual multicast address and multicast virtual multicast address to be used for communication between the gateways GW-C, and the gateway GW-C and the gateway GW-C and GW—You can notify A!
- routing table 142 is synchronized between the gateways (S1608).
- This synchronization is a routing table setting process in the multicast routing protocol for the IP tunnel used in the inter-gateway communication described in the first embodiment and the second embodiment.
- gateway when other gateways are requested to register a group of terminals in the local network managed by the gateway, address information and the like regarding the terminal group that is a member of the target group is transmitted between the gateways. Communicate in.
- the gateway according to the present invention automatically synchronizes the address information and the like of the group of terminals in a network in which a plurality of terminals exist, so that a complicated operation of address management does not occur.
- address management is performed automatically, and automatic numbering is performed so that there are no duplicates, so that setting errors such as duplicate address settings can be eliminated. Therefore, efficient network operation is possible.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Multimedia (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2007506925A JP4302170B2 (ja) | 2005-03-04 | 2005-03-04 | パケット中継装置 |
PCT/JP2005/003788 WO2006095391A1 (ja) | 2005-03-04 | 2005-03-04 | パケット中継装置 |
EP20050720060 EP1855420B1 (en) | 2005-03-04 | 2005-03-04 | Packet relay device |
CN2005800489549A CN101138205B (zh) | 2005-03-04 | 2005-03-04 | 数据包中继装置 |
US11/838,398 US7894428B2 (en) | 2005-03-04 | 2007-08-14 | Packet relay device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2005/003788 WO2006095391A1 (ja) | 2005-03-04 | 2005-03-04 | パケット中継装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/838,398 Continuation US7894428B2 (en) | 2005-03-04 | 2007-08-14 | Packet relay device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006095391A1 true WO2006095391A1 (ja) | 2006-09-14 |
Family
ID=36953002
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/003788 WO2006095391A1 (ja) | 2005-03-04 | 2005-03-04 | パケット中継装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US7894428B2 (ja) |
EP (1) | EP1855420B1 (ja) |
JP (1) | JP4302170B2 (ja) |
CN (1) | CN101138205B (ja) |
WO (1) | WO2006095391A1 (ja) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008092170A (ja) * | 2006-09-29 | 2008-04-17 | Fujitsu Ltd | パケット中継装置 |
JP2008182356A (ja) * | 2007-01-23 | 2008-08-07 | Toshiba Corp | 中継装置及び中継方法 |
JP2011171874A (ja) * | 2010-02-17 | 2011-09-01 | Fujitsu Ltd | 通信処理のためのプログラム、コンピュータ及び方法 |
JP2013504958A (ja) * | 2009-09-16 | 2013-02-07 | 中興通訊股▲ふん▼有限公司 | マルチキャストサービスの実現方法、システム及びエッジルータ |
WO2014199924A1 (ja) * | 2013-06-10 | 2014-12-18 | 日本電気株式会社 | 制御装置、通信システム、中継装置の制御方法及びプログラム |
JP2015043559A (ja) * | 2013-08-24 | 2015-03-05 | ニシラ, インコーポレイテッド | エンドポイントにより配布されるマルチキャスト |
WO2015108106A1 (ja) * | 2014-01-16 | 2015-07-23 | 日本電気株式会社 | パケット転送装置、制御装置、通信システム、通信方法及びプログラム |
US9137052B2 (en) | 2011-08-17 | 2015-09-15 | Nicira, Inc. | Federating interconnection switching element network to two or more levels |
US9602385B2 (en) | 2013-12-18 | 2017-03-21 | Nicira, Inc. | Connectivity segment selection |
US9602392B2 (en) | 2013-12-18 | 2017-03-21 | Nicira, Inc. | Connectivity segment coloring |
US9794079B2 (en) | 2014-03-31 | 2017-10-17 | Nicira, Inc. | Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks |
US10778457B1 (en) | 2019-06-18 | 2020-09-15 | Vmware, Inc. | Traffic replication in overlay networks spanning multiple sites |
CN113238833A (zh) * | 2021-05-27 | 2021-08-10 | 安天科技集团股份有限公司 | 特征数据传输方法、装置及存储介质 |
US11784922B2 (en) | 2021-07-03 | 2023-10-10 | Vmware, Inc. | Scalable overlay multicast routing in multi-tier edge gateways |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7653044B1 (en) * | 2005-04-07 | 2010-01-26 | Marvell Israel (M.I.S.L.) Ltd. | Address scope checking for internet protocol version 6 |
EP1926285B1 (en) * | 2006-10-11 | 2011-07-13 | Murata Machinery, Ltd. | Relay server |
US8010647B2 (en) * | 2006-12-11 | 2011-08-30 | Murata Machinery, Ltd. | Relay server and relay communication system arranged to share resources between networks |
US8064362B2 (en) * | 2008-08-21 | 2011-11-22 | Cisco Technology, Inc. | Wide area network optimization proxy routing protocol |
KR20100040658A (ko) * | 2008-10-10 | 2010-04-20 | 삼성전자주식회사 | UPnP 네트워크의 원격 접속 서비스에서 아이피 주소 충돌 해결 방법 및 장치 |
US8230071B1 (en) * | 2010-06-28 | 2012-07-24 | Ncircle Network Security, Inc. | Network services platform |
US10003993B2 (en) * | 2010-10-06 | 2018-06-19 | Provenance Asset Group Llc | Subscriber handling in radio telecommunication networks |
US9787544B2 (en) * | 2010-11-12 | 2017-10-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Installation and enforcement of dynamic and static PCC rules in tunneling scenarios |
JP5682782B2 (ja) * | 2011-07-11 | 2015-03-11 | 村田機械株式会社 | 中継サーバ及び中継通信システム |
US8902891B2 (en) * | 2011-07-27 | 2014-12-02 | Hewlett-Packard Development Company, L.P. | Method of managing broadcasts and multicasts by a network device |
US10230679B1 (en) * | 2011-08-22 | 2019-03-12 | Star2Star Communications, LLC | Systems and methods for optimizing application data delivery over third party networks |
US10225094B2 (en) * | 2012-05-29 | 2019-03-05 | Futurewei Technologies, Inc. | SDN facilitated multicast in data center |
JP5949417B2 (ja) * | 2012-10-09 | 2016-07-06 | 株式会社デンソー | 中継装置 |
CN103840995B (zh) * | 2012-11-26 | 2017-10-24 | 华为技术有限公司 | Ip报文处理方法、装置及网络系统 |
US20140219156A1 (en) * | 2013-02-01 | 2014-08-07 | Thomson Licensing | Optimizing wireless local area network communications |
KR102120945B1 (ko) | 2013-03-11 | 2020-06-09 | 삼성전자주식회사 | 멀티캐스트 그룹에 속하는 멤버 노드들 간의 협력에 기반하여 데이터를 전송하는 기지국, 멤버 노드 및 그 방법들 |
US9794855B2 (en) | 2014-10-01 | 2017-10-17 | At&T Intellectual Property I, L.P. | Facilitation of geographically addressed data streaming |
US11694876B2 (en) | 2021-12-08 | 2023-07-04 | Applied Materials, Inc. | Apparatus and method for delivering a plurality of waveform signals during plasma processing |
CN114531322B (zh) * | 2022-01-06 | 2023-09-29 | 南京博联智能科技有限公司 | 一种物联网多网关数据同步的方法、系统、装置和介质 |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04120839A (ja) * | 1990-09-12 | 1992-04-21 | Hitachi Ltd | 通信網接続装置 |
JP2001230774A (ja) | 2000-02-17 | 2001-08-24 | Fujitsu Ltd | パケット変換装置およびパケット変換方法 |
WO2002098063A1 (en) | 2001-05-28 | 2002-12-05 | Zooinnet | Method and system for virtual multicast networking |
JP2004254288A (ja) * | 2003-01-29 | 2004-09-09 | Nippon Telegr & Teleph Corp <Ntt> | マルチキャストデータ通信システム及び方法、クライアント側ゲートウェイ、サーバ側ゲートウェイ、コンピュータプログラム、ならびに、コンピュータプログラムを記録した記録媒体 |
JP2004282199A (ja) | 2003-03-13 | 2004-10-07 | Internatl Business Mach Corp <Ibm> | ルータを介して接続されたサブネットワーク間のブロードキャスト |
JP2004328719A (ja) * | 2003-04-24 | 2004-11-18 | Microsoft Corp | サブネット境界を越えたサブネットブロードキャストのブリッジ |
JP2005020170A (ja) * | 2003-06-24 | 2005-01-20 | Ntt Communications Kk | データ通信システム |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US526351A (en) * | 1894-09-18 | Band-cutter and feeder | ||
US6873627B1 (en) * | 1995-01-19 | 2005-03-29 | The Fantastic Corporation | System and method for sending packets over a computer network |
US6711163B1 (en) | 1999-03-05 | 2004-03-23 | Alcatel | Data communication system with distributed multicasting |
JP2001026805A (ja) | 1999-07-10 | 2001-01-30 | Tokyo Kozai Kk | ガスタービン等で廃棄された無機質繊維フィルターの高炉溶融樋保温材としての活用法 |
JP3656134B2 (ja) | 2000-03-23 | 2005-06-08 | 日本電信電話株式会社 | Vpn選択接続ゲートウェイおよびそれによる通信方法 |
US6831917B1 (en) * | 2000-05-10 | 2004-12-14 | Cisco Technology, Inc. | Network address translation for multicast virtual sourcing |
US7130303B2 (en) * | 2001-03-15 | 2006-10-31 | Lucent Technologies Inc. | Ethernet packet encapsulation for metropolitan area ethernet networks |
US7020796B1 (en) * | 2001-07-27 | 2006-03-28 | Ciena Corporation | High availability communication system |
KR100429292B1 (ko) * | 2001-12-12 | 2004-04-29 | 주식회사 케이티프리텔 | 이동 아이피 네트워크에서 명시적 멀티캐스트 터널링서비스 방법 및 장치 |
CN1553674A (zh) * | 2003-05-26 | 2004-12-08 | 广东省电信有限公司科学技术研究院 | 宽带接入服务器获取宽带用户接入端口号的方法 |
DE60315143T2 (de) * | 2003-06-25 | 2008-04-30 | Alcatel Lucent | Verfahren und Einrichtung zur Ethernet-MAC-Adressumsetzung in Ethernet-Zugangsnetzwerken |
CN1545265A (zh) * | 2003-11-25 | 2004-11-10 | 港湾网络有限公司 | 数字用户线接入服务器设备实现虚拟媒体访问控制地址的方法 |
KR100632185B1 (ko) * | 2004-10-15 | 2006-10-11 | 한국전자통신연구원 | 광 통신 패킷 데이터 정합기능을 제공하는 홈 게이트웨이시스템 및 이를 이용한 댁내 방송서비스 제공 방법 |
JP4639152B2 (ja) * | 2006-01-20 | 2011-02-23 | 株式会社日立製作所 | 通信システム |
-
2005
- 2005-03-04 JP JP2007506925A patent/JP4302170B2/ja not_active Expired - Fee Related
- 2005-03-04 WO PCT/JP2005/003788 patent/WO2006095391A1/ja not_active Application Discontinuation
- 2005-03-04 CN CN2005800489549A patent/CN101138205B/zh not_active Expired - Fee Related
- 2005-03-04 EP EP20050720060 patent/EP1855420B1/en not_active Expired - Fee Related
-
2007
- 2007-08-14 US US11/838,398 patent/US7894428B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04120839A (ja) * | 1990-09-12 | 1992-04-21 | Hitachi Ltd | 通信網接続装置 |
JP2001230774A (ja) | 2000-02-17 | 2001-08-24 | Fujitsu Ltd | パケット変換装置およびパケット変換方法 |
WO2002098063A1 (en) | 2001-05-28 | 2002-12-05 | Zooinnet | Method and system for virtual multicast networking |
JP2004254288A (ja) * | 2003-01-29 | 2004-09-09 | Nippon Telegr & Teleph Corp <Ntt> | マルチキャストデータ通信システム及び方法、クライアント側ゲートウェイ、サーバ側ゲートウェイ、コンピュータプログラム、ならびに、コンピュータプログラムを記録した記録媒体 |
JP2004282199A (ja) | 2003-03-13 | 2004-10-07 | Internatl Business Mach Corp <Ibm> | ルータを介して接続されたサブネットワーク間のブロードキャスト |
JP2004328719A (ja) * | 2003-04-24 | 2004-11-18 | Microsoft Corp | サブネット境界を越えたサブネットブロードキャストのブリッジ |
JP2005020170A (ja) * | 2003-06-24 | 2005-01-20 | Ntt Communications Kk | データ通信システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP1855420A4 |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008092170A (ja) * | 2006-09-29 | 2008-04-17 | Fujitsu Ltd | パケット中継装置 |
JP2008182356A (ja) * | 2007-01-23 | 2008-08-07 | Toshiba Corp | 中継装置及び中継方法 |
JP2013504958A (ja) * | 2009-09-16 | 2013-02-07 | 中興通訊股▲ふん▼有限公司 | マルチキャストサービスの実現方法、システム及びエッジルータ |
JP2011171874A (ja) * | 2010-02-17 | 2011-09-01 | Fujitsu Ltd | 通信処理のためのプログラム、コンピュータ及び方法 |
US11804987B2 (en) | 2011-08-17 | 2023-10-31 | Nicira, Inc. | Flow generation from second level controller to first level controller to managed switching element |
US10931481B2 (en) | 2011-08-17 | 2021-02-23 | Nicira, Inc. | Multi-domain interconnect |
US9137052B2 (en) | 2011-08-17 | 2015-09-15 | Nicira, Inc. | Federating interconnection switching element network to two or more levels |
US9288081B2 (en) | 2011-08-17 | 2016-03-15 | Nicira, Inc. | Connecting unmanaged segmented networks by managing interconnection switching elements |
US10193708B2 (en) | 2011-08-17 | 2019-01-29 | Nicira, Inc. | Multi-domain interconnect |
US9444651B2 (en) | 2011-08-17 | 2016-09-13 | Nicira, Inc. | Flow generation from second level controller to first level controller to managed switching element |
US10091028B2 (en) | 2011-08-17 | 2018-10-02 | Nicira, Inc. | Hierarchical controller clusters for interconnecting two or more logical datapath sets |
WO2014199924A1 (ja) * | 2013-06-10 | 2014-12-18 | 日本電気株式会社 | 制御装置、通信システム、中継装置の制御方法及びプログラム |
US9887851B2 (en) | 2013-08-24 | 2018-02-06 | Nicira, Inc. | Distributed multicast by endpoints |
US10218526B2 (en) | 2013-08-24 | 2019-02-26 | Nicira, Inc. | Distributed multicast by endpoints |
JP2015043559A (ja) * | 2013-08-24 | 2015-03-05 | ニシラ, インコーポレイテッド | エンドポイントにより配布されるマルチキャスト |
US10623194B2 (en) | 2013-08-24 | 2020-04-14 | Nicira, Inc. | Distributed multicast by endpoints |
US9432204B2 (en) | 2013-08-24 | 2016-08-30 | Nicira, Inc. | Distributed multicast by endpoints |
US11310150B2 (en) | 2013-12-18 | 2022-04-19 | Nicira, Inc. | Connectivity segment coloring |
US9602392B2 (en) | 2013-12-18 | 2017-03-21 | Nicira, Inc. | Connectivity segment coloring |
US9602385B2 (en) | 2013-12-18 | 2017-03-21 | Nicira, Inc. | Connectivity segment selection |
US10154073B2 (en) | 2014-01-16 | 2018-12-11 | Nec Corporation | Packet forwarding apparatus for handling multicast packet |
JPWO2015108106A1 (ja) * | 2014-01-16 | 2017-03-23 | 日本電気株式会社 | パケット転送装置、制御装置、通信システム、通信方法及びプログラム |
US10742697B2 (en) | 2014-01-16 | 2020-08-11 | Nec Corporation | Packet forwarding apparatus for handling multicast packet |
WO2015108106A1 (ja) * | 2014-01-16 | 2015-07-23 | 日本電気株式会社 | パケット転送装置、制御装置、通信システム、通信方法及びプログラム |
JP2017212759A (ja) * | 2014-01-16 | 2017-11-30 | 日本電気株式会社 | パケット転送装置、制御装置、通信システム、通信方法及びプログラム |
US9794079B2 (en) | 2014-03-31 | 2017-10-17 | Nicira, Inc. | Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks |
US10999087B2 (en) | 2014-03-31 | 2021-05-04 | Nicira, Inc. | Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks |
US10333727B2 (en) | 2014-03-31 | 2019-06-25 | Nicira, Inc. | Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks |
US11923996B2 (en) | 2014-03-31 | 2024-03-05 | Nicira, Inc. | Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks |
US10778457B1 (en) | 2019-06-18 | 2020-09-15 | Vmware, Inc. | Traffic replication in overlay networks spanning multiple sites |
US11456888B2 (en) | 2019-06-18 | 2022-09-27 | Vmware, Inc. | Traffic replication in overlay networks spanning multiple sites |
US11784842B2 (en) | 2019-06-18 | 2023-10-10 | Vmware, Inc. | Traffic replication in overlay networks spanning multiple sites |
CN113238833A (zh) * | 2021-05-27 | 2021-08-10 | 安天科技集团股份有限公司 | 特征数据传输方法、装置及存储介质 |
CN113238833B (zh) * | 2021-05-27 | 2023-09-05 | 安天科技集团股份有限公司 | 特征数据传输方法、装置及存储介质 |
US11784922B2 (en) | 2021-07-03 | 2023-10-10 | Vmware, Inc. | Scalable overlay multicast routing in multi-tier edge gateways |
Also Published As
Publication number | Publication date |
---|---|
US20080002727A1 (en) | 2008-01-03 |
JPWO2006095391A1 (ja) | 2008-08-14 |
US7894428B2 (en) | 2011-02-22 |
EP1855420B1 (en) | 2014-01-15 |
EP1855420A4 (en) | 2011-04-20 |
CN101138205B (zh) | 2012-04-11 |
EP1855420A1 (en) | 2007-11-14 |
JP4302170B2 (ja) | 2009-07-22 |
CN101138205A (zh) | 2008-03-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4302170B2 (ja) | パケット中継装置 | |
KR100579321B1 (ko) | 가상 멀티캐스트 네트워킹 방법 및 그 시스템 | |
CA2611146C (en) | Method for data communication and system thereof | |
JP2011229180A (ja) | Zigbee/ipゲートウェイ | |
JP2004242063A (ja) | データ生成装置 | |
JP2004179811A (ja) | パケット中継装置 | |
JP4628938B2 (ja) | データ通信システム、端末装置およびvpn設定更新方法 | |
WO2017031947A1 (zh) | 向网络中发送和从网络中获取目标数据的方法和装置 | |
JP2006074132A (ja) | マルチキャスト通信方法及びゲートウェイ装置 | |
JP2006101475A (ja) | マルチキャスト制御方法、マルチキャスト制御装置、及びコンテンツ属性情報管理装置、並びにプログラム | |
JP4601704B2 (ja) | パケット中継装置 | |
JP3962343B2 (ja) | マルチキャストデータ通信システム及びその方法 | |
JP4481499B2 (ja) | 階層マルチキャスティング | |
JP4862039B2 (ja) | 接続支援サーバ、及び通信機器 | |
JP2008153766A (ja) | データ中継装置 | |
JP5495175B2 (ja) | 情報転送システム | |
KR100296138B1 (ko) | 동적 멀티케스트 트리를 통한 멀티미디어 회의 서비스 방법 | |
JP4549782B2 (ja) | マルチキャスト制御方法、マルチキャスト制御装置、及びプログラム | |
JP4355004B2 (ja) | マルチキャストデータ通信システム及びその方法 | |
JP2006135508A (ja) | マルチキャスト通信中継装置およびマルチキャスト通信中継システム | |
JP2005033555A (ja) | マルチキャスト通信システム及びルータ | |
JP2004253976A (ja) | マルチキャストデータ通信システム及びその方法 | |
JP2004056610A (ja) | ネットワーク中継装置及び中継方法、中継プログラム並びにそのプログラムを記録した記録媒体 | |
JP2003069605A (ja) | アドレス秘匿通信方法、システムおよびプライバシーゲートウェイ | |
JP2004259179A (ja) | 応答メッセージ転送方法及びシステム装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2007506925 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11838398 Country of ref document: US Ref document number: 2005720060 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580048954.9 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: RU |
|
WWP | Wipo information: published in national office |
Ref document number: 2005720060 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 11838398 Country of ref document: US |