US20020090002A1 - Multicast routing method and an apparatus for routing a multicast packet - Google Patents
Multicast routing method and an apparatus for routing a multicast packet Download PDFInfo
- Publication number
- US20020090002A1 US20020090002A1 US10/094,603 US9460302A US2002090002A1 US 20020090002 A1 US20020090002 A1 US 20020090002A1 US 9460302 A US9460302 A US 9460302A US 2002090002 A1 US2002090002 A1 US 2002090002A1
- Authority
- US
- United States
- Prior art keywords
- multicast
- ipv4
- address
- ipv6
- packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- 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
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Definitions
- the present invention relates to an IPv4-IPv6 multicast communicating method and an IPv4-IPv6 multicast communicating apparatus in a communications network system. More particularly, it relates to a method and an apparatus for implementing the multicast communication between an IPv4 terminal using IPv4 (i.e., Internet Protocol Version 4) as the communications protocol and an IPv6 terminal using IPv6 (i.e., Internet Protocol Version 6) as the communications protocol.
- IPv4 i.e., Internet Protocol Version 4
- IPv6 i.e., Internet Protocol Version 6
- FIG. 1 illustrates the configuration diagram of a converting apparatus according to a 1st embodiment of the present invention
- FIG. 2 illustrates the configuration diagram of an IPv4 unicast address table
- FIG. 3 illustrates the configuration diagram of an IPv4 multicast address table
- FIG. 4 illustrates the configuration diagram of an IPv6 unicast address table
- FIG. 5 illustrates the configuration diagram of an IPv6 multicast address table
- FIG. 6 illustrates the configuration diagram of the IP address conversion table
- FIG. 7 illustrates the configuration diagram of an IPv4 multicast membership table
- FIG. 8 illustrates the configuration diagram of an IPv6 multicast membership table
- FIG. 9 illustrates the configuration diagram of a communications network system according to the 1st embodiment of the present invention.
- FIG. 10 illustrates a flowchart in the case where an IP multicast packet broadcast (transmitted) by an IPv4 multicast server is received by an IPv6 multicast client through the converting apparatus according to the 1st embodiment of the present invention
- FIG. 11 illustrates a flowchart subsequent to the one in FIG. 10;
- FIG. 12 illustrates the configuration diagram of a communications network system according to an embodiment differing from the 1st embodiment of the present invention
- FIG. 13 illustrates an example of the hardware configuration diagram of the communicating apparatus according to the present invention.
- FIG. 14 illustrates formats of the IPv6 header and the IPv4 header.
- FIG. 1 illustrates the configuration diagram of a converting apparatus 1 a according to the 1st embodiment of the present invention.
- the converting apparatus 1 a which is positioned between an IPv4 network 101 and an IPv6 network 102 , executes the IP header conversion mutually between an IPv4 multicast packet and an IPv6 multicast packet. Based on this IP header conversion processing, the converting apparatus 1 a implements the IP multicast communication between the IPv4 terminal and the IPv6 terminal. As illustrated in FIG.
- the converting apparatus 1 a includes an IP transmitting/receiving unit 2 , a for-conversion IP address holding unit 3 , an IP address conversion information holding unit 4 , an IP multicast membership group managing unit 5 , and an IP header converting unit 6 .
- the IP transmitting/receiving unit 2 performs the transmittance/reception of the IPv4 multicast packet with the IPv4 network 101 , and the transmittance/reception of the IPv6 multicast packet with the IPv6 network 102 .
- the for-conversion IP address holding unit 3 holds an IPv4 unicast address, an IPv4 multicast address, an IPv6 unicast address, and an IPv6 multicast address, all of which are used for the IP header conversion.
- An IPv4 unicast address table 31 holds the IPv4 unicast address used for the IP header conversion.
- the IP addresses to be held by the for-conversion IP address holding unit 3 have been registered in advance in accordance with the instruction from a manager of the converting apparatus 1 a .
- the following method is also allowable: The converting apparatus performs the communication with a DHCP server so as to automatically acquire unused addresses, then holding the unused addresses into the for-conversion IP address holding unit 3 .
- An IPv4 multicast address table 32 holds the IPv4 multicast address used for the IP header conversion.
- An IPv6 unicast address table 33 holds the IPv6 unicast address used for the IP header conversion.
- An IPv6 multicast address table 34 holds the IPv6 multicast address used for the IP header conversion.
- the for-conversion IP address holding unit 3 holds and manages all of the IPv4 unicast address table 31 , the IPv4 multicast address table 32 , the IPv6 unicast address table 33 , and the IPv6 multicast address table 34 .
- the IP address conversion information holding unit 4 holds the IPv4 unicast address and the IPv6 unicast address, and the IPv4 multicast address and the IPv6 multicast address in a state of being made to correspond to each other, respectively.
- the IP address conversion information holding unit 4 converts the IPv4 multicast address into the IPv6 multicast address held in correspondence with the IPv4 multicast address.
- the IPv4 multicast address is an IPv4 transmission destination address of the IPv4 multicast packet broadcast (transmitted) by the IPv4 terminal on the IPv4 network 101 .
- the IP address conversion information holding unit 4 converts the IPv4 unicast address into the IPv6 unicast address held in correspondence with the IPv4 unicast address, the IPv4 unicast address being an IPv4 transmission source address of the above-described IPv4 multicast packet.
- the IP address conversion information holding unit 4 converts the IPv6 multicast address into the IPv4 multicast address held in correspondence with the IPv6 multicast address.
- the IPv6 multicast address is an IPv6 transmission destination address of the IPv6 multicast packet broadcast (transmitted) by the IPv6 terminal on the IPv6 network 102 .
- the IP address conversion information holding unit 4 converts the IPv6 unicast address into the IPv4 unicast address held in correspondence with the IPv6 unicast address, the IPv6 unicast address being an IPv6 transmission source address of the above-described IPv6 multicast packet.
- An IP address conversion table 41 holds the following addresses, respectively: The IPv4 transmission destination address of the IPv4 multicast packet, which has been received by the converting apparatus 1 a , and the IPv6 multicast address corresponding thereto, and the IPv4 transmission source address of the above-described IPv4 multicast packet and the IPv6 unicast address corresponding thereto. Also, the IP address conversion table 41 holds the following addresses, respectively: The IPv6 transmission destination address of the received IPv6 multicast packet and the IPv4 multicast address corresponding thereto, and the IPv6 transmission source address of the above-described IPv6 multicast packet and the IPv4 unicast address corresponding thereto.
- the IP address conversion information holding unit 4 holds and manages the above-described IP address conversion table 41 .
- the IP multicast membership group managing unit 5 performs the membership state management of the converting apparatus 1 a into an IPv4 multicast group and an IPv6 multicast group. Also, the IP multicast membership group managing unit 5 instructs the IP address conversion information holding unit 4 to register the IPv4 multicast address of the IPv4 multicast group of which the converting apparatus 1 a is a member and the IPv6 multicast address corresponding thereto, or the IPv6 multicast address of the IPv6 multicast group of which the converting apparatus 1 a is a member and the IPv4 multicast address corresponding thereto.
- An IPv4 multicast membership table 51 holds the IPv4 multicast address of the IPv4 multicast group of which the converting apparatus 1 a is the member.
- an IPv6 multicast membership table 52 holds the IPv6 multicast address of the IPv6 multicast group of which the converting apparatus 1 a is the member.
- the IP multicast membership group managing unit 5 holds and manages the IPv4 multicast membership table 51 and the IPv6 multicast membership table 52 .
- the IP header converting unit 6 executes the IP header conversion toward the IPv4 multicast packet transferred from the IP transmitting/receiving unit 2 , thereby creating the IPv6 multicast packet. Furthermore, the IP header converting unit 6 instructs the IP transmitting/receiving unit 2 to send out the created IPv6 multicast packet to the IPv6 network 102 .
- FIG. 14( a ) illustrates an IPv6 header format.
- the IPv6 header format includes the following fields: The version number of IPv6, i.e., “ 6 ”, is stored into a “Version” field.
- the priority of a processing at the time when a router relays the packet on a network is stored into a “Priority” field.
- the identifier at the time of performing a priority control or the like is stored into a “Flow Label” field.
- the length of the data portion resulting from removing the IPv6 header portion from the packet is stored into a “Payload Length” field.
- the identifier as to the header of which higher-order layer's protocol will follow next to the IPv6 header or the like is stored into a “Next Header Identifier” field.
- the maximum transfer number of the packet is stored into a “Hop Limit” field.
- the transmission source IP address is stored into a “Transmission Source IP Address” field, and the transmission destination IP address is stored into a “Transmission Destination IP Address” field.
- FIG. 14( b ) illustrates an IPv4 header format.
- the IPv4 header format includes the following fields: The version number of IPv4, i.e., “4”, is stored into a “Version” field. The length of the IPv4 header itself is stored into a “Header Length” field. The information indicating the service quality of a communications processing is stored into a “Service Type” field. The size of the entire packet resulting from adding the IPv4 header to the data block dealt with in the IP is stored into a “Packet Length” field. The identifier that is used as the reference information when transferring the data to the higher-order layer is stored into an “Identifier” field.
- the control information on the division of the packet is stored into a “Fragment Offset” field.
- the information indicating where the divided data (i.e., the fragments) have been positioned within the original data is stored into a “Flag” field.
- the time during which the packet may exist on the network is stored into a “Time To Live” field.
- the information indicating what the higher-order layer's protocol is is stored into a “Protocol” field.
- the checksum of the IP header is stored into a “Header Checksum” field.
- the transmission source IP address is stored into a “Transmission Source IP Address” field
- the transmission destination IP address is stored into a “Transmission Destination IP Address” field.
- the IP header converting unit 6 executes the processing of converting the IPv4 header to the IPv6 header, both of which are illustrated in FIG. 14, or the processing of converting the IPv6 header to the IPv4 header. Then, the converting unit 6 sets the values in the respective fields within the IPv4 or the IPv6 header format after having been converted.
- an attention will be focused on, in particular, the address conversion of the transmission source IP address and the transmission destination IP address out of the IP header conversion processing. Accordingly, the description will be given mainly regarding the conversion processing of the “Transmission Source IP Address” field and the “Transmission Destination IP Address” field.
- the IP header converting unit 6 makes an inquiry of the IP address conversion information holding unit 4 , thereby acquiring the IPv6 multicast address corresponding to the IPv4 transmission destination address of the IPv4 multicast packet. Then, using the IPv6 multicast address acquired from the IP address conversion information holding unit 4 , the IP header converting unit 6 converts the IPv4 transmission destination address into the IPv6 transmission destination address. Similarly, the IP header converting unit 6 makes an inquiry of the IP address conversion information holding unit 4 , thereby acquiring the IPv6 unicast address corresponding to the IPv4 transmission source address of the IPv4 multicast packet. Then, using the IPv6 unicast address acquired from the IP address conversion information holding unit 4 , the IP header converting unit 6 converts the IPv4 transmission source address into the IPv6 transmission source address.
- the IP header converting unit 6 creates the IPv4 multicast packet from the IPv6 multicast packet transferred from the IP transmitting/receiving unit 2 , then instructing the IP transmitting/receiving unit 2 to send out the IPv4 multicast packet to the IPv4 network 101 .
- the IP header converting unit 6 makes an inquiry of the IP address conversion information holding unit 4 , thereby acquiring the IPv4 multicast address corresponding to the IPv6 transmission destination address of the IPv6 multicast packet. Then, using the acquired IPv4 multicast address, the IP header converting unit 6 converts the IPv6 transmission destination address of the above-described IPv6 multicast packet into the IPv4 transmission destination address.
- the IP header converting unit 6 makes an inquiry of the IP address conversion information holding unit 4 , thereby acquiring the IPv4 unicast address corresponding to the IPv6 transmission source address of the IPv6 multicast packet. Then, using the acquired IPv4 unicast address, the IP header converting unit 6 converts the IPv6 transmission source address of the above-described IPv6 multicast packet into the IPv4 transmission source address.
- FIG. 13 illustrates an example of the hardware configuration of the converting apparatus illustrated in FIG. 1.
- the converting apparatus 1 a includes the following devices: An IP-I/O device 133 for establishing the connection with the IPv4 network 101 and the IPv6 network 102 , a storage device 135 including, for example, a RAM 131 , a ROM 132 , and so on, and an arithmetic-logic device 130 for executing programs stored in the storage device 135 and performing the processing of various types of data stored in the storage device 135 .
- the IP-I/O device 133 , the storage device 135 , and the arithmetic-logic device 130 are connected to each other through a bus 134 or the like.
- the converting apparatus 1 a may have the other storage device such as a hard disk. In this case, the other storage device such as the hard disk is not necessarily-connected directly to the bus 134 .
- the IP transmitting/receiving unit 2 illustrated in FIG. 1 includes the IP-I/O device 133 , i.e., a network interface for performing the transmittance/reception of the IP (i.e., Internet Protocol) packets in FIG. 13, a program that is held in the storage device 135 and is needed for the operation of the IP transmitting/receiving unit 2 , and the arithmetic-logic device 130 for executing the program.
- IP i.e., Internet Protocol
- the IP-I/O device 133 may perform the transmittance/reception processing of the packets for the IPv4 network 101 and the IPv6 network 102 in the following configuration:
- the IP-I/O device 133 is not controlled by the arithmetic-logic device 130 positioned in the different place, but the IP-I/O device 133 itself has the arithmetic-logic device 130 and the storage device 135 inside.
- Each of the for-conversion IP address holding unit 3 , the IP address conversion information holding unit 4 , the IP multicast membership group managing unit 5 , and the IP header converting unit 6 illustrated in FIG. 1 includes a program that is held in the storage device 135 and is needed for the operation of each unit, and the arithmetic-logic device 130 for executing the program.
- FIG. 2 illustrates the configuration diagram of the IPv4 unicast address table 31 .
- the IPv4 unicast addresses used for the IP header conversion are registered in advance into the IPv4 unicast address table 31 in accordance with the instruction from the manager of the converting apparatus 1 a . It is assumed that, in FIG. 2, the IPv4 unicast addresses of 133. 144. 93. 100 ⁇ 133. 144. 93. 200 have been registered into the IPv4 unicast address table 31 in accordance with the instruction from the manager.
- FIG. 3 illustrates the configuration diagram of the IPv4 multicast address table 32 .
- the IPv4 multicast addresses used for the IP header conversion are registered in advance into the IPv4 multicast address table 32 in accordance with the instruction from the manager of the converting apparatus 1 a . It is assumed that, in FIG. 3, the IPv4 multicast addresses of 238. 0. 0. 100 ⁇ 238. 0. 0. 200 have been registered into the IPv4 multicast address table 32 in accordance with the instruction from the manager.
- FIG. 4 illustrates the configuration diagram of the IPv6 unicast address table 33 .
- the IPv6 unicast addresses used for the IP header conversion are registered in advance into the IPv6 unicast address table 33 in accordance with the instruction from the manager of the converting apparatus 1 a . It is assumed that, in FIG. 4, the IPv6 unicast addresses of 1 : : 100 ⁇ 1 : : 200 have been registered into the IPv6 unicast address table 33 in accordance with the instruction from the manager.
- FIG. 5 illustrates the configuration diagram of the IPv6 multicast address table 34 .
- the IPv6 multicast addresses used for the IP header conversion are registered in advance into the IPv6 multicast address table 34 in accordance with the instruction from the manager of the converting apparatus 1 a . It is assumed that, in FIG. 5, the IPv6 multicast addresses of ffle : : 100 ⁇ ffle : : 200 have been registered into the IPv6 multicast address table 34 in accordance with the instruction from the manager.
- FIG. 6 illustrates the configuration diagram of the IP address conversion table 41 .
- the IP address conversion table 41 holds the IPv4 multicast addresses and the IPv6 multicast addresses in correspondence with each other, the IPv4 multicast addresses being the IPv4 transmission destination addresses of the IPv4 multicast packets received by the converting apparatus 1 a , the IPv6 multicast addresses having been acquired from the for-conversion IP address holding unit 3 by the instruction from the IP multicast membership group managing unit 5 .
- the IP address conversion table 41 holds the IPv4 unicast addresses and the IPv6 unicast addresses in correspondence with each other, the IPv4 unicast addresses being the IPv4 transmission source addresses of the IPv4 multicast packets received by the converting apparatus 1 a , the IPv6 unicast addresses having been acquired from the for-conversion IP address holding unit 3 by the instruction from the IP address conversion information holding unit 4 .
- the IP address conversion table 41 holds the IPv6 multicast addresses and the IPv4 multicast addresses in correspondence with each other, the IPv6 multicast addresses being the IPv6 transmission destination addresses of the IPv6 multicast packets received by the converting apparatus 1 a , the IPv4 multicast addresses having been acquired from the for-conversion IP address holding unit 3 by the instruction from the IP multicast membership group managing unit 5 .
- the IP address conversion table 41 holds the IPv6 unicast addresses and the IPv4 unicast addresses in correspondence with each other, the IPv6 unicast addresses being the IPv6 transmission source addresses of the above-described IPv6 multicast packets, the IPv4 unicast addresses having been acquired from the for-conversion IP address holding unit 3 by the instruction from the IP address conversion information holding unit 4 .
- FIG. 7 illustrates the configuration diagram of the IPv4 multicast membership table 51 .
- the IPv4 multicast addresses of the IPv4 multicast group, of which the converting apparatus 1 a has become a member in accordance with the instruction from the manager of the converting apparatus 1 a are registered into the IPv4 multicast membership table 51 .
- FIG. 8 illustrates the configuration diagram of the IPv6 multicast membership table 52 .
- the IPv6 multicast addresses of the IPv6 multicast group, of which the converting apparatus 1 a has become a member in accordance with the instruction from the manager of the converting apparatus 1 a are registered into the IPv6 multicast membership table 52 .
- FIG. 9 illustrates the schematic diagram of a communications network system where the IPv4 network 101 and the IPv6 network 102 are connected to each other through the converting apparatus 1 a .
- An IPv4 multicast server 104 and an IPv4 multicast client 105 are connected to the IPv4 network 101 .
- the IPv4 multicast server 104 broadcasts (transmits) a multicast packet in compliance with IPv4, and the IPv4 multicast client 105 receives the multicast packet in compliance with IPv4.
- an IPv6 multicast server 106 and an IPv6 multicast client 107 are connected to the IPv6 network 102 .
- the IPv6 multicast server 106 broadcasts (transmits) a multicast packet in compliance with IPv6, and the IPv6 multicast client 107 receives the multicast packet in compliance with IPv6.
- IPv4 address 133. 144. 93. 1 and an IPv6 address 1 : : 1 have been assigned to the converting apparatus 1 a .
- IPv4 address 133. 144. 93. 2 has been assigned to the IPv4 multicast server 104 .
- IPv4 address 133. 144. 93. 3 has been assigned to the IPv4 multicast client 105 .
- IPv6 address 1 : : 2 has been assigned to the IPv6 multicast server 106 .
- IPv6 address 1 : : 3 has been assigned to the IPv6 multicast client 107 .
- the IPv4 multicast server 104 broadcasts (transmits), to the IPv4 network 101 , an IPv4 multicast packet the destination address of which is an IPv4 multicast address (238. 0. 0. 1).
- the IPv6 multicast server 106 broadcasts (transmits), to the IPv6 network 102 , an IPv6 multicast packet the destination address of which is an IPv6 multicast address (ffle : : 1).
- the IPv4 network 101 and the IPv6 network 102 are physically isolated completely. However, even in the case where the IPv4 network 101 and the IPv6 network 102 exist in a mixed manner within the physically same network, the explanation given below concerning the embodiment guarantees that the converting apparatus 1 a will function in much the same way.
- FIGS. 10 and 11 illustrate a flowchart in the following case: Using the IPv4 multicast address of 238. 0. 0. 1 as the destination address, the IPv4 multicast server 104 broadcasts (transmits) the IPv4 multicast packet to the IPv4 network 101 . Next, the converting apparatus 1 a receives the IPv4 multicast packet so as to subject the packet to the IP header conversion processing, then sending out the converted packet to the IPv6 network 102 .
- the IPv4 multicast server 104 broadcasts (transmits), to the IPv4 network 101 , the IPv4 multicast packet the destination address of which is the IPv4 multicast address of 238. 0. 0. 1 (FIG. 10).
- the manager of the converting apparatus 1 a instructs the IP multicast membership group managing unit 5 to make the converting apparatus 1 a become a member of the multicast group of the IPv4 multicast address (238. 0. 0. 1).
- the IP multicast membership group managing unit 5 Having received the instruction from the manager, the IP multicast membership group managing unit 5 , at first, registers the IPv4 multicast address (238. 0. 0. 1) into the IPv4 multicast membership table 51 . Next, the IP multicast membership group managing unit 5 instructs the IP address conversion information holding unit 4 to register the IPv4 multicast address (238. 0. 0. 1) and the IPv6 multicast address corresponding thereto into the IP address conversion table 41 .
- the IP address conversion information holding unit 4 searches the IP address conversion table 41 with the IPv4 multicast address (238. 0. 0. 1). If the applicable entry has been found out, the IP address conversion information holding unit 4 makes a report to the effect toward the IP multicast membership group managing unit 5 . If no applicable entry has been found out, the IP address conversion information holding unit 4 acquires the IPv6 multicast address from the for-conversion IP address holding unit 3 , then registering, into the IP address conversion table 41 , the IPv6 multicast address in a state of being made to correspond to the IPv4 multicast address (238. 0. 0. 1).
- the IP address conversion information holding unit 4 makes a report to the effect that the IPv4 multicast address (238. 0. 0. 1) and the IPv6 multicast address corresponding to this address have been registered into IP address conversion table 41 .
- the IP address conversion information holding unit 4 acquires the IPv6 multicast address (ffle : : 100) from the for-conversion IP address holding unit 3 so as to register the IPv6 multicast address into the IP address conversion table 41 in correspondence with the IPv4 multicast address (238. 0. 0. 1), then making the report to the effect toward the IP multicast membership group managing unit 5 .
- the IP multicast membership group managing unit 5 instructs the IP transmitting/receiving unit 2 to transmit, to the IPv4 network 101 , an “IGMP (i.e., Internet Group Management Protocol) Membership Report” message for indicating the membership into the IP multicast group of the IPv4 address (238. 0. 0. 1).
- IGMP Internet Group Management Protocol
- the IP transmitting/receiving unit 2 transmits the “IGMP Membership Report” message to the IPv4 network 101 .
- the converting apparatus 1 a receives the IPv4 multicast packet from the IPv4 network 101 through the IP transmitting/receiving unit 2 .
- the IP transmitting/receiving unit makes an inquiry of the IP multicast membership group managing unit 5 about whether or not the converting apparatus 1 a has become a member of the multicast group of the IPv4 destination address of the IPv4 multicast packet that the converting apparatus 1 a has received.
- the IP multicast membership group managing unit 5 checks whether or not the IPv4 destination address of the received IPv4 multicast packet has been registered in the IPv4 multicast membership table 51 , then making a report on the result (i.e., membership-completed/membership-uncompleted) toward the IP transmitting/receiving unit 2 .
- the IP multicast membership group managing unit 5 makes, toward the IP transmitting/receiving unit 2 , the report to the effect of having been membership-completed.
- the IP transmitting/receiving unit 2 disposes the IPv4 multicast packet.
- the IP transmitting/receiving unit 2 transfers the IPv4 multicast packet to the IP header converting unit 6 .
- the IP transmitting/receiving unit 2 transfers the IPv4 multicast packet to the IP header converting unit 6 .
- the IP header converting unit 6 makes an inquiry of the IP address conversion information holding unit 4 about the IPv6 address corresponding to the IPv4 destination address and the IPv6 address corresponding to the IPv4 source address.
- the IP address conversion information holding unit 4 checks whether or not the IPv4 destination address has been registered in the IP address conversion table 41 . If the IPv4 destination address has been registered therein, the IP address conversion information holding unit 4 makes, toward the IP header converting unit 6 , a report on the IPv6 multicast address corresponding to the IPv4 destination address. If the IPv4 destination address has not been registered in the IP address conversion table 41 , the IP address conversion information holding unit 4 makes, toward the IP header converting unit 6 , a report to the effect of having not been registered. Here, since the IPv4 destination address (238. 0. 0. 1) has been registered in the IP address conversion table 41 , the IP address conversion information holding unit 4 makes, toward the IP header converting unit 6 , the report on the IPv6 multicast address corresponding thereto (ffle : : 100).
- the IP address conversion information holding unit 4 checks whether or not the IPv4 source address has been registered in the IP address conversion table 41 . If the IPv4 source address has been registered therein, the IP address conversion information holding unit 4 makes, toward the IP header converting unit 6 , a report on the IPv6 unicast address corresponding to the IPv4 source address. If the IPv4 source address has not been registered in the IP address conversion table 41 , the IP address conversion information holding unit 4 acquires the IPv6 unicast address from the for-conversion IP address holding unit 3 .
- the IP address conversion information holding unit 4 makes a report on the registered IPv6 unicast address toward the IP header converting unit 6 .
- the IP address conversion information holding unit 4 acquires the IPv6 unicast address (1 : : 100) from the for-conversion IP address holding unit 3 so as to register the IPv6 unicast address into the IP address conversion table 41 .
- the IP address conversion information holding unit 4 makes the report on the IPv6 unicast address d(1 : : 100) toward the IP header converting unit 6 .
- the IP header converting unit 6 receives, from the IP address conversion information holding unit 4 , the reports on the IPv6 multicast address and the IPv6 unicast address that correspond to the IPv4 destination address of the received IPv4 multicast packet and the IPv4 source address thereof, respectively. Moreover, the IP header converting unit 6 creates the IPv6 multicast packet from the received IPv4 multicast packet by the IP header conversion, then instructing the IP transmitting/receiving unit 2 to send out the created IPv6 multicast packet to the IPv6 network 102 .
- the IP header converting unit 6 converts the IPv4 destination address into the IPv6 multicast address corresponding thereto, and converts the IPv4 source address into the IPv6 unicast address corresponding thereto.
- the IP header converting unit 6 disposes the received IPv4 multicast packet.
- the IP header converting unit 6 has received, from the IP address conversion information holding unit 4 , the reports on the IPv6 multicast address (ffle : : 100) corresponding to the IPv4 destination address (238. 0. 0.
- the IP header converting unit 6 converts the IPv4 destination address (238. 0. 0. 1) into the IPv6 destination address (ffle : : 100) using the IPv6 multicast address, and converts the IPv4 source address (133. 144. 93. 2) into the IPv6 source address (1 : : 100) using the IPv6 unicast address.
- the converting apparatus 1 a creates the IPv6 multicast packet from the IPv4 multicast packet.
- the converting apparatus 1 a sends out the created IPv6 multicast packet to the IPv6 network 102 through the IP transmitting/receiving unit 2 .
- the IPv6 multicast client 107 becomes a member of the IPv6 multicast group of the IPv6 destination address (ffle : : 100) of the IPv6 multicast packet created by the converting apparatus 1 a . This membership makes it possible for the IPv6 multicast client 107 to receive this IPv6 multicast packet.
- the above-described processing permits the IPv6 multicast client 107 to receive the IP multicast packet that the IPv4 multicast server 104 broadcasts (transmits) to the IPv4 network 101 with the IPv4 address of b 238 . 0 . 0 . 1 .
- the converting apparatus 1 a becomes a member of the group of the IPv6 multicast packet that the IPv6 multicast server 106 broadcasts (transmits) to the IPv6 network 102 .
- the IP multicast membership group managing unit 5 instructs the IP transmitting/receiving unit 2 to transmit, to the IPv6 network 102 , a “Multicast Listener Report” message described in, for example, RFC (i.e., Request For comments) 2710 .
- RFC i.e., Request For comments
- the IP header converting unit 6 converts the IPv6 destination address (ffle : : 100) of the IPv6 multicast packet into the IPv4 multicast address held in the IP address conversion table 41 in correspondence with the IPv6 multicast address, and converts the IPv6 source address into the IPv4 unicast address held in the IP address conversion table 41 in correspondence with the IPv6 unicast address. Moreover, the converting apparatus 1 a causes the IP header converting unit 6 to subject the IPv6 multicast packet received from the IPv6 network 102 to the IP header conversion processing by the IP header converting unit 6 .
- the converting apparatus 1 a sends out the created IPv4 multicast packet to the IPv4 network 101 through the IP transmitting/receiving unit 2 .
- the above-described processing permits the IPv4 multicast client 105 to receive the IPv4 multicast packet created and sent out to the IPv4 network 101 by the converting apparatus 1 a.
- the converting apparatus 1 a has executed the IP header conversion toward the IPv4 multicast packet indicated by the manager. Other than this, it is also allowable to employ the configuration where the converting apparatus 1 a executes the IP header conversion toward the IPv4 multicast packet that the converting apparatus 1 a has automatically detected by monitoring the IPv4 network 101 . Similarly, it is also allowable to employ the configuration where the converting apparatus 1 a executes the IP header conversion toward the IPv6 multicast packet that the converting apparatus 1 a has automatically detected by monitoring the IPv6 network 102 .
- the IPv4 destination address (238. 0. 0. 1) of the IPv4 multicast packet that the IPv4 multicast server 104 broadcasts (transmits) to the IPv4 network 101 is converted into the IPv6 multicast address (ffle : : 100) acquired from the for-conversion IP address holding unit 3 .
- the IPv4 destination address (238. 0. 0. 1) of the IPv4 multicast packet that the converting apparatus 1 a has received is also allowed to be converted into a 128-bit IPv6 address resulting from adding a fixed pattern to the higher-order bits of the IPv4 destination address (e.g., ffle : : ffff : 238. 0. 0. 1).
- a multicast routing protocol operates between the IPv4 multicast router 121 and an IPv4 multicast router 122 , thereby causing the IPv4 multicast packet to be transferred from the IPv4 multicast server 104 up to the converting apparatus 1 a .
- the case is also allowable where the converting apparatus 1 a and the IPv6 multicast server 104 are connected to different IPv6 networks.
- the present embodiments allow the IP multicast communication to be executed between the IPv4 terminal and the IPv6 terminal. As a result, it becomes possible for the IPv6 terminal to receive the IP multicast packet that is broadcast (transmitted) from the IPv4 terminal. Also, it becomes possible for the IPv4 terminal to receive the IP multicast packet that is broadcast (transmitted) from the IPv6 terminal.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This application relates to U.S. patent application Ser. No. 09/257,003 filed on Feb. 25, 1999 based on Japanese Patent Application Number 10-046739 filed on Feb. 27, 1998, U.S. patent application Ser. No. 09/614,715 filed on Jul. 6, 2000 based on Japanese Patent Application Numbers 8-291480 and 9-212889, and U.S. patent application Ser. No. 09/421,275 filed on Oct. 20, 1999 based on Japanese Patent Application Number 10-299613, all of which are assigned to the present assignee. The contents of those applications are incorporated herein by reference.
- The present invention relates to an IPv4-IPv6 multicast communicating method and an IPv4-IPv6 multicast communicating apparatus in a communications network system. More particularly, it relates to a method and an apparatus for implementing the multicast communication between an IPv4 terminal using IPv4 (i.e., Internet Protocol Version 4) as the communications protocol and an IPv6 terminal using IPv6 (i.e., Internet Protocol Version 6) as the communications protocol.
- As one example of the methods for implementing the communication between the IPv4 terminal and the IPv6 terminal, there can be cited a technology disclosed in U.S. Pat. No. 6,118,784 (JP-A-11-55319). This technology allows the communication between the IPv4 terminal and the IPv6 terminal in the following way: An IP address conversion table for managing the correspondence between an IPv4 address and an IPv6 address is created using DNS (i.e., Domain Name System) protocol extending technology in an apparatus located halfway in the communications path. Then, based on the IP address conversion table, an IPv4 header-IPv6 header conversion is executed, thereby allowing the communication to be implemented.
- The above-cited prior art makes it possible to implement an IP unicast communication between the IPv4 terminal and the IPv6 terminal. In this prior art, however, no consideration has been given to the IP multicast communication between the IPv4 terminal and the IPv6 terminal.
- It is an object of the present invention to provide a method of executing the IP multicast communication between the IPv4 terminal and the IPv6 terminal, and an apparatus for enabling the IP multicast communication to be executed.
- It is another object of the present invention to provide a method of permitting the IPv6 terminal to receive an IP multicast packet transmitted from the IPv4 terminal, and an apparatus for enabling the reception to be executed.
- It is still another object of the present invention to provide a method of permitting the IPv4 terminal to receive an IP multicast packet transmitted from the IPv6 terminal, and an apparatus for enabling the reception to be executed.
- FIG. 1 illustrates the configuration diagram of a converting apparatus according to a 1st embodiment of the present invention;
- FIG. 2 illustrates the configuration diagram of an IPv4 unicast address table;
- FIG. 3 illustrates the configuration diagram of an IPv4 multicast address table;
- FIG. 4 illustrates the configuration diagram of an IPv6 unicast address table;
- FIG. 5 illustrates the configuration diagram of an IPv6 multicast address table;
- FIG. 6 illustrates the configuration diagram of the IP address conversion table;
- FIG. 7 illustrates the configuration diagram of an IPv4 multicast membership table;
- FIG. 8 illustrates the configuration diagram of an IPv6 multicast membership table;
- FIG. 9 illustrates the configuration diagram of a communications network system according to the 1st embodiment of the present invention;
- FIG. 10 illustrates a flowchart in the case where an IP multicast packet broadcast (transmitted) by an IPv4 multicast server is received by an IPv6 multicast client through the converting apparatus according to the 1st embodiment of the present invention;
- FIG. 11 illustrates a flowchart subsequent to the one in FIG. 10;
- FIG. 12 illustrates the configuration diagram of a communications network system according to an embodiment differing from the 1st embodiment of the present invention;
- FIG. 13 illustrates an example of the hardware configuration diagram of the communicating apparatus according to the present invention; and
- FIG. 14 illustrates formats of the IPv6 header and the IPv4 header.
- Hereinafter, referring to the drawings, the explanation will be given concerning the embodiments of the present invention. Incidentally, the embodiments set no limitations to the present invention.
- FIG. 1 illustrates the configuration diagram of a converting
apparatus 1 a according to the 1st embodiment of the present invention. The convertingapparatus 1 a, which is positioned between anIPv4 network 101 and anIPv6 network 102, executes the IP header conversion mutually between an IPv4 multicast packet and an IPv6 multicast packet. Based on this IP header conversion processing, theconverting apparatus 1 a implements the IP multicast communication between the IPv4 terminal and the IPv6 terminal. As illustrated in FIG. 1, the convertingapparatus 1 a includes an IP transmitting/receiving unit 2, a for-conversion IPaddress holding unit 3, an IP address conversioninformation holding unit 4, an IP multicast membershipgroup managing unit 5, and an IPheader converting unit 6. - The IP transmitting/receiving
unit 2 performs the transmittance/reception of the IPv4 multicast packet with theIPv4 network 101, and the transmittance/reception of the IPv6 multicast packet with theIPv6 network 102. - The for-conversion IP
address holding unit 3 holds an IPv4 unicast address, an IPv4 multicast address, an IPv6 unicast address, and an IPv6 multicast address, all of which are used for the IP header conversion. An IPv4 unicast address table 31 holds the IPv4 unicast address used for the IP header conversion. In this embodiment, the IP addresses to be held by the for-conversion IPaddress holding unit 3 have been registered in advance in accordance with the instruction from a manager of the convertingapparatus 1 a. In addition to this method, the following method is also allowable: The converting apparatus performs the communication with a DHCP server so as to automatically acquire unused addresses, then holding the unused addresses into the for-conversion IPaddress holding unit 3. An IPv4 multicast address table 32 holds the IPv4 multicast address used for the IP header conversion. An IPv6 unicast address table 33 holds the IPv6 unicast address used for the IP header conversion. An IPv6 multicast address table 34 holds the IPv6 multicast address used for the IP header conversion. The for-conversion IPaddress holding unit 3 holds and manages all of the IPv4 unicast address table 31, the IPv4 multicast address table 32, the IPv6 unicast address table 33, and the IPv6 multicast address table 34. - The IP address conversion
information holding unit 4 holds the IPv4 unicast address and the IPv6 unicast address, and the IPv4 multicast address and the IPv6 multicast address in a state of being made to correspond to each other, respectively. The IP address conversioninformation holding unit 4 converts the IPv4 multicast address into the IPv6 multicast address held in correspondence with the IPv4 multicast address. Here, the IPv4 multicast address is an IPv4 transmission destination address of the IPv4 multicast packet broadcast (transmitted) by the IPv4 terminal on theIPv4 network 101. Moreover, the IP address conversioninformation holding unit 4 converts the IPv4 unicast address into the IPv6 unicast address held in correspondence with the IPv4 unicast address, the IPv4 unicast address being an IPv4 transmission source address of the above-described IPv4 multicast packet. - Also, the IP address conversion
information holding unit 4 converts the IPv6 multicast address into the IPv4 multicast address held in correspondence with the IPv6 multicast address. Here, the IPv6 multicast address is an IPv6 transmission destination address of the IPv6 multicast packet broadcast (transmitted) by the IPv6 terminal on theIPv6 network 102. Moreover, the IP address conversioninformation holding unit 4 converts the IPv6 unicast address into the IPv4 unicast address held in correspondence with the IPv6 unicast address, the IPv6 unicast address being an IPv6 transmission source address of the above-described IPv6 multicast packet. - An IP address conversion table41 holds the following addresses, respectively: The IPv4 transmission destination address of the IPv4 multicast packet, which has been received by the converting
apparatus 1 a, and the IPv6 multicast address corresponding thereto, and the IPv4 transmission source address of the above-described IPv4 multicast packet and the IPv6 unicast address corresponding thereto. Also, the IP address conversion table 41 holds the following addresses, respectively: The IPv6 transmission destination address of the received IPv6 multicast packet and the IPv4 multicast address corresponding thereto, and the IPv6 transmission source address of the above-described IPv6 multicast packet and the IPv4 unicast address corresponding thereto. The IP address conversioninformation holding unit 4 holds and manages the above-described IP address conversion table 41. - In accordance with the instruction from the manager of the converting
apparatus 1 a, the IP multicast membershipgroup managing unit 5 performs the membership state management of the convertingapparatus 1 a into an IPv4 multicast group and an IPv6 multicast group. Also, the IP multicast membershipgroup managing unit 5 instructs the IP address conversioninformation holding unit 4 to register the IPv4 multicast address of the IPv4 multicast group of which the convertingapparatus 1 a is a member and the IPv6 multicast address corresponding thereto, or the IPv6 multicast address of the IPv6 multicast group of which the convertingapparatus 1 a is a member and the IPv4 multicast address corresponding thereto. An IPv4 multicast membership table 51 holds the IPv4 multicast address of the IPv4 multicast group of which the convertingapparatus 1 a is the member. Also, an IPv6 multicast membership table 52 holds the IPv6 multicast address of the IPv6 multicast group of which the convertingapparatus 1 a is the member. The IP multicast membershipgroup managing unit 5 holds and manages the IPv4 multicast membership table 51 and the IPv6 multicast membership table 52. - The IP
header converting unit 6 executes the IP header conversion toward the IPv4 multicast packet transferred from the IP transmitting/receivingunit 2, thereby creating the IPv6 multicast packet. Furthermore, the IPheader converting unit 6 instructs the IP transmitting/receivingunit 2 to send out the created IPv6 multicast packet to theIPv6 network 102. - FIG. 14(a) illustrates an IPv6 header format. The IPv6 header format includes the following fields: The version number of IPv6, i.e., “6”, is stored into a “Version” field. The priority of a processing at the time when a router relays the packet on a network is stored into a “Priority” field. The identifier at the time of performing a priority control or the like is stored into a “Flow Label” field. The length of the data portion resulting from removing the IPv6 header portion from the packet is stored into a “Payload Length” field. The identifier as to the header of which higher-order layer's protocol will follow next to the IPv6 header or the like is stored into a “Next Header Identifier” field. The maximum transfer number of the packet is stored into a “Hop Limit” field. In addition, the transmission source IP address is stored into a “Transmission Source IP Address” field, and the transmission destination IP address is stored into a “Transmission Destination IP Address” field.
- FIG. 14(b) illustrates an IPv4 header format. The IPv4 header format includes the following fields: The version number of IPv4, i.e., “4”, is stored into a “Version” field. The length of the IPv4 header itself is stored into a “Header Length” field. The information indicating the service quality of a communications processing is stored into a “Service Type” field. The size of the entire packet resulting from adding the IPv4 header to the data block dealt with in the IP is stored into a “Packet Length” field. The identifier that is used as the reference information when transferring the data to the higher-order layer is stored into an “Identifier” field. The control information on the division of the packet is stored into a “Fragment Offset” field. The information indicating where the divided data (i.e., the fragments) have been positioned within the original data is stored into a “Flag” field. The time during which the packet may exist on the network is stored into a “Time To Live” field. The information indicating what the higher-order layer's protocol is is stored into a “Protocol” field. The checksum of the IP header is stored into a “Header Checksum” field. In addition, the transmission source IP address is stored into a “Transmission Source IP Address” field, and the transmission destination IP address is stored into a “Transmission Destination IP Address” field.
- The IP
header converting unit 6 executes the processing of converting the IPv4 header to the IPv6 header, both of which are illustrated in FIG. 14, or the processing of converting the IPv6 header to the IPv4 header. Then, the convertingunit 6 sets the values in the respective fields within the IPv4 or the IPv6 header format after having been converted. Incidentally, in the following explanation concerning the present embodiment, an attention will be focused on, in particular, the address conversion of the transmission source IP address and the transmission destination IP address out of the IP header conversion processing. Accordingly, the description will be given mainly regarding the conversion processing of the “Transmission Source IP Address” field and the “Transmission Destination IP Address” field. - In this IP header conversion, the IP
header converting unit 6 makes an inquiry of the IP address conversioninformation holding unit 4, thereby acquiring the IPv6 multicast address corresponding to the IPv4 transmission destination address of the IPv4 multicast packet. Then, using the IPv6 multicast address acquired from the IP address conversioninformation holding unit 4, the IPheader converting unit 6 converts the IPv4 transmission destination address into the IPv6 transmission destination address. Similarly, the IPheader converting unit 6 makes an inquiry of the IP address conversioninformation holding unit 4, thereby acquiring the IPv6 unicast address corresponding to the IPv4 transmission source address of the IPv4 multicast packet. Then, using the IPv6 unicast address acquired from the IP address conversioninformation holding unit 4, the IPheader converting unit 6 converts the IPv4 transmission source address into the IPv6 transmission source address. - Furthermore, the IP
header converting unit 6 creates the IPv4 multicast packet from the IPv6 multicast packet transferred from the IP transmitting/receivingunit 2, then instructing the IP transmitting/receivingunit 2 to send out the IPv4 multicast packet to theIPv4 network 101. In this IP header conversion, the IPheader converting unit 6 makes an inquiry of the IP address conversioninformation holding unit 4, thereby acquiring the IPv4 multicast address corresponding to the IPv6 transmission destination address of the IPv6 multicast packet. Then, using the acquired IPv4 multicast address, the IPheader converting unit 6 converts the IPv6 transmission destination address of the above-described IPv6 multicast packet into the IPv4 transmission destination address. The IPheader converting unit 6 makes an inquiry of the IP address conversioninformation holding unit 4, thereby acquiring the IPv4 unicast address corresponding to the IPv6 transmission source address of the IPv6 multicast packet. Then, using the acquired IPv4 unicast address, the IPheader converting unit 6 converts the IPv6 transmission source address of the above-described IPv6 multicast packet into the IPv4 transmission source address. - FIG. 13 illustrates an example of the hardware configuration of the converting apparatus illustrated in FIG. 1. In FIG. 13, the converting
apparatus 1 a includes the following devices: An IP-I/O device 133 for establishing the connection with theIPv4 network 101 and theIPv6 network 102, astorage device 135 including, for example, aRAM 131, aROM 132, and so on, and an arithmetic-logic device 130 for executing programs stored in thestorage device 135 and performing the processing of various types of data stored in thestorage device 135. The IP-I/O device 133, thestorage device 135, and the arithmetic-logic device 130 are connected to each other through abus 134 or the like. Here, in addition to theRAM 131 and theROM 132, the convertingapparatus 1 a may have the other storage device such as a hard disk. In this case, the other storage device such as the hard disk is not necessarily-connected directly to thebus 134. - The IP transmitting/receiving
unit 2 illustrated in FIG. 1 includes the IP-I/O device 133, i.e., a network interface for performing the transmittance/reception of the IP (i.e., Internet Protocol) packets in FIG. 13, a program that is held in thestorage device 135 and is needed for the operation of the IP transmitting/receivingunit 2, and the arithmetic-logic device 130 for executing the program. Also, the IP-I/O device 133 may perform the transmittance/reception processing of the packets for theIPv4 network 101 and theIPv6 network 102 in the following configuration: The IP-I/O device 133 is not controlled by the arithmetic-logic device 130 positioned in the different place, but the IP-I/O device 133 itself has the arithmetic-logic device 130 and thestorage device 135 inside. - Each of the for-conversion IP
address holding unit 3, the IP address conversioninformation holding unit 4, the IP multicast membershipgroup managing unit 5, and the IPheader converting unit 6 illustrated in FIG. 1 includes a program that is held in thestorage device 135 and is needed for the operation of each unit, and the arithmetic-logic device 130 for executing the program. - FIG. 2 illustrates the configuration diagram of the IPv4 unicast address table31. The IPv4 unicast addresses used for the IP header conversion are registered in advance into the IPv4 unicast address table 31 in accordance with the instruction from the manager of the converting
apparatus 1 a. It is assumed that, in FIG. 2, the IPv4 unicast addresses of 133. 144. 93. 100˜133. 144. 93. 200 have been registered into the IPv4 unicast address table 31 in accordance with the instruction from the manager. - FIG. 3 illustrates the configuration diagram of the IPv4 multicast address table32. The IPv4 multicast addresses used for the IP header conversion are registered in advance into the IPv4 multicast address table 32 in accordance with the instruction from the manager of the converting
apparatus 1 a. It is assumed that, in FIG. 3, the IPv4 multicast addresses of 238. 0. 0. 100˜238. 0. 0. 200 have been registered into the IPv4 multicast address table 32 in accordance with the instruction from the manager. - FIG. 4 illustrates the configuration diagram of the IPv6 unicast address table33. The IPv6 unicast addresses used for the IP header conversion are registered in advance into the IPv6 unicast address table 33 in accordance with the instruction from the manager of the converting
apparatus 1 a. It is assumed that, in FIG. 4, the IPv6 unicast addresses of 1 : : 100˜1 : : 200 have been registered into the IPv6 unicast address table 33 in accordance with the instruction from the manager. - FIG. 5 illustrates the configuration diagram of the IPv6 multicast address table34. The IPv6 multicast addresses used for the IP header conversion are registered in advance into the IPv6 multicast address table 34 in accordance with the instruction from the manager of the converting
apparatus 1 a. It is assumed that, in FIG. 5, the IPv6 multicast addresses of ffle : : 100˜ffle : : 200 have been registered into the IPv6 multicast address table 34 in accordance with the instruction from the manager. - FIG. 6 illustrates the configuration diagram of the IP address conversion table41. The IP address conversion table 41 holds the IPv4 multicast addresses and the IPv6 multicast addresses in correspondence with each other, the IPv4 multicast addresses being the IPv4 transmission destination addresses of the IPv4 multicast packets received by the converting
apparatus 1 a, the IPv6 multicast addresses having been acquired from the for-conversion IPaddress holding unit 3 by the instruction from the IP multicast membershipgroup managing unit 5. Moreover, the IP address conversion table 41 holds the IPv4 unicast addresses and the IPv6 unicast addresses in correspondence with each other, the IPv4 unicast addresses being the IPv4 transmission source addresses of the IPv4 multicast packets received by the convertingapparatus 1 a, the IPv6 unicast addresses having been acquired from the for-conversion IPaddress holding unit 3 by the instruction from the IP address conversioninformation holding unit 4. - Also, the IP address conversion table41 holds the IPv6 multicast addresses and the IPv4 multicast addresses in correspondence with each other, the IPv6 multicast addresses being the IPv6 transmission destination addresses of the IPv6 multicast packets received by the converting
apparatus 1 a, the IPv4 multicast addresses having been acquired from the for-conversion IPaddress holding unit 3 by the instruction from the IP multicast membershipgroup managing unit 5. Moreover, the IP address conversion table 41 holds the IPv6 unicast addresses and the IPv4 unicast addresses in correspondence with each other, the IPv6 unicast addresses being the IPv6 transmission source addresses of the above-described IPv6 multicast packets, the IPv4 unicast addresses having been acquired from the for-conversion IPaddress holding unit 3 by the instruction from the IP address conversioninformation holding unit 4. - FIG. 7 illustrates the configuration diagram of the IPv4 multicast membership table51. The IPv4 multicast addresses of the IPv4 multicast group, of which the converting
apparatus 1 a has become a member in accordance with the instruction from the manager of the convertingapparatus 1 a, are registered into the IPv4 multicast membership table 51. - FIG. 8 illustrates the configuration diagram of the IPv6 multicast membership table52. The IPv6 multicast addresses of the IPv6 multicast group, of which the converting
apparatus 1 a has become a member in accordance with the instruction from the manager of the convertingapparatus 1 a, are registered into the IPv6 multicast membership table 52. - The respective tables that have been presented in FIGS.2 to 8 so far are stored into, for example, the respective corresponding storage regions of the
storage device 135 in accordance with the - FIG. 9 illustrates the schematic diagram of a communications network system where the
IPv4 network 101 and theIPv6 network 102 are connected to each other through the convertingapparatus 1 a. AnIPv4 multicast server 104 and anIPv4 multicast client 105 are connected to theIPv4 network 101. Here, theIPv4 multicast server 104 broadcasts (transmits) a multicast packet in compliance with IPv4, and theIPv4 multicast client 105 receives the multicast packet in compliance with IPv4. Similarly, anIPv6 multicast server 106 and anIPv6 multicast client 107 are connected to theIPv6 network 102. Here, theIPv6 multicast server 106 broadcasts (transmits) a multicast packet in compliance with IPv6, and theIPv6 multicast client 107 receives the multicast packet in compliance with IPv6. - Here, the following assumptions are made concerning the address assignment: An
IPv4 address 133. 144. 93. 1 and an IPv6 address 1 : : 1 have been assigned to the convertingapparatus 1 a. Also, anIPv4 address 133. 144. 93. 2 has been assigned to theIPv4 multicast server 104. Also, anIPv4 address 133. 144. 93. 3 has been assigned to theIPv4 multicast client 105. Also, an IPv6 address 1 : : 2 has been assigned to theIPv6 multicast server 106. Also, an IPv6 address 1 : : 3 has been assigned to theIPv6 multicast client 107. - Also, the following assumptions are made: The
IPv4 multicast server 104 broadcasts (transmits), to theIPv4 network 101, an IPv4 multicast packet the destination address of which is an IPv4 multicast address (238. 0. 0. 1). Similarly, theIPv6 multicast server 106 broadcasts (transmits), to theIPv6 network 102, an IPv6 multicast packet the destination address of which is an IPv6 multicast address (ffle : : 1). - Additionally, in FIG. 9, the
IPv4 network 101 and theIPv6 network 102 are physically isolated completely. However, even in the case where theIPv4 network 101 and theIPv6 network 102 exist in a mixed manner within the physically same network, the explanation given below concerning the embodiment guarantees that the convertingapparatus 1 a will function in much the same way. - FIGS. 10 and 11 illustrate a flowchart in the following case: Using the IPv4 multicast address of 238. 0. 0. 1 as the destination address, the
IPv4 multicast server 104 broadcasts (transmits) the IPv4 multicast packet to theIPv4 network 101. Next, the convertingapparatus 1 a receives the IPv4 multicast packet so as to subject the packet to the IP header conversion processing, then sending out the converted packet to theIPv6 network 102. - The
IPv4 multicast server 104 broadcasts (transmits), to theIPv4 network 101, the IPv4 multicast packet the destination address of which is the IPv4 multicast address of 238. 0. 0. 1 (FIG. 10). - In order to relay the IPv4 multicast packet to the
IPv6 network 102 by converting the IPv4 multicast packet into the IPv6 multicast packet, the manager of the convertingapparatus 1 a instructs the IP multicast membershipgroup managing unit 5 to make the convertingapparatus 1 a become a member of the multicast group of the IPv4 multicast address (238. 0. 0. 1). - Having received the instruction from the manager, the IP multicast membership
group managing unit 5, at first, registers the IPv4 multicast address (238. 0. 0. 1) into the IPv4 multicast membership table 51. Next, the IP multicast membershipgroup managing unit 5 instructs the IP address conversioninformation holding unit 4 to register the IPv4 multicast address (238. 0. 0. 1) and the IPv6 multicast address corresponding thereto into the IP address conversion table 41. - The IP address conversion
information holding unit 4 searches the IP address conversion table 41 with the IPv4 multicast address (238. 0. 0. 1). If the applicable entry has been found out, the IP address conversioninformation holding unit 4 makes a report to the effect toward the IP multicast membershipgroup managing unit 5. If no applicable entry has been found out, the IP address conversioninformation holding unit 4 acquires the IPv6 multicast address from the for-conversion IPaddress holding unit 3, then registering, into the IP address conversion table 41, the IPv6 multicast address in a state of being made to correspond to the IPv4 multicast address (238. 0. 0. 1). Moreover, toward the IP multicast membershipgroup managing unit 5, the IP address conversioninformation holding unit 4 makes a report to the effect that the IPv4 multicast address (238. 0. 0. 1) and the IPv6 multicast address corresponding to this address have been registered into IP address conversion table 41. At this step in FIG. 10, since no applicable entry has been found out, the IP address conversioninformation holding unit 4 acquires the IPv6 multicast address (ffle : : 100) from the for-conversion IPaddress holding unit 3 so as to register the IPv6 multicast address into the IP address conversion table 41 in correspondence with the IPv4 multicast address (238. 0. 0. 1), then making the report to the effect toward the IP multicast membershipgroup managing unit 5. - Having received from the IP address conversion
information holding unit 4 the report to the effect that the entry corresponding to the IPv4 multicast address (238. 0. 0. 1) has been registered into IP address conversion table 41, the IP multicast membershipgroup managing unit 5 instructs the IP transmitting/receivingunit 2 to transmit, to theIPv4 network 101, an “IGMP (i.e., Internet Group Management Protocol) Membership Report” message for indicating the membership into the IP multicast group of the IPv4 address (238. 0. 0. 1). - In accordance with the instruction from the IP multicast membership
group managing unit 5, the IP transmitting/receivingunit 2 transmits the “IGMP Membership Report” message to theIPv4 network 101. - This allows the converting
apparatus 1 a to receive the IPv4 multicast packet that theIPv4 multicast server 104 broadcasts (transmits) to theIPv4 network 101 with the use of the IPv4 multicast address of 238. 0. 0. 1. Subsequently, the convertingapparatus 1 a executes the following processing, which is illustrated in FIG. 11. - The converting
apparatus 1 a receives the IPv4 multicast packet from theIPv4 network 101 through the IP transmitting/receivingunit 2. The IP transmitting/receiving unit makes an inquiry of the IP multicast membershipgroup managing unit 5 about whether or not the convertingapparatus 1 a has become a member of the multicast group of the IPv4 destination address of the IPv4 multicast packet that the convertingapparatus 1 a has received. The - The IP multicast membership
group managing unit 5 checks whether or not the IPv4 destination address of the received IPv4 multicast packet has been registered in the IPv4 multicast membership table 51, then making a report on the result (i.e., membership-completed/membership-uncompleted) toward the IP transmitting/receivingunit 2. At this step in FIG. 11, since the IPv4 address of 238. 0. 0. 1 has been registered in the IPv4 multicast membership table 51, the IP multicast membershipgroup managing unit 5 makes, toward the IP transmitting/receivingunit 2, the report to the effect of having been membership-completed. - When receiving from the IP multicast membership
group managing unit 5 the report of having been membership-uncompleted, the IP transmitting/receivingunit 2 disposes the IPv4 multicast packet. When receiving from the IP multicast membershipgroup managing unit 5 the report of having been membership-completed, the IP transmitting/receivingunit 2 transfers the IPv4 multicast packet to the IPheader converting unit 6. At this step in FIG. 11, since the IP transmitting/receivingunit 2 has received the report of having been membership-completed, the IP transmitting/receivingunit 2 transfers the IPv4 multicast packet to the IPheader converting unit 6. - Having received the IPv4 multicast packet from the IP transmitting/receiving
unit 2, the IPheader converting unit 6 makes an inquiry of the IP address conversioninformation holding unit 4 about the IPv6 address corresponding to the IPv4 destination address and the IPv6 address corresponding to the IPv4 source address. - First, the IP address conversion
information holding unit 4 checks whether or not the IPv4 destination address has been registered in the IP address conversion table 41. If the IPv4 destination address has been registered therein, the IP address conversioninformation holding unit 4 makes, toward the IPheader converting unit 6, a report on the IPv6 multicast address corresponding to the IPv4 destination address. If the IPv4 destination address has not been registered in the IP address conversion table 41, the IP address conversioninformation holding unit 4 makes, toward the IPheader converting unit 6, a report to the effect of having not been registered. Here, since the IPv4 destination address (238. 0. 0. 1) has been registered in the IP address conversion table 41, the IP address conversioninformation holding unit 4 makes, toward the IPheader converting unit 6, the report on the IPv6 multicast address corresponding thereto (ffle : : 100). - Next, the IP address conversion
information holding unit 4 checks whether or not the IPv4 source address has been registered in the IP address conversion table 41. If the IPv4 source address has been registered therein, the IP address conversioninformation holding unit 4 makes, toward the IPheader converting unit 6, a report on the IPv6 unicast address corresponding to the IPv4 source address. If the IPv4 source address has not been registered in the IP address conversion table 41, the IP address conversioninformation holding unit 4 acquires the IPv6 unicast address from the for-conversion IPaddress holding unit 3. Moreover, after registering the acquired IPv6 unicast address and the IPv4 source address in correspondence with each other into the IP address conversion table 41, the IP address conversioninformation holding unit 4 makes a report on the registered IPv6 unicast address toward the IPheader converting unit 6. At this step in FIG. 11, since the IPv4 source address (133. 144. 93. 2) has not been registered in the IP address conversion table 41, the IP address conversioninformation holding unit 4 acquires the IPv6 unicast address (1 : : 100) from the for-conversion IPaddress holding unit 3 so as to register the IPv6 unicast address into the IP address conversion table 41. After that, the IP address conversioninformation holding unit 4 makes the report on the IPv6 unicast address d(1 : : 100) toward the IPheader converting unit 6. - The IP
header converting unit 6 receives, from the IP address conversioninformation holding unit 4, the reports on the IPv6 multicast address and the IPv6 unicast address that correspond to the IPv4 destination address of the received IPv4 multicast packet and the IPv4 source address thereof, respectively. Moreover, the IPheader converting unit 6 creates the IPv6 multicast packet from the received IPv4 multicast packet by the IP header conversion, then instructing the IP transmitting/receivingunit 2 to send out the created IPv6 multicast packet to theIPv6 network 102. In the IP header conversion, the IPheader converting unit 6 converts the IPv4 destination address into the IPv6 multicast address corresponding thereto, and converts the IPv4 source address into the IPv6 unicast address corresponding thereto. When the IPheader converting unit 6 has received, from the IP address conversioninformation holding unit 4, the report to the effect that the IPv4 destination address of the received IPv4 multicast packet has not been registered in the IP address conversion table 41, the IPheader converting unit 6 disposes the received IPv4 multicast packet. At this step in FIG. 11, the IPheader converting unit 6 has received, from the IP address conversioninformation holding unit 4, the reports on the IPv6 multicast address (ffle : : 100) corresponding to the IPv4 destination address (238. 0. 0. 1) and the IPv6 unicast address (1 : : 100) corresponding to the IPv4 source address (133. 144. 93. 2). Furthermore, the IPheader converting unit 6 converts the IPv4 destination address (238. 0. 0. 1) into the IPv6 destination address (ffle : : 100) using the IPv6 multicast address, and converts the IPv4 source address (133. 144. 93. 2) into the IPv6 source address (1 : : 100) using the IPv6 unicast address. By executing the above-described processing, the convertingapparatus 1 a creates the IPv6 multicast packet from the IPv4 multicast packet. In addition, the convertingapparatus 1 a sends out the created IPv6 multicast packet to theIPv6 network 102 through the IP transmitting/receivingunit 2. - The
IPv6 multicast client 107 becomes a member of the IPv6 multicast group of the IPv6 destination address (ffle : : 100) of the IPv6 multicast packet created by the convertingapparatus 1 a. This membership makes it possible for theIPv6 multicast client 107 to receive this IPv6 multicast packet. - The above-described processing permits the
IPv6 multicast client 107 to receive the IP multicast packet that theIPv4 multicast server 104 broadcasts (transmits) to theIPv4 network 101 with the IPv4 address ofb 238. 0. 0. 1. - In this embodiment, the explanation has been given regarding the case where the
IPv6 multicast client 107 receives the IPv4 multicast packet that theIPv4 multicast server 104 broadcasts (transmits) to theIPv4 network 101 with the IPv4 address of 238. 0. 0. 1. Meanwhile, in the case as well where theIPv4 multicast client 105 receives the IPv6 multicast packet that theIPv6 multicast server 106 broadcasts (transmits) to theIPv6 network 102 using the IPv6 multicast address of ffle : : 1 as the destination address, it is allowable to cause the convertingapparatus 1 a to execute the same processing in order to accomplish the object. Namely, first, the convertingapparatus 1 a becomes a member of the group of the IPv6 multicast packet that theIPv6 multicast server 106 broadcasts (transmits) to theIPv6 network 102. On account of this, the IP multicast membershipgroup managing unit 5 instructs the IP transmitting/receivingunit 2 to transmit, to theIPv6 network 102, a “Multicast Listener Report” message described in, for example, RFC (i.e., Request For comments) 2710. This permits the convertingapparatus 1 a to receive the IPv6 multicast packet that theIPv6 multicast server 106 broadcasts (transmits) to theIPv6 network 102 using the IPv6 multicast address of ffle : : 1. - The IP
header converting unit 6 converts the IPv6 destination address (ffle : : 100) of the IPv6 multicast packet into the IPv4 multicast address held in the IP address conversion table 41 in correspondence with the IPv6 multicast address, and converts the IPv6 source address into the IPv4 unicast address held in the IP address conversion table 41 in correspondence with the IPv6 unicast address. Moreover, the convertingapparatus 1 a causes the IPheader converting unit 6 to subject the IPv6 multicast packet received from theIPv6 network 102 to the IP header conversion processing by the IPheader converting unit 6. - Furthermore, the converting
apparatus 1 a sends out the created IPv4 multicast packet to theIPv4 network 101 through the IP transmitting/receivingunit 2. The above-described processing permits theIPv4 multicast client 105 to receive the IPv4 multicast packet created and sent out to theIPv4 network 101 by the convertingapparatus 1 a. - In this embodiment, the converting
apparatus 1 a has executed the IP header conversion toward the IPv4 multicast packet indicated by the manager. Other than this, it is also allowable to employ the configuration where the convertingapparatus 1 a executes the IP header conversion toward the IPv4 multicast packet that the convertingapparatus 1 a has automatically detected by monitoring theIPv4 network 101. Similarly, it is also allowable to employ the configuration where the convertingapparatus 1 a executes the IP header conversion toward the IPv6 multicast packet that the convertingapparatus 1 a has automatically detected by monitoring theIPv6 network 102. - In this embodiment, the explanation has been given regarding the case where the IPv4 destination address (238. 0. 0. 1) of the IPv4 multicast packet that the
IPv4 multicast server 104 broadcasts (transmits) to theIPv4 network 101 is converted into the IPv6 multicast address (ffle : : 100) acquired from the for-conversion IPaddress holding unit 3. Other than this, the IPv4 destination address (238. 0. 0. 1) of the IPv4 multicast packet that the convertingapparatus 1 a has received is also allowed to be converted into a 128-bit IPv6 address resulting from adding a fixed pattern to the higher-order bits of the IPv4 destination address (e.g., ffle : : ffff : 238. 0. 0. 1). - In this embodiment, the explanation has been given regarding the case where, as illustrated in FIG. 9, the-converting
apparatus 1 a and theIPv4 multicast server 104 are connected to thesame IPv4 network 101. Other than this, as illustrated in FIG. 12, the case is also allowable where the convertingapparatus 1 a and theIPv4 multicast server 104 are connected to different IPv4 networks. In this case, the IGMP message that the convertingapparatus 1 a transmits in order to become the member of the IPv4 address of 238. 0. 0. 1 is received by an IPv4 multicast router 121. Then, a multicast routing protocol operates between the IPv4 multicast router 121 and an IPv4 multicast router 122, thereby causing the IPv4 multicast packet to be transferred from theIPv4 multicast server 104 up to the convertingapparatus 1 a. The case is also allowable where the convertingapparatus 1 a and theIPv6 multicast server 104 are connected to different IPv6 networks. - The present embodiments allow the IP multicast communication to be executed between the IPv4 terminal and the IPv6 terminal. As a result, it becomes possible for the IPv6 terminal to receive the IP multicast packet that is broadcast (transmitted) from the IPv4 terminal. Also, it becomes possible for the IPv4 terminal to receive the IP multicast packet that is broadcast (transmitted) from the IPv6 terminal.
Claims (9)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/094,603 US7400645B2 (en) | 2000-05-30 | 2002-03-12 | Multicast routing method and an apparatus for routing a multicast packet |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2000-164720 | 2000-05-30 | ||
JP2000164720A JP4501230B2 (en) | 2000-05-30 | 2000-05-30 | IPv4-IPv6 multicast communication method and apparatus |
US09/865,580 US6907037B2 (en) | 2000-05-30 | 2001-05-29 | Multicast routing method and an apparatus for routing a multicast packet |
US10/094,603 US7400645B2 (en) | 2000-05-30 | 2002-03-12 | Multicast routing method and an apparatus for routing a multicast packet |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/865,580 Continuation US6907037B2 (en) | 2000-05-30 | 2001-05-29 | Multicast routing method and an apparatus for routing a multicast packet |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020090002A1 true US20020090002A1 (en) | 2002-07-11 |
US7400645B2 US7400645B2 (en) | 2008-07-15 |
Family
ID=18668302
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/865,580 Expired - Lifetime US6907037B2 (en) | 2000-05-30 | 2001-05-29 | Multicast routing method and an apparatus for routing a multicast packet |
US10/094,636 Expired - Fee Related US7400646B2 (en) | 2000-05-30 | 2002-03-12 | Multicast routing method and an apparatus for routing a multicast packet |
US10/094,603 Expired - Fee Related US7400645B2 (en) | 2000-05-30 | 2002-03-12 | Multicast routing method and an apparatus for routing a multicast packet |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/865,580 Expired - Lifetime US6907037B2 (en) | 2000-05-30 | 2001-05-29 | Multicast routing method and an apparatus for routing a multicast packet |
US10/094,636 Expired - Fee Related US7400646B2 (en) | 2000-05-30 | 2002-03-12 | Multicast routing method and an apparatus for routing a multicast packet |
Country Status (5)
Country | Link |
---|---|
US (3) | US6907037B2 (en) |
EP (1) | EP1161028B1 (en) |
JP (1) | JP4501230B2 (en) |
CN (4) | CN1146197C (en) |
DE (1) | DE60110311T2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030133458A1 (en) * | 2002-01-17 | 2003-07-17 | Masaaki Sato | Unicast-to-multicast converting apparatus, method, and computer program product, and monitoring system comprising the same |
US20040081177A1 (en) * | 2002-10-24 | 2004-04-29 | Alcatel | Telecommunication router |
US20050190765A1 (en) * | 2004-02-27 | 2005-09-01 | Tomonori Gotoh | Multicast network unit, multicast network system, and multicast method |
Families Citing this family (81)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4347497B2 (en) * | 2000-04-03 | 2009-10-21 | 株式会社日立製作所 | Communication control apparatus and packet conversion method |
JP4365998B2 (en) * | 2000-07-21 | 2009-11-18 | 株式会社日立製作所 | Multicast communication method and communication apparatus |
JP4001820B2 (en) * | 2001-03-08 | 2007-10-31 | ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニー | Address converter |
EP1246425A1 (en) * | 2001-03-30 | 2002-10-02 | BRITISH TELECOMMUNICATIONS public limited company | Packet switching networks |
KR20030050506A (en) * | 2001-12-18 | 2003-06-25 | 이경근 | Virtual Conference System Based on IPv6 Multicast |
US7440471B1 (en) * | 2002-04-17 | 2008-10-21 | Mcafee, Inc. | System and method for facilitating IPv6 protocol usage by an application program |
US20030227916A1 (en) * | 2002-06-06 | 2003-12-11 | Toni Paila | System and method for the multicast distribution of multimedia messaging service messages |
JP3688664B2 (en) * | 2002-07-29 | 2005-08-31 | 株式会社東芝 | Relay device and network relay method |
WO2004028099A1 (en) * | 2002-09-18 | 2004-04-01 | Fujitsu Limited | Multi-cast group connection apparatus |
JP4073754B2 (en) * | 2002-10-29 | 2008-04-09 | 富士通株式会社 | Frame transfer device |
US20050111474A1 (en) * | 2002-10-31 | 2005-05-26 | Fujitsu Limited | IP multicast communication system |
EP1420559A1 (en) * | 2002-11-13 | 2004-05-19 | Thomson Licensing S.A. | Method and device for supporting a 6to4 tunneling protocol across a network address translation mechanism |
JP2004207840A (en) * | 2002-12-24 | 2004-07-22 | Nec Corp | Method of managing radio resource, managing apparatus used therefor, base station and terminal |
JP4077330B2 (en) * | 2003-02-06 | 2008-04-16 | 富士通株式会社 | Data generator |
KR20040082655A (en) * | 2003-03-19 | 2004-09-30 | 삼성전자주식회사 | Mobile ip communication system by use of dual stack transition mechanism and method thereof |
US7940764B2 (en) * | 2004-08-12 | 2011-05-10 | Intel Corporation | Method and system for processing multicast packets |
US7498996B2 (en) * | 2004-08-18 | 2009-03-03 | Ruckus Wireless, Inc. | Antennas with polarization diversity |
US7696946B2 (en) | 2004-08-18 | 2010-04-13 | Ruckus Wireless, Inc. | Reducing stray capacitance in antenna element switching |
US8031129B2 (en) | 2004-08-18 | 2011-10-04 | Ruckus Wireless, Inc. | Dual band dual polarization antenna array |
US7362280B2 (en) * | 2004-08-18 | 2008-04-22 | Ruckus Wireless, Inc. | System and method for a minimized antenna apparatus with selectable elements |
US7933628B2 (en) | 2004-08-18 | 2011-04-26 | Ruckus Wireless, Inc. | Transmission and reception parameter control |
US7193562B2 (en) | 2004-11-22 | 2007-03-20 | Ruckus Wireless, Inc. | Circuit board having a peripheral antenna apparatus with selectable antenna elements |
US7880683B2 (en) * | 2004-08-18 | 2011-02-01 | Ruckus Wireless, Inc. | Antennas with polarization diversity |
US7292198B2 (en) * | 2004-08-18 | 2007-11-06 | Ruckus Wireless, Inc. | System and method for an omnidirectional planar antenna apparatus with selectable elements |
US7652632B2 (en) * | 2004-08-18 | 2010-01-26 | Ruckus Wireless, Inc. | Multiband omnidirectional planar antenna apparatus with selectable elements |
US7899497B2 (en) * | 2004-08-18 | 2011-03-01 | Ruckus Wireless, Inc. | System and method for transmission parameter control for an antenna apparatus with selectable elements |
US7965252B2 (en) * | 2004-08-18 | 2011-06-21 | Ruckus Wireless, Inc. | Dual polarization antenna array with increased wireless coverage |
KR100679014B1 (en) | 2004-08-28 | 2007-02-06 | 삼성전자주식회사 | Method for communicating among hosts under mobile ad-hoc network |
CN1758649B (en) * | 2004-10-05 | 2010-04-28 | 华为技术有限公司 | Method of interconnected protocol network communicating between different edition network |
US8619662B2 (en) * | 2004-11-05 | 2013-12-31 | Ruckus Wireless, Inc. | Unicast to multicast conversion |
US9240868B2 (en) * | 2004-11-05 | 2016-01-19 | Ruckus Wireless, Inc. | Increasing reliable data throughput in a wireless network |
US8638708B2 (en) * | 2004-11-05 | 2014-01-28 | Ruckus Wireless, Inc. | MAC based mapping in IP based communications |
US7505447B2 (en) | 2004-11-05 | 2009-03-17 | Ruckus Wireless, Inc. | Systems and methods for improved data throughput in communications networks |
US20060274720A1 (en) * | 2004-11-09 | 2006-12-07 | Andrew Adams | Systems and methods for multicast routing on packet switched networks |
CN1934750B (en) * | 2004-11-22 | 2012-07-18 | 鲁库斯无线公司 | Circuit board having a peripheral antenna apparatus with selectable antenna elements |
US7358912B1 (en) * | 2005-06-24 | 2008-04-15 | Ruckus Wireless, Inc. | Coverage antenna apparatus with selectable horizontal and vertical polarization elements |
US8792414B2 (en) * | 2005-07-26 | 2014-07-29 | Ruckus Wireless, Inc. | Coverage enhancement using dynamic antennas |
KR100716163B1 (en) * | 2004-12-23 | 2007-05-10 | 삼성전자주식회사 | Tunneling Method and Apparatus for Multicasting Between IPv4 Network and IPv6 Network |
US7893882B2 (en) | 2007-01-08 | 2011-02-22 | Ruckus Wireless, Inc. | Pattern shaping of RF emission patterns |
US7646343B2 (en) * | 2005-06-24 | 2010-01-12 | Ruckus Wireless, Inc. | Multiple-input multiple-output wireless antennas |
WO2006081454A2 (en) | 2005-01-26 | 2006-08-03 | Internet Broadcasting Corporation | Layered multicast and fair bandwidth allocation and packet prioritization |
US7653044B1 (en) * | 2005-04-07 | 2010-01-26 | Marvell Israel (M.I.S.L.) Ltd. | Address scope checking for internet protocol version 6 |
KR100687745B1 (en) | 2005-06-14 | 2007-02-27 | 한국전자통신연구원 | Network processor for IPv6 source-specific multicast packet forwarding and method therefor |
KR101242117B1 (en) * | 2005-10-06 | 2013-03-12 | 삼성전자주식회사 | Apparatus and method for routing of broadcast data frame in mesh network wiht multiple mesh portals |
CN101322346A (en) | 2005-12-01 | 2008-12-10 | 鲁库斯无线公司 | On-demand services by wireless base station virtualization |
JP4639152B2 (en) * | 2006-01-20 | 2011-02-23 | 株式会社日立製作所 | Communications system |
CN101056218B (en) * | 2006-04-14 | 2012-08-08 | 华为技术有限公司 | A network performance measurement method and system |
US7788703B2 (en) * | 2006-04-24 | 2010-08-31 | Ruckus Wireless, Inc. | Dynamic authentication in secured wireless networks |
US9769655B2 (en) | 2006-04-24 | 2017-09-19 | Ruckus Wireless, Inc. | Sharing security keys with headless devices |
US9071583B2 (en) * | 2006-04-24 | 2015-06-30 | Ruckus Wireless, Inc. | Provisioned configuration for automatic wireless connection |
US7639106B2 (en) * | 2006-04-28 | 2009-12-29 | Ruckus Wireless, Inc. | PIN diode network for multiband RF coupling |
US20070293178A1 (en) * | 2006-05-23 | 2007-12-20 | Darin Milton | Antenna Control |
FR2903263A1 (en) * | 2006-06-30 | 2008-01-04 | France Telecom | METHOD FOR ADDRESSING SERVICE ELEMENTS AND CALL TRANSMISSION BETWEEN HETEROGENEOUS NODES |
CN1901449B (en) * | 2006-07-19 | 2010-05-12 | 华为技术有限公司 | Network access method and network communication system |
US8670725B2 (en) * | 2006-08-18 | 2014-03-11 | Ruckus Wireless, Inc. | Closed-loop automatic channel selection |
US8547899B2 (en) * | 2007-07-28 | 2013-10-01 | Ruckus Wireless, Inc. | Wireless network throughput enhancement through channel aware scheduling |
US8355343B2 (en) | 2008-01-11 | 2013-01-15 | Ruckus Wireless, Inc. | Determining associations in a mesh network |
US8217843B2 (en) | 2009-03-13 | 2012-07-10 | Ruckus Wireless, Inc. | Adjustment of radiation patterns utilizing a position sensor |
US8698675B2 (en) | 2009-05-12 | 2014-04-15 | Ruckus Wireless, Inc. | Mountable antenna elements for dual band antenna |
JP4851565B2 (en) * | 2009-06-17 | 2012-01-11 | 株式会社日立製作所 | Communication device |
EP2350863B1 (en) | 2009-11-16 | 2015-08-26 | Ruckus Wireless, Inc. | Establishing a mesh network with wired and wireless links |
US9979626B2 (en) | 2009-11-16 | 2018-05-22 | Ruckus Wireless, Inc. | Establishing a mesh network with wired and wireless links |
US8347100B1 (en) | 2010-07-14 | 2013-01-01 | F5 Networks, Inc. | Methods for DNSSEC proxying and deployment amelioration and systems thereof |
US9407012B2 (en) | 2010-09-21 | 2016-08-02 | Ruckus Wireless, Inc. | Antenna with dual polarization and mountable antenna elements |
WO2012151224A2 (en) | 2011-05-01 | 2012-11-08 | Ruckus Wireless, Inc. | Remote cable access point reset |
US9036633B2 (en) | 2011-10-17 | 2015-05-19 | Futurewei Technologies, Inc. | Multicast support for internet protocol version four residual deployment via encapsulation or translation |
US8756668B2 (en) | 2012-02-09 | 2014-06-17 | Ruckus Wireless, Inc. | Dynamic PSK for hotspots |
US9634403B2 (en) | 2012-02-14 | 2017-04-25 | Ruckus Wireless, Inc. | Radio frequency emission pattern shaping |
US10186750B2 (en) | 2012-02-14 | 2019-01-22 | Arris Enterprises Llc | Radio frequency antenna array with spacing element |
US9092610B2 (en) | 2012-04-04 | 2015-07-28 | Ruckus Wireless, Inc. | Key assignment for a brand |
US9570799B2 (en) | 2012-09-07 | 2017-02-14 | Ruckus Wireless, Inc. | Multiband monopole antenna apparatus with ground plane aperture |
US10230161B2 (en) | 2013-03-15 | 2019-03-12 | Arris Enterprises Llc | Low-band reflector for dual band directional antenna |
JP5967173B2 (en) * | 2014-01-31 | 2016-08-10 | 株式会社バッファロー | Network relay device, method for setting operation mode of packet relay processing unit included in network relay device, and computer program |
JP5907239B2 (en) | 2014-01-31 | 2016-04-26 | 株式会社バッファロー | Network relay device, method for setting operation mode of packet relay processing unit included in network relay device, and computer program |
CN105306227A (en) * | 2014-06-16 | 2016-02-03 | 中兴通讯股份有限公司 | Home gateway DS-Lite multicast method and equipment |
US10797888B1 (en) | 2016-01-20 | 2020-10-06 | F5 Networks, Inc. | Methods for secured SCEP enrollment for client devices and devices thereof |
US10469379B2 (en) | 2017-02-17 | 2019-11-05 | Cisco Technology, Inc. | System and method to facilitate content delivery to multiple recipients in a network environment |
US10404592B2 (en) | 2017-03-24 | 2019-09-03 | Cisco Technology, Inc. | System and method to facilitate content forwarding using bit index explicit replication (BIER) in an information-centric networking (ICN) environment |
US11012407B2 (en) * | 2017-10-27 | 2021-05-18 | Dell Products L.P. | System and method of utilizing multiple networks |
CN113595912B (en) * | 2021-07-05 | 2022-11-11 | 北京邮电大学 | One-to-many communication method and device based on IPv6 extension header in 5GLAN |
CN114285797B (en) * | 2021-12-30 | 2024-04-19 | 北京天融信网络安全技术有限公司 | Processing method, device and storage medium of IP address |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5898686A (en) * | 1995-04-25 | 1999-04-27 | Cabletron Systems, Inc. | Network bridge with multicast forwarding table |
US5959989A (en) * | 1997-06-25 | 1999-09-28 | Cisco Technology, Inc. | System for efficient multicast distribution in a virtual local area network environment |
US6038233A (en) * | 1996-07-04 | 2000-03-14 | Hitachi, Ltd. | Translator for IP networks, network system using the translator, and IP network coupling method therefor |
US6118784A (en) * | 1996-11-01 | 2000-09-12 | Hitachi, Ltd. | Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus |
US20010040895A1 (en) * | 2000-03-16 | 2001-11-15 | Templin Fred Lambert | An IPv6-IPv4 compatibility aggregatable global unicast address format for incremental deployment of IPv6 nodes within IPv4 |
US6532233B1 (en) * | 1998-10-19 | 2003-03-11 | Nec Corporation | Multicast communication method and apparatus |
US6704295B1 (en) * | 1998-10-29 | 2004-03-09 | Mitsubishi Materials Corporation | Radio communication system for push information delivery |
US6708219B1 (en) * | 1999-10-26 | 2004-03-16 | 3Com Corporation | Method and system for dual-network address utilization |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH01293046A (en) * | 1988-05-20 | 1989-11-27 | Mitsubishi Electric Corp | Packet protocol communication device |
US5818838A (en) * | 1995-10-12 | 1998-10-06 | 3Com Corporation | Method and apparatus for transparent intermediate system based filtering on a LAN of multicast packets |
JPH09130390A (en) * | 1995-10-31 | 1997-05-16 | Fujitsu Ltd | Atm interface device |
US6523696B1 (en) * | 1996-10-15 | 2003-02-25 | Kabushiki Kaisha Toshiba | Communication control device for realizing uniform service providing environment |
JPH10271164A (en) * | 1997-03-25 | 1998-10-09 | Toshiba Corp | Multicasting method/device |
US6452915B1 (en) * | 1998-07-10 | 2002-09-17 | Malibu Networks, Inc. | IP-flow classification in a wireless point to multi-point (PTMP) transmission system |
JP3519616B2 (en) * | 1998-10-21 | 2004-04-19 | 株式会社日立製作所 | Relay device |
US6272540B1 (en) * | 1998-12-31 | 2001-08-07 | Intel Corporation | Arrangement and method for providing flexible management of a network |
US6757779B1 (en) * | 1999-09-23 | 2004-06-29 | Netlogic Microsystems, Inc. | Content addressable memory with selectable mask write mode |
JP4347497B2 (en) * | 2000-04-03 | 2009-10-21 | 株式会社日立製作所 | Communication control apparatus and packet conversion method |
US6804221B1 (en) * | 2000-06-26 | 2004-10-12 | Alcatel | Micromobility using multicast |
-
2000
- 2000-05-30 JP JP2000164720A patent/JP4501230B2/en not_active Expired - Fee Related
-
2001
- 2001-05-28 EP EP01113029A patent/EP1161028B1/en not_active Expired - Lifetime
- 2001-05-28 DE DE60110311T patent/DE60110311T2/en not_active Expired - Lifetime
- 2001-05-29 US US09/865,580 patent/US6907037B2/en not_active Expired - Lifetime
- 2001-05-29 CN CNB011221941A patent/CN1146197C/en not_active Expired - Fee Related
- 2001-05-29 CN CNB031586643A patent/CN1291574C/en not_active Expired - Fee Related
- 2001-05-29 CN CNB2006101016036A patent/CN100544295C/en not_active Expired - Fee Related
- 2001-05-29 CN CNB031586651A patent/CN100525235C/en not_active Expired - Fee Related
-
2002
- 2002-03-12 US US10/094,636 patent/US7400646B2/en not_active Expired - Fee Related
- 2002-03-12 US US10/094,603 patent/US7400645B2/en not_active Expired - Fee Related
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5898686A (en) * | 1995-04-25 | 1999-04-27 | Cabletron Systems, Inc. | Network bridge with multicast forwarding table |
US6038233A (en) * | 1996-07-04 | 2000-03-14 | Hitachi, Ltd. | Translator for IP networks, network system using the translator, and IP network coupling method therefor |
US6118784A (en) * | 1996-11-01 | 2000-09-12 | Hitachi, Ltd. | Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus |
US5959989A (en) * | 1997-06-25 | 1999-09-28 | Cisco Technology, Inc. | System for efficient multicast distribution in a virtual local area network environment |
US6532233B1 (en) * | 1998-10-19 | 2003-03-11 | Nec Corporation | Multicast communication method and apparatus |
US6704295B1 (en) * | 1998-10-29 | 2004-03-09 | Mitsubishi Materials Corporation | Radio communication system for push information delivery |
US6708219B1 (en) * | 1999-10-26 | 2004-03-16 | 3Com Corporation | Method and system for dual-network address utilization |
US20010040895A1 (en) * | 2000-03-16 | 2001-11-15 | Templin Fred Lambert | An IPv6-IPv4 compatibility aggregatable global unicast address format for incremental deployment of IPv6 nodes within IPv4 |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030133458A1 (en) * | 2002-01-17 | 2003-07-17 | Masaaki Sato | Unicast-to-multicast converting apparatus, method, and computer program product, and monitoring system comprising the same |
US7525927B2 (en) * | 2002-01-17 | 2009-04-28 | Panasonic Corporation | Unicast-to-multicast converting apparatus, method, and computer program product, and monitoring system comprising the same |
US20040081177A1 (en) * | 2002-10-24 | 2004-04-29 | Alcatel | Telecommunication router |
US20050190765A1 (en) * | 2004-02-27 | 2005-09-01 | Tomonori Gotoh | Multicast network unit, multicast network system, and multicast method |
US7570635B2 (en) | 2004-02-27 | 2009-08-04 | Fujitsu Limited | Multicast network unit, multicast network system, and multicast method |
Also Published As
Publication number | Publication date |
---|---|
US6907037B2 (en) | 2005-06-14 |
CN100544295C (en) | 2009-09-23 |
US7400645B2 (en) | 2008-07-15 |
CN1496070A (en) | 2004-05-12 |
CN1921430A (en) | 2007-02-28 |
DE60110311D1 (en) | 2005-06-02 |
CN1496069A (en) | 2004-05-12 |
CN1291574C (en) | 2006-12-20 |
US7400646B2 (en) | 2008-07-15 |
CN1326281A (en) | 2001-12-12 |
US20020031130A1 (en) | 2002-03-14 |
DE60110311T2 (en) | 2006-03-09 |
EP1161028A2 (en) | 2001-12-05 |
EP1161028B1 (en) | 2005-04-27 |
JP4501230B2 (en) | 2010-07-14 |
US20020093960A1 (en) | 2002-07-18 |
CN100525235C (en) | 2009-08-05 |
CN1146197C (en) | 2004-04-14 |
EP1161028A3 (en) | 2003-05-02 |
JP2001345845A (en) | 2001-12-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6907037B2 (en) | Multicast routing method and an apparatus for routing a multicast packet | |
US7860094B2 (en) | Multicast routing method and apparatus for routing multicast packet | |
JP3519616B2 (en) | Relay device | |
US7254132B2 (en) | Mobile communication system, mobile communication method, wireless base station, mobile station, and program | |
US20060140213A1 (en) | Tunneling method and apparatus for multicasting between IPv4 network and IPv6 network | |
US7673061B2 (en) | Method and apparatus for neighborhood discovery across disparate point-to-point networks | |
US8891551B2 (en) | IPv6 over IPv4 transition method and apparatus for improving performance of control server | |
EP1858205A1 (en) | Tunneling device, tunnel frame sorting method used for the device, and its program | |
US6618398B1 (en) | Address resolution for internet protocol sub-networks in asymmetric wireless networks | |
CN112491706A (en) | Data message processing method and device, storage medium and electronic device | |
JP5385269B2 (en) | IPv6-IPv4 conversion method and apparatus for improving control server performance | |
EP2466924A1 (en) | Method, system and access service router for implementing multicast service | |
JP3791497B2 (en) | Packet conversion method | |
JP2008092607A (en) | Translator | |
JP3791496B2 (en) | Packet transmission / reception node and packet transmission / reception method | |
JP3693953B2 (en) | Broadcast transmission method, apparatus, and program | |
CN115314463A (en) | Data transmission method of hierarchical 6LoWPAN mesh network | |
JP4957819B2 (en) | IPv4-IPv6 multicast communication method and apparatus | |
KR20050073947A (en) | Apparatus and method for processing multicast packet in distributed router | |
EP3133770B1 (en) | Home gateway ds-lite multicast method and device | |
EP1993228B1 (en) | Message sending method, message sending device and message transmission system | |
JP2004088718A (en) | Packet processing apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: ALAXALA NETWORKS CORPORATION, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HITACHI, LTD.;REEL/FRAME:047037/0849 Effective date: 20180330 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20200715 |