CN113132230A

CN113132230A - Method, device and computer storage medium for sending message

Info

Publication number: CN113132230A
Application number: CN201911417611.5A
Authority: CN
Inventors: 刘元春; 谢经荣; 刘毅松
Original assignee: Beijing Huawei Digital Technologies Co Ltd
Current assignee: Beijing Huawei Digital Technologies Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2021-07-16

Abstract

The application discloses a method, equipment and a computer storage medium for sending messages, wherein the method can be applied to first network equipment, the first network equipment acquires messages to be sent, the messages comprise multicast adding information, and the multicast adding information carries information used for distinguishing different second network equipment. And then, the first network equipment sends the message to a route reflector, and the route reflector forwards the message to corresponding second network equipment according to the multicast adding information in the message. By carrying the information for distinguishing different second network devices in the multicast joining information, the message can still be ensured to be forwarded to the corresponding second network device under the condition that a plurality of second network devices exist, and further multicast interruption is prevented.

Description

Method, device and computer storage medium for sending message

Technical Field

The present application relates to the field of communications, and in particular, to a method, an apparatus, and a computer storage medium for sending a packet.

Background

Next Generation Multicast Virtual Private Network (NGMVPN) is a next generation multicast (VPN) bearer scheme, and the NGMVPN carries multicast signaling through a (border gateway protocol, BGP) update packet, and supports NGMVPN control plane operation.

In a BGP update (update) message, an attribute of Network Layer Reachability Information (NLRI) of the MCAST-VPN is newly defined, and the NLRI includes 7 types of routing types. The route No. 7 is called user multicast routing information (C-multicast routing information) and is used for transmitting private network multicast joining information.

Disclosure of Invention

The embodiment of the application provides a method, equipment and a computer readable storage medium for sending a message, which are used for solving the problems provided by the related technology, and the technical scheme is as follows:

in one aspect, a method for sending a packet is provided, where the method is applicable to a first network device, and the first network device obtains a packet to be sent, where the packet includes multicast join information, and the multicast join information carries information for distinguishing different second network devices. And then, the first network equipment sends the message to a route reflector, and the route reflector forwards the message to corresponding second network equipment according to the multicast joining information in the message.

By carrying the information for distinguishing different second network devices in the multicast joining information, the message can still be ensured to be forwarded to the corresponding second network device under the condition that a plurality of second network devices exist, and further multicast interruption is prevented.

In an exemplary embodiment, the multicast join information carries extended user multicast information, where the extended user multicast information includes an extension field, and the extension field carries an internet protocol IP address of the second network device, and the second network device can be distinguished from other second network devices by the IP address of the second network device.

In an exemplary embodiment, the multicast join information carries a leaf route, where the leaf route includes an IP address of the first network device and an IP address of the second network device, and the IP address of the first network device and the IP address of the second network device may be used to distinguish the second network device from other second network devices.

In an exemplary embodiment, the leaf route further includes a leaf route as an indication mark of the user multicast information, where the indication mark is used to indicate the second network device to perform multicast forwarding.

In an exemplary embodiment, before the first network device sends the packet, the method further includes: and the first network device receives an automatic discovery route containing a provider multicast service interface in an autonomous system domain sent by the second network device, wherein the automatic discovery route containing the provider multicast service interface in the autonomous system domain carries an LIR-PF mark, and the LIR-PF mark is used for indicating the first network device to reply the leaf route.

There is also provided an apparatus for sending a message, the apparatus comprising:

the processing unit is used for acquiring a message to be sent, wherein the message comprises multicast adding information, and the multicast adding information carries information used for distinguishing second network equipment;

and the sending unit is used for sending the message to a route reflector, and the route reflector forwards the message to the corresponding second network equipment according to the multicast adding information in the message.

In an exemplary embodiment, the multicast join information carries extended user multicast information, where the extended user multicast information includes an extension field, where the extension field carries an internet protocol IP address of the second network device, and the IP address of the second network device is used to distinguish the second network device.

In an exemplary embodiment, the multicast join information carries a leaf route, the leaf route includes an IP address of the first network device and an IP address of the second network device, and the IP address of the first network device and the IP address of the second network device are used for distinguishing the second network device.

In an exemplary embodiment, the apparatus further comprises:

a receiving unit, configured to receive an automatic discovery route including a provider multicast service interface in an autonomous system domain sent by the second network device, where the automatic discovery route including the provider multicast service interface in the autonomous system domain carries an LIR-PF flag, and the LIR-PF flag is used to indicate that the first network device replies to the leaf route.

In an exemplary embodiment, the RR is configured with a path adding function, and the path adding function is used for issuing a plurality of routes by the RR.

There is also provided an apparatus for sending a message, the apparatus comprising: the message sending method comprises a memory and a processor, wherein at least one instruction is stored in the memory and loaded and executed by the processor so as to realize any one of the message sending methods.

There is also provided a computer readable storage medium having stored therein at least one instruction which is loaded and executed by a processor to implement the method of sending a message as described in any of the above.

There is provided another communication apparatus including: a transceiver, a memory, and a processor. Wherein the transceiver, the memory and the processor communicate with each other via an internal connection path, the memory is configured to store instructions, and the processor is configured to execute the instructions stored by the memory to control the transceiver to receive signals and control the transceiver to transmit signals, and when the processor executes the instructions stored by the memory, to cause the processor to perform the method of the first aspect or any of the possible embodiments of the first aspect.

In an exemplary embodiment, the processor is one or more, and the memory is one or more.

As an example embodiment, the memory may be integrated with the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

There is provided a computer program (product) comprising: computer program code which, when run by a computer, causes the computer to perform the method of the above aspects.

There is provided a chip comprising a processor for retrieving from a memory and executing instructions stored in the memory, so that a communication device in which the chip is installed performs the method of the above aspects.

Providing another chip comprising: the system comprises an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method in the aspects.

Drawings

Fig. 1 is a schematic diagram of a networking architecture provided in an embodiment of the present application;

fig. 2 is a flowchart of a method for sending a message according to an embodiment of the present application;

fig. 3 is a schematic diagram of a message format of user multicast routing information according to an embodiment of the present application;

fig. 4 is a schematic diagram of a message format of extended user multicast routing information according to an embodiment of the present application;

fig. 5 is a schematic diagram of a networking architecture provided in an embodiment of the present application;

fig. 6 is a schematic diagram of a leaf routing packet format according to an embodiment of the present application;

fig. 7 is a schematic diagram of a format of a routing packet according to an embodiment of the present application;

fig. 8 is a schematic diagram of a networking architecture provided in an embodiment of the present application;

fig. 9 is a schematic diagram of a networking architecture provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The terminology used in the description of the embodiments section of the present application is for the purpose of explanation only of the examples of the present application and is not intended to be limiting of the present application.

The NGMVPN is a next generation multicast VPN bearing scheme, and carries multicast signaling through BGP update messages and supports the operation of an NGMVPN control plane. The BGP update message newly defines MCAST-VPN NLRI attribute, and the NLRI includes 7 routing types. Wherein, the route No. 7 is called as C-multicast route and is used for transmitting the private network multicast joining information.

The C-multicast route is to be sent to a Provider Edge (PE) at a sending end for introducing multicast traffic, and a BGP update (update) message is to be sent to all PEs. To this end, the C-multicast route also carries a Route Target (RT) attribute. The RTs are used for distribution of routing information, and are classified into an Import (Import) RT for an Import policy of routing information and an Export (Export) RT for an Export policy of routing information. When deriving a VPN route from a Virtual Routing Forwarding (VRF) table, marking the VPN route by using an Export RT; when importing the VPN route into the VRF table, only the route with the RT mark matched with any Import RT in the VRF table is imported into the VRF table.

The VRF table is a VPN route forwarding table, and allows multiple instances of a routing table to coexist in the same router at the same time. Since the routing instances in the VRF table are independent, the same or overlapping Internet Protocol (IP) addresses can be used without collision. Thus, the VRF functionality provides the functionality to change from one physical router to multiple virtual routers. RT can make PE router only contain route of VPN that links to each other directly, rather than route of all VPN of the whole network to saved PE router's resource, improved network expansibility. That is, VPNs of different topology types can be constructed by appropriate configuration of inport RT and Export RT.

Wherein the RT attribute includes a global management field (global Administrator field) and a Local management field (Local Administrator field). The global management field (global administration field) is used to fill in the IP address of the sending PE, and the Local management field (Local administration field) is used to fill in the VRF key (key value) allocated by the sending PE. When the sending end PE receives the c-multicast routing, matching is carried out according to the RT, and only the IP and the VRF key are matched and received.

However, since the IP address in the VPN is planned by the user, there is a possibility that the user selects a private address defined in Request For Comments (RFC) 1918 as a site address or different VPNs use the same address domain, and an address overlapping phenomenon occurs. One consequence of address overlap is that BGP cannot distinguish overlapping routes from different VPNs, resulting in a site being unreachable. To solve this problem, BGP/MPLS VPN introduces the concept of RD in addition to the approach of using multiple VRF tables on PE routers. The RD has global uniqueness, and the non-unique IPv4 address is converted into a unique VPN-IPv4 address by taking 8 bytes of RD as an extension of an IPv4 address prefix. The VPN-IPv4 address is not visible to the client device and is only used for distribution of routing information over the backbone network. A one-to-one correspondence is established between the RD and VRF tables. In general, for subinterfaces belonging to the same VPN on different PE routers, the same RD is allocated to their corresponding VRF tables, in other words, a unique RD is allocated to each VPN. However, in the case of overlapping VPNs, that is, a site belongs to multiple VPNs, since a sub-interface on the PE router belongs to multiple VPNs, at this time, only one RD can be allocated to the VRF table corresponding to the sub-interface, and thus, multiple VPNs share one RD.

Therefore, RD of the plurality of sending-end PEs may be the same or different. When a plurality of sending end PEs exist in a network, and RD configurations of the plurality of sending end PEs are the same, if there is a Route Reflector (RR) between the sending end PE and the receiving end PE, and when a source route from the receiving end PE is an equivalent route, it is assumed that sending ends selected by different receiving end PEs are different, NLRI parts of C-multicast messages sent by Recv1 and Recv2 as the sending end PEs are completely identical, and only RT attributes fill in IP addresses of the corresponding sending end PEs respectively. When two messages pass through RR, RR reflector only transmits one message to transmitting end PE.

For example, taking the networking structure shown in fig. 1 as an example, the sender PE selected by the receiving end Recv1 is sender1, and the sender PE selected by the other receiving end Recv2 is sender 2. For example, as shown in FIG. 1, the receiving end Recv1 and the receiving end Recv2 respectively send C-multicast routes to the RR, and the C-multicast routes sent by the receiving end Recv1 carry NLRI (1:1/100/225.0.0.1/1.1.1.1) and RT (2.2.2.2/1). The C-multicast route sent by the receiving end Recv2 carries NLRI (1:1/100/225.0.0.1/1.1.1.1) and RT (3.3.3.3/1). After RR, only one C-multicast route is forwarded. For example, the RR only forwards the C-multicast route carrying the RT attribute of 2.2.2.2/1, that is, the C-multicast route sent by the receiving end Recv1 is forwarded, and since the sending end PE selected by the receiving end Recv1 is sender1, the sender1 can successfully match after receiving the C-multicast route sent by the receiving end Recv1, and thus the Recv1 can normally receive multicast traffic. However, after the sender2 receives the C-multicast route sent by the receiving end Recv1, the matching is unsuccessful, the C-multicast route is discarded, and Recv2 cannot receive the multicast traffic. Therefore, in the scenario of multiple transmitting end PEs, the receiving end PE cannot receive the multicast traffic, and further, a problem of multicast flow interruption of part of the receiving ends occurs.

In order to solve the problem that multicast flow is cut off due to that part of receiving end PEs may not receive traffic in a scenario with multiple sending end PEs, an embodiment of the present application provides a method for sending a packet, and referring to fig. 2, the method includes the following processes.

201, a first network device obtains a message to be sent, where the message includes multicast join information, and the multicast join information carries information for distinguishing different second network devices.

The first network device in the embodiments of the present application includes, but is not limited to, a router and/or a switch. The message to be sent acquired by the first network device may be a BGP update message, which may be generated by the first network device, and is used to carry a multicast signaling and support an operation of an NGMVPN control plane. Therefore, the first network device has BGP and NGMVPN protocol processing capabilities. The message acquired by the first network device includes multicast join information, and the multicast join information carries information for distinguishing different second network devices.

In an exemplary embodiment, the following two ways of carrying information for distinguishing different second network devices by multicast join information are provided in the embodiments of the present application.

The first method is as follows: the multicast joining information carries expanded user multicast information, the expanded user multicast information comprises an expanded field, the expanded field carries an Internet Protocol (IP) address of the second network equipment, and the IP address of the second network equipment is used for distinguishing the second network equipment from other second network equipment.

In a first manner, an MCAST-VPN NLRI route type is newly added in the embodiment of the present application, for example, an extended user multicast information (C-multicast extended) is used to extend a C-multicast route. The format of the C-multicast packet can be as shown in FIG. 3.

As shown in FIG. 3, the C-Multicast packet includes RD (8octets), Source AS (4octets), Multicast Source Length (1octet), Multicast Source (variable), Multicast Group Length (1octet), and Multicast Group (variable). Wherein, Source AS represents the original autonomous domain system, Multicast Source Length represents the Multicast Source Length, Multicast Source represents the Multicast Source, Multicast Group Length represents the Multicast Group Length, and Multicast Group represents the Multicast Group. octes is a computer language that uses octets on behalf of the Internet standard. variable stands for variable.

In order to distinguish different network devices, in the embodiment of the present application, a field is extended on the basis of C-multicast, and a first network device is taken as a receiving end, and a second network device is taken as a sending end. The extension field is used to fill in the IP address of the sending end PE, and the format of the message is shown in fig. 4. In fig. 4, in addition to the fields shown in fig. 3, such AS RD (8octets), Source AS (4octets), Multicast Source Length (1octet), Multicast Source (variable), Multicast Group Length (1octet), and Multicast Group (variable), an extension field is also included, and the extension field is Root Address (variable) in fig. 4. By the method, aiming at the condition that a plurality of receiving ends and a plurality of sending ends exist, the C-multicast routes sent by the receiving ends of the same sending end can still be aggregated on the RR, and the C-multicast routes sent by the receiving ends of different sending ends can be correctly reflected.

Taking the networking structure shown in fig. 5 as an example, the sender PE selected by the receiving end Recv1 is sender1, and the sender PE selected by the other receiving end Recv2 is sender 2. The receiver Recv1 and the receiver Recv2 respectively send extended user multicast information, namely C-multicast extended, to the RR. The C-multicast extension sent by the receiving end Recv1 carries NLRI (1:1/100/225.0.0.1/1.1.1.1/2.2.2.2) and RT (2.2.2.2/1), wherein the C-multicast extension sent by the receiving end Recv1 carries Root Address (variable) which carries the IP Address 2.2.2.2 of the sender 1. The C-multicast extension sent by the receiving end Recv2 carries NLRI (1:1/100/225.0.0.1/1.1.1.1/3.3.3.3) and RT (3.3.3.3/1), wherein the C-multicast extension sent by the receiving end Recv2 carries Root Address (variable) which carries the IP Address 3.3.3.3.3 of the sender 2. After RR, two C-multicast extensions are forwarded because the two C-multicast extensions carry the IP addresses of different PE (provider edge) of the sending end respectively. Since the sending end PE selected by the receiving end Recv1 is sender1, the sender1 can successfully match after receiving the C-multicast extended sent by the receiving end Recv1, and thus the Recv1 can normally receive the multicast traffic. However, after the sender2 receives the C-multicast extended route sent by the receiving end Recv2, matching is successful, and the Recv2 can also normally receive multicast traffic. Therefore, under the scene of multiple sending end PEs, the problem that the receiving end PE cannot receive multicast traffic is avoided, so that multicast flow cutoff of part of the receiving ends is avoided.

The second method comprises the following steps: the multicast joining information carries a leaf route, the leaf route comprises an IP address of the first network device and an IP address of the second network device, and the IP address of the first network device and the IP address of the second network device are used for distinguishing the second network device from other second network devices.

For the second approach, the function of C-multicast routing is replaced by using route number 5, a Leaf route. The format of the Leaf routing packet is shown in fig. 6. The Leaf Route includes two fields, Route Key and organizing Router's IPAddr. The origin routers' IPAddr represents the IP address of the source route, which may be the IP address of the destination PE. Route Key represents a routing Key field, which may be filled in as S, G source group information, and the format of the Route Key field may be as shown in fig. 7. In FIG. 7, Route Key includes RD (8octets), Multicast Source Length (1octet), Multicast Source (variable), Multicast Group Length (1octet), Multicast Group (variable), and organizing Router's IPAddr. The aligning Router's IPAddr in Route Key is the IP address of the sending end PE.

Taking the networking structure shown in fig. 8 as an example, the sender PE selected by the receiving end Recv1 is sender1, and the sender PE selected by the other receiving end Recv2 is sender 2. The sink Recv1 and sink Recv2 send leaf routes (leaf routes) to the RRs, respectively. For example, a leaf route sent by the receiving end Recv1 carries NLRI (1: 1/100/225.0.0.1/1.1.1/2.2.2.2/4.4.4.4), wherein 2.2.2.2 is the IP address of the sender1, and 4.4.4.4 is the IP address of the receiving end Recv 1. The leaf route sent by the receiving end Recv2 carries NLRI (1: 1/100/225.0.0.1/1.1.1/3.3.3.3/5.5.5.5), wherein 3.3.3.3 is the IP address of the sender2 and 5.5.5.5 is the IP address of the receiving end Recv 2. After RR, because the two leaf routes carry the IP addresses of different sending-end PEs and receiving-end PEs, the two leaf routes are both forwarded. Since the sending end PE selected by the receiving end Recv1 is sender1, the sender1 can successfully match after receiving the leaf route sent by the receiving end Recv1, and thus the Recv1 can normally receive the multicast traffic. However, since the sender2 successfully matches the leaf route sent by the receiver Recv2, the Recv2 can also normally receive the multicast traffic. Therefore, under the scene of multiple sending end PEs, the problem that the receiving end PE cannot receive multicast traffic is avoided, so that multicast flow cutoff of part of the receiving ends is avoided.

In an exemplary embodiment, the leaf route further includes an indication flag (LIR-PF) of the leaf route as the user multicast information, where the indication flag is used to instruct the second network device to perform multicast forwarding.

In an exemplary embodiment, before the first network device sends the packet, the method further includes: the method comprises the steps that a first network device receives an automatic discovery route (Intra-AS IPMSI A-D) containing a provider multicast service interface sent by a second network device in an autonomous system domain, the automatic discovery route containing the provider multicast service interface in the autonomous system domain carries an LIR-PF mark, and the LIR-PF mark is used for indicating the first network device to reply a leaf route.

In summary, in the second mode, the process of transmitting the packet between the sending end and the receiving end includes:

1. when a sending end PE sends an Intra-AS IPMSI A-D, an LIR-pF mark is carried in a Provider Multicast Service Interface (PMSI) attribute.

2. After receiving the Intra-AS IPMSI A-D, the PE at the receiving end replies a Leaf A-D route carrying S, G source group information if the local has a receiver. Wherein, Leaf A-D carries a newly added mark 'Leaf AD as C-multicast', which is used for indicating that Leaf route is used to replace C-multicast.

3. After receiving the Leaf A-D route, the PE at the sending end forwards the multicast flow according to S, G source group information if carrying the Leaf AD as C-multicast.

In this way, because the Leaf a-D route carries both the PE IP address of the sending end and the PE IP address of the receiving end, both of which are Key values, the messages are not aggregated on the RR reflector.

202, the first network device sends the packet to the route reflector, and the route reflector forwards the packet to the corresponding second network device according to the multicast join information in the packet.

Because the multicast joining information in the message carries information for distinguishing different second network devices, after the first network device sends the message to the route reflector, the route reflector can distinguish different second network devices according to the multicast joining information in the message, so that the message is forwarded to the corresponding second network devices, and the phenomenon that the flow cutoff occurs because some second network devices cannot receive the corresponding message is avoided.

It should be noted that, no matter which of the above-mentioned manners is adopted to implement that the multicast join information carries information for distinguishing different second network devices, the RR may be configured with a path adding function, and the path adding function is used for the RR to issue multiple routes. The ADD-PATH is configured on the RR, which allows multiple routes with the same prefix to be issued to the neighbors at the same time, thus solving the problem of the scenario.

For example, taking the networking structure shown in fig. 9 as an example, the sender PE selected by the receiving end Recv1 is sender1, and the sender PE selected by the other receiving end Recv2 is sender 2. For example, as shown in FIG. 9, the receiving end Recv1 and the receiving end Recv2 respectively send C-multicast routes to the RR, and the C-multicast routes sent by the receiving end Recv1 carry NLRI (1:1/100/225.0.0.1/1.1.1.1) and RT (2.2.2.2/1). The C-multicast route sent by the receiving end Recv2 carries NLRI (1:1/100/225.0.0.1/1.1.1.1) and RT (3.3.3.3/1). After the RR, since the RR is configured with the path adding function best-path, both the received two C-multicast routes can be forwarded. Since the sending end PE selected by the receiving end Recv1 is sender1, the sender1 can successfully match after receiving the C-multicast route sent by the receiving end Recv1, and thus Recv1 can normally receive the multicast traffic. Since the sending end PE selected by the receiving end Recv2 is sender2, the sender2 can successfully match after receiving the C-multicast route sent by the receiving end Recv2, and thus Recv2 can normally receive the multicast traffic. Therefore, under the scene of multiple sending end PEs, the problem that the receiving end PE cannot receive multicast traffic is avoided, so that multicast flow cutoff of part of the receiving ends is avoided.

In an exemplary embodiment, the ADD-PATH may also set a number upper limit, for example, as shown in fig. 9, the PATH-number upper limit is set to 2, i.e., the number of routes issued at the same time is set to 2. When the receiving end PE exceeds the upper limit quantity configured by the ADD-PATH, the routing of a plurality of same prefixes to the neighbor is stopped, and the mode of the first mode or the second mode is adopted to realize the differentiation of different network devices.

In fig. 5, 8, and 9, in the information received by the RR reflector in the embodiment of the present application, information with a "x" represents information that is selected and forwarded by the RR reflector, and the "x" is only a mark for representing selection.

According to the method provided by the embodiment of the application, the multicast adding information carries information for distinguishing different second network devices, so that the message can still be guaranteed to be forwarded to the corresponding second network devices under the condition that a plurality of second network devices exist, and further multicast interruption is prevented.

An embodiment of the present application provides a network device, where the network device is configured to execute the method for sending a packet shown in fig. 2. Referring to fig. 10, the network device includes:

the processing unit 1001 is configured to acquire a message to be sent, where the message includes multicast join information, and the multicast join information carries information used for distinguishing a second network device. The processing unit 1001 is configured to perform step 201 in the embodiment shown in fig. 2.

The sending unit 1002 is configured to send the packet to the route reflector, and the route reflector forwards the packet to the corresponding second network device according to the multicast join information in the packet. The sending unit 1002 is configured to execute step 202 in the embodiment shown in fig. 2.

In an exemplary embodiment, the multicast join information carries extended user multicast information, the extended user multicast information includes an extension field, the extension field carries an IP address of the second network device, and the IP address of the second network device is used for distinguishing the second network device.

In an exemplary embodiment, the leaf route further includes the leaf route as an indication mark of the user multicast information, and the indication mark is used for indicating the second network device to perform multicast forwarding.

In an exemplary embodiment, referring to fig. 11, the apparatus further includes:

a receiving unit 1003, configured to receive an automatic discovery route including a provider multicast service interface in an autonomous system domain sent by the second network device, where the automatic discovery route including the provider multicast service interface in the autonomous system domain carries an LIR-PF flag, and the LIR-PF flag is used to indicate the first network device to reply the leaf route.

In an exemplary embodiment, an add path function is configured on the RR, the add path function being used for the RR to issue multiple routes.

According to the device for sending the packet provided by the embodiment of the application, the multicast adding information carries information for distinguishing different second network devices, so that the packet can still be guaranteed to be forwarded to the corresponding second network devices under the condition that a plurality of second network devices exist, and then multicast interruption is prevented.

It should be understood that the apparatus provided in fig. 10 or fig. 11 is only illustrated by the division of the functional modules when the functions of the apparatus are implemented, and in practical applications, the functions may be distributed and performed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Fig. 12 is a schematic diagram of a hardware structure of a device 1100 for sending a packet according to an embodiment of the present application. The device 1100 for sending a message shown in fig. 12 may perform the corresponding steps performed by the first network device in the method of the above-described embodiment.

As shown in fig. 12, the device 1100 for sending messages includes a processor 1101, a memory 1102, an interface 1103, and a bus 1104. The interface 1103 may be implemented by a wireless or wired method, and specifically may be a network card. The processor 1101, memory 1102 and interface 1103 are connected by a bus 1104.

The interface 1103 may include a sender and a receiver for the device 1100 sending the message to send the message. The processor 1101 is configured to perform the processing performed by the apparatus 1100 for sending a packet in the above embodiment. For example, the processor 1101 is configured to obtain a message to be sent, where the message includes multicast join information, and the multicast join information carries information for distinguishing different second network devices; interface 1103 sends the message to the route reflector. By way of example, processor 1101 is configured to support step 201 in fig. 2, and interface 1103 is configured to support step 202 in fig. 2. Memory 1102 includes an operating system 11021 and application programs 11022 for storing programs, code, or instructions that when executed by a processor or hardware device may perform the processes of the method embodiments involving a device sending messages. Alternatively, the Memory 1102 may include a Read-only Memory (ROM) and a Random Access Memory (RAM). Wherein, the ROM comprises a Basic Input/Output System (BIOS) or an embedded System; the RAM includes an application program and an operating system. When the device 1100 for sending a message needs to be operated, the device 1100 for sending a message is booted to enter a normal operation state by booting the BIOS which is solidified in the ROM or the bootloader in the embedded system. After the device 1100 for sending a message enters a normal operation state, the application program and the operating system in the RAM are operated, thereby completing the processing procedure of sending a message involved in the method embodiment.

It will be appreciated that fig. 12 shows only a simplified design of a device 1100 for sending messages. In practical applications, the device 1100 that sends the message may contain any number of interfaces, processors, or memories.

It should be understood that the processor may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be an advanced reduced instruction set machine (ARM) architecture supported processor.

Further, in an alternative embodiment, the memory may include both read-only memory and random access memory, and provide instructions and data to the processor. The memory may also include non-volatile random access memory. For example, the memory may also store device type information.

The memory may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available. For example, Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

There is also provided a computer readable storage medium having stored therein at least one instruction which is loaded and executed by a processor to implement a method of sending a message as described in any of the above.

The present application provides a computer program, which when executed by a computer, may cause the processor or the computer to perform the respective steps and/or procedures corresponding to the above-described method embodiments.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions described in accordance with the present application are generated, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk), among others.

The above-mentioned embodiments, objects, technical solutions and advantages of the present application are further described in detail, it should be understood that the above-mentioned embodiments are only examples of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present application should be included in the scope of the present application.

Claims

1. A method for sending a message, the method comprising:

the method comprises the steps that a first network device obtains a message to be sent, wherein the message comprises multicast adding information, and the multicast adding information carries information used for distinguishing different second network devices;

and the first network equipment sends the message to a route reflector, and the route reflector forwards the message to corresponding second network equipment according to the multicast joining information in the message.

2. The method of claim 1, wherein the multicast join information carries extended user multicast information, the extended user multicast information includes an extension field, the extension field carries an internet protocol IP address of the second network device, and the IP address of the second network device is used to distinguish the second network device from other second network devices.

3. The method of claim 1, wherein the multicast join information carries a leaf route, wherein the leaf route comprises an IP address of the first network device and an IP address of the second network device, and wherein the IP address of the first network device and the IP address of the second network device are used to distinguish the second network device from other second network devices.

4. The method of claim 3, wherein the leaf route further comprises a leaf route as an indicator of user multicast information, and wherein the indicator is used to instruct the second network device to perform multicast forwarding.

5. The method according to claim 3 or 4, wherein before the first network device sends the packet, the method further comprises:

and the first network device receives an automatic discovery route containing a provider multicast service interface in an autonomous system domain sent by the second network device, wherein the automatic discovery route containing the provider multicast service interface in the autonomous system domain carries an LIR-PF mark, and the LIR-PF mark is used for indicating the first network device to reply the leaf route.

6. The method of any of claims 1-5, wherein an add path function is configured on the RR, and the add path function is used for the RR to issue multiple routes.

7. A network device, characterized in that the network device comprises:

8. The network device according to claim 7, wherein the multicast join information carries extended user multicast information, the extended user multicast information includes an extension field, the extension field carries an internet protocol IP address of the second network device, and the IP address of the second network device is used to distinguish the second network device.

9. The network device of claim 7, wherein the multicast join information carries a leaf route, wherein the leaf route includes an IP address of the first network device and an IP address of the second network device, and the IP address of the first network device and the IP address of the second network device are used for distinguishing the second network device.

10. The network device of claim 8 or 9, wherein the leaf route further comprises a leaf route as an indication mark of user multicast information, and the indication mark is used for indicating the second network device to perform multicast forwarding.

11. The network device of claim 10, wherein the device further comprises:

12. The network device according to any of claims 7-11, wherein a path adding function is configured on the RR, and the path adding function is configured to issue multiple routes for the RR.

13. A network device, characterized in that the network device comprises:

a memory and a processor, the memory having stored therein at least one instruction, the at least one instruction being loaded and executed by the processor to implement the method of sending a message according to any of claims 1-6.

14. A computer-readable storage medium having stored thereon at least one instruction which is loaded and executed by a processor to implement the method of sending a message as claimed in any one of claims 1 to 6.