CN107948064B - SDN-based cross-domain multicast method and device - Google Patents
SDN-based cross-domain multicast method and device Download PDFInfo
- Publication number
- CN107948064B CN107948064B CN201711096189.9A CN201711096189A CN107948064B CN 107948064 B CN107948064 B CN 107948064B CN 201711096189 A CN201711096189 A CN 201711096189A CN 107948064 B CN107948064 B CN 107948064B
- Authority
- CN
- China
- Prior art keywords
- multicast
- domain
- sdn switch
- sdn
- unicast
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/04—Interdomain routing, e.g. hierarchical routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/806—Broadcast or multicast traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/20—Support for services
- H04L49/201—Multicast operation; Broadcast operation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a cross-domain multicast method and a device based on SDN.A SND controller receives multicast source registration information sent by a first SDN switch and multicast joining information sent by a second SDN switch, establishes a multicast group information table item and a multicast request information table item, and generates a multicast-to-unicast table item and a unicast-to-multicast table item according to the multicast group information table item and the multicast request information table item; sending the multicast-to-unicast table entry to a first SDN switch, informing the first SDN switch of draining from a multicast source and converting a multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item. The invention realizes the multicast service crossing the non-multicast domain, avoids the forwarding of a large amount of unicast flow in the network and saves the network bandwidth.
Description
Technical Field
The invention belongs to the technical field of network communication, and particularly relates to a cross-domain multicast method and device based on an SDN.
Background
With the development of the monitoring industry, a multicast distribution function is required in many monitoring networks. However, a large multicast domain may be isolated by a non-multicast enabled network, referred to as a non-multicast domain, such as a wide area network in the internet community, which is generally a non-multicast domain. In the prior art, if streaming media of a multicast source needs to be sent to a multicast domain across a non-multicast domain, a streaming media server generally needs to convert the streaming media into unicast in the multicast domain where the multicast source is located, so as to perform communication across the non-multicast domain. However, after passing through the non-multicast domain, the unicast data is not converted into multicast again, which results in a large amount of unicast traffic being forwarded in the network and link bandwidth waste.
Disclosure of Invention
The invention provides a cross-domain multicast method and a cross-domain multicast device based on an SDN (software defined network), which are used for solving the problem of link bandwidth waste caused by unicast forwarding when a non-multicast domain is crossed in the prior art.
In order to achieve the purpose, the technical scheme of the invention is as follows:
a cross-domain multicast method based on SDN is used for realizing multicast service from a multicast source located in a first multicast domain to a multicast member located in a second multicast domain, the first multicast domain is connected with the second multicast domain through a non-multicast domain, a first SDN switch is arranged between the first multicast domain and the non-multicast domain, a second SDN switch is arranged between the second multicast domain and the non-multicast domain, the first SDN switch and the second SDN switch are connected to an SDN controller, and the cross-domain multicast method based on SDN is applied to the SDN controller and comprises the following steps:
the method comprises the steps that an SDN controller receives multicast source registration information sent by a first SDN switch, and a multicast group information table item comprising a multicast source, a multicast group and first SDN switch information is established; receiving multicast adding information sent by a second SDN switch, and establishing a multicast request information table item comprising multicast groups and second SDN switch information;
generating a multicast-to-unicast list item and a unicast-to-multicast list item according to the multicast group information list item and the multicast request information list item;
sending the multicast-to-unicast table entry to a first SDN switch, informing the first SDN switch of draining from a multicast source and converting a multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item.
The multicast-to-unicast table entry comprises a source IP and a destination IP before conversion, and the source IP and the destination IP after conversion, wherein the source IP before conversion is an IP address of multicast source equipment, the destination IP before conversion is an IP address of a multicast group, the source IP after conversion is an IP address of a first SDN switch, and the destination IP after conversion is an IP address of a second SDN switch.
Further, the multicast-to-unicast table entry further includes a corresponding port number.
The unicast-multicast table entry comprises a source IP and a destination IP before conversion, and the source IP and the destination IP after conversion, wherein the source IP before conversion is an IP address of a first SDN switch, the destination IP before conversion is an IP address of a second SDN switch, the source IP after conversion is an IP address of the first SDN switch, and the destination IP after conversion is a multicast group IP address.
Further, the unicast multicast table entry further includes a corresponding port number.
The invention further provides a cross-domain multicast device based on SDN, which is used for implementing a multicast service from a multicast source located in a first multicast domain to a multicast member located in a second multicast domain, where the first multicast domain and the second multicast domain are connected through a non-multicast domain, a first SDN switch is arranged between the first multicast domain and the non-multicast domain, a second SDN switch is arranged between the second multicast domain and the non-multicast domain, the first SDN switch and the second SDN switch are connected to an SDN controller, and the cross-domain multicast device based on SDN is applied to the SDN controller, and includes:
the multicast information receiving module is used for receiving multicast source registration information sent by the first SDN switch and establishing a multicast group information table item comprising multicast source, multicast group and first SDN switch information; receiving multicast adding information sent by a second SDN switch, and establishing a multicast request information table item comprising multicast groups and second SDN switch information;
a conversion table item generation module, configured to generate a multicast-to-unicast table item and a unicast-to-multicast table item according to the multicast group information table item and the multicast request information table item;
the sending module is used for sending the multicast-to-unicast table entry to the first SDN switch, informing the first SDN switch of draining from a multicast source and converting the multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item.
According to the cross-domain multicast method and device based on the SDN, when a multicast stream needs to cross a non-multicast domain, an SDN switch of the domain where a multicast source is located leads the media stream to the self; then converting the multicast into the unicast and sending the unicast to the SDN switch of the domain where the receiver is located; and after the unicast message reaches the multicast domain, the SDN switch converts the unicast data into multicast data again for distribution. The invention realizes the multicast service crossing the non-multicast domain, avoids the forwarding of a large amount of unicast flow in the network and saves the network bandwidth.
Drawings
Fig. 1 is a schematic diagram of a cross-domain multicast network structure according to an embodiment of the present invention;
fig. 2 is a flowchart of a cross-domain multicast method based on SDN according to the present invention.
Detailed Description
The technical solutions of the present invention are further described in detail below with reference to the drawings and examples, which should not be construed as limiting the present invention.
At present, Software Defined Networking (SDN) is widely applied, and SDN is a novel network architecture and is designed in a manner that a control plane and a data forwarding plane of a network are separated, so that flexible network resource allocation on demand is realized. In the SDN network, an SDN controller is responsible for collecting network topology information, calculating a forwarding path of a service message generated by a host and generating a forwarding table item; and the SDN switch forwards the service message according to the forwarding table item issued by the SDN controller.
In this embodiment, SDN switches are respectively deployed at the edge of a multicast domain, and when a multicast stream needs to cross a non-multicast domain, the SDN switch in the domain where the multicast source is located directs a media stream to itself; then converting the multicast into the unicast and sending the unicast to the SDN switch of the domain where the receiver is located; and after the unicast message reaches the multicast domain, the SDN switch converts the unicast data into multicast data again for distribution.
In this embodiment, taking the network architecture shown in fig. 1 as an example, in fig. 1, a front-end device of a video monitoring system, such as a webcam IPC1, is a multicast source and is located in a multicast domain 1; while host PCs 1, PC2, PC3 are located as client devices in the multicast domain 2 and can request media streams from IPC 1. In this case, it is undoubtedly the most cost-effective way to provide the media stream in a multicast manner. However, a non-multicast domain wide area network exists between the multicast domain 1 and the multicast domain 2, and multicast spanning across the non-multicast domain is required to be realized, so that in this embodiment, a first SDN switch SW1 is disposed between the multicast domain 1 and the non-multicast domain, a second SDN switch SW2 is disposed between the non-multicast domain and the multicast domain 2, SW1 and SW2 are connected to an SDN controller, and exchange information through SDN control signaling (OpenFlow protocol), and details about a communication mechanism between the SDN controller and the SDN switch are not described here.
As shown in fig. 2, an embodiment of a cross-domain multicast method based on an SDN is applied to an SDN controller, and in the process of implementing the cross-domain multicast, the SDN controller of this embodiment executes the following steps:
step S1, receiving multicast source registration information sent by a first SDN switch, and establishing a multicast group information table item including multicast source, multicast group and first SDN switch information; and receiving multicast group joining information sent by the second SDN switch, and establishing a multicast request information table item comprising the multicast group and the second SDN switch information.
In this embodiment, a first SDN switch is set as a rendezvous point RP of a multicast domain 1, and a second SDN switch is set as a rendezvous point RP of a multicast domain 2, so that the first SDN switch receives a multicast registration packet in the multicast domain 1 to generate a multicast forwarding entry (S, G) entry, and the second SDN switch receives a multicast group join packet sent by each host in the multicast domain 2 to generate a multicast request entry (G). The first SDN switch sends the (S, G) table entry to an SDN controller, and the SDN controller generates a multicast group information table entry; and the second SDN switch sends the ([ G ]) table item to the SDN controller, and the SDN controller generates a multicast request information table item.
For example:
IPC1(1.1.1.1) of multicast domain 1 sends a multicast packet to multicast group (225.0.0.1), and the switch in multicast domain 1 registers the packet with the first SDN switch SW1 (as RP of multicast domain 1) for multicast source registration, so that the first SDN switch SW1 generates (S, G) table entry of (1.1.1.1, 225.0.0.1). The first SDN switch SW1 will report this information to the SDN controller, and the SDN controller will generate a multicast group information entry, as shown in table 1:
| multicast source | Multicast group | SDN switch |
| 1.1.1.1 | 225.0.0.1 | SDN1 |
TABLE 1
The PC1 in the multicast domain 2 sends an IGMP report, and when desiring to obtain data of the multicast group 225.0.0.1, the switch in the multicast domain 2 sends the request to the second SDN switch SW2 (as the RP of the multicast domain 2), so that the second SDN switch SW2 generates an (G) entry of (225.0.0.1). The second SDN switch SW2 will report this information to the SDN controller, and the SDN controller will generate a multicast request information entry, as shown in table 2:
| multicast source | Multicast group | SDN switch |
| * | 225.0.0.1 | SDN2 |
TABLE 2
Step S2, according to the multicast group information table and the multicast request information table, generating a multicast-to-unicast table and a unicast-to-multicast table.
For the same multicast group, the SDN controller in this embodiment compares the SDN switch information corresponding to the multicast source and the multicast joiner, and if the multicast source and the multicast joiner are not the same device, it indicates that the multicast source and the multicast receiver are in two different multicast domains and need to perform cross-domain multicast.
For example, according to table 1 and table 2, it is found that for the multicast group 225.0.0.1, if the SDN switch (SW1) in the multicast group information and the SDN switch (SW2) in the multicast request information are not the same device, the SDN controller needs to perform the following operations until the source and the receiver of the multicast are in two different multicast domains:
and generating a multicast-to-unicast table entry (shown in table 3) and issuing the table entry to the first SDN switch, and generating a unicast-to-multicast table entry (shown in table 4) and issuing the table entry to the second SDN switch.
TABLE 3
TABLE 4
The multicast-to-unicast table entry comprises a source IP and a destination IP before conversion, and the source IP and the destination IP after conversion, wherein the source IP before conversion is an IP address of multicast source equipment, the destination IP before conversion is an IP address of a multicast group, the source IP after conversion is an IP address of a first SDN switch, and the destination IP after conversion is an IP address of a second SDN switch.
The unicast-to-multicast table entry comprises a source IP and a destination IP before conversion, and the source IP and the destination IP after conversion, wherein the source IP before conversion is an IP address of a first SDN switch, the destination IP before conversion is an IP address of a second SDN switch, the source IP after conversion is an IP address of the first SDN switch, and the destination IP after conversion is a multicast group IP address.
Step S3, sending the multicast-to-unicast table entry to a first SDN switch, informing the first SDN switch to drain from a multicast source and converting the multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item.
In this embodiment, the SDN controller notifies a first SDN switch where the multicast source is located to send a multicast join packet to the multicast source, and directs the multicast media stream to the first SDN switch.
And issuing the multicast-to-unicast table entry to the first SDN switch SW1, and informing the first SDN switch SW1 of converting the 225.0.0.1 multicast message into a unicast message, wherein the source IP address is the IP address of the first SDN switch SW1, the destination IP address is the IP address of the second SDN switch SW2, and the transmission layer and the data part are unchanged.
And issuing the unicast-multicast table entry to the second SDN switch SW2, and informing the second SDN switch SW2 to convert the unicast message sent by the first SDN switch SW1 into a multicast message, where the source IP is an IP address of the second SDN switch SW2, and the destination address is a multicast group address 225.0.0.1.
Through the above steps, the media stream sent by the multicast source IPC1 is the multicast message first sent, and after reaching the first SDN switch SW1, the multicast message is converted into the unicast message, and is sent to the second SDN switch SW2 through unicast. On the second SDN switch SW2, the unicast message is converted into a multicast message, and sent to the multicast receiver (PC1, PC2, PC3), thereby implementing a multicast service across non-multicast domains, avoiding forwarding of a large amount of unicast traffic in the network, and saving network bandwidth.
It is easy to understand that when there is no multicast joiner in the multicast group, the second SDN switch no longer needs to perform unicast conversion into multicast, and the SDN controller also deletes the corresponding entry.
Specifically, when there is no more joiner of the multicast stream in the multicast domain 2, that is, no one in the multicast domain 2 needs the data of the multicast group 225.0.0.1, the second SDN switch may delete the corresponding unicast-to-multicast table entry and notify the SDN controller at the same time.
The SDN controller may query the multicast request information entry, and delete the entry information corresponding to the second SDN switch and the multicast group 225.0.0.1; the multicast-to-unicast table entry is also inquired, the table entry information corresponding to the second SDN switch and 225.0.0.1 is deleted, and the first SDN switch is informed of deleting the multicast-to-unicast table entry corresponding to the second SDN switch and 225.0.0.1; and inquiring unicast forwarding multicast table entries, and deleting table entry information corresponding to the second SDN switches and 225.0.0.1.
It should be noted that, if there are multiple unicast streams between the first SDN switch and the second SDN switch, the source IP and the destination IP of the first SDN switch are the same, a port number of UDP may be added to the corresponding entry for differentiation, where the port number is mainly added to prevent that after two multicast streams are converted into unicast, an IP address and a port number become the same, and a receiver cannot distinguish between the two multicast streams. I.e. adding port numbers to the corresponding entries of tables 3 and 4 for distinction.
For example, the table entry is changed from multicast to unicast, and after adding port number, the table is as follows:
TABLE 5
For example, the unicast to multicast table entry is shown in the following table after adding the port number:
TABLE 6
After adding port numbers in the multicast-to-unicast table entry and the unicast-to-multicast table entry, the SDN switch distinguishes according to the port number of the UDP. For the entries with increased port numbers, only the destination port number needs to be changed to distinguish different streams, for example, the destination port number of the first stream is changed to 10001, and the port number of the second stream is changed to 10002, so that the receiving side can distinguish.
Correspondingly to the method, the application also provides an embodiment of a cross-domain multicast device based on the SDN, which is used for implementing multicast service from a multicast source located in a first multicast domain to a multicast member located in a second multicast domain, the first multicast domain is connected with the second multicast domain through a non-multicast domain, a first SDN switch is arranged between the first multicast domain and the non-multicast domain, a second SDN switch is arranged between the second multicast domain and the non-multicast domain, and the first SDN switch and the second SDN switch are connected to an SDN controller. The cross-domain multicast device based on the SDN in the embodiment is applied to an SDN controller, and includes:
the multicast information receiving module is used for receiving multicast source registration information sent by the first SDN switch and establishing a multicast group information table item comprising multicast source, multicast group and first SDN switch information; receiving multicast adding information sent by a second SDN switch, and establishing a multicast request information table item comprising multicast groups and second SDN switch information;
a conversion table item generation module, configured to generate a multicast-to-unicast table item and a unicast-to-multicast table item according to the multicast group information table item and the multicast request information table item;
the sending module is used for sending the multicast-to-unicast table entry to the first SDN switch, informing the first SDN switch of draining from a multicast source and converting the multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item.
The working process of the cross-domain multicast device based on the SDN in this embodiment has been described in detail in the foregoing description of the method, and is not described here again.
The above embodiments are only for illustrating the technical solution of the present invention and not for limiting the same, and those skilled in the art can make various corresponding changes and modifications according to the present invention without departing from the spirit and the essence of the present invention, but these corresponding changes and modifications should fall within the protection scope of the appended claims.
Claims (10)
1. A cross-domain multicast method based on SDN is used for realizing multicast service from a multicast source located in a first multicast domain to a multicast member located in a second multicast domain, the first multicast domain and the second multicast domain are connected through a non-multicast domain, a first SDN switch is arranged between the first multicast domain and the non-multicast domain, a second SDN switch is arranged between the second multicast domain and the non-multicast domain, the first SDN switch and the second SDN switch are connected to an SDN controller, and the cross-domain multicast method based on SDN is applied to the SDN controller and comprises the following steps:
the method comprises the steps that an SDN controller receives multicast source registration information sent by a first SDN switch, and a multicast group information table item comprising a multicast source, a multicast group and first SDN switch information is established; receiving multicast adding information sent by a second SDN switch, and establishing a multicast request information table item comprising multicast groups and second SDN switch information;
generating a multicast-to-unicast list item and a unicast-to-multicast list item according to the multicast group information list item and the multicast request information list item;
sending the multicast-to-unicast table entry to a first SDN switch, informing the first SDN switch of draining from a multicast source and converting a multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item.
2. The SDN-based cross-domain multicast method of claim 1, wherein the multicast-to-unicast table entry comprises a source IP and a destination IP before conversion, and a source IP and a destination IP after conversion, the source IP before conversion is an IP address of a multicast source device, the destination IP before conversion is a multicast group IP address, the source IP after conversion is an IP address of a first SDN switch, and the destination IP after conversion is an IP address of a second SDN switch.
3. The SDN-based cross-domain multicast method of claim 2, wherein the multicast-to-unicast table entry further comprises a corresponding port number.
4. The SDN-based cross-domain multicast method of claim 1, wherein the unicast multicast table entry comprises a source IP and a destination IP before conversion, and a source IP and a destination IP after conversion, the source IP before conversion is an IP address of a first SDN switch, the destination IP before conversion is an IP address of a second SDN switch, the source IP after conversion is an IP address of a second SDN switch, and the destination IP after conversion is a multicast group IP address.
5. The SDN-based cross-domain multicast method of claim 4, wherein the unicast transmulticast entry further comprises a corresponding port number.
6. A cross-domain multicast device based on SDN is used for realizing multicast service from a multicast source located in a first multicast domain to a multicast member located in a second multicast domain, the first multicast domain and the second multicast domain are connected through a non-multicast domain, a first SDN switch is arranged between the first multicast domain and the non-multicast domain, a second SDN switch is arranged between the second multicast domain and the non-multicast domain, the first SDN switch and the second SDN switch are connected to an SDN controller, and the cross-domain multicast device based on SDN is applied to the SDN controller and comprises:
the multicast information receiving module is used for receiving multicast source registration information sent by the first SDN switch and establishing a multicast group information table item comprising multicast source, multicast group and first SDN switch information; receiving multicast adding information sent by a second SDN switch, and establishing a multicast request information table item comprising multicast groups and second SDN switch information;
a conversion table item generation module, configured to generate a multicast-to-unicast table item and a unicast-to-multicast table item according to the multicast group information table item and the multicast request information table item;
the sending module is used for sending the multicast-to-unicast table entry to the first SDN switch, informing the first SDN switch of draining from a multicast source and converting the multicast message into a unicast message according to the multicast-to-unicast table entry; and sending the unicast-to-multicast list item to a second SDN switch, and informing the second SDN switch to convert the unicast message sent by the first SDN switch into a multicast message according to the unicast-to-multicast list item.
7. The SDN-based cross-domain multicast apparatus of claim 6, wherein the multicast-to-unicast table entry comprises a source IP and a destination IP before conversion, and a source IP and a destination IP after conversion, the source IP before conversion is an IP address of a multicast source device, the destination IP before conversion is a multicast group IP address, the source IP after conversion is an IP address of a first SDN switch, and the destination IP after conversion is an IP address of a second SDN switch.
8. The SDN-based cross-domain multicast apparatus of claim 7, wherein the multicast-to-unicast table entry further comprises a corresponding port number.
9. The SDN-based cross-domain multicast apparatus of claim 6, wherein the unicast multicast table entry comprises a source IP and a destination IP before conversion, and a source IP and a destination IP after conversion, the source IP before conversion is an IP address of a first SDN switch, the destination IP before conversion is an IP address of a second SDN switch, the source IP after conversion is an IP address of a second SDN switch, and the destination IP after conversion is a multicast group IP address.
10. The SDN-based cross-domain multicast apparatus of claim 9, wherein the unicast relay multicast entry further comprises a corresponding port number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711096189.9A CN107948064B (en) | 2017-11-09 | 2017-11-09 | SDN-based cross-domain multicast method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711096189.9A CN107948064B (en) | 2017-11-09 | 2017-11-09 | SDN-based cross-domain multicast method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107948064A CN107948064A (en) | 2018-04-20 |
| CN107948064B true CN107948064B (en) | 2021-06-01 |
Family
ID=61934553
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711096189.9A Active CN107948064B (en) | 2017-11-09 | 2017-11-09 | SDN-based cross-domain multicast method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107948064B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108111324B (en) * | 2017-12-19 | 2022-06-03 | 刘昱 | Multicast control method, device and storage medium based on SDN network |
| CN109379292A (en) * | 2018-10-09 | 2019-02-22 | 郑州云海信息技术有限公司 | A kind of method of multicasting, virtual switch, SDN controller and storage medium |
| CN111327584A (en) * | 2019-11-12 | 2020-06-23 | 杭州海康威视系统技术有限公司 | Video monitoring method, device, system, equipment and storage medium |
| CN113055812B (en) * | 2019-12-27 | 2022-10-21 | 中国移动通信有限公司研究院 | Data transmission method, base station and core network element |
| CN114285679A (en) * | 2021-12-09 | 2022-04-05 | 武汉船舶通信研究所（中国船舶重工集团公司第七二二研究所） | Method and system for realizing heterogeneous network multicast based on centralized control |
| CN114448740B (en) * | 2022-01-14 | 2023-11-07 | 绿盟科技集团股份有限公司 | Multicast method, device, medium, product and equipment |
| CN115941594A (en) * | 2022-09-07 | 2023-04-07 | 成都西加云杉科技有限公司 | Multicast message suppression method, device, equipment and storage medium based on SDN |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468371A (en) * | 2014-11-28 | 2015-03-25 | 杭州华三通信技术有限公司 | Multicast service message processing method and device |
| CN104811393A (en) * | 2014-01-27 | 2015-07-29 | 中兴通讯股份有限公司 | Multicasting message duplicating handling method and device and open flow controller (OFC) |
| CN106210648A (en) * | 2016-08-05 | 2016-12-07 | 浙江宇视科技有限公司 | Cross-domain method of multicasting and device in a kind of video monitoring system |
| CN106851435A (en) * | 2016-12-23 | 2017-06-13 | 浙江宇视科技有限公司 | The sending method and rear end equipment of a kind of multicast data flow |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10298416B2 (en) * | 2013-09-05 | 2019-05-21 | Pismo Labs Technology Limited | Method and system for converting a broadcast packet to a unicast packet at an access point |
| CN103888369B (en) * | 2014-04-10 | 2019-02-05 | 广州市高科通信技术股份有限公司 | Ethernet communication method, system and SDN switch |
| CN105871565B (en) * | 2015-01-20 | 2019-11-29 | 华为技术有限公司 | Method and device for multicast forwarding |
| TWI556599B (en) * | 2015-06-30 | 2016-11-01 | 財團法人工業技術研究院 | Network controlling method and network controller |
-
2017
- 2017-11-09 CN CN201711096189.9A patent/CN107948064B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104811393A (en) * | 2014-01-27 | 2015-07-29 | 中兴通讯股份有限公司 | Multicasting message duplicating handling method and device and open flow controller (OFC) |
| CN104468371A (en) * | 2014-11-28 | 2015-03-25 | 杭州华三通信技术有限公司 | Multicast service message processing method and device |
| CN106210648A (en) * | 2016-08-05 | 2016-12-07 | 浙江宇视科技有限公司 | Cross-domain method of multicasting and device in a kind of video monitoring system |
| CN106851435A (en) * | 2016-12-23 | 2017-06-13 | 浙江宇视科技有限公司 | The sending method and rear end equipment of a kind of multicast data flow |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107948064A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107948064B (en) | SDN-based cross-domain multicast method and device | |
| US6654371B1 (en) | Method and apparatus for forwarding multicast data by relaying IGMP group membership | |
| US11917262B2 (en) | Dynamic designated forwarder election per multicast stream for EVPN all-active homing | |
| EP2587755B1 (en) | Method, apparatus and system for implementing multicast | |
| CN113364610B (en) | Network equipment management method, device and system | |
| CN100433730C (en) | Method and system of multicast and video-on-demand | |
| CN109150580B (en) | Protocol independent multicast join entropy | |
| CN104468384A (en) | System and method for achieving multi-service priorities | |
| CN102215172B (en) | A kind of method and system for realizing cross-virtual private local area network multicast | |
| WO2006081750A1 (en) | A process method for filtering multicast source | |
| WO2007059679A1 (en) | A method for processing the abnormal multicast service and a network equipment thereof | |
| CN101262412B (en) | A method and its access device for multicast recovery with minimal delay | |
| CN104579894A (en) | IGMP Snooping realizing method and device of distributed virtual switch system | |
| EP3396897B1 (en) | Multicast load balancing in multihoming evpn networks | |
| EP2892196B1 (en) | Method, network node and system for implementing point-to-multipoint multicast | |
| WO2017201750A1 (en) | Method, device and system for processing multicast data | |
| KR101491397B1 (en) | Efficient multicasting in a distributed system architecture | |
| KR20110095948A (en) | Multicast quality of service module and method | |
| US20060029001A1 (en) | Multicast source discovery | |
| CN101106515A (en) | Service quality guarantee method and system in multicast network | |
| CN106375100B (en) | Method of realizing group broadcasting and device in a kind of video monitoring system | |
| CN102694734B (en) | Two-layer switching equipment realizes the method for multicast based on linux kernel bridge | |
| CN106713348B (en) | OLT multicast uplink protocol message forwarding method and system | |
| CN102308518A (en) | Method for using a computer network | |
| CN106059925B (en) | Multicast processing method and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |