CN115134290A - Multicast signaling transmission method and system - Google Patents
Multicast signaling transmission method and system Download PDFInfo
- Publication number
- CN115134290A CN115134290A CN202110331611.4A CN202110331611A CN115134290A CN 115134290 A CN115134290 A CN 115134290A CN 202110331611 A CN202110331611 A CN 202110331611A CN 115134290 A CN115134290 A CN 115134290A
- Authority
- CN
- China
- Prior art keywords
- message
- pcep
- router
- multicast
- specified
- 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.)
- Granted
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/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure provides a multicast signaling transfer method and system. The multicast signaling transmission method comprises the following steps: after receiving an adding message sent by a host connected with a first router, the first router extracts first key information from the adding message, wherein the first key information comprises VPN information of a multicast source, a multicast group and an interface; the method comprises the steps that a first router sends a PCEP joining message to an SDN controller, wherein the PCEP joining message comprises first key information; the SDN controller inquires out a PCEP registration message matched with the first key information and sends a bit string message to a second router providing the PCEP registration message, wherein the bit string message comprises a first router identification; the second router encapsulates a BIER header for the first multicast data to generate second multicast data, and sends the second multicast data according to a corresponding BIFT forwarding table, wherein the BIER header comprises a bit string message; and after receiving the second multicast data through the network, the first router sends the first multicast data included in the second multicast data to the host.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and a system for multicast signaling transmission.
Background
Currently, there are two main ways for transmitting multicast signaling in IP networks: a mode based on a PIM (Protocol Independent Multicast) packet and a mode based on a BGP (Border Gateway Protocol).
The mode based on PIM is that multicast signaling is transmitted hop by hop among routers in the network, and each router needs to keep a corresponding control signaling state. .
In the BGP-based mode, an MP (Multiprotocol) -BGP neighbor is established between the border router connected to the multicast source and the border router connected to the multicast receiver, and the multicast signaling is transmitted by extending the MP-BGP message.
Disclosure of Invention
The inventor finds that the PIM-based method has a large multicast scale and poor scalability when there are many multicast groups, and the current industry has basically stopped the multicast service deployment based on the PIM-based method. Although the BGP-based method does not require an intermediate router to maintain a relevant state, under the condition of numerous receivers and uncertain distribution, the dynamic establishment and deletion of a BGP Session (Session) requires complex BGP signaling expansion and deployment, and under the condition of numerous multicast sources or multicast groups, the problem of poor expandability also exists.
Accordingly, the present disclosure provides a multicast signaling transfer scheme, so that a border router realizes transfer of multicast signaling based on a PCEP (Path computing Element Communication Protocol) extension. In addition, the scheme is efficiently combined with multicast data forwarding based on a BIER (Bit Indexed Explicit Replication) architecture, so that the scale flexible deployment of the multicast service is realized.
According to a first aspect of the embodiments of the present disclosure, there is provided a multicast data transmission method, including: after receiving an adding message sent by a host connected with a first router, the first router extracts first key information from the adding message, wherein the first key information comprises multicast source, multicast group and VPN information to which an interface belongs; the first router sends a PCEP join message to an SDN controller, wherein the PCEP join message comprises the first key information; after receiving the PCEP joining message, the SDN controller inquires out a PCEP registration message matched with the first key information and sends a bit string message to a second router providing the PCEP registration message, wherein the bit string message comprises a first router identification; after receiving first multicast data from the multicast source, the second router encapsulates a BIER header for the first multicast data to generate second multicast data, and sends the second multicast data according to a corresponding BIFT forwarding table, wherein the BIER header comprises the bit string message; and after receiving the second multicast data through the network, the first router sends the first multicast data included in the second multicast data to the host.
In some embodiments, after receiving an exit message sent by a host connected to the first router, the first router extracts second key information from the exit message, where the second key information includes multicast source and multicast group information; if no host joining the multicast group to receive multicast data from the multicast source currently exists, the first router sends a PCEP leave message to an SDN controller, wherein the PCEP leave message includes the second critical information; after receiving the PCEP leaving message, the SDN controller inquires a PCEP registration message matched with the second key information and sends deletion indication information to a second router providing the PCEP registration message, wherein the deletion indication information comprises a first router identifier; the second router deletes the bit string message associated with the first router identification.
In some embodiments, the join message is an IGMP membership message or an MLD membership message; the exit message is an IGMP exit group message or an MLD exit group message.
In some embodiments, the second router, in a case configured to receive multicast data for a specified multicast group from a specified multicast source from a specified interface, sends a PCEP registration message to the SDN controller, wherein the PCEP registration message includes VPN information to which the specified multicast source, specified multicast group, and specified interface belong; the SDN controller stores the PCEP registration message.
In some embodiments, the second router, in a case configured to cancel receiving multicast data for a specified multicast group from a specified multicast source from a specified interface, sends a PCEP registration stop message to the SDN controller, wherein the PCEP registration stop message includes VPN information to which the specified multicast source, the specified multicast group, and the specified interface belong; and the SDN controller deletes the corresponding PCEP registration message according to the PCEP registration stop message.
According to a second aspect of the embodiments of the present disclosure, there is provided a multicast data transmission system including: the system comprises a first router and a SDN controller, wherein the first router is configured to extract first key information from an adding message after receiving the adding message sent by a host connected with the first router, the first key information comprises VPN information of a multicast source, a multicast group and an interface, and the first router sends a PCEP adding message to the SDN controller, wherein the PCEP adding message comprises the first key information; further configured to transmit first multicast data included in the second multicast data to the host after receiving the second multicast data through the network; an SDN controller configured to, after receiving the PCEP join message, query a PCEP registration message matching the first key information, and send a bit string message to a second router providing the PCEP registration message, where the bit string message includes a first router identification; and the second router is configured to encapsulate a BIER header for the first multicast data to generate second multicast data after receiving the first multicast data from the multicast source, and send the second multicast data according to a corresponding BIFT forwarding table, wherein the BIER header comprises the bit string message.
In some embodiments, the first router is further configured to, after receiving an exit packet sent by a host connected to the first router, extract second key information from the exit packet, where the second key information includes multicast source and multicast group information, and send a PCEP leave message to an SDN controller if there is no host currently joining the multicast group to receive multicast data from the multicast source, where the PCEP leave message includes the second key information; the SDN controller is further configured to, after receiving the PCEP departure message, query out a PCEP registration message matching the second key information, and send deletion indication information to a second router providing the PCEP registration message, where the deletion indication information includes a first router identifier; the second router is further configured to delete the bit string message associated with the first router identification upon receiving the deletion indication information.
In some embodiments, the join message is an IGMP membership message or an MLD membership message; the exit message is an IGMP exit group message or an MLD exit group message.
In some embodiments, the second router is further configured to send a PCEP registration message to the SDN controller, where the PCEP registration message includes VPN information to which the specified multicast source, the specified multicast group, and the specified interface belong, in a case where the PCEP registration message is configured to receive multicast data for the specified multicast group from the specified multicast source from the specified interface; the SDN controller is further configured to store the PCEP registration message.
In some embodiments, the second router is further configured to send a PCEP registration stop message to the SDN controller in an instance configured to cancel receiving multicast data from a specified multicast source for a specified multicast group from a specified interface, wherein the PCEP registration stop message includes VPN information to which the specified multicast source, specified multicast group, and specified interface belong; the SDN controller is further configured to delete a corresponding PCEP registration message according to the PCEP registration stop message.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:
fig. 1 is a flow diagram of a multicast signaling method according to one embodiment of the present disclosure;
fig. 2 is a flow diagram of a multicast signaling method according to another embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a multicast signaling system according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a multicast signaling delivery system according to another embodiment of the present disclosure.
It should be understood that the dimensions of the various parts shown in the figures are not drawn to scale. Further, the same or similar reference numerals denote the same or similar components.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The description of the exemplary embodiments is merely illustrative and is in no way intended to limit the disclosure, its application, or uses. The present disclosure may be embodied in many different forms and is not limited to the embodiments described herein. These embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be noted that: the relative arrangement of parts and steps, the composition of materials and values set forth in these embodiments are to be construed as illustrative only and not as limiting unless otherwise specifically stated.
The use of "including" or "comprising" and the like in this disclosure is intended to mean that the elements preceding the word encompass the elements listed after the word and does not exclude the possibility that other elements may also be encompassed.
All terms (including technical or scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs unless specifically defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
Fig. 1 is a flow chart of a multicast signaling transfer method according to an embodiment of the present disclosure.
In step 101, after receiving an add message sent by a host connected to a first router, the first router extracts first key information from the add message, where the first key information includes a multicast source, a multicast group, and VPN (Virtual Private Network) information to which an interface belongs.
In some embodiments, the join message is an IGMP (Internet Group Management Protocol)/MLD (Multicast Listener Discovery Protocol) Membership (Membership Report) message.
At step 102, the first router sends a PCEP join (join) message to an SDN (Software Defined Network) controller, wherein the PCEP join message includes first critical information.
In step 103, after receiving the PCEP join message, the SDN controller queries out a PCEP registration (Register) message matching the first key information, and sends a bit string (bitstring) message to a second router providing the PCEP registration message, where the bit string message includes the first router identification.
In some embodiments, the second router, in an instance configured to receive multicast data for a specified multicast group from a specified multicast source from a specified interface, sends a PCEP registration message to the SDN controller, wherein the PCEP registration message includes the specified multicast source, the specified multicast group, and VPN information to which the specified interface belongs. The SDN controller stores the corresponding PCEP registration message.
For example, the PCEP registration message includes (specifying multicast source S, specifying multicast group G, specifying VPN information to which the interface belongs). For another example, the PCEP registration message includes (, specifies the multicast group G, specifies VPN information to which the interface belongs), and represents an arbitrary multicast source.
In some embodiments, the second router, in a case configured to cancel receiving multicast data for the specified multicast group from the specified multicast source from the specified interface, sends a PCEP registration Stop (Register Stop) message to the SDN controller, wherein the PCEP registration Stop message includes VPN information to which the specified multicast source, the specified multicast group, and the specified interface belong.
And the SDN controller deletes the corresponding PCEP registration message according to the PCEP registration stop message.
In step 104, after receiving the first multicast data from the multicast source, the second router encapsulates a BIER header for the first multicast data to generate second multicast data, and sends the second multicast data according to a corresponding biet forwarding table, where the BIER header includes the bit string message.
In step 105, the first router transmits the first multicast data included in the second multicast data to the host after receiving the second multicast data through the network.
It should be noted that, since the BIER architecture for multicast data forwarding based on bitstring is not the point of the present disclosure, the description is not provided here.
In the multicast signaling transfer scheme provided by the foregoing embodiment of the present disclosure, the border router implements transfer of multicast signaling based on PCEP extension. In addition, the method is efficiently combined with multicast data forwarding based on the BIER architecture, so that the scale flexible deployment of the multicast service is realized.
Fig. 2 is a flow chart of a multicast signaling method according to another embodiment of the disclosure.
In step 201, after receiving an exit message sent by a host connected to the first router, the first router extracts second key information from the exit message, where the second key information includes multicast source and multicast group information.
In some embodiments, the exit packet is an IGMP/MLD exit Group (Leave Group) packet.
In step 202, if there is no host currently joining the multicast group to receive multicast data from the multicast source, the first router sends a PCEP Leave (Leave) message to the SDN controller, where the PCEP Leave message includes the second critical information.
If the hosts currently connected with the first router also include hosts joining the multicast group to receive multicast data from the multicast source, the first router does not send PCEP leave messages so as to avoid affecting other hosts.
In step 203, after receiving the PCEP leave message, the SDN controller queries out a PCEP registration message matching the second key information, and sends deletion indication information to the second router providing the PCEP registration message, where the deletion indication information includes the first router identifier.
At step 204, the second router deletes the bit string message associated with the first router identification.
Fig. 3 is a schematic structural diagram of a multicast signaling delivery system according to an embodiment of the present disclosure. As shown in fig. 3, the system includes an SDN controller 30, and a first router 31 and a second router 32 in the network. The host 33 is connected to the first router 31.
After receiving an add message sent by a host 33 connected to the first router, the first router 31 extracts first key information from the add message, where the first key information includes VPN information to which a multicast source, a multicast group, and an interface belong.
In some embodiments, the join message is an IGMP/MLD membership message.
The first router 31 sends a PCEP join message to the SDN controller 30, wherein the PCEP join message includes the first critical information.
Upon receiving the PCEP join message, the SDN controller 30 is configured to query for a PCEP registration message matching the first key information, and send a bit string message to the second router 32 providing the PCEP registration message, the bit string message including the first router identification.
After receiving the first multicast data from the multicast source, the second router 32 encapsulates the BIER header for the first multicast data to generate second multicast data, and sends the second multicast data according to the corresponding BIFT forwarding table, where the BIER header includes a bit string message.
The first router 31 transmits the first multicast data included in the second multicast data to the host 33 after receiving the second multicast data through the network.
In the multicast signaling transfer system provided by the above embodiment of the present disclosure, the border router implements transfer of multicast signaling based on PCEP extension. In addition, the method is efficiently combined with multicast data forwarding based on the BIER framework, so that the scale flexible deployment of the multicast service is realized.
In some embodiments, after receiving the exit message sent by the host 33 connected to the first router, the first router 31 extracts second key information from the exit message, where the second key information includes multicast source and multicast group information. If there is no host currently joining the multicast group to receive multicast data from the multicast source, the first router 31 sends a PCEP leave message to the SDN controller 30, where the PCEP leave message includes the second critical information.
In some embodiments, the exit packet is an IGMP/MLD exit group packet.
Upon receiving the PCEP leave message, the SDN controller 30 queries out a PCEP registration message matching the second key information, and sends deletion indication information to the second router 32 providing the PCEP registration message, where the deletion indication information includes the first router identification.
The second router 32, upon receiving the deletion indication information, deletes the bit string message associated with the first router identification.
In some embodiments, the second router 32, in the event configured to receive multicast data for a specified multicast group from a specified multicast source from a specified interface, sends a PCEP registration message to the SDN controller 30, wherein the PCEP registration message includes VPN information for the specified multicast source, the specified multicast group, and a specified interface affiliation. The SDN controller 30 stores PCEP registration messages.
In some embodiments, the second router 32, in a case configured to cancel receiving multicast data for the specified multicast group from the specified multicast source from the specified interface, sends a PCEP registration stop message to the SDN controller 30, wherein the PCEP registration stop message includes VPN information to which the specified multicast source, the specified multicast group, and the specified interface belong. The SDN controller 30 deletes the corresponding PCEP registration message according to the PCEP registration stop message.
Fig. 4 is a schematic structural diagram of a multicast signaling delivery system according to another embodiment of the present disclosure.
As shown in fig. 4, the router R1, when configured to receive multicast data for a specified multicast group from a specified multicast source S1 from a specified interface, sends a PCEP registration message to the SDN controller. The PCEP registration message includes VPN information for the designated multicast source, the designated multicast group, and the designated interface affiliation. The SDN controller stores the PCEP registration message.
After receiving the IGMP/MLD membership message sent by the host H1 connected to the router R4, the router R4 extracts key information from the IGMP/MLD membership message, where the key information includes multicast source, multicast group, and VPN information to which an interface belongs.
Router R4 sends a PCEP join message to the SDN controller, where the PCEP join message includes the first critical information.
After receiving the PCEP join message, the SDN controller queries out a PCEP registration message matching the key information, and sends a bit string (bitstring) message to the router R1 providing the PCEP registration message, where the bit string message includes the identifier of the router R4.
After receiving the first multicast data from the multicast source S1, the router R1 encapsulates the BIER header for the first multicast data to generate second multicast data, and sends the second multicast data to the downstream router R2 according to the corresponding BIFT forwarding table, where the BIER header includes the bit string message.
The router R2 sends the second multicast data to the downstream router R3 according to the corresponding BIFT forwarding table, and the router R3 sends the second multicast data to the downstream router R4 according to the corresponding BIFT forwarding table.
The router R4, upon receiving the second multicast data, transmits the first multicast data included in the second multicast data to the host H1.
The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions, and the instructions, when executed by the processor, implement the method according to any one of the embodiments in fig. 1.
Through implementing this disclosure, can obtain following beneficial effect:
1. discovery of router corresponding to unspecified multicast source and multicast receiver can be realized
2. Complex BGP protocol extension and PIM-based router hop-by-hop state maintenance are not needed.
3. The method can be simultaneously suitable for intra-domain multicast, inter-domain multicast, global routing multicast and VPN-based multicast service deployment, and is suitable for IPv4 multicast service and IPv6 multicast service.
In some embodiments, the functional modules may be implemented as a general purpose Processor, a Programmable Logic Controller (PLC), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable Logic device, discrete Gate or transistor Logic, discrete hardware components, or any suitable combination thereof, for performing the functions described in this disclosure.
So far, embodiments of the present disclosure have been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It will be understood by those skilled in the art that various changes may be made in the above embodiments or equivalents may be substituted for elements thereof without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (10)
1. A method of multicast signaling delivery, comprising:
after receiving an adding message sent by a host connected with a first router, the first router extracts first key information from the adding message, wherein the first key information comprises multicast source, multicast group and VPN information to which an interface belongs;
the first router sends a PCEP join message to an SDN controller, wherein the PCEP join message comprises the first key information;
after receiving the PCEP join message, the SDN controller queries out a PCEP registration message matched with the first key information, and sends a bit string message to a second router providing the PCEP registration message, where the bit string message includes a first router identifier;
after receiving first multicast data from the multicast source, the second router encapsulates a BIER header for the first multicast data to generate second multicast data, and sends the second multicast data according to a corresponding BIFT forwarding table, wherein the BIER header comprises the bit string message;
and after receiving the second multicast data through the network, the first router sends the first multicast data included in the second multicast data to the host.
2. The method of claim 1, further comprising:
after receiving an exit message sent by a host connected with the first router, the first router extracts second key information from the exit message, wherein the second key information comprises multicast source and multicast group information;
if no host joining the multicast group to receive multicast data from the multicast source currently exists, the first router sends a PCEP leave message to an SDN controller, wherein the PCEP leave message includes the second critical information;
after receiving the PCEP leave message, the SDN controller queries a PCEP registration message matched with the second key information, and sends deletion indication information to a second router providing the PCEP registration message, where the deletion indication information includes a first router identifier;
the second router deletes the bit string message associated with the first router identification.
3. The method of claim 2, wherein,
the joining message is an IGMP membership message or an MLD membership message;
the exit message is an IGMP exit group message or an MLD exit group message.
4. The method of any of claims 1-3, further comprising:
the second router, in a case where the second router is configured to receive multicast data for a specified multicast group from a specified multicast source from a specified interface, sends a PCEP registration message to the SDN controller, where the PCEP registration message includes VPN information to which the specified multicast source, the specified multicast group, and the specified interface belong;
the SDN controller stores the PCEP registration message.
5. The method of claim 4, further comprising:
the second router, in a case where the second router is configured to cancel receiving, from a specified interface, multicast data for a specified multicast group from a specified multicast source, sends a PCEP registration stop message to the SDN controller, where the PCEP registration stop message includes VPN information to which the specified multicast source, the specified multicast group, and the specified interface belong;
and the SDN controller deletes the corresponding PCEP registration message according to the PCEP registration stop message.
6. A multicast signaling delivery system, comprising:
the system comprises a first router and a SDN controller, wherein the first router is configured to extract first key information from a joining message after receiving the joining message sent by a host connected with the first router, the first key information comprises VPN information of a multicast source, a multicast group and an interface, and send a PCEP joining message to the SDN controller, wherein the PCEP joining message comprises the first key information; further configured to transmit first multicast data included in the second multicast data to the host after receiving the second multicast data through the network;
an SDN controller configured to, after receiving the PCEP join message, query a PCEP registration message matching the first key information, and send a bit string message to a second router providing the PCEP registration message, where the bit string message includes a first router identification;
and the second router is configured to encapsulate a BIER header for the first multicast data to generate second multicast data after receiving the first multicast data from the multicast source, and send the second multicast data according to a corresponding BIFT forwarding table, wherein the BIER header comprises the bit string message.
7. The method of claim 6, wherein,
the first router is further configured to extract second key information from an exit message after receiving the exit message sent by a host connected with the first router, where the second key information includes multicast source and multicast group information, and send a PCEP leave message to an SDN controller if there is no host currently joining the multicast group to receive multicast data from the multicast source, where the PCEP leave message includes the second key information;
the SDN controller is further configured to, after receiving the PCEP departure message, query out a PCEP registration message matching the second key information, and send deletion indication information to a second router providing the PCEP registration message, where the deletion indication information includes a first router identifier;
the second router is further configured to delete the bit string message associated with the first router identification upon receiving the deletion indication information.
8. The system of claim 7, wherein,
the joining message is an IGMP membership message or an MLD membership message;
the exit message is an IGMP exit group message or an MLD exit group message.
9. The system of any one of claims 6-8,
the second router is further configured to send a PCEP registration message to the SDN controller, in the event that it is configured to receive multicast data for a specified multicast group from a specified multicast source from a specified interface, wherein the PCEP registration message includes VPN information to which the specified multicast source, specified multicast group, and specified interface belong;
the SDN controller is further configured to store the PCEP registration message.
10. The system of claim 9, wherein,
the second router is further configured to send a PCEP registration stop message to the SDN controller, in case it is configured to cancel receiving multicast data for a specified multicast group from a specified multicast source from a specified interface, wherein the PCEP registration stop message includes VPN information to which the specified multicast source, specified multicast group and specified interface belong;
the SDN controller is further configured to delete a corresponding PCEP registration message according to the PCEP registration stop message.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110331611.4A CN115134290B (en) | 2021-03-29 | 2021-03-29 | Multicast signaling transfer method and system |
PCT/CN2021/128705 WO2022205908A1 (en) | 2021-03-29 | 2021-11-04 | Method and system for transmitting multicast signaling |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110331611.4A CN115134290B (en) | 2021-03-29 | 2021-03-29 | Multicast signaling transfer method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN115134290A true CN115134290A (en) | 2022-09-30 |
CN115134290B CN115134290B (en) | 2023-06-20 |
Family
ID=83375588
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110331611.4A Active CN115134290B (en) | 2021-03-29 | 2021-03-29 | Multicast signaling transfer method and system |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115134290B (en) |
WO (1) | WO2022205908A1 (en) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008071111A1 (en) * | 2006-12-14 | 2008-06-19 | Huawei Technologies Co., Ltd. | Method, system and router for forwarding multicast data |
CN102316083A (en) * | 2010-07-06 | 2012-01-11 | 杭州华三通信技术有限公司 | Method and device for realizing multicast service in Internet protocol (IP) network |
CN106411751A (en) * | 2016-09-26 | 2017-02-15 | 杭州华三通信技术有限公司 | Route optimization method and apparatus |
WO2017156974A1 (en) * | 2016-03-18 | 2017-09-21 | 中兴通讯股份有限公司 | Information transmission method, apparatus and system |
CN107204920A (en) * | 2016-03-18 | 2017-09-26 | 中兴通讯股份有限公司 | A kind of quick heavy-route processing method, device and system |
WO2018006671A1 (en) * | 2016-07-07 | 2018-01-11 | 中兴通讯股份有限公司 | Message sending method and apparatus, network architecture, and computer storage medium |
US10158558B1 (en) * | 2017-01-19 | 2018-12-18 | Cisco Technology, Inc. | Segment routing of packets according to a multicast distribution tree in a network |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9450864B2 (en) * | 2013-10-11 | 2016-09-20 | Futurewei Technologies, Inc. | Using PCE as SDN controller |
-
2021
- 2021-03-29 CN CN202110331611.4A patent/CN115134290B/en active Active
- 2021-11-04 WO PCT/CN2021/128705 patent/WO2022205908A1/en active Application Filing
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008071111A1 (en) * | 2006-12-14 | 2008-06-19 | Huawei Technologies Co., Ltd. | Method, system and router for forwarding multicast data |
CN102316083A (en) * | 2010-07-06 | 2012-01-11 | 杭州华三通信技术有限公司 | Method and device for realizing multicast service in Internet protocol (IP) network |
WO2017156974A1 (en) * | 2016-03-18 | 2017-09-21 | 中兴通讯股份有限公司 | Information transmission method, apparatus and system |
CN107204920A (en) * | 2016-03-18 | 2017-09-26 | 中兴通讯股份有限公司 | A kind of quick heavy-route processing method, device and system |
WO2018006671A1 (en) * | 2016-07-07 | 2018-01-11 | 中兴通讯股份有限公司 | Message sending method and apparatus, network architecture, and computer storage medium |
CN107592262A (en) * | 2016-07-07 | 2018-01-16 | 中兴通讯股份有限公司 | File transmitting method and the network architecture of the cross-domain forwarding of device, message |
CN106411751A (en) * | 2016-09-26 | 2017-02-15 | 杭州华三通信技术有限公司 | Route optimization method and apparatus |
US10158558B1 (en) * | 2017-01-19 | 2018-12-18 | Cisco Technology, Inc. | Segment routing of packets according to a multicast distribution tree in a network |
Non-Patent Citations (2)
Title |
---|
Z. ZHANG; R. RASZUK; BLOOMBERG LP;D. PACELLA; VERIZON;A. GULKO; THOMSON REUTERS;: "Controller Based BGP Multicast Signaling\ndraft-ietf-bess-bgp-multicast-controller-03", IETF * |
熊焕;裴波;: "SDN架构在军事通信核心网中的应用研究", 指挥与控制学报 * |
Also Published As
Publication number | Publication date |
---|---|
WO2022205908A1 (en) | 2022-10-06 |
CN115134290B (en) | 2023-06-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11431650B2 (en) | Multicast based on bit indexed explicit replication | |
CN110460522B (en) | Multicast data transmission method, related device and system | |
US9832031B2 (en) | Bit index explicit replication forwarding using replication cache | |
US8243643B2 (en) | Active multicast information protocol | |
US6839348B2 (en) | System and method for distributing multicasts in virtual local area networks | |
US8339973B1 (en) | Multicast traceroute over MPLS/BGP IP multicast VPN | |
EP2378720B1 (en) | Extranet networking method, system and device for multicast virtual private network | |
CN106603407B (en) | Multicast address transmission method and device | |
WO2013168737A1 (en) | Communication system, control device, communication method, and program | |
US10498667B2 (en) | Multicast based on bit indexed explicit replication | |
EP3226491A1 (en) | Hot root standby support for multicast | |
CN106656524A (en) | Transmission method, apparatus and system of BIER control information | |
US9344382B2 (en) | Multicast support for internet protocol version four residual deployment via encapsulation or translation | |
EP2989755B1 (en) | Efficient multicast delivery to dually connected (vpc) hosts in overlay networks | |
WO2017117956A1 (en) | Information transmission method and device | |
WO2010111956A1 (en) | Method and system for multicast-forwarding-path convergence | |
CN104253698B (en) | The processing method and equipment of message multicast | |
EP4191966A1 (en) | Method and device for processing data message, storage medium, and electronic device | |
US10567180B2 (en) | Method for multicast packet transmission in software defined networks | |
WO2022117018A1 (en) | Packet transmission method and apparatus | |
CN104468139B (en) | A kind of multicast data packet forwarding method and apparatus | |
US9641649B2 (en) | IGMP/MLD translation | |
CN108199960B (en) | Multicast data message forwarding method, entrance routing bridge, exit routing bridge and system | |
US20200106628A1 (en) | Bit forwarding router identifier signaling using protocol independent multicast attribute | |
CN115134290B (en) | Multicast signaling transfer 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 |