WO2017193848A1 - 路由建立、报文发送 - Google Patents
路由建立、报文发送 Download PDFInfo
- Publication number
- WO2017193848A1 WO2017193848A1 PCT/CN2017/082897 CN2017082897W WO2017193848A1 WO 2017193848 A1 WO2017193848 A1 WO 2017193848A1 CN 2017082897 W CN2017082897 W CN 2017082897W WO 2017193848 A1 WO2017193848 A1 WO 2017193848A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- sdn
- routing information
- terminal device
- vpn
- controller
- Prior art date
Links
Images
Classifications
-
- 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
- H04L45/04—Interdomain routing, e.g. hierarchical routing
-
- 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/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- 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/38—Flow based routing
-
- 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/64—Routing or path finding of packets in data switching networks using an overlay routing layer
-
- 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/74—Address processing for routing
Definitions
- SDN Software Defined Network
- the SDN may include a gateway device, a controller, a switching device, a terminal device, and the like.
- the controller is a control center and can be sent to the switching device according to the configuration of the user or the dynamically generated protocol.
- the switching device can further send the flow table to each terminal device connected to itself. After receiving the packet, the switching device or the terminal device can send the packet according to the locally saved flow table.
- the terminal device may be a virtual machine.
- FIG. 1 is a flowchart of a route establishment method provided by an example of the present disclosure.
- FIG. 2 is a flowchart of a method for sending a message according to an example of the present disclosure.
- FIG. 3 is a schematic structural diagram of a route establishing apparatus according to an example of the present disclosure.
- FIG. 4 is a schematic structural diagram of another route establishing apparatus according to an example of the present disclosure.
- FIG. 5 is a schematic structural diagram of a message sending apparatus according to an example of the present disclosure.
- FIG. 6 is a schematic diagram of a route establishment process of an example of the present disclosure.
- FIG. 7 is a schematic diagram of a message sending process according to an example of the present disclosure.
- VPN Virtual Private Network
- two types of routing devices can be included: a Provider Edge (PE) device and a CE (Customer Edge) device.
- PE Provider Edge
- CE Customer Edge
- each device can learn the routing information of each device in the network by transmitting VPN-IPv4 routing information.
- the user CE device may send the VPN-IPv4 routing information carrying the routing information to the user PE device, and the user PE device may send the VPN-IPv4 routing information to the operator CE device, and the carrier CE device may use the VPN.
- the IPv4 routing information is sent to the operator PE device; the carrier PE device can send the VPN-IPv4 routing information to the peer operator PE device, and the peer carrier PE device can further pass its carrier CE device, The user PE device sends the VPN-IPv4 routing information to the user CE device, thereby completing the delivery of the routing information. After receiving a data packet, any device can send a data packet through its saved route.
- the SDN can be nested with the Layer 2 and Layer 3 networks, for example, SDN and VPN are nested.
- the SDN and the VPN can be connected through the gateway device in the SDN. Because the SDN uses the openflow flow table to guide the packet transmission, the Layer 3 network uses the routing table to guide the packet transmission. Therefore, the PEs and CEs in the gateway device and the VPN cannot obtain the routing addresses of the terminal devices in the SDN, for example, 32. Bit address information.
- Each terminal device in the SDN may be a server, a vRouter (virtual router), a virtual machine (virtual machine), and of course, if a VXLAN tunnel connection exists in the SDN, the terminal device may also be a VTEP (VXLAN Tunnel End Point). , VXLAN node device).
- the gateway device Since the data transmission in the SDN is performed by the flow table sent by the controller, the gateway device does not have the routing information of the terminal device in the SDN, so that the device in the VPN cannot send the packet to the terminal in the SDN according to the corresponding routing entry. device. Therefore, the process of sending service data from a VPN to an SDN can only be overly complicated by re-planning the network, such as adding a new subnet.
- the present disclosure provides a method and device for route establishment and message transmission.
- the controller in the SDN obtains the address information of each terminal device saved in the SDN, generates routing information, and uses a corresponding routing protocol (such as a BGP routing protocol) to connect the VPN gateway device in the SDN.
- the routing information is sent to each device in the VPN, such as the PE and CE devices in the VPN.
- the PE or CE device in the VPN needs to upload packets (such as service data packets) to the terminal device in the SDN.
- the packet can be sent according to the obtained routing information, so that the network is not required to be re-planned, and the complexity of transmitting the packet in the VPN to the terminal device in the SDN is reduced.
- the present disclosure example provides a route establishment method procedure applied to a controller of a software defined network SDN. As shown in Figure 1, the process includes the following steps.
- the controller may obtain address information of each terminal device included in the SDN saved locally.
- the address information of each terminal device in the SDN is obtained, and the routing information may be generated according to the obtained address information, where the routing information may be a routing entry or part of the routing entry, for example, Source address, destination address, RD, RT, etc.
- the controller establishes a BGP neighbor with the gateway device, and the routing information of each terminal device generated in the SDN can be transmitted to each device in the VPN through the gateway device by using the BGP protocol, so that each device in the VPN obtains the SDN.
- the routing information of each terminal device is such that each device in the VPN can send a packet to each terminal device in the SDN according to the obtained routing information. In this way, the complexity of transmitting service data inside the VPN to the SDN can be reduced.
- the controller in the SDN and the gateway device can establish a neighbor relationship.
- the gateway device can also pre-configure the Border Gateway Protocol BGP routing protocol, and the gateway device can also be connected to the operator PE device of the VPN.
- the controller can obtain address information of each terminal device included in the locally saved SDN.
- the foregoing terminal device may be a virtual machine in the SDN.
- the address information of the terminal device may include vport data (ie, a virtual egress port).
- the controller may pre-build the database locally and obtain the address information of each terminal device included in the SDN, so that the obtained address information of each terminal device may be saved in the database, so that the controller obtains the SDN. Address information of each terminal device.
- the controller may generate routing information according to the address information of each terminal device, and send the routing information to the gateway device, so that the operator PE device connected to the gateway device is configured according to the Routing information is used to establish routes, that is, packets are sent according to routing information.
- the routing information may be generated according to the address information of each terminal device. For example, a routing entry may be generated for sending a packet, where the routing entry carries the Routing information. The routing information can then be sent to the gateway device.
- the routing information may include: address information of the terminal device, such as interface information, an IP address, a MAC address, and the like.
- the controller When the controller generates routing information according to the address information of each terminal device, the vport data of each terminal device can be mapped to the VPN route according to the mapping table, and the IP address and MAC address of each terminal device are obtained.
- the mapping table defines a data structure in which the name of the controller, the name of the VPN, the type of the port, the RD information used to distinguish different VPNs, and the extended community attribute used to control the distribution and learning of VPN routing information ( Route target, RT) information, MAC address of the terminal device, IP address, and so on.
- the controller may extract the information to be converted from the vport data of each terminal device saved locally, and map the extracted information into VPN routing information according to the mapping table. Then, the VPN routing information is sent to the gateway device in the form of a BGP update message.
- the gateway device may send the routing information to the operator PE device of the VPN connected to itself to deliver the routing information to the VPN.
- the operator PE device After the operator PE device receives the routing information sent by the gateway device, the operator PE device can advertise the routing information it receives in the VPN. For example, the operator PE device can send the routing information to all the PE devices and the CE device connected to the device, so that each device in the VPN stores the routing information received by the carrier PE device. In addition, when the service data needs to be converted into the SDN, each device can send the service data packet it receives according to the locally saved routing information.
- the routing information may further include a routing identifier RD information corresponding to each terminal device as a flag for isolating the VPN during the delivery process.
- RD information corresponding to each terminal device as a flag for isolating the VPN during the delivery process.
- the IP address spaces of different VPNs are independent.
- the RD information can be used as a flag for isolating the VPN.
- each terminal device in the SDN such as the vRouter of each tenant, can be understood to correspond to one VPN instance.
- the RD information may be added to the routing information, so that the routing information is sent to the PE device through the gateway device, the PE device may RD information to distinguish between different terminal devices.
- the controller of the SDN can obtain the address information of each terminal device included in the SDN, and generate routing information according to the address information of each terminal device. Further, the controller may send the routing information to the operator PE device of the VPN through the gateway device. Therefore, each device in the VPN can be saved locally by control. Route information generated by the device. When any device in the VPN performs service data conversion, it can send service data packets to the SDN according to the locally saved routing information, without re-planning the network. Therefore, the complexity of converting service data inside the VPN to the SDN can be reduced.
- another route establishment method is also provided, which is applied to a carrier PE device of a virtual private network VPN.
- the operator PE device can receive the routing information sent by the gateway device, where the routing information is generated by the controller according to the address information of each terminal device in the SDN and sent to the gateway device. .
- the address information of each terminal device included in the SDN may be transmitted to the virtual private network VPN, and the corresponding route may be saved in each device of the VPN.
- the controller in the SDN can establish a neighbor relationship with the gateway device, and the gateway device can also pre-configure the border gateway protocol BGP routing protocol, and the gateway device can also be connected to the carrier PE device of the VPN.
- the controller can obtain address information of each terminal device included in the locally saved SDN. Then, the controller may generate routing information according to the address information of each terminal device, and send the routing information to the gateway device.
- the foregoing terminal device may be a virtual machine in the SDN.
- the address information of the terminal device may be vport data.
- the gateway device may send the routing information to the operator PE device of the VPN connected to itself to deliver the routing information to the VPN.
- an operator PE device can receive routing information transmitted by a gateway device.
- the carrier PE device can also publish its received routing information in the VPN.
- the operator PE device can send the routing information it receives to the PE device and/or the CE device connected to itself, so that each device in the VPN stores the routing information received by the operator PE device.
- each device can send the service data packet it receives according to the locally saved routing information.
- a BGP peer relationship can be established between the PEs and the CEs in the VPN. After receiving the routing information sent by the gateway, the PE can send the routing information to other PEs or CEs according to the BGP protocol.
- the device is configured to enable each PE device and CE device in the VPN to obtain routing information of each terminal device in the SDN.
- the controller of the SDN can obtain the address information of each terminal device included in the SDN, and can generate routing information according to the address information of each terminal device. Further, the routing information may be sent to the operator PE device and the CE device of the VPN through the gateway device. Therefore, each PE device and CE device in the VPN can locally save routing information of each terminal device in the SDN.
- any device in the VPN needs to send service data packets
- the service data packet can be sent to the terminal device in the SDN according to the locally saved routing information, so that the new subnet does not need to be added and the network is re-planned. Therefore, the complexity of transmitting a message inside the VPN to the SDN can be reduced.
- a packet sending method is also provided, which is applied to a carrier PE device of a virtual private network VPN. As shown in FIG. 2, the method includes the following steps.
- the operator PE device can receive the service data packet, where the service data packet includes the address information of the destination terminal device, and the destination terminal device is any terminal device in the SDN.
- the VPN may send some or all of the service data of the VPN to the SDN.
- any device in the VPN can generate corresponding service data packets for the service data to be sent.
- the service data packet may include address information of the destination terminal device.
- the service data packet can be further sent to the operator PE device.
- the operator PE device can receive the service data message, where the service data message includes the address information of the destination terminal device.
- the destination terminal device is a terminal device in the SDN.
- the operator PE device may search for the target routing information that matches the destination terminal device in the locally saved routing information according to the address information of the destination terminal device, and send the service according to the target routing information.
- the locally saved routing information is generated by the controller according to the address information of each terminal device in the SDN, and is sent by the controller to the PE device via the gateway device.
- the carrier PE device in the VPN can be connected to the gateway device of the SDN.
- the gateway device in the SDN may send routing information to the operator PE device in the VPN, where the routing information is generated by the controller according to the address information of each terminal device in the SDN and sent to the gateway device.
- the service PE device may send the service data packet to the gateway device to send the corresponding service data to the SDN.
- the operator PE device can find the target routing information that matches the destination terminal device in the locally saved routing information according to the address information of the destination terminal device, and send the service data packet according to the target routing information.
- the PE device in the VPN may send the service data packet according to the address information of the destination terminal device included in the service data packet and the locally saved routing information.
- the terminal device corresponding to the address information of the destination terminal device in the SDN is re-planned without adding a new subnet. Therefore, the complexity of converting service data inside the VPN to the SDN can be reduced.
- the present disclosure example also provides a corresponding device example.
- FIG. 3 is a schematic diagram of a route establishing apparatus, which is applied to a controller of a software-defined network SDN, where the controller establishes a neighbor relationship with a gateway device of the SDN, and the gateway device is configured with a border gateway protocol BGP.
- a routing protocol, the gateway device being connected to a carrier PE device of the virtual private network VPN.
- the apparatus includes a processor 301 and a non-transitory storage medium 302.
- the non-transitory storage medium 302 stores a plurality of machine readable instruction modules executed by the processor 301.
- the plurality of machine readable instruction modules includes an acquisition module 310 and a processing module 320.
- the obtaining module 310 is configured to obtain address information of each terminal device included in the locally saved SDN, where the controller establishes a neighbor relationship with a gateway device of the SDN, where the gateway device is configured with a border gateway Protocol (BGP) routing protocol, and the gateway device is connected to a carrier edge (PE) device of a virtual private network (VPN).
- BGP border gateway Protocol
- PE carrier edge
- the processing module 320 is configured to generate routing information according to the address information of each terminal device, and send the routing information to the PE device by using the gateway device, so that the PE device performs the routing information according to the routing information.
- the message is sent.
- routing information further includes route identifier (RD) information corresponding to each terminal device.
- RD route identifier
- the controller of the SDN can obtain address information of each terminal device included in the SDN, and generate routing information according to address information of each terminal device. Further, the routing information may be sent to the operator PE device of the VPN through the gateway device. Therefore, each device in the VPN can save the routing information locally.
- the service data packet can be sent to the terminal device in the SDN according to the locally saved routing information, so that no new subnet needs to be added. Re-plan the network. Therefore, the complexity of converting service data inside the VPN to the SDN can be reduced.
- the apparatus includes a processor 401 and a non-transitory storage medium 402.
- the non-transitory storage medium 402 stores a plurality of machine readable instruction modules executed by the processor 401.
- the plurality of machine readable instruction modules includes a receiving module 410.
- the receiving module 410 is configured to receive routing information sent by the gateway device, where the routing information is generated by the controller according to address information of each terminal device in the SDN and sent to the gateway device.
- the apparatus further includes:
- the publishing module 420 is configured to advertise the routing information in the VPN.
- a controller of an SDN can obtain address information of each terminal device included in the SDN, and generate routing information according to address information of each terminal device. Further, the routing information may be sent to the operator PE device of the VPN through the gateway device. Therefore, each device in the VPN can locally save the routing information generated by the controller.
- the service data packet can be sent to the terminal device in the SDN according to the locally saved routing information, without adding a new subnet. Re-plan the network. Therefore, the complexity of converting service data inside the VPN to the SDN can be reduced.
- FIG. 5 is a packet sending apparatus provided in an example of the present disclosure, which is applied to a carrier PE device of a virtual private network VPN, where the operator PE device is connected to a gateway device of a software-defined network SDN.
- the apparatus includes a processor 501 and a non-transitory storage medium 502.
- the non-transitory storage medium 502 stores a plurality of machine readable instruction modules executable by the processor 501.
- the machine readable instruction module includes a receiving module 510 and a transmitting module 520.
- the receiving module 510 is configured to receive a service data packet, where the service data packet includes address information of the destination terminal device in the SDN.
- the sending module 520 is configured to search, according to the address information of the destination terminal device, the target routing information that matches the destination terminal device in the locally saved routing information, and send the service data packet according to the target routing information.
- the locally saved routing information is generated by the controller according to the address information of each terminal device in the SDN, and is sent by the controller to the PE device via the gateway device.
- the PE device in the VPN may send the service data packet according to the address information of the destination terminal device included in the service data packet and the locally saved routing information. Re-plan the network to the gateway device without adding a new subnet. Therefore, the complexity of converting service data inside the VPN to the SDN can be reduced.
- routing establishment method provided by the present disclosure will be described in detail below with reference to a specific example.
- the overall network structure of this example includes SDN and nested VPN.
- the SDN includes a controller 600, a switching device 6001, a switching device 6002, a switching device 6003, and a gateway device 6100.
- the SDN may further include a plurality of virtual machines (not shown); the nested VPN includes an operator PE device 6010.
- the gateway device 6100 in the SDN is connected to the operator PE device 6010 of the VPN.
- the controller 600 of the SDN may obtain vport data of each virtual machine included in the SDN, and may generate routing information according to vport data of each virtual machine, and send the routing information to the gateway device. 6100.
- the gateway device 6100 After receiving the routing information sent by the controller 600 to the gateway 600, the gateway device 6100 can send the routing information to the Carrier PE device 6010 of the VPN to which it is connected.
- the operator PE device 6010 may advertise the routing information in the VPN. For example, the operator PE device 6010 can send the routing information to the operator PE device 6020 and the operator CE device 6030. Further, the operator PE device 6020 can send the routing information to the operator CE device 6040 and the user PE device. 6050; User PE device 6050 further sends the routing information to user CE device 6060.
- the overall network structure of this example includes SDN and nested VPN.
- the SDN includes a controller 700, a switching device 7001, a switching device 7002, a switching device 7003, and a gateway device 7100.
- the SDN may further include multiple virtual machines (not shown); the nested VPN includes an operator PE device 7010.
- the gateway device 7100 in the SDN is connected to the operator PE device 7010 of the VPN.
- each device in the VPN has already saved routing information of each terminal device in the SDN.
- the resource website type service in the VPN may not be able to carry load pressure due to sudden demand.
- the server may not be able to provide sufficient storage space for the user due to the increase in traffic.
- the part of the service data in the VPN can be sent to the terminal device in the SDN, that is, the service data in the VPN is sent to the terminal device in the cloud.
- any device in the VPN such as the user CE device 8060, can generate a corresponding service data packet for the service data to be converted.
- the service data packet may include address information of the destination virtual machine.
- the user CE device 7060 can send the service data packet to the user PE device 7050.
- the user PE device 7050 may send the service data packet to the operator PE device 7020 according to the locally saved routing information according to the address information of the destination virtual machine included in the service data packet.
- the operator PE device 7020 may send the service data packet to the operator PE device 7010 according to the locally saved routing information according to the address information of the destination virtual machine included in the service data packet.
- the operator PE device 7010 may send the service data packet to the gateway device 7100 of the SDN according to the locally saved routing information according to the address information of the destination virtual machine included in the service data packet.
- the gateway device 7100 may send the service data packet to the destination virtual machine according to the locally saved flow table and the address information of the destination virtual machine included in the service data packet, for example, The service data packet can be sent to the switching device through the switching device 7003. 7003 connected destination virtual machine.
- the destination VM can share the load pressure of the original server in the VPN. For example, if the service of the storage space such as the network disk is provided as an example, after the service data packet is sent to the destination virtual machine, the destination virtual machine can provide a certain storage space for the user to store the storage space that the user wants to store. content.
- the description is relatively simple, and the relevant parts can be referred to the partial description of the method example.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本公开示例提供了一种路由建立方法、报文发送方法及装置、以及软件定义网络(SDN)的控制器。所述路由建立方法应用于所述SDN的控制器,所述控制器与所述SDN的网关设备建立了邻居关系,所述网关设备配置了边界网关协议BGP路由协议,所述网关设备与VPN的运营商PE设备相连。根据该路由建立方法的示例,控制器获得本地保存的所述SDN中包括的每个终端设备的地址信息。控制器根据所述每个终端设备的地址信息,生成路由信息。控制器经由所述网关设备向所述PE设备发布所述路由信息,以使所述PE设备根据所述路由信息进行报文发送。
Description
相关申请的交叉引用
本专利申请要求于2016年5月10日提交的、申请号为201610305131.X、发明名称为“一种路由建立方法、业务数据转换方法及装置”的中国专利申请的优先权,该申请的全文以引用的方式并入本文中。
SDN(Software Defined Network,软件定义网络)技术可将控制平面与转发平面分离开,打破了传统网络交换机/路由器设计的封闭性,提高了网络管理的可编程性,降低了网络交换机/路由器的复杂性。
SDN可包括网关设备、控制器、交换设备和终端设备等。控制器是控制中心,可以根据用户的配置或者动态运行的协议生成流表发送给交换设备。交换设备可进一步地将流表发送给与自身连接的各终端设备。交换设备或终端设备接收到报文后,可以根据本地保存的流表对报文进行发送。其中,上述终端设备可以为虚拟机。
为了更清楚地说明本公开示例中的技术方案,下面将对示例描述中所需要使用的附图作简单地介绍。显而易见地,下面描述中的附图仅仅是本公开的一些示例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本公开示例提供的一种路由建立方法的流程图。
图2为本公开示例提供的一种报文发送方法的流程图。
图3为本公开示例提供的一种路由建立装置的结构示意图。
图4为本公开示例提供的另一种路由建立装置的结构示意图。
图5为本公开示例提供的一种报文发送装置的结构示意图。
图6为本公开示例的路由建立过程示意图。
图7为本公开示例的报文发送过程示意图。
在VPN(Virtual Private Network,虚拟专用网络)中,可以包括两种类型的路由设备:PE(Provider Edge,运营商边缘设备)设备和CE(Customer Edge,客户端边缘设备)设备。并且,在VPN中,实际上可存在用户CE设备、用户PE设备、运营商CE设备以及运营商PE设备。在实际应用中,各设备间可以通过传递VPN-IPv4路由信息,来得知网络中各设备的路由信息。具体地,用户CE设备可将携带自身路由信息的VPN-IPv4路由信息发送给用户PE设备,用户PE设备可将该VPN-IPv4路由信息发送给运营商CE设备,运营商CE设备可将该VPN-IPv4路由信息发送给运营商PE设备;运营商PE设备可将该VPN-IPv4路由信息发送给对端运营商PE设备,并且,对端运营商PE设备可进一步地通过其运营商CE设备、用户PE设备将该VPN-IPv4路由信息发送给用户CE设备,从而完成路由信息的传递。当任一设备接收到数据报文后,可以通过自身保存的路由,对数据报文进行发送。
可将SDN与二层、三层网络嵌套连接,例如SDN与VPN进行嵌套,其中,SDN与VPN间可以通过SDN中的网关设备连接。由于SDN是利用openflow流表指导报文发送,三层网络是利用路由表项指导报文发送,因此网关设备和VPN中的各PE、CE设备无法获得SDN中各终端设备的路由地址,例如32位地址信息。SDN中各终端设备可以是服务器、vRouter(virtual Router,虚拟路由)、VM(virtual machine,虚拟机),当然,如果SDN中存在VXLAN隧道连接,则该终端设备也可以是VTEP(VXLAN Tunnel End Point,VXLAN节点设备)。
而此时,若VPN内部的原有设备因被访问的压力增大,导致无法承担访问压力的情况。这种情况下,需将VPN内部的部分或全部的业务数据发送给SDN中的终端设备,以缓解VPN中原有设备被访问的压力。由于SDN中的数据发送是依靠控制器下发的流表完成的,网关设备没有SDN中终端设备的路由信息,从而VPN中的设备无法根据相应的路由表项将报文发送给SDN中的终端设备。因此,只能通过重新规划网络,例如添加新子网,使得将业务数据从VPN发送到SDN的过程过于复杂。
为了降低将VPN内部的业务数据发送到SDN中的复杂度,本公开示例提供了一种路由建立、报文发送的方法及装置。在本公开示例中,利用SDN中的控制器获取SDN中保存的各终端设备的地址信息,生成路由信息,并利用相应的路由协议(如BGP路由协议)通过SDN中连接VPN的网关设备将该路由信息发送给VPN中的各设备,例如VPN中的PE、CE设备。当VPN中的PE或CE设备需要将报文(如业务数据报文)上传至SDN中的终端设备
时,可以根据获取的路由信息发送该报文,从而无需重新规划网络,降低了将VPN中的报文发送给SDN中的终端设备的复杂度。
下面将结合本公开示例中的附图,对本公开示例中的技术方案进行清楚、完整地描述,显然,所描述的示例仅仅是本公开一部分示例,而不是全部的示例。基于本公开中的示例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他示例,都属于本公开保护的范围。
需要说明的是,在不冲突的情况下,本公开中的示例及示例中的特征可以相互组合。下面将参考附图并结合示例来详细说明本公开。
为了降低将VPN内部的业务数据转换到SDN中的复杂度,本公开示例提供了一种路由建立方法过程,应用于软件定义网络SDN的控制器。如图1所示,该过程包括以下步骤。
在步骤S101,控制器可获得本地保存的所述SDN中包括的每个终端设备的地址信息。
在本公开示例中,获取了SDN中各终端设备的地址信息,可以根据获取的地址信息生成路由信息,其中,该路由信息可以是路由表项,也可以是路由表项中的部分信息,例如源地址、目的地址、RD、RT等信息。
在本公开示例中,控制器与网关设备建立BGP邻居,可将SDN中生成的各终端设备的路由信息利用BGP协议通过网关设备传递给VPN中的各设备,进而使VPN中的各设备获取SDN中各终端设备的路由信息,以使VPN中的各设备可以根据获取的路由信息向SDN中的各终端设备发送报文。这样,可降低将VPN内部的业务数据发送到SDN中的复杂度。为此,SDN中的控制器与网关设备可以建立邻居关系。网关设备还可以预先配置边界网关协议BGP路由协议,并且,网关设备还可以与VPN的运营商PE设备相连。
在本公开示例中,控制器可以获得本地保存的SDN中包括的每个终端设备的地址信息。其中,上述终端设备可以是SDN中的虚拟机。相应的,终端设备的地址信息可以包括vport数据(即虚拟出端口)。
例如,控制器可以预先在本地构建数据库,并获取SDN中包括的每个终端设备的地址信息,进而可以将获得的每个终端设备的地址信息保存在该数据库中,以便于控制器获取SDN中各终端设备的地址信息。
在步骤S102,控制器可根据所述每个终端设备的地址信息,生成路由信息,并向所述网关设备发送所述路由信息,以使与所述网关设备连接的运营商PE设备根据所述路由信息建立路由,即根据路由信息发送报文。
当控制器获得每个终端设备的地址信息后,可以根据每个终端设备的地址信息,生成路由信息,例如,可以生成用于进行报文发送的路由表项,该路由表项承载了所述路由信息。然后,可向网关设备发送该路由信息。其中,所述路由信息可包括:终端设备的地址信息,例如接口信息、IP地址、MAC地址等。
控制器根据各终端设备的地址信息生成路由信息时,可以根据映射表将各终端设备的vport数据映射到VPN路由,得到各终端设备的IP地址、MAC地址等。该映射表定义了一种数据结构,其中可以限定控制器的名称、VPN的名称、端口的类型、用于区分不同VPN的RD信息、用于控制VPN路由信息的发布和学习的扩展团体属性(Route target,RT)信息、终端设备的MAC地址、IP地址等。控制器可以从本地保存的各终端设备的vport数据中提取需要转换的信息,根据映射表将该提取的信息映射为VPN路由信息。然后,可将该VPN路由信息以BGP update报文的形式发送给网关设备。
在本公开示例中,当网关设备接收到控制器向其发送的路由信息后,其可以将该路由信息发送给与自身相连的VPN的运营商PE设备,以将路由信息传递到VPN中。
当运营商PE设备接收到网关设备向其发送的路由信息后,运营商PE设备可以在VPN中发布其接收的路由信息。例如,运营商PE设备可以将该路由信息发送给与自身连接的所有的PE设备和CE设备,以使VPN中的各设备都保存有运营商PE设备接收的路由信息。进而,当需要将业务数据转换到SDN中时,各设备都可以根据本地保存的路由信息,发送其接收到的业务数据报文。
运营商PE设备在VPN中发布其接收的路由信息的过程在此不进行赘述。
在一个示例中,上述路由信息中还可以包括对应每个终端设备的路由标识符RD信息,以作为传递过程中用于隔离VPN的标记。在VPN应用中,不同VPN的IP地址空间是独立的,为了在公网中对这些不同的VPN实例的IP地址加以区分,可以使用RD信息来作为用于隔离VPN的标记。在根据本公开的SDN与VPN的嵌套网络中,SDN中的各终端设备、例如每个租户的vRouter可以理解为与一个VPN实例相对应。当SDN中的控制器根据本地保存的各终端设备的vport数据生成路由信息时,可以在路由信息中增加该RD信息,使得该路由信息经由网关设备被发送给PE设备时,PE设备可以根据该RD信息来区分不同的终端设备。
通过上述示例可以看出,SDN的控制器可以获得该SDN中包括的每个终端设备的地址信息,并根据每个终端设备的地址信息生成路由信息。进一步地,控制器可以将该路由信息通过网关设备发送给VPN的运营商PE设备。因此,VPN中的各设备都可以在本地保存由控制
器生成的路由信息。当VPN中的任一设备进行业务数据转换时,可以根据本地保存的路由信息将业务数据报文发送到SDN中,而不需要添加新子网,重新规划网络。因此能够降低将VPN内部的业务数据转换到SDN中的复杂度。
在一个示例中,还提供了另一种路由建立方法,应用于虚拟专用网络VPN的运营商PE设备。根据该路由建立方法,运营商PE设备可接收网关设备发送的路由信息,其中,所述路由信息是所述控制器根据所述SDN中各终端设备的地址信息生成并发送给所述网关设备的。
在本公开示例中,可将SDN中包括的各终端设备的地址信息传递给虚拟专用网络VPN,进而可在VPN的各设备中保存相应的路由。这样,可降低将VPN内部的业务数据转换到SDN中的复杂度。为此,SDN中的控制器可与网关设备可以建立邻居关系,网关设备还可以预先配置边界网关协议BGP路由协议,并且,网关设备还可以与VPN的运营商PE设备相连。
在本公开示例中,控制器可以获得本地保存的SDN中包括的每个终端设备的地址信息。然后,控制器可根据每个终端设备的地址信息,生成路由信息,并向网关设备发送该路由信息。其中,上述终端设备可以是SDN中的虚拟机。相应的,终端设备的地址信息可以是vport数据。
在本公开示例中,当网关设备接收到控制器向其发送的路由信息后,其可以将该路由信息发送给与自身相连的VPN的运营商PE设备,以将路由信息传递到VPN中。因此,在本公开示例中,运营商PE设备可以接收网关设备发送的路由信息。
在一个示例中,运营商PE设备还可以在VPN中发布其接收的路由信息。例如,运营商PE设备可以将其接收的路由信息发送给与自身连接的PE设备和/或CE设备,以使VPN中的各设备都保存有运营商PE设备接收的路由信息。进而,当需要将业务数据转换到SDN中时,各设备都可以根据本地保存的路由信息,发送其接收到的业务数据报文。
由于VPN中的各PE设备、CE设备间可以建立BGP邻居关系,当VPN中的某个PE设备接收到网关设备发送的路由信息后,可以根据BGP协议将该路由信息发送给其他PE设备或CE设备,以使VPN中的各PE设备、CE设备可以获得SDN中各终端设备的路由信息。
通过上述示例可以看出,SDN的控制器可以获得该SDN中包括的每个终端设备的地址信息,并可根据每个终端设备的地址信息生成路由信息。进一步地,可以将该路由信息通过网关设备发送给VPN的运营商PE设备、CE设备。因此,VPN中的各PE设备、CE设备都可以在本地保存SDN中各终端设备的路由信息。当VPN中的任一设备需要将业务数据报文发
送给SDN中的终端设备时,可以根据本地保存的路由信息将业务数据报文发送到SDN中的终端设备,从而不需要添加新子网,重新规划网络。因此能够降低将VPN内部的报文发送到SDN中的复杂度。
在另一示例中,还提供了一种报文发送方法,应用于虚拟专用网络VPN的运营商PE设备,如图2所示,该方法包括以下步骤。
在步骤S201,运营商PE设备可接收业务数据报文,其中,所述业务数据报文中包括目的终端设备的地址信息,所述目的终端设备为SDN中的任意终端设备。
当VPN内部因突发需求,原有服务器无法负载访问压力时,可以将VPN内部的部分或者全部业务数据发送到SDN中。例如,VPN中的任一设备可以针对待发送的业务数据,生成相应的业务数据报文。其中,该业务数据报文中可以包括目的终端设备的地址信息。并且,可以进一步地将该业务数据报文发送给运营商PE设备。
因此,在本公开示例中,运营商PE设备可以接收业务数据报文,其中,该业务数据报文中包括目的终端设备的地址信息。其中,该目的终端设备为SDN中的终端设备。
在步骤S202,运营商PE设备可根据所述目的终端设备的地址信息,在本地保存的路由信息中查找与所述目的终端设备匹配的目标路由信息,并根据所述目标路由信息发送所述业务数据报文。其中,所述本地保存的路由信息包括由所述控制器根据所述SDN中各终端设备的地址信息生成,并由所述控制器经由所述网关设备发送给所述PE设备。
在本公开示例中,VPN中的运营商PE设备可以与SDN的网关设备相连。并且,SDN中的网关设备可以向VPN中的运营商PE设备发送路由信息,该路由信息是控制器根据SDN中各终端设备的地址信息生成并发送给网关设备的。
当运营商PE设备接收到业务数据报文后,可以将该业务数据报文发送给网关设备,以将对应的业务数据发送到SDN中。
例如,运营商PE设备可以根据目的终端设备的地址信息,在本地保存的路由信息中查找与该目的终端设备匹配的目标路由信息,并根据该目标路由信息发送该业务数据报文。
根据本公开的示例,VPN中的PE设备接收到业务数据报文后,可以根据该业务数据报文中包括的目的终端设备的地址信息,以及本地保存的路由信息,将该业务数据报文发送给SDN中的与目的终端设备的地址信息对应的终端设备,而不需要添加新子网,重新规划网络。因此能够降低将VPN内部的业务数据转换到SDN中的复杂度。
相应于上面的方法示例,本公开示例还提供了相应的装置示例。
图3为本公开示例提供的一种路由建立装置,应用于软件定义网络SDN的控制器,所述控制器与所述SDN的网关设备建立了邻居关系,所述网关设备配置了边界网关协议BGP路由协议,所述网关设备与虚拟专用网络VPN的运营商PE设备相连。所述装置包括:处理器301以及非暂时性存储介质302。非暂时性存储介质302存储有处理器301执行的多个机器可读指令模块。所述多个机器可读指令模块包括获得模块310和处理模块320。
获得模块310,用于获得本地保存的所述SDN中包括的每个终端设备的地址信息,其中,所述控制器与所述SDN的网关设备建立了邻居关系,所述网关设备配置了边界网关协议(BGP)路由协议,并且所述网关设备与虚拟专用网络(VPN)的运营商边缘(PE)设备相连。
处理模块320,用于根据所述每个终端设备的地址信息,生成路由信息,并经由所述网关设备向所述PE设备发送所述路由信息,以使所述PE设备根据所述路由信息进行报文发送。
进一步地,所述路由信息中还包括对应每个终端设备的路由标识符(RD)信息。
本公开示例提供的一种路由建立装置,SDN的控制器可以获得该SDN中包括的每个终端设备的地址信息,并根据每个终端设备的地址信息生成路由信息。进一步地,可以将该路由信息通过网关设备发送给VPN的运营商PE设备。因此,VPN中的各设备都可以在本地保存该路由信息。当VPN中的任一设备需要将业务数据报文发送给SDN中的终端设备时,可以根据本地保存的路由信息将业务数据报文发送给SDN中的终端设备,从而不需要添加新子网,重新规划网络。因此能够降低将VPN内部的业务数据转换到SDN中的复杂度。
图4为本公开示例提供的一种路由建立装置,应用于虚拟专用网络VPN的运营商PE设备,所述运营商PE设备与软件定义网络SDN的网关设备相连,所述网关设备与所述SDN的控制器建立了邻居关系,所述网关设备配置了边界网关协议BGP路由协议。所述装置包括:处理器401以及非暂时性存储介质402。非暂时性存储介质402存储有处理器401执行的多个机器可读指令模块。所述多个机器可读指令模块包括接收模块410。
接收模块410,用于接收所述网关设备发送的路由信息,其中,所述路由信息是所述控制器根据所述SDN中各终端设备的地址信息生成并发送给所述网关设备的。
在另一示例中,所述装置还包括:
发布模块420,用于在所述VPN中发布所述路由信息。
根据本公开的示例,SDN的控制器可以获得该SDN中包括的每个终端设备的地址信息,并根据每个终端设备的地址信息生成路由信息。进一步地,可以将该路由信息通过网关设备发送给VPN的运营商PE设备。因此,VPN中的各设备都可以在本地保存控制器生成的路由信息。当VPN中的任一设备需要将业务数据报文发送给SDN中的终端设备时,可以根据本地保存的路由信息将业务数据报文发送给SDN中的终端设备,而不需要添加新子网,重新规划网络。因此能够降低将VPN内部的业务数据转换到SDN中的复杂度。
图5为本公开示例提供的一种报文发送装置,应用于虚拟专用网络VPN的运营商PE设备,所述运营商PE设备与软件定义网络SDN的网关设备相连。所述装置包括:处理器501和非暂时性存储介质502。非暂时性存储介质502存储有处理器501可执行的多个机器可读指令模块。所述机器可读指令模块包括接收模块510和发送模块520。
接收模块510,用于接收业务数据报文,其中,所述业务数据报文中包括SDN中的目的终端设备的地址信息。
发送模块520,用于根据所述目的终端设备的地址信息,在本地保存的路由信息中查找与所述目的终端设备匹配的目标路由信息,并根据所述目标路由信息发送所述业务数据报文,其中,所述本地保存的路由信息是由所述控制器根据所述SDN中各终端设备的地址信息生成,并通过所述控制器经由所述网关设备发送给所述PE设备。
根据本公开的示例,VPN中的PE设备接收到业务数据报文后,可以根据该业务数据报文中包括的目的终端设备的地址信息,以及本地保存的路由信息,将该业务数据报文发送给网关设备,而不需要添加新子网,重新规划网络。因此能够降低将VPN内部的业务数据转换到SDN中的复杂度。
下面结合一个具体的示例对本公开提供的路由建立方法进行详细的说明。
如图6所示,本示例的整体网络结构中,包括SDN和嵌套VPN。该SDN包括控制器600、交换设备6001、交换设备6002、交换设备6003以及网关设备6100,SDN中还可以包括多个虚拟机(图中未示出);该嵌套VPN包括运营商PE设备6010、运营商PE设备6020、运营商CE设备6030、运营商CE设备6040、用户PE设备6050以及用户CE设备6060。并且,SDN中的网关设备6100与VPN的运营商PE设备6010相连。
在本公开示例中,SDN的控制器600可以获得该SDN中包括的每个虚拟机的vport数据,并且,可以根据每个虚拟机的vport数据生成路由信息,并将该路由信息发送给网关设备6100。
网关设备6100接收到控制器600向其发送的路由信息后,其可以将该路由信息发送给与
自身相连的VPN的运营商PE设备6010。
运营商PE设备6010接收到网关设备6100向其发送的路由信息后,可以在VPN中发布该路由信息。例如,运营商PE设备6010可以将该路由信息发送给运营商PE设备6020和运营商CE设备6030;进一步地,运营商PE设备6020可以将该路由信息发送给运营商CE设备6040和用户PE设备6050;用户PE设备6050进一步地将该路由信息发送给用户CE设备6060。
下面结合一个具体的示例对本公开提供的报文发送方法进行详细的说明。
如图7所示,本示例的整体网络结构中,包括SDN和嵌套VPN。该SDN包括控制器700、交换设备7001、交换设备7002、交换设备7003以及网关设备7100,SDN中还可以包括多个虚拟机(图中未示出);该嵌套VPN包括运营商PE设备7010、运营商PE设备7020、运营商CE设备7030、运营商CE设备7040、用户PE设备7050以及用户CE设备7060。并且,SDN中的网关设备7100与VPN的运营商PE设备7010相连。
在本公开示例中,VPN中的每个设备都已经保存了SDN中各终端设备的的路由信息。
在本示例中,VPN中的资源网站类业务,因突发需求原有服务器可能无法承载负载压力。例如,为用户提供网盘等存储空间的业务,因业务量增加服务器可能无法为用户提供足够的存储空间。此时,可以将VPN内部的该部分业务数据发送给SDN中的终端设备,即将VPN中的业务数据发送给云端的终端设备。
当需要将业务数据发送给SDN中的终端设备时,VPN中的任一设备,如用户CE设备8060,可以针对待转换的业务数据,生成相应的业务数据报文。其中,该业务数据报文中可以包括目的虚拟机的地址信息。
用户CE设备7060生成业务数据报文后,可以将该业务数据报文发送给用户PE设备7050。进一步地,用户PE设备7050可以根据该业务数据报文中包括的目的虚拟机的地址信息,根据本地保存的路由信息,将该业务数据报文发送给运营商PE设备7020。进一步地,运营商PE设备7020可以根据该业务数据报文中包括的目的虚拟机的地址信息,根据本地保存的路由信息,将该业务数据报文发送给运营商PE设备7010。进一步地,运营商PE设备7010可以根据该业务数据报文中包括的目的虚拟机的地址信息,根据本地保存的路由信息,将该业务数据报文发送给SDN的网关设备7100。网关设备7100接收到该业务数据报文后,可以根据本地保存的流表,以及该业务数据报文中包括的目的虚拟机的地址信息,将该业务数据报文发送给目的虚拟机,例如,可以通过交换设备7003将该业务数据报文发送给与交换设备
7003连接的目的虚拟机。
将业务数据报文发送给目的虚拟机后,目的虚拟机即可分担VPN中的原服务器的负载压力。如,仍以为用户提供网盘等存储空间的业务为例,将业务数据报文发送给目的虚拟机后,目的虚拟机就可以为用户提供一定的存储空间,以供用户存储其想要存储的内容。
对于装置示例而言,由于其基本相似于方法示例,所以描述的比较简单,相关之处参见方法示例的部分说明即可。
需要说明的是,在本文中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本公开中的各个示例均采用相关的方式描述,各个示例之间相同相似的部分互相参见即可,每个示例重点说明的都是与其他示例的不同之处。尤其,对于系统示例而言,由于其基本相似于方法示例,所以描述的比较简单,相关之处参见方法示例的部分说明即可。
以上所述仅为本公开的较佳示例而已,并非用于限定本公开的保护范围。凡在本公开的精神和原则之内所作的任何修改、等同替换、改进等,均包含在本公开的保护范围内。
Claims (10)
- 一种路由建立方法,包括:软件定义网络(SDN)中的控制器获得本地保存的所述SDN中包括的每个终端设备的地址信息,其中,所述控制器与所述SDN的网关设备建立了邻居关系,所述网关设备配置了边界网关协议(BGP)路由协议,并且所述网关设备与虚拟专用网络(VPN)的运营商边缘(PE)设备相连;所述控制器根据所述每个终端设备的地址信息,生成路由信息;所述控制器经由所述网关设备向所述PE设备发布所述路由信息,以使所述PE设备根据所述路由信息进行报文发送。
- 根据权利要求1所述的方法,其中,针对每个终端设备生成的所述路由信息中包括对应该终端设备的路由标识符(Route Distinguisher,RD)信息。
- 一种报文发送方法,所述方法包括:虚拟专用网络(VPN)的运营商PE设备接收由软件定义网络(SDN)的网关设备发送的路由信息,其中,所述PE设备与所述网关设备相连,所述网关设备与所述SDN的控制器建立了邻居关系,所述网关设备配置了边界网关协议BGP路由协议,其中,所述路由信息是由所述控制器根据所述SDN中各终端设备的地址信息生成,并通过所述控制器经由所述网关设备发送给所述PE设备。
- 根据权利要求3所述的方法,其中,还包括:所述PE设备在所述VPN中发布所述路由信息。
- 根据权利要求3所述的方法,还包括:所述PE设备接收业务数据报文,其中,所述业务数据报文中包括所述SDN中的目的终端设备的地址信息;所述PE设备根据所述目的终端设备的地址信息,在本地保存的所述路由信息中查找与所述目的终端设备匹配的目标路由信息,并根据所述目标路由信息发送所述业务数据报文。
- 一种报文发送装置,包括:处理器;以及存储有机器可执行指令的非暂时性存储介质,其中,通过执行所述机器可执行指令,所述处理器被使得执行如权利要求3所述的报文发送方法:接收所述网关设备发送的路由信息,其中,所述路由信息是由所述控制器根据所述SDN中各终端设备的地址信息生成,并通过所述控制器经由所述网关设备发送给所述PE设备。
- 根据权利要求6所述的装置,其中,所述机器可执行指令还使得所述处理器:所述VPN中发布所述路由信息。
- 根据权利要求6所述的装置,其中,所述机器可执行指令还使得所述处理器:接收业务数据报文,其中,所述业务数据报文中包括所述SDN中的目的终端设备的地址信息;根据所述目的终端设备的地址信息,在本地保存的所述路由信息中查找与所述目的终端设备匹配的目标路由信息,并根据所述目标路由信息发送所述业务数据报文。
- 一种软件定义网络(SDN)的控制器,包括:处理器;以及存储有机器可执行指令的非暂时性存储介质,其中,通过执行所述机器可执行指令,所述处理器被使得:获得本地保存的所述SDN中包括的每个终端设备的地址信息,其中,所述控制器与所述SDN的网关设备建立了邻居关系,所述网关设备配置了边界网关协议(BGP)路由协议,并且所述网关设备与虚拟专用网络(VPN)的运营商边缘(PE)设备相连;根据所述每个终端设备的地址信息,生成路由信息;经由所述网关设备向所述PE设备发布所述路由信息,以使所述PE设备根据所述路由信息进行报文发送。
- 根据权利要求9所述的装置,其中,针对每个终端设备生成的所述路由信息中包括对应该终端设备的路由标识符(Route Distinguisher,RD)信息。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17795466.6A EP3457640B1 (en) | 2016-05-10 | 2017-05-03 | Route establishment and message sending |
JP2018559209A JP2019519146A (ja) | 2016-05-10 | 2017-05-03 | ルーティング確立、パケット送信 |
US16/099,489 US20190109781A1 (en) | 2016-05-10 | 2017-05-03 | Route Establishment and Message Sending |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610305131.XA CN107360089B (zh) | 2016-05-10 | 2016-05-10 | 一种路由建立方法、业务数据转换方法及装置 |
CN201610305131.X | 2016-05-10 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017193848A1 true WO2017193848A1 (zh) | 2017-11-16 |
Family
ID=60266228
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/082897 WO2017193848A1 (zh) | 2016-05-10 | 2017-05-03 | 路由建立、报文发送 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20190109781A1 (zh) |
EP (1) | EP3457640B1 (zh) |
JP (1) | JP2019519146A (zh) |
CN (1) | CN107360089B (zh) |
WO (1) | WO2017193848A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108965090A (zh) * | 2018-07-12 | 2018-12-07 | 中国联合网络通信集团有限公司 | 一种vpn网络用户路由数的控制方法及sdn控制器 |
CN109257296A (zh) * | 2018-10-30 | 2019-01-22 | 中国联合网络通信集团有限公司 | 路由发布数限制方法及装置 |
TWI715107B (zh) * | 2018-12-25 | 2021-01-01 | 大陸商中國銀聯股份有限公司 | 基於sdn的vpn流量調度方法以及基於sdn的vpn流量調度系統 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10637890B2 (en) | 2016-06-09 | 2020-04-28 | LGS Innovations LLC | Methods and systems for establishment of VPN security policy by SDN application |
US10484428B2 (en) | 2016-06-09 | 2019-11-19 | LGS Innovations LLC | Methods and systems for securing VPN cloud servers |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103607349A (zh) * | 2013-11-14 | 2014-02-26 | 华为技术有限公司 | 虚拟网络中确定路由的方法及运营商边缘设备 |
US20140211615A1 (en) * | 2012-12-18 | 2014-07-31 | Juniper Networks, Inc. | Aggregation network with centralized control |
CN105357099A (zh) * | 2015-12-18 | 2016-02-24 | 南京优速网络科技有限公司 | 一种基于sdn的虚拟专用网络的实现方法 |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7145898B1 (en) * | 1996-11-18 | 2006-12-05 | Mci Communications Corporation | System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture |
US7894432B2 (en) * | 2005-04-09 | 2011-02-22 | Audiocodes, Inc. | Apparatus and method creating virtual routing domains in an internet protocol network |
US8270413B2 (en) * | 2005-11-28 | 2012-09-18 | Cisco Technology, Inc. | Method and apparatus for self-learning of VPNS from combination of unidirectional tunnels in MPLS/VPN networks |
US8180735B2 (en) * | 2006-12-29 | 2012-05-15 | Prodea Systems, Inc. | Managed file backup and restore at remote storage locations through multi-services gateway at user premises |
US20080240098A1 (en) * | 2007-03-26 | 2008-10-02 | James Uttaro | Method and apparatus for providing flexible virtual forwarding table |
US8422502B1 (en) * | 2008-08-13 | 2013-04-16 | Packet Design, Inc. | System and method for identifying VPN traffic paths and linking VPN traffic and paths to VPN customers of a provider |
WO2014082656A1 (en) * | 2012-11-27 | 2014-06-05 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and routers for connectivity setup between provider edge routers |
JP5965335B2 (ja) * | 2013-02-19 | 2016-08-03 | 日本電信電話株式会社 | 通信システム、及び経路制御方法 |
CN103746923B (zh) * | 2013-12-19 | 2017-02-15 | 杭州华三通信技术有限公司 | 一种组播树管理、调度方法及装置 |
EP2892183B1 (en) * | 2014-01-07 | 2017-08-23 | Alcatel Lucent | Enablement of service level agreement negotiation |
CN104869042B (zh) * | 2014-02-20 | 2018-07-13 | 华为技术有限公司 | 报文转发方法和装置 |
US10110710B2 (en) * | 2014-04-03 | 2018-10-23 | Centurylink Intellectual Property Llc | System and method for implementing extension of customer LAN at provider network service point |
US9871695B2 (en) * | 2014-05-22 | 2018-01-16 | Coriant Oy | Network element and a controller for managing the network element |
US9634936B2 (en) * | 2014-06-30 | 2017-04-25 | Juniper Networks, Inc. | Service chaining across multiple networks |
CN104518940B (zh) * | 2014-10-27 | 2017-12-29 | 华为技术有限公司 | 实现nvo3网络与mpls网络之间通信的方法和装置 |
WO2017014164A1 (ja) * | 2015-07-17 | 2017-01-26 | 日本電気株式会社 | 通信システム、通信装置、通信方法、端末、プログラム |
WO2017014163A1 (ja) * | 2015-07-17 | 2017-01-26 | 日本電気株式会社 | 通信システム、通信装置、通信方法、端末、プログラム |
WO2017022791A1 (ja) * | 2015-08-04 | 2017-02-09 | 日本電気株式会社 | 通信システム、通信装置、通信方法、端末、プログラム |
US10158565B2 (en) * | 2016-08-26 | 2018-12-18 | Cisco Technology, Inc. | Network services across non-contiguous subnets of a label switched network separated by a non-label switched network |
US10560431B1 (en) * | 2016-12-05 | 2020-02-11 | Amazon Technologies, Inc. | Virtual private gateway for encrypted communication over dedicated physical link |
-
2016
- 2016-05-10 CN CN201610305131.XA patent/CN107360089B/zh active Active
-
2017
- 2017-05-03 WO PCT/CN2017/082897 patent/WO2017193848A1/zh unknown
- 2017-05-03 US US16/099,489 patent/US20190109781A1/en not_active Abandoned
- 2017-05-03 EP EP17795466.6A patent/EP3457640B1/en active Active
- 2017-05-03 JP JP2018559209A patent/JP2019519146A/ja active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140211615A1 (en) * | 2012-12-18 | 2014-07-31 | Juniper Networks, Inc. | Aggregation network with centralized control |
CN103607349A (zh) * | 2013-11-14 | 2014-02-26 | 华为技术有限公司 | 虚拟网络中确定路由的方法及运营商边缘设备 |
CN105357099A (zh) * | 2015-12-18 | 2016-02-24 | 南京优速网络科技有限公司 | 一种基于sdn的虚拟专用网络的实现方法 |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108965090A (zh) * | 2018-07-12 | 2018-12-07 | 中国联合网络通信集团有限公司 | 一种vpn网络用户路由数的控制方法及sdn控制器 |
CN108965090B (zh) * | 2018-07-12 | 2020-12-22 | 中国联合网络通信集团有限公司 | 一种vpn网络用户路由数的控制方法及sdn控制器 |
CN109257296A (zh) * | 2018-10-30 | 2019-01-22 | 中国联合网络通信集团有限公司 | 路由发布数限制方法及装置 |
TWI715107B (zh) * | 2018-12-25 | 2021-01-01 | 大陸商中國銀聯股份有限公司 | 基於sdn的vpn流量調度方法以及基於sdn的vpn流量調度系統 |
US11296997B2 (en) | 2018-12-25 | 2022-04-05 | China Unionpay Co., Ltd. | SDN-based VPN traffic scheduling method and SDN-based VPN traffic scheduling system |
Also Published As
Publication number | Publication date |
---|---|
EP3457640A4 (en) | 2019-03-20 |
CN107360089A (zh) | 2017-11-17 |
JP2019519146A (ja) | 2019-07-04 |
CN107360089B (zh) | 2021-03-19 |
EP3457640A1 (en) | 2019-03-20 |
EP3457640B1 (en) | 2022-06-22 |
US20190109781A1 (en) | 2019-04-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10361884B2 (en) | Virtual private network forwarding and nexthop to transport mapping scheme | |
US10484203B2 (en) | Method for implementing communication between NVO3 network and MPLS network, and apparatus | |
US10476796B2 (en) | Packet processing method, and device and system | |
CN108075956B (zh) | 一种数据处理方法和装置 | |
WO2017193848A1 (zh) | 路由建立、报文发送 | |
US10778564B2 (en) | Proxy of routing protocols to redundant controllers | |
WO2017162095A1 (zh) | 基于流规则协议的通信方法、设备和系统 | |
KR102054338B1 (ko) | 개별 관리들을 이용하는 vlan 태깅된 패킷들의 가상 포워딩 인스턴스들의 원단 주소들로의 라우팅 | |
CN110912796B (zh) | 一种通信方法、设备和系统 | |
EP3148131B1 (en) | Address information publishing method and apparatus | |
EP3054634B1 (en) | Scheme for performing one-pass tunnel forwarding function on two-layer network structure | |
US11296973B2 (en) | Path information transmission device, path information transmission method and path information transmission program | |
WO2016023499A1 (zh) | 一种处理修改后的报文方法和装置 | |
CN105453513B (zh) | 报文转发方法、转发表项下发方法及网络设备 | |
EP2901630A2 (en) | Method operating in a fixed access network and ues | |
US20210281507A1 (en) | Parameter notification and obtaining methods and devices, and storage medium | |
WO2017177794A1 (zh) | 业务路径的建立方法、装置及系统 | |
CN113726653B (zh) | 报文处理方法及装置 | |
CN106230730B (zh) | 一种组播传输方法和装置 | |
CN106034075B (zh) | 一种为vpn路由分配标签的方法及装置 | |
US10715431B2 (en) | Methods and apparatuses for routing data packets in a network topology | |
WO2015184876A1 (zh) | Vpn路由标签的分配方法、asbr、pe及分配系统 | |
JP2012175198A (ja) | 流通経路設定システム及び方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2018559209 Country of ref document: JP Kind code of ref document: A |
|
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: 17795466 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017795466 Country of ref document: EP Effective date: 20181210 |