WO2020220459A1

WO2020220459A1 - Vxlan and openflow-based method and system for sharing virtual home network

Info

Publication number: WO2020220459A1
Application number: PCT/CN2019/094124
Authority: WO
Inventors: 喻晶洁; 何奥林; 姚洁
Original assignee: 烽火通信科技股份有限公司
Priority date: 2019-04-30
Filing date: 2019-07-01
Publication date: 2020-11-05
Also published as: CN109936490A; CN109936490B

Abstract

The present invention relates to the field of data message forwarding, and disclosed thereby are a VXLAN and OpenFlow-based method and system for sharing a virtual home network. The method comprises: establishing a VXLAN connection, and connecting a vG end and a pG end of virtual homes; newly establishing a VXLAN connection between virtual homes, and modifying a VXLAN FDB table of the newly established VXLAN connection so that a two-layer network between the virtual homes may be achieved; the vG end multicasting resources contained thereby to a pG end hanging device by means of a multicasting manner; the pG end hanging device notifying the vG end about resources required thereby by means of a unicasting manner; and the vG end sending the resources required by the pG end hanging device by means of a unicasting manner. The present invention may enable data message transmission between various virtual homes, thus implementing resource sharing.

Description

Virtual home network sharing method and system based on VXLAN and OpenFlow

Technical field

The present invention relates to the field of data message forwarding, in particular to a virtual home network sharing method and system based on VXLAN (Virtual Extensible LAN) and OpenFlow (communication protocol).

Background technique

The virtual home gateway is divided into two parts, the vG (virtual gateway) end placed in the data center server and the pG (physical gateway) placed in the user's home, between the vG end and the pG end of the virtual home Use VXLAN to connect. The vG end is equivalent to the server side, and the pG end is equivalent to the user side.

For virtual home gateways, traditional network isolation mainly uses VLANs (Virtual Local Area Network, virtual local area network). However, due to the large number of home gateways in the data center, the overlay method is generally used to isolate families. However, with the Overlay approach, there is currently no effective solution to how families can share access to data center server-side resources.

Summary of the invention

The invention discloses a virtual home network sharing method and system based on VXLAN and OpenFlow, which can enable data message transmission between virtual homes and realize resource sharing.

A virtual home network sharing method based on VXLAN and OpenFlow provided by the present invention includes the following steps:

Create a VXLAN connection to connect the vG end and pG end of the virtual home;

Create a new VXLAN connection between virtual homes and modify the VXLAN FDB table of the newly created VXLAN connection to make the second-tier network between the virtual homes reachable;

The vG end multicasts its own resources to the device connected to the pG end through multicast;

The device attached to the pG end informs the vG end of its required resources through unicast;

The vG end sends the resources required by the device connected to the pG end through unicast.

On the basis of the above scheme,

Before the vG end multicasts its own resources to all pG end-linked devices in a multicast manner, it specifically includes:

Modify the FDB table of the VXLAN connection on the vG side to the VTEP side so that the multicast packets on the vG side can reach the pG side;

Modify the OpenFlow flow table on the vG side to make the source IP address of the vG side an unused IP address;

Before the pG end-linked device notifies the vG end of its required resources through unicast, it specifically includes:

Modify the FDB table of the VXLAN connection on the pG end to the VTEP end so that the unicast packets of the device connected to the pG end can reach the vG end;

Modify the OpenFlow flow table on the pG end so that the source IP address of the packet sent by the device attached to the pG end to the vG end is an unused IP address.

On the basis of the above solution, modify the FDB table of the VXLAN connection on the vG side to the VTEP side, and modify the OpenFlow flow table on the vG side, including:

Perform IP mapping in the virtual switch on the vG side, and map the source IP address of the vG side to the unused first IP address by issuing the OpenFlow flow table;

Modify the FDB table on the VTEP side in the newly created VXLAN connection on the vG side, and map the destination mac address of the multicast packet to the vtep endpoint on the pG side.

On the basis of the above solution, modify the FDB table of the VXLAN connection of the pG end to the VTEP end, and modify the OpenFlow flow table of the pG end, including:

IP mapping is performed in the virtual switch on the pG end, and the OpenFlow flow table is issued to map the source IP address of the packet sent by the device at the pG end to the vG end to the unused second IP address;

Modify the ARP table in the virtual switch on the pG side to correspond the first IP address to the mac address on the vG side;

Connect the pG end VXLAN to the VTEP end FDB table, the mac address of the vG end corresponds to the vG end VTEP endpoint.

On the basis of the foregoing solution, before the vG end sends the resources required by the pG end-linked device through unicast, it further includes:

Perform IP mapping in the virtual switch on the vG side, and map the source IP address of the vG side to the first IP address by issuing the OpenFlow flow table;

Modify the ARP table in the virtual switch on the vG end to correspond the second IP address to the mac address of the device connected to the pG end;

Connect the newly created VXLAN at the vG end to the FDB table at the VTEP end. The mac address of the device connected to the pG end corresponds to the VTEP end point of the pG end.

A virtual home network sharing system based on VXLAN and OpenFlow provided by the present invention includes:

The first creation module, which is used to create a VXLAN connection and connect the vG end and the pG end of the virtual home gateway;

The second creation module is used to create a new VXLAN connection between virtual homes and modify the VXLAN FDB table of the newly created VXLAN connection to make the second-tier network between the virtual homes reachable;

Multicast module, which is used to drive the vG end to broadcast its own resources to the pG end-linked device through multicast;

The first unicast module, which is used to drive the device connected to the pG end to inform the vG end of the resources it needs by unicasting;

The second unicast module is used to drive the vG end to send the resources required by the device connected to the pG end in a unicast manner.

On the basis of the above scheme,

Before the vG end broadcasts its own resources in a multicast manner, it specifically includes:

Modify the FDB table of the newly created VXLAN connection on the VTEP side on the vG side so that the multicast packets on the vG side can reach the pG side;

On the basis of the above solution, modify the FDB table on the vG side to create a new VXLAN connection to the VTEP side, and modify the OpenFlow flow table on the vG side, including:

Perform IP mapping in the virtual switch on the pG end, and by issuing an OpenFlow flow table, map the source IP address of the packet sent by the device at the pG end to the vG end to an unused second IP address;

Compared with the prior art, the present invention has the advantage of creating a new VXLAN connection between virtual homes and modifying the VXLAN FDB table of the newly created VXLAN connection, so that the second layer network between the virtual homes can be reached, so that the vG of a virtual home The terminal can communicate with devices connected to the pG end of other virtual homes, and other virtual homes can obtain resources on the vG end of the virtual home, and the vG end and the pG end of each virtual home can transmit data messages to realize resource sharing.

Description of the drawings

Figure 1 is a flowchart of a method for virtual home network sharing based on VXLAN and OpenFlow in an embodiment of the present invention;

Figure 2 is a schematic diagram of the process of a multicast message sent from the vG end to the pG end in an example of the present invention;

FIG. 3 is a schematic diagram of the process in which the device attached to the pG end in the example of the present invention responds to a message in a unicast manner to inform the vG end of its required resources;

Fig. 4 shows that the vG end transmits resources to the pG end-linked device through unicast in the example of the present invention;

Figure 5 shows the FDB table format saved in the VXLAN endpoint VTEP in the example of the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the drawings and embodiments. Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

The embodiment of the present invention provides a virtual home network sharing method based on VXLAN and OpenFlow. By creating a VXLAN connection between virtual homes, and modifying the VXLAN FDB table of the newly created VXLAN connection, the second layer network between the virtual homes can be reached, so that a certain The vG end of a virtual home can communicate with the pG end of other virtual homes, and other virtual homes can obtain the resources of the vG end of the virtual home to realize resource sharing. The embodiment of the present invention also correspondingly provides a virtual home network sharing system based on VXLAN and OpenFlow.

Referring to FIG. 1, an embodiment of a method for sharing a virtual home network based on VXLAN and OpenFlow provided by an embodiment of the present invention includes:

S1: Create a VXLAN connection to connect the vG end and pG end of the virtual home;

In the embodiment of the present invention, the pG terminal corresponds to the access device on the user side in the virtual home, and is used to access terminal devices such as mobile phones and computers in the home. It can be understood that each pG corresponds to a virtual home vG. The vG end and the pG end of each virtual home are connected by VXLAN, and the vG end and the pG end use a virtual switch that supports the OpenFlow protocol.

S2: Create a new VXLAN connection between the virtual homes, and modify the VXLAN FDB table of the newly created VXLAN connection to make the second-tier network between the virtual homes reachable;

In the embodiment of the present invention, by modifying the VXLAN connection VXLAN FDB table between the virtual homes, data between the virtual homes can be communicated, that is, data packet transmission can be performed between the vG end and the pG end of each virtual home.

In the actual application process, there are multiple virtual homes, but there may be only two virtual homes that need to share data at a certain time. For example, virtual home A and virtual home B, then create a new VXLAN between virtual home A and virtual home B Connect, and then modify the VXLAN connection VXLAN FDB table between virtual home A and virtual home B, so that the second layer link is reachable between virtual home A and virtual home B, and the data is interoperable. Virtual home A can obtain resources from the vG end of virtual home B In the same way, the virtual home B can also obtain the resources of the vG end of the virtual home A. FDB (Forwarding Data Base) table, that is, MAC address forwarding table.

S3: The vG end broadcasts its own resources to the pG end through multicast;

S4: The devices connected to the pG end (computers, mobile phones, etc.) inform the vG end of its own resources through unicast;

S5: The vG end sends the resources required by the device connected to the pG end through unicast.

In the embodiment of the present invention, when vG-side resource sharing between virtual homes is performed, the vG-side informs the pG-side connected device of the resources provided by itself through multicast, and the pG-side downlink device informs the resource provided by the vG-side The resources required by the vG end itself, and the vG end transmits the resources to the devices connected to the pG end through unicast.

A method for sharing a virtual home network based on VXLAN and OpenFlow in an embodiment of the present invention is to create a VXLAN connection between virtual homes and modify the VXLAN FDB table of the newly created VXLAN connection to make the second-tier network between the virtual homes reachable, so that a certain The vG end of a virtual home can send multicast packets to other virtual home pG end-linked devices, and other virtual home pG end-linked devices can obtain resources of the virtual home vG end. Between the vG end and the pG end of each virtual home It can carry out data message transmission and realize resource sharing.

Optionally, on the basis of the corresponding embodiment of the above-mentioned VXLAN and OpenFlow-based virtual home network sharing method, the first optional implementation of the VXLAN and OpenFlow-based virtual home network sharing method provided by the embodiment of the present invention In the example, before the vG end multicasts its own resources to all the pG end-connected devices through multicast, the specific steps include: modifying the FDB table of the newly created VXLAN connection VTEP end at the vG end so that the multicast packets on the vG end can reach the pG end; Modify the OpenFlow flow table on the vG side so that the source IP address of the vG side is an unused IP address, that is, an unused IP address before, to avoid conflicts with existing IP addresses. VTEP, namely VXLAN Tunnel End Point, is responsible for VXLAN encapsulation and decapsulation of original Ethernet packets.

Before the device linked to the pG end informs the vG end of its required resources through unicast, the specific steps include: modifying the FDB table of the VXLAN connection on the pG end to the VTEP end, so that the unicast packets of the device linked to the pG end can reach the vG end; modifying the pG end OpenFlow flow table, so that the source IP address of the packet sent by the device attached to the pG to the vG end is an unused IP address, that is, an unused IP address before, so as to avoid conflicts with existing IP addresses.

Optionally, on the basis of the foregoing VXLAN and OpenFlow-based virtual home network sharing method corresponding to the first optional embodiment, the embodiment of the present invention provides a VXLAN and OpenFlow-based virtual home network sharing method in the first embodiment. In the two alternative embodiments, modifying the FDB table of the VXLAN connection on the vG side to the VTEP side and modifying the OpenFlow flow table on the vG side includes:

Modify the FDB table of the VXLAN connection on the pG side to the VTEP side, and modify the OpenFlow flow table on the pG side, including:

Perform IP mapping in the virtual switch on the pG side, and by issuing the OpenFlow flow table, map the IP address of the packet sent to the vG side by the device connected to the pG side to the unused second IP address;

Modify the ARP table in the pG virtual switch to map the first IP address to the mac address of the vG end;

Optionally, on the basis of the foregoing VXLAN and OpenFlow-based virtual home network sharing method corresponding to the second optional embodiment, the embodiment of the present invention provides a VXLAN and OpenFlow-based virtual home network sharing method in the first In the three optional embodiments, before the vG side sends the resources required by the pG-connected device in unicast mode, it further includes:

The following uses an example to inform the vG end of the embodiment of the present invention of the resources provided by other pG offline devices through multicast. The pG offline device learns the resources provided by the vG end and informs the vG end of the resources it needs. The resource is transmitted to the device connected to the pG end in a unicast mode, and the above process is described in detail.

As shown in Figure 2, the vG end is equivalent to the server side of the virtual home gateway, and the pG end is equivalent to the user side of the virtual home gateway. A vSwitch is deployed in vG and pG, and accepts the control of the controller through the OpenFlow protocol, so that the quintuple information of the data message can be modified. NC (Network Card) stands for network card, and the VXLAN tunnel endpoint is vtep. The agent (pG2Agent is omitted and not shown in Figure 2) accepts the management of the controller to configure the VXLAN FDB table of vtep. In the process of informing other pG-connected devices of the resources provided by the vG end through multicast, the multicast packet sent from the vG end to the pG end has the following processing logic:

VXLAN source endpoint (vG side) is vtep1, source IP address is ip1, source mac address is mac1; VXLAN destination endpoint (pG side) is vtep2, destination IP address is multicast address ip_multi, destination mac address is multicast mac address mac_multi .

IP mapping is performed in the virtual switch on the vG side, and the source IP address ip1 is mapped to ip1_new by issuing the OpenFlow flow table (this address is a reserved address and will not cause address conflicts between different families), and the VXLAN FDB table on the vG side is modified at the same time , Corresponding to mac_multi as VXLAN endpoint vtep2;

For the multicast packet received by the pG end, the source MAC address is mac1, the source IP address is ip1_new, the destination MAC address is mac_multi, and the destination IP address is ip_multi.

As shown in Figure 3, the pG-side attached device informs the vG side of the resources it needs after learning the resources provided by the vG side. In the process, the pG-side attached device replies with a unicast message to inform the vG side of the resources it needs. The logic is as follows:

The VXLAN endpoint of the vG end is vtep1, the IP address of the vG end is ip1, and the mac address of the server is mac1; the VXLAN endpoint of pG is vtep2, the IP address of the device attached to the pG end is ip2, and the mac address of the device attached to the pG end is mac2. Since the source IP address of the multicast message received by the pG end is ip1_new, the destination IP address of the reply message is ip1_new, and the source IP address is ip2;

IP mapping is performed in the virtual switch on the pG side, and the OpenFlow flow table is issued through the controller to map the source IP address ip2 to ip2_new (this address is a reserved address and will not cause address conflicts between different families), and modify the virtual switch The ARP table is ip1_new corresponding to mac1, modify the FDB table in the VXLAN endpoint where the pG end is located, and match mac1 to the VXLAN endpoint vtep1;

After the packet received by the VXLAN interface vtep1 on the vG side is decapsulated, the source MAC address is mac2, the source IP address is ip2_new, the destination mac address is mac1, and the destination IP address is ip1_new. The OpenFlow flow table in the vG side is modified to do IP mapping. Change the destination IP address ip1_new of the message to ip1, and then forward the message to the vG end for internal processing.

As shown in Figure 4, the vG end transmits resources to the pG end through unicast, and the logic is as follows:

The VXLAN endpoint of the vG end is vtep1, the IP address of the vG end is ip1, and the mac address of the vG end is mac1; the VXLAN endpoint of the pG end is vtep2, the IP address of the device at the pG end is ip2, and the mac address of the device at the pG end is mac2;

The source mac address of the data message sent by the vG end is mac1, the source IP address is ip1, the destination mac address is mac2, and the destination IP address is ip2_new. IP mapping is done in the virtual switch on the vG side, the source IP address is mapped to ip1_new by issuing the OpenFlow flow table, the ARP table in the virtual switch on the vG side is modified so that ip2_new corresponds to mac2, and the FDB table of the VXLAN on the vG side is modified to mac2 Corresponding to vtep2;

The packet decapsulated by the VXLAN interface vtep2 on the pG side has the source mac address as mac1, the source IP address as ip1_new, the destination mac address as mac2, and the destination IP address as ip2_new. IP mapping is done in the virtual switch where the pG end is located, the destination IP address ip2_new is mapped to ip2 by issuing the OpenFlow flow table, and the ARP table is modified to ip1_new corresponding to mac1, and the source mac address of the packet received by the device connected to the pG end Is mac1, the source IP address is ip1_new, the destination mac address is mac2, and the destination IP address is ip2.

In the embodiment of the present invention, on the server side and the user side of the virtual home gateway, an Agent needs to be deployed for receiving instructions from the controller to issue configuration. The Controller connects to the Agent through the Netconf protocol, and uses the following configuration to change the FDB table of the vtep on the server side and the device side.

The Controller mainly provides the north-south API interface, the southbound interface is responsible for communicating and calling with basic network equipment, and the northbound interface is responsible for communicating and calling with upper-layer applications. At the same time, the controller will provide a web management platform. All SDN network functions are deployed and invoked on this interface. The independence, ease of use, and scalability between network functions are key indicators for measuring SDN Controller.

Assign unused IP resources to each agent, and send configuration to the agent through protocols such as Netconf to modify the VXLAN FDB table on the VTEP side. Modify the forwarding rules of the vSwitch. If a virtual switch that supports the OpenFlow protocol is used, the flow table is issued through the OpenFlow protocol to change the IP address of the data message.

To configure the agent, the VXLAN forwarding data table needs to be maintained. The Agent receives instructions from the Controller and configures the FDB table of the VTEP.

The format of the VXLAN FDB table is shown in Figure 5. The endpoint of the VXLAN tunnel is called a VTEP, and a forwarding data table can be configured in the VTEP. It can decide to encapsulate the data packet in a VXLAN message and send it to the next hop VTEP according to the destination MAC address of the inner message. If it is a unicast MAC, the agent only needs to configure the remote vtep corresponding to the MAC address. The vtep information includes IP, VNI (VXLAN Network Identifier, virtual extensible local area network identifier) and port information. If it is a multicast MAC, the agent needs to configure the remote vtep linked list corresponding to the MAC address. As shown in Figure 5(a), if the destination MAC address of the inner layer message is a unicast MAC address, it means that the message only needs to be sent to one vtep end, so only the vtep corresponding to the unicast MAC address needs to be recorded The IP address, VNI number, and port number of the terminal. As shown in Figure 5(b), if the destination MAC address of the inner message is a multicast MAC address, it means that the message needs to be sent to multiple vtep ends, so the IP addresses and VNI numbers of multiple vtep ends need to be recorded And the port number, and store it in the form of a linked list.

An embodiment of a virtual home network sharing system based on VXLAN and OpenFlow provided by the embodiment of the present invention includes:

Before the vG end broadcasts its own resources through multicast, it specifically includes:

Before the device connected to the pG end informs the vG end of its required resources through unicast, it specifically includes:

Optionally, on the basis of the above-mentioned corresponding embodiment of a virtual home network sharing system based on VXLAN and OpenFlow, the first optional implementation of a virtual home network sharing system based on VXLAN and OpenFlow provided in the embodiment of the present invention In the example, modify the FDB table of the newly created VXLAN connection VTEP side on the vG side, and modify the OpenFlow flow table on the vG side, including:

Connect the pG end VXLAN to the VTEP end FDB table, and the mac address of the vG end corresponds to the VXLAN end point of the vG end.

Before the vG end sends the resources required by the device connected to the pG end through unicast, it also includes:

The present invention is described with reference to flowcharts and/or block diagrams of methods, equipment (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

The present invention is not limited to the above-mentioned embodiments. For those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and modifications can be made, and these improvements and modifications are also regarded as the protection of the present invention. Within range. The content not described in detail in this specification belongs to the prior art known to those skilled in the art.

Claims

A virtual home network sharing method based on VXLAN and OpenFlow is characterized in that it includes the following steps:

Create a VXLAN connection to connect the vG end and pG end of the virtual home;

Create a new VXLAN connection between virtual homes and modify the VXLAN FDB table of the newly created VXLAN connection to make the second-tier network between the virtual homes reachable;

The vG end multicasts its own resources to the device connected to the pG end through multicast;

The device attached to the pG end informs the vG end of its required resources through unicast;

The vG end sends the resources required by the device connected to the pG end through unicast.
A virtual home network sharing method based on VXLAN and OpenFlow according to claim 1, characterized in that:

Before the vG end multicasts its own resources to all pG end-linked devices in a multicast manner, it specifically includes:

Modify the FDB table of the VXLAN connection on the vG side to the VTEP side so that the multicast packets on the vG side can reach the pG side;

Modify the OpenFlow flow table on the vG side to make the source IP address of the vG side an unused IP address;

Before the pG end-linked device notifies the vG end of its required resources through unicast, it specifically includes:

Modify the FDB table of the VXLAN connection on the pG end to the VTEP end so that the unicast packets of the device connected to the pG end can reach the vG end;

Modify the OpenFlow flow table on the pG end so that the source IP address of the packet sent by the device attached to the pG end to the vG end is an unused IP address.
A virtual home network sharing method based on VXLAN and OpenFlow according to claim 2, characterized in that modifying the FDB table of the VXLAN connection on the vG side and the VTEP side and modifying the OpenFlow flow table on the vG side specifically includes:

Perform IP mapping in the virtual switch on the vG side, and map the source IP address of the vG side to the unused first IP address by issuing the OpenFlow flow table;

Modify the FDB table on the VTEP side in the newly created VXLAN connection on the vG side, and map the destination mac address of the multicast packet to the vtep endpoint on the pG side.
A virtual home network sharing method based on VXLAN and OpenFlow according to claim 3, characterized in that modifying the FDB table of the VXLAN connection on the pG side and the VTEP side and modifying the OpenFlow flow table on the pG side specifically includes:

IP mapping is performed in the virtual switch on the pG end, and the OpenFlow flow table is issued to map the source IP address of the packet sent by the device at the pG end to the vG end to the unused second IP address;

Modify the ARP table in the virtual switch on the pG side to correspond the first IP address to the mac address on the vG side;

Connect the pG end VXLAN to the VTEP end FDB table, the mac address of the vG end corresponds to the vG end VTEP endpoint.
A virtual home network sharing method based on VXLAN and OpenFlow according to claim 4, characterized in that, before the vG end sends the resources required by the pG end connected device through unicast, it further comprises:

Perform IP mapping in the virtual switch on the vG side, and map the source IP address of the vG side to the first IP address by issuing the OpenFlow flow table;

Modify the ARP table in the virtual switch on the vG end to correspond the second IP address to the mac address of the device connected to the pG end;

Connect the newly created VXLAN at the vG end to the FDB table at the VTEP end. The mac address of the device connected to the pG end corresponds to the VTEP end point of the pG end.
A virtual home network sharing system based on VXLAN and OpenFlow is characterized in that it includes:

The first creation module, which is used to create a VXLAN connection and connect the vG end and the pG end of the virtual home gateway;

The second creation module is used to create a new VXLAN connection between virtual homes and modify the VXLAN FDB table of the newly created VXLAN connection to make the second-tier network between the virtual homes reachable;

Multicast module, which is used to drive the vG end to broadcast its own resources to the pG end-linked device through multicast;

The first unicast module, which is used to drive the device connected to the pG end to inform the vG end of the resources it needs by unicasting;

The second unicast module is used to drive the vG end to send the resources required by the device connected to the pG end in a unicast manner.
A virtual home network sharing system based on VXLAN and OpenFlow according to claim 6, characterized in that:

Before the vG end broadcasts its own resources in a multicast manner, it specifically includes:

Modify the FDB table of the newly created VXLAN connection on the VTEP side on the vG side so that the multicast packets on the vG side can reach the pG side;

Modify the OpenFlow flow table on the vG side to make the source IP address of the vG side an unused IP address;

Before the pG end-linked device notifies the vG end of its required resources through unicast, it specifically includes:

Modify the FDB table of the VXLAN connection on the pG end to the VTEP end so that the unicast packets of the device connected to the pG end can reach the vG end;

Modify the OpenFlow flow table on the pG end so that the source IP address of the packet sent by the device attached to the pG end to the vG end is an unused IP address.
The virtual home network sharing system based on VXLAN and OpenFlow according to claim 7, characterized in that modifying the FDB table of the VXLAN connection VTEP side on the vG side and modifying the OpenFlow flow table on the vG side specifically includes:

Perform IP mapping in the virtual switch on the vG side, and map the source IP address of the vG side to the unused first IP address by issuing the OpenFlow flow table;

Modify the FDB table on the VTEP side in the newly created VXLAN connection on the vG side, and map the destination mac address of the multicast packet to the vtep endpoint on the pG side.
A virtual home network sharing system based on VXLAN and OpenFlow according to claim 8, characterized in that modifying the FDB table of the VXLAN connection on the pG side to the VTEP side and modifying the OpenFlow flow table of the pG side specifically includes:

IP mapping is performed in the virtual switch on the pG end, and the OpenFlow flow table is issued to map the source IP address of the packet sent by the device at the pG end to the vG end to the unused second IP address;

Modify the ARP table in the virtual switch on the pG side to correspond the first IP address to the mac address on the vG side;

Connect the pG end VXLAN to the VTEP end FDB table, the mac address of the vG end corresponds to the vG end VTEP endpoint.
The virtual home network sharing system based on VXLAN and OpenFlow according to claim 9, characterized in that, before the vG end sends the resources required by the pG end connected device through unicast, it further comprises:

Perform IP mapping in the virtual switch on the vG side, and map the source IP address of the vG side to the first IP address by issuing the OpenFlow flow table;

Modify the ARP table in the virtual switch on the vG end to correspond the second IP address to the mac address of the device connected to the pG end;

Connect the newly created VXLAN on the vG end to the VTEP end FDB table, and the mac address of the device connected to the pG end corresponds to the VTEP end point of the pG end.