Edge device communication processing method and system, electronic device and storage medium

Abstract

The invention provides an edge device communication processing method and system, electronic equipment and a storage medium. The method comprises the steps that a multicast receiving end PE monitors first state information of a locally-stored virtual routing forwarding table in real time, and a multicast sending end PE monitors second state information of the locally-stored virtual routing forwarding table in real time; the multicast receiving end PE packages the first state information through a border gateway protocol module to obtain routing information, and sends the routing information to the multicast sending end PE; and the multicast sending end PE determines whether to establish communication connection with the multicast receiving end PE according to the routing information and the second state information. The purpose of quickly cutting off multicast traffic in batches is achieved, and forwarding of redundant traffic in a backbone network is reduced.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an edge device communication processing method, system, electronic device and storage medium. Background Art

[0002] With the widespread application of BGP / MPLS IP VPN in existing networks and the development of multicast services such as IPTV, video conferencing, and distance education, service providers have more needs to run multicast services on BGP / MPLS IP VPN networks. Multicast VPN enables multicast services on existing BGP / MPLS IP VPNs and transmits private network data traffic to VPN remote sites through the public network. NG-MVPN establishes a private network neighbor relationship between network edge devices (Provider Edge, PE) and PE to transmit multicast protocol packets and implement data forwarding. When the multicast interface on the private network side fails, it is necessary to wait for the BGP Update message to transmit the pruning message to prune the multicast tunnel interface of the multicast sender provider edge device (Sender PE). As a result, multicast traffic is still forwarded to the MPLS domain for a period of time.

[0003] At present, NG-MVPN is to establish a multicast neighbor relationship based on a private network between PEs and establish a multicast neighbor through a special MVPN tunnel interface. After the neighbor is established, the multicast PIM (Protocol Independent Multicast) neighbor of the tunnel interface will never time out, which will cause the Sender PE to be unable to perceive the interface changes of the multicast receiving operator edge device (Receiver PE). When the receiver of the Receiver PE fails, the multicast outbound interface on the Receiver PE is deleted, and the pruning message is sent to the Sender PE with the help of the BGP Update message. Only when the Sender PE receives the message will it delete the outbound interface in the multicast forwarding table and the multicast traffic will be cut off.

[0004] The PIM neighbors between PEs of NG-MVPN never time out, and the outbound interface cannot be deleted through fast PIM neighbor perception. If the private network PIM interface fails, it is necessary to wait for BGP Update messages to delete the outbound interfaces of the upstream PE one by one. At this time, multicast traffic will be forwarded to the MPLS domain for a period of time, and the outbound interfaces of the upstream PE cannot be deleted in batches and quickly, resulting in a waste of network bandwidth. Summary of the invention

[0005] The purpose of this application is to provide an edge device communication processing method, system, electronic device and storage medium to improve the efficiency of handling faults in view of the deficiencies in the above-mentioned prior art.

[0006] To achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0007] In a first aspect, an embodiment of the present application provides an edge device communication processing method, the method comprising:

[0008] The multicast receiving end PE monitors the first state information of the locally stored virtual routing forwarding table in real time, and the multicast sending end PE monitors the second state information of the locally stored virtual routing forwarding table in real time, wherein the first state information and the second state information respectively include: a normal state or a fault state;

[0009] The multicast receiving end PE encapsulates the first state information through a border gateway protocol BGP module to obtain routing information, and sends the routing information to the multicast sending end PE;

[0010] The multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the routing information and the second state information.

[0011] Optionally, the multicast receiving end PE monitors the first state information of the locally stored virtual routing forwarding table in real time, including:

[0012] The multicast receiving end PE monitors the status information of the connection interface on each network device connected to the multicast receiving end PE in the virtual routing forwarding table in real time;

[0013] The first state information is determined according to the state information of the connection interface on each network device connected to the multicast receiving end PE.

[0014] Optionally, the first state information is determined based on the state information of the connection interface on each network device connected to the multicast receiving end PE, including:

[0015] If the status information of the connection interfaces on all network devices connected to the multicast receiving end PE are all in a fault state, it is determined that the first status information is in a fault state; otherwise, it is determined that the first status information is in a normal state.

[0016] Optionally, the multicast receiving end PE encapsulates the first state information through a border gateway protocol BGP module to obtain routing information, and sends the routing information to the multicast sending end PE, including:

[0017] The BGP module encapsulates the first state information, the identifier of the multicast tunnel interface and the routing identifier to obtain the routing information, wherein the source address of the routing information is the address of the multicast receiving end PE, and the destination address of the routing information is the address of the multicast sending end PE;

[0018] The routing information is sent to the multicast sending end PE according to the source address and the destination address.

[0019] Optionally, the multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the routing information and the second state information, including:

[0020] The multicast sending end PE parses the routing information to obtain the first state information, the routing identifier and the identifier of the multicast tunnel interface;

[0021] The multicast sending end PE matches the corresponding virtual routing forwarding table stored by the multicast sending end PE according to the routing identifier and obtains the second state information of the virtual routing forwarding table;

[0022] The multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information.

[0023] Optionally, the multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information, including:

[0024] If the value in the first state information is a first preset value, the multicast transmitting end PE determines whether the value in the second state information is consistent with the first preset value, and the first preset value is used to indicate that the state of the virtual routing forwarding table of the multicast receiving end PE is normal;

[0025] If they are consistent, a communication connection between the multicast sending end PE and the multicast receiving end PE is established.

[0026] Optionally, the multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information, including:

[0027] If the value in the first state information is a second preset value, the multicast transmitting end PE disconnects the communication connection with the multicast receiving end PE, and the second preset value is used to indicate that the state of the virtual routing forwarding table of the multicast receiving end PE is a fault state.

[0028] In a second aspect, an embodiment of the present application further provides an edge device communication processing system, the system receiving end PE and sending end PE, wherein:

[0029] The receiving end PE is used to execute the method steps executed by any receiving end PE in the first aspect above; the sending end PE is used to execute the method steps executed by any sending end PE in the first aspect above.

[0030] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, and when the application is running, the processor communicates with the storage medium through the bus, and the processor executes the program instructions to execute the method steps executed by the receiving end PE or the method steps executed by the sending end PE described in the first aspect above.

[0031] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program is read and executes the method steps executed by the receiving end PE or the method steps executed by the sending end PE described in the first aspect above.

[0032] The beneficial effects of this application are:

[0033] The present application provides an edge device communication processing method, system, electronic device and storage medium, which respectively monitors the state information of the virtual routing forwarding table stored in each device at the multicast receiving end PE and the multicast sending end PE, and the multicast receiving end PE encapsulates the monitored first state information through the border gateway protocol module to generate routing information and sends the routing information to the multicast sending end PE, so that the multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the received routing information and the state information of the virtual routing forwarding table monitored by itself, so that when the multicast receiving end PE fails, the group can be directly The private network multicast neighbor in the multicast sending end PE is deleted, that is, the multicast receiving end PE in the multicast sending end PE is directly deleted, so as to achieve the effect of synchronously deleting all connection interfaces in the multicast forwarding table, and achieve the purpose of batch fast cutting off multicast traffic, reduce the forwarding of redundant traffic in the backbone network, avoid the need to wait for the multicast sending end PE to delete each outbound interface of the multicast sending end PE one by one in the prior art, and the multicast traffic can be cut off, which can reduce the waste of network bandwidth; at the same time, by real-time monitoring the status information of each virtual forwarding routing table on each device, the change of the status of the virtual forwarding routing table can be quickly perceived, and the efficiency of fault handling is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0035] Figure 1 A schematic diagram of the architecture of an edge device communication processing system provided in an embodiment of the present application;

[0036] Figure 2 A flow chart of an edge device communication processing method provided in an embodiment of the present application;

[0037] Figure 3 A flowchart of another edge device communication processing method provided in an embodiment of the present application;

[0038] Figure 4 A flowchart of another edge device communication processing method provided in an embodiment of the present application;

[0039] Figure 5 A structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0041] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0042] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0043] Figure 1 A schematic diagram of the architecture of an edge device communication processing system provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, it includes a multicast sender PE (Sender Provider Edge, sender operator edge device) and a multicast receiver PE (Receiver Provider Edge, receiver operator edge device), wherein the multicast sender PE is an edge device close to the multicast source, taking PE1 as an example, for example, it can be connected to the multicast source network device (for example Figure 1 The multicast receiving end PE is an edge device close to the multicast receiver, taking PE2 as an example, which can communicate with the multicast receiver network device (such as Figure 1 The next generation multicast virtual private network (NG-MVPN) is capable of transmitting private network multicast routing and establishing public network tunnels. Specifically, it can establish a private network multicast neighbor relationship between PE1 and PE2, transmit multicast protocol messages and implement data forwarding.

[0044] like Figure 1 As shown, network devices CE1, CE2 and CE3 are all network devices in the same virtual routing table VRF1. PE1, P and PE2 together form the operator's backbone network. CE1, as a multicast source network device, can forward multicast traffic. CE2 and CE3, as multicast receiver network devices, receive messages from the multicast source network device.

[0045] Optionally, an embodiment of the present application provides a protocol independent multicast (PIM) interface monitoring mechanism in the virtual routing table (Virtual RoutingEdge, VRF) of a PE device. Each PE device in the NG-MVPN environment maintains the PIM neighbor monitoring mechanism. The PE device can enable the PIM function according to the interface under different VRFs, so that the PIM interface status under each VRF can be recorded. Each PE monitors the status of each PIM interface under different VRFs in real time. When the PIM interface under the VRF monitored by the multicast receiving end PE fails, the method provided in the embodiment of the present application is used to delete the private network multicast neighbor of the multicast sending end PE, so as to achieve batch and rapid deletion of the tunnel outbound interface of the multicast sending end PE, thereby reducing the waste of network bandwidth.

[0046] It is worth mentioning that Figure 1 The number of network devices, the number of edge devices, and the number of VRFs shown in are all exemplary, and the embodiments of the present application do not impose specific limitations on this.

[0047] The specific implementation process of the edge device communication processing provided in the embodiment of the present application is explained in detail below.

[0048] Figure 2 The present invention provides a flow chart of an edge device communication processing method provided in an embodiment of the present invention, and the method is applied in the aforementioned application scenario. Figure 2 As shown, the method includes:

[0049] S101. The multicast receiving end PE monitors the first state information of the locally stored virtual routing forwarding table in real time, and the multicast sending end PE monitors the second state information of the locally stored virtual routing forwarding table in real time.

[0050] Optionally, the first state information and the second state information may respectively include: a normal state or a fault state, wherein the normal state can be identified, for example, by a value "1", and the fault state can be identified, for example, by a value "0", or by other methods, and the embodiments of the present application do not impose specific restrictions on this.

[0051] Optionally, at least one virtual routing table may be stored in the multicast receiving PE and the multicast sending PE, respectively, and each virtual routing table stores the status information of the interfaces enabled with the PIM function and each interface enabled with the PIM function. For example, the status information of the virtual routing table may be represented by VRF[i].PIM.status, where i refers to the identifier of each VRF. Figure 1As shown in , PE2 as a multicast receiving end PE can monitor the first state information of VRF1 in the device in real time, and PE1 as a multicast sending end PE can monitor the second state information of VRF1 in the device in real time.

[0052] S102: The multicast receiving end PE encapsulates the first state information through a border gateway protocol module to obtain routing information, and sends the routing information to the multicast sending end PE.

[0053] Among them, the Border Gateway Protocol (BGP) module is mainly used for the interconnection between network autonomous systems, mainly to control the propagation of routes and select the best routes.

[0055] The BGP module can be deployed in the multicast receiving PE or in the multicast sending PE. The BGP module in the multicast receiving PE can obtain the first status information monitored by the device, and the BGP module in the multicast sending PE can obtain the second status information monitored by the device.

[0056] Exemplarily, when the BGP module in PE2 receives the first state information of VRF1, it encapsulates the first state information of VRF1 to obtain routing information, which then contains the first state information of VRF1 of PE2, and sends the routing information containing the first state information of VRF1 of PE2 to PE1.

[0057] S103: The multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the routing information and the second state information.

[0058] Specifically, the multicast transmitter PE may determine whether to establish a communication connection with the multicast receiver PE according to routing information including the first state information of VRF1 monitored by the multicast receiver PE and the second state information of VRF1 monitored by the multicast transmitter PE.

[0059] Among them, whether to establish a communication connection can also be whether to establish a neighbor relationship, that is, the multicast sending end PE determines whether to establish a neighbor relationship with the multicast receiving end PE. Specifically, if the multicast sending end PE determines that the neighbor relationship with the multicast receiving end PE is not established, the neighbor table containing the multicast receiving end PE in the multicast sending end PE can be deleted, that is, the private network multicast neighbor in the multicast sending end PE is deleted; if the neighbor relationship is established, the neighbor table with the multicast receiving end PE in the multicast sending end PE can be re-established, thereby establishing a neighbor relationship with the multicast receiving end PE. Among them, the neighbor table includes the address of the multicast receiving end PE, the tunnel interface and the timer status, wherein the tunnel interface refers to the tunnel interface between the multicast sending end PE and the multicast receiving end PE.

[0060] Exemplarily, when PE1 receives the routing information in S102, PE1 determines whether to establish a communication connection with PE2 according to the routing information including the first state information of VRF1 of PE2 and the second state information of VRF1 monitored by PE1.

[0061] In the embodiment of the present application, by respectively monitoring the state information of the virtual routing table stored in each device at the multicast receiving end PE and the multicast sending end PE, the multicast receiving end PE encapsulates the monitored first state information through the border gateway protocol module to generate routing information and sends the routing information to the multicast sending end PE, so that the multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the received routing information and the state information of the virtual routing table monitored by itself, so that when the multicast receiving end PE fails, the private network multicast neighbor in the multicast sending end PE can be directly deleted, that is, the multicast receiving end PE in the multicast sending end PE is directly deleted, so as to achieve the effect of synchronously deleting all connection interfaces in the multicast forwarding table, so as to achieve the purpose of batch fast cutting off multicast traffic, reduce the forwarding of redundant traffic in the backbone network, avoid the need to wait for the multicast sending end PE to delete each outbound interface of the multicast sending end PE one by one in the prior art, so that the multicast traffic can be cut off, and the waste of network bandwidth can be reduced; in addition, by real-time monitoring the state information of each virtual forwarding routing table on each device, the change of the state of the virtual forwarding routing table can be quickly perceived, and the efficiency of fault handling is improved.

[0062] Figure 3 A flow chart of another edge device communication processing method provided in an embodiment of the present application, such as Figure 3 As shown, the above S101, the multicast receiving end PE monitors the first state information of the locally stored virtual routing forwarding table in real time, which may include:

[0063] S201. The multicast receiving end PE monitors in real time the status information of the connection interface on each network device connected to the multicast receiving end PE in the virtual routing forwarding table.

[0064] Specifically, the multicast receiving end PE can monitor in real time the status information of the connection interfaces on each network device connected to the multicast receiving end PE in the virtual routing forwarding table stored in the multicast receiving end PE. Wherein, each connection interface is enabled with the PIM function, and for the connection interface with the PIM function enabled, the multicast receiving end backbone device can monitor in real time the status information of the connection interface with the PIM function enabled.

[0065] Optionally, the multicast receiving end PE may include multiple virtual routing forwarding tables, and the connection interfaces in each virtual routing table are different. Different virtual routing forwarding tables can represent different data forwarding modes. For example, for PE2, multiple different virtual routing forwarding tables such as VRF1, VRF2 and VRF3 may be included, and the data forwarding modes of VRF1, VRF2 and VRF3 are different. For example, VRF1 includes CE2 and CE3; VRF2 may include CE4; VRF5 may include CE5, CE6 and CE7. Then, the multicast receiving end PE can monitor the status information of each connection interface in each VRF respectively.

[0066] It is worth noting that the network devices and quantities of the multicast receiving ends included in the VRF listed in this embodiment are exemplary and are not limited to this in the embodiments of the present application.

[0067] For example, Figure 1 As shown, the receiver network devices in VRF1 connected to PE2, namely the customer edge devices (Customer Edge, referred to as CE), are CE2 and CE3, and the connection interface between CE2 and PE2 and the connection interface between CE3 and PE2 are both enabled with the PIM function. PE2 can monitor the status information of the connection interface of CE2 and the connection interface of CE3 in VRF1 in real time.

[0068] S202: Determine first status information according to status information of connection interfaces on each network device at the multicast receiving end PE.

[0069] Specifically, the multicast receiving end PE can determine the first state information of each virtual routing forwarding table according to the state information of the connection interface on each network device monitored. The state information of each connection interface can also include a normal state or a fault state, wherein the normal state can be represented by 1, or it can represent that the connection interface is up; the fault state can be represented by 0, or it can represent that the connection interface is down.

[0070] For example, Figure 1The first state information of VRF1 of PE2 shown can be determined based on the state information of the connection interface on CE2 connected to PE2 and the connection interface on CE3 obtained by real-time monitoring.

[0071] Exemplarily, the first status information of other VRFs stored in PE2 may be determined by status information of all connection interfaces included in each VRF.

[0072] Optionally, the above S201-S202 describes the process of determining the first state information of each virtual routing forwarding table of the multicast receiving end PE. The process of determining the second state information of each virtual routing forwarding table of the multicast sending end PE is similar to that of the multicast receiving end PE. With reference to steps S201-S202, the second state information of the virtual routing forwarding table of the multicast sending end PE can be obtained. For example, the attached Figure 1 The second state information of VRF1 stored in PE1 is as follows: Figure 1 As shown, the second state information of VRF1 of PE1 is determined by the state information of the connection interface on CE1 connected to PE1. Figure 1 , the multicast source network device CE1 and the receiver network devices CE2 and CE3 are all devices in the VRF1 routing forwarding table.

[0073] Through the method of this embodiment, the first state information of each virtual routing forwarding table of the multicast receiving end PE and the second state information of each virtual routing forwarding table of the multicast sending end PE can be obtained respectively.

[0074] Optionally, determining the first status information according to the status information of the connection interface on each network device of the multicast receiving end PE in S202 may include:

[0075] Optionally, if the status information of the connection interfaces on all network devices connected to the multicast receiving end PE is a fault state, the first status information is determined to be a fault state; otherwise, the first status information is determined to be a normal state.

[0076] For example, continue with Figure 1 Taking PE2 shown as an example, if the status of the connection interface on CE2 and the connection interface on CE3 are both 0, it means that the first status information of VRF1 on PE2 is 0; if the status of either the connection interface on CE2 or the connection interface on CE3 is 1 or both are 1, it means that the first status information of VRF1 on PE2 is 1.

[0077] Exemplarily, the status information VRF[1].PIM.status of the virtual routing table stored on PE2 is as shown in Table 1:

[0078] VRF Interface Status 1 1 1 1 2 1

[0079] Table 1

[0080] Specifically, according to the above table, VRF[1].PIM.status={interface[1].status}||{interface[2].status}=1 can be obtained, where interface[1].status can be the status information of the connection interface on the CE2 device connected to PE2, and interface[2].status can be the status information of the connection interface on the CE3 device connected to PE2. PE2 monitors that the PIM interface of VRF1 on the local end is normal, and notifies the BGP module of the result 1 of VRF[1].PIM.status.

[0081] Optionally, the second state information of each virtual routing table of the multicast sending end PE is determined in the same manner as the method of the multicast receiving end PE, and the method of the second state information of each virtual routing table of the multicast sending end PE is continued. Figure 1 Taking PE1 in the example, if the state of the connection interface on CE1 is 1, the second state information of VRF1 of PE1 is 1; if the state of the connection interface on CE1 is 0, the second state information of VRF1 of PE1 is 0.

[0082] Optionally, in S102, the multicast receiving end PE encapsulates the first state information through a border gateway protocol module to obtain routing information, and sends the routing information to the multicast sending end PE, which may include:

[0083] Optionally, the border gateway protocol module encapsulates the first state information, the identifier of the multicast tunnel interface and the routing identifier to obtain routing information, wherein the source address of the routing information is the address of the multicast receiving end PE, and the destination address is the address of the multicast sending end PE.

[0084] Among them, the BGP module can encapsulate the first status information into a type of route, and the type of route information is carried in the network layer reachable information field in the BGP update message for transmission, which is used for automatic discovery of MVPN members within the domain. Among them, the attributes in the type of route may include: PMSI_TUNNEL_ATTRIBUTE attribute (multicast tunnel information), MP_REACH_NLRI attribute (routing information), PIM.STATUS attribute (local multicast interface status information), then the multicast tunnel interface identifier, routing identifier and the first status information can be encapsulated into each attribute respectively. Specifically, the multicast tunnel interface identifier can be encapsulated in the PMSI_TUNNEL_ATTRIBUTE attribute, the routing identifier can be encapsulated in the MP_REACH_NLRI attribute, and the value of the first status information can be encapsulated in the PIM.STATUS attribute. The following

[0085] Table 2 is an exemplary list of attributes included in a type of routing.

[0086] TYPE(update message) Path Attribute-PMSI_TUNNEL_ATTRIBUTE(Tunnel id:65536) Path Attribute-MP_REACH_NLRI(Router Distinguisher:20:1) Path Attribute-PIM.STATUS(flag: 1)

[0087] Table 2

[0088] The source address of the BGP message is the IP address of PE2 that sends the first state information, for example, 2.2.2.2, and the destination address is the IP address of PE1, for example, 1.1.1.1. From Table 2, it can be obtained that the identifier of the multicast tunnel interface is 65536, the routing identifier is 20:1, and the flag value is 1, that is, the value in the identifier first state information is 1. The multicast tunnel interface refers to the multicast tunnel interface between PE2 and PE1.

[0089] Optionally, the BGP module may send the routing information to the multicast sending end PE according to the source address and the destination address.

[0090] In this embodiment, the first status information is encapsulated as a type of routing information through the BGP module and sent to the multicast sending end PE. When all the connection interfaces in the virtual routing table of the multicast receiving end PE fail, the BGP module can be immediately triggered to send a routing update message so that the multicast sending end PE synchronously receives the interface status information of the multicast receiving end PE.

[0091] Figure 4 A flow chart of another edge device communication processing method provided in an embodiment of the present application is as follows: Figure 4 As shown, in the above S103, the multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the routing information and the second state information, which may include:

[0092] S301. The multicast transmitting end PE parses routing information to obtain first state information, a routing identifier and an identifier of a multicast tunnel interface.

[0093] S302: The multicast sending end PE matches the corresponding virtual routing forwarding table stored in the multicast sending end PE according to the routing identifier and obtains the second state information of the virtual routing forwarding table.

[0094] Specifically, the corresponding virtual routing table on the multicast sending end PE can be matched according to the routing identifier. For example, VRF1 on PE1 can be matched according to the routing identifier 20:1 in Table 2. At the same time, PE1 can also obtain the second state information of VRF1 of PE1 monitored by the local end; the corresponding tunnel interface can also be obtained as tunnel40960 through the identifier 65536 of the multicast tunnel interface in Table 2.

[0095] S303: The multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information.

[0096] Exemplarily, PE1 may determine whether to establish a communication connection with PE2 by parsing the first state information of VRF1 on PE2 and the second state information of VRF1 on the local PE1.

[0097] Optionally, in S303, the multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information, which may include:

[0098] Optionally, if the value in the first state information is a first preset value, the multicast transmitter PE determines whether the value in the second state information is consistent with the first preset value, and if they are consistent, establishes a communication connection between the multicast transmitter PE and the multicast receiver PE.

[0099] The first preset value may be used to indicate that the state of the virtual routing forwarding table of the multicast receiving end PE is normal, for example, the value of VRF1 on PE2 is 1.

[0100] Optionally, the initial value of VRF on each PE is 0. If the first status information in the routing information sent by the multicast receiving end PE when the multicast sending end PE receives it for the first time is 1, a neighbor relationship is established with the multicast receiving end PE, and the neighbor status timeout timer is set to never time out. After the private network PIM neighbor is successfully established, multicast traffic is forwarded normally. When the multicast receiving end PE monitors that the status of the VRF on this end has changed to 0.

[0101] Exemplarily, if the value of VRF1 in a type of routing information received by PE1 and sent by PE2 through the BGP module is 1, and the value of VRF1 on the local PE1 is found through the routing identifier, if the value of VRF1 on PE1 is also 1, a communication connection between PE1 and PE2 is established, that is, a neighbor relationship with PE2 is established, and the neighbor state timeout timer is set to never time out, as shown in Table 3 below.

[0102] Optionally, a neighbor table of the multicast receiving end PE is also stored on the multicast sending end PE, and the neighbor table includes the address, tunnel interface and timer status of the multicast receiving end PE, such as the following Table 3:

[0103] Neighbor Address Interface Expires 2.2.2.2 Tunnel40960 Never

[0104] Table 3

[0105] Optionally, in S303, the multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information, which may include:

[0106] Optionally, if the value in the first state information is a second preset value, the multicast transmitting end PE disconnects the communication connection with the multicast receiving end PE, wherein the second preset value is used to indicate that the state of the virtual routing forwarding table of the multicast receiving end PE is a fault state.

[0107] Specifically, after the multicast sending end PE establishes a communication connection with the multicast receiving end PE, the multicast traffic is forwarded normally. When the multicast receiving end PE monitors that the value of the virtual routing forwarding table at the local end is 0, the BGP module is notified to immediately send a routing information update message, the source address of which is the address of the multicast receiving end PE, the destination address is the address of the multicast sending end PE, and the first state information carried is 0. After receiving the message, the multicast sending end PE sets the multicast neighbor timer of the tunnel interface under the corresponding virtual routing table in the multicast sending end PE to 0, that is, the multicast receiving end PE in the multicast sending end PE is deleted.

[0108] Optionally, when the multicast sending end PE deletes the multicast receiving end PE in the multicast sending end PE, all outbound interfaces in the virtual routing forwarding table on the multicast sending end PE are deleted. In addition, the multicast sending end PE can also send a pruning message to the multicast source to delete the communication connection between the multicast sending end PE and the multicast source.

[0109] Optionally, after the multicast sending end PE is disconnected from the multicast receiving end PE, when the multicast receiving end PE monitors that the virtual routing table of the local end becomes 1, it notifies the BGP module to immediately send a routing update message carrying the first status information of 1. When the multicast sending end PE receives the message and parses the first status information as 1, it re-establishes the private network multicast neighbor of the tunnel interface in the message, that is, re-establishes the communication connection with the multicast receiving end PE, and sets the timer to never time out.

[0110] In this embodiment, when all the connection interfaces in the virtual routing table of the multicast receiving end PE fail, the BGP module can be immediately triggered to send a routing update message, and the multicast receiving end PE under the corresponding virtual routing table in the multicast sending end PE is directly deleted, so as to achieve the effect of deleting the multicast forwarding table outgoing interface at the same time, and achieve the purpose of batch fast cutting off multicast traffic, thereby reducing the forwarding of redundant traffic in the backbone network and reducing the waste of network bandwidth.

[0111] Optionally, when the enabling function of the connection interface of each network device in the virtual routing forwarding table in the multicast receiving end PE fails, the state of the virtual routing table of the multicast receiving end PE is also a faulty state. At this time, the fault handling is consistent with the fault handling method mentioned above.

[0112] Figure 5A structural block diagram of an electronic device 400 provided in an embodiment of the present application, such as Figure 5 As shown, the electronic device may include: a processor 401 and a memory 402 .

[0113] Optionally, a bus 403 may also be included, wherein the memory 402 is used to store machine-readable instructions executable by the processor 401. When the electronic device 400 is running, the processor 401 communicates with the memory 402 through the bus 403. When the machine-readable instructions are executed by the processor 401, the method steps in the above method embodiment are performed.

[0114] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method steps in the embodiment of the edge device communication processing method are executed.

[0115] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0116] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, RandomAccess Memory), disk or optical disk and other media that can store program code.

[0117] The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be covered by the protection scope of the present application.

Claims

1. A method for edge device communication processing, characterized in that: The method comprises: The multicast receiving end operator edge device PE monitors the first state information of the locally stored virtual routing forwarding table in real time, and the multicast sending end PE monitors the second state information of the locally stored virtual routing forwarding table in real time, wherein the first state information and the second state information respectively include: a normal state or a fault state; The multicast receiving end PE encapsulates the first state information through a border gateway protocol BGP module to obtain routing information, and sends the routing information to the multicast sending end PE; The multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the routing information and the second state information.

2. The edge device communication processing method according to claim 1, characterized in that: The multicast receiving end operator edge device PE monitors the first state information of the locally stored virtual routing forwarding table in real time, including: The multicast receiving end PE monitors the status information of the connection interface on each network device connected to the multicast receiving end itself in the virtual routing forwarding table in real time; The multicast receiving end PE determines the first status information according to the status information of the connection interface on each network device connected to the multicast receiving end itself.

3. The edge device communication processing method according to claim 2, characterized in that: The multicast receiving end PE determines the first state information according to the state information of the connection interface on each network device connected to itself, including: If the status information of the connection interfaces on all network devices connected to the multicast receiving end itself are all in a fault state, then the first status information is determined to be in a fault state; otherwise, the first status information is determined to be in a normal state.

4. The edge device communication processing method according to claim 1, characterized in that: The multicast receiving end PE encapsulates the first state information through a border gateway protocol BGP module to obtain routing information, and sends the routing information to the multicast sending end PE, including: The BGP module of the multicast receiving end PE encapsulates the first state information, the identifier of the multicast tunnel interface and the routing identifier to obtain the routing information, wherein the source address of the routing information is the address of the multicast receiving end PE, and the destination address of the routing information is the address of the multicast sending end PE; The multicast receiving end PE sends the routing information to the multicast sending end PE according to the source address and the destination address.

5. The edge device communication processing method according to claim 1, characterized in that: The multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the routing information and the second state information, including: The multicast sending end PE parses the routing information to obtain the first state information, the routing identifier and the identifier of the multicast tunnel interface; The multicast sending end PE matches the corresponding virtual routing forwarding table stored by the multicast sending end PE according to the routing identifier and obtains the second state information of the virtual routing forwarding table; The multicast sending end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information.

6. The edge device communication processing method according to claim 5, characterized in that: The multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information, including: If the value in the first state information is a first preset value, the multicast transmitting end PE determines whether the value in the second state information is consistent with the first preset value, and the first preset value is used to indicate that the state of the virtual routing forwarding table of the multicast receiving end PE is normal; If they are consistent, the multicast sending end PE establishes a communication connection between the multicast sending end and the multicast receiving end PE.

7. The edge device communication processing method according to claim 5, characterized in that: The multicast transmitting end PE determines whether to establish a communication connection with the multicast receiving end PE according to the first state information and the second state information, including: If the value in the first state information is a second preset value, the multicast transmitting end PE disconnects the communication connection with the multicast receiving end PE, and the second preset value is used to indicate that the state of the virtual routing forwarding table of the multicast receiving end PE is a fault state.

8. An edge device communication processing system, characterized in that: It includes the receiving PE and the sending PE, where: The receiving end PE is used to execute the method steps executed by the receiving end PE in any one of claims 1-7; the sending end PE is used to execute the method steps executed by the sending end PE in any one of claims 1-7.

9. An electronic device, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program executable by the processor, and when the processor executes the computer program, it implements the method steps executed by the receiving end PE or the method steps executed by the sending end PE as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps performed by the receiving end PE or the method steps performed by the sending end PE as described in any one of claims 1 to 7 are executed.

Images