Source: https://patents.google.com/patent/US20050190765A1/en
Timestamp: 2019-03-21 01:56:07
Document Index: 593754464

Matched Legal Cases: ['art 44', 'art 44', 'arts 7', 'art 6', 'art 40', 'art 40', 'art 40', 'art 40', 'art 9', 'art 44', 'art 6', 'art 6', 'art 9', 'art 9', 'art 40', 'art 9', 'art.\n5', 'art.\n10', 'art.\n12', 'art.\n15']

US20050190765A1 - Multicast network unit, multicast network system, and multicast method - Google Patents
US20050190765A1
US20050190765A1 US10/949,503 US94950304A US2005190765A1 US 20050190765 A1 US20050190765 A1 US 20050190765A1 US 94950304 A US94950304 A US 94950304A US 2005190765 A1 US2005190765 A1 US 2005190765A1
US7570635B2 (en
The conversion data table 8 also correlates the numbers (#1 to #N3) of the ports 15 c (transmitting-receiving port identification information) with multicast source address information or multicast destination address information (see FIG. 2) and holds them. For the “request destination address information,” the addresses of multicast packets that are received from port number 1 (multicast addresses of a group to which data is delivered) are listed as 224.0.0.1, 224.0.0.2, etc. Also, the addresses of the delivery source servers of the multicast addresses 224.0.0.1 and 224.0.0.2 are listed as 10.10.10.1 and 10.10.10.2. On the other hand, for the “delivery destination address information,” the delivery destination groups of the multicast network unit 1 are represented as 224.0.1.1, etc. Also, delivery source server addresses that deliver data to the delivery destination groups 224.0.1.1, etc., are registered as 10.10.20.1, etc.
FIG. 13 shows a multicast network unit id constructed in accordance with a fifth modification of the first embodiment of the present invention. The multicast network unit id shown in the figure has a pseudo data delivery function in addition to the function of the above-described traffic management part 44. When an address contained in a data delivery request has not been registered in the conversion data table 8, or when the traffic management part 44 judges that traffic has exceeded a traffic limiting value and judges that acceptance of a data delivery request is not allowed, the data delivery transmitter-receiver parts 7 a and 7 b (or the main control part 6 c) notify a first pseudo data delivery part 40 a and a second pseudo delivery part 40 b of the data delivery request and falsely transmits a pseudo multicast source representing non-allowance instead of transmitting the original multicast data.
Therefore, if the multicast network unit id judges that the throughput and number of sessions have exceeded predetermined threshold values and judges the data delivery request to be unacceptable, the delivery destination server is notified that acceptance has not been allowed. Therefore, the delivery destination server can receive, for example, a message of non-allowance with respect to the data delivery request message transmitted to a delivery source server. As a result, the delivery destination server can know whether the data delivery request message has been lost on a transmission path, or whether the transmitted message has not been processed in the delivery source server without being received. For that reason, delivery destination servers do not need to transmit the same data delivery request message repeatedly, so that network congestion is suppressed.
With the above-described construction, the session control method of the multicast network unit id will be described in detail with reference to FIG. 14.
If the multicast network unit 1 d receives a data delivery request (message of transfer B=>A) from domain (A) (message N1), the unit 1 d makes reference to the conversion data table 8 and judges whether the multicast address of the data delivery request has been registered (step B1). When it has not been registered, the data delivery request passes through a route labeled “Non-Allowance,” and the multicast network unit id discards the data delivery request as a non-allowance request. Even when it has been registered, the multicast network unit id judges the requested address to be a non-allowance address, if the registered address is an address that cannot be delivered. And the multicast network unit id transmits the data delivery request to the first pseudo data delivery part 40 a of the domain (A) and notifies that it is a non-allowance address (message N2). When it is not-allowance, the multicast network unit id outputs the data delivery request to the first pseudo data delivery part 40 a (FIG. 13) and informs that it has exceeded a limiting capacity (step B2).
On the other hand, in step B1, when it has been registered, it passes through a route labeled “Allowance,” and the multicast network unit id converts the multicast address according to the conversion rule of the conversion data table 8, then transfers the data delivery request containing the converted address to domain (B) (step B3), and registers the data delivery request in the address converting/filtering part 9 (step B4). At the same time, the multicast network unit id transmits a confirmation request to the traffic management part 44 thereof as an allowed request. In step B5, the priority is judged.
In step B5, when the priority is judged to be high, the main control part 6 c requests the pseudo data delivery part to deliver the pseudo data on a non-priority side (message N4). The pseudo data delivery part delivers pseudo data to domain (A). Note that the multicast network unit id is also able to transmit to domain (A) a message indicating that traffic is above a limit. In step B8, the main control part 6 c also deletes the requested non-priority data from the address converting/filtering part 9 (step B9).
As set forth above, in step B5, when it is non-allowance but has been registered as data whose priority is high, the multicast network unit id retrieves for the presence or absence of a session that is lower in priority than a session judged to be non-allowance and is lowest in priority, with respect to the address converting/filtering part 9 presently being set. When there is present a session with the lowest priority, the multicast network unit id rewrites the address of a lower-priority session to the multicast address on the side of the domain (B). The multicast network unit id also notifies the first pseudo data delivery part 40 a of pseudo data delivery.
In step B3, when the present traffic is judged to be within a traffic limiting value and is allowed, and when the present traffic has exceeded the traffic limiting value but is allowed, the multicast network unit id continues to transfer data. In step B4, the multicast network unit id converts the multicast address in dependence on the conversion rule held in the conversion data table 8 and transmits the data delivery request containing the converted address (transfer of B=>A: message N3) to domain (B). At the same time, the conversion rule is registered in the address converting/filtering part 9 (step B6).
Thus, according to the traffic control function of the multicast network unit id, traffic congestion can be avoided.
Furthermore, FIG. 16 shows another delivery system constructed in accordance with the second embodiment of the present invention. A multicast network unit if of the delivery system 100 d shown in the figure is connected to three different domains 11, 22, and 23. The multicast network unit if performs multicast communication between the domains 11, 22, and 23, whereby a plurality of domains can be interconnected.
1. A multicast network unit for delivering data between a plurality of independent multicast network domains, comprising:
an extraction part for extracting first group address information within a first multicast network domain of said plurality of independent multicast network domains from received data;
a holder part for holding said first group address information and second address information within a second multicast network domain of said plurality of independent multicast network domains so that said first group address information and said second address information correspond to each other;
a filtering part which, when said result of judgment is holding, converts said first group address information to said second address information in said holder part corresponding to said first group address information and, when said result of judgment is non-holding, discards said received data; and
a transmitter part for transmitting data containing said second address information converted by said filtering part, to said second multicast network domain.
2. The multicast network unit as set forth in claim 1, wherein
said extraction part is constructed to extract delivery destination group address information representing a delivery destination domain as said first group address information, and
said holder part is constructed to hold conversion data that correlates delivery source address information representing a delivery source domain as said second address information with said delivery destination group address information.
3. A multicast network unit for delivering data between a plurality of independent multicast network domains, comprising:
an extraction part for extracting delivery destination group address information and delivery source address information from received data;
a filtering part which, when said result of the judgment in said judgment part is holding, converts said delivery source address information to delivery source address information in said holder part corresponding to said delivery destination group address information and, when said result of judgment is non-holding, discards said received data; and
a transmitter part for transmitting data containing said delivery source address information converted by said filtering part, to a delivery destination domain of said plurality of independent multicast network domains.
4. The multicast network unit as set forth in claim 1, wherein said filtering part is constructed so that it converts at least either said delivery destination group address or delivery source address information contained in said received data in dependence on a conversion rule held in said holder part.
5. The multicast network unit as set forth in claim 4, wherein said filtering part is constructed so that it converts at least either a multicast address or delivery source address contained in said delivery destination group address information to a multicast address or delivery source address contained in said delivery source address information, respectively.
6. The multicast network unit as set forth in claim 4, wherein said filtering part is constructed so that it converts a multicast address and delivery source address contained in said delivery destination group address information to a specific multicast address and delivery source address, respectively.
7. The multicast network unit as set forth in claim 4, wherein said filtering part is constructed so that it transfers said received data in dependence on a multicast address in said delivery destination group address that is partially masked.
8. The multicast network unit as set forth in claim 4, wherein said filtering part is constructed so that it disconnects or processes one or more sessions, which are being selected from the present session as acquired delivery traffic and a plurality of communication sessions, in dependence on a priority held in said holder part and assigned to each session.
9. The multicast network unit as set forth in claim 2, wherein said filtering part is constructed so that it converts at least either said delivery destination group address or delivery source address information contained in said received data, in dependence on a conversion rule held in said holder part.
10. The multicast network unit as set forth in claim 4, wherein said holder part is constructed to hold data transmitting-receiving port identification information and said delivery source address or delivery destination group address information so that said data transmitting-receiving port identification information corresponds to said delivery source address or delivery destination group address information.
11. The multicast network unit as set forth in claim 1, further comprising a traffic management part for managing traffic in said delivery source domain or delivery destination domain in dependence on delivery traffic information contained in said received data extracted by said extraction part.
12. The multicast network unit as set forth in claim 11, wherein said traffic management part is constructed so that it controls traffic in dependence on both delivery traffic information contained in a first delivery request and limitation information about said delivery traffic information.
13. The multicast network unit as set forth in claim 12, wherein said traffic management part is constructed so that it disconnects or processes one or more sessions, which are being selected from the present session as acquired delivery traffic and a plurality of communication sessions, in dependence on a priority assigned to each session.
14. The multicast network unit as set forth in claim 1, further comprising a notification part for notifying a server transmitting said received data of information about processing of said received data in said filtering part.
15. The multicast network unit as set forth in claim 2, wherein said transmitter part is constructed so that it transmits a stream containing information about said result of the judgment.
16. The multicast network unit as set forth in claim 1, further comprising a unicast transfer part for unicasting data between said delivery destination domain and said delivery source domain.
17. A multicast network system for delivering data between a plurality of independent multicast network domains, comprising:
a multicast network unit, for delivering said data between a delivery destination domain and a delivery source domain of said plurality of independent multicast network domains, comprising
an extraction part for extracting delivery destination group address information within said delivery source domain from received data,
a holder part for holding conversion data where said delivery destination group address information corresponds to delivery source address information within said delivery source domain,
a filtering part which, when said result of the judgment in said judgment part is holding, converts said delivery destination group address information to said delivery source address information in said holder part corresponding to said delivery destination group address information and, when said result of judgment is non-holding, discards said received data, and
a transmitter part for transmitting data containing said delivery source address information converted by said filtering part, to said delivery source domain.
18. The multicast network system as set forth in claim 17, wherein said multicast network unit is constructed so that it delivers said data between said plurality of independent multicast network domains through an external network.
19. A multicast method of delivering data between a plurality of independent multicast network domains, comprising the steps of:
extracting delivery destination group address information and delivery source address information from received data;
when said result of the judgment is holding, converting said delivery destination group address information to said delivery source address information held so as to correspond to said delivery destination group address information and, when said result of the judgment is non-holding, discarding said received data; and
transmitting data containing said delivery source address information converted, to a delivery destination domain of said plurality of independent multicast network domains.
US20050190765A1 true US20050190765A1 (en) 2005-09-01
US7570635B2 US7570635B2 (en) 2009-08-04
US20060222012A1 (en) * 2005-04-01 2006-10-05 Punit Bhargava Clustering methods for scalable and bandwidth-efficient multicast
EP2164203A1 (en) * 2007-08-25 2010-03-17 Huawei Technologies Co., Ltd. Message transmission method, device and system for implementing multicast services
EP2204963A1 (en) * 2007-11-20 2010-07-07 Huawei Technologies Co., Ltd. Session monitoring method, device and system based on multicast technique
US20100303073A1 (en) * 2009-05-28 2010-12-02 Alaxala Networks Corporation Network relay apparatus and inter-network relay method
US20120263035A1 (en) * 2011-03-18 2012-10-18 Fujitsu Limited System and method for changing a delivery path of multicast traffic
CN103634219A (en) * 2013-11-27 2014-03-12 杭州华三通信技术有限公司 Maintaining method and device for Anycast-RP (rendezvous point)
CN103888351A (en) * 2012-12-20 2014-06-25 国际商业机器公司 Method and device used for managing multiple conversations in network based on multi-path routing
US20160337374A1 (en) * 2012-04-27 2016-11-17 Hewlett-Packard Development Company, L.P. Access of a service
JP4825696B2 (en) * 2007-01-22 2011-11-30 アラクサラネットワークス株式会社 Packet relay device
JP3656418B2 (en) 1998-07-15 2005-06-08 富士ゼロックス株式会社 Computer readable recording medium recording a gateway device and a multicast packet relay program
JP3833466B2 (en) 2000-11-08 2006-10-11 三菱電機株式会社 Network system and a network control method
JP3890243B2 (en) 2002-03-28 2007-03-07 キヤノン株式会社 Controller, network communication method and control program
US20020181464A1 (en) * 2000-07-21 2002-12-05 Hitachi, Ltd. Multicast routing method and apparatus for routing multicast packet
EP2164203A4 (en) * 2007-08-25 2010-06-30 Huawei Tech Co Ltd Message transmission method, device and system for implementing multicast services
US20140036916A1 (en) * 2007-10-15 2014-02-06 Media Patents, S.L. Methods for managing multicast traffic between sources sending data and hosts requesting data and network equipment used to implement the methods
US8422499B2 (en) * 2007-10-15 2013-04-16 Media Patents, S.L. Methods and apparatus for managing multicast traffic
US8582572B2 (en) * 2007-10-15 2013-11-12 Media Paents, S.L. Methods and apparatus for managing multicast traffic
US8571028B2 (en) * 2007-10-15 2013-10-29 Media Patents, S.L. Methods and apparatus for managing multicast traffic
EP2204963A4 (en) * 2007-11-20 2010-11-17 Huawei Tech Co Ltd Session monitoring method, device and system based on multicast technique
US8539088B2 (en) 2007-11-20 2013-09-17 Huawei Technologies Co., Ltd. Session monitoring method, apparatus, and system based on multicast technologies
US8817683B2 (en) * 2009-05-28 2014-08-26 Alaxala Networks Corporation Network relay apparatus and inter-network relay method
US8599683B2 (en) * 2011-03-18 2013-12-03 Fujitsu Limited System and method for changing a delivery path of multicast traffic
US7570635B2 (en) 2009-08-04