WO2013176051A1 - マルチキャスト通信方法、通信ノード装置及びプログラム - Google Patents
マルチキャスト通信方法、通信ノード装置及びプログラム Download PDFInfo
- Publication number
- WO2013176051A1 WO2013176051A1 PCT/JP2013/063787 JP2013063787W WO2013176051A1 WO 2013176051 A1 WO2013176051 A1 WO 2013176051A1 JP 2013063787 W JP2013063787 W JP 2013063787W WO 2013176051 A1 WO2013176051 A1 WO 2013176051A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- confirmation message
- parent node
- redundant
- route
- Prior art date
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- 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/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
- H04L12/1868—Measures taken after transmission, e.g. acknowledgments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
Definitions
- the present invention relates to a multicast communication method, a communication node apparatus, and a program for performing multicast delivery redundantly and confirming reception in response to a network failure.
- Non-Patent Document 1 introduces representative studies thereof.
- a route between multicast nodes is controlled by unicast routing.
- the optimum route is selected by a routing protocol such as OSPF (Open Shortest Path First) defined in RFC (Request For Comment) 2328 of IETF (Internet Engineering Task Force).
- OSPF Open Shortest Path First
- RFC Request For Comment
- IETF Internet Engineering Task Force
- the present invention has been made in view of the above problems, and a multicast communication method and communication in which data can be reliably distributed within a restricted time even in the event of a network failure in overlay multicast, and a transmission node can confirm a reception state. It is an object to provide a node device and a program.
- the present invention is a multicast communication method in a network composed of a plurality of communication nodes, and when data is transferred to a subordinate node along a normal distribution route, it is also retransmitted to a child node of the redundant distribution route.
- a reception confirmation message is sent to both the parent node of the normal distribution route and the parent node of the redundant distribution route.
- the present invention is a communication node device that constitutes a communication system that performs multicasting.
- a retransmission timer is also provided to a child node of the redundant distribution route.
- a reception confirmation message is sent to both the parent node of the normal distribution route and the parent node of the redundant distribution route.
- the present invention is a multicast communication program, and when transferring data to a subordinate node along a normal distribution route to a computer, a process for setting a retransmission timer for a child node of a redundant distribution route,
- the program When receiving data, the program is characterized by executing a transmission process of sending a reception confirmation message to both the parent node of the normal distribution route and the parent node of the redundant distribution route.
- data can be reliably distributed within the restricted time even in the event of a network failure in overlay multicast, and the transmission node can confirm the reception state.
- FIG. 1 is a functional configuration diagram of a communication node device according to an embodiment of the present invention.
- FIG. 2 is a diagram showing a configuration example of a network for carrying out the present invention.
- FIG. 3 is a diagram illustrating an example of a distribution tree.
- FIG. 4 is a diagram for explaining a normal communication sequence.
- FIG. 5 is a diagram for explaining a normal communication sequence.
- FIG. 6 is a diagram for explaining a normal communication sequence.
- FIG. 7 is a diagram for explaining a normal communication sequence.
- FIG. 8 is a diagram for explaining a normal communication sequence.
- FIG. 9 is a diagram for explaining a normal communication sequence.
- FIG. 10 is a diagram for explaining a normal communication sequence.
- FIG. 11 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 12 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 13 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 14 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 15 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 16 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 17 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 18 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 19 is a diagram for explaining a communication sequence at the time of failure.
- FIG. 1 shows the configuration of a communication node device according to an embodiment of the present invention.
- the communication node device according to the embodiment of the present invention includes a packet reception unit 901, a packet transmission unit 902, a data processing unit 903, an ACK creation unit 904, a data transfer unit 906, a retransmission management unit 905, a distribution route table 907, and a retransmission management table. 908.
- parent nodes and child nodes are registered in advance for normal and redundant distribution routes.
- the distribution route will be described later.
- the retransmission management table 908 includes retransmission data information such as a retransmission timer for the node that transmitted the data, ACK (reception confirmation message) information received from other nodes, and data reception information (information of the transmission source node) regarding the received data. Etc.) are stored.
- the packet receiving unit 901 receives a packet (data or ACK) from another communication node device. When receiving data, the packet receiving unit 901 passes the received data to the data processing unit 903. When ACK is received, it is passed to the retransmission management section 905.
- the packet transmission unit 902 transmits the requested data or ACK to another communication node.
- the data processing unit 903 passes the data received from the packet receiving unit 901 to the data transfer unit 906 and issues an ACK creation request to the ACK creation unit 904.
- the ACK creation unit 904 determines a node to send an ACK based on the distribution route table 907 and creates an ACK.
- the ACK destination is the parent node (normal system and redundant system) registered in the distribution route table 907.
- the ACK creation unit 904 obtains the data transmission source node from the retransmission management table 908 at the time of ACK creation, and adds information for ACK transfer when the transmission source node is the parent node of the redundant distribution route.
- the ACK transfer information includes information on the parent node of the redundant delivery route that is the transmission source and the parent node of the normal delivery route.
- the data transfer unit 906 acquires the distribution route information registered in the distribution route table 907 and determines which node to transfer. When determining the transfer destination node, the data transfer unit 906 requests the packet transmission unit 902 to transmit data. Thereafter, the retransmission management unit 905 is requested to set a data retransmission timer.
- the retransmission management unit 905 sets a retransmission timer for each receiving node.
- the retransmission timer is set for the normal and redundant child nodes when data is transferred to the subordinate nodes along the normal distribution route.
- the ACK information from the packet receiving unit 901 is recorded in the retransmission management table 908, and the corresponding retransmission timer is canceled.
- ACK transfer information is added to the ACK from the packet receiving unit 901 if the parent node of the redundant distribution route of the transmission source indicated by the ACK transfer information matches itself, the ACK transfer information is The packet transmission unit 902 is requested to transfer ACK to the parent node of the normal distribution route shown.
- FIG. 2 shows a configuration example of a network for carrying out the present invention.
- nodes there are 10 communication node devices (hereinafter simply referred to as nodes) 101, 102, 111, 112, 121, 122, 131, 132, 141, 142.
- Nodes 101 and 102, 111 and 112, 121 and 122, 131 and 132, and 141 and 142 are connected to the same LAN (Local Area Network).
- Each LAN is connected in a ring shape by five routers 201-205.
- All nodes belong to the same multicast group (hereinafter simply referred to as group), and multicast data (hereinafter simply referred to as data) is distributed by overlay multicast.
- group multicast group
- data multicast data
- the node 101 is called an origin node that generates data
- the other nodes are called receiving nodes that receive data.
- the nodes 111, 121, 131, and 141 serve as transfer nodes that transfer data onto each LAN.
- Data distribution from the node 101 is performed along the distribution tree of FIG.
- the solid line in FIG. 3 is a normal transfer path
- the dotted line is a redundant transfer path used when the upper path is disconnected.
- the normal transfer path and the redundant transfer path are set so that the links do not overlap.
- different links are used for the route from the node 101 to 121 and the route from the node 111 to 121.
- FIG. 4 is an example of route setting between nodes in an actual network.
- the path 302 between the nodes 101 and 121 passes through a different link from the path 401 between the nodes 111 and 121, so that both sides do not become disconnected at the same time for a single link failure.
- Each data can be uniquely identified by the origin node 101 adding a sequence number.
- ACK contains information of (origin node ID, group ID, sequence number) and can identify which data is the reception notification.
- ACK Complete
- ACK Pending
- ACK Complete
- ACK is the source of data transfer when the receiving node that does not transfer any more receives data or when the transferring node receives ACK (Complete) from all receiving nodes that are responsible for the transfer. It is sent back to the node (parent node on the distribution route).
- ACK Pending
- ACK Pending
- ACK (Pending) is returned to the data transfer source node in order to notify that it has received the data before performing the transfer.
- the origin node 101 transmits to all receiving nodes on the local LAN using IP multicast on the local LAN (501). Furthermore, data is transmitted to forwarding nodes 111 and 121 of different LANs using IP unicast (511 and 521). The node 101 sets a retransmission timer for the nodes 111, 121, and 102 after transmission.
- the node 102 that has received the data transmitted by IP multicast on the LAN returns an ACK (Complete) indicating that the data has been received to the node 101 by IP unicast (502).
- ACK Complete
- the node 101 cancels the retransmission timer to the node 102.
- the nodes 111 and 121 that have received data from the origin node 101 transmit ACK (Pending) to the node 101 (512 and 513). Further, the nodes 111 and 121 similarly transmit ACK (Pending) to each other, which is the parent of the redundant transfer path (513 and 523).
- the node 101 cancels the retransmission timer for the nodes 111 and 121.
- the nodes 111 and 121 record the ACK (513, 523) received from each node.
- the node 111 transfers the received data to the receiving node 112 on its own LAN using IP multicast (514). Furthermore, it transfers by IP unicast to the transfer node 131 on a different LAN (531). The node 111 sets a retransmission timer for the nodes 112 and 131. Since the node 121 has already received ACK (523) for the data, no retransmission timer is set.
- the node 121 transfers the received data to the receiving node 122 on its own LAN using IP multicast (524). Further, the data is transferred to the transfer node 141 on a different LAN by IP unicast (541). The node 121 sets a retransmission timer for the nodes 122 and 141. Note that since the node 111 has already received ACK (513) for the data, no retransmission timer is set.
- the node 112 after receiving the data, the node 112 returns ACK (Complete) to the node 111 (515).
- ACK Complete
- the node 111 cancels the retransmission timer for the node 112.
- the node 131 After receiving the data, the node 131 returns ACK (Pending) to the node 111 (532). When node 111 receives the ACK, it cancels the retransmission timer to node 131. The node 131 further transmits ACK (Pending) to the node 141 which is the parent node of the redundant transfer path (533). The node 141 records the received ACK.
- the node 122 After receiving the data, the node 122 returns ACK (Complete) to the node 121 (525). When the node 121 receives the ACK, the node 121 cancels the retransmission timer for the node 122.
- the node 141 When the node 141 receives the data, the node 141 returns ACK (Pending) to the node 121 (542). When node 121 receives the ACK, node 121 cancels the retransmission timer to node 141. The node 141 further transmits ACK (Pending) to the node 131 which is the parent node of the redundant transfer path (543). The node 131 records the received ACK.
- the node 131 transfers the received data to the receiving node 132 on its own LAN using IP multicast (534), and sets a retransmission timer for the node 132.
- the node 141 transfers the received data to the receiving node 142 on its own LAN using the IP multicast (544), and sets a retransmission timer for the node 142.
- the node 132 when receiving the data, the node 132 returns an ACK (Complete) to the node 131 (535). When the node 131 receives the ACK, the node 131 cancels the retransmission timer for the node 132. Since the node 131 has received ACK (Complete) from all receiving nodes under the transfer path, the node 131 transmits ACK (Complete) to the node 111 (536). When the node 111 receives ACK (Compete) from the node 131, it similarly receives ACK (Complete) from all receiving nodes under the transfer path, and therefore transmits ACK (Complete) to the node 101 (516).
- the node 142 When the node 142 receives the data, it returns an ACK (Complete) to the node 141 (545). When the node 141 receives the ACK, the node 141 cancels the retransmission timer for the node 142. Since the node 141 has received ACK (Complete) from all receiving nodes under the transfer path, the node 141 transmits ACK (Complete) to the node 121 (546). When the node 121 receives ACK (Compete) from the node 141, it similarly receives ACK (Complete) from all receiving nodes under the transfer path, and therefore transmits ACK (Complete) to the node 101 (526). The node 101 receives ACK (Complete) from all receiving nodes under the transfer path, and confirms that all receiving nodes in the network have received data.
- ACK Complete
- the origin node 101 transmits data to the receiving node 102 on its own LAN, and the nodes 111 and 121 on different LANs (6101, 6201, 6301). However, due to a link failure, the data 6201 sent to the node 121 is discarded by the router 201 and does not reach the node 121.
- the node 101 sets a retransmission timer for the nodes 111, 121, and 102.
- the node 102 responds with ACK (Complete) to the node 101 (6102).
- ACK Complete
- node 101 cancels the retransmission timer to node 102.
- the node 111 returns an ACK (Pending) response to the nodes 101 and 121 (6302 and 6303).
- node 101 cancels the retransmission timer to node 111.
- the node 121 records that the ACK is received from the node 111 which is the parent node of the redundant system for the data which has not been received.
- the node 111 transfers data to the receiving node 112 on its own LAN using IP multicast (6305). Further, data transfer is also performed to the transfer node 131 on a different LAN by IP unicast (6304).
- the node 111 sets a retransmission timer for the nodes 112 and 131. Furthermore, a retransmission timer is also set for the node 121 which is a redundant child node.
- the node 112 responds with ACK (Complete) to the node 111 (6306).
- ACK Consumer
- node 111 cancels the retransmission timer for node 112.
- the node 131 returns ACK (Pending) to the node 111 (6307).
- ACK Pending is also transmitted to the node 141 which is a child node of the redundant system (6308).
- the node 131 transfers the data to the node 132 on its own LAN by IP multicast (6309).
- the node 131 sets a retransmission timer for the node 132 and the node 141 which is a redundant child node.
- the node 111 When the node 111 receives the ACK from the node 131, the node 111 cancels the retransmission timer to the node 131.
- the node 141 records that the ACK of the data that has not been received yet is received from the node 131 that is the parent node of the redundant system.
- the node 101 retransmits data to the node 121 by firing a retransmission timer to the node 121 (6202). However, this data is also discarded due to a failure and does not reach the node 121.
- the node 111 also fires a retransmission timer to the node 121 and transmits data to the node 121 (6312).
- the node 132 transmits ACK (Complete) to the node 131 (6310).
- ACK Complete
- the node 131 receives the ACK, it receives the ACK (Complete) from all subordinate receiving nodes, and therefore transmits the ACK (Complete) to the node 111 (6311).
- the node 121 when receiving data from the node 111, the node 121 transmits ACK (Pending) to the normal parent node 101 and the redundant parent node 111 (6203 and 6204). . Since the node 121 has received data from the redundant parent node 111 instead of the normal parent node 101, the node that is the data reception source node (redundant parent node) in response to the ACK (Pending) to the node 111 111 and the information of the node 101 which is a normal parent node are added. The 6203 ACK transmitted to the node 101 is discarded due to a failure and does not reach the node 101.
- Node 111 receives ACK (Pending) from node 121.
- the node 111 transfers the ACK to the node 101 which is the normal parent node of the node 121 (6205). ).
- the node 101 When the node 101 receives the ACK (Pending) of the node 121 transferred from the node 111, the node 101 cancels the retransmission timer to the node 121.
- the node 121 transfers the received data to the receiving node 122 on its own LAN by IP multicast (6206). Further, the data is transferred to the node 141 by IP unicast (6207). The node 121 sets a retransmission timer for the node 122 and the node 141.
- the node 122 when the node 122 receives the data, the node 122 transmits ACK (Complete) to the node 121 (6208). When the node 121 receives the ACK, the node 121 cancels the retransmission timer to the node 122.
- ACK Complete
- the node 141 transmits ACK (Pending) to the node 121 and the node 131 which is the parent node of the redundant system (6209, 6210).
- ACK Send
- the node 131 cancels the retransmission timer to the node 141.
- the node 141 transfers the data to the receiving node 142 on its own LAN using IP multicast (6211).
- the node 142 when the node 142 receives the data, it returns an ACK (Complete) to the node 141 (6212).
- the node 141 confirms that the ACK (Complete) has been received from all subordinate recipients, and transmits ACK (Complete) to the node 121 and the node 131 which is the redundant parent node (6213). 6214).
- the node 121 confirms that ACK (Complete) has been received from all receiving nodes under its control, and transmits ACK (Complete) to the normal parent node 101 and the redundant parent node 111 (6215, 6216). Since the node 121 receives the data from the redundant parent node 111 instead of the normal parent node 101, the node 121 also receives the ACK (Complete) to the node 111 from the node 111 that is the data receiving node. The information of the node 101 which is the normal parent node is added.
- ACK (6215) to the node 101 is discarded due to a failure and does not reach the node 101.
- Node 111 receives ACK (Complete) from node 121.
- ACK Complete
- the node 111 transfers the ACK to the node 101 which is the normal parent node of the node 121 (6217). .
- the node 101 When the node 101 receives the ACK (Complete) of the node 121 transferred from the node 111, it confirms that the ACK (Complete) has been received from all the receiving nodes under its control, and all the receiving nodes in the network have received it normally. Recognize that.
- the communication node device may be realized by a CPU (Central Processing Unit) reading and executing an operation program or the like stored in a storage unit, or configured by hardware. May be. Only some functions of the above-described embodiments can be realized by a computer program.
- CPU Central Processing Unit
- a multicast communication method in a network composed of a plurality of communication nodes When data is transferred to a subordinate node along the normal delivery route, a retransmission timer is set for the child node of the redundant delivery route, A multicast communication method characterized by sending a reception confirmation message to both a parent node of a normal distribution route and a parent node of a redundant distribution route when data is received.
- the node itself is a forwarding node in the distribution route, when receiving data, the first reception confirmation message is sent to both the parent node of the normal distribution route and the parent node of the redundant distribution route, If it is a terminal node in the distribution route, when receiving data, it sends a second receipt confirmation message to the normal parent node, Note that when the second receipt confirmation message is received from all the child nodes of its own delivery route, the second receipt confirmation message is sent to the parent nodes of both the normal delivery route and the redundant delivery route.
- the multicast communication method according to 1 or appendix 2.
- a communication node device constituting a communication system that performs multicasting, When data is transferred to a subordinate node along the normal delivery route, a retransmission timer is set for the child node of the redundant delivery route, A communication node device that, when receiving data, sends a reception confirmation message to both a parent node of a normal distribution route and a parent node of a redundant distribution route.
- the node itself is a forwarding node in the distribution route, when receiving data, the first reception confirmation message is sent to both the parent node of the normal distribution route and the parent node of the redundant distribution route, If it is a terminal node in the distribution route, when receiving data, it sends a second receipt confirmation message to the normal parent node, Note that when the second receipt confirmation message is received from all the child nodes of its own delivery route, the second receipt confirmation message is sent to the parent nodes of both the normal delivery route and the redundant delivery route. 4.
- the communication node device according to 4 or appendix 5.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
まず、障害が発生していない正常時のデータ転送の手順について、図5~10を用いて説明する。図中の矢印線は、ノード間のパケット(データもしくはACK)の流れを示し、実線矢印はIPユニキャストでの送信、点線矢印はIPマルチキャストでの送信を示している。
次に、ルータ201と203間のリンク障害が発生し、ノード101と121の通信が不通となった場合の転送シーケンスについて図11~19を使い説明する。
正常系配信経路に沿って配下のノードへデータを転送した場合、冗長系配信経路の子ノードに対しても再送タイマーを設定し、
データを受信した場合に、正常系配信経路の親ノードと冗長系配信経路の親ノードの両方に受信確認メッセージを送ることを特徴とするマルチキャスト通信方法。
冗長系配信経路の親ノードからデータを受信した場合、前記受信確認メッセージに、送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報を付加し、
送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報が付加された受信確認メッセージを受信した場合、自身が当該受信確認メッセージに付加された送信元である冗長系配信経路の親ノードと一致したならば、当該受信確認メッセージに付加された正常系配信経路の親ノードへ当該受信確認メッセージを転送する
ことを特徴とする付記1に記載のマルチキャスト通信方法。
自身が配信経路における転送ノードである場合、データを受信した際に、正常系配信経路の親ノードと、冗長系配信経路の親ノードの両方に第1の受信確認メッセージを送り、
自身が配信経路における末端ノードである場合、データを受信した際に、正常系親ノードに第2の受信確認メッセージを送り、
自身の配信経路の全ての子ノードから第2の受信確認メッセージを受信した場合、正常系配信経路と冗長系配信経路の両方の親ノードに第2の受信確認メッセージを送る
ことを特徴とする付記1又は付記2に記載のマルチキャスト通信方法。
マルチキャストを行う通信システムを構成する通信ノード装置であって、
正常系配信経路に沿って配下のノードへデータを転送した場合、冗長系配信経路の子ノードに対しても再送タイマーを設定し、
データを受信した場合に、正常系配信経路の親ノードと冗長系配信経路の親ノードの両方に受信確認メッセージを送る
ことを特徴とする通信ノード装置。
冗長系配信経路の親ノードからデータを受信した場合、前記受信確認メッセージに、送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報を付加し、
送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報が付加された受信確認メッセージを受信した場合、自身が当該受信確認メッセージに付加された送信元である冗長系配信経路の親ノードと一致したならば、当該受信確認メッセージに付加された正常系配信経路の親ノードへ当該受信確認メッセージを転送する
ことを特徴とする付記4に記載の通信ノード装置。
自身が配信経路における転送ノードである場合、データを受信した際に、正常系配信経路の親ノードと、冗長系配信経路の親ノードの両方に第1の受信確認メッセージを送り、
自身が配信経路における末端ノードである場合、データを受信した際に、正常系親ノードに第2の受信確認メッセージを送り、
自身の配信経路の全ての子ノードから第2の受信確認メッセージを受信した場合、正常系配信経路と冗長系配信経路の両方の親ノードに第2の受信確認メッセージを送る
ことを特徴とする付記4又は付記5に記載の通信ノード装置。
マルチキャスト通信のプログラムであって、
コンピュータに、
正常系配信経路に沿って配下のノードへデータを転送した場合、冗長系配信経路の子ノードに対しても再送タイマーを設定する処理、
データを受信した場合に、正常系配信経路の親ノードと冗長系配信経路の親ノードの両方に受信確認メッセージを送る送信処理、
を実行させることを特徴とするプログラム。
前記コンピュータに、
冗長系配信経路の親ノードからデータを受信した場合、前記受信確認メッセージに、送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報を付加する処理、
送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報が付加された受信確認メッセージを受信した場合、自身が当該受信確認メッセージに付加された送信元である冗長系配信経路の親ノードと一致したならば、当該受信確認メッセージに付加された正常系配信経路の親ノードへ当該受信確認メッセージを転送する処理、
をさらに実行させることを特徴とする付記7に記載のプログラム。
前記コンピュータに、
自身が配信経路における転送ノードである場合、データを受信した際に、正常系配信経路の親ノードと、冗長系配信経路の親ノードの両方に第1の受信確認メッセージを送る処理、
自身が配信経路における末端ノードである場合、データを受信した際に、正常系親ノードに第2の受信確認メッセージを送る処理、
自身の配信経路の全ての子ノードから第2の受信確認メッセージを受信した場合、正常系配信経路と冗長系配信経路の両方の親ノードに第2の受信確認メッセージを送る処理、
をさらに実行させることを特徴とする付記7又は付記8に記載のプログラム。
201~205 ルータ
Claims (9)
- 複数の通信ノードで構成されたネットワークにおけるマルチキャスト通信方法であって、
正常系配信経路に沿って配下のノードへデータを転送した場合、冗長系配信経路の子ノードに対しても再送タイマーを設定し、
データを受信した場合に、正常系配信経路の親ノードと冗長系配信経路の親ノードの両方に受信確認メッセージを送る
ことを特徴とするマルチキャスト通信方法。 - 冗長系配信経路の親ノードからデータを受信した場合、前記受信確認メッセージに、送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報を付加し、
送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報が付加された受信確認メッセージを受信した場合、自身が当該受信確認メッセージに付加された送信元である冗長系配信経路の親ノードと一致したならば、当該受信確認メッセージに付加された正常系配信経路の親ノードへ当該受信確認メッセージを転送する
ことを特徴とする請求項1に記載のマルチキャスト通信方法。 - 自身が配信経路における転送ノードである場合、データを受信した際に、正常系配信経路の親ノードと、冗長系配信経路の親ノードの両方に第1の受信確認メッセージを送り、
自身が配信経路における末端ノードである場合、データを受信した際に、正常系親ノードに第2の受信確認メッセージを送り、
自身の配信経路の全ての子ノードから第2の受信確認メッセージを受信した場合、正常系配信経路と冗長系配信経路の両方の親ノードに第2の受信確認メッセージを送ることを特徴とする請求項1又は請求項2に記載のマルチキャスト通信方法。 - マルチキャストを行う通信システムを構成する通信ノード装置であって、
正常系配信経路に沿って配下のノードへデータを転送した場合、冗長系配信経路の子ノードに対しても再送タイマーを設定し、
データを受信した場合に、正常系配信経路の親ノードと冗長系配信経路の親ノードの両方に受信確認メッセージを送る
ことを特徴とする通信ノード装置。 - 冗長系配信経路の親ノードからデータを受信した場合、前記受信確認メッセージに、送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報を付加し、
送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報が付加された受信確認メッセージを受信した場合、自身が当該受信確認メッセージに付加された送信元である冗長系配信経路の親ノードと一致したならば、当該受信確認メッセージに付加された正常系配信経路の親ノードへ当該受信確認メッセージを転送する
ことを特徴とする請求項4に記載の通信ノード装置。 - 自身が配信経路における転送ノードである場合、データを受信した際に、正常系配信経路の親ノードと、冗長系配信経路の親ノードの両方に第1の受信確認メッセージを送り、
自身が配信経路における末端ノードである場合、データを受信した際に、正常系親ノードに第2の受信確認メッセージを送り、
自身の配信経路の全ての子ノードから第2の受信確認メッセージを受信した場合、正常系配信経路と冗長系配信経路の両方の親ノードに第2の受信確認メッセージを送る
ことを特徴とする請求項4又は請求項5に記載の通信ノード装置。 - マルチキャスト通信のプログラムであって、
コンピュータに、
正常系配信経路に沿って配下のノードへデータを転送した場合、冗長系配信経路の子ノードに対しても再送タイマーを設定する処理、
データを受信した場合に、正常系配信経路の親ノードと冗長系配信経路の親ノードの両方に受信確認メッセージを送る送信処理、
を実行させることを特徴とするプログラム。 - 前記コンピュータに、
冗長系配信経路の親ノードからデータを受信した場合、前記受信確認メッセージに、送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報を付加する処理、
送信元である冗長系配信経路の親ノードと、正常系配信経路の親ノードの情報が付加された受信確認メッセージを受信した場合、自身が当該受信確認メッセージに付加された送信元である冗長系配信経路の親ノードと一致したならば、当該受信確認メッセージに付加された正常系配信経路の親ノードへ当該受信確認メッセージを転送する処理、
をさらに実行させることを特徴とする請求項7に記載のプログラム。 - 前記コンピュータに、
自身が配信経路における転送ノードである場合、データを受信した際に、正常系配信経路の親ノードと、冗長系配信経路の親ノードの両方に第1の受信確認メッセージを送る処理、
自身が配信経路における末端ノードである場合、データを受信した際に、正常系親ノードに第2の受信確認メッセージを送る処理、
自身の配信経路の全ての子ノードから第2の受信確認メッセージを受信した場合、正常系配信経路と冗長系配信経路の両方の親ノードに第2の受信確認メッセージを送る処理、
をさらに実行させることを特徴とする請求項7又は請求項8に記載のプログラム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/401,534 US9425970B2 (en) | 2012-05-21 | 2013-05-17 | Multicast communication method, communication node device and program |
JP2014516780A JPWO2013176051A1 (ja) | 2012-05-21 | 2013-05-17 | マルチキャスト通信方法、通信ノード装置及びプログラム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012115398 | 2012-05-21 | ||
JP2012-115398 | 2012-05-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013176051A1 true WO2013176051A1 (ja) | 2013-11-28 |
Family
ID=49623745
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/063787 WO2013176051A1 (ja) | 2012-05-21 | 2013-05-17 | マルチキャスト通信方法、通信ノード装置及びプログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US9425970B2 (ja) |
JP (1) | JPWO2013176051A1 (ja) |
WO (1) | WO2013176051A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150381377A1 (en) * | 2014-06-26 | 2015-12-31 | Qualcomm Technologies International, Ltd. | Method and apparatus for managing addresses and connectivity arrangements for transporting multicast data in a wireless network |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06315060A (ja) * | 1993-04-28 | 1994-11-08 | Matsushita Electric Ind Co Ltd | 同報通信装置 |
JP2007228064A (ja) * | 2006-02-21 | 2007-09-06 | Mitsubishi Electric Corp | ネットワークシステムおよび通信装置 |
JP2007535879A (ja) * | 2004-04-30 | 2007-12-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | エンド・ツー・エンドの信頼性のあるグループ通信のための方法および装置 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7289433B1 (en) * | 2000-10-24 | 2007-10-30 | Nortel Networks Limited | Method and system for providing robust connections in networking applications |
JP4637832B2 (ja) * | 2004-05-24 | 2011-02-23 | パナソニック株式会社 | 端末機能を有する無線lan装置及び基地局機能を有する無線lan装置、並びに、この無線lan装置を備えた無線ネットワーク |
US7620409B2 (en) * | 2004-06-17 | 2009-11-17 | Honeywell International Inc. | Wireless communication system with channel hopping and redundant connectivity |
CN101808044B (zh) * | 2010-03-19 | 2013-10-16 | 中兴通讯股份有限公司 | 一种流控制传输协议多归属选路的方法及装置 |
CN102694713B (zh) * | 2011-03-21 | 2015-08-05 | 鸿富锦精密工业(深圳)有限公司 | 网络通信多通路选择方法及系统 |
CN102204188B (zh) * | 2011-05-25 | 2013-03-20 | 华为技术有限公司 | 虚拟网络单元中的路由计算方法和主节点设备 |
US8630291B2 (en) * | 2011-08-22 | 2014-01-14 | Cisco Technology, Inc. | Dynamic multi-path forwarding for shared-media communication networks |
US20140241315A1 (en) * | 2011-09-30 | 2014-08-28 | Huaning Niu | Radio access network (ran) for peer-to-peer (p2p) communication |
US9596182B2 (en) * | 2013-02-12 | 2017-03-14 | Adara Networks, Inc. | Controlling non-congestion controlled flows |
-
2013
- 2013-05-17 WO PCT/JP2013/063787 patent/WO2013176051A1/ja active Application Filing
- 2013-05-17 US US14/401,534 patent/US9425970B2/en active Active
- 2013-05-17 JP JP2014516780A patent/JPWO2013176051A1/ja active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06315060A (ja) * | 1993-04-28 | 1994-11-08 | Matsushita Electric Ind Co Ltd | 同報通信装置 |
JP2007535879A (ja) * | 2004-04-30 | 2007-12-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | エンド・ツー・エンドの信頼性のあるグループ通信のための方法および装置 |
JP2007228064A (ja) * | 2006-02-21 | 2007-09-06 | Mitsubishi Electric Corp | ネットワークシステムおよび通信装置 |
Non-Patent Citations (1)
Title |
---|
YOSHIHIKO IKENAGA: "Overlay Multicast System with Adaptability to Heterogeneous and Dynamic Environments", IPSJ SIG NOTES, vol. 2007, no. 24, 9 March 2007 (2007-03-09), pages 13 - 18 * |
Also Published As
Publication number | Publication date |
---|---|
US20150139226A1 (en) | 2015-05-21 |
JPWO2013176051A1 (ja) | 2016-01-12 |
US9425970B2 (en) | 2016-08-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1747644B1 (en) | Method and apparatus for group communication with end-to-end reliability | |
JP5691703B2 (ja) | マルチキャストネットワークシステム | |
CN103262457B (zh) | 共享介质网络中的中继节点 | |
JP2013542662A5 (ja) | ||
US9094224B2 (en) | Acknowledged multicast convergence | |
WO2007095542A2 (en) | Dynamic multicasting scheme for mesh networks | |
WO2012068996A1 (zh) | 链路状态检测方法和装置 | |
JP2006101471A (ja) | マルチキャスト冗長経路ルータ、マルチキャスト冗長化方式 | |
JP2011515057A5 (ja) | ||
EP2465233B1 (en) | Router and method for graceful restart | |
JP2010183143A (ja) | Ipネットワークシステム | |
JP2005252670A (ja) | 通信システムおよびバックアップサーバならびに通信制御装置 | |
Scott et al. | Robust communications for disconnected, intermittent, low-bandwidth (DIL) environments | |
JP2006074132A (ja) | マルチキャスト通信方法及びゲートウェイ装置 | |
CN103227724A (zh) | 一种在vrrp网络环境下实现pim组播的方法及装置 | |
JP2010045732A (ja) | マルチキャストパケット転送装置およびマルチキャストパケット転送方法 | |
WO2013008890A1 (ja) | 通信システム、通信経路制御方法及び通信装置 | |
WO2013176051A1 (ja) | マルチキャスト通信方法、通信ノード装置及びプログラム | |
JP2007228293A (ja) | ノード装置および通信システム | |
JP5287759B2 (ja) | ネットワークシステム及び経路検索方法 | |
JP3965202B1 (ja) | ネットワーク通信機器およびリング型ネットワーク用通信プログラム。 | |
Papán et al. | The new PIM-SM IPFRR mechanism | |
JP2009065617A (ja) | Lan通信システム | |
JP4609862B2 (ja) | ネットワーク中継方法、ネットワーク要素およびネットワーク中継システム | |
JP2007074313A (ja) | ネットワーク冗長制御方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13794024 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2014516780 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14401534 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13794024 Country of ref document: EP Kind code of ref document: A1 |