WO2008058428A1 - Méthode de multidiffusion d'une source spécifique - Google Patents

Méthode de multidiffusion d'une source spécifique Download PDF

Info

Publication number
WO2008058428A1
WO2008058428A1 PCT/CN2006/003101 CN2006003101W WO2008058428A1 WO 2008058428 A1 WO2008058428 A1 WO 2008058428A1 CN 2006003101 W CN2006003101 W CN 2006003101W WO 2008058428 A1 WO2008058428 A1 WO 2008058428A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
channel
mode
layer
switch
Prior art date
Application number
PCT/CN2006/003101
Other languages
English (en)
Chinese (zh)
Inventor
Yancong Ma
Qinxue Li
Original Assignee
Zte Corporation
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 Zte Corporation filed Critical Zte Corporation
Priority to CN200680055256.6A priority Critical patent/CN101480010B/zh
Priority to PCT/CN2006/003101 priority patent/WO2008058428A1/fr
Publication of WO2008058428A1 publication Critical patent/WO2008058428A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present invention relates to the field of communications, and in particular to a specific source multicast method, which relates to
  • IGMPv3 Internet Group Member Protocol version 3
  • IGMPvl and IGMPv2 Internet Multicast Management Protocol Version 1 and Version 2
  • ASM Any Source Multicast
  • any source multicast system there are some inherent defects, such as address allocation and access control issues, which cannot prevent address conflicts between multiple applications.
  • Once a receiver joins a multicast group it will forward any source to the multicast group. The data. Even if a multicast source obtains a multicast group address to send data, there is no guarantee that no other source will use this address.
  • SSM Specific Source Multicast
  • the service provided by the SSM to the network layer is a "channel” that uses the destination IP address of the specific multicast (G) and the source IP address.
  • the address S (Source Address) is "channel", and the recipient can receive these datagrams by joining the (S, G) channel.
  • SSM mitigates and compensates for the shortcomings of ASM.
  • the specific source multicast defines the IP address G and the source IP address S (S, G), and the G is extended by S, for example (SI, G) and (S2, G), although they have the same The group address G, but represents two channels by S1 and S2, respectively. This avoids the problem of globally assigning multicast addresses of specific source multicast destinations.
  • Each multicast source can separately handle address conflicts between multiple channels it creates.
  • access control when a receiver joins a (S, G) channel, it can only receive data sent by the source S. Instead, any host can send data to an ASM host multicast group.
  • the specific source multicast is automatically guaranteed not to There are other senders that send data on one channel. This makes it much more difficult to send spam on a particular source multicast channel than on any source multicast group.
  • the SSM In the process of processing a well-known multicast source, the SSM only needs to maintain a source-based forwarding tree. The shared tree system in the multicast routing protocol is no longer needed. This will greatly reduce the multicast routing structure.
  • Layer 3 routers can control the forwarding of multicast packets.
  • multicast packets inevitably pass through some Layer 2 switching devices, such as Layer 2 switches, especially in a LAN environment. If a Layer 2 switch does not process multicast packets, it floods all interfaces of the Layer 2 switch, causing waste of resources and affecting performance.
  • IGMP Snooping is usually used to solve this problem in any source multicast system.
  • the receiving host sends an IGMP member report message.
  • the Layer 2 switch passes the Layer 2 switch, the Layer 2 switch listens to the message and records the relationship between the group member and the interface.
  • the multicast packet When a multicast packet is received, the multicast packet is forwarded only to the interface that has the member of the group. After the Layer 2 switch processes the IGMP protocol packet, it forwards the protocol packet to the Layer 3 device interface intact.
  • the IGMP multicast member management mechanism is designed for the Layer 3, and the Layer 3 router can control the forwarding of multicast packets.
  • Layer 2 switches in a specific source multicast cannot process multicast packets, causing flooding to all interfaces of the Layer 2 switch, resulting in waste of resources and impact on performance. .
  • the present invention is directed to a specific source multicast method for solving the problem that a specific source multicast cannot be implemented on a layer 2 switch in the related art.
  • a specific source multicast method for a network including a Layer 2 switch and a Layer 3 switch comprising the steps of: dividing a VLAN resource into a specific source multicast dedicated in a Layer 2 switch, and The working area of the VLAN resource is divided; the (S, G) channel is added in the working domain; the IGMP protocol packet sent by the port is matched with the (S, G) channel in the VLAN resource; and the packet is reassembled according to the matching situation. And forwarded to the Layer 3 switch.
  • adding the (S, G) channel in the working domain includes the following steps: Specifying a source port and a receiving port in the working domain, where the source port is a program source port in the VLAN resource, and the receiving port Is the section view port in the VLAN resource.
  • the matching includes the following steps: If the message is consistent with the (S, G) channel, the port is added to the (S, G) channel; if the message conflicts with the (S, G) channel, Then delete the port in the (S, G) channel.
  • determining whether the packet and the (S, G) channel are consistent includes the following steps: parsing all channel request information in the packet, and then (S, G) channel configured on the layer 2 switch Matches to determine whether the port is a traffic port or a traffic-free port. If it is a traffic port, it is the same, otherwise it is a conflict.
  • parsing all the channel request information in the packet includes the following steps: Decomposing the packet in units of group records to obtain channel request information, where each channel of the request is configured as a request type ⁇ R , (S, G) ⁇ , mark the request type as ⁇ Join, (S, G) ⁇ and ⁇ Leave, (S, G) ⁇ .
  • the judgment criterion of ⁇ Join, (S, G) ⁇ is as follows: If the record type is MODE-IS-INCLUDE or CHANGE-TO-INCLUDE-MODE, the message contains (S, G) If the record type is MODE—IS—EXCLUDE or CHANGE—TO—EXCLUDE—MODE, the message does not contain (S, G) items; the record type is ALLOW_NEW—SOURCES, and the current filter mode is INCLUDE, then the message contains ( S, G); The record type is BLOCK_OLD_SOURCES, and the current filter mode is EXCLUDE, then the message contains (S, G) entries.
  • the judgment criterion of ⁇ Leave, (S, G) ⁇ is as follows: If the record type is MODE JS—INCLUDE or CHANGE_TO—INCLUDE_MODE, the message does not contain (S, G) Item; record type is MODE-IS-EXCLUDE or CHANGE-TO-EXCLUDE-MODE, the message does not contain (S, G) items; record type is ALLOW_NEW__SOURCES, the current filter mode is EXCLUDE, then the message contains (S, G); the record type is BLOCK_OLD_SOURCES, and the current filter mode is INCLUDE, then the message contains (S, G) entries.
  • adding a port includes the following steps: When the channel request information of the port is ⁇ Join, (S, G) ⁇ , the (S, G) channel is searched, if it does not match, the ⁇ Join, (S, G ) ⁇ will be discarded; if it matches, add a port in the (S, G) channel.
  • deleting a port includes the following steps: When the channel request information of the port is ⁇ Leave, (S, G) ⁇ , the port is deleted in the (S, G) channel.
  • reassembling the IGMP protocol packet and forwarding it to the Layer 3 switch includes the following steps:
  • the Layer 2 switch encapsulates the IGMP protocol packet into multiple MODE-ISJNCLUDE records [G, SI], [G, S2], [G, S3] . ⁇ .., and then forward these records to the Layer 3 switch through different channels.
  • the present invention achieves the following technical effects: This document provides a method for implementing a Layer 2 switch IGMPv3, which is a "Dominated IGMPv3 Snooping" method.
  • the implementation method performs effective analysis and processing on IGMP v3 packets based on the multicast deployment plan of the Layer 2 and Layer 3 devices, and then splits, converts, records, and transmits the packets to the upper-layer routers.
  • This method is no longer a simple monitoring and recording. It needs to monitor and process IGMPv3 packets according to the deployment of multicast traffic.
  • the method effectively implements the support of the Layer 2 switch for IGMPv3, so that the Layer 2 switch can have a strong specific source multicast function under the existing conditions.
  • FIG. 1 shows a flow chart of a specific source multicast method according to the present invention
  • FIG. 2 shows a flow chart of a specific source multicast method according to an embodiment of the present invention.
  • the present invention provides a specific source multicast implementation method.
  • Step S102 Divide a VLAN resource into a specific source multicast in a Layer 2 switch, and divide the VLAN resource. a working domain; step S104, adding a (&, G) channel in the working domain; step S106, matching an IGMP protocol packet sent by the port with the (S, G) channel in the VLAN resource; and step S108, according to the matching In the case, the message is reassembled and forwarded to the Layer 3 switch.
  • Step S104 may include the following steps: Specifying a source port and a receiving port in the working domain, where the source port is a program source port in the VLAN resource, and the receiving port is a program viewing port in the VLAN resource.
  • the matching may include the following steps: If the message is consistent with the (S, G) channel, then the port is added to the (S, G) channel; if the message and the (S, G) channel conflict, then in the (S, G) channel Delete the port.
  • Determining whether the packet is consistent with the (S, G) channel may include the following steps: parsing all channel request information in the packet, and then matching with the (S, G) channel configured on the layer 2 switch, thereby determining that the port is The flow port is still a no-flow port. If it is a flow-through port, it is the same, otherwise it is a conflict.
  • Parsing all the channel request information in the message may include the following steps: Decomposing the message in units of group records to obtain channel request information, wherein each channel of the request is configured as a request type ⁇ R, (S, G) ⁇ , Request types are labeled ⁇ Join, (S, G) ⁇ and ⁇ Leave, (S, G) ⁇ .
  • the judgment criterion of ⁇ Join, (S, G) ⁇ can be as follows: Record type is MODE—IS—INCLUDE or CHANGE—TO—INCLUDE—MODE, then the message contains (S, G); Record type is MODE—IS— EXCLUDE or CHANGE_TO_EXCLUDE_MODE, the message does not contain (S, G) items; the record type is ALLOW_NEW_SOURCES, the current filter mode is INCLUDE, then the message contains (S, G) items; The type is BLOCK_OLD_SOURCES, and the current filtering mode is EXCLUDE, then the message contains (S, G) items.
  • the judgment criterion of ⁇ Leave, (S, G) ⁇ can be as follows: If the record type is MODE-IS-INCLUDE or CHANGE_TO-INCLUDE-MODE, the message does not contain (S, G) items; the record type is MODE-IS — EXCLUDE or CHANGE— TO— EXCLUDE— MODE , the message does not contain ( S, G) items; the record type is ALLOW_NEW_SOURCES, the current filter mode is EXCLUDE, Then the message contains (S, G) items; the record type is BLOCK_OLD_SOURCES, and the current filtering mode is INCLUDE, then the message contains (S, G) items.
  • Adding a port may include the following steps: When the channel request information of the port is ⁇ Join, (S, G) ⁇ , the (S, G) channel is searched, and if it does not match, the ⁇ Join, (S, G) ⁇ will be thrown. Discard; if matching, add a port in the (S, G) channel. Deleting a port can include the following steps: When the channel request information of the port is ⁇ Leave, (S, G) ⁇ , the port is deleted in the (S, G) channel.
  • Reassembling IGMP protocol packets and forwarding them to Layer 3 switches can include the following steps: Layer 2 switches encapsulate IGMP protocol packets into multiple MODE-IS-INCLUDE records [G, SI], [G, S2], [G, S3 ] , . . . . . , then forward these records to the Layer 3 switch through different channels.
  • the present invention will be described in detail below with reference to FIG. 2 and in conjunction with the embodiments.
  • the method includes the following steps: Step S202. Divide some VLAN (Virtual Local Area Network) resources into multicast for the Layer 2 device. And divide the working domain of the multicast VLAN. Step S204. In the working domain of the multicast VLAN, add several (S, G) channels. Step S206.
  • step S208 Match the IGMP protocol packet sent by the port with the (S, G) channel in the multicast VLAN.
  • step S208 if they are consistent, the port is added to the (S, G) channel.
  • step S210 if there is a conflict, the port is deleted in the (S, G) channel.
  • Step S212 In the multicast VLAN, the packet is reassembled to the Layer 3 device according to the matching with the (S, G) channel.
  • a Layer 2 device identifies a data stream and exchanges data through a VLAN ID (VID) and a destination MAC (Destination Media Access Control) address (DA) in data exchange.
  • VIP VLAN ID
  • DA Destination Media Access Control
  • the present invention divides two parts of VLAN resources on the Layer 2 switch, and a part of the multicast data stream uses a multicast VLAN, and the Layer 3 switching device connected to the Layer 2 switch passes the multicast stream through the multicast VLAN. It is sent to the uplink port of the Layer 2 switch; another part of the VLAN is given to the (S, G) channel.
  • Each (S, G) channel corresponds to an SGVLAN, and the SGVALN is assigned to the (S, G) channel of a specific source address and group address through the network management configuration.
  • the present invention corresponds to the (S, G) channel multicast stream and the layer 2 forwarding stream (VID, DA) by configuring the (S, G) channel.
  • each multicast VLAN corresponds to the same VLAN interface of the Layer 3 device.
  • the (S, G) channel on the Layer 2 switch belongs to a multicast VLAN.
  • IGMPv3 report packets and query packets are processed during IGMPv3 packet processing.
  • the terminal host connected to the Layer 2 switch will send a report message to indicate the (S, G) channel that you want to join or leave.
  • a complete group record mainly consists of three parts, group record type, one group address (G), and one column source address (SI, S2, S3).
  • the types of IGMPv3 group records are as follows:
  • the current state is the inclusion mode (MODE_IS JNCLUDE)
  • the current state is the exclusion mode (MODE_IS—EXCLUDE)
  • Source address list transformation allowing new source addresses ( ALLOW - NEW - SOURCES )
  • Source address list conversion masking the old source address (BLOCK_OLD_SOURCES)
  • the group address and the source address list correspond to the (S, G) channel's permissions for the port are different, whether it is What combination, for the (S, G) channel on the Layer 2 switch, only two results are produced.
  • One is that the port allows the traffic in the (S, G) channel to be received, for the (S, G) channel.
  • the traffic port; the second is that the port is prohibited from receiving traffic in the (S, G) channel, which is the forbidden port of the (S, G) channel.
  • the core problem of the Layer 2 switch in the processing of IGMPv3 report packets is to resolve all (S, G) channels in the packets and then match the (S, G) channels configured on the Layer 2 switch.
  • the port is a flow port or a no-flow port, if it is a flow port, it needs to be at (S, G) The port is added to the channel, otherwise the port is deleted.
  • the Layer 2 switch After processing the channel according to the report message, the Layer 2 switch reassembles the message and encapsulates the message record [G, SI, S2, S3...] into several records [G, SI ], [G, S2], [G, S3], etc., then forward these records to the third layer through different multicast VLANs according to the membership of the (S, G) channel in the Layer 2 switch in the multicast VLAN. device. Specifically, when the Layer 2 switch receives the multicast address as G from the host, and the source address list is MODE_IS-INCLUDE of S1, S2, and S3, for example, the Layer 2 switch receives an IGMP report message from the host.
  • record type is MODE-ISJNCLUDE
  • multicast address is G
  • source address list is SI
  • the port will be decomposed into three MODE-IS-INCLUDE, (SI, G) records will be sent to the multicast VLAN1 interface, (S2, G) records will be sent to the multicast VLAN2 interface, (S3, G) records will be Send to the multicast VLAN3 interface.
  • Such (SI, G), (S2, G), (S3, G) multicast streams will be sent to the Layer 2 switch through different VLANs 1, 2, 3, for the same group address data stream, VLAN1, VLAN2, VLAN3 Corresponding to different VLAN IDs, so that different source IDs can be distinguished by different VLAN IDs, and the correspondence between (S, G) and (VID, G) is realized.
  • the source port and the receiving port are first specified in the multicast working domain, where the source port is a program source port in the multicast VLAN, and for the layer 2 switch, it is usually a port associated with the layer 3 router; It is the program viewing port, usually the program out port, so the packets of the non-source port and the receiving port will be ignored. Then, the report message is decomposed in units of group records, and the request information of the port for several channels is obtained.
  • Each channel is configured as a request type (R: Request) plus channel information (S, G), abbreviated as ⁇ R, (S , G) ⁇
  • the request type has two types: Join and Leave, which are labeled ⁇ Join, (S, G) W ⁇ Leave, (S, G) ⁇ .
  • the judgment criteria of ⁇ Join, (S, G) ⁇ in the message are as follows:
  • the record type is MODE—IS—INCLUDE or CHANGE—TO—INCLUDE—MODE, and the message contains (S, G) items;
  • the record type is MODE_IS—EXCLUDE or CHANGEJTO—EXCLUDE—MODE, and the message does not contain (S, G) items; 3.
  • the record type is ALLOW-NEW-SOURCES, the current filter mode is INCLUDE, and the message contains (S, G) items; _ ;
  • the record type is BLOCK_OLD_SOURCES, and the current filter mode is EXCLUDE, the message contains (S, G) items; the judgment criteria of ⁇ Leave, (S, G) ⁇ in the message are as follows:
  • the record type is MODE—ISJNCLUDE or CHANGE—TOJNCLUDE—MODE, and the message does not contain (S, G) items;
  • the type of record is MODE—IS—EXCLUDE or CHANGE—TO—EXCLUDE—MODE, and the message does not contain (S, G) items;
  • the record type is ALLOW-NEW_SOURCES, the current filter mode is EXCLUDE, and the message contains (S, G) entries;
  • Step 1 Decompose the IGMPv3 report received by the receiving port in units of group records. , get a series of ⁇ Join, (S, G) p ⁇ Leave, (S, G) ⁇ , and then process them one by one.
  • Step 2. When ⁇ Join, (S, G) ⁇ is processed, search for the (S, G) channel configured in each multicast VLAN configured on the Layer 2 switch.
  • the received query messages will be sent to all receiving ports in the multicast VLAN.
  • the present invention achieves the following beneficial effects.
  • This document provides a method for implementing a Layer 2 switch IGMPv3, which is a "Dominated IGMPv3 Snooping" method.
  • the implementation method effectively analyzes and processes IGMP v3 packets based on the multicast deployment plan of the Layer 2 and Layer 3 devices, splits, converts, records, and delivers them to the upper-layer routers. This method is no longer a simple monitoring and recording. It needs to monitor and process IGMPv3 packets according to the deployment of multicast traffic.
  • the method effectively implements the support of the Layer 2 switch for IGMPv3, so that the Layer 2 switch can have a strong specific source multicast function in the existing device.

Landscapes

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

Abstract

L'invention porte sur une méthode de multidiffusion d'une source spécifique s'appliquant à un réseau comprenant une couche de commutation 2 et une couche de commutation 3. Ladite méthode comporte les étapes suivantes: diffusion de la ressource RLV particulièrement pour la multidiffusion de la source spécifique dans la couche de commutation 2 et division du domaine de travail de la ressource RLV; adjonction du canal (S, G) au domaine de travail; appariement du message de protocole IGMP provenant du port avec le canal (S, G) dans la ressource VLAN; et selon le résultat de l'appariement, reconstitution du message et sa transmission sur la couche de commutation 3.
PCT/CN2006/003101 2006-11-17 2006-11-17 Méthode de multidiffusion d'une source spécifique WO2008058428A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN200680055256.6A CN101480010B (zh) 2006-11-17 2006-11-17 特定源组播方法
PCT/CN2006/003101 WO2008058428A1 (fr) 2006-11-17 2006-11-17 Méthode de multidiffusion d'une source spécifique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2006/003101 WO2008058428A1 (fr) 2006-11-17 2006-11-17 Méthode de multidiffusion d'une source spécifique

Publications (1)

Publication Number Publication Date
WO2008058428A1 true WO2008058428A1 (fr) 2008-05-22

Family

ID=39401304

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003101 WO2008058428A1 (fr) 2006-11-17 2006-11-17 Méthode de multidiffusion d'une source spécifique

Country Status (2)

Country Link
CN (1) CN101480010B (fr)
WO (1) WO2008058428A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102185785A (zh) * 2011-06-07 2011-09-14 杭州华三通信技术有限公司 一种二层转发芯片及其实现方法
CN106302188A (zh) * 2015-05-18 2017-01-04 中兴通讯股份有限公司 一种交换机设备的组播报文转发控制方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1378365A (zh) * 2002-05-10 2002-11-06 北京港湾网络有限公司 一种ip组播路由转发优化方法
CN1555165A (zh) * 2003-12-26 2004-12-15 三层交换中ip组播精确端口转发的方法
CN1852232A (zh) * 2005-11-29 2006-10-25 华为技术有限公司 源特定组播和源无关组播配合的组播方法及其接入设备
CN1863153A (zh) * 2005-10-09 2006-11-15 华为技术有限公司 以太网支持源特定组播转发的方法及其设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1378365A (zh) * 2002-05-10 2002-11-06 北京港湾网络有限公司 一种ip组播路由转发优化方法
CN1555165A (zh) * 2003-12-26 2004-12-15 三层交换中ip组播精确端口转发的方法
CN1863153A (zh) * 2005-10-09 2006-11-15 华为技术有限公司 以太网支持源特定组播转发的方法及其设备
CN1852232A (zh) * 2005-11-29 2006-10-25 华为技术有限公司 源特定组播和源无关组播配合的组播方法及其接入设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102185785A (zh) * 2011-06-07 2011-09-14 杭州华三通信技术有限公司 一种二层转发芯片及其实现方法
CN106302188A (zh) * 2015-05-18 2017-01-04 中兴通讯股份有限公司 一种交换机设备的组播报文转发控制方法及装置

Also Published As

Publication number Publication date
CN101480010B (zh) 2012-06-27
CN101480010A (zh) 2009-07-08

Similar Documents

Publication Publication Date Title
US7835276B2 (en) Admission control mechanism for multicast receivers
US8339973B1 (en) Multicast traceroute over MPLS/BGP IP multicast VPN
US7590120B2 (en) Enhanced multicast VLAN registration
CN100450086C (zh) 在虚拟专用局域网业务中实现组播数据流转发的方法
CN101616014B (zh) 一种实现跨虚拟专用局域网组播的方法
CN102215172B (zh) 一种实现跨虚拟专用局域网组播的方法和***
EP1318628A1 (fr) Dispositif et procédé destiné à diriger du trafic multidiffusion dans un reseau Ethernet MAN
CN100442770C (zh) 一种在bgp/mpls vpn实现组播的方法
WO2010075771A1 (fr) Procédé de mise en réseau par extranet, système et procédé pour réseau privé virtuel en multidiffusion
CN102137000B (zh) 一种建立切换组播分发树的方法、装置及***
WO2006063513A1 (fr) Procede de multidiffusion dans un reseau prive virtuel utilisant un routeur virtuel
JP2003032287A (ja) ネットワーク間接続方法、その装置およびその装置を用いたシステム
WO2007056923A1 (fr) Procede de mise en oeuvre de la multidiffusion
US9264244B2 (en) Multicasting in a provider backbone bridge network
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
WO2007059679A1 (fr) Procede pour le traitement de service multidiffusion anormal et equipement de reseau associe
US20110274109A1 (en) Multicast Quality Of Service Module And Method
WO2011020346A1 (fr) Procédé et appareil de réacheminement de données de diffusion groupée
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
US20060029001A1 (en) Multicast source discovery
CN101083664A (zh) 一种防止二层组播数据流洪泛的方法
WO2007041942A1 (fr) Système pour ethernet de support de la transmission de la multidiffusion spécifique à une source et procédé idoine
WO2008058428A1 (fr) Méthode de multidiffusion d'une source spécifique
WO2007059699A1 (fr) Procede et entite de relais de donnees pour le relais de la trame de donnees par l'entite de relais de donnees
WO2008141516A1 (fr) Procédé de transmission d'un message, dispositif de transmission et système de transmission

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680055256.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06805250

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06805250

Country of ref document: EP

Kind code of ref document: A1