CN108234358B

CN108234358B - Multicast message transmission method, device and machine readable storage medium

Info

Publication number: CN108234358B
Application number: CN201711471523.4A
Authority: CN
Inventors: 徐步正; 章靠; 裘锦晶
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2017-12-29
Filing date: 2017-12-29
Publication date: 2021-09-21
Anticipated expiration: 2037-12-29
Also published as: CN108234358A

Abstract

The present disclosure provides a multicast message transmission method, apparatus and machine-readable storage medium, the method comprising: sending an IGMP query message to convergence layer equipment connected with a standby BRAS (broadband remote access server), so that the convergence layer equipment sends an IGMP report message to the standby BRAS according to the IGMP query message; after receiving an IGMP report message, establishing a multicast table item according to the IGMP report message; if the main BRAS does not have a fault, refusing to forward the multicast message through the multicast list item; and if the main BRAS has a fault, forwarding the multicast message through the multicast list item. According to the technical scheme disclosed by the invention, after the main BRAS fails, the standby BRAS does not need to reestablish the multicast list item, the multicast message can be directly forwarded, the transmission interruption of the multicast message is avoided, the user experience is improved, and the multicast service can be quickly recovered after the main BRAS is switched over.

Description

Multicast message transmission method, device and machine readable storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a multicast packet transmission method, an apparatus, and a machine-readable storage medium.

Background

A BRAS (Broadband Remote Access Server) is an Access gateway facing Broadband network application, is located at an edge layer of a backbone network, and mainly completes network bearing functions and control implementation functions (such as authentication, charging and management). In order to improve the reliability of the BRAS, a dual-backup network is usually adopted, that is, two BRASs are deployed, one BRAS is a primary BRAS, and the other BRAS is a standby BRAS.

Disclosure of Invention

The present disclosure provides a multicast packet transmission method, applied to a BRAS, the method including:

when the BRAS is a standby BRAS, sending an IGMP query message to convergence layer equipment connected with the standby BRAS so that the convergence layer equipment sends an IGMP report message to the standby BRAS according to the IGMP query message;

after receiving an IGMP report message, establishing a multicast table item according to the IGMP report message;

if the main BRAS does not have a fault, refusing to forward the multicast message through the multicast list item;

and if the main BRAS has a fault, forwarding the multicast message through the multicast list item.

The present disclosure provides a multicast message transmission device, applied to a BRAS, the device includes: the system comprises a sending module, an establishing module and a processing module, wherein when the BRAS is a backup BRAS:

the sending module is used for sending an IGMP query message to convergence layer equipment connected with the standby BRAS so that the convergence layer equipment sends an IGMP report message to the standby BRAS according to the IGMP query message;

the establishing module is used for establishing a multicast table item according to the IGMP report message after receiving the IGMP report message;

the processing module is used for refusing to forward the multicast message through the multicast list item when the main BRAS does not have a fault; and when the main BRAS has a fault, forwarding the multicast message through the multicast list item.

The present disclosure provides an electronic device, including: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute the machine-executable instructions to perform the method steps 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 perform the method steps described above.

Based on the technical scheme, in the embodiment of the disclosure, the standby BRAS establishes a multicast table item in advance, and if the main BRAS fails, the multicast message is refused to be forwarded through the multicast table item, so that the situation that the main BRAS and the standby BRAS both send the multicast message and the host receives two identical multicast messages is avoided. If the main BRAS has a fault, the multicast message is forwarded through the multicast list item, and because the multicast list item is established before the fault of the main BRAS, the multicast message can be directly forwarded without reestablishing the multicast list item after the fault of the main BRAS, thereby avoiding the transmission interruption of the multicast message, improving the user experience, and quickly recovering the multicast service after the main BRAS is switched over.

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 packet transmission method according to an embodiment of the present disclosure;

fig. 3 is a structural diagram of a multicast packet transmission apparatus according to an embodiment of the present disclosure;

fig. 4 is a hardware configuration diagram of a backup BRAS in an 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".

When the main BRAS is not in fault, after receiving an IGMP (Internet Group Management Protocol) report message sent by a host, the convergence layer equipment sends the IGMP report message to the main BRAS, but does not send the IGMP report message to the standby BRAS, and the main BRAS establishes a multicast table item of the host according to the IGMP report message and sends the multicast message to the host by using the multicast table item.

However, when the main BRAS fails, the convergence layer device needs to send the IGMP report message to the standby BRAS again, and the standby BRAS establishes a multicast entry of the host according to the IGMP report message and sends the multicast message to the host by using the multicast entry. And before the backup BRAS establishes the multicast list item, the backup BRAS cannot send the multicast message to the host, so that the transmission of the multicast message is interrupted, and the user experience is influenced.

In view of the above discovery, the present disclosure provides a multicast packet transmission method, which may be applied to a dual-backup network, where two or more BRAS may be deployed in the dual-backup network, one BRAS is a primary BRAS, and other BRAS except the primary BRAS are all standby BRASs.

Referring to fig. 1, which is a schematic view of an application scenario of the embodiment of the present disclosure, in fig. 1, two BRAS are taken as an example for description, and in practical applications, the number of BRAS may be more.

In fig. 1, the host may be any type of device, such as an IPTV (Internet Protocol Television) device, a PC (Personal Computer), and a terminal device, which are not limited thereto. The access layer device may be any device of the access layer, such as an access layer switch, without limitation. The convergence layer device may be any device of the convergence layer, such as a convergence layer switch, without limitation. The core layer device may be any device of the core layer, such as a core layer router, without limitation.

Referring to fig. 1, in the two BRAS, one BRAS is a primary BRAS, the other BRAS is a secondary BRAS, and a BRAS101 is a primary BRAS, and a BRAS102 is a secondary BRAS, which are taken as examples for description.

In one example, the primary BRAS is elected as an IGMP querier, and the secondary BRAS is not elected as an IGMP querier, which is not described in detail herein. Based on the working principle of the IGMP querier, the primary BRAS elected as the IGMP querier can send the IGMP query message. After receiving the IGMP query packet through the port 1111, the convergence layer device 111 sets the port 1111 as a router port. Since no IGMP query message is received via port 1112, port 1112 is not set to a router port.

In order to join the multicast group G, each host may send an IGMP report message (e.g., an IGMP membership report message), and the IGMP report message may carry the multicast group G and indicate that the host belongs to the multicast group G.

After receiving the IGMP report packet, the access layer device 121 sends the IGMP report packet to the convergence layer device 111. After receiving the IGMP report packet, the convergence layer device 111 queries the router port from the local, that is, the port 1111, and sends the IGMP report packet through the queried port 1111.

After receiving the IGMP report packet through the port 1011, the primary BRAS may establish a multicast entry according to the IGMP report packet, for example, the multicast entry may include a correspondence between the multicast group G and the port 1011, and based on the multicast entry, the multicast packet for the multicast group G may be forwarded through the port 1011.

If the main BRAS fails, the standby BRAS is elected as a new IGMP querier, and the specific election process is not repeated. Based on the working principle of the IGMP querier, the backup BRAS elected as the IGMP querier can send the IGMP enquiry message. After receiving the IGMP query message through port 1112, the convergence layer device 111 may set the port 1112 as a router port. In addition, after receiving the IGMP report packet, the convergence layer device 111 may also send the IGMP report packet through the router port (i.e., the port 1112). After receiving the IGMP report message through the port 1021, the backup BRAS establishes a multicast entry according to the IGMP report message, and if the multicast entry includes a correspondence between a multicast group G and the port 1021, the multicast packet for the multicast group G may be forwarded through the port 1021 based on the multicast entry.

Obviously, before the backup BRAS establishes the multicast table entry, the backup BRAS cannot send the multicast message to the host, so that the transmission of the multicast message is interrupted, and the user experience is influenced. That is, in the dual-backup network, when the primary BRAS and the backup BRAS are switched, there is a problem of long-time traffic interruption.

For the above discovery, referring to fig. 2, the flow chart of the multicast packet transmission method provided in this embodiment may be applied to a BRAS, and when the BRAS is a backup BRAS, the method may include:

step 201, sending an IGMP query message to a convergence layer device connected to a standby BRAS, so that the convergence layer device sends an IGMP report message to the standby BRAS according to the IGMP query message.

In one example, whether the primary BRAS fails or not, the secondary BRAS may determine itself as an IGMP querier, and send an IGMP query message to a convergence layer device connected to the secondary BRAS through the IGMP querier. Thus, after receiving the IGMP query message, the convergence layer device may set a receiving port of the IGMP query message as a router port. And after receiving the IGMP report message, the convergence layer device may send the IGMP report message to the backup BRAS through the router port.

Each BRAS (such as a primary BRAS and a standby BRAS) of the dual-backup network can determine itself as an IGMP querier, that is, multiple IGMP queriers are allowed to exist simultaneously. Therefore, based on the working principle of the IGMP querier, the main BRAS and the standby BRAS can both send IGMP query messages.

In order to make each BRAS of the dual-backup network determine itself as an IGMP querier, the following method may be adopted: and issuing a first configuration for each BRAS of the dual-computer backup network, wherein the first configuration is used for enabling each BRAS to elect the BRAS as an IGMP (Internet group management protocol) querier, so that the main BRAS can elect the BRAS as the IGMP querier according to the first configuration, and the standby BRAS can elect the BRAS as the IGMP querier according to the first configuration. Or, issuing a second configuration for each BRAS of the dual-backup network, where the second configuration is used to make each BRAS not perform election of the IGMP querier, so that the primary BRAS may not perform election of the IGMP querier based on the second configuration, the primary BRAS automatically becomes the IGMP querier, and the backup BRAS may also not perform election of the IGMP querier based on the second configuration, and the backup BRAS automatically becomes the IGMP querier.

Referring to fig. 1, both the primary BRAS and the secondary BRAS are IGMP queriers, based on the working principle of the IGMP querier, the primary BRAS may send an IGMP query message, for example, periodically send an IGMP query message, and the secondary BRAS may also send an IGMP query message, for example, periodically send an IGMP query message.

After receiving the IGMP query packet sent by the primary BRAS through the port 1111, the convergence layer device 111 may set the port 1111 as a router port. After receiving the IGMP query message sent by the backup BRAS through the port 1112, the convergence layer device 111 may set the port 1112 as a router port.

Further, in order to join the multicast group G, each host (e.g., host 141, host 142, host 143, etc.) may send an IGMP report message (e.g., an IGMP membership report message, etc.), and the IGMP report message may carry the multicast group G and indicate that the host belongs to the multicast group G. After receiving the IGMP report message, the access layer device 121 may send the IGMP report message to the convergence layer device 111.

After receiving the IGMP report message, the convergence layer device 111 queries the router port from the local, that is, the port 1111 and the port 1112, so that the convergence layer device 111 can send the IGMP report message through the queried port 1111 and the port 1112, respectively. That is, the convergence layer device 111 may send IGMP report messages to the primary BRAS and may send IGMP report messages to the secondary BRAS.

Step 202, after receiving the IGMP report message, establishing a multicast entry according to the IGMP report message.

In an example, after receiving the IGMP report packet, the primary BRAS may establish a multicast entry according to the IGMP report packet, where the multicast entry is used to record a corresponding relationship between a multicast group and an egress port. In addition, after receiving the IGMP report message, the backup BRAS may also establish a multicast entry according to the IGMP report message, where the multicast entry is used to record a corresponding relationship between a multicast group and an egress port.

Referring to fig. 1, after receiving an IGMP report packet through a port 1011, a primary BRAS establishes a multicast entry according to the IGMP report packet, where the multicast entry includes a correspondence between a multicast group G and the port 1011, and based on the multicast entry, a multicast packet for the multicast group G may be forwarded through the port 1011. In addition, after receiving the IGMP report message through the port 1021, the backup BRAS establishes a multicast entry according to the IGMP report message, and if the multicast entry includes a correspondence between the multicast group G and the port 1021, the multicast message of the multicast group G may be forwarded through the port 1021 based on the multicast entry.

Step 203, after receiving the multicast message, if the primary BRAS is not in fault, refusing to forward the multicast message through the multicast entry, and if the primary BRAS is in fault, forwarding the multicast message through the multicast entry.

Referring to fig. 1, if the primary BRAS does not fail, after receiving the multicast packet, the primary BRAS may send the multicast packet through a multicast entry established by the primary BRAS. For example, if the multicast packet corresponds to a multicast group G, the primary BRAS may query the multicast table entry through the multicast group G to obtain an egress port, i.e., port 1011, corresponding to the multicast group G, and therefore the primary BRAS sends the multicast packet through the port 1011.

If the main BRAS does not have a fault, the standby BRAS can refuse to send the multicast message through the multicast list item established by the standby BRAS after receiving the multicast message, and can directly discard the multicast message.

As shown in fig. 1, if the primary BRAS fails, the primary BRAS cannot process the multicast packet. After the backup BRAS receives the multicast message, because the primary BRAS has failed, the multicast message can be sent through the multicast list item established by the backup BRAS. For example, if the multicast packet corresponds to the multicast group G, the backup BRAS may query the multicast entry through the multicast group G to obtain an egress port, i.e., port 1021, corresponding to the multicast group G, and therefore, the backup BRAS sends the multicast packet through the port 1021.

In one example, if the backup BRAS knows that the primary BRAS is not in fault, the backup BRAS does not switch its role, that is, the backup BRAS is still the backup BRAS, and therefore, after receiving the multicast packet, the backup BRAS refuses to send the multicast packet, but directly discards the multicast packet. In addition, if the backup BRAS knows that the primary BRAS has a fault, the backup BRAS can switch the role of the backup BRAS, that is, the backup BRAS is switched to a new primary BRAS, and the original primary BRAS is switched to a new secondary BRAS.

With continued reference to fig. 1, if host 141, host 142, and host 143 join multicast group G:

in one example, when a primary BRAS/a backup BRAS sends a multicast message, 3 multicast messages, which are respectively called multicast message 1, multicast message 2 and multicast message 3, may be copied; then, the primary BRAS/backup BRAS sends multicast message 1 for host 141, multicast message 2 for host 142, and multicast message 3 for host 143. After receiving the multicast message 1, the multicast message 2, and the multicast message 3, the convergence layer device 111 sends all the multicast message 1, the multicast message 2, and the multicast message 3 to the access layer device 121. After receiving multicast packet 1, multicast packet 2, and multicast packet 3, access layer device 121 sends multicast packet 1 to host 141, multicast packet 2 to host 142, and multicast packet 3 to host 143.

In another example, when the primary BRAS/secondary BRAS sends a multicast packet, only one multicast packet may be sent, for example, a Virtual Local Area Network (VLAN) is encapsulated for the multicast packet, and then the primary BRAS/secondary BRAS sends the multicast packet carrying the multicast VLAN. After receiving the multicast packet, the convergence layer device 111 sends the multicast packet to the access layer device 121. After receiving the multicast packet, the access layer device 121 may send the multicast packet to the host 141, the host 142, and the host 143 corresponding to the multicast VLAN because the multicast packet encapsulates the multicast VLAN.

Based on the technical scheme, in the embodiment of the disclosure, the standby BRAS establishes a multicast table item in advance, and if the main BRAS fails, the multicast message is refused to be forwarded through the multicast table item, so that the situation that the main BRAS and the standby BRAS both send the multicast message and the host receives two identical multicast messages is avoided. If the main BRAS has a fault, the multicast message is forwarded through the multicast list item, and because the multicast list item is established before the fault of the main BRAS, the multicast message can be directly forwarded without reestablishing the multicast list item after the fault of the main BRAS, thereby avoiding the transmission interruption of the multicast message, improving the user experience and realizing the rapid recovery of the multicast service after the main/standby switching under the dual-machine networking.

In the above embodiment, it may be known for each BRAS (e.g., BRAS101 and BRAS102) whether the BRAS is a primary BRAS or a secondary BRAS, where in fig. 1, BRAS101 is a primary BRAS and BRAS102 is a secondary BRAS. To implement this procedure, in one example, a configuration command may be sent to the BRAS indicating that the BRAS is either a primary BRAS or a backup BRAS. For example, a configuration command 1 may be sent to BRAS101, where configuration command 1 is used to indicate that BRAS101 is a primary BRAS, so that BRAS101 may determine itself as the primary BRAS. A configuration command 2 may be sent to the BRAS102, where the configuration command 2 is used to indicate that the BRAS102 is a standby BRAS, so that the BRAS102 may determine itself as a standby BRAS.

In another example, a BRAS may obtain an identifier of another BRAS from an IGMP query message sent by another BRAS, and may determine that the BRAS is a primary BRAS or a standby BRAS according to the identifier of the BRAS and the identifiers of the other BRASs. Further, the BRAS determines that the BRAS is a primary BRAS or a backup BRAS according to the identifier of the BRAS and the identifiers of other BRASs, which may include but is not limited to:

in a first mode, if the identifier of the BRAS is the minimum identifier, the BRAS can be determined to be a main BRAS; if the identifier of the BRAS is not the minimum identifier, the BRAS can be determined to be the backup BRAS.

In a second mode, if the identifier of the BRAS is the maximum identifier, the BRAS can be determined to be a main BRAS; if the identifier of the BRAS is not the maximum identifier, the BRAS can be determined to be the backup BRAS.

Wherein, the above-mentioned identification may include but is not limited to: an IP address; or, a MAC (Media Access Control) address. In the following process, an IP address is taken as an example for explanation.

Referring to fig. 1, BRAS101 may send an IGMP query message, and after receiving the IGMP query message, convergence layer device 111 sends the IGMP query message to BRAS 102. After receiving the IGMP query message, BRAS102 resolves the IP address of BRAS101 from the IGMP query message. Then, BRAS102 compares its own IP address with the IP address of BRAS101, and if the IP address of BRAS102 is greater than the IP address of BRAS101, it is determined that BRAS102 is the backup BRAS, taking the above-mentioned manner as an example.

Referring to fig. 1, BRAS102 may send an IGMP query message, and after receiving the IGMP query message, convergence layer device 111 sends the IGMP query message to BRAS 101. After receiving the IGMP query message, BRAS101 resolves the IP address of BRAS102 from the IGMP query message. Then, BRAS101 compares its own IP address with the IP address of BRAS102, and if the IP address of BRAS102 is greater than the IP address of BRAS101, it is determined that BRAS101 is the primary BRAS, as an example.

To this end, BRAS102 determines itself to be a backup BRAS, and BRAS101 determines itself to be a primary BRAS.

In the above embodiment, the backup BRAS may also know whether the primary BRAS fails, and if the primary BRAS fails, refuse to forward the multicast packet through the multicast entry, and if the primary BRAS fails, forward the multicast packet through the multicast entry. The learning mode for whether the primary BRAS fails includes:

in the first case, the standby BRAS may detect whether the primary BRAS fails according to an established BFD (Bidirectional Forwarding Detection) session associated with the IGMP, that is, detect that the primary BRAS fails or does not fail. Wherein the BFD session is a BFD session between the standby BRAS and the primary BRAS. For example, the BFD session established between the standby BRAS and the primary BRAS by the primary BRAS may be also established between the standby BRAS and the primary BRAS by the secondary BRAS.

The BFD may be a bidirectional forwarding detection mechanism, which may implement rapid detection of a fault, and may be linked with an upper layer protocol (for example, the upper layer protocol may be IGMP). Specifically, a BFD session may be established between the secondary BRAS and the primary BRAS, for example, a BFD session may be established between the secondary BRAS, the convergence layer device 111, and the primary BRAS, and the BFD session establishment procedure is not limited. And then, BFD detection is carried out between the backup BRAS and the main BRAS for establishing the BFD session, and the detection process is not limited.

The standby BRAS can comprise a BFD module for realizing a BFD function and an IGMP module for realizing a multicast function, if the BFD module detects that the main BRAS fails, the IGMP module is notified, and when the IGMP module senses that the main BRAS fails, the multicast message can be forwarded through the multicast table entry. If the BFD module detects that the main BRAS is not in fault, the BFD module informs the IGMP module, and the IGMP module can refuse to forward the multicast message through the multicast table entry when sensing that the main BRAS is not in fault.

Since the upper layer protocol is IGMP, the BFD session is referred to as an IGMP-associated BFD session.

And in the second situation, after sensing that the self network side port has a fault, the main BRAS sends an IGMP query message carrying the specific identifier to the standby BRAS. And if the backup BRAS receives the IGMP query message sent by the main BRAS and the IGMP query message carries the specific identifier, determining that the main BRAS has a fault.

Referring to fig. 1, after sensing that a network-side port (e.g., port 1012) has a fault (e.g., port DOWN), the primary BRAS may send an IGMP query message through port 1011, where the IGMP query message carries a Max Resp Time field, and a value of the Max Resp Time field is a specific identifier (e.g., full F). After receiving the IGMP query message sent by the primary BRAS, the backup BRAS can determine that the primary BRAS fails because the IGMP query message carries the specific identifier.

The network-side port of the primary BRAS may be an upstream port of the primary BRAS, that is, a port connected to the core layer device 131.

After sensing that a network-side port is faulty, the primary BRAS indicates that the primary BRAS cannot receive a multicast packet sent by the core layer device 131, and therefore, an IGMP query packet may be sent through the port 1011, where the IGMP query packet carries a specific identifier. Therefore, the backup BRAS can determine that the main BRAS fails, upgrade the backup BRAS to a new main BRAS and forward the multicast message through the multicast list item.

Based on the same concept as the foregoing method, an embodiment of the present disclosure further provides a multicast packet transmission apparatus, which may be applied to a BRAS, as shown in fig. 3, where the apparatus is a structure diagram of the apparatus, the apparatus may include a sending module 301, an establishing module 302, and a processing module 303, and when the BRAS is a backup BRAS:

the sending module 301 is configured to send an IGMP query message to a convergence layer device connected to a standby BRAS, so that the convergence layer device sends an IGMP report message to the standby BRAS according to the IGMP query message;

the establishing module 302 is configured to, after receiving an IGMP report packet, establish a multicast entry according to the IGMP report packet;

the processing module 303 is configured to, when the primary BRAS does not fail, refuse to forward the multicast packet through the multicast entry; and when the main BRAS has a fault, forwarding the multicast message through the multicast list item.

The processing module 303 is further configured to detect whether the primary BRAS fails according to the established BFD session associated with the IGMP; wherein the BFD session is a BFD session between the secondary BRAS and the primary BRAS.

In one example, the multicast packet forwarding apparatus further includes (not shown in fig. 3): the determining module is used for acquiring the identifiers of other BRASs from IGMP query messages sent by other BRASs; determining the BRAS as a main BRAS or a standby BRAS according to the identification of the BRAS and the identifications of other BRASs;

when the BRAS is determined to be a main BRAS or a standby BRAS according to the identifier of the BRAS and the identifiers of other BRASs, if the identifier of the BRAS is the minimum identifier, the BRAS is determined to be the main BRAS; if the identifier of the BRAS is not the minimum identifier, determining the BRAS as a backup BRAS; or, if the identifier of the BRAS is the maximum identifier, determining the BRAS as the main BRAS; if the identifier of the BRAS is not the maximum identifier, determining the BRAS as a backup BRAS;

wherein, the identifier is specifically: an IP address; alternatively, a MAC address.

The processing module 303 is further configured to determine that the primary BRAS has a fault when an IGMP query message sent by the primary BRAS is received and the IGMP query message carries a specific identifier; and the IGMP query message is sent by the main BRAS after sensing that the own network side port has a fault.

When the BRAS is a primary BRAS, the sending module 301 is configured to send, after sensing that a network side port of the primary BRAS has a fault, an IGMP query message carrying a specific identifier to the secondary BRAS, so that the secondary BRAS determines that the primary BRAS has the fault according to the specific identifier of the IGMP query message.

In the embodiment of the present disclosure, an electronic device (i.e., the backup BRAS) is provided, and from a hardware level, a schematic diagram of a hardware architecture may be as shown in fig. 4. The method comprises the following steps: a machine-readable storage medium and a processor, wherein:

a machine-readable storage medium: storing machine executable instructions executable by the processor.

A processor: the machine-executable instructions stored in the machine-readable storage medium are read and executed to realize the multicast message transmission operation disclosed in the above example of the present disclosure.

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

1. A method for multicast message transmission, applied to a BRAS, the method comprising:

if the main BRAS has a fault, forwarding a multicast message through the multicast list item;

if an IGMP query message sent by the main BRAS is received and the IGMP query message carries a specific identifier, determining that the main BRAS has a fault; wherein, the IGMP query message is sent by the primary BRAS after sensing that a failure occurs on its own network side port.

2. The method of claim 1, further comprising:

detecting whether the main BRAS has a fault according to the established BFD session associated with the IGMP;

wherein the BFD session is a BFD session between the secondary BRAS and the primary BRAS.

3. The method of claim 1, further comprising:

acquiring the identifiers of other BRASs from IGMP query messages sent by other BRASs; and determining the BRAS as a main BRAS or a standby BRAS according to the identifier of the BRAS and the identifiers of other BRASs.

4. The method of claim 3, wherein the determining that the BRAS is a primary BRAS or a backup BRAS according to the identifier of the BRAS and the identifiers of other BRASs comprises:

if the identifier of the BRAS is the minimum identifier, determining the BRAS as a main BRAS; if the identifier of the BRAS is not the minimum identifier, determining the BRAS as a backup BRAS; alternatively, the first and second electrodes may be,

if the identifier of the BRAS is the maximum identifier, determining the BRAS as a main BRAS; if the identifier of the BRAS is not the maximum identifier, determining the BRAS as a backup BRAS;

5. The method of claim 1, further comprising:

when the BRAS is a main BRAS, after sensing that a network side port of the BRAS has a fault, sending an IGMP query message carrying a specific identifier to the standby BRAS, so that the standby BRAS determines that the main BRAS has the fault according to the specific identifier of the IGMP query message.

6. A multicast message transmission apparatus, for use in a BRAS, the apparatus comprising: the system comprises a sending module, an establishing module and a processing module, wherein when the BRAS is a backup BRAS:

the processing module is used for refusing to forward the multicast message through the multicast list item when the main BRAS does not have a fault; when the main BRAS has a fault, the multicast message is forwarded through the multicast list item;

the processing module is further configured to determine that the primary BRAS has a fault when an IGMP query message sent by the primary BRAS is received and the IGMP query message carries a specific identifier; and the IGMP query message is sent by the main BRAS after sensing that the own network side port has a fault.

7. The apparatus of claim 6, wherein the processing module is further configured to detect whether the primary BRAS fails according to the established BFD session associated with IGMP; wherein the BFD session is a BFD session between the secondary BRAS and the primary BRAS.

8. The apparatus of claim 6, further comprising: the determining module is used for acquiring the identifiers of other BRASs from IGMP query messages sent by other BRASs; determining the BRAS as a main BRAS or a standby BRAS according to the identification of the BRAS and the identifications of other BRASs;

9. The apparatus of claim 6, wherein when the BRAS is a primary BRAS, the sending module is configured to send, after sensing that a network-side port of the primary BRAS has a fault, an IGMP query packet with a specific identifier to the secondary BRAS, so that the secondary BRAS determines that the primary BRAS has a fault according to the specific identifier of the IGMP query packet.

10. An electronic device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute the machine-executable instructions to perform the method steps of any of claims 1-5.

11. 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.