JP5000618B2 - IP multicast communication monitoring method and system - Google Patents

Description

  The present invention is a network composed of a plurality of nodes connecting a plurality of distribution servers and a plurality of viewer terminals, and the IP multicast is confirmed when the IP multicast adjacency confirmation is completed between the plurality of nodes. Source information (S) indicating that the transfer request is sent from a specific distribution server among a plurality of nodes performing IP multicast communication via a route (hereinafter referred to as an acceptance route) for which the transfer request is accepted. ) And specific group information (G) and whether or not IP multicast communication having information on a specific test target (S, G) communicates with a plurality of viewer terminals to be reached from a specific distribution server. The present invention relates to an IP multicast communication monitoring method and system to be confirmed.

  A conventional IP multicast communication monitoring method will be described (for example, see Non-Patent Documents 1 and 2). The first conventional method example based on the technology disclosed in Non-Patent Document 1 is a “block diagram of an example of a conventional IP multicast arrival monitoring method (part 1)” using a PING address for IP multicast. This is shown in FIG. In addition, the second conventional method example based on the technology disclosed in Non-Patent Document 2 is a “block diagram of an example of a conventional IP multicast arrival monitoring method (part 2)” using ssmping. It shows.

5 and 6,
101-1, 101-2 are distribution servers MS1, MS2,
110-1 and 110-2 are viewer terminals h1 and h2,
115 is its own network area,
116 is a distribution server side,
117 is a user side (that is, viewer terminal side),
118 and 119 are network boundary points,
120 is a source node A;
121 and 122 are relay nodes B, C,
123 and 124 are edge nodes D, E,
Reference numerals 140-1 to 140-6 denote multicast routes addressed to the same group (G) whose transmission source information (S) is MS1 (101-1).

  Here, as a precondition, in this example, a multicast control protocol between nodes is described using PIM-SSM, and a terminal viewing management protocol is described using MLDv2. Further, in the multicast route of 140-1 to 140-6, Neighber is established in the PIM-Hello between adjacent nodes of the source node A (120) to the edge node E (124) (establishment of adjacency confirmation), Furthermore, it is assumed that the confirmation of PIM-Join is completed and the request procedure from the viewer terminal by MLDv2 is completed (establishment of consent route).

  Referring to the sequence shown in FIG. 5, PING addressed to the IP multicast group is transmitted from the distribution server MS1 (101-1) to the group (G). The PING addressed to the IP multicast group is copied by the relay node C (122) via the originating node A (120) and arrives at the edge node D (123) and the edge node E (124), respectively. The edge node D (123) transmits the PING addressed to the IP multicast group to the viewer terminal h2 (110-2) requesting viewing by MLDv2, and the viewer terminal h2 (110-2) is the distribution server of the transmission source Report the reply of the PING address to the IP multicast group to MS1 (101-1). Also, the edge node E (124) transmits the PING addressed to the IP multicast group to the viewer terminal h1 (110-1) requesting viewing by MLDv2, and the viewer terminal h1 (110-1) is the transmission source. A reply of the PING addressed to the IP multicast group is reported to the distribution server MS1 (101-1).

  Note that the reply to the IP multicast group-addressed PING returned from the viewer terminal h1 (110-1) is sent to the viewer via the edge node E (124), the relay node C (122), and the source node A (120). Arrives at terminal MS1. In parallel, the reply to the IP multicast group-addressed PING returned from the viewer terminal h2 (110-2) passes through the edge node D (123), the relay node C (122), and the originating node A (120). And arrives at the distribution server MS1. By this procedure, the distribution server MS1 confirms the IP multicast communication (see, for example, Non-Patent Document 1).

  On the other hand, in the case of confirming the communication by the viewer terminal h1 using ssmping, referring to the sequence shown in FIG. 6, the smpmping is performed from the viewer terminal h1 (110-1) to the edge node E (124). Send to. Ssmping arrives at the distribution server MS1 via the edge node E (124), the relay node C (122), and the originating node A (120). The distribution server MS1 (101-1) distributes the IP multicast packet to the group (G) to the viewer terminal h1 (110-1) upon receipt of the ssmping. The IP multicast packet distributed from the distribution server MS1 (101-1) is sent to the viewer terminal h1 (110-1) via the originating node A (120), the relay node C (122), and the edge node E (124). To arrive. Through this procedure, the viewer terminal h1 confirms the IP multicast communication (see, for example, Non-Patent Document 2).

Kamil Sarac and one other, "draft-sarac-mping-00.txt. MPING Protocol Operation", [online], June 2004, IETF, [Search on December 21, 2007], Internet <URL: http /// ietfreport.isoc.org/all-ids/draft-sarac-mping-00.txt> Pavan Namburi and 2 others, “433-059 SSM-PING: A PING UTILITY FOR SOURCE SPECIFIC MULTICAST 4 SSM-Ping”, [online], November 22, 2004, CIIT 2004, [December 21, 2007 Search], Internet <URL: http://www.actapress.com/Content_Of_Proceeding.aspx? ProceedingID = 266 # pages>, <URL: http://imj.gate.edu/papers/CIIT-04b.pdf.gz>

  Here, in the conventional technique described above, when confirming the IP multicast communication, a route for passing an IP multicast packet (hereinafter referred to as multicast tree) is set by a user request, and the network boundary points (118, 119) are set. Since the communication exceeds the limit, there is a problem that it is not possible to confirm the communication closed in the local network area (115). In addition, since it is difficult to check the communication in units of source information (S) and specific group information (G), it is not possible to grasp a timely route for passing an IP multicast packet (that is, multicast tree). There is also a problem that route monitoring is difficult. Furthermore, there is a problem that the IP multicast bandwidth usage status cannot be confirmed in a timely manner.

  Therefore, a passing route number that can identify the passing of the own forwarding node is assigned to the IP multicast maintenance packet, forwarded together with the IP multicast packet to one or more viewer terminals, and can be connected to each node in the network. A conservative OpS is a method of monitoring the IP multicast communication by acquiring the information of the path communication from each node (reference document as prior art: Japanese Patent Application No. 2008-43300).

  Here, FIG. 7 to FIG. 10 are block diagrams showing examples of the IP multicast maintenance packet insertion function of the originating node for explaining the principle of the above-described prior art (hereinafter collectively referred to as “prior art”). FIG. 11 is a diagram showing information in the IP multicast maintenance packet in the embodiment of the IP multicast arrival monitoring method of the prior application technique. FIG. 12 is a block diagram showing an example of bandwidth usage status confirmation in the prior art IP multicast arrival monitoring system. FIG. 13 is a block diagram regarding the IP multicast maintenance packet insertion function of the originating node that can be inferred from the principle of the prior art IP multicast arrival monitoring system. The multicast control protocol between nodes is described using PIM-SSM, and the terminal viewing management protocol is described using MLDv2. In addition, the multicast routes 140-1 to 140-6 are established in the PIM-Hello between the adjacent nodes of the node A (120) to the node E (124), the confirmation of the PIM-Join is completed, and the viewer by the MLDv2 It is assumed that the required procedures from have been completed.

7 to 13,
013 is an IP multicast maintenance packet buffer,
015 is a transmission control unit,
016 is a communication data buffer;
030 is the input packet,
032 is the output packet,
101-1 to 101-2 are distribution servers MS1 to MS2,
110-1 to 110-2 are viewer terminals h1 to h2,
115 is its own network area,
116 is a distribution server side,
117 is a user side (that is, viewer terminal terminal side),
118 and 119 are network boundary points,
120 is a source node A;
121-122 are relay nodes B-C,
123 to 124 are edge nodes D to E,
140-1 to 140-6 are multicast routes addressed to the same group (G) whose source information (S) is MS1 (101-1),
150 is a maintenance OpS,
160 is a breakdown of IP multicast maintenance packet information,
161 represents detailed information in the test mode (TM).

  First, an embodiment of an IP multicast communication monitoring method in which the principle of the prior art is applied at a source node will be described with reference to FIGS. In the description, the processing for the multicast route (140-1 to 140-6) originating from MS1 is taken as an example.

  The IP multicast packet distributed from the distribution server MS1 (101-1) passes through the source node A (120) according to the multicast route (140-1 to 140-6) of the MS1, and then passes through the relay node C (122). After copying, it is transmitted to the edge node D (123) and the edge node E (124) and distributed to the viewer terminals h1 and h2.

  First, the processing of the originating node A (120) will be described as “processing 11” (see FIG. 7).

[Process 11]
The originating node A (120) performs the following [Processing 11-a] to [Processing 11-c] in a steady state, and [Processing 11-d] is performed when an inquiry from the maintenance OpS is received.

[Process 11-a]
The source information S and group number G (hereinafter referred to as (S, G) or simply S, G) of the passing IP multicast packet are confirmed.

[Process 11-b]
A corresponding (S, G) IP multicast maintenance packet is generated and inserted into the multicast route (140-2). At the time of generation, the test mode (TM), sequence number (SN), and passing route number (RN) are inserted when the packet is inserted. ) Is added to the payload in the packet. In addition, the originating node A (120) gives a test packet identifier (TPM) that can identify an IP multicast maintenance packet to an empty area of the header in the IP multicast maintenance packet (160).

[Process 11-c]
The (S, G), test mode (TM), and sequence number (SN) of the inserted IP multicast maintenance packet are reported to the maintenance OpS.

[Process 11-d]
For (S, G) corresponding to the IP multicast maintenance packet transmitted to the multicast route (140-2), the PIM-Join / Prune transmission state from the multicast route (140-2) is confirmed.

  Next, the processing of the relay node C (122) will be described as “processing 12” (see FIG. 8).

[Process 12]
In the relay node C (122), the following [Processing 12-a] is performed in a steady state, and [Processing 12-b] to [Processing 12-d] are performed when there is an inquiry from the maintenance OpS.

[Process 12-a]
The relay node C (122) refers to the test packet identifier (TPM), confirms that it is an IP multicast maintenance packet, assigns a passing route number (RN), and sends multicast routes (140-3) and (140- 5) Copy and transfer.

[Process 12-b]
The PIM-Hello is confirmed between the originating node A (120), between the edge nodes E (124) and between the edge nodes D (123).

[Process 12-c]
For (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-2), the PIM-Join / Prune reception status from the multicast routes (140-3) and (140-4) is confirmed.

[Process 12-d]
For (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-2), the PIM-Join / Prune transmission status to the multicast route (140-2) is confirmed.

  Next, the processing of the edge node D (123) will be described as “processing 13” (see FIG. 9).

[Process 13]
In the edge node D (123), the following [Process 13-a] is performed in a steady state, and [Process 13-b] to [Process 13-d] are performed when an inquiry is made from the maintenance OpS.

[Process 13-a]
The edge node D (123) refers to the test packet identifier (TPM), extracts only the IP multicast maintenance packet received from the multicast route (140-5), and obtains the sequence number (SN) and transit route number (RN). Confirm and report to maintenance OpS.

[Process 13-b]
Regarding (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-5), the transmission state of the MLDv2: Query to the viewer terminal h2 (110-2) is confirmed.

[Process 13-c]
For (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-5), the reception status of the MLDv2: Report (Join / Leave) to the viewer terminal h2 (110-2) is confirmed.

[Process 13-d]
For (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-5), the PIM-Join / Prune transmission status to the multicast route (140-5) is confirmed.

  In the edge node E (124), the following [Process 13-a] is performed in a steady state, and [Process 13-b] to [Process 13-d] are performed when an inquiry is made from the maintenance OpS.

[Process 13-a]
The edge node E (124) refers to the test packet identifier (TPM), extracts only the IP multicast maintenance packet received from the multicast route (140-3), and obtains the sequence number (SN) and transit route number (RN). Confirm and report to maintenance OpS.

[Process 13-b]
Regarding (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-3), the transmission state of the MLDv2: Query to the viewer terminal h1 (110-1) is confirmed.

[Process 13-c]
For (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-3), the reception status of the MLDv2: Report (Join / Leave) to the viewer terminal h1 (110-1) is confirmed.

[Process 13-d]
For (S, G) corresponding to the IP multicast maintenance packet received from the multicast route (140-3), the PIM-Join / Prune transmission status to the multicast route (140-3) is confirmed.

  Next, the processing of the maintenance OpS (150) will be described as “processing 14” (see FIG. 10).

[Process 14]
In the maintenance OpS (150), the following [Processing 14-a] and [Processing 14-b] are performed.

[Process 14-a]
The maintenance OpS includes (S, G), test mode (TM), sequence number (SN) of the IP multicast maintenance packet acquired from the originating node A (120) in “Process 11-a”, and “Process 13-a”. The IP multicast maintenance packet acquired from the edge nodes D (123) and E (124) in step 3 is collated with the test mode (TM), sequence number (SN), passage route number (RN), and the arrival status of the IP multicast packet And route monitoring by grasping the IP multicast tree.

[Process 14-b]
The maintenance OpS receives an IP multicast packet as requested from the viewing host h (110) based on information from the edge nodes D (123) and E (124) in "Process 13-b" to "Process 13-d". If the arrival normality is confirmed and it is determined that there is an abnormality, the information of “Process 11-d” is transmitted to the originating node A (120) on the multicast route and the relay node C (122) is The information of “Processing 12-b to 12-d” is inquired, and fault isolation is performed.

  With reference to FIG.11 and FIG.12, the example of the band usage condition confirmation in the IP multicast arrival monitoring method which can provide the principle of a prior art is demonstrated.

  FIG. 11 shows information in the IP multicast maintenance packet indicating the principle of the present invention. When it is confirmed whether the IP multicast packet is using the required bandwidth (hereinafter also referred to as bandwidth usage status confirmation), the test mode (TM) area is used for identification.

Details of the test mode (TM) (161) show the breakdown of parameters.
MD: Mode identification (normal mode / bandwidth confirmation mode)
PST: Packet status (first packet / intermediate packet / last packet)
T: Monitoring cycle (sending time from the first packet to completion of the last packet: sec)
M: Packet length (bit)
N: Number of packets (number of packets sent within the monitoring period (T): number)

  From this parameter, the transfer bandwidth is expressed by equation (1).

  Next, the operation will be described with reference to FIG.

  In the description, an example of processing in which an IP multicast packet is transferred through the IP multicast route (140) from the MS1 will be described.

  In the case of “confirmation of bandwidth usage”, the bandwidth confirmation mode is set in the mode identification (MD) in the test mode (TM) of the IP multicast maintenance packet to be inserted at the originating node A (120).

  In the band confirmation mode, the packet status (PST), measurement interval (T), packet length (M), and number of packets (N) are set. M allows a variable value for each packet, and T and M must be set when PST = first packet.

  When the originating node A (120) starts sending an IP multicast maintenance packet in which MD = bandwidth confirmation mode and PST = first packet are set to the relay node C, the state of “bandwidth usage confirmation” is started. A (120) transmits the packet set to the number of packets (N) within the measurement interval (T).

  The edge node E (124) and the edge node D (123) confirm the transfer confirmation mode (MD) IP multicast maintenance packet in which the transferred PST is from the first packet to the last packet, and based on the extracted T, M, and N Then, the transfer bandwidth is calculated from the above equation (1), and the bandwidth usage status is confirmed.

  However, when the IP multicast maintenance packet insertion function of the originating node A (120) showing the principle of the prior art will be described with reference to FIG. 13, it may happen that traffic different from the traffic sent by the IP multicast maintenance packet is sent. sell.

  The input packet (030) composed of the IP multicast packet to be tested (S, G) and other packets (hereinafter referred to as active packets) transferred from the distribution server MS1 (101-1) is one end. It is written in the communication data buffer (016). Upon receiving the test instruction from the outside, the transmission control unit (015) receives the operation packet (030) in the communication data buffer (016) and the IP multicast maintenance packet with N = 1 to 5 in the IP multicast maintenance packet buffer (013). Is sent out as a send packet (032) from both buffers by read control. Here, since the IP multicast packet and the IP multicast maintenance packet of the test objects S and G are mixed in the monitoring cycle T in the transmission packet (032), the actual transmission traffic is expressed by the following equation. Traffic different from the traffic transmitted by the IP multicast maintenance packet is transmitted.

  As described above, according to the technique based on the prior art, the IP multicast communication monitoring technique is provided in units of source information (S) and specific group information (G). The originating node A (120) that communicates grasps the IP multicast packet for each of the transmission source information (S) and the specific group information (G) during the communication, and for each combination of the transmission source and the specific group information, the payload An IP multicast maintenance packet (160) having a storage area for a sequence number (SN) and a passage route number (RN) is generated, and a predetermined sequence number (SN) and a passage route number (RN) of its own node are stored in the storage area. And transmit to the downstream node together with the IP multicast packet. Each of the downstream nodes assigns the passing route number of the own node to the IP multicast maintenance packet and forwards it to the one or more viewer terminals together with the IP multicast packet. The maintenance OpS (150) It is possible to acquire information on path communication from each node.

  However, in the above-described prior art, since the same S and G user-issued IP multicast as the IP multicast maintenance packet is transferred in the same brain during operation, the IP multicast maintenance extracted at the receiving edge node is used. When the bandwidth used is measured based on the packet, there may be a situation where it cannot be accurately grasped. That is, there is a problem that the bandwidth usage status of the IP multicast can be confirmed in a timely manner only when the user-issued IP multicast of the same test target (S, G) does not communicate.

  In view of the above-described problems, an object of the present invention is to provide an IP multicast communication monitoring method and system for monitoring the IP multicast route communication.

According to the IP multicast communication monitoring method of the present invention, an IP multicast adjacency check is completed between a plurality of nodes in a network composed of a plurality of nodes connecting a plurality of distribution servers and a plurality of viewer terminals. The plurality of nodes include at least one source node, a plurality of relay nodes, and a plurality of edge nodes, and perform IP multicast communication via an acceptance route in which an IP multicast transfer request is accepted. Among the plurality of nodes, the IP multicast communication having the information of the test targets S and G including the transmission source information (S) and the specific group information (G) indicating transmission from a specific distribution server is In order to confirm whether or not the plurality of viewer terminals to be reached from the distribution server is communicated with the maintenance OpS, After an IP multicast maintenance packet, which is an observation packet, is inserted and forwarded together with the IP multicast packet to the originating node among the nodes located at the boundary between the distribution server and the carrier network, the destination node of the plurality of nodes In the IP multicast communication monitoring method for extracting only the IP multicast maintenance packet,
The processing of the originating node is as follows:
Of the packets transferred from the specific distribution server, the bandwidth allocation between the IP multicast packet of the test target S and G that is communicating as the test target and the active packet other than the IP multicast packet of the test target S and G is X A control step of inserting and transferring an IP multicast maintenance packet as a padding packet in the empty band of X at a speed of X / (X + Y) when Y (X and Y are natural numbers of 1 or more);
The processing of the edge node is as follows:
It includes a test target S / G extraction step of monitoring the bandwidth used and extracting the IP multicast packet of the test target S / G inserted as a padding packet.

In the IP multicast communication monitoring method of the present invention,
The source node includes a first filter, a second filter, a first fluctuation absorbing buffer, a second fluctuation absorbing buffer, a communication data buffer, an IP multicast maintenance packet buffer, and a transmission / reception control unit.
The control steps in the processing of the originating node are:
The transmission / reception control unit includes the first filter, the second filter, the first fluctuation absorbing buffer ES-A, the second fluctuation absorbing buffer ES-D, the communication data buffer, and the IP multicast maintenance packet buffer. Control
When receiving the filter control instruction from the transmission / reception control unit by the first filter, the IP multicast packets of the test target S and G among the packets transferred from the specific distribution server are filtered, and other operations are performed. Extracting the middle packet and transferring it to the first fluctuation absorbing buffer at the connection destination with the same transfer clock as the input transfer clock;
When receiving the filter control instruction from the transmission / reception control unit by the second filter, the other active packets among the packets transferred from the specific distribution server are filtered, and the IPs of the test targets S and G Extracting a multicast packet and transferring it to the second fluctuation absorbing buffer at the connection destination with the same transfer clock as the input transfer clock; and
The communication data buffer absorbs the second fluctuation of the connection destination of the IP multicast packet of the test objects S and G received by the second filter at the speed of X / (X + Y) of the input transfer clock from the first filter. Sending to the buffer;
When there is no transfer from the communication data buffer to the second fluctuation absorbing buffer by the IP multicast maintenance packet buffer, the connection destination at the speed of X / (X + Y) of the input transfer clock from the first filter. Transmitting an IP multicast maintenance packet as a padding packet to the second fluctuation absorbing buffer;
Controlling the transmission / reception control unit to read and transfer packets in the second fluctuation absorbing buffer and the first fluctuation absorbing buffer at a frequency of X: Y;
It is characterized by including.

In the IP multicast communication monitoring method of the present invention,
The edge node includes a test target S and G traffic monitoring unit, a test packet extraction unit, and a reception information processing unit,
The test object S and G extraction step in the processing of the edge node includes:
The test target S, G traffic monitoring unit monitors a packet received from the adjacent relay node, transfers the used bandwidth monitoring information of the IP multicast packet of the test target S, G to the reception information processing unit, and connects to the connection destination. Transferring the packet to the test packet extractor of
Extracting the test target S and G IP multicast packets inserted as padding packets by the test packet extraction unit and transferring them to the reception information processing unit;
It is characterized by including.

Furthermore, the IP multicast communication monitoring system of the present invention is a network composed of a plurality of nodes connecting a plurality of distribution servers and a plurality of viewer terminals, and the IP multicast adjacency confirmation is completed between the plurality of nodes. And the plurality of nodes include at least one source node, a plurality of relay nodes, and a plurality of edge nodes, and perform IP multicast communication via an acceptance route in which an IP multicast transfer request is accepted. IP multicast communication having information on test targets S and G including transmission source information (S) and specific group information (G) indicating that a plurality of nodes are transmitted from a specific distribution server, In order to confirm whether the plurality of viewer terminals to be reached from the specific distribution server are communicated with each other, the maintenance OpS More, after the IP multicast maintenance packet, which is an observation packet, is inserted and forwarded together with the IP multicast packet to the originating node among the nodes located at the boundary between the distribution server and the carrier network, In the IP multicast communication monitoring system that extracts only the IP multicast maintenance packet at the destination node,
Among the packets transferred from the specific distribution server, the originating node is a test target S, G IP multicast packet in communication and a test packet other than the test target S, G IP multicast packet in operation When bandwidth allocation is set to X: Y (X and Y are natural numbers of 1 or more), control is performed to insert an IP multicast maintenance packet as a padding packet and transfer it to the X free bandwidth at a speed of X / (X + Y). Having means,
The edge node is
It is characterized by having test target S and G extraction means for monitoring the used bandwidth and extracting the IP multicast packet of the test target S and G inserted as a padding packet.

In the IP multicast communication monitoring system of the present invention,
The control means in the source node includes a first filter, a second filter, a first fluctuation absorbing buffer, a second fluctuation absorbing buffer, a communication data buffer, an IP multicast maintenance packet buffer, and a transmission / reception control unit. Have
The transmission / reception control unit includes the first filter, the second filter, the first fluctuation absorbing buffer ES-A, the second fluctuation absorbing buffer ES-D, the communication data buffer, and the IP multicast maintenance packet buffer. Control
The first filter, when receiving a filter control instruction from the transmission / reception control unit, filters the IP multicast packets of the test target S and G among the packets transferred from the specific distribution server, and performs other operations. The middle packet is extracted and transferred to the first fluctuation absorbing buffer at the connection destination with the same transfer clock as the input transfer clock.
When the second filter receives a filter control instruction from the transmission / reception control unit, the second filter filters other active packets among the packets transferred from the specific distribution server, and the IPs of the test targets S and G Extract the multicast packet, transfer it to the second fluctuation absorbing buffer at the connection destination with the same transfer clock as the input transfer clock,
The communication data buffer absorbs the second fluctuation of the connection destination of the IP multicast packet of the test targets S and G received by the second filter at a speed of X / (X + Y) of the input transfer clock from the first filter. Send to buffer,
When there is no transfer from the communication data buffer to the second fluctuation absorbing buffer, the IP multicast maintenance packet buffer is connected to the connection destination at the speed of X / (X + Y) of the input transfer clock from the first filter. Send the IP multicast maintenance packet as a padding packet to the second fluctuation absorbing buffer,
The transmission / reception control unit controls to read and transfer packets in the second fluctuation absorbing buffer and the first fluctuation absorbing buffer at a frequency of X: Y.
It is characterized by that.

In the IP multicast communication monitoring system of the present invention,
The test target S, G extraction means in the processing of the edge node includes a test target S, G traffic monitoring unit, a test packet extraction unit, and a reception information processing unit,
The test target S, G traffic monitoring unit monitors a packet received from the adjacent relay node, transfers use band monitoring information of the IP multicast packet of the test target S, G to the reception information processing unit, and connects to the connection destination. Forward the packet to the test packet extractor of
The test packet extraction unit extracts the IP multicast packets of the test targets S and G inserted as padding packets and transfers them to the reception information processing unit.
It is characterized by that.

  According to the present invention, even when the IP multicast packets of the test targets S and G that have arrived from the distribution server to the originating node do not use the bandwidth allocated to the test targets S and G at 100%, the shortage of empty By inserting an IP multicast maintenance packet into the bandwidth as a padding packet, it is possible to satisfy the transfer of 100% of the S and G allocated bandwidth to be tested, and accurately check the status for bandwidth in a timely manner even during system operation. Will be able to.

  Hereinafter, an IP multicast arrival monitoring method and system according to an embodiment of the present invention will be described in detail with reference to the drawings. Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram relating to the IP multicast maintenance packet insertion function of the originating node showing the principle of the present invention. FIG. 2 is a block diagram relating to the IP multicast packet processing function of the edge node showing the principle of the present invention. FIG. 3 is a block diagram of an embodiment of an IP multicast arrival monitoring method showing the principle of the present invention. FIG. 4 shows information in the IP multicast maintenance packet in the embodiment of the IP multicast arrival monitoring method showing the principle of the present invention. In addition, the same reference number is attached | subjected to the same component in each figure.

  Also in this description, PIM-SSM is used as a multicast control protocol between nodes, and MLDv2 is used as a terminal viewing management protocol. Further, in the multicast routes 140-1 to 140-6, Neighber is established in the PIM-Hello between the adjacent nodes of the source node A (120) to the node E (124) (establishment of adjacency confirmation). , PIM-Join confirmation is completed, and the request procedure from the viewer terminal by MLDv2 is completed (establishment of consent route).

1-4,
a01 is the input traffic status and packet distribution from the upstream distribution server (hereinafter referred to as “input traffic“ a ””),
a02 is the output traffic status and packet distribution to the downstream relay node (hereinafter referred to as “output traffic“ a ””),
a03 is the first filter;
a04 is the second filter;
a05 is a first fluctuation absorbing buffer ES-A,
a06 is a second fluctuation absorbing buffer ES-D,
a07 is a communication data buffer;
a08 is an IP multicast maintenance packet buffer,
a09 is a transmission / reception control unit;
b01 is the input traffic status and packet distribution from the adjacent upstream relay node (hereinafter referred to as “input traffic“ b ””),
b02 is the output traffic status and packet distribution (hereinafter referred to as “output traffic“ b ””) to the downstream viewer,
b03 is a test target S, G traffic monitoring unit,
b04 is a test packet extraction unit;
b05 is a reception information processing unit;
101-1 to 101-2 are distribution servers MS1 to MS2, respectively.
110-1 to 110-2 are viewer terminals h1 to h2,
115 is its own network area,
116 is a distribution server side,
117 is a user side (that is, viewer terminal terminal side),
118 and 119 are network boundary points,
120 is a source node A;
121-122 are relay nodes B-C,
123 to 124 are edge nodes D to E,
140-1 to 140-6 are multicast routes addressed to the same group (G) whose source information (S) is MS1 (101-1),
150 is a maintenance OpS,
160 is a breakdown of IP multicast maintenance packet information,
161-1 represents detailed information in the test mode (TM).

  Also, each of the plurality of distribution servers MS1, MS2 (101-1, 101-2) establishes a route upon completion of transfer and arbitration of the IP multicast packet, and then sends the IP multicast packet to the adjacent source node A (120). It has a function to transfer.

  Each of the plurality of viewer terminals h1 and h2 has a function of receiving an IP multicast packet transferred from an adjacent edge node.

  The originating node A (120) refers to the IP multicast packet received from any of the plurality of adjacent distribution servers MS1, MS2 (101-1, 101-2) as the function similar to the prior art, and transmits the source information (S) and a function of grasping the IP multicast packet of the specific group information (G), and generating one IP multicast maintenance packet for each of the grasped source information (S) and the specific group information (G), A function to transmit to the adjacent relay node of the acceptance route to which the referred IP multicast packet is transferred, and a test mode (hereinafter referred to as TM) that can identify the test mode when generating the IP multicast maintenance packet Sequence number (SN) that can determine the order of IP multicast maintenance packets and IP multicast A function of inserting a route number (RN) information capable of grasping a route through which the maintenance packet passes into a predetermined storage area, and an IP corresponding to the accepted route after the IP multicast maintenance packet is transferred to the accepted route Source information (S) of multicast maintenance packet, specific group information (G), test mode (TM), function to report sequence number (SN) to maintenance OpS (150), source information (S) and identification By confirming whether PIM-Join and PIM-Prun, which are routing protocols for each combination of group information (G), are received from the adjacent relay node of the downstream acceptance route, the downstream adjacent relay There is a function to grasp the IP multicast transfer request from the node and the maintenance OpS (150). When the, and a function to report IP multicast forwarding requests from downstream of the adjacent relay node.

  The originating node A (120), as a function similar to the prior art, generates an IP multicast maintenance packet of the corresponding (S, G) and inserts it into the multicast route (140-2). , A test mode (TM), a sequence number (SN), and a passing route number (RN) are added to the intra-packet payload. In addition, the originating node A (120) gives a test packet identifier (TPM) for identifying an IP multicast maintenance packet to an empty area of the header in the IP multicast maintenance packet (160). This test packet identifier (TPM) is used to identify whether the packet is an IP multicast packet or an IP multicast packet in a downstream node (relay node or edge node).

  Each of the plurality of relay nodes B and C (121, 122) has the same function as the prior art, the function of transferring the IP multicast packet and the IP multicast maintenance packet transferred from the adjacent node to the adjacent node of the acceptance route, and the IP A function of assigning a passing route number (RN) of the own node that can identify passing of the own forwarding node to the predetermined storage area in the IP multicast maintenance packet when transferring the multicast maintenance packet to the adjacent node of the acceptance route; By confirming the PIM-Hello based on the routing protocol, the function of grasping the IP multicast adjacency status with the adjacent node, the PIM-Join for each combination of the source information (S) and the specific group information (G), and For PIM-Prune, the adjacent node of the downstream consent route By confirming whether or not it has been received from the network, and a PIM- for each combination of the source information (S) and the specific group information (G) When there is an inquiry from the maintenance OpS (150) and the function to grasp the IP multicast transfer request to the upstream adjacent node by confirming whether Join and PIM-Prune are transmitted to the upstream adjacent node, It has a function of reporting an IP multicast adjacency situation, an IP multicast transfer request from a downstream adjacent node, and an IP multicast transfer request to an upstream adjacent node.

  Each of the plurality of edge nodes D and E (123, 124) has the same function as the prior art, the function of extracting only the IP multicast maintenance packet from the IP multicast packets arriving from the adjacent relay node, and the extracted IP multicast maintenance. A function for confirming the source information (S), specific group information (G), test mode (TM), sequence number (SN), and transit route number (RN) in the packet and reporting to the maintenance OpS (150); By confirming whether the query of the terminal viewing management protocol for each combination of the transmission source information (S) and the specific group information (G) is transmitted to the viewer terminal corresponding to the consent route, the viewer For each combination of the function for grasping the viewing permission status to the terminal, the transmission source information (S) and the specific group information (G) A function for grasping the viewing request status from the viewer terminal by confirming whether or not the report of the terminal viewing management protocol is received from the viewer terminal corresponding to the acceptance route, the transmission source information (S), and By grasping whether or not PIM-Join and PIM-Prun for each combination of specific group information (G) are transmitted to the upstream adjacent relay node, the IP multicast transfer request to the upstream adjacent relay node is grasped. When there is an inquiry from the function and the maintenance OpS (150), the viewing permission status to the viewer terminal corresponding to the accepted route, the viewing request status from the viewer terminal, and the IP multicast to the upstream adjacent relay node A function of reporting a transfer request.

  The maintenance OpS (150) has a function similar to that of the prior art. The originating node A (120), each of the plurality of relay nodes B and C (121, 122), and the plurality of edge nodes D and E (123, 124) ), A function for transmitting / receiving information, transmission source information (S), specific group information (G), test mode (TM), sequence number (reported from the source node A (120)) SN), source information (S) that is reported from the edge node, specific group information (G), test mode (TM), sequence number (SN), and transit route number (RN) are confirmed. Thus, it has a function of confirming whether or not the IP multicast maintenance packet transmitted by the originating node A (120) has arrived at the edge node to arrive.

  The maintenance OpS (150), as a function similar to the prior art, makes an inquiry according to the necessity of information acquisition at each node, and the source node A (120) is downstream of the source node A (120). The IP multicast transfer request from the adjacent relay node is confirmed, and for each of the plurality of relay nodes B and C (121, 122), the IP multicast adjacency status grasping request and the IP from the downstream adjacent node are transmitted. The multicast transfer request and the IP multicast transfer request to the upstream adjacent node are confirmed. For each of the plurality of edge nodes D and E (123, 124), the viewing permission status to each viewer terminal is confirmed. It has a function of confirming a grasp request, a grasp request for a viewing request status from a viewer terminal, and a request for forwarding an IP multicast to an upstream adjacent relay node.

  That is, the operation of the IP multicast communication monitoring system according to the present embodiment relating to FIGS. 1 to 4 can include the same functions as those described in FIGS. 7 to 13 as the prior art. Each component of the example IP multicast communication monitoring system further has a function described below. Here, the present invention is not limited to the configuration of the present embodiment with respect to a specific originating node, a plurality of distribution servers, a plurality of relay nodes, a plurality of edge nodes, and a plurality of viewer terminals. Needless to say.

  In other words, the IP multicast arrival monitoring system according to the embodiment of the present invention is provided between a plurality of distribution servers MS1, MS2 (101-1, 101-2) and a plurality of viewer terminals h1, h2 (110-1, 110-2). In a network composed of a plurality of nodes (120 to 124) that connect to each other, the IP multicast adjacency confirmation is completed between the plurality of nodes (120 to 124), and the plurality of nodes (120 to 124) Accepted route comprising at least one source node A (120), a plurality of relay nodes B, C (121, 122), and a plurality of edge nodes D, E (123, 124), for which an IP multicast forwarding request has been accepted. Among a plurality of nodes (120 to 124) that are performing IP multicast communication via a specific distribution server MS1 (101-1) The IP multicast communication having the information of the test targets S and G including the transmission source information (S) indicating the transmission and the specific group information (G) should reach from the specific distribution server MS1 (101-1). In order to confirm whether or not the plurality of viewer terminals h1, h2 (110-1, 110-2) are communicated with each other, the maintenance OpS (150) makes a carrier network to the distribution server MS1 (101-1). After the IP multicast maintenance packet, which is an observation packet, is inserted together with the IP multicast packet and transferred to the originating node A (120) among the nodes located at the boundary of Are the edge nodes D, E located at the boundary of the carrier network with respect to the viewer terminals h1, h2 (110-1, 110-2). In 123 and 124)), it is a system for extracting only the IP multicast service packet.

  Also in the IP multicast arrival monitoring system according to the embodiment of the present invention, the distribution server MS1 (101-1), after completing the IP multicast transfer and arbitration, transmits the IP multicast to the adjacent originating node A (120) as in the prior art. ).

  In addition, the plurality of viewer terminals h1 and h2 (110-1 and 110-2) have a function of receiving an IP multicast transferred from adjacent edge nodes D and E (123 and 124), as in the prior art. Have.

  On the other hand, in the IP multicast arrival monitoring system according to the embodiment of the present invention, the source node A (120) includes the first filter (a03), the second filter (a04), and the first fluctuation absorbing buffer ES-A (a05). A second fluctuation absorbing buffer ES-D (a06), a communication data buffer (016), an IP multicast maintenance packet buffer (013), and a transmission / reception control unit (014), and a maintenance OpS (150). The transmission / reception control unit (014) receives the instruction from the first filter (a03), the second filter (a04), the first fluctuation absorbing buffer ES-A (a05), and the second fluctuation absorbing buffer ES-D (a06). , The communication data buffer (016) and the IP multicast maintenance packet buffer (013) are controlled, and the distribution server MS1 (10 -1) allocating bandwidth between the IP multicast packets of the test target S and G in communication as the test target and the active packets other than the IP multicast packet of the test target S and G as X: Y When (X and Y are natural numbers of 1 or more), an IP multicast maintenance packet is inserted as a padding packet into the X free band at a rate of X / (X + Y) and transferred. A more specific configuration will be described below.

  When receiving the filter control instruction from the transmission / reception control unit (014), the first filter (a03), among the packets transferred from the distribution server MS1 (101-1), IP multicast packets of the test targets S and G Is filtered (blocked), other active packets are extracted, and transferred to the first fluctuation absorbing buffer ES-A (a05) at the connection destination using the same transfer clock as the input transfer clock.

  When the second filter (a04) receives a filter control instruction from the transmission / reception control unit (014), the second filter (a04) filters (blocks) other active packets among the packets transferred from the distribution server MS1 (101-1). And IP multicast packets of the test objects S and G are extracted and transferred to the communication data buffer (a07) at the connection destination using the same transfer clock as the input transfer clock.

  The communication data buffer (a07) connects the IP multicast packets of the test objects S and G received by the second filter (a04) at the speed of X / (X + Y) of the input transfer clock from the first filter (a03). The second fluctuation absorbing buffer ES-D (a06) has a function of transmitting.

  The IP multicast maintenance packet buffer (a08) receives the X of the input transfer clock from the first filter (a03) when there is no transfer from the communication data buffer (a07) to the second fluctuation absorbing buffer ES-D (a06). It has a function of transmitting an IP multicast maintenance packet as a padding packet to the second fluctuation absorbing buffer ES-D (a06) at the connection destination at a speed of / (X + Y).

  Therefore, the transmission / reception control unit (a09) transfers the packets in the second fluctuation absorbing buffer ES-D (a06) and the first fluctuation absorbing buffer ES-A (a05) to X: Y under the control from the maintenance OpS (150). The function of controlling to read and transfer at a frequency of.

  Further, in the IP multicast arrival monitoring system according to the embodiment of the present invention, the edge nodes D and E (123, 124) monitor the used bandwidth according to an instruction from the maintenance OpS (150) and are inserted as padding packets. The IP multicast packets of the test targets S and G are extracted. As a more specific configuration, the edge nodes D and E (123 and 124) include a test target S and G traffic monitoring unit (b03), a test packet extraction unit (b04), and a reception information processing unit (b05). Have. In response to an instruction from the maintenance OpS (150), the reception information processing unit (b05) controls the test target S, G traffic monitoring unit (b03) and the test packet extraction unit (b04).

  The test target S and G traffic monitoring unit (b03) monitors packets received from the adjacent relay nodes B and C (121 and 122), and receives received bandwidth monitoring information of the IP multicast packets of the test targets S and G. It has a function of transferring a packet to the processing unit (b05) and a packet to the connection destination test packet extracting unit (b04).

  The test packet extraction unit (b04) has a function of extracting the IP multicast packets of the test targets S and G inserted as padding packets and transferring them to the reception information processing unit (b05).

  With reference to FIG. 1, the IP multicast packet processing function of the originating node showing the principle of the present invention will be described. As a precondition for explaining this figure, the bandwidth allocation ratio of “other packets” and “IP multicast packets of test objects S and G (hereinafter referred to as test objects S and G packets)” is 3 : 1. Input traffic “a” (a01) is transfer clock = 1 Gbps, maximum throughput (hereinafter referred to as MAX throughput) is “test target S, G packet” = 0.25 Gbps, “other packet” = 0.75 Gbps. is there. These values are only one setting example for facilitating understanding of the invention, and can be arbitrarily set by control from the maintenance OpS (150).

  Note that the actual throughput of the “test target S, G packet” during Tsec is that each of the packet “d” (packet length = M2) and the packet “j” (packet length = M4) is transferred, Suppose that

  In the first filter (a03), only the “test object S, G packet” is blocked by the filter process and transferred to the first fluctuation absorbing buffer ES-A (a05) at the transfer clock of 1 Gbps. Since the bandwidth allocation is “other packets”: “test target S, G packets” = 3: 1, the MAX throughput is 0.75 Gbps (= “other packets”).

  In the second filter (a04), only “other packets” are blocked by the filter process and transferred to the communication data buffer (a07) at the transfer clock of 1 Gbps. In the example of this figure, packets “d” and “j” are transferred. Since the bandwidth allocation is “other packets”: “test target S, G packets” = 3: 1, the MAX throughput is 0.25 Gbps (= “test target S, G packets”).

  If there is a packet that can be sent to the communication data buffer (a07), the packet is transferred to the second fluctuation absorbing buffer ES-D (a06) at a transfer clock of 0.25 Gbps. If there is no packet that can be sent to the communication data buffer (a07) (if there is a packet in the communication data buffer (a07), it waits for insertion from the IP multicast maintenance packet buffer (a08), and Read from the communication data buffer (a07) is preferentially controlled.) Inserts an IP multicast maintenance packet as a padding packet from the IP multicast maintenance packet buffer (a08).

  The transmission / reception control unit (a09) performs the read control from the first fluctuation absorbing buffer ES-A (a05) and the second fluctuation absorbing buffer ES-D (a06) with the band allocation of “other packets”: “test object S , G packet ”= 3: 1, 3: 1 read arbitration is performed, and the packet is transferred to the downstream relay node with a transfer clock of 1 Gbps.

  As a result, as shown in the output traffic “a” (a02), the “test target S, G packet” is continuously transferred at 0.25 Gbps, so that the transfer state of the usable bandwidth 100%, that is, The transfer state is as follows.

  Next, the IP multicast packet processing function of the edge node showing the principle of the present invention will be described with reference to FIG. The input traffic “b” (b01) is transfer clock = 1 Gbps, the MAX throughput is “test target S, G packet” = 0.25 Gbps, “other packet” = 0.75 Gbps, and “test target S, G The actual throughput of the “packet” is that the IP multicast maintenance packet is inserted as a padding packet in the 0.25 Gbps bandwidth allocated to the “test target S, G packet” at the originating node A (120). Thus, the “test object S, G packet” is transferred with the usable bandwidth of 100%. In the example of this figure, packet “1” (packet length = M1), packet “d” (packet length = M2), packet “2” (packet length = M3), packet “j” (packet length = M4), The transfer of the packet “3” (packet length = M5) indicates the transfer state of the usable bandwidth 100% of the “test target S, G packet”, that is, the transfer state of the following equation.

  The test target S / G traffic monitoring unit (b03) observes the traffic of the “test target S / G packet” among the packets received from the upstream relay node, and uses the received bandwidth monitoring information as the received information processing unit (b05). At the same time, the received packet is transferred to the downstream test packet extraction unit (b04) as it is.

  The test packet extraction unit (b04) extracts only the IP multicast maintenance packets of the test objects S and G inserted as padding packets, transfers them to the reception information processing unit (b05), and transfers this information to the maintenance OpS. Therefore, check the communication. In addition, the actual throughput of the “test target S, G packet” after extraction is equivalent to the input traffic “a”, and is expressed by the following equation.

  As described above, according to the IP multicast communication monitoring system of the present invention, the IP multicast packets of the test objects S and G that have arrived from the distribution server to the originating node use 100% of the bandwidth allocated to the test objects S and G. Even if there is not, by inserting the IP multicast maintenance packet as a padding packet in the insufficient empty bandwidth, it is possible to satisfy the transfer of 100% of the allocated bandwidth of the test target S and G, and even during system operation, It becomes possible to accurately check the bandwidth usage status in a timely manner.

  Thus, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present invention. Accordingly, the invention is not limited by the embodiments described above, but only by the claims.

  Communication between a specific server and a plurality of viewer terminals to be reached can be confirmed efficiently, which is useful for services using multicast communication.

It is a block diagram regarding the IP multicast packet processing function of the originating node showing the principle of the IP multicast communication monitoring system of one embodiment according to the present invention. It is a block diagram regarding the IP multicast packet processing function of the edge node which shows the principle of the IP multicast communication monitoring system of one Example by this invention. It is a block diagram of the Example of the IP multicast arrival monitoring method which shows the principle of the IP multicast communication monitoring system of one Example by this invention. It is a figure which shows the information in IP multicast maintenance packet in the Example of the IP multicast arrival monitoring method which shows the principle of the IP multicast communication monitoring system of one Example by this invention. It is a block diagram of the Example of the conventional IP multicast arrival monitoring method (the 1). It is a block diagram of the Example of the conventional IP multicast arrival monitoring method (the 2). It is a block diagram of the Example of the IP multicast arrival monitoring method of a prior application technique (the 1). It is a block diagram of the Example of the IP multicast arrival monitoring method of a prior application technique (the 2). It is a block diagram of the Example of the IP multicast arrival monitoring method of a prior application technique (the 3). It is a block diagram of the Example of the IP multicast arrival monitoring method of a prior application technique (the 4). It is a figure which shows the information in an IP multicast maintenance packet in the Example of the IP multicast arrival monitoring method of a prior application technique. It is a block diagram of the Example of the band usage condition confirmation in the Example of the IP multicast arrival monitoring method of prior application technology. It is a block diagram regarding the IP multicast maintenance packet insertion function of the originating node which can be inferred from the principle of the prior application technique.

Explanation of symbols

010 Distribution unit 011 First communication data buffer 012 Second communication data buffer 013 IP multicast maintenance packet buffer 014 Transmission / reception control unit 015 Transmission control unit 016 Communication data buffer 030 Input packet 031 Output packet 032 Output packet 101-1 and 101 -2 distribution server MS1, MS2
110-1, 110-2 Viewer terminals h1, h2
115 Local network area 116 Distribution server side 117 User side (ie viewer terminal side)
118,119 Network boundary point 120 Originating node A
121, 122 Relay nodes B, C
123, 124 Edge nodes D, E
140-1 to 140-6 Multicast route addressed to the same group (G) 150 Maintenance OpS
160 Breakdown of IP multicast maintenance packet information 161 Detailed information in test mode (TM) 161-1 Detailed information in test mode (TM) MD mode identification (normal mode / bandwidth confirmation mode)
PST packet status (first packet / intermediate packet / last packet)
T Monitoring cycle (Sending time from the first packet to the completion of the last packet: sec)
M packet length (bit)
N Number of packets (number of packets sent within the monitoring period (T): number)
a01 Input traffic “a”
a02 Output traffic “a”
a03 1st filter a04 2nd filter a05 1st fluctuation absorption buffer (ES-A)
a06 Second fluctuation absorbing buffer (ES-D)
a07 Communication data buffer a08 IP multicast maintenance packet buffer a09 Transmission / reception control unit b01 Input traffic “b”
b02 Output traffic “b”
b03 Test target S, G traffic monitoring unit b04 Test packet extraction unit b05 Receive information processing unit

Claims (6)

In a network composed of a plurality of nodes connecting a plurality of distribution servers and a plurality of viewer terminals, IP multicast adjacency confirmation is completed between the plurality of nodes, and the plurality of nodes are at least 1 Specific distribution among a plurality of nodes performing IP multicast communication via an acceptance route in which an IP multicast transfer request is accepted, consisting of one source node, a plurality of relay nodes, and a plurality of edge nodes. The IP multicast communication having the information of the test targets S and G including the transmission source information (S) and the specific group information (G) indicating that it is transmitted from the server, should be reached from the specific distribution server. In order to confirm whether or not communication with the viewer terminal is established, a maintenance OpS causes a boundary between the distribution server and the carrier network. The IP multicast maintenance packet, which is an observation packet, is inserted together with the IP multicast packet and transferred to the originating node among the nodes to be placed, and then only the IP multicast maintenance packet is received at the destination node of the plurality of nodes. In the IP multicast communication monitoring method to be extracted,
Among the packets transferred from the specific distribution server, the processing of the originating node is an IP multicast packet of the test target S and G being communicated as a test target and an operating packet other than the IP multicast packet of the test target S and G And X: Y (where X and Y are natural numbers of 1 or more), an IP multicast maintenance packet is inserted as a padding packet into the X free band at a rate of X / (X + Y) and transferred. Control steps to
The processing of the edge node is as follows:
An IP multicast communication monitoring method comprising: a test target S / G extraction step for monitoring a use band and extracting an IP multicast packet of the test target S / G inserted as a padding packet. The source node includes a first filter, a second filter, a first fluctuation absorbing buffer, a second fluctuation absorbing buffer, a communication data buffer, an IP multicast maintenance packet buffer, and a transmission / reception control unit.
The control steps in the processing of the originating node are:
The transmission / reception control unit includes the first filter, the second filter, the first fluctuation absorbing buffer ES-A, the second fluctuation absorbing buffer ES-D, the communication data buffer, and the IP multicast maintenance packet buffer. Control
When receiving the filter control instruction from the transmission / reception control unit by the first filter, the IP multicast packets of the test target S and G among the packets transferred from the specific distribution server are filtered, and other operations are performed. Extracting the middle packet and transferring it to the first fluctuation absorbing buffer at the connection destination with the same transfer clock as the input transfer clock;
When receiving the filter control instruction from the transmission / reception control unit by the second filter, the other active packets among the packets transferred from the specific distribution server are filtered, and the IPs of the test targets S and G Extracting a multicast packet and transferring it to the communication data buffer at the connection destination with the same transfer clock as the input transfer clock; and
The communication data buffer absorbs the second fluctuation of the connection destination of the IP multicast packet of the test objects S and G received by the second filter at the speed of X / (X + Y) of the input transfer clock from the first filter. Sending to the buffer;
When there is no transfer from the communication data buffer to the second fluctuation absorbing buffer by the IP multicast maintenance packet buffer, the connection destination at the speed of X / (X + Y) of the input transfer clock from the first filter. Transmitting an IP multicast maintenance packet as a padding packet to the second fluctuation absorbing buffer;
Controlling the transmission / reception control unit to read and transfer packets in the second fluctuation absorbing buffer and the first fluctuation absorbing buffer at a frequency of X: Y;
The IP multicast communication monitoring method according to claim 1, further comprising: The edge node includes a test target S and G traffic monitoring unit, a test packet extraction unit, and a reception information processing unit,
The test object S and G extraction step in the processing of the edge node includes:
The test target S, G traffic monitoring unit monitors a packet received from the adjacent relay node, transfers the used bandwidth monitoring information of the IP multicast packet of the test target S, G to the reception information processing unit, and connects to the connection destination. Transferring the packet to the test packet extractor of
Extracting the test target S and G IP multicast packets inserted as padding packets by the test packet extraction unit and transferring them to the reception information processing unit;
The IP multicast communication monitoring method according to claim 1 or 2, characterized by comprising: In a network composed of a plurality of nodes connecting a plurality of distribution servers and a plurality of viewer terminals, IP multicast adjacency confirmation is completed between the plurality of nodes, and the plurality of nodes are at least 1 Specific distribution among a plurality of nodes performing IP multicast communication via an acceptance route in which an IP multicast transfer request is accepted, consisting of one source node, a plurality of relay nodes, and a plurality of edge nodes. The IP multicast communication having the information of the test targets S and G including the transmission source information (S) and the specific group information (G) indicating that it is transmitted from the server, should be reached from the specific distribution server. In order to confirm whether or not communication with the viewer terminal is established, a maintenance OpS causes a boundary between the distribution server and the carrier network. The IP multicast maintenance packet, which is an observation packet, is inserted together with the IP multicast packet and transferred to the originating node among the nodes to be placed, and then only the IP multicast maintenance packet is received at the destination node of the plurality of nodes. In the IP multicast communication monitoring system to be extracted,
The source node is
Of the packets transferred from the specific distribution server, the bandwidth allocation between the IP multicast packet of the test target S and G that is communicating as the test target and the active packet other than the IP multicast packet of the test target S and G is X : When Y (X and Y are natural numbers of 1 or more), it has a control means for inserting and transferring an IP multicast maintenance packet as a padding packet in the X empty band at a speed of X / (X + Y) ,
The edge node is
An IP multicast communication monitoring system characterized by comprising test target S and G extraction means for monitoring a bandwidth used and extracting an IP multicast packet of test targets S and G inserted as padding packets. The control means in the source node includes a first filter, a second filter, a first fluctuation absorbing buffer, a second fluctuation absorbing buffer, a communication data buffer, an IP multicast maintenance packet buffer, and a transmission / reception control unit. Have
The transmission / reception control unit includes the first filter, the second filter, the first fluctuation absorbing buffer ES-A, the second fluctuation absorbing buffer ES-D, the communication data buffer, and the IP multicast maintenance packet buffer. Control
The first filter, when receiving a filter control instruction from the transmission / reception control unit, filters the IP multicast packets of the test target S and G among the packets transferred from the specific distribution server, and performs other operations. The middle packet is extracted and transferred to the first fluctuation absorbing buffer at the connection destination with the same transfer clock as the input transfer clock.
When the second filter receives a filter control instruction from the transmission / reception control unit, the second filter filters other active packets among the packets transferred from the specific distribution server, and the IPs of the test targets S and G Extract the multicast packet and transfer it to the communication data buffer at the connection destination with the same transfer clock as the input transfer clock.
The communication data buffer absorbs the second fluctuation of the connection destination of the IP multicast packet of the test targets S and G received by the second filter at a speed of X / (X + Y) of the input transfer clock from the first filter. Send to buffer,
When there is no transfer from the communication data buffer to the second fluctuation absorbing buffer, the IP multicast maintenance packet buffer is connected to the connection destination at the speed of X / (X + Y) of the input transfer clock from the first filter. Send the IP multicast maintenance packet as a padding packet to the second fluctuation absorbing buffer,
The transmission / reception control unit controls to read and transfer packets in the second fluctuation absorbing buffer and the first fluctuation absorbing buffer at a frequency of X: Y.
The IP multicast communication monitoring system according to claim 4, wherein: The test target S, G extraction means in the processing of the edge node includes a test target S, G traffic monitoring unit, a test packet extraction unit, and a reception information processing unit,
The test target S, G traffic monitoring unit monitors a packet received from the adjacent relay node, transfers use band monitoring information of the IP multicast packet of the test target S, G to the reception information processing unit, and connects to the connection destination. Forward the packet to the test packet extractor of
The test packet extraction unit extracts the IP multicast packets of the test targets S and G inserted as padding packets and transfers them to the reception information processing unit.
The IP multicast communication monitoring system according to claim 4 or 5, wherein

Images