CN109981306B - Multicast data processing method, device, equipment and machine readable storage medium - Google Patents
Multicast data processing method, device, equipment and machine readable storage medium Download PDFInfo
- Publication number
- CN109981306B CN109981306B CN201910231468.4A CN201910231468A CN109981306B CN 109981306 B CN109981306 B CN 109981306B CN 201910231468 A CN201910231468 A CN 201910231468A CN 109981306 B CN109981306 B CN 109981306B
- Authority
- CN
- China
- Prior art keywords
- multicast
- information
- interface
- receiver
- link state
- 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
- 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
-
- 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
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
- H04L45/123—Evaluation of link metrics
-
- 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/16—Multipoint routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure provides a multicast data processing method, apparatus, device and machine-readable storage medium, the method comprising: acquiring multicast source information, multicast group information, receiver information and link state information; generating a multicast list item according to the multicast source information, the multicast group information, the receiver information and the link state information; the key value of the multicast list item comprises the multicast source information and the multicast group information, and the content of the multicast list item comprises an uplink interface and a downlink interface; and after receiving the multicast data matched with the multicast source information and the multicast group information, processing the multicast data by utilizing the uplink interface and the downlink interface. By the technical scheme, the convergence rate can be increased, and the service experience can be improved.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a multicast data processing method, apparatus, device, and machine-readable storage medium.
Background
The multicast technology is an efficient transmission technology for realizing single-point transmission and multi-point reception, and in the multicast technology, a host that transmits multicast data is called a multicast source, and a host that receives multicast data is called a receiver. In order to transmit multicast data, a multicast entry needs to be established in each network device (e.g., a router), where the multicast entry uses the IP address of the multicast source and the IP address of the multicast group as an index, and the multicast entry directs transmission of the multicast data.
In order to establish the Multicast table entry, the network device needs to support a Multicast routing Protocol, such as a PIM-DM (Protocol Independent Multicast-Dense-Mode) Protocol, a PIM-SM (Protocol Independent Multicast-Sparse Mode) Protocol, and the like, and establish the Multicast table entry based on the Multicast routing Protocol, and then transmit Multicast data by using the Multicast table entry.
Taking PIM-SM protocol as an example, a network device connected to a receiver sends a join packet to an RP (Rendezvous Point), where the join packet is sent to the RP hop by hop, and a path that passes through forms an RPT (Rendezvous Point Tree). And the network equipment connected with the multicast source sends a registration message to the RP, and the registration message triggers the establishment of SPT (Shortest Path Tree) after reaching the RP. The multicast source sends multicast data along the SPT to the RP, which sends the multicast data along the RPT to the receiver.
Disclosure of Invention
The present disclosure provides a multicast data processing method, applied to a network device, the method including:
acquiring multicast source information, multicast group information, receiver information and link state information;
generating a multicast list item according to the multicast source information, the multicast group information, the receiver information and the link state information; the key value of the multicast list item comprises the multicast source information and the multicast group information, and the content of the multicast list item comprises an uplink interface and a downlink interface;
and after receiving the multicast data matched with the multicast source information and the multicast group information, processing the multicast data by utilizing the uplink interface and the downlink interface.
The present disclosure provides a multicast data processing apparatus applied to a network device, the apparatus comprising:
the acquisition module is used for acquiring multicast source information, multicast group information, receiver information and link state information;
a generating module, configured to generate a multicast entry according to the multicast source information, the multicast group information, the receiver information, and the link state information; the key value of the multicast list item comprises the multicast source information and the multicast group information, and the content of the multicast list item comprises an uplink interface and a downlink interface;
and the processing module is used for processing the multicast data by utilizing the uplink interface and the downlink interface after receiving the multicast data matched with the multicast source information and the multicast group information.
The present disclosure provides an electronic device, including: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to implement the multicast data processing method described above.
The present disclosure provides a machine-readable storage medium having stored thereon machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the multicast data processing method described above.
Based on the above technical solution, in the embodiment of the present disclosure, a multicast entry may be generated according to multicast source information, multicast group information, recipient information, and link state information, and multicast data is processed by using the multicast entry, that is, a multicast entry may be generated based on the link state information without an additional multicast routing protocol, so as to solve the problems of long establishment time of the multicast entry, complex implementation manner, and the like, improve convergence speed, reduce implementation complexity, greatly improve reliability during network oscillation, and improve service experience.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present disclosure or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present disclosure.
FIG. 1 is a schematic diagram of an application scenario in one embodiment of the present disclosure;
fig. 2 is a flowchart of a multicast data processing method in an embodiment of the present disclosure;
fig. 3 is a block diagram of a multicast data processing apparatus according to an embodiment of the present disclosure;
fig. 4 is a hardware configuration diagram of a network device in one embodiment of the present disclosure.
Detailed Description
The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information in the embodiments of the present disclosure, such information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
In the PIM-SM protocol, the process of constructing RPT and SPT is the process of establishing multicast table entries in each network device. The process of transmitting the multicast data to the RP along the SPT and transmitting the multicast data to the receiver along the RPT is a process of transmitting the multicast data by each network device using the multicast entry.
However, when a multicast entry is established based on a multicast routing protocol, there are problems of long establishment time of the multicast entry, complex implementation mode, and the like. For example, it is necessary to interactively add a message, register a message, and the like between network devices, and establish an RPT, an SPT, and the like using these messages, which takes a relatively long time. Each network device needs to support the PIM-SM protocol and establish a multicast table entry based on the PIM-SM protocol, and the implementation mode is complex.
In view of the above problems, the present disclosure provides a multicast data processing method, which is applied to a multicast network, that is, a network that transmits multicast data by using a multicast technology. In a multicast network, a multicast source, a recipient (e.g., one or more recipients), a plurality of network devices (e.g., routers, switches, etc.) may be included. Referring to fig. 1, which is a schematic view of an application scenario of the embodiment of the present disclosure, a host 111 is a multicast source, a host 112 and a host 113 are receivers, a network device 121-a network device 125 are network devices between the multicast source and the receivers, the multicast source transmits multicast data to the network device, and the network device transmits the multicast data to the receivers.
In order to realize the transmission of multicast data, it is necessary to generate a multicast entry in each network device and transmit multicast data based on the multicast entry, and the generation of the multicast entry and the transmission of the multicast data will be described below.
Referring to fig. 2, a flowchart of a multicast data processing method is shown, where the method may include:
In one example, for a multicast network in which both the multicast source and the receiver are fixed, the multicast source information, the multicast group information, and the receiver information may be statically configured in advance in each network device. On this basis, the network device can acquire statically configured multicast source information, multicast group information, and receiver information.
For example, in some application scenarios, for network stability and simple implementation, the multicast source and the receiver may be fixed, that is, both the multicast source and the receiver are fixed, and the multicast group is also fixed, instead of dynamically creating the multicast source, the multicast group, and the receiver as needed. Assuming that host 111 is fixed as the multicast source, i.e., the multicast source does not change, host 112 and host 113 are fixed as the receiver, i.e., the receiver does not change.
In this application scenario, the multicast source information, the multicast group information, and the receiver information are known, and the user can acquire the multicast source information, the multicast group information, and the receiver information and store the multicast source information, the multicast group information, and the receiver information in each network device. Based on this, for each network device, statically configured multicast source information, multicast group information, and recipient information may be acquired from the device.
In another example, the multicast source information, the multicast group information, and the receiver information of the multicast network are collected by a control device (e.g., any network device in fig. 1, or other device not shown in fig. 1), and the collection process is not limited, for example, the multicast source and the receiver can notify the control device of their own information. Then, the control device transmits the multicast source information, the multicast group information, and the receiver information to each network device. For each network device, multicast source information, multicast group information, and recipient information may be acquired from the control device.
In a three-layer multicast network, the multicast source information may be an IP address of the multicast source (i.e., an IP address of the multicast source S, such as host 111), the multicast group information may be an IP address of the multicast group (i.e., multicast group G), and the recipient information may be an IP address of the recipient (e.g., IP addresses of host 112 and host 113).
In addition, in the two-layer multicast Network, the multicast source information may be a MAC (Media Access Control) address of the multicast source (e.g., a MAC address of the host 111), the multicast group information may be a VLAN (Virtual Local Area Network) of the multicast group, and the receiver information may be a MAC address of the receiver (e.g., a MAC address of the host 112 and a MAC address of the host 113).
For convenience of description, in the following embodiments, an IP address of a multicast source, an IP address of a multicast group, and an IP address of a receiver are taken as examples for explanation, and the implementation process is similar for a scenario of a two-layer multicast network.
In step 202, the network device obtains link state information, i.e. link state information of the multicast network.
Specifically, the network device may obtain the Link State information of the network device, receive a Link State message (such as an LSA (Link-State Advertisement) message) sent by another network device in the multicast network, and obtain the Link State information of the other network device according to the Link State message.
Further, the network device may generate a link-state topology of the multicast network by using the link-state information, that is, the network topology shown in fig. 1 is a link-state topology of the multicast network.
For example, assume that the device identification of network device 121 is aaa, the device identification of network device 122 is bbb, the device identification of network device 123 is ccc, the device identification of network device 124 is ddd, the device identification of network device 125 is eee, the device identification of host 111 is fff, the device identification of host 112 is ggg, and the device identification of host 113 is hhh. The device identifiers are unique, and for each host, in a three-layer multicast network, the device identifiers may be local IP addresses, and in a two-layer multicast network, the device identifiers may be local MAC addresses. For each network device, in a three-layer multicast network, the device identifier may be a Router-ID (e.g., an IP address), and in a two-layer multicast network, the device identifier may be a bridge MAC address.
The IP address of the interface 1211 of the network device 121 is 2.1.1.1/24, the IP address of the host 111 connected to the interface 1211 is 2.1.1.2/24, and the multicast source information may include the IP address 2.1.1.2/24.
The IP address of interface 1212 is 3.1.1.1/24 and the IP address of interface 1221 is 3.1.1.2/24.
Interface 1222 has an IP address of 5.1.1.1/24 and interface 1241 has an IP address of 5.1.1.2/24.
Interface 1232 has an IP address of 6.1.1.1/24 and interface 1251 has an IP address of 6.1.1.2/24.
The IP address of the interface 1242 is 7.1.1.1/24, and the IP address of the interface 1252 is 7.1.1.2/24.
The IP address of the interface 1243 of the network device 124 is 8.1.1.1/24, the IP address of the host 112 connected to the interface 1243 is 8.1.1.2/24, and the recipient information may include the IP address 8.1.1.2/24.
The IP address of the interface 1253 of the network device 125 is 9.1.1.1/24, the IP address of the host 113 connected to the interface 1253 is 9.1.1.2/24, and the recipient information may include the IP address 9.1.1.2/24.
In the above application scenario, each network device may collect link state information, such as an interface IP address, a device identifier of a device where the interface is located, and the like. Specifically, each network device may send a link status message in a broadcast manner, where the link status message carries link status information, and each network device may obtain link status information of all network devices based on the link status information carried by the link status message.
Based on these link-state information, the link-state topology of the multicast network may be determined for each network device. For example, network device 121, identified as aaa, may include interface 1211, interface 1212, interface 1213, interface 1211 having an IP address of 2.1.1.1/24, interface 1211 connected to host 111, interface 1212 having an IP address of 3.1.1.1/24, interface 1212 connected to interface 1221 of network device 122, interface 1213 having an IP address of 4.1.1.1/24, interface 1213 connected to interface 1231 of network device 123, and so on. Eventually, each network device may obtain the link-state topology shown in fig. 1.
Of course, the above is only one example of obtaining the link state information and determining the link state topology based on the link state information, and the implementation manners of obtaining the link state information and determining the link state topology based on the link state information are all within the protection scope of the embodiment of the present disclosure.
The number of the uplink interfaces may be one, and the number of the downlink interfaces may be one or more.
In one example, the network device generates a multicast entry according to the multicast source information, the multicast group information, the receiver information and the link state information, which may include but is not limited to: determining the multicast source information and the multicast group information as the key value of the multicast list item; according to the multicast source information, the receiver information and the link state information, determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver; and determining the uplink interface and the downlink interface as the content of the multicast table entry.
The following describes a process for generating multicast entries in conjunction with two specific implementations.
In the first mode, the multicast source information and the multicast group information are determined as the key value of the multicast list item. Determining a first optimal path from the multicast source to the equipment according to the multicast source information and the link state information, and determining an interface of the equipment of the first optimal path as an uplink interface; and determining a second optimal path from the equipment to the receiver according to the receiver information and the link state information, and determining the interface of the second optimal path at the equipment as a downlink interface. And determining the uplink interface and the downlink interface as the content of the multicast table entry.
For each network device, determining a first optimal path from the multicast source to the device according to the multicast source information and the link state information may include: the link state topology is determined by using the link state information, in a specific manner, see the above embodiment. Then, based on the link state topology, a shortest path algorithm is adopted to determine an optimal path from the multicast source to the device, and for the sake of convenience of differentiation, the optimal path is referred to as a first optimal path, where the first optimal path includes an interface from the multicast source to a network device through which the device passes.
The Shortest Path Algorithm (Shortest Path Algorithm) may include, but is not limited to: dijkstra (Dijkstra) algorithm, Bellman-Ford (Bellman-Ford) algorithm, Floyd (flouyd) algorithm, or SPF (Shortest Path first) algorithm, without limitation.
The shortest path algorithm employed by each network device may be the same, such as an SPF algorithm employed by each network device. Moreover, when each network device selects the optimal path by using the shortest path algorithm, the adopted strategies may be the same. For example, the path with the smallest link cost value is preferentially selected as the shortest path. If there are multiple paths with the minimum link cost values, that is, if the link cost values of the multiple paths are the same, the path with the minimum device identifier (or the path with the maximum device identifier) is taken as the shortest path. If there are a plurality of paths with the smallest device identifier, that is, if the device identifiers of the plurality of paths are the same, the path with the smallest interface address (or the largest interface address) may be the shortest path. Of course, the above is only an example of selecting the shortest path, and no limitation is made to this.
After the first optimal path from the multicast source to the device is determined, the interface of the device on which the first optimal path is located may be determined as an uplink interface, and the number of the uplink interfaces may be one.
For each network device, determining a second optimal path from the device to the receiver according to the receiver information and the link state information may include: the link state topology is determined by using the link state information, in a specific manner, see the above embodiment. Then, based on the link state topology, a shortest path algorithm is adopted to determine an optimal path from the device to the receiver, and for the sake of differentiation, the optimal path is referred to as a second optimal path, and the second optimal path includes interfaces from the device to network devices passed by the receiver.
Referring to the above embodiments, the shortest path algorithm may include, but is not limited to: the Dijkstra algorithm, Bellman-Ford algorithm, Floyd algorithm, or SPF algorithm, without limitation. Moreover, the shortest path algorithm employed by each network device may be the same, such as an SPF algorithm employed by each network device. In addition, when each network device selects the optimal path by using the shortest path algorithm, the adopted strategy may be the same.
After determining the second optimal path from the device to the receiver, the interface of the device may be determined as a downlink interface, and the number of the downlink interfaces may be one or more.
Further, when the interface of the second optimal path in the device is determined as the downlink interface, it is first determined whether the interface of the second optimal path in the device is already determined as the uplink interface. If not, the interface can be determined as a downlink interface; if so, the interface is not determined to be a downstream interface.
Of course, the above-mentioned method is only an example of determining the downlink interface, and other methods may also be used to determine the downlink interface, which is not limited to this. For example, a unicast route from the device to the receiver is searched (each network device has a routing table including unicast routes from the device to other devices, and the generation process of the routing table and the content of the routing table are not limited), and then, an outgoing interface of the unicast route is determined as a downstream interface.
The first mode will be described in detail below with reference to the application scenario shown in fig. 1. In this application scenario, the network device 124 is taken as an example for description, and the implementation of other network devices is similar to the network device 124.
First, network device 124 may determine multicast source information (e.g., 2.1.1.2/24 for the IP address of host 111) and multicast group information (e.g., 224.0.0.1 for the multicast group address) as the key for the multicast entry.
Then, the network device 124 determines the first optimal path from the host 111 to the device by using a shortest path algorithm based on the link state topology, and the determination method is not limited. For example, referring to fig. 1, the first optimal path may include: interface 1211 of network device 121, interface 1212 of network device 121, interface 1221 of network device 122, interface 1222 of network device 122, and interface 1241 of network device 124.
Then, since the interface of the first optimal path at the network device 124 is the interface 1241, the network device 124 determines the interface 1241 as an uplink interface and determines the uplink interface as the content of the multicast entry.
In addition, network device 124 determines a second optimal path from the device to host 113 using a shortest path algorithm based on the link state topology. For example, referring to fig. 1, the second optimal path may include: interface 1242 of network device 124-interface 1252 of network device 125-interface 1253 of network device 125. Since the second optimal path is interface 1242 at the interface of the network device 124, the network device 124 may determine the interface 1242 as a downstream interface and determine the downstream interface as the content of the multicast entry.
In summary, the network device 124 may generate the multicast table entry shown in table 1.
TABLE 1
| Key value | Uplink interface | Downlink interface |
| 2.1.1.2/24、224.0.0.1 | |
Interface 1243 and |
| … | … | … |
And secondly, determining the multicast source information and the multicast group information as key values of the multicast entries. Determining a third optimal path from the multicast source to the receiver according to the multicast source information, the receiver information and the link state information, and judging whether the third optimal path passes through the device; if so, determining the third optimal path as an uplink interface at the input interface of the equipment, and determining the third optimal path as a downlink interface at the output interface of the equipment. And determining the uplink interface and the downlink interface as the content of the multicast table entry. If the third optimal path does not pass through the device, the device does not generate the multicast table entry aiming at the multicast source to the receiver.
For each network device, determining a third optimal path from the multicast source to the receiver according to the multicast source information, the receiver information, and the link state information may include: the link state topology is determined by using the link state information, in a specific manner as in the above embodiment. Then, based on the link state topology, a shortest path algorithm is adopted to determine an optimal path from the multicast source to the receiver, and for the sake of differentiation, the optimal path is referred to as a third optimal path, and the third optimal path includes interfaces of network devices passing from the multicast source to the receiver.
Referring to the above embodiments, the shortest path algorithm may include, but is not limited to: the Dijkstra algorithm, Bellman-Ford algorithm, Floyd algorithm, or SPF algorithm, without limitation. Moreover, the shortest path algorithm employed by each network device may be the same, such as an SPF algorithm employed by each network device. In addition, when each network device selects the optimal path by using the shortest path algorithm, the adopted strategy may be the same.
After determining the third optimal path from the multicast source to the receiver, it may be determined whether the third optimal path passes through the present device. If not, the multicast list item does not need to be generated. If yes, determining the third optimal path as an uplink interface at the input interface of the device, where the number of the uplink interfaces may be one; and determining the third optimal path as a downlink interface at an outgoing interface of the device, where the number of the downlink interfaces may be one or more.
The second mode will be described in detail below with reference to the application scenario shown in fig. 1. In this application scenario, the network device 124 is taken as an example for description, and the implementation of other network devices is similar to the network device 124.
First, network device 124 may determine multicast source information (e.g., 2.1.1.2/24 for the IP address of host 111) and multicast group information (e.g., 224.0.0.1 for the multicast group address) as the key for the multicast entry.
Then, the network device 124 determines a third optimal path from the host 111 to the host 112 by using a shortest path algorithm based on the link state topology, and the determination method is not limited. For example, referring to fig. 1, the third optimal path may include: interface 1211 of network device 121, interface 1212 of network device 121, interface 1221 of network device 122, interface 1222 of network device 122, interface 1241 of network device 124, and interface 1243 of network device 124. Since the third optimal path passes through the present device (i.e., the network device 124), the third optimal path is determined as the uplink interface at the input interface (i.e., the interface 1241) of the present device, and the uplink interface is determined as the content of the multicast entry, and the third optimal path is determined as the downlink interface at the output interface (i.e., the interface 1243) of the present device, and the downlink interface is determined as the content of the multicast entry.
In addition, the network device 124 determines a third optimal path from the host 111 to the host 113 by using a shortest path algorithm based on the link state topology, and the determination method is not limited. For example, referring to fig. 1, the third optimal path may include: interface 1211-interface 1213 of network device 121-interface 1231 of network device 123-interface 1252 of network device 125-interface 1253 of network device 125. Since the third optimal path does not pass through the device (i.e., network device 124), no multicast entry is generated for the third optimal path from host 111 to host 113.
In summary, the network device 124 may generate the multicast table entry shown in table 2.
TABLE 2
| Key value | Uplink interface | Downlink interface |
| 2.1.1.2/24、224.0.0.1 | |
Interface 1243 |
| … | … | … |
In summary, in the above-mentioned first or second mode, each network device may generate a multicast entry, and then may instruct transmission of multicast data based on the multicast entry, where the specific process refers to the following steps.
In step 204, after receiving the multicast data matched with the multicast source information and the multicast group information, the network device processes the multicast data by using the uplink interface and the downlink interface.
Specifically, processing the multicast data by using the uplink interface and the downlink interface may include: acquiring a receiving interface of the multicast data on the device; if the receiving interface is the uplink interface, sending multicast data through the downlink interface; if the receiving interface is not the uplink interface, discarding the multicast data.
For example, for multicast data sent by the multicast source (i.e., host 111), it is assumed that the source address of the multicast data is IP address 2.1.1.2/24 of host 111, and the multicast group address of the multicast data is 224.0.0.1.
Assuming that the network device 124 generates the multicast entry shown in table 1 in one way, after receiving the multicast data, since the IP address 2.1.1.2/24 and the multicast group address 224.0.0.1 of the multicast data match the multicast entry shown in table 1, if the network device 124 receives the multicast data through the interface 1241, the receiving interface of the multicast data on the local device is the interface 1241, and since the interface 1241 is the uplink interface in the multicast entry, the network device 124 may send the multicast data through the downlink interfaces (the interface 1243 and the interface 1242) in the multicast entry. In addition, if the network device 124 receives the multicast data through the interface 1242, the receiving interface of the multicast data on the device is the interface 1242, and since the interface 1242 is not an uplink interface in the multicast entry, the network device 124 may discard the multicast data.
In addition, it is assumed that the network device 124 generates the multicast entry shown in table 2 in the second mode, and after receiving the multicast data, since the IP address 2.1.1.2/24 and the multicast group address 224.0.0.1 of the multicast data match the multicast entry shown in table 2, if the network device 124 receives the multicast data through the interface 1241, the receiving interface of the multicast data on the local device is the interface 1241, and since the interface 1241 is the uplink interface in the multicast entry, the network device 124 can send the multicast data through the downlink interface (interface 1243) in the multicast entry. In addition, if the network device 124 receives the multicast data through the interface 1242, the receiving interface of the multicast data on the device is the interface 1242, and since the interface 1242 is not an uplink interface in the multicast entry, the network device 124 may discard the multicast data.
Based on the above technical solution, in the embodiment of the present disclosure, a multicast entry may be generated according to multicast source information, multicast group information, recipient information, and link state information, and multicast data is processed by using the multicast entry, that is, a multicast entry may be generated based on the link state information without an additional multicast routing protocol, so as to solve the problems of long establishment time of the multicast entry, complex implementation manner, and the like, improve convergence speed, reduce implementation complexity, greatly improve reliability during network oscillation, and improve service experience.
Based on the same concept as the method described above, the embodiment of the present disclosure further provides a multicast data processing apparatus, where the multicast data processing apparatus is applied to a network device, and as shown in fig. 3, the apparatus includes:
an obtaining module 31, configured to obtain multicast source information, multicast group information, receiver information, and link state information;
a generating module 32, configured to generate a multicast entry according to the multicast source information, the multicast group information, the receiver information, and the link state information; the key value of the multicast list item comprises the multicast source information and the multicast group information, and the content of the multicast list item comprises an uplink interface and a downlink interface;
and a processing module 33, configured to process the multicast data by using the uplink interface and the downlink interface after receiving the multicast data matched with the multicast source information and the multicast group information.
The generating module 32 is specifically configured to, when generating a multicast entry according to the multicast source information, the multicast group information, the receiver information, and the link state information:
determining the multicast source information and the multicast group information as key values of the multicast list items;
according to the multicast source information, the receiver information and the link state information, determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver;
and determining the uplink interface and the downlink interface as the content of the multicast table entry.
The generating module 32 determines, according to the multicast source information, the receiver information, and the link state information, that when the multicast source reaches the uplink interface of the device and when the device reaches the downlink interface of the receiver, the device is specifically configured to: determining a first optimal path from a multicast source to the equipment according to the multicast source information and the link state information, and determining an interface of the first optimal path at the equipment as the uplink interface;
and determining a second optimal path from the equipment to the receiver according to the receiver information and the link state information, and determining an interface of the second optimal path at the equipment as the downlink interface.
The generating module 32 determines, according to the multicast source information, the receiver information, and the link state information, that when the multicast source reaches the uplink interface of the device and when the device reaches the downlink interface of the receiver, the device is specifically configured to: determining a third optimal path from the multicast source to the receiver according to the multicast source information, the receiver information and the link state information, and judging whether the third optimal path passes through the device;
if so, determining the third optimal path as the uplink interface at the input interface of the device, and determining the third optimal path as the downlink interface at the output interface of the device.
The processing module 33 is specifically configured to, when processing the multicast data by using the uplink interface and the downlink interface: acquiring a receiving interface of the multicast data on the device;
if the receiving interface is the uplink interface, the multicast data is sent through the downlink interface;
and if the receiving interface is not the uplink interface, discarding the multicast data.
In terms of hardware, the electronic device (such as the network device described above) provided in the embodiment of the present disclosure may specifically refer to fig. 4, and may include: a machine-readable storage medium and a processor, wherein: the machine-readable storage medium stores machine-executable instructions executable by the processor, and the processor communicates with the machine-readable storage medium, reads and executes the instruction codes stored in the machine-readable storage medium, to implement the multicast data processing method.
The disclosed embodiments provide a machine-readable storage medium having stored thereon machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the above-described multicast data processing method.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the various elements may be implemented in the same one or more software and/or hardware implementations in practicing the disclosure.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the disclosed embodiments may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only an example of the present disclosure and is not intended to limit the present disclosure. Various modifications and variations of this disclosure will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the scope of the claims of the present disclosure.
Claims (8)
1. A multicast data processing method, applied to a network device, the method comprising:
acquiring multicast source information, multicast group information, receiver information and link state information;
generating a multicast list item according to the multicast source information, the multicast group information, the receiver information and the link state information; the key value of the multicast list item comprises the multicast source information and the multicast group information, and the content of the multicast list item comprises an uplink interface and a downlink interface;
after receiving multicast data matched with the multicast source information and the multicast group information, processing the multicast data by utilizing the uplink interface and the downlink interface;
generating a multicast entry according to the multicast source information, the multicast group information, the receiver information, and the link state information, including: determining the multicast source information and the multicast group information as key values of the multicast list items; according to the multicast source information, the receiver information and the link state information, determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver; determining the uplink interface and the downlink interface as the content of the multicast table item;
determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver according to the multicast source information, the receiver information and the link state information, including:
determining a first optimal path from a multicast source to the equipment according to the multicast source information and the link state information, and determining an interface of the first optimal path at the equipment as the uplink interface;
and determining a second optimal path from the equipment to the receiver according to the receiver information and the link state information, and determining an interface of the second optimal path at the equipment as the downlink interface.
2. The method of claim 1,
determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver according to the multicast source information, the receiver information and the link state information, further comprising:
determining a third optimal path from the multicast source to the receiver according to the multicast source information, the receiver information and the link state information, and judging whether the third optimal path passes through the device;
if so, determining the third optimal path as the uplink interface at the input interface of the device, and determining the third optimal path as the downlink interface at the output interface of the device.
3. The method of claim 1,
processing the multicast data by using the uplink interface and the downlink interface, including:
acquiring a receiving interface of the multicast data on the device;
if the receiving interface is the uplink interface, the multicast data is sent through the downlink interface;
and if the receiving interface is not the uplink interface, discarding the multicast data.
4. The method of claim 1,
the method is applied to a multicast network with fixed multicast sources and receivers;
acquiring multicast source information, multicast group information, receiver information and link state information, comprising:
acquiring statically configured multicast source information, multicast group information and receiver information;
and acquiring the link state information of the equipment, receiving link state messages sent by other network equipment in the multicast network, and acquiring the link state information of other network equipment according to the link state messages.
5. The method according to any one of claims 1 to 4, wherein the multicast source information is an IP address of a multicast source, the multicast group information is an IP address of a multicast group, and the receiver information is an IP address of a receiver; or, the multicast source information is a media access control MAC address of a multicast source, the multicast group information is a VLAN of a multicast group, and the receiver information is a MAC address of a receiver.
6. A multicast data processing apparatus, applied to a network device, the apparatus comprising:
the acquisition module is used for acquiring multicast source information, multicast group information, receiver information and link state information;
a generating module, configured to generate a multicast entry according to the multicast source information, the multicast group information, the receiver information, and the link state information; the key value of the multicast list item comprises the multicast source information and the multicast group information, and the content of the multicast list item comprises an uplink interface and a downlink interface;
the processing module is used for processing the multicast data by utilizing the uplink interface and the downlink interface after receiving the multicast data matched with the multicast source information and the multicast group information;
generating a multicast entry according to the multicast source information, the multicast group information, the receiver information, and the link state information, including: determining the multicast source information and the multicast group information as key values of the multicast list items; according to the multicast source information, the receiver information and the link state information, determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver; determining the uplink interface and the downlink interface as the content of the multicast table item;
determining an uplink interface from the multicast source to the device and a downlink interface from the device to the receiver according to the multicast source information, the receiver information and the link state information, including:
determining a first optimal path from a multicast source to the equipment according to the multicast source information and the link state information, and determining an interface of the first optimal path at the equipment as the uplink interface;
and determining a second optimal path from the equipment to the receiver according to the receiver information and the link state information, and determining an interface of the second optimal path at the equipment as the downlink interface.
7. An electronic device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to perform the method steps of any of claims 1-5.
8. A machine-readable storage medium having stored thereon machine-executable instructions which, when invoked and executed by a processor, cause the processor to perform the method steps of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910231468.4A CN109981306B (en) | 2019-03-26 | 2019-03-26 | Multicast data processing method, device, equipment and machine readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910231468.4A CN109981306B (en) | 2019-03-26 | 2019-03-26 | Multicast data processing method, device, equipment and machine readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109981306A CN109981306A (en) | 2019-07-05 |
| CN109981306B true CN109981306B (en) | 2021-09-21 |
Family
ID=67080528
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910231468.4A Active CN109981306B (en) | 2019-03-26 | 2019-03-26 | Multicast data processing method, device, equipment and machine readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109981306B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101383772A (en) * | 2008-09-26 | 2009-03-11 | 中兴通讯股份有限公司 | Method and device for automatically discovering and establishing MAC route information table |
| WO2014072374A1 (en) * | 2012-11-09 | 2014-05-15 | Siemens Aktiengesellschaft | Method for transmitting messages in an industrial communication network of an industrial automation system and communication device for an industrial communication network |
| CN105337746A (en) * | 2015-09-23 | 2016-02-17 | 浙江宇视科技有限公司 | Multicast data transmission method and apparatus |
| CN105634952A (en) * | 2015-07-29 | 2016-06-01 | 杭州华三通信技术有限公司 | Fast notification method and apparatus for LSP message |
| CN106059962A (en) * | 2016-06-07 | 2016-10-26 | 杭州华三通信技术有限公司 | Forwarding method and device for multicast messages in SPBM (Shortest Path Bridging Virtual Local Area Network Mode) network |
| CN106209622A (en) * | 2016-06-23 | 2016-12-07 | 广州海格通信集团股份有限公司 | A kind of method of multicasting based on SDN |
| CN106357540A (en) * | 2016-08-24 | 2017-01-25 | 浪潮(北京)电子信息产业有限公司 | Multicast control method and device thereof as well as multicast system |
| CN108923946A (en) * | 2018-06-27 | 2018-11-30 | 中国人民解放军国防科技大学 | Centralized multicast control method based on software definition |
-
2019
- 2019-03-26 CN CN201910231468.4A patent/CN109981306B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101383772A (en) * | 2008-09-26 | 2009-03-11 | 中兴通讯股份有限公司 | Method and device for automatically discovering and establishing MAC route information table |
| WO2014072374A1 (en) * | 2012-11-09 | 2014-05-15 | Siemens Aktiengesellschaft | Method for transmitting messages in an industrial communication network of an industrial automation system and communication device for an industrial communication network |
| CN105634952A (en) * | 2015-07-29 | 2016-06-01 | 杭州华三通信技术有限公司 | Fast notification method and apparatus for LSP message |
| CN105337746A (en) * | 2015-09-23 | 2016-02-17 | 浙江宇视科技有限公司 | Multicast data transmission method and apparatus |
| CN106059962A (en) * | 2016-06-07 | 2016-10-26 | 杭州华三通信技术有限公司 | Forwarding method and device for multicast messages in SPBM (Shortest Path Bridging Virtual Local Area Network Mode) network |
| CN106209622A (en) * | 2016-06-23 | 2016-12-07 | 广州海格通信集团股份有限公司 | A kind of method of multicasting based on SDN |
| CN106357540A (en) * | 2016-08-24 | 2017-01-25 | 浪潮(北京)电子信息产业有限公司 | Multicast control method and device thereof as well as multicast system |
| CN108923946A (en) * | 2018-06-27 | 2018-11-30 | 中国人民解放军国防科技大学 | Centralized multicast control method based on software definition |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109981306A (en) | 2019-07-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11665595B2 (en) | Forwarding entry generation method, controller, and network device | |
| US7911977B2 (en) | Designated router assignment per multicast group address/range | |
| US8982881B2 (en) | Upstream label allocation on ethernets for MP2MP LSPS | |
| CN110661711B (en) | Method for generating label forwarding table, message sending method, device and equipment | |
| US7304955B2 (en) | Scalable IP multicast with efficient forwarding cache | |
| CN107547391B (en) | Message transmission method and device | |
| CN109714274B (en) | Method for acquiring corresponding relation and routing equipment | |
| CN104335537A (en) | System and method for layer-2 multicast multipathing | |
| JP2018191290A (en) | Method, apparatus, and network system for implementing load balancing | |
| CN100484080C (en) | Routing access method, system and operator edge equipment for virtual private network | |
| CN105791109B (en) | Method, device and node for multicast forwarding of multi-protocol label switching intermediate node | |
| CN104283782B (en) | The method and apparatus that message forwarding path is determined in multi-protocol label switching network | |
| EP2892196B1 (en) | Method, network node and system for implementing point-to-multipoint multicast | |
| WO2017201750A1 (en) | Method, device and system for processing multicast data | |
| CN107547377B (en) | Multicast traffic transmission method and device | |
| CN109981306B (en) | Multicast data processing method, device, equipment and machine readable storage medium | |
| CN111600798B (en) | Method and equipment for sending and obtaining assertion message | |
| CN110062058B (en) | Network address configuration method and device | |
| WO2018010568A1 (en) | Information notification method, and method and apparatus for generating forwarding entry | |
| CN112054962B (en) | Method and device for realizing multicast | |
| CN102413062A (en) | Route selecting method and route equipment | |
| US7944846B1 (en) | DVMRP border router for reverse path forwarding validation with external sources | |
| CN107276774B (en) | Multicast message transmission method and forwarding equipment | |
| CN108600110B (en) | PIM message processing method and device | |
| CN108183859B (en) | Internet traffic scheduling method and system |
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 |