Method for implementing network virtualization and related apparatus and communications system
Uložené v:
| Názov: | Method for implementing network virtualization and related apparatus and communications system |
|---|---|
| Patent Number: | 11563,669 |
| Dátum vydania: | January 24, 2023 |
| Appl. No: | 17/236363 |
| Application Filed: | April 21, 2021 |
| Abstrakt: | A method for implementing network virtualization, and a related apparatus and a communications system are provided. The method for implementing network virtualization may include: receiving, by an SDN controller, a virtual network creation request that carries virtual network topology information; creating a virtual network in response to the virtual network creation request; establishing, by the SDN controller, a device mapping relationship; establishing, by the SDN controller, a port mapping relationship; allocating, by the SDN controller, a virtual SDN controller to the virtual network; and registering, by the SDN controller, a first virtual forwarding device and a second virtual forwarding device with the virtual SDN controller. Technical solutions of embodiments of the present invention help to improve networking flexibility, reduce service costs, and shorten a service deployment period. |
| Inventors: | HUAWEI TECHNOLOGIES CO., LTD. (Guangdong, CN) |
| Assignees: | HUAWEI TECHNOLOGIES CO., LTD. (Guangdong, CN) |
| Claim: | 1. A method for implementing network virtualization, the method comprising: creating a virtual network comprising a virtual forwarding device; establishing a device mapping relationship between the virtual forwarding device and a physical forwarding device in a physical network; establishing a port mapping relationship between a port of the virtual forwarding device and a port of the physical forwarding device; and registering the virtual forwarding device with a virtual controller, wherein the virtual controller is usable to control the virtual network. |
| Claim: | 2. The method according to claim 1 , further comprising: allocating a virtual network identifier to the virtual network; and establishing a mapping relationship between the virtual network identifier and an identifier of the virtual controller. |
| Claim: | 3. The method according to claim 1 , wherein the port mapping relationship comprises at least one of the following mapping relationships: a mapping relationship between inbound port information of the virtual forwarding device and inbound port information of the physical forwarding device; or a mapping relationship between outbound port information of the virtual forwarding device and outbound port information of the physical forwarding device. |
| Claim: | 4. The method according to claim 3 , wherein: the inbound port information of the virtual forwarding device comprises a port identifier of an inbound port of the virtual forwarding device; the outbound port information of the virtual forwarding device comprises a port identifier of an outbound port of the virtual forwarding device; the inbound port information of the physical forwarding device comprises a port identifier of an inbound port of the physical forwarding device; and the outbound port information of the physical forwarding device comprises a port identifier of an outbound port of the physical forwarding device. |
| Claim: | 5. The method according to claim 3 , further comprising: obtaining a first routing entry delivered by the virtual controller, wherein the first routing entry carries a network address representing a destination address or a source address and the outbound port information of the virtual forwarding device; determining the physical forwarding device and the outbound port information of the physical forwarding device; and sending a second routing entry to the physical forwarding device, wherein the second routing entry carries the network address and the outbound port information of the physical forwarding device. |
| Claim: | 6. The method according to claim 3 , further comprising: obtaining a third routing entry delivered by the virtual controller, wherein the third routing entry carries the inbound port information of the virtual forwarding device and the outbound port information of the virtual forwarding device; determining the physical forwarding device, the outbound port information of the physical forwarding device, and the inbound port information of the physical forwarding device; and sending a fourth routing entry to the physical forwarding device, wherein the fourth routing entry carries the inbound port information of the physical forwarding device and the outbound port information of the physical forwarding device. |
| Claim: | 7. The method according to claim 3 , further comprising: receiving a first control message reported by the physical forwarding device, wherein the first control message carries the inbound port information of the physical forwarding device; determining the inbound port information of the virtual forwarding device; and sending a second control message to the virtual controller, wherein the second control message carries the inbound port information of the virtual forwarding device. |
| Claim: | 8. The method according to claim 1 , further comprising: allocating a device identifier to the virtual forwarding device; wherein the device mapping relationship comprises a mapping relationship between the device identifier of the virtual forwarding device and a device identifier of the physical forwarding device. |
| Claim: | 9. The method according to claim 1 , wherein the virtual forwarding device is a first virtual forwarding device and the physical forwarding device is a first physical forwarding device, the method further comprises: establishing a mapping relationship between a virtual link and a link tunnel, wherein the virtual link is a virtual link between the first virtual forwarding device and a second virtual forwarding device in the virtual network, and the link tunnel is a link tunnel between the first physical forwarding device and a second physical forwarding device in the physical network. |
| Claim: | 10. A method for implementing network virtualization, the method comprising: obtaining a first routing entry delivered by a virtual controller, wherein the first routing entry carries outbound port information of a virtual forwarding device controlled by the virtual controller; determining a physical forwarding device based on a device mapping relationship between the virtual forwarding device and the physical forwarding device; determining outbound port information of the physical forwarding device, based on a port mapping relationship and the outbound port information of the virtual forwarding device; and sending a second routing entry to the physical forwarding device, wherein an action field of the second routing entry carries the outbound port information of the physical forwarding device. |
| Claim: | 11. The method according to claim 10 , wherein: the outbound port information of the virtual forwarding device comprises a port identifier of an outbound port of the virtual forwarding device; and the outbound port information of the physical forwarding device comprises a port identifier of an outbound port of the physical forwarding device. |
| Claim: | 12. The method according to claim 10 , wherein a match field of the first routing entry carries inbound port information of the virtual forwarding device, and the method further comprises: determining, based on the port mapping relationship and the inbound port information of the virtual forwarding device, inbound port information of the physical forwarding device; wherein the second routing entry carries the inbound port information of the physical forwarding device. |
| Claim: | 13. A controller, comprising: a processor; and a non-transitory memory coupled to the processor and comprising instructions, which when executed by the processor, cause the controller to: create a virtual network comprising a virtual forwarding device; establish a device mapping relationship between the virtual forwarding device and a physical forwarding device in a physical network; establish a port mapping relationship between a port of the virtual forwarding device and a port of the physical forwarding device; and register the virtual forwarding device with a virtual controller, wherein the virtual controller is usable to control the virtual network. |
| Claim: | 14. The controller according to claim 13 , wherein the instructions further cause the controller to: allocate a virtual network identifier to the virtual network; and establish a mapping relationship between the virtual network identifier and an identifier of the virtual controller. |
| Claim: | 15. The controller according to claim 13 , wherein the port mapping relationship comprises at least one of the following mapping relationships: a mapping relationship between inbound port information of the virtual forwarding device and inbound port information of the physical forwarding device; or a mapping relationship between outbound port information of the virtual forwarding device and outbound port information of the physical forwarding device. |
| Claim: | 16. The controller according to claim 13 , wherein the instructions further cause the controller to: obtain a first routing entry delivered by the virtual controller, wherein the first routing entry carries a network address representing a destination address or a source address and outbound port information of the virtual forwarding device; determine, based on the virtual forwarding device and the device mapping relationship, the physical forwarding device; determine, based on the port mapping relationship and the outbound port information of the virtual forwarding device, outbound port information of the physical forwarding device; and send a second routing entry to the physical forwarding device, wherein the second routing entry carries the network address and the outbound port information of the physical forwarding device. |
| Claim: | 17. The controller according to claim 13 , wherein the instructions further cause the controller to: obtain a third routing entry delivered by the virtual controller, wherein the third routing entry carries inbound port information of the virtual forwarding device and outbound port information of the virtual forwarding device; determine, based on the virtual forwarding device and the device mapping relationship, the physical forwarding device; determine, based on the port mapping relationship and the outbound port information of the virtual forwarding device, outbound port information of the physical forwarding device; determine, based on the port mapping relationship and the inbound port information of the virtual forwarding device, inbound port information of the physical forwarding device; and send a fourth routing entry to the physical forwarding device, wherein the fourth routing entry carries the inbound port information of the physical forwarding device and the outbound port information of the physical forwarding device. |
| Claim: | 18. The controller according to claim 13 , wherein the instructions further cause the controller to: receive a first control message reported by the physical forwarding device, wherein the first control message carries the inbound port information of the physical forwarding device; determine inbound port information of the virtual forwarding device; and send a second control message to the virtual controller, wherein the second control message carries the inbound port information of the virtual forwarding device. |
| Claim: | 19. The controller according to claim 13 , wherein the instructions further cause the controller to: allocate a device identifier to the virtual forwarding device; wherein the device mapping relationship between the virtual forwarding device and the physical forwarding device comprises a mapping relationship between the device identifier of the virtual forwarding device and a device identifier of the physical forwarding device. |
| Claim: | 20. A controller, comprising: a processor; and a non-transitory memory coupled to the processor and comprising instructions, which when executed by the processor, cause the controller to: obtain a first routing entry delivered by a virtual controller, wherein the first routing entry carries outbound port information of a virtual forwarding device controlled by the virtual controller; determine, based on the virtual forwarding device and a device mapping relationship, a physical forwarding device, wherein the device mapping relationship comprises a mapping relationship between the virtual forwarding device and the physical forwarding device in a physical network; determine, based on a port mapping relationship and the outbound port information of the virtual forwarding device, outbound port information of the physical forwarding device, wherein the port mapping relationship comprises a mapping relationship between the outbound port information of the virtual forwarding device and the outbound port information of the physical forwarding device; and send a second routing entry to the physical forwarding device, wherein the second routing entry carries the outbound port information of the physical forwarding device. |
| Claim: | 21. The controller according to claim 20 , wherein: the outbound port information of the virtual forwarding device comprises a port identifier of an outbound port of the virtual forwarding device; and the outbound port information of the physical forwarding device comprises a port identifier of an outbound port of the physical forwarding device. |
| Claim: | 22. The controller according to claim 20 , wherein the first routing entry carries inbound port information of the virtual forwarding device; and the instructions further cause the controller to: determine inbound port information of the physical forwarding device, wherein the second routing entry carries the inbound port information of the physical forwarding device. |
| Patent References Cited: | 10419326 September 2019 Hu 11005747 May 2021 Hu 20080301303 December 2008 Matsuoka 20100257263 October 2010 Casado et al. 20120005392 January 2012 Yagi 20130332602 December 2013 Nakil et al. 20140047125 February 2014 Hyoudou et al. 20140280864 September 2014 Fin et al. 20150049636 February 2015 Tai 102710432 October 2012 2833579 February 2015 2013/139298 September 2013 2013/146829 October 2013 |
| Other References: | “OpenFlow Switch Specification Version 1.1.0”, Open Networking Foundation (Year: 2011). cited by applicant EP Application No. 14882883.3, Extended European Search Report, dated Dec. 9, 2016, 13 pages. cited by applicant ETSI Anonymous, “Network Functions Virtualisation (NFV); Architectural Framework,” ETSI GS NVF 002 V1 .1.1, Oct. 1, 2013, pp. 1-21. cited by applicant Hewlett-Packard, et al., “NVF and SON,” European Telecommunications Standards Institute (ETSI), Feb. 6, 2014, pp. 1-10. cited by applicant PCT/CN2014/072425, International Search Report, dated Dec. 1, 2014, 12 pages. cited by applicant LN, Pingping, et al., “VCP: A Virtualization Cloud Platform for SON Intra-domain Production Network,” 2012 2oth IEEE International Conference on Network Protocols (ICNP), Oct. 30-Nov. 2, 2012, 2 pages. cited by applicant Sun, Ying-ying, et al., “Design and Implementation of Virtual Network Infrastructure Based on OpenFlow,” Jan. 2014, 5 pages (English Abstract). cited by applicant Dmitry Drutskoy et al:.‘Scalable Network Virtualization in Software-Defined Networks’, IEEE Internet Computing, Institute of Electrical and Electronics Engineers,US,vol. 17, No. 2, Mar. 1, 2013, pp. 20-27,XP011498339. cited by applicant |
| Primary Examiner: | Duffy, James P |
| Attorney, Agent or Firm: | Womble Bond Dickinson (US) LLP |
| Prístupové číslo: | edspgr.11563669 |
| Databáza: | USPTO Patent Grants |
Buďte prvý, kto okomentuje tento záznam!