WO2017143695A1 - 一种子网互通方法和装置 - Google Patents

一种子网互通方法和装置 Download PDF

Info

Publication number
WO2017143695A1
WO2017143695A1 PCT/CN2016/085362 CN2016085362W WO2017143695A1 WO 2017143695 A1 WO2017143695 A1 WO 2017143695A1 CN 2016085362 W CN2016085362 W CN 2016085362W WO 2017143695 A1 WO2017143695 A1 WO 2017143695A1
Authority
WO
WIPO (PCT)
Prior art keywords
subnet
network
route
dci
dci network
Prior art date
Application number
PCT/CN2016/085362
Other languages
English (en)
French (fr)
Inventor
沈世元
袁俊
叶松青
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017143695A1 publication Critical patent/WO2017143695A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery

Definitions

  • the present application relates to, but is not limited to, the field of communications, and in particular, to a subnet interworking method and apparatus.
  • SDN Software Defined Network
  • OpenFlow separates the control plane of the network device from the data plane, thus achieving flexible control of network traffic and providing a good platform for innovation of core networks and applications.
  • VDC Virtual Data Center
  • ToR Topic of Rank
  • vSwitch Virtual Switch
  • OF OpenFlow
  • the main purpose of the embodiments of the present invention is to provide a method and device for subnet interworking, which aims to solve the technical problem that the different subnets under the same tenant cannot communicate with each other.
  • a subnet interworking method includes:
  • the DCI network Upon receiving a create instruction to create a data center interconnect DCI network, the DCI network is created in accordance with the create instruction.
  • the routing information corresponding to the route of the subnet is sent to the switch.
  • creating the DCI network according to the creating instruction includes:
  • the method further includes: after the routing information corresponding to the route of the subnet is sent to the switch, when the creation instruction for creating the DCI network is received again, determining the DCI network Identifies if the information has been stored.
  • the selecting to join the subnet in the DCI network and increasing the route of the subnet includes:
  • the second subnet is a subnet that joins the DCI network after the first subnet.
  • the first increased interface is invoked to increase the communication route of the DCI network
  • the second added interface and the third added interface are invoked to increase the inbound route and the outgoing direction of the first subnet. routing.
  • the second increase interface and the third increase interface are invoked to increase the inbound route and the outbound route of the second subnet.
  • the method further includes:
  • the routing information corresponding to the route of the subnet is sent to the switch, when detecting an operation instruction for deleting the subnet from the DCI network, determining that the deleted subnet is the A subnet is also the second subnet.
  • the first deletion interface and the second deletion interface are invoked to delete the inbound route and the outbound route of the second subnet.
  • the first deletion interface and the second deletion interface are invoked to delete the inbound route and the outbound route of the first subnet, and the third deletion interface is invoked to delete the DCI. Communication route of the network.
  • a subnet interworking device, the subnet interworking device includes:
  • the DCI network is created in accordance with the create instruction.
  • the sending module is configured to deliver the routing information corresponding to the route of the subnet to the switch.
  • the creating module includes:
  • the processing unit is configured to: when receiving the creation instruction of the DCI network, generate identification information of the DCI network to be created according to a preset rule.
  • a creating unit configured to store the identifier information of the DCI network, and create the DCI network according to the creating instruction and the identifier information of the DCI network.
  • the subnet interworking device further includes:
  • a first judging module configured to determine, after the sending module sends the routing information corresponding to the route of the subnet to the switch, when the creation instruction of creating the DCI network is received again, determining the DCI Whether the identification information of the network has been stored.
  • the prohibition module is configured to prohibit execution of the creation instruction of the DCI network that is newly received if the identification information of the DCI network has been stored.
  • the adding module includes:
  • the determining unit is configured to select to join the subnet in the DCI network, and determine whether the subnet is the first subnet or the second subnet, where the first subnet is the first one to join the DCI network.
  • the subnet, the second subnet is a subnet that joins the DCI network after the first subnet.
  • a calling unit configured to: if the subnet is the first subnet, invoke a first adding interface to increase a communication route of the DCI network, and invoke a second adding interface and a third adding interface to increase the first subnet Inbound route and outbound route.
  • the calling unit is further configured to: if the subnet is the second subnet, invoke the second adding interface and the third adding interface to increase the inbound route and the outbound route of the second subnet.
  • the subnet interworking device further includes:
  • a second determining module configured to: after the sending module sends the routing information corresponding to the route of the subnet to the switch, when detecting an operation instruction for deleting the subnet from the DCI network When it is determined, the deleted subnet is the first subnet or the second subnet.
  • the calling module is configured to: if the deleted subnet is the second subnet, invoke the first deleting interface and the second deleting interface to delete the inbound route and the outbound route of the second subnet.
  • the calling module is further configured to: if the deleted subnet is the first subnet, invoke the first deletion interface and the second deletion interface to delete the inbound route and the outbound route of the first subnet, and invoke The third delete interface deletes the communication route of the DCI network.
  • a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the subnet interworking method.
  • the embodiment of the present invention creates a DCI network, adds a subnet to the DCI network, adds an outbound route and an inbound route to the subnet, and uses the routing information corresponding to the outbound route and the inbound route of the subnet. Issued to the switch. It is not necessary to manually configure the routing table from the SDN network management interface to the switch, so as to implement unified management and scheduling of multiple distributed DCs, and realize interworking between the same subnets of the same tenant between DCs, omitting the SDN network management interface and simplifying
  • the VDC management and maintenance system facilitates the maintenance of the DCI network.
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for interworking between networks according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of creating a DCI network according to the creation instruction when receiving a creation instruction for creating a DCI network according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of selecting a subnet in the DCI network and adding an outbound route and an inbound route of the subnet according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a second embodiment of a method for interworking between networks according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of functional modules of a first embodiment of a network interworking device according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a functional module for creating a module according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a functional module of adding a module according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of functional modules of a second embodiment of an interworking device according to an embodiment of the present invention.
  • the embodiment of the invention provides a subnet interworking method.
  • FIG. 1 is a schematic flowchart of a first embodiment of a network interworking method according to an embodiment of the present invention.
  • the subnet interworking method includes steps S10-S30:
  • Step S10 When receiving a creation instruction for creating a data center interconnection DCI network, creating the DCI network according to the creation instruction.
  • the VDC management system When the VDC management system receives the creation instruction of the DCI (Data Center Interconnection) network, the RESTConf interface is invoked to create the DCI network according to the creation instruction.
  • the VDC management system can allocate a plurality of small DCs into a uniformly managed resource pool, and each DC is configured with a public network address, and the addresses of the DCs are mutually interoperable. of.
  • the VDC is a new type of data center that applies the concept of cloud computing to IDC (Internet Data Center).
  • the network element involved includes a virtual platform of an openstack, a network element such as an SDN network element, and a switch.
  • the openstack is an open source cloud computing management platform project that is composed of several major components combined to complete the work.
  • the SDN is implemented based on the OpenFlow, and implements the separation of forwarding and control.
  • the control plane of the switch is responsible for the OpenFlow Controller.
  • the data forwarding plane of the switch is responsible for the Switch of the OpenFlow, without relying on the underlying network equipment (routers, switches, firewalls, etc.). ), shielding the differences from the underlying network devices. Thereby, the control rights on the network device are completely open, so that the user can customize any network routing and transmission rule policies that he wants to implement.
  • the switch includes an access switch and a core switch.
  • the access switch is at the aggregation layer, and the aggregation layer access switch is capable of processing all traffic from the access layer device and transmitting the traffic to the uplink of the core layer.
  • the core switch is mainly a Layer 3 switch and works at the network layer.
  • the core switch works in OSI/RM (Open System Interconnect) and has a routing function.
  • Step S20 selecting to join the subnet in the DCI network, and increasing the route of the subnet.
  • the VDC management system selects a DCI network in the DCI network list and selects a subnet to be added to the DCI network.
  • the VDC management system increases the route of the subnet, where the route of the subnet is an outbound route and an inbound route. Among them, the subnet of the tenant under different DCs already exists.
  • the inbound route is a request route, and the parameters of the interface corresponding to the inbound route
  • the number includes, but is not limited to, an ID (Identification) of the tenant in the subnet and a UUID (Universally Unique Identifier) of the subnet.
  • the outgoing route is a response route, and the parameters of the interface corresponding to the outgoing route include, but are not limited to, a tenant ID, a subnet address segment, and an address mask in the subnet.
  • step S30 the routing information corresponding to the route of the subnet is delivered to the switch.
  • the VDC management system calls the interface zenic-logical-conf: getDCIConn to confirm the routing information corresponding to the outbound route and the inbound route corresponding to the subnet, that is, the route corresponding to the inbound route and the outbound route that need to be delivered. And the SDN controller sends the routing information corresponding to the outbound routing and the inbound routing of the subnet to the core switch.
  • the outgoing route and the incoming direction A routing flow table is formed by routing information corresponding to the route, and when the routing flow table is obtained, the routing flow table is sent to the core switch.
  • the routing information corresponding to the outbound routing and the inbound routing includes but is not limited to the tenant ID, the tenant IP (Internet Protocol, protocol interconnected between networks), and MAC (Medium/Media Access Control, medium access control) )address.
  • the core switch contains the routing information of the outbound route and the inbound route of different subnets, different subnets of different DCs can communicate with each other.
  • a DCI network is created, and a subnet is added to the DCI network to add an outbound route and an inbound route to the subnet, and the outbound route and the inbound route corresponding to the subnet are routed.
  • the VDC management and maintenance system facilitates the maintenance of the DCI network.
  • FIG. 2 is a schematic flowchart of creating a DCI network according to the creation instruction when a creation instruction for creating a DCI network is received according to an embodiment of the present invention.
  • step S10 that is, when the creation instruction for creating the DCI network is received, creating the DCI network according to the creation instruction includes steps S11-S12:
  • step S11 when the creation instruction of the DCI network is received, the identification information of the DCI network to be created is generated according to a preset rule.
  • the VDC management system When the VDC management system receives the creation instruction for creating the DCI network, the VDC management system generates the identification information of the DCI network to be created according to the preset rule.
  • the preset gauge Then, the rules are agreed between the VDC management system and the SDN controller.
  • the preset rule specifies the identification information of the DCI network to be generated, and the sequence of generating the identification information.
  • the identification information includes, but is not limited to, an RD (Route-Distinguisher Route Identity), an RT (Route-Target Route Target), and an ID of the tenant of the DCI network.
  • the RD is used to identify different VPN (Virtual Private Network) instances on the PE (Provider Edge) device.
  • the main function of the RD is to implement address multiplexing between VPN instances.
  • the addresses together form a 12-byte VPNv4 address space, and the RD is carried in the BGP (Border Gateway Protocol) Update message and is advertised to the peer.
  • the RT is an important attribute carried by the VPNv4 route. It determines the sending and receiving and filtering of the VPN route.
  • the PE Windows Preinstallation Environment
  • the RT includes an export_RT (outbound route target) and an import_RT (inbound route target). The format of the RT is consistent with the RD.
  • Step S12 Store identifier information of the DCI network, and create the DCI network according to the creation instruction and the identifier information of the DCI network.
  • the VDC management system stores the identification information of the DCI network, that is, the RD, the RT of the DCI network, and the ID of the tenant. It should be understood that, in this embodiment, the identifier information of the DCI network is The key attributes of the DCI network.
  • the VDC management system invokes the RESTConf interface to create the DCI network according to the creation instruction and the RD, RT of the DCI network and the ID of the tenant.
  • the subnet interworking method further includes:
  • the routing information corresponding to the route of the subnet is sent to the switch, when the creation instruction for creating the DCI network is received again, it is determined whether the identification information of the DCI network is stored.
  • the VDC management system determines whether the identification information of the DCI network already exists, that is, whether the identification information of the DCI network has been stored. If the identification information of the DCI network has been stored, the VDC management system prohibits execution of the creation instruction of the DCI network; if the DCI network The identification information is not stored, and the VDC management system invokes the RESTConf interface to create the DCI network again according to the creation instruction.
  • the identifier information of the DCI network is stored, so that the subsequent VDC management system prevents the repeated establishment of the DCI network according to the identification information of each DCI network when creating the DCI network.
  • FIG. 3 is a schematic flowchart of selecting a subnet in the DCI network and adding an outbound route and an inbound route of the subnet according to an embodiment of the present invention.
  • step S20 that is, selecting to join the subnet in the DCI network, and increasing the route of the subnet includes steps S21-S23:
  • Step S21 selecting to join the subnet in the DCI network, determining whether the subnet is a first subnet or a second subnet, where the first subnet is the first subnet to join the DCI network.
  • the second subnet is a subnet that joins the DCI network after the first subnet.
  • the VDC management system selects a subnet to be added to the DCI network, and determines whether the subnet currently joining the DCI network is the first subnet or the second subnet.
  • the first subnet is the first subnet that joins the DCI network
  • the second subnet is a subnet that joins the DCI network after the first subnet.
  • Step S22 if the subnet is the first subnet, the first adding interface is invoked to increase the communication route of the DCI network, and the second adding interface and the third adding interface are invoked to increase the inbound direction of the first subnet. Routing and outgoing routes.
  • the VDC management system When the VDC management system determines that the subnet joining the DCI network is the first subnet, the VDC management system invokes the first adding interface to increase the communication route of the DCI network, and invokes the second adding interface to increase the The inbound route of the first subnet, and the third increasing interface are invoked to increase the outbound route of the first subnet.
  • the first added interface is zenic-logical-conf: addDCIConn.
  • the VDC management system informs the SDN controller of the RD, the export_RT, the import_RT, and the VNI (VXLAN Network Identifier) of the DCI network through the zenic-logical-conf: addDCIConn interface, for the SDN controller to
  • the RD, export_RT, import_RT, and VNI of the DCI network generate communication routes suitable for communication corresponding to the message.
  • the second added interface is a zenic-logical-conf: addDCIIngressRoute, and the parameters of the second added interface include, but are not limited to, an ID of a tenant in the subnet and a UUID of the subnet.
  • the third added interface is zenic-logical-conf: addDCIEgressRoute, and the parameters of the third added interface include but are not limited to The ID, subnet address segment, and address mask of the tenant in the subnet.
  • Step S23 If the subnet is the second subnet, the second adding interface and the third adding interface are invoked to increase the inbound route and the outbound route of the second subnet.
  • the VDC management system determines that the subnet that joins the DCI network is the first subnet, the VDC management system invokes the second increased interface to increase the inbound route of the second subnet, and the second increase
  • the interface is zenic-logical-conf: addDCIIngressRoute; and the third interface is invoked to add an outgoing route of the second subnet, and the third added interface is zenic-logical-conf: addDCIEgressRoute.
  • FIG. 4 is a schematic flowchart diagram of a second embodiment of a method for subnet interworking according to an embodiment of the present invention.
  • the subnet interworking method further includes steps S40-S60:
  • Step S40 after the routing information corresponding to the route of the subnet is sent to the switch, when detecting an operation instruction for deleting the subnet from the DCI network, determining that the deleted subnet is The first subnet is also the second subnet.
  • the VDC management system When the VDC management system detects an operation instruction for deleting the subnet from the DCI network, the VDC management system invokes the RESTConf interface to delete the operation according to the operation instruction for deleting the subnet.
  • a subnet in the DCI network and determining whether the deleted subnet is the first subnet or the second subnet in the DCI network, that is, determining whether the deleted subnet is the first one to join the DCI network. Subnet.
  • Step S50 If the deleted subnet is the second subnet, the first deletion interface and the second deletion interface are invoked to delete the inbound route and the outbound route of the second subnet.
  • the subnet deleted by the VDC management system is the second subnet, that is, the deleted subnet is a subnet in the DCI network after the first subnet.
  • the VDC management system invokes the first deletion interface to delete the inbound route of the second subnet, and invokes the second deletion interface to delete the outbound route of the second subnet.
  • the first deletion interface is zenic-logical-conf:delDCIIngressRout; the second deletion interface is zenic-logical-conf:delDCIEgressRoute.
  • Step S60 If the deleted subnet is the first subnet, the first deletion interface and the second deletion interface are invoked to delete the inbound route and the outbound route of the first subnet, and the third delete interface is deleted. Communication route of the DCI network.
  • the VDC management system invokes the first deletion interface to delete the inbound route of the first subnet, and invokes the second deletion interface to delete the The outbound route of the first subnet, and calling the third delete interface to delete the communication route of the DCI network.
  • the VDC management system further invokes the fourth interface to confirm whether the inbound route and the outbound route of the first subnet are deleted from the core switch to ensure that no waste data is left in the core switch.
  • the first deletion interface is zenic-logical-conf:delDCIIngressRout; the second deletion interface is zenic-logical-conf:delDCIEgressRoute; the third deletion interface is zenic-logical-conf:delDCIConn; the fourth interface Is zenic-logical-conf: getDCIConn.
  • the subnet in the DCI network is deleted, which facilitates maintenance of the virtualized data center.
  • the embodiment of the invention further provides a subnet interworking device.
  • FIG. 5 is a schematic diagram of functional modules of a preferred embodiment of a network interworking device according to an embodiment of the present invention.
  • the subnet interworking device includes: a creating module 10, an adding module 20, and a sending module 30.
  • the creation module 10 is configured to create the DCI network according to the creation instruction when receiving a creation instruction to create a data center interconnection DCI network.
  • the VDC management system When the VDC management system receives the creation instruction of the DCI (Data Center Interconnection) network, the RESTConf interface is invoked to create the DCI network according to the creation instruction.
  • the VDC management system can allocate a plurality of small DCs to a uniformly managed resource pool, and each DC is configured with a public network address, and the addresses of the DCs are interoperable.
  • the VDC is a new type of data center that applies the concept of cloud computing to IDC (Internet Data Center).
  • the network element involved includes a virtual platform of an openstack, a network element such as an SDN network element, and a switch.
  • the openstack is an open source cloud computing management platform project, which is composed of several major components. To get the job done.
  • the SDN is implemented based on the OpenFlow, and implements the separation of forwarding and control.
  • the control plane of the switch is responsible for the OpenFlow Controller.
  • the data forwarding plane of the switch is responsible for the Switch of the OpenFlow, without relying on the underlying network equipment (routers, switches, firewalls, etc.). ), shielding the differences from the underlying network devices. Thereby, the control rights on the network device are completely open, so that the user can customize any network routing and transmission rule policies that he wants to implement.
  • the switch includes an access switch and a core switch.
  • the access switch is at the aggregation layer, and the aggregation layer access switch is capable of processing all traffic from the access layer device and transmitting the traffic to the uplink of the core layer.
  • the core switch is mainly a Layer 3 switch and works at the network layer.
  • the core switch works in OSI/RM (Open System Interconnect) and has a routing function.
  • the adding module 20 is configured to select to join a subnet in the DCI network and increase the routing of the subnet.
  • the VDC management system selects a DCI network in the DCI network list and selects a subnet to be added to the DCI network.
  • the VDC management system increases the route of the subnet, where the route of the subnet is an outbound route and an inbound route. Among them, the subnet of the tenant under different DCs already exists.
  • the inbound route is a request route, and the parameters of the interface corresponding to the inbound route include, but are not limited to, an ID (Identification) of the tenant in the subnet and a UUID (Universally Unique Identifier) of the subnet. Unique identification code).
  • the outgoing route is a response route, and the parameters of the interface corresponding to the outgoing route include, but are not limited to, a tenant ID, a subnet address segment, and an address mask in the subnet.
  • the sending module 30 is configured to deliver the routing information corresponding to the route of the subnet to the switch.
  • the VDC management system calls the interface zenic-logical-conf: getDCIConn to confirm the reason information corresponding to the outbound route and the inbound route corresponding to the subnet, that is, the route corresponding to the inbound route and the outbound route that need to be delivered. And the SDN controller sends the routing information corresponding to the outbound routing and the inbound routing of the subnet to the core switch. It should be understood that, in this embodiment, the outgoing route and the incoming direction A routing flow table is formed by routing information corresponding to the route, and when the routing flow table is obtained, the routing flow table is sent to the core switch.
  • the routing information corresponding to the outgoing route and the inbound route includes but is not limited to the tenant ID, the tenant IP (Internet Protocol, protocol interconnected between networks) and MAC (Medium/Media Access) Control, media access control) address.
  • tenant IP Internet Protocol, protocol interconnected between networks
  • MAC Medium/Media Access Control, media access control
  • a DCI network is created, and a subnet is added to the DCI network to add an outbound route and an inbound route to the subnet, and the outbound route and the inbound route corresponding to the subnet are routed.
  • the VDC management and maintenance system facilitates the maintenance of the DCI network.
  • FIG. 6 is a schematic diagram of a functional module for creating a module according to an embodiment of the present invention.
  • the creating module 10 includes: a processing unit 11 and a creating unit 12.
  • the processing unit 11 is configured to, when receiving the creation instruction of the DCI network, generate identification information of the DCI network to be created according to a preset rule.
  • the VDC management system When the VDC management system receives the creation instruction for creating the DCI network, the VDC management system generates the identification information of the DCI network to be created according to the preset rule.
  • the preset rule is a rule that is agreed between the VDC management system and the SDN controller, and the preset rule specifies the identity information of the DCI network to be generated, the sequence of generating the identifier information, and the like.
  • the identification information includes, but is not limited to, an RD (Route-Distinguisher), an RT (Route-Target), and an ID of the tenant of the DCI network.
  • the RD is used to identify different VPN (Virtual Private Network) instances on the PE (Provider Edge) device.
  • the main function of the RD is to implement address multiplexing between VPN instances.
  • the UDP (Border Gateway Protocol) Update message is sent to the peer end.
  • the RT is an important attribute carried by the VPNv4 route. It determines the sending and receiving and filtering of VPN routes.
  • the PE relies on the RT attribute to distinguish routes between different VPNs.
  • the RT includes export_RT and import_RT. The format of the RT is consistent with the RD.
  • the creating unit 12 is configured to store the identification information of the DCI network, and create the DCI network according to the creation instruction and the identification information of the DCI network.
  • the VDC management system stores the identification information of the DCI network, that is, the RD, the RT of the DCI network, and the ID of the tenant. It should be understood that, in this embodiment, the DCI The identification information of the network is a key attribute of the DCI network.
  • the VDC management system invokes the RESTConf interface to create the DCI network according to the creation instruction and the RD, RT of the DCI network and the ID of the tenant.
  • the subnet interworking device further includes: a first determining module and a prohibiting module.
  • a first judging module configured to determine, after the sending module sends the routing information corresponding to the route of the subnet to the switch, when the creation instruction of creating the DCI network is received again, determining the DCI Whether the identification information of the network has been stored.
  • the prohibition module is configured to prohibit execution of the creation instruction of the DCI network that is newly received if the identification information of the DCI network has been stored.
  • the VDC management system determines whether the identification information of the DCI network already exists, that is, whether the identification information of the DCI network has been stored. If the identification information of the DCI network is already stored, the VDC management system prohibits the creation of the creation instruction of the DCI network; if the identification information of the DCI network is not stored, the VDC management system according to the Creating an instruction to invoke the RESTConf interface to create the DCI network again.
  • the identifier information of the DCI network is stored, so that the subsequent VDC management system prevents the repeated establishment of the DCI network according to the identification information of each DCI network when creating the DCI network.
  • FIG. 7 is a schematic diagram of a functional module of an adding module according to an embodiment of the present invention.
  • the adding module 20 includes: a determining unit 21 and a calling unit 22.
  • the determining unit 21 is configured to select to join the subnet in the DCI network, and determine whether the subnet is the first subnet or the second subnet, where the first subnet is the first one to join the DCI network.
  • the subnet, the second subnet is a subnet that joins the DCI network after the first subnet.
  • the VDC management system selects a subnet to be added to the DCI network, and determines whether the subnet currently joining the DCI network is the first subnet or the second subnet.
  • the first subnet is the first subnet that joins the DCI network
  • the second subnet is a subnet that joins the DCI network after the first subnet.
  • the calling unit 22 is configured to: if the subnet is the first subnet, call the first adding interface to increase the communication route of the DCI network, and invoke the second adding interface and the third adding interface to add the first subnet Inbound route and outbound route.
  • the VDC management system When the VDC management system determines that the subnet joining the DCI network is the first subnet, the VDC management system invokes the first adding interface to increase the communication route of the DCI network, and invokes the second adding interface to increase the The inbound route of the first subnet, and the third increasing interface are invoked to increase the outbound route of the first subnet.
  • the first added interface is zenic-logical-conf: addDCIConn.
  • the VDC management system informs the SDN controller of the RD, the export_RT, the import_RT, and the VNI (VXLAN Network Identifier) of the DCI network through the zenic-logical-conf: addDCIConn interface, for the SDN controller to
  • the RD, export_RT, import_RT, and VNI of the DCI network generate communication routes suitable for communication corresponding to the message.
  • the second added interface is a zenic-logical-conf: addDCIIngressRoute, and the parameters of the second added interface include, but are not limited to, an ID of a tenant in the subnet and a UUID of the subnet.
  • the third added interface is a zenic-logical-conf: addDCIEgressRoute, and the parameters of the third added interface include, but are not limited to, a tenant ID, a subnet address segment, and an address mask in the subnet.
  • the calling unit 22 is further configured to: if the subnet is the second subnet, invoke the second adding interface and the third adding interface to increase the inbound route and the outbound route of the second subnet.
  • the VDC management system determines that the subnet that joins the DCI network is the first subnet, the VDC management system invokes the second increased interface to increase the inbound route of the second subnet, and the second increase
  • the interface is zenic-logical-conf: addDCIIngressRoute; and the third interface is invoked to add an outgoing route of the second subnet, and the third added interface is zenic-logical-conf: addDCIEgressRoute.
  • FIG. 8 is a schematic diagram of functional modules of a second embodiment of an interworking device according to an embodiment of the present invention.
  • the subnet interworking device further includes: a second judging module 40 and a calling module 50.
  • the second judging module 40 is configured to: after the sending module sends the routing information corresponding to the route of the subnet to the switch, after detecting that the subnet is deleted from the DCI network When instructing, determining whether the deleted subnet is the first subnet or the second subnet;
  • the VDC management system When the VDC management system detects an operation instruction for deleting the subnet from the DCI network, the VDC management system invokes the RESTConf interface to delete the operation according to the operation instruction for deleting the subnet.
  • a subnet in the DCI network and determining whether the deleted subnet is the first subnet or the second subnet in the DCI network, that is, determining whether the deleted subnet is the first one to join The subnet of the DCI network.
  • the calling module 50 is configured to delete the inbound route and the outbound route of the second subnet by invoking the first deleting interface and the second deleting interface if the deleted subnet is the second subnet.
  • the subnet deleted by the VDC management system is the second subnet, that is, the deleted subnet is a subnet in the DCI network after the first subnet.
  • the VDC management system invokes the first deletion interface to delete the inbound route of the second subnet, and invokes the second deletion interface to delete the outbound route of the second subnet.
  • the first deletion interface is zenic-logical-conf:delDCIIngressRout; the second deletion interface is zenic-logical-conf:delDCIEgressRoute.
  • the calling module is further configured to: if the deleted subnet is the first subnet, invoke the first deletion interface and the second deletion interface to delete the inbound route and the outbound route of the first subnet, and invoke The third delete interface deletes the communication route of the DCI network.
  • the VDC management system invokes the first deletion interface to delete the inbound route of the first subnet, and invokes the second deletion interface to delete the The outbound route of the first subnet, and calling the third delete interface to delete the communication route of the DCI network.
  • the VDC management system further invokes the fourth interface to confirm whether the inbound route and the outbound route of the first subnet are deleted from the core switch to ensure that no waste data is left in the core switch.
  • the first deletion interface is zenic-logical-conf:delDCIIngressRout; the second deletion interface is zenic-logical-conf:delDCIEgressRoute; the third deletion interface is zenic-logical-conf:delDCIConn; the fourth interface Is zenic-logical-conf: getDCIConn.
  • the subnet in the DCI network is deleted, which facilitates maintenance of the virtualized data center.
  • a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the subnet interworking method.
  • all or part of the steps of the above embodiments may also be implemented using an integrated circuit.
  • the steps may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps may be fabricated into a single integrated circuit module.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium (such as ROM/RAM, disk). And an optical disc, including if the dry command is used to cause a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in each embodiment of the present invention.
  • a terminal device which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
  • the embodiment of the present invention creates a DCI network, adds a subnet to the DCI network, adds an outbound route and an inbound route to the subnet, and uses the routing information corresponding to the outbound route and the inbound route of the subnet. Issued to the switch. It is not necessary to manually configure the routing table from the SDN network management interface to the switch, so as to implement unified management and scheduling of multiple distributed DCs, and realize interworking between the same subnets of the same tenant between DCs, omitting the SDN network management interface and simplifying
  • the VDC management and maintenance system facilitates the maintenance of the DCI network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种子网互通方法和装置，该方法包括：当接收到创建数据中心互联DCI网络的创建指令时，根据所述创建指令创建所述DCI网络；选择加入所述DCI网络中的子网，并增加所述子网的路由；将所述子网的路由所对应的路由信息下发至交换机中。

Description

一种子网互通方法和装置 技术领域
本申请涉及但不限于通讯领域，尤其涉及一种子网互通方法和装置。
背景技术
SDN(Software Defined Network，软件定义网络)，其核心技术OpenFlow通过将网络设备控制面与数据面分离开来，从而实现了网络流量的灵活控制，为核心网络及应用的创新提供了良好的平台，当前在运营商网络中就比较纯粹的SDN而言，首先可以从网络相对封闭的数据中心等场景开始入手，构建新型的SDN增强的VDC(Virtual Data Center，虚拟化数据中心)。通过在网络控制侧引入SDN控制器，对内建在计算资源之上vSwitch(Virtual Switch，虚拟交换机)和OF(OpenFlow)协议增强的ToR(Top of Rank，柜顶)硬件交换机等进行集中控制，变传统的数据中心的复杂的网络拓扑为大二层网络架构，及时应对数据中心内部和数据中心之间的虚拟机流量占比增大的变化要求。但是，在相关的SDN网管界面上需要手动配置路由流表至交换机上，导致DC(Data Center，数据中心)间同一租户下不同子网间的不能互通。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例的主要目的在于提供一种子网互通方法及装置，旨在解决相关DC间同一租户下不同子网间的不能互通的技术问题。
一种子网互通方法，包括：
当接收到创建数据中心互联DCI网络的创建指令时，根据所述创建指令创建所述DCI网络。
选择加入所述DCI网络中的子网，并增加所述子网的路由。
将所述子网的路由所对应的路由信息下发至交换机中。
可选地，所述当接收到创建DCI网络的创建指令时，根据所述创建指令创建所述DCI网络包括：
当接收到DCI网络的创建指令时，根据预设规则生成所要创建的所述 DCI网络的标识信息。
存储所述DCI网络的标识信息，根据所述创建指令和所述DCI网络的标识信息创建所述DCI网络。
可选地，所述方法还包括：在将所述子网的路由所对应的路由信息下发至交换机中之后，当再次接收到创建所述DCI网络的创建指令时，判断所述DCI网络的标识信息是否已存储。
如果所述DCI网络的标识信息已存储，则禁止执行再次接收到的所述创建所述DCI网络的创建指令。
可选地，所述选择加入所述DCI网络中的子网，并增加所述子网的路由包括：
选择加入所述DCI网络中的子网，判断所述子网是第一子网还是第二子网，其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网。
如果所述子网是第一子网，则调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口和第三增加接口增加所述第一子网的入向路由和出向路由。
如果所述子网是第二子网，则调用第二增加接口和第三增加接口增加所述第二子网的入向路由和出向路由。
可选地，所述方法还包括：
在将所述子网的路由所对应的路由信息下发至交换机中之后，当侦测到从所述DCI网络中删除所述子网的操作指令时，判断所删除的子网是所述第一子网还是所述第二子网。
如果所删除的子网是所述第二子网，则调用第一删除接口和第二删除接口删除所述第二子网的入向路由和出向路由。
如果所删除的子网是所述第一子网，则调用第一删除接口和第二删除接口删除所述第一子网的入向路由和出向路由，并调用第三删除接口删除所述DCI网络的通信路由。
一种子网互通装置，所述子网互通装置包括：
创建模块，设置为当接收到创建数据中心互联DCI网络的创建指令时， 根据所述创建指令创建所述DCI网络。
增加模块，设置为选择加入所述DCI网络中的子网，并增加所述子网的路由。
下发模块，设置为将所述子网的路由所对应的路由信息下发至交换机中。
可选地，所述创建模块包括：
处理单元，设置为当接收到DCI网络的创建指令时，根据预设规则生成所要创建的所述DCI网络的标识信息。
创建单元，设置为存储所述DCI网络的标识信息，根据所述创建指令和所述DCI网络的标识信息创建所述DCI网络。
可选地，所述子网互通装置还包括：
第一判断模块，设置为在所述下发模块将所述子网的路由所对应的路由信息下发至交换机中之后，当再次接收到创建所述DCI网络的创建指令时，判断所述DCI网络的标识信息是否已存储。
禁止模块，设置为如果所述DCI网络的标识信息已存储，则禁止执行再次接收到的所述创建所述DCI网络的创建指令。
可选地，所述增加模块包括：
判断单元，设置为选择加入所述DCI网络中的子网，判断所述子网是第一子网还是第二子网，其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网。
调用单元，设置为如果所述子网是第一子网，则调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口和第三增加接口增加所述第一子网的入向路由和出向路由。
所述调用单元，还设置为如果所述子网是第二子网，则调用第二增加接口和第三增加接口增加所述第二子网的入向路由和出向路由。
可选地，所述子网互通装置还包括：
第二判断模块，设置为在所述下发模块将所述子网的路由所对应的路由信息下发至交换机中之后，当侦测到从所述DCI网络中删除所述子网的操作指令时，判断所删除的子网是所述第一子网还是所述第二子网。
调用模块，设置为如果所删除的子网是所述第二子网，则调用第一删除接口和第二删除接口删除所述第二子网的入向路由和出向路由。
所述调用模块，还设置为如果所删除的子网是所述第一子网，则调用第一删除接口和第二删除接口删除所述第一子网的入向路由和出向路由，并调用第三删除接口删除所述DCI网络的通信路由。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现所述的子网互通方法。
本发明实施例通过创建DCI网络，并在所述DCI网络中加入子网，为所述子网增加出向路由和入向路由，将所述子网的出向路由和入向路由所对应的路由信息下发至交换机中。实现了不需要从SDN网管界面上手动配置路由表至交换中，从而实现对将分散的多个DC进行统一管理和调度，实现DC间同一租户下子网间的互通，省略了SDN网管界面，简化了VDC的管理维护系统，便于DCI网络的维护。
附图概述
图1为本发明实施例子网互通方法第一实施例的流程示意图；
图2为本发明实施例中当接收到创建DCI网络的创建指令时，根据所述创建指令创建所述DCI网络的一种流程示意图；
图3为本发明实施例中选择加入所述DCI网络中的子网，并增加所述子网的出向路由和入向路由的一种流程示意图；
图4为本发明实施例子网互通方法第二实施例的流程示意图；
图5为本发明实施例子网互通装置第一实施例的功能模块示意图；
图6为本发明实施例中创建模块的一种功能模块示意图；
图7为本发明实施例中增加模块的一种功能模块示意图；
图8为本发明实施例子网互通装置第二实施例的功能模块示意图。
本发明的实施方式
下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
本发明实施例提供一种子网互通方法。
参照图1，图1为本发明实施例子网互通方法第一实施例的流程示意图。
在本实施例中，所述子网互通方法包括步骤S10-S30：
步骤S10，当接收到创建数据中心互联DCI网络的创建指令时，根据所述创建指令创建所述DCI网络。
当VDC管理系统接收到创建DCI(Data Center Interconnection，数据中心互联)网络的创建指令时，根据所述创建指令，调用RESTConf接口创建所述DCI网络。在所述DCI网络中，所述VDC管理系统将分散的多个小的DC可以放入统一管理的资源池，每个DC都配置有公网地址，所述DC相互间的地址都是可以互通的。所述VDC是将云计算概念运用于IDC(Internet Data Center，互联网数据中心)的一种新型的数据中心形态。通过传统IDC业务与云计算技术相结合，建设统一创新型VDC运营管理系统，应用虚拟化、自动化部署等技术，构建可伸缩的虚拟化基础架构，采用集中管理、分布服务模式，向用户提供一点受理、全网服务的基础IT设施方案与服务。在所述VDC中，涉及的网元有openstack的虚拟平台、SDN网元、交换机等网元。所述openstack是一个开源的云计算管理平台项目，由几个主要的组件组合起来完成工作。所述SDN基于OpenFlow实现，实现了转发和控制的分离，将交换机的控制层面通过OpenFlow Controller负责；将交换机的数据转发平面交由OpenFlow的Switch负责，无须依赖底层网络设备(路由器、交换机和防火墙等)，屏蔽了来自底层网络设备的差异。从而使网络设备上的控制权完全开放，使用户可以自定义任何想实现的网络路由和传输规则策略。所述交换机包括接入交换机和核心交换机。所述接入交换机是处于汇聚层，汇聚层接入交换机能够处理来自接入层设备的所有通信量，并将所述通信量发送到核心层的上行链路中。所述核心交换机主要是三层交换机，工作在网络层。所述核心交换机工作于OSI/RM(Open System Interconnect，开放系统互连参考模型)，具有路由功能。
步骤S20，选择加入所述DCI网络中的子网，并增加所述子网的路由。
所述VDC管理系统在所述DCI网络列表中选择一个DCI网络，并选择需要加入所述DCI网络中的子网。所述VDC管理系统增加所述子网的路由，其中，所述子网的路由为出向路由和入向路由。其中，租户在不同的DC下的子网已经存在。所述入向路由为请求路由，所述入向路由所对应接口的参 数包括但不限于所述子网中租户的ID(Identification，身份标识)和所述子网的UUID(Universally Unique Identifier，通用唯一识别码)。所述出向路由为响应路由，所述出向路由所对应接口的参数包括但不限于所述子网中租户的ID、子网地址段和地址掩码。
步骤S30，将所述子网的路由所对应的路由信息下发至交换机中。
所述VDC管理系统调用接口zenic-logical-conf:getDCIConn确认所述子网所对应的出向路由和入向路由所对应的路由信息，即确认需要下发的入向路由和出向路由所对应的路由信息，并激活SDN控制器将所述子网的出向路由和入向路由所对应的路由信息发送至核心交换机中，应当理解的是，在本实施例中，所述出向路由和所述入向路由所对应的路由信息组成的路由流表，当得到所述路由流表时，将所述路由流表下发至核心交换机中。所述出向路由和入向路由所对应的路由信息包括但不限于所述租户ID，所述租户IP(Internet Protocol，网络之间互连的协议)和MAC(Medium/Media Access Control，媒介访问控制)地址。所述核心交换机中含有不同子网的出向路由和入向路由的路由信息后，不同DC间的不同子网可以实现互通。
本实施例通过创建DCI网络，并在所述DCI网络中加入子网，为所述子网增加出向路由和入向路由，将所述子网的出向路由和入向路由所对应的路由信息下发至交换机中。实现了不需要从SDN网管界面上手动配置路由表至交换机中，从而实现对将分散的多个DC进行统一管理和调度，实现DC间同一租户下子网间的互通，省略了SDN网管界面，简化了VDC的管理维护系统，便于DCI网络的维护。
参照图2，图2为本发明实施例中当接收到创建DCI网络的创建指令时，根据所述创建指令创建所述DCI网络的一种流程示意图。
在本实施例中，步骤S10，即当接收到创建DCI网络的创建指令时，根据所述创建指令创建所述DCI网络包括步骤S11-S12：
步骤S11，当接收到DCI网络的创建指令时，根据预设规则生成所要创建的所述DCI网络的标识信息。
当所述VDC管理系统接收到创建DCI网络的创建指令时，所述VDC管理系统根据预设规则生成所要创建的所述DCI网络的标识信息。所述预设规 则是所述VDC管理系统与SDN控制器之间约定的规则，如所述预设规则规定了要生成所述DCI网络的标识信息，以及生成所述标识信息的顺序等。所述标识信息包括但不限于所述DCI网络的RD(Route-Distinguisher路由标识)、RT(Route-Target路由目标)、和所述租户的ID。所述RD用于标示PE(Provider Edge，服务商边缘路由器)设备上不同VPN(Virtual Private Network，虚拟专用网络)实例，其主要作用也就是实现VPN实例之间地址复用，它与互联网协议IP地址一起构成了12byte的VPNv4地址空间，所述RD与路由一起被携带在BGP(Border Gateway Protocol，边界网关协议)Update报文中发布给对端。所述RT是VPNv4路由携带的一个重要属性，它决定VPN路由的收发和过滤，PE(Windows Preinstallation Environment，Windows预安装环境)依靠所述RT属性区分不同VPN之间路由。所述RT包括export_RT(出向路由目标)和import_RT(入向路由目标)所述RT的格式构成和所述RD一致。
步骤S12，存储所述DCI网络的标识信息，根据所述创建指令和所述DCI网络的标识信息创建所述DCI网络。
所述VDC管理系统存储所述DCI网络的标识信息，即存储所述DCI网络的RD、RT和所述租户的ID，应当理解的是，在本实施例中，所述DCI网络的标识信息为所述DCI网络的关键属性。所述VDC管理系统根据所述创建指令和所述DCI网络的RD、RT和所述租户的ID，调用所述RESTConf接口创建所述DCI网络。
可选地，所述子网互通方法还包括：
在将所述子网的路由所对应的路由信息下发至交换机中之后，当再次接收到创建所述DCI网络的创建指令时，判断所述DCI网络的标识信息是否已存储。
如果所述DCI网络的标识信息已存储，则禁止执行再次接收到的所述创建所述DCI网络的创建指令。
当所述VDC管理系统再次接收到创建所述DCI网络的创建指令时，所述VDC管理系统判断所述DCI网络的标识信息是否已存在，即所述DCI网络的标识信息是否已存储。如果所述DCI网络的标识信息已存储，所述VDC管理系统则禁止执行所述创建所述DCI网络的创建指令；如果所述DCI网络 的标识信息未存储，所述VDC管理系统则根据所述创建指令，调用所述RESTConf接口再次创建所述DCI网络。
本实施例通过存储DCI网络的标识信息，以供后续VDC管理系统在创建DCI网络时，根据每个DCI网络的标识信息防止重复建立所述DCI网络。
参照图3，图3为本发明实施例中选择加入所述DCI网络中的子网，并增加所述子网的出向路由和入向路由的一种流程示意图。
在本实施例中，步骤S20，即选择加入所述DCI网络中的子网，并增加所述子网的路由包括步骤S21-S23：
步骤S21，选择加入所述DCI网络中的子网，判断所述子网是第一子网还是第二子网，其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网。
所述VDC管理系统选择需要加入所述DCI网络中的子网，并判断当前加入所述DCI网络的子网是第一子网还是第二子网。其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网。
步骤S22，如果所述子网是第一子网，则调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口和第三增加接口增加所述第一子网的入向路由和出向路由。
当所述VDC管理系统判定加入所述DCI网络的子网为第一子网时，所述VDC管理系统调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口增加所述第一子网的入向路由，和调用第三增加接口增加所述第一子网的出向路由。所述第一增加接口为zenic-logical-conf:addDCIConn。所述VDC管理系统通过所述zenic-logical-conf:addDCIConn接口将所述DCI网络的RD、export_RT、import_RT、VNI(VXLAN Network Identifier)告知所述SDN控制器，以供所述SDN控制器根据所述DCI网络的RD、export_RT、import_RT、VNI生成适合对应报文进行通信的通信路由。所述第二增加接口为zenic-logical-conf:addDCIIngressRoute，所述第二增加接口的参数包括但不限于所述子网中租户的ID和所述子网的UUID。所述第三增加接口为zenic-logical-conf:addDCIEgressRoute，所述第三增加接口的参数包括但不限 于所述子网中租户的ID、子网地址段和地址掩码。
步骤S23，如果所述子网是第二子网，则调用第二增加接口和第三增加接口增加所述第二子网的入向路由和出向路由。
如果所述VDC管理系统判定加入所述DCI网络的子网为第一子网时，所述VDC管理系统则调用第二增加接口增加所述第二子网的入向路由，所述第二增加接口为zenic-logical-conf:addDCIIngressRoute；并调用所述第三接口增加所述第二子网的出向路由，所述第三增加接口为zenic-logical-conf:addDCIEgressRoute。
参照图4，图4为本发明实施例中子网互通方法第二实施例的流程示意图。
在本实施例中，所述子网互通方法还包括步骤S40-S60：
步骤S40，在将所述子网的路由所对应的路由信息下发至交换机中之后，当侦测到从所述DCI网络中删除所述子网的操作指令时，判断所删除的子网是所述第一子网还是所述第二子网。
当所述VDC管理系统侦测到从所述DCI网络中删除所述子网的操作指令时，所述VDC管理系统根据所述删除所述子网的操作指令，调用所述RESTConf接口删除所述DCI网络中的子网，并判断所删除的子网是所述DCI网络中的第一子网还是第二子网，即判断所述删除的子网是否是第一个加入所述DCI网络的子网。
步骤S50，如果所删除的子网是所述第二子网，则调用第一删除接口和第二删除接口删除所述第二子网的入向路由和出向路由。
如果所述VDC管理系统所删除的子网是第二子网，即所述删除的子网是在所述第一子网之后加入所述DCI网络中的子网。所述VDC管理系统则调用第一删除接口删除所述第二子网的入向路由，并调用第二删除接口删除所述第二子网的出向路由。所述第一删除接口为zenic-logical-conf:delDCIIngressRout；所述第二删除接口为zenic-logical-conf:delDCIEgressRoute。
步骤S60，如果所删除的子网是所述第一子网，则调用第一删除接口和第二删除接口删除所述第一子网的入向路由和出向路由，并调用第三删除接口删除所述DCI网络的通信路由。
如果所述VDC管理系统所删除的子网是第一子网，所述VDC管理系统则调用第一删除接口删除所述第一子网的入向路由，调用所述第二删除接口删除所述第一子网的出向路由，并调用第三删除接口删除所述DCI网络的通信路由。可选地，所述VDC管理系统还调用第四接口确认所述第一子网的入向路由和出向路由是否从所述核心交换机中删除，以确保所述核心交换机中无遗留的垃圾数据。所述第一删除接口为zenic-logical-conf:delDCIIngressRout；所述第二删除接口为zenic-logical-conf:delDCIEgressRoute；所述第三删除接口为zenic-logical-conf:delDCIConn；所述第四接口为zenic-logical-conf:getDCIConn。
本实施例通过当不需要DCI网络中的子网时，删除所述DCI网络中的子网，便于对虚拟化数据中心的维护。
本发明实施例还提供一种子网互通装置。
参照图5，图5为本发明实施例子网互通装置较佳实施例的功能模块示意图。
在本实施例中，所述子网互通装置包括：创建模块10、增加模块20和下发模块30。
创建模块10，设置为当接收到创建数据中心互联DCI网络的创建指令时，根据所述创建指令创建所述DCI网络。
当VDC管理系统接收到创建DCI(Data Center Interconnection，数据中心互联)网络的创建指令时，根据所述创建指令，调用RESTConf接口创建所述DCI网络。在所述DCI网络中，所述VDC管理系统将分散的多个小的DC可以加入统一管理的资源池，每个DC都配置有公网地址，所述DC相互间的地址都是可以互通的。所述VDC是将云计算概念运用于IDC(Internet Data Center，互联网数据中心)的一种新型的数据中心形态。通过传统IDC业务与云计算技术相结合，建设统一创新型VDC运营管理系统，应用虚拟化、自动化部署等技术，构建可伸缩的虚拟化基础架构，采用集中管理、分布服务模式，向用户提供一点受理、全网服务的基础IT设施方案与服务。在所述VDC中，涉及的网元有openstack的虚拟平台、SDN网元、交换机等网元。所述openstack是一个开源的云计算管理平台项目，由几个主要的组件组合起 来完成工作。所述SDN基于OpenFlow实现，实现了转发和控制的分离，将交换机的控制层面通过OpenFlow Controller负责；将交换机的数据转发平面交由OpenFlow的Switch负责，无须依赖底层网络设备(路由器、交换机和防火墙等)，屏蔽了来自底层网络设备的差异。从而使网络设备上的控制权完全开放，使用户可以自定义任何想实现的网络路由和传输规则策略。所述交换机包括接入交换机和核心交换机。所述接入交换机是处于汇聚层，汇聚层接入交换机能够处理来自接入层设备的所有通信量，并将所述通信量发送到核心层的上行链路中。所述核心交换机主要是三层交换机，工作在网络层。所述核心交换机工作于OSI/RM(Open System Interconnect，开放系统互连参考模型)，具有路由功能。
增加模块20，设置为选择加入所述DCI网络中的子网，并增加所述子网的路由。
所述VDC管理系统在所述DCI网络列表中选择一个DCI网络，并选择需要加入所述DCI网络中的子网。所述VDC管理系统增加所述子网的路由，其中，所述子网的路由为出向路由和入向路由。其中，租户在不同的DC下的子网已经存在。所述入向路由为请求路由，所述入向路由所对应接口的参数包括但不限于所述子网中租户的ID(Identification，身份标识)和所述子网的UUID(Universally Unique Identifier，通用唯一识别码)。所述出向路由为响应路由，所述出向路由所对应接口的参数包括但不限于所述子网中租户的ID、子网地址段和地址掩码。
下发模块30，设置为将所述子网的路由所对应的路由信息下发至交换机中。
所述VDC管理系统调用接口zenic-logical-conf:getDCIConn确认所述子网所对应的出向路由和入向路由所对应的理由信息，即确认需要下发的入向路由和出向路由所对应的路由信息，并激活SDN控制器将所述子网的出向路由和入向路由所对应的路由信息发送至核心交换机中，应当理解的是，在本实施例中，所述出向路由和所述入向路由所对应的路由信息组成的路由流表，当得到所述路由流表时，将所述路由流表下发至核心交换机中。所述出向路由和入向路由所对应的路由信息包括但不限于所述租户ID，所述租户IP(Internet Protocol，网络之间互连的协议)和MAC(Medium/Media Access  Control，媒介访问控制)地址。所述核心交换机中含有不同子网的出向路由和入向路由的路由信息后，不同DC间的不同子网可以实现互通。
本实施例通过创建DCI网络，并在所述DCI网络中加入子网，为所述子网增加出向路由和入向路由，将所述子网的出向路由和入向路由所对应的路由信息下发至交换机中。实现了不需要从SDN网管界面上手动配置路由表至交换机中，从而实现对将分散的多个DC进行统一管理和调度，实现DC间同一租户下子网间的互通，省略了SDN网管界面，简化了VDC的管理维护系统，便于DCI网络的维护。
参照图6，图6为本发明实施例中创建模块的一种功能模块示意图。
在本实施例中，所述创建模块10包括：处理单元11和创建单元12。
处理单元11，设置为当接收到DCI网络的创建指令时，根据预设规则生成所要创建的所述DCI网络的标识信息。
当所述VDC管理系统接收到创建DCI网络的创建指令时，所述VDC管理系统根据预设规则生成所要创建的所述DCI网络的标识信息。所述预设规则是所述VDC管理系统与SDN控制器之间约定的规则，如所述预设规则规定了要生成所述DCI网络的标识信息，以及生成所述标识信息的顺序等。所述标识信息包括但不限于所述DCI网络的RD(Route-Distinguisher)、RT(Route-Target)、和所述租户的ID。所述RD用于标示PE(Provider Edge，服务商边缘路由器)设备上不同VPN(Virtual Private Network，虚拟专用网络)实例，其主要作用也就是实现VPN实例之间地址复用，它与IP地址一起构成了12byte的VPNv4地址空间，所述RD与路由一起被携带在BGP(Border Gateway Protocol，边界网关协议)Update报文中发布给对端。所述RT是VPNv4路由携带的一个重要属性，它决定VPN路由的收发和过滤，PE依靠所述RT属性区分不同VPN之间路由。所述RT包括export_RT和import_RT所述RT的格式构成和所述RD一致。
创建单元12，设置为存储所述DCI网络的标识信息，根据所述创建指令和所述DCI网络的标识信息创建所述DCI网络。
所述VDC管理系统存储所述DCI网络的标识信息，即存储所述DCI网络的RD、RT和所述租户的ID，应当理解的是，在本实施例中，所述DCI 网络的标识信息为所述DCI网络的关键属性。所述VDC管理系统根据所述创建指令和所述DCI网络的RD、RT和所述租户的ID，调用所述RESTConf接口创建所述DCI网络。
可选地，所述子网互通装置还包括：第一判断模块和禁止模块。
第一判断模块，设置为在所述下发模块将所述子网的路由所对应的路由信息下发至交换机中之后，当再次接收到创建所述DCI网络的创建指令时，判断所述DCI网络的标识信息是否已存储。
禁止模块，设置为如果所述DCI网络的标识信息已存储，则禁止执行再次接收到的所述创建所述DCI网络的创建指令。
当所述VDC管理系统再次接收到创建所述DCI网络的创建指令时，所述VDC管理系统判断所述DCI网络的标识信息是否已存在，即所述DCI网络的标识信息是否已存储。如果所述DCI网络的标识信息已存储，所述VDC管理系统则禁止执行所述创建所述DCI网络的创建指令；如果所述DCI网络的标识信息未存储，所述VDC管理系统则根据所述创建指令，调用所述RESTConf接口再次创建所述DCI网络。
本实施例通过存储DCI网络的标识信息，以供后续VDC管理系统在创建DCI网络时，根据每个DCI网络的标识信息防止重复建立所述DCI网络。
参照图7，图7为本发明实施例中增加模块的一种功能模块示意图。
在本实施例中，所述增加模块20包括：判断单元21和调用单元22。
判断单元21，设置为选择加入所述DCI网络中的子网，判断所述子网是第一子网还是第二子网，其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网。
所述VDC管理系统选择需要加入所述DCI网络中的子网，并判断当前加入所述DCI网络的子网是第一子网还是第二子网。其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网。
调用单元22，设置为如果所述子网是第一子网，则调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口和第三增加接口增加所述第一子网的入向路由和出向路由。
当所述VDC管理系统判定加入所述DCI网络的子网为第一子网时，所述VDC管理系统调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口增加所述第一子网的入向路由，和调用第三增加接口增加所述第一子网的出向路由。所述第一增加接口为zenic-logical-conf:addDCIConn。所述VDC管理系统通过所述zenic-logical-conf:addDCIConn接口将所述DCI网络的RD、export_RT、import_RT、VNI(VXLAN Network Identifier)告知所述SDN控制器，以供所述SDN控制器根据所述DCI网络的RD、export_RT、import_RT、VNI生成适合对应报文进行通信的通信路由。所述第二增加接口为zenic-logical-conf:addDCIIngressRoute，所述第二增加接口的参数包括但不限于所述子网中租户的ID和所述子网的UUID。所述第三增加接口为zenic-logical-conf:addDCIEgressRoute，所述第三增加接口的参数包括但不限于所述子网中租户的ID、子网地址段和地址掩码。
所述调用单元22，还设置为如果所述子网是第二子网，则调用第二增加接口和第三增加接口增加所述第二子网的入向路由和出向路由。
如果所述VDC管理系统判定加入所述DCI网络的子网为第一子网时，所述VDC管理系统则调用第二增加接口增加所述第二子网的入向路由，所述第二增加接口为zenic-logical-conf:addDCIIngressRoute；并调用所述第三接口增加所述第二子网的出向路由，所述第三增加接口为zenic-logical-conf:addDCIEgressRoute。
参照图8，图8为本发明实施例子网互通装置的第二实施例的功能模块示意图。
在本实施例中，所述子网互通装置还包括：第二判断模块40和调用模块50。
第二判断模块40，设置为在所述下发模块将所述子网的路由所对应的路由信息下发至交换机中之后，当侦测到从所述DCI网络中删除所述子网的操作指令时，判断所删除的子网是所述第一子网还是所述第二子网；
当所述VDC管理系统侦测到从所述DCI网络中删除所述子网的操作指令时，所述VDC管理系统根据所述删除所述子网的操作指令，调用所述RESTConf接口删除所述DCI网络中的子网，并判断所删除的子网是所述DCI网络中的第一子网还是第二子网，即判断所述删除的子网是否是第一个加入 所述DCI网络的子网。
调用模块50，设置为如果所删除的子网是所述第二子网，则调用第一删除接口和第二删除接口删除所述第二子网的入向路由和出向路由。
如果所述VDC管理系统所删除的子网是第二子网，即所述删除的子网是在所述第一子网之后加入所述DCI网络中的子网。所述VDC管理系统则调用第一删除接口删除所述第二子网的入向路由，并调用第二删除接口删除所述第二子网的出向路由。所述第一删除接口为zenic-logical-conf:delDCIIngressRout；所述第二删除接口为zenic-logical-conf:delDCIEgressRoute。
所述调用模块，还设置为如果所删除的子网是所述第一子网，则调用第一删除接口和第二删除接口删除所述第一子网的入向路由和出向路由，并调用第三删除接口删除所述DCI网络的通信路由。
如果所述VDC管理系统所删除的子网是第一子网，所述VDC管理系统则调用第一删除接口删除所述第一子网的入向路由，调用所述第二删除接口删除所述第一子网的出向路由，并调用第三删除接口删除所述DCI网络的通信路由。可选地，所述VDC管理系统还调用第四接口确认所述第一子网的入向路由和出向路由是否从所述核心交换机中删除，以确保所述核心交换机中无遗留的垃圾数据。所述第一删除接口为zenic-logical-conf:delDCIIngressRout；所述第二删除接口为zenic-logical-conf:delDCIEgressRoute；所述第三删除接口为zenic-logical-conf:delDCIConn；所述第四接口为zenic-logical-conf:getDCIConn。
本实施例通过当不需要DCI网络中的子网时，删除所述DCI网络中的子网，便于对虚拟化数据中心的维护。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现所述的子网互通方法。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这 些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明实施例的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括如果干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本发明每个实施例所述的方法。
工业实用性
本发明实施例通过创建DCI网络，并在所述DCI网络中加入子网，为所述子网增加出向路由和入向路由，将所述子网的出向路由和入向路由所对应的路由信息下发至交换机中。实现了不需要从SDN网管界面上手动配置路由表至交换中，从而实现对将分散的多个DC进行统一管理和调度，实现DC间同一租户下子网间的互通，省略了SDN网管界面，简化了VDC的管理维护系统，便于DCI网络的维护。

Claims (11)

  1. 一种子网互通方法，所述子网互通方法包括：
    当接收到创建数据中心互联DCI网络的创建指令时，根据所述创建指令创建所述DCI网络；
    选择加入所述DCI网络中的子网，并增加所述子网的路由；
    将所述子网的路由所对应的路由信息下发至交换机中。
  2. 如权利要求1所述的子网互通方法，其中，所述当接收到创建DCI网络的创建指令时，根据所述创建指令创建所述DCI网络包括：
    当接收到DCI网络的创建指令时，根据预设规则生成所要创建的所述DCI网络的标识信息；
    存储所述DCI网络的标识信息，根据所述创建指令和所述DCI网络的标识信息创建所述DCI网络。
  3. 如权利要求2所述的子网互通方法，所述方法还包括：
    在将所述子网的路由所对应的路由信息下发至交换机中之后，当再次接收到创建所述DCI网络的创建指令时，判断所述DCI网络的标识信息是否已存储；
    如果所述DCI网络的标识信息已存储，则禁止执行再次接收到的所述创建所述DCI网络的创建指令。
  4. 如权利要求1至3任一项所述的子网互通方法，其中，所述选择加入所述DCI网络中的子网，并增加所述子网的路由包括：
    选择加入所述DCI网络中的子网，判断所述子网是第一子网还是第二子网，其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网；
    如果所述子网是第一子网，则调用第一增加接口增加所述DCI网络的通信路由，并调用第二增加接口和第三增加接口增加所述第一子网的入向路由和出向路由；
    如果所述子网是第二子网，则调用第二增加接口和第三增加接口增加所述第二子网的入向路由和出向路由。
  5. 如权利要求4所述的子网互通方法，所述方法还包括：
    在将所述子网的路由所对应的路由信息下发至交换机中之后，当侦测到 从所述DCI网络中删除所述子网的操作指令时，判断所删除的子网是所述第一子网还是所述第二子网；
    如果所删除的子网是所述第二子网，则调用第一删除接口和第二删除接口删除所述第二子网的入向路由和出向路由；
    如果所删除的子网是所述第一子网，则调用第一删除接口和第二删除接口删除所述第一子网的入向路由和出向路由，并调用第三删除接口删除所述DCI网络的通信路由。
  6. 一种子网互通装置，所述子网互通装置包括：
    创建模块，设置为当接收到创建数据中心互联DCI网络的创建指令时，根据所述创建指令创建所述DCI网络；
    增加模块，设置为选择加入所述DCI网络中的子网，并增加所述子网的路由；
    下发模块，设置为将所述子网的路由所对应的路由信息下发至交换机中。
  7. 如权利要求6所述的子网互通装置，其中，所述创建模块包括：
    处理单元，设置为当接收到DCI网络的创建指令时，根据预设规则生成所要创建的所述DCI网络的标识信息；
    创建单元，设置为存储所述DCI网络的标识信息，根据所述创建指令和所述DCI网络的标识信息创建所述DCI网络。
  8. 如权利要求7所述的子网互通装置，所述子网互通装置还包括：
    第一判断模块，设置为在所述下发模块将所述子网的路由所对应的路由信息下发至交换机中之后，当再次接收到创建所述DCI网络的创建指令时，判断所述DCI网络的标识信息是否已存储；
    禁止模块，设置为如果所述DCI网络的标识信息已存储，则禁止执行再次接收到的所述创建所述DCI网络的创建指令。
  9. 如权利要求6至8任一项所述的子网互通装置，其中，所述增加模块包括：
    判断单元，设置为选择加入所述DCI网络中的子网，判断所述子网是第一子网还是第二子网，其中，所述第一子网为第一个加入所述DCI网络的子网，所述第二子网为在所述第一子网后加入所述DCI网络的子网；
    调用单元，设置为如果所述子网是第一子网，则调用第一增加接口增加 所述DCI网络的通信路由，并调用第二增加接口和第三增加接口增加所述第一子网的入向路由和出向路由；
    所述调用单元，还设置为如果所述子网是第二子网，则调用第二增加接口和第三增加接口增加所述第二子网的入向路由和出向路由。
  10. 如权利要求9所述的子网互通装置，所述子网互通装置还包括：
    第二判断模块，设置为在所述下发模块将所述子网的路由所对应的路由信息下发至交换机中之后，当侦测到从所述DCI网络中删除所述子网的操作指令时，判断所删除的子网是所述第一子网还是所述第二子网；
    调用模块，设置为如果所删除的子网是所述第二子网，则调用第一删除接口和第二删除接口删除所述第二子网的入向路由和出向路由；
    所述调用模块，还设置为如果所删除的子网是所述第一子网，则调用第一删除接口和第二删除接口删除所述第一子网的入向路由和出向路由，并调用第三删除接口删除所述DCI网络的通信路由。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现权利要求1至5任意一项所述的子网互通方法。
PCT/CN2016/085362 2016-02-22 2016-06-08 一种子网互通方法和装置 WO2017143695A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610096219.5A CN107104871B (zh) 2016-02-22 2016-02-22 子网互通方法和装置
CN201610096219.5 2016-02-22

Publications (1)

Publication Number Publication Date
WO2017143695A1 true WO2017143695A1 (zh) 2017-08-31

Family

ID=59658817

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/085362 WO2017143695A1 (zh) 2016-02-22 2016-06-08 一种子网互通方法和装置

Country Status (2)

Country Link
CN (1) CN107104871B (zh)
WO (1) WO2017143695A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112751759A (zh) * 2019-10-30 2021-05-04 华为技术有限公司 路由信息传输方法及装置、数据中心互联网络
CN114697326A (zh) * 2022-03-17 2022-07-01 浪潮云信息技术股份公司 一种边缘计算场景下多边通信的方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111327531B (zh) * 2018-12-17 2022-08-02 中兴通讯股份有限公司 基于vdc的路由配置方法、装置、设备及可读存储介质
CN109981437B (zh) * 2019-03-08 2022-02-18 平安科技（深圳）有限公司 一种基于vpc的多数据中心互通方法及相关设备
CN112702372B (zh) 2019-10-22 2024-04-05 中兴通讯股份有限公司 一种云服务管理方法、云服务管理装置及可读存储介质
CN114866472B (zh) * 2022-07-11 2022-09-30 广东省新一代通信与网络创新研究院 一种在多模态网络中实现开源社区访问的方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882758A (zh) * 2011-07-12 2013-01-16 华为技术有限公司 虚拟私云接入网络的方法、网络侧设备和数据中心设备
CN102946355A (zh) * 2012-09-29 2013-02-27 华为技术有限公司 组播组处理方法、dci路由器及系统
CN104601472A (zh) * 2015-02-04 2015-05-06 盛科网络（苏州）有限公司 在芯片中实现vxlan网关分布式路由的方法及报文处理系统
CN104954281A (zh) * 2014-03-31 2015-09-30 中国移动通信集团公司 通信方法、系统、资源池管理系统、交换机和控制装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916326B (zh) * 2008-09-11 2017-10-31 瞻博网络公司 用于数据中心的系统、方法以及设备
WO2013036580A2 (en) * 2011-09-09 2013-03-14 Interdigital Patent Holdings, Inc. Methods and apparatus for accessing localized applications
US9276838B2 (en) * 2012-10-05 2016-03-01 Futurewei Technologies, Inc. Software defined network virtualization utilizing service specific topology abstraction and interface
US9973429B2 (en) * 2013-04-05 2018-05-15 Futurewei Technologies, Inc. Software defined networking (SDN) controller orchestration and network virtualization for data center interconnection
CN103618672B (zh) * 2013-11-29 2017-05-10 杭州华三通信技术有限公司 一种基于分布式数据中心的路由发布方法和设备
US9716628B2 (en) * 2014-05-23 2017-07-25 Cisco Technology, Inc. Touchless orchestration for layer 3 data center interconnect in communications networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882758A (zh) * 2011-07-12 2013-01-16 华为技术有限公司 虚拟私云接入网络的方法、网络侧设备和数据中心设备
CN102946355A (zh) * 2012-09-29 2013-02-27 华为技术有限公司 组播组处理方法、dci路由器及系统
CN104954281A (zh) * 2014-03-31 2015-09-30 中国移动通信集团公司 通信方法、系统、资源池管理系统、交换机和控制装置
CN104601472A (zh) * 2015-02-04 2015-05-06 盛科网络（苏州）有限公司 在芯片中实现vxlan网关分布式路由的方法及报文处理系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112751759A (zh) * 2019-10-30 2021-05-04 华为技术有限公司 路由信息传输方法及装置、数据中心互联网络
CN114697326A (zh) * 2022-03-17 2022-07-01 浪潮云信息技术股份公司 一种边缘计算场景下多边通信的方法
CN114697326B (zh) * 2022-03-17 2024-04-30 浪潮云信息技术股份公司 一种边缘计算场景下多边通信的方法

Also Published As

Publication number Publication date
CN107104871B (zh) 2021-11-19
CN107104871A (zh) 2017-08-29

Similar Documents

Publication Publication Date Title
WO2017143695A1 (zh) 一种子网互通方法和装置
CN110120934B (zh) 应用防火墙策略的方法、软件定义网络控制器和介质
CN109561108B (zh) 一种基于策略的容器网络资源隔离控制方法
JP5948362B2 (ja) コンピュータネットワークの動的な移行
EP3152865B1 (en) Provisioning and managing slices of a consumer premises equipment device
WO2020125320A1 (zh) 基于vdc的路由配置方法、装置、设备及可读存储介质
EP3176979A1 (en) Information processing method and device
US11303555B2 (en) Inter-data center software-defined network controller network
WO2016180181A1 (zh) 业务功能的部署方法及装置
US10320666B2 (en) Method and device for processing routing status and/or policy information
WO2016159113A1 (ja) 制御装置、制御方法及びプログラム
WO2018006704A1 (zh) 公网ip分配方法、装置以及虚拟化数据中心系统
US11469998B2 (en) Data center tenant network isolation using logical router interconnects for virtual network route leaking
WO2017162030A1 (zh) 一种虚拟网络的生成方法和装置
WO2023056722A1 (zh) 一种分布式防火墙定义方法及系统
JP2017507566A (ja) ネットワークサービスのクラウドベースネットワーク機能注入
Levin et al. Networking architecture for seamless cloud interoperability
US20230093915A1 (en) Cloud router platform for sdn networks
JP2019519146A (ja) ルーティング確立、パケット送信
Matias et al. The EHU-OEF: an OpenFlow-based layer-2 experimental facility
CN108768861B (zh) 一种发送业务报文的方法及装置
WO2020029793A1 (zh) 一种上网行为管理系统、设备及方法
CN112671811B (zh) 一种网络接入方法和设备
Chainho et al. Decentralized communications: trustworthy interoperability in peer-to-peer networks
CN115002029A (zh) 一种流量转发方法、装置、设备及存储介质

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16891149

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16891149

Country of ref document: EP

Kind code of ref document: A1