Data transmission method, PNF SDN controller, VNF SDN controller, and data transmission system
A data transmission method includes: receiving, by the PNF SDN controller, a first packet and an access loop identifier that are sent by a first network device; generating, by the PNF SDN controller, a second packet based on the access loop identifier and the first packet; and sending, by the PNF SDN controller, the second packet to the virtualized network function software-defined networking VNF SDN controller, so that the VNF SDN controller sends the second packet to a second network device, where the second packet is used to request the second network device to assign an IP address or IP address prefix to user equipment.
1. A data transmission method implemented by a physical network function software-defined networking (PNF SDN) controller, the data transmission method comprising:
receiving, from a first network device, a first packet originating from a terminal device;
receiving, from the first network device, an access loop identifier, wherein the access loop identifier identifies a physical port or a logical port of the first network device and through which the first network device receives the first packet;
generating a second packet comprising the first packet and the access loop identifier; and
sending, to a virtualized network function software-defined networking (VNF SDN) controller, the second packet to prompt the VNF SDN controller to send the second packet to a second network device,
wherein the second packet requests that the second network device assign an Internet Protocol (IP) address or an IP address prefix to the terminal device.
2. The data transmission method of claim 1 , wherein after sending the second packet, the data transmission method further comprises:
receiving, from the VNF SDN controller, a response packet corresponding to the second packet, wherein the response packet comprises the access loop identifier and either the IP address or the IP address prefix; and
sending, to the first network device, the access loop identifier and either the IP address or the IP address prefix.
3. The data transmission method of claim 1 , further comprising further sending the second packet through an interconnection interface between the PNF SDN controller and the VNF SDN controller.
4. The data transmission method of claim 1 , further comprising further sending the second packet using an upper-level controller.
5. The data transmission method of claim 2 , wherein after receiving the response packet, the data transmission method further comprises:
generating, based on the response packet, a table mapping a media access control (MAC) address of the terminal device to either the IP address or the IP address prefix; and
sending, to the first network device, the table.
6. A physical network function software-defined networking (PNF SDN) controller comprising:
a communications interface configured to:
receive, from a first network device, a first packet originating from a terminal device; and
receive, from the first network device, an access loop identifier, wherein the access loop identifier identifies a physical port or a logical port of the first network device and through which the first network device receives the first packet; and
a processor coupled to the communications interface and configured to generate a second packet comprising the first packet and the access loop identifier,
wherein the communications interface is further configured to send, to a virtualized network function software-defined networking (VNF SDN) controller, that the second packet to prompt the VNF SDN controller to send the second packet to a second network device,
wherein the second packet requests that the second network device assign an Internet Protocol (IP) address or an IP address prefix to the terminal device.
7. The PNF SDN controller of claim 6 , wherein the communications interface is further configured to:
receive, from the VNF SDN controller, a response packet corresponding to the second packet, wherein the response packet comprises the access loop identifier and either the IP address or the IP address prefix; and
send, to the first network device, the access loop identifier and either the IP address or the IP address prefix.
8. The PNF SDN controller of claim 6 , wherein the communications interface is further configured to further send the second packet through an interconnection interface between the PNF SDN controller and the VNF SDN controller.
9. The PNF SDN controller of claim 6 , wherein the communications interface is further configured to further send the second packet using an upper-level controller.
10. The PNF SDN controller of claim 7 , wherein after the communications interface receives the response packet, the processor is further configured to generate, based on the response packet, a table mapping a media access control (MAC) address of the terminal device to either the IP address or the IP address prefix, and wherein the communications interface is further configured to send, to the first network device, the table.
11. A virtualized network function software-defined networking (VNF SDN) controller comprising:
a processor; and
a communications interface coupled to the processor and configured to:
receive, from a physical network function software-defined networking (PNF SDN) controller, a second packet that is based on an access loop identifier and that is based on a first packet that originates from a terminal device; and
send, to a second network device, the second packet to request that the second network device assign an Internet Protocol (IP) address or an IP address prefix to the terminal device,
wherein the access loop identifier identifies a physical port or a logical port of a first network device and through which the first network device receives the first packet.
12. The VNF SDN controller of claim 11 , wherein the communications interface is further configured to:
receive, from the second network device, a response packet corresponding to the second packet, wherein the response packet comprises the access loop identifier and either the IP address or the IP address prefix; and
send, to the PNF SDN controller, the response packet.
13. The VNF SDN controller of claim 11 , wherein the communications interface is further configured to receive, from the PNF SDN controller and through an interconnection interface between the VNF SDN controller and the PNF SDN controller, the second packet.
14. The VNF SDN controller of claim 11 , wherein the communications interface is further configured to receive, from the PNF SDN controller and using an upper-level controller, the second packet.
15. The VNF SDN controller of claim 12 , wherein the processor is configured to generate, based on the response packet, a table mapping a media access control (MAC) address of the terminal device to either the IP address or the IP address prefix, and wherein the communications interface is further configured to send, to a third network device, the table.
16. The VNF SDN controller of claim 11 , wherein the processor is further configured to obtain the access loop identifier from the second packet, and wherein the communications interface is further configured to:
send, to a fourth network device, an authentication request packet comprising the access loop identifier; and
receive, from the fourth network device, an authorization response packet.
17. A data transmission system comprising:
a physical network function software-defined networking (PNF SDN) controller configured to:
receive, from a first network device, a first packet originating from a terminal device;
receive, from the first network device, an access loop identifier, wherein the access loop identifier identifies a physical port or a logical port of the first network device and through which the first network device receives the first packet;
generate a second packet comprising the first packet and the access loop identifier; and
send the second packet;
a virtualized network function software-defined networking (VNF SDN) controller configured to:
receive, from the PNF SDN controller, the second packet; and
send, to a second network device, the second packet to request that the second network device assign an Internet Protocol (IP) address or an IP address prefix to the terminal device.
18. The data transmission system of claim 17 , wherein the access loop identifier identifies the physical port, but not the logical port.
19. The data transmission system of claim 17 , wherein the access loop identifier identifies the logical port, but not the physical port.
20. The data transmission system of claim 17 , wherein the VNF SDN controller is further configured to further send the second packet to request the second network device to assign the IP address, but not the IP address prefix.