CN103973576B - A kind of processing method and the network equipment of link local multicast message - Google Patents
A kind of processing method and the network equipment of link local multicast message Download PDFInfo
- Publication number
- CN103973576B CN103973576B CN201410220227.7A CN201410220227A CN103973576B CN 103973576 B CN103973576 B CN 103973576B CN 201410220227 A CN201410220227 A CN 201410220227A CN 103973576 B CN103973576 B CN 103973576B
- Authority
- CN
- China
- Prior art keywords
- unicast
- address
- local multicast
- multicast address
- link local
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Abstract
The present invention proposes a kind of processing method of link local multicast message, the described method includes：Empty the link local multicast address safeguarded in local multicast address table；Unicast corresponding with the link local multicast address is created in unicast routing table and substitutes route table items；When receiving the message that destination address is link local multicast address, according to the unicast that is created in unicast routing table substitute route table items by after the message up sending in processing locality.The forward efficiency of multicast message can be improved by the present invention, while save the memory space of local multicast address table.
Description
Technical field
The present invention relates to field of communication technology, more particularly to a kind of processing method of link local multicast message and network to set
It is standby.
Background technology
Link local (Link Local) multicast address is a kind of special multicast group address, is link for destination address
The multicast data message of local address, without the forwarding of cross-network segment.That is the sender of link local multicast and reception
In the same network segment, data message only forwards person in this network segment, it is not necessary to will can not be spread to other network segments.
The scope of the link local multicast address of IPv4 is 224.0.0.0~224.0.0.255；The link local group of IPv6
It is FF02 to broadcast address realm::1~FF02::FF；For the data packet using multicast address in the range of this as purpose address, no
It is how many by TTL (Time to Live, life span) value in the data packet, all without being forwarded out local network segment.
For the network equipment, meeting preserves the ground for the link local multicast group that total interface is added in multicast address
Location, when either interface receives data message, first looks for singlecast router forwarding-table item, if the data message is multicast report
Text, then search local multicast address table, compared in local multicast address table the multicast data message destination address whether be
The address for the link local multicast group that this interface is added, if directly the message up sending is handled to local host,
It is forwarded to if not multicast forwarding list item is then further searched for.
It can be seen from the above that local interface needs to be searched twice to the multicast message of received link local, and for general
Logical multicast message then needs to be searched three times, and forward efficiency is low；Meanwhile the link local multicast group that each interface is added
Address will be saved in local multicast address table, waste of storage space can be caused.
The content of the invention
In view of this, the present invention proposes a kind of processing method of link local multicast message, applied on the network equipment, institute
The method of stating includes：
Empty the link local multicast address safeguarded in local multicast address table；
Unicast corresponding with the link local multicast address is created in unicast routing table and substitutes route table items；
When receiving the message that destination address is link local multicast address, according to the list created in unicast routing table
Broadcast substitute route table items by after the message up sending in processing locality.
Preferably, corresponding unicast replacement route table items are created in unicast routing table to be included：In the unicast routing table
One destination address of middle establishment is the link local multicast address；Next-hop is loopback address；Outgoing interface is local loopback mouth
Singlecast router list item as the unicast substitute route table items.
Preferably, the method further includes：When the network equipment is not provided with local loopback mouth, a local ring is created
Answer back or other local enable ports are configured to loopback mouth.
Preferably, corresponding unicast replacement route table items are created in unicast routing table to be included：In the unicast routing table
It is middle to create the singlecast router list item that a destination address is the link local multicast address；For singlecast router list item increase
On send mark；Wherein, mark is sent to represent that the message for matching the singlecast router list item needs send and in local on described
Processing.
Preferably, the link local multicast address is IPv4 or IPv6 link local multicast address.
The present invention also proposes a kind of network equipment, and the network equipment includes：
Module is emptied, for emptying the link local multicast address safeguarded in local multicast address table；
Creation module, road is substituted for creating unicast corresponding with the link local multicast address in unicast routing table
By list item；
Processing module, used in receive destination address be link local multicast address message when, according in unicast routing table
Create the unicast substitute route table items by after the message up sending in processing locality.
Preferably, the creation module is further used for：It is institute that a destination address is created in the unicast routing table
State link local multicast address；Next-hop is loopback address；Outgoing interface is described in the singlecast router list item conduct of local loopback mouth
Unicast substitutes route table items.
Preferably, the creation module is further used for：When the network equipment is not provided with local loopback mouth, one is created
Other local enable ports are configured to loopback mouth by a local loopback mouth.
Preferably, the creation module is further used for：It is institute that a destination address is created in the unicast routing table
The singlecast router list item of link local multicast address is stated, and to give mark in the singlecast router list item increase；Wherein, on described
Mark is sent to represent that the message for matching the singlecast router list item needs send and in processing locality.
Preferably, the link local multicast address is IPv4 or IPv6 link local multicast address.
By the present invention, the forward efficiency of multicast message can be improved, while the storage for saving local multicast address table is empty
Between.
Brief description of the drawings
Fig. 1 is a kind of flow chart of the processing method for link local multicast message that the embodiment of the present invention proposes；
Fig. 2 is a kind of building-block of logic for network equipment that the embodiment of the present invention proposes.
Embodiment
Below in conjunction with the attached drawing in the embodiment of the present invention, the technical solution in the embodiment of the present invention is carried out clear, complete
Site preparation describes.
Fig. 1 is referred to, the embodiment of the present invention proposes a kind of processing method of link local multicast message, applied to network
In equipment, the method performs following steps：
S101, empty the link local multicast address safeguarded in local multicast address table；
S102, create unicast replacement route table items corresponding with the link local multicast address in unicast routing table；
S103, when receive destination address be link local multicast address message when, according to what is created in unicast routing table
The unicast substitute route table items by after the message up sending in processing locality.
In the present embodiment, the link local group that the network equipment will can be safeguarded in local multicast address table upon actuation
Broadcast address to empty, while create corresponding unicast in local unicast routing table and substitute route table items.
Wherein, unicast corresponding with the link local multicast address is created in unicast routing table and substitutes route table items,
There can be following two embodiments：
In a kind of exemplary embodiment, it is described for a destination address being created in the unicast routing table
Link local multicast address, next-hop are loopback address (Loopback Address), and outgoing interface is the unicast of local loopback mouth
Route table items substitute route table items as the unicast.
Wherein, what deserves to be explained is, the loopback address refers to 127.x.x.x, i.e., a kind of address of 127 beginnings；It is described
The link local multicast address safeguarded in local multicast address table, the link local group added for current this equipment total interface
Broadcast the address of group.
Specifically, with the 224.0.0.1 in link local multicast address (it is below FF02 for IPv6::1) and
224.0.0.2 (it is FF02 for IPv6::2) it is described in detail exemplified by.Wherein IP address is 224.0.0.1 (FF02::1)
Link local multicast group includes all local hosts and router；IP address is 224.0.0.2 (FF02::2) link local group
Broadcasting group includes all multicast routers.
For the network equipment, two above multicast group can be automatically added on each interface.
After the network equipment starts, the IP address 224.0.0.1 (FF02 that will be safeguarded first in local multicast address table::1)
With 224.0.0.2 (FF02::2) empty, while it is respectively the two IP to create destination address in the local unicast routing table
Location, next-hop (can be 127.0.0.1 for IPv4, can be for IPv6 for loopback address::1), outgoing interface is local ring
Answer back (InLoopback0) unicast substitute route table items；
For IPv4, it is as follows that the unicast created substitutes route table items：
| Destination address | Mask-length | Next-hop | Outgoing interface |
| 224.0.0.1 | 32 | 127.0.0.1 | InLoopback0 |
| 224.0.0.2 | 32 | 127.0.0.1 | InLoopback0 |
For IPv6, it is as follows that the unicast created substitutes route table items：
| Destination address | Mask-length | Next-hop | Outgoing interface |
| FF02::1 | 128 | ::1 | InLoopback0 |
| FF02::2 | 128 | ::1 | InLoopback0 |
After above singlecast router list item is created in the unicast routing table, the network equipment either interface at this time
It is 224.0.0.1 (FF02 to receive destination address::Or 224.0.0.2 (FF02 1)::2) it is single searching during local multicast message
Corresponding unicast can be matched when broadcasting routing table and substitutes route table items, since the unicast substitutes next-hop in route table items
For loopback address, outgoing interface is local loopback mouth, therefore destination address is 224.0.0.1 (FF02::Or 224.0.0.2 1)
(FF02::2) local multicast message is after having hit the unicast and having substituted route table items, and the network equipment is not by the local
Multicast message is sent, but by the local multicast message by local loopback choma back to the loopback address (loopback
Address represents local host), it is 224.0.0.1 (FF02 to the destination address by local host::Or 224.0.0.2 1)
(FF02::2) local multicast message up sending is handled to after CPU locally；Therefore, described in being created in unicast routing table
Unicast substitute route table items, it is possible to achieve by local multicast message directly match singlecast router list item can be carried out giving and
Local host is handled, and is forwarded to without matching local multicast address table.
Same reason, for link local multicast address range (for IPv4 refer to 224.0.0.0~
224.0.0.255；Refer to FF02 for IPv6::1~FF02::FF 224.0.0.1 (is FF02 for IPv6 in)::1) and
224.0.0.2 (it is FF02 for IPv6::2) other IP address beyond, still can be implemented according to the method described above.
Specifically, if the total interface of the network equipment except be automatically added to IP address for 224.0.0.1 and
224.0.0.2 outside link local multicast group, it is also necessary to which it (is FF02 for IPv6 to add IP address as 224.0.0.5::5)
Link local multicast group；
Wherein IP address is 224.0.0.5 (FF02::5) link local multicast group enables ospf protocol including all
The network equipment.
Since the network equipment can add IP address 224.0.0.1 (FF02 automatically in local multicast address table::1) and
224.0.0.1(FF02::2), thus the network equipment on startup, you can the IP address that will be safeguarded in local multicast address table
224.0.0.1(FF02::1)、224.0.0.1(FF02::2) empty, and destination address point is created in local unicast routing table
Wei not 224.0.0.1 (FF02::And 224.0.0.1 (FF02 1)::2), next-hop (is for IPv4 for loopback address
127.0.0.1, it is for IPv6::1), outgoing interface substitutes route table items for the unicast of local loopback mouth (InLoopback0)；And
For 224.0.0.5 (FF02::5), then need to remove again after the network equipment enables ospf protocol；
Specifically, after the response interface of the network equipment enables ospf protocol, will be tieed up in local multicast address table
IP address 224.0.0.5 (the FF02 of shield::5) empty, and it is 224.0.0.5 to create destination address in local unicast routing table
(FF02::5), next-hop (can be 127.0.0.1 for IPv4, can be for IPv6 for loopback address::1), outgoing interface
Route table items are substituted for the unicast of local loopback mouth (InLoopback0)；
For IPv4, it is as follows that the unicast finally created substitutes route table items
| Destination address | Mask-length | Next-hop | Outgoing interface |
| 224.0.0.1 | 32 | 127.0.0.1 | InLoopback0 |
| 224.0.0.2 | 32 | 127.0.0.1 | InLoopback0 |
| 224.0.0.5 | 32 | 127.0.0.1 | InLoopback0 |
For IPv6, it is as follows that the unicast finally created substitutes route table items
| Destination address | Mask-length | Next-hop | Outgoing interface |
| FF02::1 | 128 | ::1 | InLoopback0 |
| FF02::2 | 128 | ::1 | InLoopback0 |
| FF02::5 | 128 | ::1 | InLoopback0 |
After above unicast replacement route table items are created in the unicast routing table, the network equipment is any at this time
When interface receives the multicast message that destination address is 224.0.0.1,224.0.0.2 or 224.0.0.5, unicast routing table is being searched
When can match corresponding unicast and substitute route table items, and route table items are substituted directly by the message up sending according to the unicast
Handled to after CPU in the machine.
What deserves to be explained is in specific implementation, the loopback address can also be selected in loopback address section 127.x.x.x
Other IP address, above-described embodiment selection 127.0.0.1 implement exemplary only, is not intended to limit the present invention.
Can be that the network equipment creates a loopback mouth in addition, if current network device does not configure loopback mouth, or by institute
Other the enabled interfaces for stating the network equipment are configured to loopback mouth.
In another exemplary embodiment, a destination address can be created in the unicast routing table is institute
The singlecast router list item for stating link local multicast address substitutes route table items as the unicast；It is at the same time the unicast routing table
Mark is sent in item increase；
Wherein, in the present embodiment, the message that mark represents to match the singlecast router list item is sent on described to be needed to carry out
On send and in processing locality；In specific implementation, the unicast substitutes the next-hop of route table items and outgoing interface can be sky, or
Person fills next-hop IP address 0.0.0.0, and outgoing interface Null0 (pseudo- interface) interface is filled；
Specifically, still with the 224.0.0.1 in link local multicast address (it is below FF02 for IPv6::1) and
224.0.0.2 (it is FF02 for IPv6::2) it is described in detail exemplified by.
After the network equipment starts, the IP address 224.0.0.1 (FF02 that will be safeguarded first in local multicast address table::1)
With 224.0.0.2 (FF02::2) empty, and it is respectively the two IP address to create destination address in local unicast routing table
Singlecast router list item substitutes route table items as the unicast；
Next-hop and outgoing interface wherein in the singlecast router list item can use IP address respectively in specific implementation
0.0.0.0 filled with pseudo- interface Null0；
Meanwhile increase for the singlecast router list item and send mark on one；Mark is sent to represent to match the unicast road on this
Need send and in processing locality by the message of list item；Specific implementation when can will be described on send tag definitions be one
Character string or numeral；For example, in the present embodiment can will be described on send tag definitions be 1；
For IPv4, it is as follows that the unicast created substitutes route table items：
| Destination address | Mask-length | Next-hop | Outgoing interface | On send mark |
| 224.0.0.1 | 32 | 0.0.0.0 | Null0 | 1 |
| 224.0.0.2 | 32 | 0.0.0.0 | Null0 | 1 |
For IPv6, it is as follows that the unicast created substitutes route table items：
| Destination address | Mask-length | Next-hop | Outgoing interface | On send mark |
| FF02::1 | 128 | :: | Null0 | 1 |
| FF02::2 | 128 | :: | Null0 | 1 |
After above singlecast router list item is created in the unicast routing table, the network equipment either interface at this time
It is 224.0.0.1 (FF02 to receive destination address::Or 224.0.0.2 (FF02 1)::2) it is single searching during local multicast message
Corresponding unicast can be matched when broadcasting routing table and substitutes route table items, has been increased since the unicast substitutes route table items
Add and above sent mark, therefore destination address is 224.0.0.1 (FF02::Or 224.0.0.2 (FF02 1)::2) local multicast report
After having hit the unicast and having substituted route table items, the network equipment does not send the local multicast message text, but
Directly the local multicast message up sending is handled to after CPU locally according to mark is sent on described.
Same reason, for link local multicast address range (for IPv4 refer to 224.0.0.0~
224.0.0.255；Refer to FF02 for IPv6::1~FF02::FF 224.0.0.1 (is FF02 for IPv6 in)::1) and
224.0.0.2 (it is FF02 for IPv6::2) other IP address beyond, still can be implemented according to the method described above.
Specifically, if the total interface of the network equipment except be automatically added to IP address for 224.0.0.1 and
224.0.0.2 outside link local multicast group, it is also necessary to which it (is FF02 for IPv6 to add IP address as 224.0.0.5::5)
Link local multicast group；
Since the network equipment can add IP address 224.0.0.1 (FF02 automatically in local multicast address table::1) and
224.0.0.1(FF02::2), thus the network equipment on startup, you can the IP address that will be safeguarded in local multicast address table
224.0.0.1(FF02::1)、224.0.0.1(FF02::2) empty, and create the unicast in local unicast routing table and replace
For route table items；And for 224.0.0.5 (FF02::5), then need to remove again after the network equipment enables ospf protocol；
Specifically, after the response interface of the network equipment enables ospf protocol, will be tieed up in local multicast address table
IP address 224.0.0.5 (the FF02 of shield::5) empty, while create the unicast in local unicast routing table and substitute routing table
；
For IPv4, it is as follows that the unicast finally created substitutes route table items
| Destination address | Mask-length | Next-hop | Outgoing interface | On send mark |
| 224.0.0.1 | 32 | :: | Null0 | 1 |
| 224.0.0.2 | 32 | :: | Null0 | 1 |
| 224.0.0.5 | 32 | :: | Null0 | 1 |
For IPv6, it is as follows that the unicast finally created substitutes route table items
| Destination address | Mask-length | Next-hop | Outgoing interface | On send mark |
| FF02::1 | 128 | :: | Null0 | 1 |
| FF02::2 | 128 | :: | Null0 | 1 |
| FF02::5 | 128 | :: | Null0 | 1 |
After above unicast replacement route table items are created in the unicast routing table, the network equipment is any at this time
It is 224.0.0.1 (FF02 that interface, which receives destination address,::1)、224.0.0.2(FF02::Or 224.0.0.5 (FF02 2)::5)
During multicast message, corresponding unicast can be matched when searching unicast routing table and substitutes route table items, and according to the unicast
Mark is sent directly to be handled the message up sending in the machine to after CPU in replacement route table items.
As can be seen from the above description, the present invention is clear by the link local multicast address that will be safeguarded in local multicast address table
Sky, while create corresponding unicast in unicast routing table and substitute route table items so that it is sent to the message of link local multicast group
Corresponding singlecast router list item can be matched by once tabling look-up, it is no longer necessary to search local multicast address table；And for
The common multicast message received, due to no longer maintenance link local multicast address in current multicast address table, it is convenient to omit one
Secondary lookup, so as to improve the forward efficiency of multicast message, while saves the memory space of multicast address.
Corresponding with a kind of foregoing processing method embodiment of link local multicast message, the disclosure additionally provides a kind of net
The embodiment of network equipment.
Fig. 2 is referred to, one embodiment of the application also proposes a kind of network equipment 20, the net as carrying apparatus of the present invention 20
In the hardware structure that network equipment is related to, CPU, memory, nonvolatile memory, I/O interface and other hardware are generally included.With
Exemplified by software is realized, apparatus of the present invention 20 run it is generally understood that the computer program of loading in memory by CPU
The logic device that the software and hardware formed afterwards is combined；The device 20 includes：
Module 21 is emptied, for emptying the link local multicast address safeguarded in local multicast address table；
Creation module 22, substitutes for creating unicast corresponding with the link local multicast address in unicast routing table
Route table items；
Processing module 23, used in receive destination address be link local multicast address message when, according to unicast routing table
In the unicast that is pre-created substitute route table items by after the message up sending in processing locality.
In the present embodiment, the creation module 22 is further used for：
It is the link local multicast address that a destination address is created in the unicast routing table, and next-hop is loopback
Address, outgoing interface substitute route table items for the singlecast router list item of local loopback mouth as the unicast.
In the present embodiment, the creation module 22 is further used for：
When the network equipment is not provided with local loopback mouth, creates a local loopback mouth or incite somebody to action other local Enable Pins
Mouth is configured to loopback mouth.
In the present embodiment, the creation module 22
It is further used for：
The unicast routing table that a destination address is the link local multicast address is created in the unicast routing table
, and to give mark in the singlecast router list item increase；
Wherein, mark is sent to represent that the message for matching the singlecast router list item needs send and be originally located on described
Reason.
In the present embodiment, the link local multicast address is IPv4 or IPv6 link local multicast address.
By the description of above example, the module that skilled person is appreciated that in embodiment in device can merge
For a module, multiple submodule can also be further split into.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all essences in the present invention
God and any modification, equivalent substitution, improvement and etc. within principle, done, should be included within the scope of protection of the invention.
Claims (10)
- A kind of 1. processing method of link local multicast message, applied on the network equipment, it is characterised in that the method bag Include：Empty the link local multicast address safeguarded in local multicast address table；Wherein, the link local multicast address is IP Address；Unicast corresponding with the link local multicast address is created in unicast routing table and substitutes route table items；When receiving the message that destination address is link local multicast address, replaced according to the unicast created in unicast routing table For route table items by the message up sending to after CPU in processing locality.
- 2. the method as described in claim 1, it is characterised in that corresponding unicast is created in unicast routing table and substitutes routing table Item includes：It is the link local multicast address that a destination address is created in the unicast routing table；Next-hop is loopback address；Outgoing interface substitutes route table items for the singlecast router list item of local loopback mouth as the unicast.
- 3. method as claimed in claim 2, it is characterised in that the method further includes：When the network equipment is not provided with local loopback mouth, creates a local loopback mouth or match somebody with somebody other local enable ports It is set to loopback mouth.
- 4. the method as described in claim 1, it is characterised in that corresponding unicast is created in unicast routing table and substitutes routing table Item includes：The singlecast router list item that a destination address is the link local multicast address is created in the unicast routing table；To send mark in the singlecast router list item increase；Wherein, mark is sent to represent that the message for matching the singlecast router list item needs send and in processing locality on described.
- 5. the method as described in claim 1, it is characterised in that the link local multicast address is IPv4 or IPv6 link sheets Ground multicast address.
- 6. a kind of network equipment, it is characterised in that the network equipment includes：Module is emptied, for emptying the link local multicast address safeguarded in local multicast address table；Wherein, the link local Multicast address is IP address；Creation module, routing table is substituted for creating unicast corresponding with the link local multicast address in unicast routing table ；Processing module, for when receiving the message that destination address is link local multicast address, according to pre- in unicast routing table The unicast that first creates substitute route table items by the message up sending to after CPU in processing locality.
- 7. the network equipment as claimed in claim 6, it is characterised in that the creation module is further used for：It is the link local multicast address that a destination address is created in the unicast routing table；Next-hop is loopback address；Outgoing interface substitutes route table items for the singlecast router list item of local loopback mouth as the unicast.
- 8. the network equipment as claimed in claim 7, it is characterised in that the creation module is further used for：When the network equipment is not provided with local loopback mouth, creates a local loopback mouth or match somebody with somebody other local enable ports It is set to loopback mouth.
- 9. the network equipment as claimed in claim 6, it is characterised in that the creation module is further used for：The singlecast router list item that a destination address is the link local multicast address is created in the unicast routing table, and To send mark in the singlecast router list item increase；Wherein, mark is sent to represent that the message for matching the singlecast router list item needs send and in processing locality on described.
- 10. the network equipment as claimed in claim 6, it is characterised in that the link local multicast address is IPv4 or IPv6 Link local multicast address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410220227.7A CN103973576B (en) | 2014-05-22 | 2014-05-22 | A kind of processing method and the network equipment of link local multicast message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410220227.7A CN103973576B (en) | 2014-05-22 | 2014-05-22 | A kind of processing method and the network equipment of link local multicast message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103973576A CN103973576A (en) | 2014-08-06 |
| CN103973576B true CN103973576B (en) | 2018-05-08 |
Family
ID=51242636
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410220227.7A Active CN103973576B (en) | 2014-05-22 | 2014-05-22 | A kind of processing method and the network equipment of link local multicast message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103973576B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106453088B (en) * | 2016-09-28 | 2019-06-25 | 平安科技（深圳）有限公司 | A kind of static routing configuration method and terminal |
| CN113472665B (en) * | 2021-06-17 | 2022-11-18 | 新华三信息安全技术有限公司 | Method and device for realizing butt joint of different networks under EVPN |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252529A (en) * | 2008-03-31 | 2008-08-27 | 杭州华三通信技术有限公司 | Method and apparatus for forwarding multicast message |
| CN103391251A (en) * | 2013-07-16 | 2013-11-13 | 杭州华三通信技术有限公司 | Method and device for reducing redundant flow in PBB (provider backbone bridge) network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7792057B2 (en) * | 2007-12-21 | 2010-09-07 | At&T Labs, Inc. | Method and system for computing multicast traffic matrices |
-
2014
- 2014-05-22 CN CN201410220227.7A patent/CN103973576B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252529A (en) * | 2008-03-31 | 2008-08-27 | 杭州华三通信技术有限公司 | Method and apparatus for forwarding multicast message |
| CN103391251A (en) * | 2013-07-16 | 2013-11-13 | 杭州华三通信技术有限公司 | Method and device for reducing redundant flow in PBB (provider backbone bridge) network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103973576A (en) | 2014-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10536324B2 (en) | Per-prefix LFA FRR with bit indexed explicit replication | |
| Estrin et al. | Protocol independent multicast-sparse mode (PIM-SM): Protocol specification | |
| US9036463B2 (en) | Scalable BGP protection from edge node failure using dynamically assigned labels in data packets | |
| US9237025B2 (en) | Source routing in multicast transmissions | |
| US9736058B2 (en) | Multi-region source routed multicast using sub-tree identifiers | |
| EP3694163B1 (en) | Method and device for implementing multicast service | |
| US10225295B2 (en) | Multicast packet forwarding method and device | |
| US9596180B2 (en) | Installation of cached downward paths based on upward data traffic in a non-storing low-power and lossy network | |
| EP3968580B1 (en) | Method for generating multicast forwarding table entry, and access gateway | |
| EP3240245B1 (en) | Method and device for multicasting and forwarding multiple protocol label switching intermediate node, and node | |
| CN104539545B (en) | Method for forwarding multicast message and equipment in TRILL network | |
| KR20220098152A (en) | Communication method and device | |
| CN104426781A (en) | Method for realizing gathering of multicast routers, multicast method and route equipment | |
| CN103973576B (en) | A kind of processing method and the network equipment of link local multicast message | |
| WO2015113456A1 (en) | Method for generating media access control table, and network device | |
| CN103460675B (en) | Cluster and retransmission method | |
| CN108768845B (en) | Multi-homing host routing synchronization method and device | |
| WO2016124055A1 (en) | Method and network node for forwarding mpls message in ring network | |
| CN105429878A (en) | Method for creating PIM-SM SPT | |
| CN108471374A (en) | The retransmission method and device of data message | |
| CN104394081B (en) | A kind of data processing method and device | |
| CN105376161A (en) | Multicast distribution tree switching method and device | |
| CN104412548A (en) | Method and device for keeping user device IP address fixed | |
| CN109039902B (en) | Method and device for forwarding multicast message | |
| KR20230088494A (en) | Method and Apparatus for Determining Next Hop |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |