WO2007137464A1 - Procédé d'optimisation de protocole de gestion de groupe et serveur et système associés - Google Patents

Procédé d'optimisation de protocole de gestion de groupe et serveur et système associés Download PDF

Info

Publication number
WO2007137464A1
WO2007137464A1 PCT/CN2006/003289 CN2006003289W WO2007137464A1 WO 2007137464 A1 WO2007137464 A1 WO 2007137464A1 CN 2006003289 W CN2006003289 W CN 2006003289W WO 2007137464 A1 WO2007137464 A1 WO 2007137464A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
source
mode
group
router
Prior art date
Application number
PCT/CN2006/003289
Other languages
English (en)
French (fr)
Inventor
Feng Guo
Singh Krishnaraj Rathore
Haiyang Su
Xiaoniu Zhou
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to ES06828243T priority Critical patent/ES2428372T3/es
Priority to EP06828243.3A priority patent/EP2023563B1/en
Publication of WO2007137464A1 publication Critical patent/WO2007137464A1/zh
Priority to US12/277,050 priority patent/US8102870B2/en
Priority to US13/326,811 priority patent/US8625591B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227—Filtering policies
    • H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL

Definitions

  • the present invention relates to multicast services, and in particular, to a method, server and system for optimizing a group management protocol. Background technique
  • the IGMP protocol is a group management protocol for IPV4 multicast. It runs between the host and the multicast router directly connected to the host. Through this protocol, the host tells the local router that it wants to join a specific multicast group. At the same time, the router periodically queries whether a member of a known group in the LAN is active (that is, whether the network segment still belongs to a certain network. Member of the multicast group). Collects and maintains the membership of the connected network group.
  • IGMPvl The basic group member query and reporting process is defined in IGMPvl [RFC1112].
  • IGMPv2 [RFC2236] is commonly used.
  • IGMPv2 adds a mechanism for group members to leave quickly.
  • IGMPv3 [RFC3376] mainly adds source filtering. That is, group members can specify to receive or specify packets that do not receive certain multicast sources.
  • Multicast Snooping Discovery Protocol MLD is an IGMP IPV6 extension that implements the same functionality as IGMP.
  • VDLD Low Density Deformation Protocol
  • MLDV1 Low Density Polyethylene Streaming Protocol
  • MLDV2 Low Density Polyethylene Streaming Protocol
  • IGMPV3 IGMPV3
  • the protocol defines two filtering modes: INCLUDE (included) and EXCLUDE (excluded) mode.
  • INCLUDE mode the multicast receiver "only" receives messages from a specific multicast source.
  • EXCLUDE mode the receiver only receives multicast messages other than "specific" sources. The particular source is represented by a list of sources.
  • the source filtering function defined in IGMPV3/MLDV2 improves the expressive ability of group members. Receivers can choose to receive multicast messages from some sources or not from certain sources.
  • the source filtering function is implemented in the host system by the following operations: IPMulticastListen ( socket, interface , multicast-address , filter-mode, source-list ) ( 1 )
  • Socket is a parameter related to different requesting entities (a high-level protocol or an application) in the IPV4 system; Interface is a local identifier of the network interface, and the interface may be physical or logical.
  • the multicast-address is the group address to which the request belongs.
  • Filter-mode is INCLUDE or EXCLUDE.
  • the source-list is a list of IP unicast addresses of multicast sources that the multicast receiver wants to receive (in INCLUDE mode) and do not wish to receive (in EXCLUDE mode).
  • IPv6MulticastListen socket, interface, IPv6 multicast address, filter mode, source list ) ( 2 )
  • equation (2) The main difference between equation (2) and equation (1) is that the multicast address and source list are expressed in the form of IPV6 addresses.
  • IGMPV3 the description of related technical solutions in this paper takes IGMPV3 as an example. Since the source filtering function implemented in MLDV2 is equivalent to IGMPV3, it is not specifically described here.
  • IGMP is an asymmetric protocol, and group members (usually located on the host and sometimes on the router) have different protocol behaviors from the multicast router.
  • the IGMPV3 host system saves the status of multicast group reception on each Socket and each interface to support source filtering mode.
  • the state of the socket is the desire received by the group expressed by each application, that is, on what interface the application wants to be, in what filtering mode, which multicast source list is filtered, and which multicast group is added.
  • the group receiving state of the interface is the union of the group receiving states of all the sockets on the interface.
  • the host can generate IGMPV3 status report messages based on the group receiving status and its changes on the interface, and respond to group member queries of the connected routers.
  • the router supporting IGMPV3 also needs to save the group receiving status of the connected network.
  • the conceptual model is: (multicast address, group timer, filter-mode, (source records)); (3)
  • the multicast address is the group address corresponding to the status record.
  • Filter-mode is the filtering mode defined by the router itself. As long as the router receives the report message in EXCLUDE mode, the source of the filtering mode is recorded as EXCLUDE.
  • the group timer group timer is only used in EXCLUDE mode, indicating the timeout period for the group's filtering mode to be converted from EXCLUDE to INCLUDE.
  • Source Record is the source, i has recorded, it has the form of the mouth: (Source address, source timer).
  • the source address is the source address of the multicast source that the host wants to receive.
  • the source timer is the timeout timer.
  • IGMPV3 and MLDV2 have increased support for source filtering lists, they have increased the flexibility of joining groups.
  • PIM-SSM source-specific multicast
  • Mode setting and conversion mechanism is complicated: The router needs to set and convert the mode according to the change of the receiving state of the adjacent system group. These operations are closely related to the state of the source/group timer and require complex decision logic. The implementation of the agreement is cumbersome.
  • the implementation mechanism of the EXCLUDE mode does not fully meet the requirements of practical applications: On the one hand, in a multicast application system, it is relatively rare to expect to receive multicast packets from a certain source (or some). On the other hand, even if there is such an application scenario, if a host connected to an interface of the router does not want to receive multicast data of a certain source, there is a great possibility that other hosts in the network wish to receive the multicast. The source data, in this case, the router must also forward the message from the source, so the role of the EXLUDE mode is very limited. Summary of the invention
  • the invention provides a method, a server and a system for optimizing a group management protocol, which are used to solve the problem that the filtering mode setting and the conversion mechanism of the existing protocol are complicated.
  • the method of the invention comprises the following steps:
  • the group member sends a member report to the multicast router
  • the multicast router After receiving the member report, the multicast router determines whether the report includes a non-empty source list of the excluded mode EXCLUDE, and if so, updates the corresponding state inside the router according to the joining of the non-specific source; otherwise, directly completes the router by the content of the report. An update of the corresponding internal status.
  • the group member sends a member report containing the non-empty source list containing the mode INCLUDE to the multicast router to complete the joining operation of the specific source.
  • the multicast router receives the join report of the non-specific source and processes it according to the INCLUDE mode. Further, the group member sends the INCLUDE mode containing the arbitrary source list to the multicast router. Reported to complete the join operation for non-specific sources.
  • the non-specific source of the group member side joins the interface model of the operation, and INCLUDE, ANY indicates that the list contains any source.
  • the group member sends a member report of the EXCLUDE mode containing the empty source list to the multicast router to complete the join operation of the non-specific source.
  • EXCLUDE In the interface model of the non-specific source joining operation of the group member side, EXCLUDE, NULL is used to exclude the empty source list.
  • the multicast router receives a member report of the EXCLUDE mode containing a list of non-empty sources, it reports the member report of the INCLUDE mode containing any source list or the member report process of the EXCLUDE mode containing the empty source list.
  • the multicast router of the present invention is configured to implement collection and maintenance of group membership, and further includes: a judgment module, configured to determine whether the received member report includes a non-empty source list of the exclusion mode EXCLUDE, and if yes, trigger the conversion module ; otherwise, trigger the identification module;
  • a conversion module configured to convert the received member report into a join report of a non-specific source, and submit it to the identification module for processing
  • the identification module is configured to identify the join report of the non-specific source and complete the update of the corresponding status inside the router.
  • the identification module identifies a member report of the INCLUDE schema containing any source list and a member report of the EXCLUDE schema containing the empty source list as a join report of a non-specific source.
  • the conversion module converts a member report of the EXCLUDE schema containing the list of non-empty sources into a report that can be identified by the recognition module as being joined by a non-specific source.
  • the multicast system of the present invention includes a plurality of group members; and a multicast router for processing members of the EXCLUDE mode sent by the group members in the INCLUDE filtering mode to report the members of the INCLUDE mode.
  • the multicast router includes the following submodule: a judging module, configured to determine whether the received member report includes a non-empty source list of the exclusion mode EXCLUDE, and if so, trigger the conversion module; otherwise, trigger the identification module; and the conversion module is configured to The received member report is converted into a non-specific source join report and processed by the identification module; the identification module is configured to identify the join report of the non-specific source, and complete the update of the corresponding state inside the router.
  • the identification module identifies a member report of the INCLUDE schema containing any source list, and a member report of the EXCLUDE schema containing the empty source list as a join report of a non-specific source.
  • the conversion module converts a member report of the EXCLUDE schema containing the list of non-empty sources into a report that can be identified by the recognition module as being joined by a non-specific source.
  • the present invention shields the filtering function implemented by the original EXCLUDE filtering mode. After the multicast router receives the member report, it determines whether the report contains the non-empty EXCLUDE mode.
  • Source list if yes, update the corresponding state inside the router according to the joining of non-specific sources; otherwise (ie receive a member report of INCLUDE mode containing non-empty source list, member report of INCLUDE mode containing any source list, or contain empty
  • the member list of the EXCLUDE mode of the source list directly updates the corresponding state inside the router with the content of the report without performing mode determination and conversion.
  • the multicast router After the multicast router receives the member report, it judges the filtering mode of the report and the characteristics of the source list included in the report, instead of blocking the original EXCLUDE filtering mode, and rejects the non-empty source list of the EXCLUDE mode. Correspondingly, when receiving such a report, the multicast router updates the internal state of the router according to the joining of non-specific sources, thereby being compatible with other low-level multicast management protocols.
  • the SSM protocol can be supported.
  • the present invention also provides a multicast router, and a corresponding multicast system.
  • FIG. 1 is a schematic structural diagram of a multicast router according to the present invention.
  • FIG. 2 is a schematic structural diagram of a multicast system according to the present invention
  • Figure 3 is a flow chart of the method steps of the present invention. detailed description
  • the present invention provides a multicast router, which can implement the collection and maintenance functions of the existing group membership, see As shown in FIG. 1, the method includes: a judging module, a conversion module, and an identification module that are sequentially connected, and the judging module is also directly connected to the identification module.
  • the determining module is configured to determine whether the received member report includes a non-empty source list of the exclusion mode EXCLUDE, and if yes, trigger the conversion module; otherwise, trigger the identification module.
  • the conversion module is configured to convert a member report of the EXCLUDE mode including the non-empty source list into a report that can be recognized as a non-specific source by the identification module, and is processed by the identification module.
  • the identification module is configured to identify a join report of a non-specific source, and complete an update of a corresponding state inside the router.
  • the identification module may identify a member report of the INCLUDE mode including any source list, and a member report of the EXCLUDE mode including the empty source list as a join report of a non-specific source.
  • the present invention further provides a multicast system, as shown in FIG. 2, comprising: the multicast router of the present invention, and a plurality of group members connected to the multicast router.
  • the present invention provides a method for optimizing a group management protocol. Referring to FIG. 3, the following main steps are included:
  • the group member sends a member report to the multicast router.
  • the group member when a group member starts a multicast application, or when a group member receives a query sent by a multicast router periodically, the group member sends a member report to the multicast router to notify the current group of the interface. Receive status.
  • group members are allowed to send member reports of INCLUDE filtering mode and EXCLUDE filtering mode to the multicast router.
  • the member report of the INCLUDE filtering mode can be further divided into a member report of the INCLUDE mode including a non-empty source list, and a member report of the INCLUDE mode including any source list. Report.
  • the member report of the EXCLUDE filtering mode can be further divided into a member report of the EXCLUDE mode containing a list of non-empty sources, and a member report of the EXCLUDE mode containing a list of empty sources.
  • the multicast router determines whether the non-empty source list of the EXCLUDE mode is included in the report, and if yes, proceeds to step S3; otherwise, proceeds to step S4.
  • the multicast router After receiving the report of the member, the multicast router determines the filtering mode of the report and the characteristics of the source list therein, and then proceeds to step S3 to perform the shielding process of the EXCLUDE mode to embody the beneficial effects of the present invention and achieve low Version protocol compatibility.
  • step S4 the process proceeds to step S4 to complete the update of the corresponding state inside the router.
  • the present invention optimizes the existing protocol, so when the router receives the report of the EXCLUDE mode, no processing such as mode setting and timeout conversion is performed.
  • the report containing the non-empty source list of the EXCLUDE mode is added as a non-specific source to report processing (for details, refer to the content in step S4), that is, the corresponding state inside the router is updated according to the joining of the non-specific source.
  • the router completes the router directly with the non-empty source list according to the existing processing flow. An update of the corresponding internal status.
  • the multicast router receives a join report from a non-specific source sent by a group member, it is processed according to INCLUDE mode.
  • the group members can include any source list (INCLUDE, ANY ) in the interface model of the non-specific source join operation, and send the member report of the INCLUDE mode containing the arbitrary source list to the multicast router; To a member report containing the INCLUDE mode of INCLUDE, ANY, the report is considered to be a non-specific source join report, and then completed Join operation for non-specific sources.
  • INCLUDE any source list
  • ANY the interface model of the non-specific source join operation
  • the group member may exclude the empty source list by (EXCLUDE, NULL) in the interface model of the non-specific source joining operation, and send a member report of the EXCLUDE mode including the empty source list to the multicast router;
  • EXCLUDE EXCLUDE
  • NULL EXCLUDE mode
  • the report is considered to be a non-specific source join report, thereby completing the non-specific source join operation.
  • IPMulticastListen socket, interface, multicast-address , INCLUDE, ANY
  • IPMulticastListen represents the IGMPV3 protocol interface model. If it is MLDV2 protocol, IPMulticastListen can be replaced with IPv6MulticastListen; Socket represents parameters related to different request entities in the system; Interface represents the local identifier of the network interface; multicast-address indicates the request. The group address to which it belongs; (INCLUDE , ANY ) indicates a list of IP unicast addresses of non-specific sources that the multicast receiver wishes to receive.
  • IPMulticastListen socket, interface, multicast-address , EXCLUDE, NULL ( 5 )
  • IPMulticastListen represents the IGMPV3 protocol interface model. If it is the MLDV2 protocol, the shell 'J IPMulticastListen can be replaced with IPv6MulticastListen; Socket indicates the parameters related to different request entities in the system; Interface indicates the local identifier of the network interface; multicast-address Indicates the group address to which the request belongs; (EXCLUDE, NULL ) indicates the joining of a group of non-specific sources.
  • CHANGE—TO—INCLUDE is represented by IS—IN, ALLOW, and BLOCK and TOJN, respectively.
  • the host machine encapsulates NODE-ISJNCLUDE, ALLOW-NEW_SOURCES and BLOCK-OLD-SOURCES when generating the report.
  • CHANGE TO—The report type of INCLUDE.
  • the host side of the original protocol sets a group timer for responding to the source-group query message of the router. When the timer times out, it responds to the report message. When the group timer expires, the host needs to compare the source list corresponding to the group timer with the source of the corresponding group of the interface, and determine the interface status form reported to the router.
  • Table 2 The rules for determining the optimization protocol are shown in Table 2:
  • the IGMPV3/MLDV2 router filtering mode is defined to simplify the number of states inside the router. The specific operation is that when a packet of the source filtering mode EXCLUDE is received, the filtering mode of the router is set to EXCLUDE. If the source of EXCLUCE does not exist, when the group-timer times out, the router filter mode is converted to INCLUDE.
  • the router since the router does not perform mode setting and conversion, and only uses the INCLUDE filtering mode to process the received member report, the EXCLUDE mode in the existing router side protocol has no meaning, thus canceling the mode definition of the router.
  • the conceptual model of the receiver's receive status is:
  • the multicast address is the group address corresponding to the status record; the group timer is used to determine whether the network connected to the router has a group receiving status of a non-specific source; source records indicates that the source has been recorded.
  • the interface timer of the interface was used in EXCLUDE mode, which indicates the timeout period for the router to switch from EXCLUDE filtering mode to INCLUDE mode.
  • the source timer of the router is maintained for each source record.
  • a group timer is used to represent a group of non-specific sources.
  • the protocol behavior related to the group timer is shown in Table 3:
  • G_Timer > 0 indicates that the connected network has a group receiving status of a non-specific source
  • G— TIMER 0
  • a IS_IN(B) A+B B timer is set to GMI/MALI
  • G— TIMER 0
  • a IS_ EX(NULL) Group A timer is set to GMI/MALI
  • a IS— IN(B) A+B B timer is set to GMI/MALI
  • a IS_EX(NULL) Group A timer is set to GMI/MALI Table 5
  • the GMI Group Member Interval
  • the MALI Multicast Address Listening Interval
  • the router After the original protocol receives the packet with the filter mode change and the source list change, there will be a series of processing and conversion mechanisms.
  • the router does not perform mode setting and conversion, but only uses the INCLUDE filtering mode to process the received member report, that is, the router only processes the source list change record report.
  • Table 6 For the corresponding operation behavior, see Table 6:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种优化组管理协议的方法、 服务器及系统 技术领域
本发明涉及组播业务， 特别是涉及一种优化组管理协议的方法、 服务器 及系统。 背景技术
IGMP协议是 IPV4组播的组管理协议， 它运行于主机和与主机直接相连 的组播路由器之间。 主机通过此协议告诉本地路由器希望加入某个特定的组 播组， 同时路由器通过此协议周期性地查询局域网内某个已知组的成员是否 处于活动状态（即该网段是否仍有属于某个組播组的成员）， 实现所连网络组 成员关系的收集与维护。
IGMP有三个版本， IGMPvl[RFC1112]中定义了基本的组成员查询和报告 过程； 目前通用的是 IGMPv2[RFC2236], IGMPv2添加了组成员快速离开的 机制。 IGMPv3[RFC3376]中主要增加了源过滤的功能， 即组成员可以指定接 收或指定不接收某些组播源的报文。
组播侦听发现协议 MLD为 IGMP的 IPV6扩展， 其实现的功能与 IGMP 是相同的。] VDLD有两个版本, MLDV1与 MLDV2,分别与 IGMPV2和 IGMPV3 对应。
在 IGMPV3/MLDV2 中， 为了支持对特定源的过滤功能， 协议定义了两 种过滤模式： INCLUDE (包含）和 EXCLUDE (排除）模式。 在 INCLUDE 模式中， 组播接收者"只"从特定的组播源接收报文。 在 EXCLUDE模式中， 接收者只接收 "除了 "特定源之外的组播报文。 所述特定源是用源列表来表示 的。
IGMPV3/MLDV2中定义的源过滤功能， 提高了组成员的表达能力。接收 者可以自行选择从某些源或不从某些源接收组播报文。 在 IGMPV3中， 源过 滤功能在主机系统中是通过如下操作实现的： IPMulticastListen ( socket， interface , multicast-address , filter-mode， source-list ) ( 1 )
上式中， Socket为 IPV4系统内与不同请求实体（某个高层协议或应用程 序）相关的参数； Interface为网络接口的本地标识， 该接口可为物理或逻辑 的。 multicast-address 为该请求所属的组地址。 filter-mode 为 INCLUDE或 EXCLUDE。 source-list为组播接收者希望接收（ INCLUDE模式下）和不希望 接收（EXCLUDE模式下） 的组播源的 IP单播地址列表。
在 MLDV2中具有相似的表达方式：
IPv6MulticastListen ( socket, interface, IPv6 multicast address, filter mode, source list ) ( 2 )
式 (2)与式 (1)主要的区别在于组播地址和源列表是以 IPV6地址的形式表 述。 为方便起见， 本文中相关技术方案的阐述以 IGMPV3为例。 由于 MLDV2 中实现的源过滤功能与 IGMPV3是等同的 , 不在这里做特别说明。
IGMP为非对称协议， 组成员 （通常位于主机上， 有时也在路由器上）和 组播路由器的协议行为是不同的。 IGMPV3主机系统在每个 Socket和每个接 口上保存组播组接收的状态， 以实现源过滤模式的支持。 其中 socket的状态 为每个应用所表达的组接收的愿望， 即该应用希望在什么接口上， 以何种过 滤模式， 过滤哪些组播源列表， 加入哪个组播组。 而接口的組接收状态为该 接口上所有 socket的组接收状态的联合。 主机可以根据接口上的組接收状态 及其变化，生成 IGMPV3状态报告报文，以及响应相连路由器的组成员查询。
支持 IGMPV3的路由器也需要保存所连网络的组接收状态， 其概念模型 为： ( multicast address , group timer， filter-mode , ( source records ) )； ( 3 )
其中 multicast address 为该状态记录对应的组地址。 filter-mode为路由器 自身定义的过滤模式， 只要路由器收到 EXCLUDE模式的报告报文， 将该过 滤模式源记录为 EXCLUDE。 组定时器 group timer只在 EXCLUDE模式下使 用， 表示该组的过滤模式从 EXCLUDE转换为 INCLUDE的超时时间。 source record 为源、 i己录, 它具有 口下形式： ( Source address, source timer )。 Source address为主机希望接收的组播源的源地址， source timer为其超时定时器。
IGMPV3和 MLDV2虽然增加了对源过滤列表的支持， 增加了加入组的 灵法性，特别是通过定义 INCLUDE模式，可以实现对源特定组播（ PIM-SSM ) 路由协议的支持， 但是过滤模式的引入也有一定的缺点：
1、 模式设定与转换机制复杂： 路由器需根据邻接系统组接收状态的变化 进行模式的设定和转换， 这些操作与源 /组定时器的状态紧密相关， 需要复杂 的判决逻辑。 协议实现起来繁瑣。
2、 EXCLUDE模式的实现机制并不能完全满足实际应用的需求： 一方面， 在组播应用系统中， 希望不从某个（或某些） 源接收组播报文的情况是比较 少见的。 另一方面， 即使存在这样的应用场景， 如果与路由器某个接口相连 的主机希望不接收某个源的组播数据， 那么存在很大的可能性， 该网络中的 其他主机希望接收该组播源的数据， 在这种情况下， 路由器也必须将该源的 报文转发过来， 因而 EXLUDE模式起的作用是非常有限的。 发明内容
本发明提供一种优化组管理协议的方法、 服务器及系统， 用以解决现有 协议的过滤模式设定和转换机制较复杂的问题。
本发明方法包括下列步驟：
组成员向组播路由器发送成员报告；
組播路由器收到成员报告后，判断该报告中是否包含排除模式 EXCLUDE 的非空源列表， 若是， 则按照非特定源的加入更新路由器内部的相应状态； 否则， 以该报告的内容直接完成路由器内部相应状态的更新。
其中， 组成员向组播路由器发送包含非空源列表的包含模式 INCLUDE 的成员报告， 以完成特定源的加入操作。
其中，组播路由器收到非特定源的加入报告，则按照 INCLUDE模式处理。 进一步，组成员向组播路由器发送包含任意源列表的 INCLUDE模式的成 员报告， 以完成非特定源的加入操作。 组成员侧的非特定源加入操作的接口 模型中， 以 INCLUDE , ANY表示包含任意源列表。
进一步， 组成员向組播路由器发送包含空源列表的 EXCLUDE模式的成 员报告， 以完成非特定源的加入操作。 组成员侧的非特定源加入操作的接口 模型中， 以 EXCLUDE , NULL表示排除空源列表。
若组播路由器收到包含非空源列表的 EXCLUDE模式的成员报告， 则按 照收到包含任意源列表的 INCLUDE模式的成员报告或收到包含空源列表的 EXCLUDE模式的成员报告处理。
本发明的组播路由器， 用于实现组成员关系的收集与维护， 其还包括： ' 判断模块， 用于判断收到成员报告是否包含排除模式 EXCLUDE的非空 源列表， 若是， 则触发转换模块； 否则， 触发识别模块；
转换模块， 用于将收到的成员报告转换为非特定源的加入报告， 并交由 识别模块处理；
识别模块， 用于识别非特定源的加入报告， 并完成路由器内部相应状态 的更新。
所述识别模块将包含任意源列表的 INCLUDE模式的成员报告，以及包含 空源列表的 EXCLUDE模式的成员报告认定为非特定源的加入报告。
所述转换模块将包含非空源列表的 EXCLUDE模式的成员报告转换为可 被所述识別模块认定为非特定源加入的报告。
本发明的组播系统， 包括若干组成员； 以及组播路由器， 其用于以 INCLUDE 过滤模式处理组成员发来的 EXCLUDE 模式的成员才艮告和 INCLUDE模式的成员报告。
所述组播路由器包括下列子模块： 判断模块， 用于判断收到成员报告是 否包含排除模式 EXCLUDE的非空源列表， 若是， 则触发转换模块； 否则， 触发识别模块； 转换模块， 用于将收到的成员报告转换为非特定源的加入报 告， 并交由识别模块处理； 识别模块， 用于识别非特定源的加入报告， 并完 成路由器内部相应状态的更新。 所述识别模块将包含任意源列表的 INCLUDE模式的成员报告，以及包含 空源列表的 EXCLUDE模式的成员报告认定为非特定源的加入报告。
所述转换模块将包含非空源列表的 EXCLUDE模式的成员报告转换为可 被所述识别模块认定为非特定源加入的报告。
本发明有益效果如下：
由于现有技术定义了两种源过滤模式， 需要主机和路由器维护复杂的过 滤模式和处理机制。 考虑到 EXCLUDE过滤模式较少的应用场景和有限的过 滤功能， 本发明屏蔽原 EXCLUDE过滤模式所实现的过滤功能， 在组播路由 器收到成员报告后， 判断该报告中是否包含 EXCLUDE模式的非空源列表， 若是， 则按照非特定源的加入更新路由器内部的相应状态； 否则 （即收到包 含非空源列表的 INCLUDE模式的成员报告，包含任意源列表的 INCLUDE模 式的成员报告， 或者包含空源列表的 EXCLUDE模式的成员报告）， 以该报告 的内容直接完成路由器内部相应状态的更新， 而无需进行模式判定和转换。
通过本发明方法的实施， 可以避免现有协议复杂的过滤模式转换和处理。 由于组播路由器收到成员报告后， 对该报告的过滤模式和该报告包含的 源列表的特性进行判断， 而不是在屏蔽原 EXCLUDE过滤模式后， 一味的拒 收 EXCLUDE模式的包含非空源列表的报告； 相应的在收到该种报告时， 组 播路由器按照非特定源的加入更新路由器内部的相应状态， 从而兼容其它低 版本组播管理协议。
由于本发明方法保留了有应用价值的 INCLUDE模式源过滤功能，所以可 支持 SSM协议。
为了支撑本发明方法， 本发明还提供了一种组播路由器， 以及相应的组 播系统。 附图说明
图 1为本发明的组播路由器结构示意图;
图 2为本发明组播系统结构示意图； 图 3为本发明方法步骤流程图。 具体实施方式
为了简化现有协议 (包括段不限于 IGMPV3或 MLDV2协议） 的过滤模 式设定和转换机制， 本发明提供了一种组播路由器， 其可实现现有的组成员 关系的收集与维护功能， 参见图 1 所示， 其包括： 依次相连的判断模块、 转 换模块和识别模块， 所述判断模块还直接与识别模块相连。
所述判断模块， 用于判断收到成员报告是否包含排除模式 EXCLUDE的 非空源列表， 若是， 则触发转换模块； 否则， 触发识别模块。
所述转换模块， 用于将包含非空源列表的 EXCLUDE模式的成员报告转 换为可被所述识别模块认定为非特定源加入的报告， 并交由识别模块处理。
所述识别模块， 用于识别非特定源的加入报告， 并完成路由器内部相应 状态的更新。本发明中，识别模块可将包含任意源列表的 INCLUDE模式的成 员报告， 以及包含空源列表的 EXCLUDE模式的成员报告认定为非特定源的 加入报告。
对应上述组播路由器， 本发明又提供了一种组播系统， 参见图 2所示， 其包括： 本发明的组播路由器， 以及与该组播路由器相连的若干个组成员。
应用上述组播路由器及系统， 本发明提供了一种优化组管理协议的方法， 参见图 3所示， 包括下列主要步骤：
Sl、 组成员向组播路由器发送成员报告。
根据现有技术， 当组成员启动组播应用时， 或者组成员收到组播路由器 定时发来的查询 4艮文时， 组成员向组播路由器发送成员报告， 以 4艮告接口当 前的組接收状态。
为了兼容低版本的协议，允许组成员向组播路由器发送 INCLUDE过滤模 式和 EXCLUDE过滤模式的成员报告。
进一步，所迷 INCLUDE过滤模式的成员报告又可分为包含非空源列表的 INCLUDE模式的成员报告， 以及包含任意源列表的 INCLUDE模式的成员报 告。 所述 EXCLUDE 过滤模式的成员报告又可分为包含非空源列表的 EXCLUDE模式的成员报告， 以及包含空源列表的 EXCLUDE模式的成员报 告。
52、 組播路由器收到成员报告后， 判断该报告中是否包含 EXCLUDE模 式的非空源列表， 若是， 则转入步骤 S3; 否则， 转入步骤 S4。
组播路由器收到成员报告后， 对该报告的过滤模式， 以及其中的源列表 特点进行判断， 并相应转入步骤 S3进行 EXCLUDE模式的屏蔽处理， 以体现 本发明的有益效果， 并实现对低版本协议的兼容。
或者， 相应转入步骤 S4, 完成路由器内部相应状态的更新。
53、 按照非特定源的加入更新路由器内部的相应状态。
由于本发明对现有协议作了优化， 屏蔽了应用场景较少， 过滤效率不高 的 EXCLUDE过滤模式， 所以当路由器收到 EXCLUDE模式的报告时， 不进 行模式设定和超时转换等处理， 而是将包含 EXCLUDE模式的非空源列表的 报告作为非特定源加入才艮告处理（具体处理方式参见步骤 S4 中的内容）， 即 按照非特定源的加入更新路由器内部的相应状态。 这样做不但避免了模式设 定和超时转换， 而且路由器在收到包含 EXCLUDE模式的非空源列表的报告 时， 不会向组成员返回错误报文， 从而兼容现有低版本的协议。
S4、 以该^ =艮告的内容直接完成路由器内部相应状态的更新。
若组播路由器收到与现有协议相同的包含非空源列表的 INCLUDE模式 的成员报告， 即组成员发起特定源的加入操作， 则按照现有处理流程， 直接 以该非空源列表完成路由器内部相应状态的更新。
若組播路由器收到组成员发来的非特定源的加入报告，则按照 INCLUDE 模式处理。
其中， 组成员可在非特定源加入操作的接口模型中， 以 （INCLUDE , ANY ) 表示包含任意源列表， 并向组播路由器发送包含任意源列表的 INCLUDE模式的成员报告； 若组播路由器收到含有 ( INCLUDE , ANY )的 INCLUDE模式的成员报告， 则认定该报告为非特定源的加入报告， 进而完成 非特定源的加入操作。
或者， 组成员可在非特定源加入操作的接口模型中， 以 （EXCLUDE , NULL )表示排除空源列表， 并向组播路由器发送包含空源列表的 EXCLUDE 模式的成员报告；若组播路由器收到含有 ( EXCLUDE , NULL )的 EXCLUDE 模式的成员报告， 则认定该报告为非特定源的加入报告， 进而完成非特定源 的加入操作。
至此本发明方法概述完毕。
结合上述概述的内容， 以下描述按照本发明方法对现有协议优化后的相 关信息的定义， 以及具体操作的处理。
1、 为非特定源的加入定义新的业务接口模型：
IPMulticastListen ( socket, interface, multicast-address , INCLUDE, ANY);
( 4 )
式（ 4 )中， IPMulticastListen表示 IGMPV3协议接口模型 , 若为 MLDV2 协议， 则 IPMulticastListen可替换为 IPv6MulticastListen; Socket表示系统内 与不同请求实体相关的参数； Interface 表示网络接口的本地标识； multicast-address表示请求所属的组地址； （INCLUDE ， ANY )表示组播接收 者希望接收的非特定源的 IP单播地址列表。
IPMulticastListen ( socket, interface, multicast-address , EXCLUDE, NULL) ( 5 )
式（ 5 )中， IPMulticastListen表示 IGMPV3协议接口模型， 若为 MLDV2 协议， 贝' J IPMulticastListen可替换为 IPv6MulticastListen; Socket表示系统内 与不同请求实体相关的参数； Interface 表示网络接口的本地标识； multicast-address表示请求所属的组地址； （EXCLUDE, NULL )表示非特定 源的组的加入。
2、 组成员报告报文中与模式相关的字段定义（以 INCLUDE , ANY为 例， EXCLUDE, NULL可类推）：
在 IGMPV3/MLDV2中组成员报告中，组记录定义有六种类型 [RFC3376] , 保 留 INCLUDE 相 关 的 四 种 类 型 NODE_IS— INCLUDE ,! ALLOW— NEW— SOURCES 和 BLOCK— OLD— SOURCES ,
CHANGE— TO— INCLUDE下文分别以 IS— IN, ALLOW和 BLOCK和 TOJN 表示。
3、组成员协议行为的重新定义（以 INCLUDE , ANY为例， EXCLUDE, NULL可类推 ):
a、 主机接口状态变化的操作：
原协议中的主机状态转化规则表， 在优化协议中参见表一：
Figure imgf000011_0001
表一
此 时 主 机 在 生 成 报 告 时 ， 封 装 NODE—ISJNCLUDE 、 ALLOW一 NEW— SOURCES 和 BLOCK—OLD— SOURCES 和
CHANGE— TO— INCLUDE的报告类型。
b、 主机在接收到查询报文之后的操作：
原协议主机侧为响应路由器的源 -组查询报文设定一个组定时器， 当该定 时超时时， 响应报告报文。 組定时器超时时， 主机需要将该组定时器所对应 的源列表和接口相应组的源进行比较， 决定向路由器报告的接口状态形式。 优化协议的判定规则如表二所示：
接口状态 等待的源列表 响应的状态记录
INCLUDE (A) B IS— IN(A*B)
INCLUDE (ANY) B IS_IN(B) 4、组播路由器协议行为（以 INCLUDE , ANY为例， EXCLUDE, NULL 可类推）：
a、 路由器过滤模式：
IGMPV3/MLDV2路由器过滤模式定义是为了简化路由器内部的状态数 目， 具体操作为当收到一个源过滤模式 EXCLUDE的报文时， 路由器的过滤 模式即设为 EXCLUDE。如果不存在 EXCLUCE的源， 当 group-timer超时时， 路由器过滤模式转换为 INCLUDE。
在优化协议中， 由于路由器不进行模式设定和转换， 而只采用 INCLUDE 过滤模式处理收到的成员报告， 所以现有路由器侧的协议中的 EXCLUDE模 式没有存在的意义， 因而取消路由器的模式定义， 此时路由器的接收状态的 概念模型为：
( multicast address , group timer , ( source records ) ) ；
( 6 )
式（6 ) 中, multicast address 为该状态记录对应的組地址； group timer 用于判定与路由器相连的网絡是否有非特定源的组接收状态； source records 表示源己录。
b、 定时器的相关操作：
在原协议中， 接口的组定时器是在 EXCLUDE模式下使用的， 它表示了 路由器从 EXCLUDE过滤模式转换为 INCLUDE模式的超时时间。 路由器的 源定时器为每个源记录维护。
在优化协议中， 不使用组定时器标识 EXCLUDE模式， 而是采用组定时 器表示一个非特定源的组。 这时与组定时器相关的协议行为参见表三：
组定时器取值 意义与操作
G— Timer > 0 表明相连的网络有非特定源的组接收状态
G— Timer = = 0 说明所连网络没有非特定源的组接收状态， 这时
1 如果该组中有运行的源定时器， 说明网络上还 存在该组的源特定组接收状态。 2 如果该组中所有源定时器超时， 说明网络上也 没有该组的源特定组接收状态， 则删除组记录；
c、 源特定转发规则：
在优化协议中， 当连接子网的组播路由器接收到一个组播报文时， 需要 根据 IGMPV3/MLDV2 的信息判定是否将所需的报文转发到子网上。 具体的 判定规则参见表四：
Figure imgf000013_0001
表四
d、 接收到主机成员报告报文的操作：
原协议中， 当接收到组记录之后, 路由器需要更新组定时器与源定时器， 并可能导致路由器的过滤模式发生变化。 在优化协议中， 相应的操作行为参 见表五： 组定时器 原源列表 接收到的报告 新源列表 操作 IGMPV3/MLDV2
G— TIMER = 0 A IS_IN(B) A+B B定时器设为 GMI/MALI
G— TIMER = 0 A IS一 EX(NULL) A 组定时器设为 GMI/MALI
G— TIMER > 0 A IS— IN(B) A+B B定时器设为 GMI/MALI
G_TIMER> 0 A IS_EX(NULL) A 组定时器设为 GMI/MALI 表五
其中 GMI ( Group Member Interval )为 IGMPV3协议中定义的组成员关 系超时定时器， MALI ( Multicast Address Listening Interval )为 GMI在 MLDV2 中的对应部分。
e、 收到源列表变化记录的操作方法：
原协议在收到过滤模式变化和源列表变化的报文之后， 会有一系列的处 理和转换机制。 在优化协议中， 路由器不进行模式设定和转换， 而只采用 INCLUDE过滤模式处理收到的成员报告， 即路由器只处理源列表变化记录报 告， 相应的操作行为参见表六：
Figure imgf000014_0001
表六
5、 与其他版本的 IGMPV3 MLDV2的兼容性处理（以 INCLUDE , ANY 为例， EXCLUDE, NULL可类推）：
在 RFC3376 和 RFC3810 中 描 述 了 IGMPV3/MLDV2 与 IGMPV2 GMPV1/MLDV1 的兼容方法。 优化的 IGMPV3/MLDV2 与原 IGMPV3/MLDV2的兼容原则是相同的。但由于模式定义的变化， 需要引入一 些特殊的处理。 a、 与 IGMPV1/IGMPV2/MLDV1之间的兼容处理， 参见表七：
Figure imgf000015_0001
表七
b、 与 IGMPV3/MLDV2之间的兼容处理， 参见表八:
Figure imgf000015_0002
表八
显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种优化组管理协议的方法， 其特征在于， 包括下列步骤：
组成员向组播路由器发送成员报告；
组播路由器收到成员报告后，判断该报告中是否包含排除模式 EXCLUDE 的非空源列表， 若是， 则按照非特定源的加入更新路由器内部的相应状态； 否则， 以该报告的内容直接完成路由器内部相应状态的更新。
2、 如权利要求 1所述的方法， 其特征在于， 组成员向组播路由器发送包 含非空源列表的包含模式 INCLUDE的成员报告， 以完成特定源的加入操作。
3、 如权利要求 1所述的方法， 其特征在于， 组播路由器收到非特定源的 加入报告， 则按照 INCLUDE模式处理。
4、 如权利要求 3所述的方法， 其特征在于， 组成员向组播路由器发送包 含任意源列表的 INCLUDE模式的成员报告， 以完成非特定源的加入操作。
5、 如权利要求 4所述的方法， 其特征在于， 组成员侧的非特定源加入操 作的接口模型中， 以 INCLUDE ， ANY表示包含任意源列表。
6、 如权利要求 3所述的方法， 其特征在于， 组成员向组播路由器发送包 含空源列表的 EXCLUDE模式的成员报告， 以完成非特定源的加入操作。
7、 如权利要求 6所述的方法， 其特征在于， 组成员侧的非特定源加入操 作的接口模型中， 以 EXCLUDE ， NULL表示排除空源列表。
8、 如权利要求 3所述的方法， 其特征在于， 若组播路由器收到包含非空 源列表的 EXCLUDE 模式的成员报告， 则按照收到包含任意源列表的 INCLUDE模式的成员报告或收到包含空源列表的 EXCLUDE模式的成员报 告处理。
9、 如权利要求 1至 8任一项所述的方法， 其特征在于， 组成员启动组播 应用时， 或者组成员收到组播路由器定时发来的查询^ 1艮文时， 组成员向组播 路由器发送成员报告， 以报告接口当前的组接收状态。
.
10、 一种组播路由器， 用于实现组成员关系的收集与维护， 其特征在于， 所述组播路由器还包括：
判断模块， 用于判断收到成员报告是否包含排除模式 EXCLUDE的非空 源列表， 若是， 则触发转换模块； 否则， 触发识别模块；
转换模块， 用于将收到的成员报告转换为非特定源的加入报告， 并交由 识别模块处理；
识别模块， 用于识别非特定源的加入^ =艮告， 并完成路由器内部相应状态 的更新。
11、 如权利要求 10所述的路由器， 其特征在于， 所述识别模块将包含任 意源列表的 INCLUDE模式的成员报告， 以及包含空源列表的 EXCLUDE模 式的成员报告认定为非特定源的加入报告。 '
12、 如权利要求 11所述的路由器， 其特征在于， 所述转换模块将包含非 空源列表的 EXCLUDE模式的成员报告转换为可被所述识别模块认定为非特 定源加入的报告。 .
13、 一种组播系统， 包括： 若干组成员， 其特征在于， 所述系统还包括： 组播路由器， 用于以 INCLUDE过滤模式处理组成员发来的 EXCLUDE模式 的成员报告和 INCLUDE模式的成员报告。
14、 如权利要求 13所述的系统， 其特征在于， 所述组播路由器包括下列 子模块：
判断模块， 用于判断收到成员报告是否包含排除模式 EXCLUDE的非空 源列表， 若是， 则触发转换模块； 否则， 触发识别模块；
转换模块， 用于将收到的成员报告转换为非特定源的加入报告， 并交由 识别模块处理；
识别模块， 用于识别非特定源的加入报告， 并完成路由器内部相应状态 的更新。 '
15、 如权利要求 14所述的系统， 其特征在于， 所述识别模块将包含任意 源列表的 INCLUDE模式的成员报告， 以及包含空源列表的 EXCLUDE模式 的成员报告认定为非特定源的加入报告。
16、 如权利要求 15所述的系统， 其特征在于， 所述转换模块将包含非空 源列表的 EXCLUDE模式的成员报告转换为可被所述识别模块认定为非特定 源加入的 艮告。
PCT/CN2006/003289 2006-05-26 2006-12-05 Procédé d'optimisation de protocole de gestion de groupe et serveur et système associés WO2007137464A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
ES06828243T ES2428372T3 (es) 2006-05-26 2006-12-05 Método para la optimización del protocolo de gestión de grupos, y servidor y sistema del mismo
EP06828243.3A EP2023563B1 (en) 2006-05-26 2006-12-05 A method for optimizing group management protocol and server and system thereof
US12/277,050 US8102870B2 (en) 2006-05-26 2008-11-24 System, server and method for optimizing a group management protocol
US13/326,811 US8625591B2 (en) 2006-05-26 2011-12-15 System, server and method for optimizing a group management protocol

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610080979.3 2006-05-26
CN2006100809793A CN101079728B (zh) 2006-05-26 2006-05-26 一种优化组管理协议的方法、服务器及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/277,050 Continuation US8102870B2 (en) 2006-05-26 2008-11-24 System, server and method for optimizing a group management protocol

Publications (1)

Publication Number Publication Date
WO2007137464A1 true WO2007137464A1 (fr) 2007-12-06

Family

ID=38778092

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003289 WO2007137464A1 (fr) 2006-05-26 2006-12-05 Procédé d'optimisation de protocole de gestion de groupe et serveur et système associés

Country Status (5)

Country Link
US (2) US8102870B2 (zh)
EP (1) EP2023563B1 (zh)
CN (1) CN101079728B (zh)
ES (1) ES2428372T3 (zh)
WO (1) WO2007137464A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE602007011653D1 (de) * 2007-06-26 2011-02-10 Media Patents Sl Router zur Verwaltung von Multicastgruppen
WO2009049659A1 (en) 2007-10-15 2009-04-23 Soporte Multivendor S.L. Method for managing multicast traffic in a data network and network equipment using said method
WO2009109684A1 (es) 2008-03-05 2009-09-11 Media Patents, S. L. Procedimiento para monitorizar o gestionar equipos conectados a una red de datos
US8379641B2 (en) * 2009-07-20 2013-02-19 Telefonaktiebolaget L M Ericsson (Publ) Light host management protocol on multicast capable router
US8325725B2 (en) * 2009-07-20 2012-12-04 Telefonaktiebolaget L M Ericsson (Publ) Efficient host management protocol on multicast capable router
US8189584B2 (en) * 2009-07-27 2012-05-29 Media Patents, S. L. Multicast traffic management in a network interface
CN101719919B (zh) * 2009-12-09 2012-09-05 中兴通讯股份有限公司 一种实现组播源控制的方法及装置
CN105491558A (zh) * 2014-09-18 2016-04-13 北京信威通信技术股份有限公司 一种集群组的IPv6组播地址生成方法
CN108809840B (zh) * 2018-06-12 2021-04-13 天津卓越信通科技有限公司 一种用于控制和管理子网中组播组的方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006053027A2 (en) * 2004-11-09 2006-05-18 Nexthop Technologies, Inc. Systems and methods for multicast routing on packet switched networks

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4077330B2 (ja) * 2003-02-06 2008-04-16 富士通株式会社 データ生成装置
US7724739B2 (en) * 2005-03-18 2010-05-25 Cisco Technology, Inc. Source specific multicast layer 2 networking device and method
US7813287B2 (en) * 2007-08-29 2010-10-12 Alcatel Lucent Fast TV channel changing in IPTV network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006053027A2 (en) * 2004-11-09 2006-05-18 Nexthop Technologies, Inc. Systems and methods for multicast routing on packet switched networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LI HAIHUA AND WANG XIUFA: "Analysis of IGMPv3", COMPUTER & DIGITAL ENGINEERING, no. 2, 28 February 2005 (2005-02-28), pages 24 - 27, XP008090711 *

Also Published As

Publication number Publication date
EP2023563A1 (en) 2009-02-11
EP2023563A4 (en) 2009-07-15
US20120087371A1 (en) 2012-04-12
US20090219933A1 (en) 2009-09-03
US8625591B2 (en) 2014-01-07
US8102870B2 (en) 2012-01-24
CN101079728A (zh) 2007-11-28
ES2428372T3 (es) 2013-11-07
CN101079728B (zh) 2010-11-10
EP2023563B1 (en) 2013-07-03

Similar Documents

Publication Publication Date Title
WO2007137464A1 (fr) Procédé d'optimisation de protocole de gestion de groupe et serveur et système associés
CN100396055C (zh) 组播源过滤的处理方法
US8571028B2 (en) Methods and apparatus for managing multicast traffic
Christensen et al. Considerations for Internet group management protocol (IGMP) and multicast listener discovery (MLD) snooping switches
US7590116B2 (en) Method for forwarding multicast message in network communication
JP5196685B2 (ja) マルチキャストグループを管理する方法と装置
JP4077330B2 (ja) データ生成装置
JP5653912B2 (ja) マルチキャスト・グループ管理のための方法及び装置
US20080002727A1 (en) Packet relay device
US20060198394A1 (en) Network system and gateway device
US20050195817A1 (en) Switching device and multicast packet processing method therefor
JP5343127B2 (ja) 端末マルチキャスト状態の取得方法
JP2009094832A (ja) マルチキャストデータ配信装置、その配信方法およびその配信制御プログラム
WO2008069455A1 (en) Method and apparatus for blocking forged multicast packets
WO2007059679A1 (fr) Procede pour le traitement de service multidiffusion anormal et equipement de reseau associe
WO2007054006A1 (fr) Station de base de système d’accès sans fil large bande et système pour réaliser un service de diffusion de groupe
WO2008138248A1 (fr) Procédé, carte d'interface et routeur destinés à transmettre un message
WO2009024054A1 (fr) Procédé, dispositif et système pour réaliser l'agent de protocole de gestion pour des membres dans un groupe de multidiffusion
WO2009030143A1 (fr) Système et procédé de routage multidiffusion, passerelle multimédia et contrôleur de passerelle multimédia
CN108111323B (zh) vxworks系统下igmpsnooping协议的实现系统
JP5553425B2 (ja) マルチキャスト配信システム、配信ルータ、および、マルチキャスト配信方法
US20100135298A1 (en) Method and system for providing source specific multicast service on ethernet network
WO2012103694A1 (zh) 一种二层组播路径跟踪方法、装置及系统
KR20050073947A (ko) 분산구조 라우터에서 멀티캐스트 패킷 처리장치 및 그 방법
JP3652964B2 (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: 06828243

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2006828243

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE