CN112751766B - Message forwarding method and system, related equipment and chip - Google Patents

Abstract

The application discloses a message forwarding method and system, related equipment and chips, and belongs to the technical field of network function virtualization. In this method, the CSG receives the message, and selects a proxy VPNSID from the multiple proxy VPNSIDs included in the first forwarding table as the target proxy VPNSID to forward the message, so as to forward the message to the data center routing node indicated by the target proxy VPNSID . That is, in this method, during load sharing, the CSG only needs to be responsible for sharing the load to each data center routing node, and each data center routing node completes the actual load sharing. However, the maximum number of load sharing paths of the routing nodes in the data center can be as high as 128. Therefore, the message forwarding method provided by the embodiment of the present application is equivalent to increasing the number of paths for CSG to finally perform load sharing, thereby improving the efficiency of load sharing. .

Description

Message forwarding method and system, related equipment and chip

technical field

The present application relates to the technical field of network function virtualization, in particular to a message forwarding method and system, related equipment and chips.

Background technique

In the 5G regional data center (regnional data center, RDC) technology, a virtual network function (virtualization network function, VNF) can be deployed on multiple virtual machines, and the multiple virtual machines can execute the VNF independently to achieve Load balancing of the VNF. Therefore, when a base station service gateway (cellsite service gateway, CSG) receives a message carrying the identifier of the VNF, the CSG needs to forward the message to one of the virtual machines, and the virtual machine based on the message Execute VNFs.

In related technologies, for any VNF, the CSG pre-acquires a virtual private network segment identifier (virtual private network segment identifier, VPNSID) of each of the multiple virtual machines deployed on the VNF to obtain multiple VPNSIDs. And obtain the private network route of the VNF, the private network route of the VNF is used to uniquely identify the VNF. The CSG establishes the correspondence between the multiple VPNSIDs and the private network routes of the VNF. When CSG receives a message, if the message carries the private network route of the VNF, it maps the message to one of the multiple VPNSIDs through the multipath hash algorithm according to the corresponding relationship, and then sends the The VPNSID is forwarded as the destination address of the packet, so as to forward the packet to the virtual machine indicated by the VPNSID.

However, in the above method of forwarding packets, since the current maximum number of load sharing supported by the CSG is 8 routes, the above corresponding relationship includes at most 8 VPNSIDs, thereby limiting the efficiency of load sharing.

Contents of the invention

The present application provides a message forwarding method and system, related equipment and chips, which can improve the efficiency of load sharing. Described technical scheme is as follows:

In a first aspect, a message forwarding method is provided, and the method is applied to a CSG in a communication network. Wherein, the communication network further includes multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF, and each of the multiple VRFs is connected to one or more of the aforementioned multiple VMs . Each of the aforementioned multiple VMs is configured with a VPNSID, and each of the aforementioned multiple data center routing nodes is configured with a proxy VPNSID.

In this method, the CSG receives a message, which carries the target VNF identifier; the CSG selects a proxy VPNSID from the multiple proxy VPNSIDs included in the first forwarding table as the target proxy VPNSID, and the CSG uses the target proxy VPNSID as the destination address Forwarding the message, to forward the message to the data center routing node indicated by the target proxy VPNSID, for instructing the data center routing node indicated by the target proxy VPNSID to forward the message according to the multiple VPNSIDs included in the second forwarding table. Wherein, the first forwarding table is a forwarding table corresponding to the identifier of the target VNF, and the multiple proxy VPNSIDs included in the first forwarding table refer to the proxy VPNSIDs configured corresponding to the VPNSIDs of multiple VMs. The multiple VPNSIDs included in the second forwarding table refer to the VPNSID of the VM corresponding to the target proxy VPNSID among the VPNSIDs of the multiple VMs.

In the embodiment of the present application, in order to avoid being limited by the maximum number of load sharing routes of the CSG, a proxy VPNSID may be configured for each data center routing node. For the VPNSID of any VM, configure multiple proxy VPNSIDs corresponding to the VPNSID of the VM. In this way, the proxy VPNSID can be used in the local forwarding table of the CSG to replace the VPNSID of the original VM, so that the CSG only needs to be responsible for sharing the load to each data center routing node during load sharing, and each data center routing node Complete the actual load sharing. However, the maximum number of load sharing paths of the data center routing nodes can be as high as 128. Therefore, the message forwarding method provided by the embodiment of the present application is equivalent to increasing the number of paths for CSG to finally perform load sharing, thereby improving the efficiency of load sharing. .

Optionally, in this method, the CSG acquires proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs, and adds the acquired proxy VPNSIDs to the first forwarding table.

Since the embodiment of this application uses the proxy VPNSID to replace the original VPNSID of the VM in the local forwarding table of the CSG, before the CSG forwards the message, it needs to obtain the proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs to construct the implementation of this application. The example provides the first forwarding table, thereby improving the efficiency of subsequent load sharing.

Optionally, the above-mentioned CSG acquires proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs, specifically: the CSG receives a first notification message sent by any one of the multiple VRFs, and the first notification message carries each Multiple proxy VPNSIDs corresponding to the VPNSID of each VM in the VM.

In one implementation, the VRF can proactively report multiple proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to the CSG, so that the CSG can construct the first forwarding table and improve the efficiency of the CSG in constructing the first forwarding table .

Optionally, the communications network further includes RRs. At this time, the CSG obtains the proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs, specifically: the CSG receives the second notification message sent by the RR, and the second notification message carries the proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs.

In another implementation manner, the RR reports the proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs to the CSG, so that the CSG can build the first forwarding table, which improves the flexibility of the CSG to build the first forwarding table.

In a second aspect, a message forwarding method is provided, and the method is applied to any data center routing node among multiple data center routing nodes in a communication network. The communication network further includes a CSG, multiple VRFs, and multiple VMs for executing the target VNF, and each VRF is connected to one or more of the multiple VMs. Wherein, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

In this method, any data center routing node receives the message sent by the CSG, and the message carries the target proxy VPNSID. In the case that the target proxy VPNSID carried in the message is the proxy VPNSID of the any data center routing node, the any data center routing node selects a VPNSID from the VPNSIDs of the multiple VMs included in the second forwarding table, and any data center routing node The central routing node forwards the packet using the selected VPNSID as the destination address. Wherein, the plurality of VPNSIDs included in the second forwarding table refer to the VPNSIDs of the plurality of VMs corresponding to the proxy VPNSID of any data center routing node.

Since the embodiment of this application uses the proxy VPNSID in the local forwarding table of the CSG to replace the VPNSID of the original VM, so that the CSG only needs to be responsible for sharing the load to the routing nodes of each data center during load sharing. Routing nodes to complete the actual load sharing. Therefore, when the routing node in the data center receives the message, it needs to forward the message to one of the multiple VMs according to the second forwarding table, so as to realize load sharing. Since the maximum number of load sharing paths of the routing nodes in the data center can be as high as 128, the message forwarding method provided by the embodiment of this application is equivalent to increasing the number of paths for CSG to finally perform load sharing, thereby improving the efficiency of load sharing .

Optionally, in this method, the any data center routing node acquires the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the any data center routing node, and adds the acquired VPNSIDs of the VMs to the second forwarding table.

Since the actual load sharing is performed by each data center routing node in this embodiment of the application, the data center routing node needs to obtain the VPNSIDs of multiple VMs corresponding to its own proxy VPNSID before forwarding the message, so as to construct this application The second forwarding table provided by the embodiment further improves the efficiency of subsequent load sharing.

Optionally, the any data center routing node acquires the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of any data center routing node, specifically: the any data center routing node receives the VPNSID sent by any VRF among the multiple VRFs. The third announcement message, the third announcement message carries a plurality of proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to any VRF; the any data center routing node, according to the proxy VPNSID of any data center routing node, from the first The VPNSID of the VM corresponding to the proxy VPNSID of any data center routing node is obtained from the notification message.

In one implementation, the VRF can actively report multiple proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to itself to the routing node in the data center, so that the routing node in the data center can build a second forwarding table, improving data center routing. The routing node constructs the efficiency of the second forwarding table.

Optionally, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of any data center routing node are configured by a manager on any data center routing node.

In another implementation manner, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of any data center routing node can be manually configured directly, so as to improve the flexibility of the data center routing node in constructing the second forwarding table.

In the third aspect, a message forwarding method is provided, the method is applied to any VRF among multiple VRFs in the communication network, and the communication network also includes a CSG, multiple data center routing nodes, and a VNF for executing the target For multiple VMs, one or more of the multiple VMs are connected to each VRF in the multiple VRFs. Wherein, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

In this method, for any VRF, the VRF obtains multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to the VRF; the VRF issues a first notification message to the CSG, and the first notification message carries the VRF Multiple proxy VPNSIDs corresponding to the VPNSID of each VM among multiple connected VMs.

In this embodiment of the application, the VRF can actively report to the CSG the multiple proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to it, so that the CSG can build the first forwarding table, which improves the efficiency of the CSG to build the first forwarding table .

Optionally, after the VRF acquires multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to the VRF, the VRF also issues a third notification message to multiple data center routing nodes, the third notification message carrying the Multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to the VRF.

In this embodiment of the application, the VRF can also proactively report to the data center routing node the multiple proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to itself, so that the data center routing node can build a second forwarding table and improve data The efficiency with which the central routing node constructs the second forwarding table.

In the fourth aspect, a message forwarding method is provided, and the method is applied to an RR in a communication network. The communication network also includes a CSG, multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF, and each VRF is connected to one or more of the multiple VMs. Each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

In this method, the RR obtains the VPNSID of each of the multiple VMs connected to any VRF in multiple VRFs; for the obtained VPNSID of any VM, the RR determines based on the correspondence between the locally stored VPNSID and the proxy VPNSID The proxy VPNSID corresponding to the VPNSID of the VM obtains multiple proxy VPNSIDs corresponding to the VPNSID of each VM in multiple VMs connected to any VRF; the RR sends a second notification message to the CSG, and the second notification message carries information related to multiple VRFs Multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to each VRF in .

When the RR reports the proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs to the CSG, and the CSG constructs the first forwarding table, the RR needs to obtain multiple proxy VPNSIDs corresponding to the VPNSIDs of each of the multiple VMs first, and then send The CSG sends the second notification message so that the CSG can build the first forwarding table, which improves the flexibility of the CSG to build the first forwarding table.

Optionally, in this method, the corresponding relationship between the VPNSID locally stored in the RR and the proxy VPNSID is configured by the administrator on the RR, thereby improving the flexibility of the CSG in constructing the first forwarding table.

In a fifth aspect, a CSG in a communication network is provided. Wherein, the communication network further includes multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF, and each of the multiple VRFs is connected to one or more of the aforementioned multiple VMs . Each of the aforementioned multiple VMs is configured with a VPNSID, and each of the aforementioned multiple data center routing nodes is configured with a proxy VPNSID.

CSGs include:

The receiving module is used to receive the message, and the message carries the identification of the target VNF;

A selection module, configured to select a proxy VPNSID from multiple proxy VPNSIDs included in the first forwarding table as the target proxy VPNSID;

A forwarding module, configured to use the target proxy VPNSID as the destination address to forward the message, so as to forward the message to the data center routing node indicated by the target proxy VPNSID, and to indicate that the data center routing node indicated by the target proxy VPNSID according to the second transfer Publish forwarding packets including multiple VPNSIDs. Wherein, the first forwarding table is a forwarding table corresponding to the identifier of the target VNF, and the multiple proxy VPNSIDs included in the first forwarding table refer to the proxy VPNSIDs configured corresponding to the VPNSIDs of multiple VMs. The multiple VPNSIDs included in the second forwarding table refer to the VPNSID of the VM corresponding to the target proxy VPNSID among the VPNSIDs of the multiple VMs.

Optionally, the CSG further includes an adding module, configured to obtain proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs, and add the obtained proxy VPNSIDs to the first forwarding table.

Optionally, the above-mentioned adding module is specifically configured to: receive a first notification message sent by any one of the multiple VRFs, where the first notification message carries the multiple proxy VPNSID.

Optionally, the communications network further includes RRs. At this time, the above adding module is specifically configured to: receive a second notification message sent by the RR, where the second notification message carries proxy VPNSIDs corresponding to VPNSIDs of multiple VMs.

For the technical effect of each module included in the CSG provided in the fifth aspect, reference may be made to the packet forwarding method provided in the first aspect, and will not be described in detail here.

In a sixth aspect, any data center routing node among multiple data center routing nodes in a communication network is provided. The communication network further includes a CSG, multiple VRFs, and multiple VMs for executing the target VNF, and each VRF is connected to one or more of the multiple VMs. Wherein, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

The data center routing nodes include:

The receiving module is configured to receive the message sent by the CSG, and the message carries the VPNSID of the target proxy.

A selecting module, configured to select a VPNSID from the plurality of VM VPNSIDs included in the second forwarding table when the target proxy VPNSID carried in the message is the proxy VPNSID of any data center routing node.

A forwarding module, configured to use the selected VPNSID as the destination address to forward the message. Wherein, the multiple VPNSIDs included in the second forwarding table refer to multiple VM VPNSIDs corresponding to the proxy VPNSID of the data center routing node.

Optionally, the data center routing node also includes:

An adding module, configured to obtain the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node, and add the obtained VPNSIDs of the VMs to the second forwarding table.

Optionally, the aforementioned acquisition module is specifically configured to: receive a third notification message sent by any one of the multiple VRFs, where the third notification message carries multiple agents corresponding to the VPNSID of each VM in each VM connected to any VRF VPNSID: Obtain the VPNSID of the VM corresponding to the proxy VPNSID of the data center routing node from the third notification message according to the proxy VPNSID of the data center routing node.

Optionally, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node are configured on the data center routing node by a manager.

For the technical effect of each module included in the data center routing node provided in the sixth aspect, reference may be made to the message forwarding method provided in the second aspect, and will not be described in detail here.

In a seventh aspect, any VRF among multiple VRFs in a communication network is provided, and the communication network further includes a CSG, multiple data center routing nodes, and multiple VMs for executing target VNFs, and each of the multiple VRFs One or more of multiple VMs are connected to a VRF. Wherein, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

The VRF includes:

An acquisition module, configured to acquire multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to the VRF;

The issuing module is configured to issue a first notification message to the CSG, where the first notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to the VRF.

Optionally, the issuing module is further configured to issue a third notification message to multiple data center routing nodes, where the third notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to the VRF.

For the technical effect of each module included in the VRF provided in the seventh aspect, reference may be made to the packet forwarding method provided in the third aspect, which will not be described in detail here.

In an eighth aspect, an RR in a communication network is provided. The communication network also includes a CSG, multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF, and each VRF is connected to one or more of the multiple VMs. Each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

The RR includes:

The acquiring module is configured to acquire the VPNSID of each of the multiple VMs connected to any VRF in the multiple VRFs; for the obtained VPNSID of any VM, the RR determines the VPNSID based on the correspondence between the locally stored VPNSID and the proxy VPNSID The proxy VPNSID corresponding to the VPNSID of the VM obtains multiple proxy VPNSIDs corresponding to the VPNSID of each VM in a plurality of VMs connected to any VRF;

An issuing module, configured to send a second notification message to the CSG, where the second notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to each of the multiple VRFs.

Optionally, the corresponding relationship between the VPNSID locally stored in the RR and the proxy VPNSID is configured by the administrator on the RR, thereby improving the flexibility of the CSG in constructing the first forwarding table.

For the technical effect of each module included in the RR provided in the eighth aspect, reference may be made to the packet forwarding method provided in the fourth aspect, which will not be described in detail here.

A ninth aspect provides a CSG in a communication network, where the communication network further includes multiple data center routing nodes, multiple virtual routing and forwarding VRFs, and multiple VMs for executing target virtual network functions VNFs, the One or more of the plurality of VMs is connected to each VRF in the plurality of VRFs, each VM in the plurality of VMs is configured with a VPNSID, and each data center routing node in the plurality of data center routing nodes The node is configured with a proxy VPNSID;

The CSG includes a memory and a processor;

The memory is used to store computer programs;

The processor is configured to execute the program stored in the memory to perform the method described in any one of the above first aspects.

A tenth aspect provides a data center routing node in a communication network, where the communication network includes multiple data center routing nodes, a CSG, multiple VRFs, and multiple VMs for executing target VNFs, and each VRF is connected to There are one or more of the plurality of VMs, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with a proxy VPNSID;

Any one of the plurality of data center routing nodes includes a memory and a processor;

The memory is used to store computer programs;

The processor is configured to execute the program stored in the memory to perform the method described in any one of the above second aspects.

In an eleventh aspect, a VRF in a communication network is provided, where the communication network includes multiple VRFs, CSGs, multiple data center routing nodes, and multiple VMs for executing target VNFs, and each of the multiple VRFs One or more of the plurality of VMs are connected to each VRF, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with an agent VPNSID;

Any one of the plurality of VRFs includes a memory and a processor;

The memory is used to store computer programs;

The processor is configured to execute the program stored in the memory to perform the method described in any one of the above third aspects.

In a twelfth aspect, an RR in a communication network is provided, and the communication network further includes a CSG, multiple data center routing nodes, multiple VRFs, and multiple VMs for executing target VNFs, and each VRF is connected to One or more of the plurality of VMs, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with a proxy VPNSID;

The RR includes a memory and a processor;

The memory is used to store computer programs;

The processor is configured to execute the program stored in the memory to perform the method described in any one of the above fourth aspects.

In a thirteenth aspect, a chip is provided, the chip is set in a CSG in a communication network, and the communication network further includes multiple data center routing nodes, multiple virtual routing and forwarding VRFs, and a target virtual network for executing Multiple VMs of functional VNFs, one or more of the multiple VMs are connected to each of the multiple VRFs, each of the multiple VMs is configured with a VPNSID, and the multiple data Each data center routing node in the central routing node is configured with a proxy VPNSID;

The chip includes a processor and an interface circuit;

The interface circuit is used to receive instructions and transmit them to the processor;

The processor is configured to execute the method described in any one of the above first aspects.

In a fourteenth aspect, a chip is provided, and the chip is set in any one of the multiple data center routing nodes included in the communication network, and the communication network further includes a CSG, multiple VRFs, for Executing multiple VMs of the target VNF, each VRF is connected to one or more of the multiple VMs, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes Each data center routing node is configured with a proxy VPNSID;

The chip includes a processor and an interface circuit;

The interface circuit is used to receive instructions and transmit them to the processor;

The processor is configured to execute any one of the above second aspects.

In a fifteenth aspect, a chip is provided, the chip is set in any VRF among the multiple VRFs included in the communication network, and the communication network also includes a CSG, multiple data center routing nodes, and is used to execute the target VNF Multiple VMs, each of the multiple VRFs is connected to one or more of the multiple VMs, each of the multiple VMs is configured with a VPNSID, and the multiple data center routing Each data center routing node in the node is configured with a proxy VPNSID;

The chip includes a processor and an interface circuit;

The interface circuit is used to receive instructions and transmit them to the processor;

The processor is configured to execute any one of the third aspects above.

A sixteenth aspect provides a chip, the chip is set in the RR of the communication network, and the communication network further includes CSG, multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF , each VRF is connected to one or more of the plurality of VMs, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with A proxy VPNSID;

The chip includes a processor and an interface circuit;

The interface circuit is used to receive instructions and transmit them to the processor;

The processor is configured to execute any aspect described in the fourth aspect above.

A sixteenth aspect provides a message forwarding system, the system includes a CSG, multiple data center routing nodes, multiple virtual routing and forwarding VRFs, and multiple VMs for executing target virtual network functions VNFs, the Each of the multiple VRFs is connected to one or more of the multiple VMs, each of the multiple VMs is configured with a virtual private network segment identifier VPNSID, and each of the multiple data center routing nodes The central routing node is configured with a proxy VPNSID;

The CSG is configured to obtain proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs, and add the obtained proxy VPNSIDs to the first forwarding table;

Any data center routing node among the plurality of data center routing nodes is configured to obtain VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node, and add the obtained VPNSIDs of VMs to the second forwarding table.

Optionally, the CSG is specifically configured to: receive a first notification message sent by any one of the multiple VRFs, where the first notification message carries multiple proxies corresponding to the VPNSID of each of the VMs connected to the any VRF VPNSID.

Optionally, the CSG is specifically configured to: the CSG receives a second notification message sent by the RR, where the second notification message carries proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs.

Optionally, the data center routing node is configured to receive a third notification message sent by any VRF among the plurality of VRFs, where the third notification message carries the VPNSID corresponding to each VM among the VMs connected to any VRF. A plurality of proxy VPNSIDs; according to the proxy VPNSID of the data center routing node, obtain the VPNSID of the VM corresponding to the proxy VPNSID of the data center routing node from the third notification message.

Optionally, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node are configured on the data center routing node by a manager.

The technical effects of each node in the above message forwarding system can also refer to the technical effects of the message forwarding method provided in the first aspect, the second aspect, the third aspect and the fourth aspect, and will not be repeated here.

Description of drawings

FIG. 1 is a schematic structural diagram of a communication network provided by an embodiment of the present application;

FIG. 2 is a schematic structural diagram of another communication network provided by an embodiment of the present application;

FIG. 3 is a flowchart of a message forwarding method provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a message forwarding process provided by an embodiment of the present application;

FIG. 5 is a flowchart of a method for configuring a first forwarding table and a second forwarding table provided in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of another network device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of an interface board in the network device shown in FIG. 7 provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a CSG provided by an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a data center routing node provided by an embodiment of the present application;

FIG. 11 is a schematic structural diagram of another network device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

It should be understood that the "plurality" mentioned herein refers to two or more than two. In the description of this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this article is just a description of the relationship between associated objects, Indicates that there may be three relationships, for example, A and/or B, may indicate: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

Before explaining the message forwarding method provided by the embodiment of the present application, the communication network involved in the embodiment of the present application is explained first.

FIG. 1 is a schematic structural diagram of a communication network provided by an embodiment of the present application. As shown in FIG. 1 , the communication network 100 includes multiple CSGs, multiple provider edge devices (provider edges, PEs), multiple data center routing nodes, multiple data centers, and multiple virtual route forwarding (virtual route forwarding, VRF).

The data center may be an RDC, or a central data center (central data center, CDC) or an edge data center (edge data center, EDC). Figure 1 uses the RDC as an example for illustration. The data center routing node may be a data center gateway (data center gateway, DCGW) deployed between the PE and the data center, and may also be a DC Spine (ridge) router deployed between the data center and the VRF. This is not specifically limited. FIG. 1 takes the data center routing node as an example to illustrate the DCGW deployed between the PE and the data center.

As shown in Figure 1, any CSG communicates with any DCGW through multiple PEs in the backbone network. Any DCGW communicates with any RDC. Any RDC communicates with each connected VRF, and each VRF is connected with one or more VMs (in FIG. 1 , each VRF is connected with one VM as an example for illustration). There are multiple VMs used to execute the same VNF, and they may be connected to different VRFs. As shown in FIG. 1 , there are three VMs used to execute the VNF shown in FIG. 1 , which are the three VMs connected to the first three VRFs from top to bottom in FIG. 1 .

In order to accurately implement load sharing for a certain VNF, an END.dx-type SID, also called VPNSID, is configured for each VM in each VM used to execute the VNF. That is, in this embodiment of the application, each VPNSID is used to uniquely identify a VM. In this way, the forwarding table of the CSG in the related art includes multiple VPNSIDs corresponding to the identifier of the VNF, so that the CSG forwards the message to the VM indicated by one of the VPNSIDs according to the forwarding table.

As shown in Figure 1, the current CSG supports up to 8-way load sharing, that is, when the CSG receives a message, the CSG can forward the message to one of the 8 VMs at most based on the multi-path hash algorithm. VM for processing, which seriously affects the efficiency of load sharing. In this basic scenario, the embodiment of the present application provides a method for forwarding packets, so as to improve the efficiency of load sharing.

In addition, the VNF shown in FIG. 1 may be an access management function (access management function, AMF), may also be a session management function (session management function, SMF), may also be a user plane function (userplane function, UPF), etc. .

In addition, any one of the aforementioned VRFs is connected to a VM through a designated access (Access Circuit, AC) layer-3 interface or sub-interface, which will not be described in detail here.

It should be noted that the number of devices shown in FIG. 1 is only for illustration, and does not constitute a limitation on the architecture of the communication network provided in the embodiment of the present application.

For convenience of subsequent description, the communication network shown in FIG. 1 is simplified, and the simplified communication network is shown in FIG. 2 . The subsequent method for forwarding packets is illustrated by taking the communication network shown in FIG. 2 as an example. As shown in FIG. 2, the communication network 200 includes a CSG and a plurality of data center routing nodes (in FIG. 2, two data center routing nodes are taken as an example, which are respectively marked as data center routing node 1 and data center routing node 2) , multiple VRFs (two VRFs are taken as an example in Figure 2, marked as VRF1 and VRF2 respectively), and multiple VMs for executing the target VNF, each of the multiple VRFs is connected to multiple VMs One or more (in FIG. 2, two VMs connected to each VRF are taken as an example for illustration).

In addition, as shown in Figure 2, the network is divided into multiple domains, each domain includes a group of hosts and a group of routers, and the hosts and routers in a domain are managed by a controller. In FIG. 2 , CSG, data center routing node 1, and data center routing node 2 are located in the same domain, and data center routing node 1, data center routing node 2, and VRF1 and VRF2 are located in another domain. A route reflector (route reflector, RR) is also deployed in each domain, which are respectively marked as RR1 and RR2 in FIG. 2 . Among them, the function of the route reflector in each domain is: any routing device in the domain can communicate with other routing devices through this route reflector, without directly establishing a network connection between the two routing devices, thereby reducing network resources consumption.

The functions of each node in the communication network shown in FIG. 2 will be described in detail in the following embodiments, and will not be described one by one here.

The following uses the communication network shown in Figure 2 as an example to illustrate the message forwarding method provided by the embodiment of the present application. For the deployment of other nodes in the communication network shown in Figure 1, you can refer to the following embodiments to implement the message forwarding method. Forward.

FIG. 3 is a flowchart of a message forwarding method provided by an embodiment of the present application. As shown in Figure 3, the method includes the following steps:

Step 301: The CSG receives a message, which carries the identifier of the target VNF.

In the embodiment of the present application, in order to avoid being limited by the maximum number of load sharing routes of the CSG, a proxy VPNSID may be configured for each data center routing node. For any VM's VPNSID, multiple proxy VPNSIDs can be configured for that VM's VPNSID. In this way, the proxy VPNSID can be used in the local forwarding table of the CSG to replace the VPNSID of the original VM, so that the CSG only needs to be responsible for sharing the load to each data center routing node during load sharing, and each data center routing node The actual load sharing is completed, and the maximum number of load sharing paths of the routing nodes in the data center can be as high as 128. Therefore, the message forwarding method adopted in the embodiment of the present application is equivalent to increasing the number of paths for CSG to finally perform load sharing, thereby The efficiency of packet forwarding is improved.

Therefore, a first forwarding table corresponding to the target VNF identifier is stored in the CSG, and the first forwarding table includes multiple proxy VPNSIDs, so that the CSG forwards the packet through the following steps 302 and 303 . The multiple proxy VPNSIDs included in the first forwarding table refer to proxy VPNSIDs corresponding to VPNSIDs of multiple VMs used to execute the target VNF. Wherein, the configuration process of the first forwarding table will be described in the following embodiments, and will not be described here.

FIG. 4 is a schematic diagram of packet forwarding provided by an embodiment of the present application. As shown in FIG. 4 , the first forwarding table stored in the CSG includes two proxy VPNSIDs, which are DE::B100 and DF::B100 respectively. DE::B100 is the proxy VPNSID of data center routing node 1. DF::B100 is the proxy VPNSID of data center routing node 2.

Wherein, for the VPNSID of any VM, multiple proxy VPNSIDs are configured for the VPNSID of the VM. As shown in Figure 4, two corresponding proxy VPNSIDs are configured for the VPNSID of the first VM from top to bottom (the VPNSID is A8:1::B100), which are DE::B100 and DF::B100 respectively. For the VPNSID of the second VM from top to bottom (the VPNSID is A8:1::B101), two corresponding proxy VPNSIDs are also configured, namely DE::B100 and DF::B100. In addition, for the third VM and the fourth VM from top to bottom, these two corresponding proxy VPNSIDs can also be configured. That is, for the VPNSID of each VM shown in FIG. 4 , two corresponding proxy VPNSIDs are configured, namely DE::B100 and DF::B100.

After the VPNSID of each VM is configured with the corresponding proxy VPNSID according to the above method, at this time, the first forwarding table includes two proxy VPNSIDs (these two proxy VPNISDs are DE::B100 and DF::B100 respectively.) and execute All proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs of the target VNF. The process of configuring the proxy VPNSID corresponding to the VPNSID of each VM and the specific implementation of generating the first forwarding table will be described in detail in the following embodiment of generating the first forwarding table, and will not be repeated here.

Step 302: The CSG selects a proxy VPNSID from multiple proxy VPNSIDs included in the first forwarding table as the target proxy VPNSID.

In a specific implementation manner, the CSG may select a proxy VPNSID from multiple proxy VPNSIDs included in the first forwarding table through a multipath hash algorithm. The multi-path hash algorithm may be an equal-cost multi-path (equal-cost multi path routing, ECMP) algorithm. At this time, the multiple proxy VPNSIDs in the first forwarding table have the same probability of being selected, so that the CSG evenly distributes the received message to each data center routing node. For example, for the forwarding process shown in Figure 4, the proxy VPNSID selected by the CSG based on the multipath hash algorithm is DE::B100, indicating that the message needs to be forwarded to the data center routing node 1 at this time.

It can be understood that in another implementation manner, different hash algorithms may be used to make the probabilities of being selected for each proxy VPNSID in the first forwarding table different. Specifically, a specific type of hash algorithm may be determined according to a load balancing strategy.

Step 303: The CSG forwards the message with the target proxy VPNSID as the destination address.

In the embodiment of this application, since the proxy VPNSID is used to replace the VPNSID in the related technology, after the CSG selects the proxy VPNSID from the first forwarding table as the target proxy VPNSID, it can use the target proxy VPNSID as the message destination address to forward packets.

For example, for the forwarding process shown in Figure 4, the CSG uses proxy VPNSID=DE::B100 as the destination address of the message (the destination address is marked as DA in Figure 4), and the source address of the message (the source address is marked as DA in Figure 4). Addresses labeled SA) are CSG. In addition, as shown in FIG. 4 , the packet also includes a payload (payload). The steps marked as ① in Fig. 4 are used to illustrate the aforementioned process.

Through the above steps 301 to 303, the CSG can forward the message to the data center routing node indicated by the selected target proxy VPNSID. The data center routing node indicated by the target proxy VPNSID is configured with a second forwarding table, and the second forwarding table includes multiple VPNSIDs for indicating the multiple VPNSIDs included in the data center routing node corresponding to the target proxy VPNSID according to the second forwarding table For forwarding the packet, the multiple VPNSIDs included in the second forwarding table refer to the VPNSIDs corresponding to the target proxy VPNSID among the VPNSIDs of the multiple VMs. Therefore, for any data center routing node, if the data center routing node is the data center routing node indicated by the target proxy VPNSID selected by CSG, the received message can be processed through the following steps 304 to 306 . The configuration process of the second forwarding table will be described in the following embodiments, and will not be described here.

Step 304: For any data center routing node, the data center routing node receives the message sent by the CSG, and the message carries the target proxy VPNSID.

Since any data center routing node in the network may receive the message sent by the CSG, for any data center routing node, when the data center routing node receives the message sent by the CSG, it needs to determine whether the message is Handled by itself. In a specific implementation manner, since the destination address carried in the message is the target proxy VPNSID, the data center routing node can compare whether the target proxy VPNSID carried in the message is consistent with its own configured proxy VPNSID. If not, it indicates that the message is processed by other data center routing nodes. At this time, the message is forwarded to other data center routing nodes for processing. If they are consistent, it indicates that the message is processed by itself. At this time, the data center routing node can continue to forward the message through the following steps 305 and 306.

For example, for the forwarding process shown in Figure 4, when data center routing node 1 receives the message, since the proxy VPNSID carried in the message is DE::B100, the proxy VPNSID is exactly its own proxy VPNSID, therefore, the data The central routing node 1 may continue to forward the message through the following steps Step 305 and Step 306 .

When the data center routing node 2 receives the message, because the target proxy VPNSID carried in the message is inconsistent with its own proxy VPNSID, the data center routing node 2 continues to forward the message to the data indicated by the target proxy VPNSID Central routing node.

Step 305: In the case that the target proxy VPNSID carried in the message is the proxy VPNSID of the data center routing node, the data center routing node selects a VPNSID from the VPNSIDs of the multiple VMs included in the second forwarding table, and the second forwarding table The VPNSID of multiple VMs included in the announcement refers to the VPNSID of the VM corresponding to the proxy VPNSID of any data center routing node.

Since the data center routing node locally stores a second forwarding table corresponding to its own proxy VPNSID, and the second forwarding table includes VPNSIDs of multiple VMs corresponding to its own proxy VPNSID, the proxy VPNSID carried in the packet If it is the proxy VPNSID of any data center routing node, the data center routing node can directly select a VPNSID from the second forwarding table through the multipath hash algorithm to forward the message through the following step 306 .

The aforementioned multipath hash algorithm may also be an ECMP algorithm. At this time, the VPNSIDs of the VMs in the second forwarding table have the same probability of being selected, so that the data center routing node evenly distributes the received packets to the VMs. It can be understood that in another implementation manner, different hash algorithms may be used to make the VPNSIDs of the VMs in the second forwarding table have different selection probabilities, and a specific type of hash algorithm may be determined according to a load balancing strategy.

For example, for the forwarding process shown in Figure 4, it is assumed that the second forwarding table of data center routing node 1 includes two VPNSIDs, which are A8:1::B100 and A8:1::B101 respectively. Therefore, the data center routing node 1 can select one of these two VPNSIDs by the ECMP algorithm.

Step 306: The data center routing node forwards the message with the selected VPNSID as the destination address.

Since the message needs to be processed by the VM in the end, after the data center routing node selects a VPNSID from the second forwarding table, it can use the selected VPNSID as the destination address to forward the message, so that the selected VPNSID The indicated VM processes the packet.

For example, for the forwarding process shown in Figure 4, if the VPNSID selected by data center routing node 1 from the second forwarding table is A8:1::B100, as shown in Figure 4, data center routing node 1 can transfer A8 :1::B100 is forwarded as the destination address of the message (the destination address is marked as DA in Figure 4). If the VPNSID selected by data center routing node 1 from the second forwarding table is A8:1::B101, as shown in Figure 4, data center routing node 1 can use A8:1::B101 as the destination address of the message to retweet. It should be noted that the two steps marked ② in FIG. 4 are used to illustrate the aforementioned process, and the two steps marked ② are in an OR relationship.

In addition, since each VM is deployed on a VRF, when the data center routing node forwards the message with the selected VPNSID as the destination address, the VRF of the VM indicated by the selected VPNSID will first receive the message , and then forward the packet to the VM indicated by the selected VPNSID. The step marked ③ in Fig. 4 is used to illustrate the aforementioned process.

In the process of forwarding packets shown in Figure 3, it is necessary to configure the first forwarding table on the CSG, and configure the second forwarding table in each data center routing node. The specific functions of the first forwarding table and the second forwarding table have been described in The above embodiment has been explained, and the configuration process of the first forwarding table and the second forwarding table will be explained next.

Fig. 5 is a flow chart of a method for configuring a first forwarding table and a second forwarding table provided by an embodiment of the present application. As shown in Figure 5, the method includes the following steps:

Step 501: For any VRF, the VRF obtains the VPNSID configured for any one of the multiple VMs connected to the VRF.

Wherein, the VPNSID configured for any one of the multiple VMs connected to the VRF may be configured by the network controller, or may be directly configured on the VRF by a manager, which is not specifically limited in this application. If the VPNSID is configured by the network controller, after configuring the VPNSID of any one of the multiple VMs connected to the VRF, the network controller will issue the configured VPNSID to the VRF so that the VRF can obtain the VPNSID of the multiple VMs connected to the VRF. The VPNSID configured for any one of the VMs.

In a specific implementation manner, the network controller or the administrator configures the VPNSID for each connected VM according to the locator identifier (Locator) of the VRF. For example, for the communication network shown in Figure 4, the location identifier of VRF1 is A8:1::/64, as shown in Figure 4, the network controller or administrator can configure two VPNSIDs for the two VMs connected to VRF1 respectively, Wherein, the VPNSID configured for the first VM from top to bottom in FIG. 4 is A8:1::B100, and the VPNSID configured for the second VM from top to bottom is A8:1::B101.

Step 502: For any data center routing node, the data center routing node obtains the proxy VPNSID configured for the data center routing node.

The proxy VPNSID of the data center routing node configured on the data center routing node can be configured by the network controller, or can be configured on the data center routing node by the administrator, which is not specifically limited in this application. If the network controller configures the proxy VPNSID, the network controller will issue the configuration proxy VPNSID to the data center routing node after configuring the proxy VPNSID of the data center routing node, so that the data center routing node can obtain the data Proxy VPNSID configured by the central routing node.

In a specific implementation manner, the network controller or the administrator configures the proxy VPNSID for the data center routing node according to the location identifier (Locator) of the data center routing node. For example, for the communication network shown in Figure 4, the location identifier of data center routing node 1 is DE::/64, as shown in Figure 4, the network controller or administrator can configure a proxy VPNSID for data center routing node 1, for DE::B100. In the same manner as above, as shown in FIG. 4 , the proxy VPNSID configured for the data center routing node 2 based on the location identifier DF::/64 of the data center routing node 2 is DF::B100.

Step 503: The CSG acquires proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs used to execute the target VNF, and adds the acquired proxy VPNSIDs to the first forwarding table.

In the implementation of this application, the CSG can obtain the proxy VPNSID corresponding to the VPNSID of multiple VMs used to execute the target VNF through the following two specific implementation methods:

A first implementation manner: For any VRF, the VRF obtains multiple proxy VPNSIDs configured corresponding to the VPNSID of any one of the multiple VMs connected to the VRF. The VRF issues a first notification message to the CSG, where the first notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of any one of the multiple VMs connected to the VRF. The CSG receives the first notification message sent by the VRF. The CSG can acquire the proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs according to the first notification message sent by each VRF.

Wherein, for any VM, multiple proxy VPNSIDs configured corresponding to the VPNSID of the VM may be configured by the network controller, or may be directly configured on the VRF by a manager, which is not specifically limited in this application. If the network controller configures multiple proxy VPNSIDs corresponding to the VPNSID, after the network controller configures multiple proxy VPNSIDs corresponding to the VPNSID of the VM, it issues the multiple proxy VPNSIDs corresponding to the VPNSID of the configured VM to The VRF enables the VRF to obtain a plurality of proxy VPNSIDs correspondingly configured for the VPNSID of the VM.

As shown in Figure 2, the VRF and the CSG are located in different domains, so any one of the VRFs above can issue the first notification message to the CSG through MP-BGP/EVPN (a Border Gateway Protocol (Border Gateway Protocol, BGP) and Ethernet-based Network virtual private network (Ethernet Virtual Private Network, EVPN) multilink protocol (MultilinkProtocol), MP)) to release.

In the above first implementation manner, the VRF actively reports to the CSG the multiple proxy VPNSIDs configured corresponding to the VPNSID of any one of the multiple VMs connected to the VRF.

The second implementation mode: the RR in the communication network pre-stores the correspondence between VPNSID and proxy VPNSID in advance, the correspondence includes VPNSIDs of multiple VMs and multiple proxy VPNSIDs corresponding to the VPNSID of each VM, the correspondence The construction process of the relationship will be described in detail below, and will not be elaborated here. For any VRF, the RR obtains the VPNSID of each VM in each VM connected to the VRF. For the obtained VPNSID of any VM, the RR can determine the VPNSID corresponding to the VM based on the correspondence between the VPNSID and the proxy VPNSID. Multiple proxy VPNSIDs. After the RR acquires multiple proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to each VRF, the RR can send a second notification message to the CSG. Multiple proxy VPNSIDs corresponding to the VPNSID of each VM in the VM. The CSG receives the second notification message sent by the RR, and the CSG can acquire the multiple proxy VPNSIDs according to the second notification message.

The above-mentioned RR is specifically RR2 in FIG. 4 . In addition, the above-mentioned RR sending the second advertisement message to the CSG is also advertised through MP-BGP/EVPN.

In addition, for any VRF, the way for the RR to obtain the VPNSID of each of the VMs connected to the VRF may be as follows: the RR sends a VPNSID obtaining request to the VRF, and the VPNSID obtaining request is used to instruct the VRF to connect to the VRF. The VPNSID of each of the VMs is sent to the RR. That is, in the second implementation manner, the VRF passively sends the VPNSID of each VM connected to the VRF to the RR.

In addition, in the second implementation manner, the corresponding relationship between the VPNSID stored locally in the RR and the proxy VPNSID can be directly configured on the RR by the administrator. In a specific implementation, the administrator can configure multiple proxy VPNSIDs corresponding to the VPNSID of any one of the multiple VMs connected to the VRF on the RR through the management system or the command line, so that the RR can obtain the VRF connection Multiple proxy VPNSIDs corresponding to the VPNSID of any one of the multiple VMs, so as to establish a correspondence between the VPNSID and the proxy VPNSID.

Step 504: For any data center routing node, the data center routing node obtains VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node, and the data center routing node adds the obtained VPNSIDs of multiple VMs to In the second forwarding table corresponding to its own proxy VPNSID.

Among them, the data center routing node can obtain multiple VPNSIDs corresponding to the proxy VPNSID of the data center routing node through the following two specific implementation methods:

A first implementation manner: For any VRF, the VRF acquires multiple proxy VPNSIDs corresponding to the VPNSID of any VM among the multiple VMs connected to any VRF. The VRF issues a third notification message to each data center routing node, where the third notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of any one of the multiple VMs connected to the VRF. For any data center routing node, the data center routing node receives the third notification message sent by the VRF, and according to the proxy VPNSID of the data center routing node, obtains the proxy VPNSID corresponding to the data center routing node from the third notification message The VPNSID of the corresponding VM. After the data center routing node receives all the third notification messages issued by the VRF, it can determine the VPNSIDs of all VMs corresponding to the proxy VPNSID of the data center routing node according to all the third notification messages.

Wherein, the VRF acquires multiple proxy VPNSIDs corresponding to the VPNSID of any one of the multiple VMs connected to any VRF can refer to the first implementation manner in step 503 , which will not be described in detail here.

Based on the communication network shown in FIG. 2, it can be seen that the VRF and the data center routing node are located in the same domain, therefore, the aforementioned VRF issues the third notification message to each data center routing node through an interior network protocol (InteriorGateway Protocol, IGP).

In the above first implementation manner, the VRF actively reports multiple proxy VPNSIDs configured corresponding to the VPNSID of any one of the multiple VMs connected to the VRF to the data center routing node.

The second implementation manner: for any data center routing node, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node are configured by the administrator on the data center routing node. For example, the administrator can directly configure VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node on the data center routing node through a command line or a management system.

The above two implementations of step 503 and step 504 can be used in combination. When the first forwarding table and the second forwarding table are configured through the first implementation in step 503 and the first implementation in step 504, this The configuration mode may also be referred to as a full dynamic configuration mode. In the full dynamic configuration mode, the VRF actively reports the VPNSID of the VM and the corresponding proxy VPNSID, so that the CSG and the data center routing node can obtain the VPNSID of the VM and the corresponding proxy VPNSID, and then configure their respective forwarding tables.

When the first forwarding table and the second forwarding table are configured through the first implementation manner in step 503 and the second implementation manner in step 504, this configuration manner may also be called a semi-dynamic configuration manner. In the semi-dynamic configuration mode, the VRF actively reports the VPNSID of the VM and the corresponding proxy VPNSID to the CSG, so that the CSG configures the first forwarding table, and the administrator directly configures the proxy VPNSID and the corresponding VPNSID of the VM on the routing node of the data center, so that Make the data center routing node generate the second forwarding table.

When the first forwarding table and the second forwarding table are configured through the second implementation manner in step 503 and the second implementation manner in step 504, this configuration manner may also be called a static configuration manner. In the static configuration mode, the VRF does not actively report any information, so the RR needs to obtain the VPNSID of each VM connected to the VRF from the VRF, and then determine the corresponding VPNSID of each VM according to the correspondence between the locally stored VPNSID and the proxy VPNSID. The VPNSID of the proxy is notified to the CSG, and the CSG generates the first forwarding table. Since the VRF does not actively report any information, the data center routing node can only manually configure the VPNSID of the VM corresponding to its own proxy VPNSID through the administrator.

Through the above different implementation manners, the flexibility of configuring the first forwarding table and the second forwarding table is improved.

FIG. 6 is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device 600 can be any node in the communication network in the embodiment shown in FIGS. 1-5 above, such as a CSG, a data center routing node, VRF, etc. The network device 600 may be a switch, a router or other network devices for forwarding packets. In this embodiment, the network device 600 includes: a main control board 610 , an interface board 630 and an interface board 640 . In the case of multiple interface boards, a switching fabric board (not shown in the figure) may be included, and the switching fabric board is used to complete data exchange between interface boards (interface boards are also called line cards or service boards).

The main control board 610 is used to implement functions such as system management, device maintenance, and protocol processing. The interface boards 630 and 640 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.), and implement packet forwarding. There are mainly three types of functional units on the main control board 610: a system management control unit, a system clock unit and a system maintenance unit. The main control board 610, the interface board 630, and the interface board 640 are connected to the system backplane through a system bus to realize intercommunication. The interface board 630 includes one or more processors 631 . The processor 631 is used for controlling and managing the interface board, communicating with the central processing unit on the main control board, and forwarding and processing messages. The memory 632 on the interface board 630 is used to store forwarding entries, and the processor 631 performs message forwarding by looking up the forwarding entries stored in the memory 632 .

The interface board 630 includes one or more network interfaces 633 for receiving messages sent by other devices, and sending the messages according to instructions of the processor 631 . For a specific implementation process, reference may be made to steps 301, 303, 304, and 306 in the embodiment shown in FIG. 3 . I won't repeat them one by one here.

The processor 631 is used to execute the processing steps and functions of any node in the communication network described in the embodiment shown in FIG. 1-5. For details, refer to 302 in the embodiment shown in FIG. processing) or 305 steps (processing as a data center routing node), 501 steps in the embodiment shown in Figure 5 (processing as a VRF), 502 steps (processing as a data center routing node), and 503 steps (processing as a CSG) and step 504 (processing as a data center routing node). I won't repeat them one by one here.

It can be understood that, as shown in FIG. 6, multiple interface boards are included in this embodiment, and a distributed forwarding mechanism is adopted. Under this mechanism, the operations on the interface board 640 are basically similar to the operations on the interface board 630. For simplicity ,No longer. In addition, it can be understood that the processors 631 and/or 641 in the interface board 630 in FIG. One implementation is the so-called forwarding plane using dedicated hardware or chip processing. Refer to the embodiment shown in FIG. 7 below for a specific implementation manner using dedicated hardware or a chip that is a network processor. In another implementation manner, the processor 631 and/or 641 may also use a general-purpose processor, such as a general-purpose CPU, to implement the functions described above.

In addition, it should be noted that there may be one or more main control boards, and when there are multiple main control boards, the main main control board and the standby main control board may be included. There may be one or more interface boards. The stronger the data processing capability of the device, the more interface boards it provides. In the case of multiple interface boards, the multiple interface boards can communicate through one or more switching fabric boards, and when there are multiple interface boards, they can jointly implement load sharing and redundant backup. Under the centralized forwarding architecture, the device does not need a switching network board, and the interface board undertakes the processing function of the service data of the entire system. Under the distributed forwarding architecture, the device includes multiple interface boards, which can realize data exchange between multiple interface boards through the switching network board, and provide large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices with a distributed architecture are greater than those with a centralized architecture. Which architecture to use depends on the specific networking deployment scenario, and there is no limitation here.

In a specific embodiment, the memory 632 can be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or can store Other types of dynamic storage devices for information and instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disc or other magnetic storage device, or capable of carrying or storing desired program code in the form of instructions or data structures and any other medium that can be accessed by a computer, but is not limited to. The memory 632 may exist independently, and is connected to the processor 631 through a communication bus. The memory 632 can also be integrated with the processor 631 .

Wherein, the memory 632 is used to store program codes, which are controlled and executed by the processor 631, so as to implement the path detection method provided by the above-mentioned embodiments. The processor 631 is used to execute program codes stored in the memory 632 . One or more software modules may be included in the program code. The one or more software modules may be the software modules provided in any of the embodiments shown in FIG. 9 and FIG. 10 below.

In a specific embodiment, the network interface 633 may use any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN) and so on.

FIG. 7 is a schematic structural diagram of another network device provided by the embodiment of the present application. The network device 700 can be any node in the communication network in the embodiment shown in FIGS. 1-5 above, such as a CSG or a data center router. Nodes, VRFs, etc. The network device 700 may be a switch, a router or other network devices for forwarding packets. In this embodiment, the network device 700 includes: a main control board 710 , an interface board 730 , a switching fabric board 720 and an interface board 740 . The main control board 710 is used to complete functions such as system management, equipment maintenance, and protocol processing. The SFU 720 is used to implement data exchange between interface boards (interface boards are also called line cards or service boards). The interface boards 730 and 740 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.), and realize data packet forwarding. The control plane is composed of various management and control units on the main control board 710 and management and control units on the interface boards 730 and 740 . There are mainly three types of functional units on the main control board 710: a system management control unit, a system clock unit and a system maintenance unit. The main control board 710, the interface boards 730 and 740, and the switching fabric board 720 are connected to the system backplane through the system bus to realize intercommunication. The central processor 731 on the interface board 730 is used to control and manage the interface board and communicate with the central processor on the main control board. The forwarding entry storage 734 on the interface board 730 is used to store the forwarding entries, and the network processor 732 forwards the message by searching the forwarding entries stored in the forwarding entry storage 734 .

The physical interface card 733 of the interface board 730 is used to receive packets. For a specific implementation process, reference may be made to steps 301 and 304 in the embodiment shown in FIG. 3 . I won't repeat them one by one here.

The network processor 732 is used to execute the processing steps and functions of any node described in the embodiment shown in Figures 1-5, for details, please refer to 302 (processing when serving as a CSG) in the embodiment shown in Figure 3 above Or step 305 (processing as a data center routing node), step 501 (processing as a VRF) in the embodiment shown in Figure 5, step 502 (processing as a routing node in a data center), step 503 (processing as a CSG processing) and step 504 (processing as a data center routing node). I won't repeat them one by one here.

Then, the processed message is sent to other devices through the physical interface card 733 . For a specific implementation process, reference may be made to steps 303 and 306 in the embodiment shown in FIG. 3 . I won't repeat them one by one here.

It can be understood that, as shown in FIG. 7, multiple interface boards are included in this embodiment, and a distributed forwarding mechanism is adopted. Under this mechanism, the operations on the interface board 740 are basically similar to the operations on the interface board 730. For the sake of brevity, ,No longer. In addition, as mentioned above, the functions of the network processors 732 and 742 in FIG. 7 can be replaced by application specific integrated circuits.

In addition, it should be noted that there may be one or more main control boards, and when there are multiple main control boards, the main main control board and the standby main control board may be included. There may be one or more interface boards. The stronger the data processing capability of the device, the more interface boards it provides. There may also be one or more physical interface cards on the interface board. There may be no SFU, or there may be one or more SFUs. When there are multiple SFUs, they can jointly implement load sharing and redundant backup. Under the centralized forwarding architecture, the device does not need a switching network board, and the interface board undertakes the processing function of the service data of the entire system. Under the distributed forwarding architecture, the device can have at least one SFU, through which data exchange between multiple interface boards can be realized, and large-capacity data exchange and processing capabilities can be provided. Therefore, the data access and processing capabilities of network devices with a distributed architecture are greater than those with a centralized architecture. Which architecture to use depends on the specific networking deployment scenario, and there is no limitation here.

FIG. 8 is a schematic structural diagram of an interface board 800 in the network device shown in FIG. 7 provided by an embodiment of the present application. The network device where the interface board 800 is located may be the communication network in the embodiment shown in FIGS. 1-5 above. Any node, for example, may be a CSG, a data center routing node, a VRF, and the like. The interface board 800 may include a physical interface card (physical interface card, PIC) 830, a network processor (network processor, NP) 810, and a traffic management module (traffic management) 820.

Among them, PIC: physical interface card (physical interface card), used to realize the docking function of the physical layer, the original traffic enters the interface board of the network device, and the processed message is sent from the PIC card.

The network processor NP 810 is used to realize packet forwarding and processing. Specifically, the processing of the upstream message includes: the processing of the incoming interface of the message, and the forwarding table search (as related to the first forwarding table or the second forwarding table in the above-mentioned embodiment); the processing of the downstream message: the forwarding table Search (as in the above embodiment related to the relevant content of the first forwarding table or the second forwarding table) and so on.

Traffic management TM 820, used to realize QoS, wire-speed forwarding, large-capacity cache, queue management and other functions. Specifically, upstream traffic management includes: upstream QoS processing (such as congestion management and queue scheduling, etc.) and slice processing; downstream traffic management includes: packet processing, multicast replication, and downstream QoS processing (such as congestion management and queue scheduling, etc. ).

It can be understood that, if the network device has multiple interface boards 800 , the multiple interface boards 800 can communicate through the switching network 840 .

It should be noted that FIG. 8 only shows a schematic processing flow or modules inside the NP, and the processing order of each module in specific implementation is not limited thereto, and other modules or processing flows can be deployed as required in actual applications. The comparison of the examples in this application is not limited.

FIG. 9 is a schematic structural diagram of a CSG provided by an embodiment of the present application. Wherein, the communication network further includes multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF, and each of the multiple VRFs is connected to one or more of the aforementioned multiple VMs . Each of the aforementioned multiple VMs is configured with a VPNSID, and each of the aforementioned multiple data center routing nodes is configured with a proxy VPNSID.

As shown in Figure 9, the CSG 900 includes:

The receiving module 901 is configured to receive a message, and the message carries the identifier of the target VNF. For a specific implementation manner, refer to step 301 in the embodiment in FIG. 3 .

The selection module 902 is configured to select a proxy VPNSID from the multiple proxy VPNSIDs included in the first forwarding table as the target proxy VPNSID. For a specific implementation manner, refer to step 302 in the embodiment in FIG. 3 .

The forwarding module 903 is configured to use the target proxy VPNSID as the destination address to forward the packet, so as to forward the packet to the data center routing node indicated by the target proxy VPNSID, and to indicate that the data center routing node indicated by the target proxy VPNSID according to the second Multiple VPNSIDs included in the forwarding table forward packets. Wherein, the first forwarding table is a forwarding table corresponding to the identifier of the target VNF, and the multiple proxy VPNSIDs included in the first forwarding table refer to the proxy VPNSIDs configured corresponding to the VPNSIDs of multiple VMs. The multiple VPNSIDs included in the second forwarding table refer to the VPNSID of the VM corresponding to the target proxy VPNSID among the VPNSIDs of the multiple VMs. For a specific implementation manner, refer to step 303 in the embodiment in FIG. 3 .

Optionally, the CSG further includes an adding module, configured to obtain proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs, and add the obtained proxy VPNSIDs to the first forwarding table.

Optionally, the above-mentioned adding module is specifically configured to: receive a first notification message sent by any one of the multiple VRFs, where the first notification message carries the multiple proxy VPNSID.

Optionally, the communications network further includes RRs. At this time, the above adding module is specifically configured to: receive a second notification message sent by the RR, where the second notification message carries proxy VPNSIDs corresponding to VPNSIDs of multiple VMs.

For the technical effect of each module included in the CSG provided in the fifth aspect, reference may be made to the packet forwarding method provided in the first aspect, and will not be described in detail here.

In the embodiment of the present application, in order to avoid being limited by the maximum number of load sharing routes of the CSG, a proxy VPNSID may be configured for each data center routing node. For the VPNSID of any VM, configure multiple proxy VPNSIDs corresponding to the VPNSID of the VM. In this way, the proxy VPNSID can be used in the local forwarding table of the CSG to replace the VPNSID of the original VM, so that the CSG only needs to be responsible for sharing the load to each data center routing node during load sharing, and each data center routing node Complete the actual load sharing. However, the maximum number of load sharing paths of the data center routing nodes can be as high as 128. Therefore, the message forwarding method provided by the embodiment of the present application is equivalent to increasing the number of paths for CSG to finally perform load sharing, thereby improving the efficiency of load sharing. .

It should be noted that when the CSG provided in the above embodiment performs message forwarding, the division of the above functional modules is used as an example for illustration. In practical applications, the above function allocation can be completed by different functional modules according to needs. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the CSG provided in the foregoing embodiments and the packet forwarding method embodiments belong to the same idea, and the specific implementation process thereof is detailed in the method embodiments, and will not be repeated here.

FIG. 10 is a schematic structural diagram of any data center routing node among multiple data center routing nodes in a communication network provided by an embodiment of the present application. The communication network further includes a CSG, multiple VRFs, and multiple VMs for executing the target VNF, and each VRF is connected to one or more of the multiple VMs. Wherein, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

As shown in Figure 10, the data center routing node 1000 includes:

The receiving module 1001 is configured to receive a message sent by the CSG, and the message carries the target proxy VPNSID. For a specific implementation manner, refer to step 304 in the embodiment in FIG. 3 .

The selection module 1002 is configured to select a VPNSID from multiple VM VPNSIDs included in the second forwarding table when the target proxy VPNSID carried in the message is the proxy VPNSID of any data center routing node. For a specific implementation manner, refer to step 305 in the embodiment in FIG. 3 .

A forwarding module 1003, configured to use the selected VPNSID as the destination address to forward the message. Wherein, the multiple VPNSIDs included in the second forwarding table refer to multiple VM VPNSIDs corresponding to the proxy VPNSID of the data center routing node. For a specific implementation manner, refer to step 306 in the embodiment in FIG. 3 .

Optionally, the data center routing node also includes:

An adding module, configured to obtain the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node, and add the obtained VPNSIDs of the VMs to the second forwarding table.

Optionally, the aforementioned acquisition module is specifically configured to: receive a third notification message sent by any one of the multiple VRFs, where the third notification message carries multiple agents corresponding to the VPNSID of each VM in each VM connected to any VRF VPNSID: Obtain the VPNSID of the VM corresponding to the proxy VPNSID of the data center routing node from the third notification message according to the proxy VPNSID of the data center routing node.

Optionally, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node are configured on the data center routing node by a manager.

In the embodiment of the present application, in order to avoid being limited by the maximum number of load sharing routes of the CSG, a proxy VPNSID may be configured for each data center routing node. For the VPNSID of any VM, configure multiple proxy VPNSIDs corresponding to the VPNSID of the VM. In this way, the proxy VPNSID can be used in the local forwarding table of the CSG to replace the VPNSID of the original VM, so that the CSG only needs to be responsible for sharing the load to each data center routing node during load sharing, and each data center routing node Complete the actual load sharing. However, the maximum number of load sharing paths of the data center routing nodes can be as high as 128. Therefore, the message forwarding method provided by the embodiment of the present application is equivalent to increasing the number of paths for CSG to finally perform load sharing, thereby improving the efficiency of load sharing. .

It should be noted that when the data center routing node provided in the above embodiment forwards messages, it only uses the division of the above functional modules as an example. In practical applications, the above functions can be assigned to different functional modules according to needs. Completion means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the data center routing node and the message forwarding method embodiment provided by the above embodiment belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

In addition, the embodiment of the present application also provides any one of multiple VRFs in a communication network, where the communication network further includes a CSG, multiple data center routing nodes, multiple VMs for executing target VNFs, multiple One or more of the multiple VMs are connected to each VRF in the VRFs. Wherein, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

The VRF includes:

An obtaining module, configured to obtain multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to the VRF.

The issuing module is configured to issue a first notification message to the CSG, where the first notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to the VRF.

Optionally, the issuing module is further configured to issue a third notification message to multiple data center routing nodes, where the third notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to the VRF.

In this embodiment of the application, the VRF can actively report to the CSG the multiple proxy VPNSIDs corresponding to the VPNSID of each VM in each VM connected to it, so that the CSG can build the first forwarding table, which improves the efficiency of the CSG to build the first forwarding table .

It should be noted that when the VRF provided in the above embodiment performs message forwarding, it only uses the division of the above functional modules as an example for illustration. In practical applications, the above function allocation can be completed by different functional modules according to needs. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the VRF provided in the foregoing embodiment is based on the same idea as the packet forwarding method embodiment, and its specific implementation process is detailed in the method embodiment, and will not be repeated here.

In addition, the embodiment of the present application also provides an RR in a communication network. The communication network also includes a CSG, multiple data center routing nodes, multiple VRFs, and multiple VMs for executing the target VNF, and each VRF is connected to one or more of the multiple VMs. Each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID.

The RR includes:

The acquiring module is configured to acquire the VPNSID of each of the multiple VMs connected to any VRF in the multiple VRFs; for the obtained VPNSID of any VM, the RR determines the VPNSID based on the correspondence between the locally stored VPNSID and the proxy VPNSID The proxy VPNSID corresponding to the VPNSID of the VM obtains multiple proxy VPNSIDs corresponding to the VPNSID of each VM in a plurality of VMs connected to any VRF;

An issuing module, configured to send a second notification message to the CSG, where the second notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to each of the multiple VRFs.

Optionally, the corresponding relationship between the VPNSID locally stored in the RR and the proxy VPNSID is configured by the administrator on the RR, thereby improving the flexibility of the CSG in constructing the first forwarding table.

When the RR reports the proxy VPNSIDs corresponding to the VPNSIDs of multiple VMs to the CSG, and the CSG constructs the first forwarding table, the RR needs to obtain multiple proxy VPNSIDs corresponding to the VPNSIDs of each of the multiple VMs first, and then send The CSG sends the second notification message so that the CSG can build the first forwarding table, which improves the flexibility of the CSG to build the first forwarding table.

It should be noted that when the RR provided in the above embodiment forwards packets, it only uses the division of the above functional modules as an example for illustration. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the RR provided in the foregoing embodiments belongs to the same idea as the embodiment of the packet forwarding method, and its specific implementation process is detailed in the method embodiment, and will not be repeated here.

In addition, the embodiment of the present application also provides a message forwarding system, the system includes CSG, multiple data center routing nodes, multiple virtual routing and forwarding VRFs, and multiple VMs for executing the target virtual network function VNF, the Each of the multiple VRFs is connected to one or more of the multiple VMs, each of the multiple VMs is configured with a virtual private network segment identifier VPNSID, and each of the multiple data center routing nodes The central routing node is configured with a proxy VPNSID;

The CSG is configured to obtain proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs, and add the obtained proxy VPNSIDs to the first forwarding table;

Any data center routing node among the plurality of data center routing nodes is configured to obtain VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node, and add the obtained VPNSIDs of VMs to the second forwarding table.

Optionally, the CSG is specifically configured to: receive a first notification message sent by any one of the multiple VRFs, where the first notification message carries multiple proxies corresponding to the VPNSID of each of the VMs connected to the any VRF VPNSID.

Optionally, the CSG is specifically configured to: the CSG receives a second notification message sent by the RR, where the second notification message carries proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs.

Optionally, the data center routing node is configured to receive a third notification message sent by any VRF among the plurality of VRFs, where the third notification message carries the VPNSID corresponding to each VM among the VMs connected to any VRF. A plurality of proxy VPNSIDs; according to the proxy VPNSID of the data center routing node, obtain the VPNSID of the VM corresponding to the proxy VPNSID of the data center routing node from the third notification message.

Optionally, the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the data center routing node are configured on the data center routing node by a manager.

The functions of each node in the above packet forwarding system have been described in detail in the foregoing embodiments, and will not be described here again.

FIG. 11 is a schematic structural diagram of a network device 1100 provided by an embodiment of the present application. Any node in the communication network in the embodiments of Fig. 1 to Fig. 5, such as CSG, data center routing node, VRF, etc., can be realized by the network device 1100 shown in Fig. 11. At this time, the network device 1100 can be a switch, Routers or other network devices that forward packets. In addition, the network controller in the embodiment shown in FIG. 1 to FIG. 5 can also be realized by the network device 1100 shown in FIG. The specific implementation manner of the network controller will not be repeated here. Referring to FIG. 11 , the device includes at least one processor 1101 , a communication bus 1102 , a memory 1103 and at least one communication interface 1104 .

The processor 1101 may be a general-purpose central processing unit (central processing unit, CPU), an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits for controlling the execution of programs in the solution of this application.

Communication bus 1102 may include a path for communicating information between the components described above.

The memory 1103 may be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or other types that can store information and instructions The dynamic storage device can also be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc (compactdisc read-only memory, CD-ROM) or other optical disc storage, optical disc storage ( including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disks or other magnetic storage devices, or any other storage device capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer Any other medium, but not limited thereto. The memory 1103 may exist independently, and is connected to the processor 1101 through the communication bus 1102 . The memory 1103 may also be integrated with the processor 1101 .

Wherein, the memory 1103 is used to store program codes, which are controlled and executed by the processor 1101, so as to execute the path detection method provided by any one of the above-mentioned embodiments. The processor 1101 is used to execute program codes stored in the memory 1103 . One or more software modules may be included in the program code. Any node in the communication network in the embodiments provided in FIGS. 1 to 5 may determine data for developing an application through the processor 1101 and one or more software modules in the program code in the memory 1103 . The one or more software modules may be the software modules provided in any of the embodiments in FIG. 9 and FIG. 10 .

The communication interface 1104 uses any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (radio access network RAN), wireless local area network (wireless local area networks, WLAN) and so on.

In a specific implementation, as an embodiment, a network device may include multiple processors, for example, processor 1101 and processor 1105 shown in FIG. 11 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In the above embodiments, all or part may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example: floppy disk, hard disk, magnetic tape), an optical medium (for example: digital versatile disc (digital versatile disc, DVD)), or a semiconductor medium (for example: solid state disk (solid state disk, SSD) )wait.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, and the like.

The above-mentioned embodiments provided by the application are not intended to limit the application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the application shall be included in the protection scope of the application. Inside.

Claims (21)

1. A message forwarding method, characterized in that it is applied to a base station service gateway CSG in a communication network, and the communication network also includes a plurality of data center routing nodes, a plurality of virtual routing and forwarding VRFs, and is used to perform target virtualization A plurality of virtual machine VMs of the network function VNF, each of the plurality of VRFs is connected to one or more of the plurality of VMs; each of the plurality of VMs is configured with a virtual private network segment Identify VPNSID, each data center routing node in the plurality of data center routing nodes is configured with a proxy VPNSID; The methods include: The CSG receives a message, and the message carries the identifier of the target VNF; The CSG selects a proxy VPNSID as the target proxy VPNSID from multiple proxy VPNSIDs included in the first forwarding table, the first forwarding table is a forwarding table corresponding to the target VNF identifier, and the first forwarding table includes Multiple proxy VPNSIDs refer to proxy VPNSIDs configured correspondingly to the VPNSIDs of the multiple VMs, and the VPNSIDs of each VM are correspondingly configured with multiple proxy VPNSIDs; The CSG uses the target proxy VPNSID as the destination address to forward the message, so as to forward the message to the data center routing node indicated by the target proxy VPNSID, for indicating the target proxy VPNSID indicated The data center routing node forwards the message according to the multiple VPNSIDs included in the second forwarding table, where the multiple VPNSIDs included in the second forwarding table refer to the VM corresponding to the target proxy VPNSID among the VPNSIDs of the multiple VMs The VPNSID. 2. The method of claim 1, further comprising: The CSG acquires proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs, and adds the acquired proxy VPNSIDs to the first forwarding table. 3. The method according to claim 2, wherein the CSG obtains proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs, comprising: The CSG receives a first notification message sent by any VRF among the plurality of VRFs, where the first notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the VMs connected to the any VRF. 4. The method according to claim 2, wherein the communication network further comprises a route reflector RR; the CSG acquiring proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs comprises: The CSG receives the second notification message sent by the RR, where the second notification message carries proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs. 5. A message forwarding method, characterized in that it is applied to any data center routing node in a plurality of data center routing nodes in a communication network, and the communication network also includes a CSG, a plurality of VRFs, and is used to execute target A plurality of VMs of the VNF, one or more of the plurality of VMs are connected to each VRF; each VM in the plurality of VMs is configured with a VPNSID, and each data center routing node in the plurality of data centers The central routing node is configured with a proxy VPNSID; The methods include: The any data center routing node receives the message sent by the CSG, and the message carries the target proxy VPNSID; In the case where the target proxy VPNSID carried in the message is the proxy VPNSID of any data center routing node, the any data center routing node selects a VPNSID from the VPNSIDs of multiple VMs included in the second forwarding table , the multiple VPNSIDs included in the second forwarding table refer to the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of any data center routing node, and the VPNSID of each VM is correspondingly configured with multiple proxy VPNSIDs; The any data center routing node forwards the packet using the selected VPNSID as the destination address. 6. The method of claim 5, further comprising: The any data center routing node acquires the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the any data center routing node, and adds the acquired VPNSIDs of the VMs to the second forwarding table. 7. The method according to claim 6, wherein said any data center routing node obtains the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of said any data center routing node, comprising: The any data center routing node receives a third notification message sent by any VRF among the plurality of VRFs, where the third notification message carries the multiple information corresponding to the VPNSID of each VM among the VMs connected to the any VRF. proxy VPNSID; The any data center routing node obtains the VPNSID of the VM corresponding to the proxy VPNSID of the any data center routing node from the third notification message according to the proxy VPNSID of the any data center routing node. 8. The method according to claim 6, wherein the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of any data center routing node are configured by a manager on the any data center routing node. 9. A message forwarding method, characterized in that it is applied to any VRF among multiple VRFs in a communication network, and the communication network further includes a CSG, multiple data center routing nodes, and multiple VNFs for executing target VNFs. VMs, each of the plurality of VRFs is connected to one or more of the plurality of VMs; each of the plurality of VMs is configured with a VPNSID, and among the plurality of data center routing nodes Each data center routing node is configured with a proxy VPNSID; The methods include: The any VRF acquires multiple proxy VPNSIDs corresponding to the VPNSID of each VM in the multiple VMs connected to the any VRF; The any VRF issues a first notification message to the CSG, and the first notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to the any VRF, so that the CSG When forwarding the message carrying the identifier of any VRF, select a proxy VPNSID as the target proxy VPNSID from the multiple proxy VPNSIDs corresponding to the VPNSID of each VM in the multiple VMs connected to the any VRF, and set The target proxy VPNSID is used as the destination address to forward the message. 10. The method according to claim 9, wherein after said any VRF acquires multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to said any VRF, further comprising: The any VRF issues a third notification message to the multiple data center routing nodes, where the third notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each VM among the multiple VMs connected to the any VRF. 11. A message forwarding method, characterized in that it is applied to an RR in a communication network, and the communication network further includes a CSG, a plurality of data center routing nodes, a plurality of VRFs, and a plurality of VMs for executing a target VNF, One or more of the multiple VMs are connected to each VRF; each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a VPNSID Proxy VPNSID; The methods include: The RR obtains the VPNSID of each VM in the multiple VMs connected to any VRF in the multiple VRFs; For the obtained VPNSID of any VM, the RR determines the proxy VPNSID corresponding to the VPNSID of any VM based on the correspondence between the locally stored VPNSID and the proxy VPNSID, and obtains multiple VMs connected to the any VRF Multiple proxy VPNSIDs corresponding to the VPNSID of each VM in ; The RR sends a second notification message to the CSG, where the second notification message carries multiple proxy VPNSIDs corresponding to the VPNSID of each of the multiple VMs connected to each VRF in the multiple VRFs, so that When the CSG forwards the message carrying the identifier of any VRF, select a proxy VPNSID as the target proxy VPNSID from the multiple proxy VPNSIDs corresponding to the VPNSID of each VM in the multiple VMs connected to the any VRF , and forward the message with the target proxy VPNSID as the destination address. 12. The method according to claim 11, wherein the corresponding relationship between the VPNSID and the proxy VPNSID is configured on the RR by a manager. 13. A CSG in a communication network, the communication network further comprising a plurality of data center routing nodes, a plurality of virtual routing and forwarding VRFs, and a plurality of VMs for executing a target virtual network function VNF, among the plurality of VRFs Each VRF is connected to one or more of the plurality of VMs, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with a VPNSID Proxy VPNSID; It is characterized in that the CSG includes a memory and a processor; The memory is used to store computer programs; The processor is used to execute the program stored in the memory to execute the method according to any one of claims 1-4. 14. A data center routing node in a communication network, the communication network comprising multiple data center routing nodes, a CSG, multiple VRFs, and multiple VMs for executing target VNFs, each VRF is connected to the multiple One or more of the VMs, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID; It is characterized in that any data center routing node in the plurality of data center routing nodes includes a memory and a processor; The memory is used to store computer programs; The processor is used to execute the program stored in the memory to execute the method according to any one of claims 5-8. 15. A VRF in a communication network, the communication network comprising multiple VRFs, CSGs, multiple data center routing nodes, and multiple VMs for executing target VNFs, each of the multiple VRFs is connected to a One or more of the plurality of VMs, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with a proxy VPNSID; It is characterized in that any VRF in the plurality of VRFs includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the program stored in the memory to perform the method according to any one of claims 9-10. 16. An RR in a communication network, the communication network further comprising a CSG, a plurality of data center routing nodes, a plurality of VRFs, and a plurality of VMs for executing a target VNF, and each VRF is connected to the plurality of VMs One or more of them, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes is configured with a proxy VPNSID; It is characterized in that the RR includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the program stored in the memory to perform the method according to any one of claims 11-12. 17. A chip, the chip is set in a CSG in a communication network, and the communication network further includes a plurality of data center routing nodes, a plurality of virtual routing and forwarding VRFs, and a plurality of VNFs for executing target virtual network functions VM, each of the multiple VRFs is connected to one or more of the multiple VMs, each of the multiple VMs is configured with a VPNSID, and each of the multiple data center routing nodes Each data center routing node is configured with a proxy VPNSID; It is characterized in that the chip includes a processor and an interface circuit; The interface circuit is used to receive instructions and transmit them to the processor; The processor is configured to execute the method according to any one of claims 1-4. 18. A chip, the chip is set in any one of the multiple data center routing nodes included in the communication network, and the communication network further includes a CSG, multiple VRFs, multiple VNFs for executing target VNFs VMs, one or more of the plurality of VMs are connected to each VRF, each VM in the plurality of VMs is configured with a VPNSID, and each data center routing node in the plurality of data center routing nodes Configured with a proxy VPNSID; It is characterized in that the chip includes a processor and an interface circuit; The interface circuit is used to receive instructions and transmit them to the processor; The processor is configured to execute the method according to any one of claims 5-8. 19. A chip, the chip is set in any one of a plurality of VRFs included in a communication network, the communication network further comprising a CSG, a plurality of data center routing nodes, and a plurality of VMs for executing a target VNF, Each of the plurality of VRFs is connected to one or more of the plurality of VMs, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes The central routing node is configured with a proxy VPNSID; It is characterized in that the chip includes a processor and an interface circuit; The interface circuit is used to receive instructions and transmit them to the processor; The processor is configured to execute the method according to any one of claims 9-10. 20. A chip, the chip is set in the RR of the communication network, the communication network also includes CSG, multiple data center routing nodes, multiple VRFs, multiple VMs for executing the target VNF, each VRF One or more of the plurality of VMs are connected, each of the plurality of VMs is configured with a VPNSID, and each of the plurality of data center routing nodes is configured with a proxy VPNSID; It is characterized in that the chip includes a processor and an interface circuit; The interface circuit is used to receive instructions and transmit them to the processor; The processor is configured to execute the method according to any one of claims 11-12. 21. A message forwarding system, characterized in that the system includes CSG, multiple data center routing nodes, multiple virtual routing and forwarding VRFs, and multiple VMs for executing target virtual network functions VNFs, the multiple One or more of the multiple VMs are connected to each of the VRFs, each of the multiple VMs is configured with a virtual private network segment identifier VPNSID, and each of the multiple data center routing nodes Each data center routing node is configured with a proxy VPNSID; The CSG is configured to acquire proxy VPNSIDs corresponding to the VPNSIDs of the multiple VMs, and add the acquired proxy VPNSIDs to the first forwarding table; Any data center routing node among the plurality of data center routing nodes is configured to obtain the VPNSIDs of multiple VMs corresponding to the proxy VPNSID of the any data center routing node, and add the obtained VPNSIDs of the VMs to the second transfer Publishing.

Images