Multicast forwarding methods and apparatuses across autonomous systems
US-2024275714-A1 · Aug 15, 2024 · US
US9344286B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9344286-B2 |
| Application number | US-201214004489-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 7, 2012 |
| Priority date | Mar 11, 2011 |
| Publication date | May 17, 2016 |
| Grant date | May 17, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are a multicast data forwarding method and device supporting a virtual terminal. The method includes: a bridge forwarding module receiving multicast data sent by an end station and determining output ports; when a certain output port is the same with the input port of the multicast data and the input port has enabled reflective relay function, not carrying Ingress extended channel identifier (Ingress_E-CID) in the forwarded message information or the value of the Ingress_E-CID being zero. By modifying the source port filtering mechanism, the present invention enables a Port Extender (PE) supporting the virtual terminal technology to transmit and receive data normally while multicasting.
Opening claim text (preview).
What is claimed is: 1. A multicast data forwarding method supporting virtual terminal, comprising: a bridge forwarding module receiving multicast data sent by an end station and determining an output port, when a certain output port is the same with the input port of said multicast data and said input port has enabled a reflective relay function, not carrying an ingress extended channel identifier (Ingress_E-CID) in forwarded message information or the value of said Ingress_E-CID being equal to 0. 2. The method according to claim 1 , further comprising: said bridge forwarding module also determining the value of extended channel identifier (E-CID) carried in said forwarded message information. 3. The method according to claim 2 , wherein, said bridge forwarding module refers to a VLAN-aware Bridge Component in a Controlling Bridge in an Ethernet switch. 4. The method according to claim 1 , wherein, said input port and output port belong to a same replication group. 5. The method according to claim 4 , wherein, said bridge forwarding module refers to a VLAN-aware Bridge Component in a Controlling Bridge in an Ethernet switch. 6. The method according to claim 1 , wherein, said bridge forwarding module refers to a VLAN-aware Bridge Component in a Controlling Bridge in an Ethernet switch. 7. The method according to claim 6 , wherein, after receiving said forwarded message information, an internal port extended forwarding module (Port Extender) of said Controlling Bridge adds an extended tag (E-tag) into said multicast data according to said Ingress_E-CID carried in said forwarded message information; after receiving said multicast data, an Extended Port of an Edge Port Extender checks the value of said Ingress_E-CID in said E-tag, and if the value of said Ingress_E-CID is consistent with a port extended channel identifier (PCID) of said extended port, said data is filtered out. 8. A multicast data forwarding method supporting virtual terminal, comprising: a bridge forwarding module receiving multicast data sent by an end station and determining an output port, when a certain output port is the same with the input port of said multicast data and said input port has disabled a reflective relay function, carrying an ingress extended channel identifier (Ingress_E-CID) in forwarded message information and the value of said carried Ingress_E-CID being equal to E-CID when said multicast data is inputted. 9. The method according to claim 8 , further comprising: said bridge forwarding module also determining the value of said E-CID carried in said forwarded message information. 10. The method according to claim 9 , wherein, said input port and output port belong to a same replication group. 11. The method according to claim 8 , wherein, said input port and output port belong to a same replication group. 12. A multicast data forwarding device supporting virtual terminal, applied to an Ethernet switch, said device comprising a processer which executes the steps in a port determination unit and a forwarding determination unit in a bridge forwarding module, wherein, said port determination unit is configured to: receive multicast data sent by an end station and determine an output port; said forwarding determination unit is configured to: according to said output port determined by said port determination unit, when a certain output port is the same with the input port of said multicast data and said input port has enabled a reflective relay function, not carry ingress extended channel identifier (Ingress_E-CID) in forwarded message information or make the value of said Ingress_E-CID equal 0. 13. The device according to claim 12 , wherein, said forwarding determination unit is further configured to: determine the value of E-CID carried in said forwarded message information. 14. The device according to claim 13 , wherein, said bridge forwarding module refers to a VLAN-aware Bridge Component in a Controlling Bridge in an Ethernet switch; said processor in said device further executes the steps in an edge port extended forwarding module, and an internal port extended forwarding module in said Controlling Bridge; said internal port extended forwarding module is configured to: after receiving said forwarded message information, according to said Ingress_E-CID carried in said forwarded message information, add an extended tag (E-tag) into said multicast data; said edge port extended forwarding module is configured to: after receiving said multicast data from an extended port, check the value of said Ingress_E-CID value in said E-tag, and if the value of said Ingress E-CID is consistent with PCID of said extended port, filter out said data. 15. The device according to claim 12 , wherein, said forwarding determination unit is further configured to: determine that said output port and input port belong to a same replication group. 16. The device according to claim 15 , wherein, said bridge forwarding module refers to a VLAN-aware Bridge Component in a Controlling Bridge in an Ethernet switch; said processor in said device further executes the steps in an edge port extended forwarding module, and an internal port extended forwarding module in said Controlling Bridge; said internal port extended forwarding module is configured to: after receiving said forwarded message information, according to said Ingress_E-CID carried in said forwarded message information, add an extended tag (E-tag) into said multicast data; said edge port extended forwarding module is configured to: after receiving said multicast data from an extended port, check the value of said Ingress_E-CID value in said E-tag, and if the value of said Ingress E-CID is consistent with PCID of said extended port, filter out said data. 17. The device according to claim 12 , wherein, said bridge forwarding module refers to a VLAN-aware Bridge Component in a Controlling Bridge in an Ethernet switch; said processor in said device further executes the steps in an edge port extended forwarding module, and an internal port extended forwarding module in said Controlling Bridge; said internal port extended forwarding module is configured to: after receiving said forwarded message information, according to said Ingress_E-CID carried in said forwarded message information, add an extended tag (E-tag) into said multicast data; said edge port extended forwarding module is configured to: after receiving said multicast data from an extended port, check the value of said Ingress_E-CID value in said E-tag, and if the value of said Ingress E-CID is consistent with PCID of said extended port, filter out said data. 18. A multicast data forwarding device supporting virtual terminal, applied to an Ethernet switch, said device comprising a processer which executes the steps in a port determination unit and a forwarding determination unit in a bridge forwarding module, wherein, said port determination unit is configured to: receive multicast data sent by an end station and determine an output port; said forwarding determination unit is configured to: according to said output port determined by said port determination unit, when a certain output port is the same with the input port of said multicast data and said input port has disabled a reflective relay function, carrying an ingress extended channel identifier (Ingress_E-CID) in forwarded message information and make the value of said carried Ingress_E-CID equal E-CID used when inputting said multicast data. 19. The device according to claim 18 ,
Multipoint routing · CPC title
Multicast operation; Broadcast operation · CPC title
Packet switching systems · CPC title
for broadcast or conference {, e.g. multicast} · CPC title
Remote access server, e.g. BRAS · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.