WO2017004693A1 - Système, appareil, et procédé pour la fourniture d'un réseau virtuel edge ou overlay - Google Patents

Système, appareil, et procédé pour la fourniture d'un réseau virtuel edge ou overlay Download PDF

Info

Publication number
WO2017004693A1
WO2017004693A1 PCT/CA2016/000185 CA2016000185W WO2017004693A1 WO 2017004693 A1 WO2017004693 A1 WO 2017004693A1 CA 2016000185 W CA2016000185 W CA 2016000185W WO 2017004693 A1 WO2017004693 A1 WO 2017004693A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
connection
aggregated
client site
bonded
Prior art date
Application number
PCT/CA2016/000185
Other languages
English (en)
Inventor
Patricio Humberto Saavedra
Original Assignee
Teloip Inc.
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
Priority claimed from US14/791,311 external-priority patent/US9692713B2/en
Application filed by Teloip Inc. filed Critical Teloip Inc.
Priority to US15/738,056 priority Critical patent/US10523593B2/en
Priority to CA2990045A priority patent/CA2990045C/fr
Publication of WO2017004693A1 publication Critical patent/WO2017004693A1/fr

Links

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
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2863—Arrangements for combining access network resources elements, e.g. channel bonding
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • Embodiments described herein relate generally to network communications and, in particular, to aggregating or bonding communications links for a variety of different networks including wired and wireless networks, and including Wide Area Networks ("WAN").
  • WAN Wide Area Networks
  • bonded/aggregated links provide significant network performance improvement over the connections available to carry network traffic for example from Location A to an access point to the backbone of a network (whether an Internet access point, or access point to another data network such as a private data network, an MPLS network, or high performance wireless network) ("network backbone”), the bonded/aggregated links are generally slower than the network backbone.
  • embodiments described herein may provide a network system for improving network communication performance between at least a first client site and a second client site, wherein the first client site and the second client site are at a distance from one another that is such that would usually require long haul network communication.
  • the system may include at least one client site network component implemented at least at the first client site, the client site network component bonding or aggregating one or more diverse network connections so as to configure a bonded/aggregated connection that has increased throughput.
  • the system may include at least one network server component configured to connect to the client site network component using the bonded/aggregated connection, the network server component including at least one concentrator element implemented at a network access point to at least one network, the network server component automatically terminating the bonded/aggregated connection and passing data traffic to the network access point to the at least one network.
  • the system may include a virtual edge connection providing at least one of transparent lower-link encryption and lower-link encapsulation using a common access protocol for the bonded/aggregated connection between the client site network component and the network server component.
  • the system may include a cloud network controller configured to manage the data traffic so as to provide a managed network overlay that incorporates the virtual edge connection and at least one long haul network path carried over the at least one network.
  • the network server component may include a first concentrator element implemented at the network access point to the at least one network and a second concentrator element implemented at another network access point to at least one other network.
  • the first concentrator element and the second concentrator element may be configured to interoperate to provide a virtual core connection between the network access point and the other network access point, the virtual core connection providing another bonded/aggregated connection.
  • the cloud network controller may be configured to manage the data traffic so as to provide the managed network overlay that incorporates the virtual edge connection, the virtual core connection and the at least one long haul network path carried over the at least one network and the at least one other network.
  • the virtual core connection may provide at least one of the transparent lower-link encryption and the lower-link encapsulation using the common access protocol for the other bonded/aggregated connection.
  • the network server component may have at least one other concentrator element, the at least one other concentrator element bonding or aggregating one or more other diverse network connections so as to configure another bonded/aggregated connection that has increased throughput, the other bonded/aggregated connection connecting the at least one concentrator element and the at least one other concentrator element.
  • the cloud network controller may be configured to manage the data traffic so as to provide the managed network overlay that incorporates the bonded/aggregated connection and the other bonded/aggregated connection.
  • the client site network component may be configured to separate lower-link data traffic and encapsulate data packets of the lower-link data traffic using the common access protocol for the bonded/aggregated connection.
  • the client site network component may be configured with a route to the at least one network server component to separate the lower- link traffic to prepare the data traffic for the bonded/aggregated connection or the managed network overlay.
  • the route is a static route, a dynamic route or a route from a separate or independent virtual routing forwarding table.
  • the network server component is configured to connect with an intelligent packet distribution engine that manages data packets transmission over the at least one long haul network path by obtaining data traffic parameters and, based on the data traffic parameters and performance criteria, selectively applies one or more techniques to alter the traffic over the at least one long haul network path to conform to the data traffic parameters.
  • the network server component is configured to provide Multi-Directional Pathway Selection (MDPS) for pre-emptive failover using echo packets received from the client site network component.
  • MDPS Multi-Directional Pathway Selection
  • the network server component is configured to provide an intelligent packet distribution engine (IPDE) for packet distribution with differing speed links using weighted packet distribution and for bi-directional (inbound and outbound) QoS.
  • IPDE intelligent packet distribution engine
  • the first client site and the second client site are at a distance from one another such that data traffic transmission between the first client site and the second client site is subject to long haul effects.
  • each of the least one network server components is accessible to a plurality of client site network components, each client site network component being associated with a client site location.
  • the system may have a network aggregation device that: (A) configures a plurality of dissimilar network connections or network connections provided by a plurality of diverse network carriers ("diverse network connections") as one or more aggregated groups, at least one aggregated group creating the
  • bonded/aggregated connection that is a logical connection of the plurality of diverse
  • the network aggregation engine includes or is linked to a network aggregation policy database that includes one or more network aggregation policies for configuring the aggregated groups within accepted tolerances so as to configure and maintain the aggregated network connection so that the logical connection has a total communication traffic throughput that is a sum of available
  • embodiments described herein may provide a client site network component implemented at least at least a first client site in network communication with a second client site, wherein the first client site and the second client site are at a distance from one another that is such that would usually require long haul network communication, the client site network component bonding or aggregating one or more diverse network connections so as to configure a bonded/aggregated connection that has increased throughput, the client site network component configured to connect to at least one network server component implemented at an access point to at least one wide area network, the network server component automatically terminating the bonded/aggregated connection and passing the data traffic to an access point to at least one wide area network, the client site network component configuring a virtual edge providing at least one of transparent lower-link encryption and lower- link encapsulation using a common access protocol for the bonded/aggregated connection.
  • the client site network component may be configured to separate lower-link data traffic and use the common access lower-link protocol for encapsulation of data packets of the lower-link data traffic for the bonded/aggregated connection.
  • the client site network component may configure a route to the at least one network server component to separate the lower-link traffic to prepare the data traffic for the bonded/aggregated connection or the managed network overlay.
  • the route may be a static route, a dynamic route or a route from a separate or independent virtual routing forwarding table.
  • the client site network component may be configured to transmit echo packets to the network server component to provide Multi- Directional Pathway Selection for pre-emptive failover using the echo packets.
  • the client site network component may be further configured to provide IPDE for packet distribution with differing speed links using weighted packet distribution and for bi-directional (inbound and outbound) QoS.
  • a network server component configured to interoperate with a client site network component at a first client site to bond or aggregate one or more diverse network connections so as to configure a bonded/aggregated connection that has increased throughput
  • the network server component including at least one concentrator element implemented at a network access point to at least one network, the network server component automatically terminating the bonded/aggregated connection and passing data traffic to the network access point to the at least one network for data transmission to a second client site, the first client site and the second client site at a distance from one another that is such that would usually require long haul network communication, the network server component configuring a virtual edge connection providing at least one of transparent lower-link encryption and lower-link encapsulation using a common access protocol for the
  • the network server component in communication with a cloud network controller configured to manage the data traffic so as to provide a managed network overlay that incorporates the virtual edge connection and at least one long haul network path carried over the at least one network.
  • the network server component may have a first concentrator element implemented at the network access point to the at least one network and a second concentrator element implemented at another network access point to at least one other network.
  • the first concentrator element and the second concentrator element are configured to interoperate to provide a virtual core connection between the network access point and the other network access point, the virtual core connection providing another
  • the cloud network controller is configured to manage the data traffic so as to provide the managed network overlay that incorporates the virtual edge connection, the virtual core connection and the at least one long haul network path carried over the at least one network and the at least one other network.
  • the network server component may be configured to use the common access lower-link protocol for encapsulation of data packets of the lower-link data traffic for the bonded/aggregated connection.
  • the network server component may be configured to receive echo packets from the client site network component to provide Multi- Directional Pathway Selection (MDPS) for pre-emptive failover using the echo packets.
  • MDPS Multi- Directional Pathway Selection
  • the network server component may be configured to provide IPDE for packet distribution with differing speed links using weighted packet distribution and for bi-directional (inbound and outbound) QoS.
  • FIG. 1a illustrates a prior art network configuration that includes a bonded/aggregated network connection.
  • FIG. 1a illustrates an example problem of long haul aggregation/bonding.
  • FIG. 1b also illustrates a prior art network configuration that includes central management of bonded/aggregated network connections, which also shows the problem of long-haul aggregation/ bonding with multiple customer sites.
  • FIG. 1c illustrates a prior art MPLS network configuration with IPSEC embedded.
  • FIG. 2a shows a network solution in accordance with an embodiment of the present invention, with bonding/aggregation implemented at both Site A and Site B, while minimizing long haul effects based on the technology of the present invention.
  • FIG. 2b shows another network solution in accordance with an embodiment of the present invention, in which bonded/aggregated network service exists at Site A but not at Site B.
  • FIG. 2c shows a still other network solution in accordance with an embodiment of the present invention, in which bonding/aggregation is implemented as between Site A, Site B, and Site C.
  • FIG. 2d shows a further implementation of the network architecture of an embodiment of the present invention, in which a plurality of servers/concentrators are implemented as part of a Point-of-Presence.
  • FIG. 2e shows a network solution with bonding/aggregation implemented at both
  • FIG. 2f shows a network solution with bonding/aggregation implemented at Site A, Site B, Site C, Site D, HQ A, HQ C and Site E to connect to a first MPLS network from a first provider connecting and a second MPLS network from a second provider.
  • FIG. 3 is a block diagram of a communication device incorporating a particular embodiment of the invention, demonstrating the device as an aggregation means on the client/CPE-CE side of a network connection.
  • FIG. 4 is a block diagram of a communication device incorporating a particular embodiment of the invention, demonstrating the device as an aggregation means on the server/concentrator side of a network connection and an MPLS data store.
  • FIG. 5 is a block diagram of a communication network incorporating a particular embodiment of the invention, demonstrating the device as an aggregation means on both the client/CPE-CE side and server/concentrator or CCPE side of a network connection.
  • FIG. 6 is a flow diagram of a method of providing redundancy and increased throughput through a plurality of network connections in an aggregated network connection.
  • FIG. 7a illustrates a prior art network architecture where long haul effects apply, and presents network performance based on download speed.
  • FIG. 7b illustrates, in similar network conditions as in FIG. 7a but implementing the present invention in order to reduce long haul bonding/aggregation, improved network performance based on faster download speed.
  • Fig. 8a illustrates a network solution with aggregated/ bonded connections with a virtual edge in accordance with one embodiment.
  • Fig. 8b illustrates another network solution with aggregated/ bonded connections with a virtual edge in accordance with another embodiment.
  • Fig. 9a illustrates a network solution with aggregated/ bonded connections with a virtual edge and two virtual core connections in accordance with one embodiment.
  • Fig. 9b illustrates a network solution with aggregated/ bonded connections with a virtual edge and one virtual core connection in accordance with one embodiment.
  • Fig. 9c illustrates another network solution with aggregated/ bonded connections with a virtual edge and a virtual core connection in accordance with another embodiment.
  • Fig. 10 illustrates a Virtual Network with aggregated/ bonded connections with Virtual Network Overlay and private backhaul options in accordance with one embodiment.
  • Fig. 11 illustrates an example of the Virtual Network Overlay framework is illustrated in accordance with one embodiment.
  • Fig. 12 illustrates another Virtual Network Overlay with aggregated/ bonded connections and private backhaul options in accordance with one embodiment.
  • Fig. 13a illustrates a network solution where IPSEC encryption is used for Lower-
  • Fig. 13b illustrates another network solution where IPSEC encryption is used for
  • Fig. 14 illustrates a network solution in a star topology in accordance with one embodiment.
  • Fig. 15 illustrates a network solution in a full mesh topology in accordance with one embodiment.
  • Fig. 16 illustrates a network solution with third party routers in accordance with one embodiment.
  • Fig. 17 illustrates a transparent encrypted transport of virtual core connections between PoPs for each customer and multiple CPE devices connecting on either side of the virtual core connections in accordance with one embodiment.
  • Fig. 18 illustrates BIRD and OSPF (or RIP) with multi-Fib support and filters for each FIB in accordance with one embodiment.
  • Fig. 19a illustrates exemplary relationship diagrams for cloud manager 140 and
  • Fig. 19b illustrates additional relationship diagrams for cloud manager 140
  • Fig. 20 illustrates a CPE node using a corporate Active Directory security, or Customer RADIUS database for assigning users in accordance with one embodiment.
  • Fig. 21a illustrates an exemplary block diagram for implementation of VLAN as
  • Fig. 21b illustrates an exemplary block diagram for driver customization.
  • Embodiments may provide network infrastructure with utilization of diverse carriers and diverse connections via high-quality link aggregation in combination with a secured and trusted virtual network overlay.
  • the virtual network overlay may provide a managed and encrypted connection of virtual links to provide a virtual WAN, for example.
  • Wide Area Networks WAN
  • a Wide Area Network is a network that covers a wide or broad geographic area that may span cities, regions, countries, or the world.
  • the Internet may be viewed as a WAN, for example.
  • a WAN may be used to transmit data over long distances and connect different networks, including Personal Area Networks ("PAN”), Local Area Networks ("LAN”), or other local or regional network.
  • PAN Personal Area Networks
  • LAN Local Area Networks
  • a WAN may connect physically disparate networks and different types of networks that may be local or remote.
  • An Enterprise WAN may refer to a private WAN built for a specific enterprise often using leased or private lines or circuit-switching or packet-switching methods.
  • Multi-Protocol Label Switch (MPLS) is a technology framework developed by the MPLS
  • MPLS can be a WAN virtualization using virtual routing and forwarding.
  • the technology may be used to build carrier and enterprise networks, implemented with routers and switches.
  • MPLS is protocol independent and can map IP addresses to MPLS labels.
  • MPLS improves network performance by forwarding packets (e.g. IP packets) from one network node to the next based on short path labels, avoiding complex lookups in a routing table.
  • MPLS utilizes the concept of labels to direct data traffic, as a label associated with a packet generally contains the information required to direct the packet within an MPLS network.
  • a packet can enter an MPLS network through an MPLS ingress router or a provider edge / point-of-entry (PE) router, which encapsulates the packet with the appropriate labels.
  • PE point-of-entry
  • various nodes in the network forward the packet based on the content of the labels.
  • LSR label switch router
  • an MPLS egress router or a provider edge (PE) router removes the label(s) from the packet and sends it on its way to the final destination.
  • PE routers typically sit on the edge of an MPLS network and act as an interface between the customer-side network and the MPLS core network.
  • PE routers can add or remove label(s) to incoming and exiting packets or data traffic.
  • a single PE router may be connected to one or more customer networks.
  • label switch routers Within the MPLS core network, label switch routers (LSRs) receive incoming packets and route or forward the packets in accordance with their respective label information. LSRs can also swap or add label(s) to each packet.
  • LSRs label switch routers
  • a customer who wishes to connect to an MPLS network may employ the use of customer edge (CE) routers or their equivalent network elements, which can be located on the customer premises.
  • CE routers can connect to one or more PE routers, which in turn connects to the MPLS core network.
  • MPLS can deliver a range of benefits to customers, including: convergence of voice and data networking, high performance for mission-critical and cloud applications, easy- to-manage or fully managed environments reducing operating cost, SLA based assurances, and so on.
  • MPLS can be delivered with a variety of access technologies such as Iayer2, Iayer3, on the edge over the internet via IPSEC, and so on.
  • MPLS itself is trending as a core networking technology with options to establish access edge points.
  • Routers may be any device including, without limitation, a router, switch, server, computer or any network equipment that provides routing or package forwarding capacity. Routers may or may not have routing tables. Routers may be implemented in hardware, software, or a combination of both. Routers may also be implemented as a cloud service and remotely configurable. IPVPN/ IPSEC
  • IPSEC Internet Protocol Security
  • the MPLS network is considered secured and trusted.
  • IPSEC gateways can be any network equipment such as computers, servers, routers, or special IPSEC devices.
  • IPSEC VPN is typically provisioned using a CE router connected to a broadband internet circuit.
  • IPSEC may be implemented at the PE routers or device.
  • AN MPLS network with IPSEC features is also sometimes also referred to as an IPSEC VPN or IPVPN network.
  • IPSEC VPN can access MPLS networks on the edge, which may be a low cost approach for branch connectivity.
  • IPSEC VPN for MPLS Edge has not been innovated.
  • SLA Service Level Agreement
  • MTTR Mean Time to Repair
  • IPVPN is typically purchased for cost and reach.
  • IPVPN has numerous drawbacks such as the lack of traffic prioritization and CoS capabilities.
  • IPVPN can also be hindered by poor provider service-level agreement (SLA) and mean time to repair (MTTR) on a given service or provider.
  • SLA provider service-level agreement
  • MTTR mean time to repair
  • drivers for corporations to choose a network architecture solution may include:
  • Reasons for deploying a network architecture solution may include:
  • Criteria for selecting WAN network architecture solution and services may include
  • CAPEX/equipment costs including ability to leverage existing CPE
  • Examples are described herein in relation to MPLS as an illustrative example transport mechanism where data packets are assigned labels. This is an example only and other transport mechanisms may be used with different labeling or encapsulation techniques.
  • the embodiments of the systems and methods described herein may be implemented in hardware or software, or a combination of both. These embodiments may be implemented in computer programs executing on programmable computers, each computer including at least one processor, a data storage system (including volatile memory or nonvolatile memory or other data storage elements or a combination thereof), and at least one communication interface.
  • the various programmable computers may be a server, network appliance, set-top box, embedded device, computer expansion module, personal computer, laptop, personal data assistant, cellular telephone, smartphone device, UMPC tablets and wireless hypermedia device or any other computing device capable of being configured to carry out the methods described herein.
  • Program code is applied to input data to perform the functions described herein and to generate output information.
  • the communication interface may be a network communication interface.
  • the communication interface may be a software communication interface, such as those for inter-process communication (IPC).
  • IPC inter-process communication
  • Each program may be implemented in a high level procedural or object oriented programming or scripting language, or both, to communicate with a computer system. However, alternatively the programs may be implemented in assembly or machine language, if desired. The language may be a compiled or interpreted language. Each such computer program may be stored on a storage media or a device (e.g., ROM, magnetic disk, optical disc), readable by a general or special purpose programmable computer, for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein.
  • Embodiments of the system may also be considered to be implemented as a non-transitory computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner to perform the functions described herein.
  • the systems and methods of the described embodiments are capable of being distributed in a computer program product including a physical, non-transitory computer readable medium that bears computer usable instructions for one or more processors.
  • the medium may be provided in various forms, including one or more diskettes, compact disks, tapes, chips, magnetic and electronic storage media, volatile memory, non-volatile memory and the like.
  • Non-transitory computer-readable media may include all computer-readable media, with the exception being a transitory, propagating signal.
  • the term non-transitory is not intended to exclude computer readable media such as primary memory, volatile memory, RAM and so on, where the data stored thereon may only be temporarily stored.
  • the computer useable instructions may also be in various forms, including compiled and non-compiled code.
  • Coupled to is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms “coupled to” and “coupled with” are used synonymously.
  • MPLS Edge is an improved alternative to IPSEC VPN on the MPLS network.
  • Autonomous Network Aggregation (ANA) or a network bonding/aggregation technology can be used as part of a hybrid solution to extend an MPLS network, allowing partners to use lower- cost broadband connectivity while maintaining the quality and reliability of an MPLS service.
  • MPLS Edge virtualizes MPLS over network bonding/aggregation on the edge of carrier infrastructures, delivering MPLS labels to the customer premises equipment or device coupled with network bonding/aggregation.
  • cloud concentrators in ANA or a link aggregation system may act as an MPLS PE (Provider Edge) router on the edge of the network.
  • MPLS PE Provide Edge
  • MPLS Edge technology can extend an MPLS network to the customer's LAN as a private service offering that can deliver consolidated WAN, VoIP, and Internet access.
  • a system and network architecture for aggregating multiple network access connections from similar or diverse carriers to create a new aggregated connection that accommodates greater speed and high availability characteristics, and that connects to an MPLS network via customer premises equipment (CPE-CE) or cloud concentrator/ provider equipment (CCPE).
  • CPE-CE customer premises equipment
  • CCPE cloud concentrator/ provider equipment
  • a network solution for improving network communication performance between at least two sites, where the two sites are at a distance from one another that is such that would usually require long haul network communication.
  • the network solutions includes at least one network bonding/aggregation system that includes (A) at least one first network component that is implemented at a first service site, the first network component being configured to bond or aggregate one or more diverse network connections so as to configure a bonded/aggregated connection that has increased throughput; and (B) a second network component, configured to interoperate with the first network component, the second network component including a server/concentrator (also referred to as network server component) that is implemented at an access or point-of-entry point to a multiple protocol label switching network.
  • a server/concentrator also referred to as network server component
  • Multiprotocol label switching is a network mechanism that directs data between network using path labels rather than network addresses, avoiding complex routing table lookups.
  • the labels identify virtual links or paths between nodes rather than endpoints.
  • MPLS can encapsulate packets of various network protocols and supports a range of access technologies.
  • embodiments described herein may provide a virtual edge provide encryption over the bonded/aggregated network connection.
  • the first network component may be implemented using what is called in this disclosure a "CPE-CE" or customer premises equipment (also referred to as customer edge (CE) router or client site network component).
  • the CPE-CE may involve a third party router that may be particularly configured in accordance with embodiments to provide the bonded/aggregated network connection. This configuration may involve separating lower-link data traffic on third party routers by removing default routing information and adding routes on each respective lower-link for the corresponding concentrator lower-link IP address. This configuration may further involve using a common access protocol for encapsulation of lower-link data packets. Further configuration details are described herein.
  • the CPE-CE may be implemented using a virtual edge, as will be described herein.
  • the server/concentrator is implemented at an access or point-of-entry point to an MPLS network or other network, with access to the network backbone provided by an MPLS networking solution so as to provide a high-quality, end-to-end, secured network connection.
  • the server/concentrator may provide a bridge between the bonded/aggregated network and the broadband network portion to deliver MPLS to the CPE.
  • the server/concentrator may be configured to operate as a provider edge or point-of-entry (PE) router on the MPLS network.
  • PE point-of-entry
  • MPLS is protocol independent and supports a bonded/aggregated network supported protocol. This is an example protocol described for illustrative purpose.
  • the server/concentrator may also support lower-link encapsulation to be compatible with CPE-CE routers that are configured to provide separation and encapsulation of lower-link data traffic.
  • the server/concentrator may be implemented as a cloud service, a cluster service or simply a cluster hosted in cloud, or a router server configured based on certain configurations. It may also be referred to as a cluster or a cloud concentrator throughout this application.
  • the clusters or cloud concentrators may serve multiple CPE-CEs.
  • a client site may have multiple CPE-CEs and a cluster can serve multiple client sites.
  • the clusters or cloud concentrators may also communicate with one another on a basis of multiple points-of-presence ("Multi- POP"), as will be described below.
  • Multi- POP multiple points-of-presence
  • the server/concentrator may be remotely or closely coupled with one or more CPE-CEs, and comprise of software, or entirely of hardware, or include both software and hardware components.
  • the server/concentrator may be implemented to one or more server computers, or may be implemented as an interconnected network of computer residing at the same or different physical locations, and connected to one or more CPE-CEs and the core network (e.g. MPLS or other protocol) through one or more trusted network connections.
  • the server/concentrator can interoperate with CPE-CEs and/or the other components in the network architecture in order to deliver the functionalities described herein.
  • Network architectures that involve long-haul bonded/aggregated network communication result in less than optimal performance, thereby minimizing the advantages of the bonding/aggregation technology.
  • the bonding/aggregation technology may improve service to Site A associated with for example a CPE (or equivalent to customer premises equipment), based on bonding/aggregation between the CPE and an associated server/concentrator (or equivalent such as a cloud concentrator), overall performance may be less than desired and in fact may be less than what would be available without bonding/aggregation because of the long haul effects of carrying the bonded/aggregated from Site A, to at least Site B. These long haul effects will present wherever Site A and at least Site B are at a substantial distance from one another.
  • the CCPE may be implemented with virtualization software such as vmWare, vSphere5, Citrix Xen, and so on.
  • FIG. 1a illustrates the problem of long haul aggregation/bonding generally.
  • packets are carried over the Internet through an extension of the bonded/aggregated connection across the Internet (102), rather than a high performing Internet core network such as an MPLS core network.
  • the bonded/aggregated connection across a distance that is subject to long haul effects, will not perform as well as the Internet, thereby providing less than ideal performance.
  • FIG. 1 b Another problem with some bonding/aggregation solutions is that they generally require control or management by a central server. Depending on the location of the central server, this can result in multiplying the long haul effects because traffic between Site A and Site B may need to also be transferred to a Site C that is associated with the central server.
  • Central server (104) manages network communications, and routes network communications between Site A and Site C. To the extent that the distance between central servers (104) is substantial from either of Site A or Site C, long haul effects will present.
  • Embodiments of the present invention provide a network solution, including a network system and architecture and associated networking method that addresses the aforesaid long haul effects that have a negative effect on performance.
  • Fig. 1c illustrates a prior art MPLS network configuration with IPSEC embedded therein.
  • packets are carried over the Internet through a single connection such as DSL or cable, from Branch Customers A or B (e.g. Sites A or B) to one PE router of MPLS.
  • An IPSEC tunnel may be implemented between the Branch Customers A or B to the MPLS PE router, and terminated immediately before or at the PE router.
  • the PE router therefore fulfills two tasks: IPSEC remote access termination and providing an MPLS PE router.
  • IPSEC in this prior art configuration serves mainly as a secure access method into the MPLS network.
  • the protection of IPSEC secures the data on transport over any untrusted infrastructure, such as public WIFI hot spots or DSL Internet.
  • the network path from Branch Customer A or B to IPSEC Termination may be over a sole connection that can be, for example, a cable or a DSL connection. If the cable connection from Branch Customer A fails for any reason, then that customer would not be able to connect to the MPLS network as there is no alternative Internet connection available.
  • embodiments of the present invention provide significant improvements in regards to a number of additional features such as bi-directional communication, failover protection and diversity of carriers.
  • IPSEC tunnel may also be implemented from one PE router to another PE router over the MPLS network core or from Branch Customer A to HQ Customer B (CPE-CE to CPE-CE).
  • CPE-CE Branch Customer A to HQ Customer B
  • MPLS networks with embedded IPSEC are very costly to set up, difficult to maintain and reconfigure, and generally leave much to be desired in terms of carrier diversity, failover protection, aggregated bandwidth, bi-directional communication, quality of service (QoS), prevention of dropped calls, application acceleration, and scoring of quality of experience (QoE), to name a few.
  • QoS quality of service
  • QoE quality of service
  • the server/concentrator (or otherwise known as cloud concentrator) side of a bonding/aggregation network solution for Site A (120a) is implemented such that (A) the location of the cloud concentrator (110a) is implemented with access to the network core of MPLS (112), and (B) the cloud concentrator (110a) includes functionality for (i) receiving packets by means of the bonded/aggregated connection (116a), (ii) interrupting the bonded/aggregated connection (116a) using an interrupter (118), and (iii) directing the packets (114) to the MPLS (112) for delivery to a Site B (120b).
  • the cloud concentrator (110a) is also acting as the PE router of MPLS (112).
  • the cloud concentrator (or the server/concentrator) (110a) thus is also known as the cloud concentrator provider edge or the cloud concentrator point-of-entry (CCPE) of the MPLS.
  • CCPE cloud concentrator point-of-entry
  • the CCPE (110b) can then establish a further bonded/aggregated connection (116b) and directs the packets (114) via the bonded/aggregated connection (116b) to a CPE-CE (B) (124b) at Site B.
  • the MPLS network 112 may also be Wide Area Network WAN 112.
  • FIG. 2b illustrates a configuration where bonded/aggregated network service exists at Site A but not at Site B.
  • FIG. 2c illustrates one possible implementation, where the network system is based on a distributed network architecture where CCPEs (110a) (110b) (110c) and corresponding CPE-CEs (124a) (124b) (124c) are configured to provide improved network communications, including interruption of network communications at the network backbone so as to reduce long haul effects, dynamically and on a peer to peer basis without the need for a persistent central manager.
  • each of the network components of the network system included functionality to operate on a peer-to-peer basis.
  • a CPE-CE (124) initiates network communications on a bonded/aggregated basis, cooperating with a CCPE (110), with packets destined for a remote location.
  • Each CCPE (110) receives dynamic updates including a location and identifier associated with other CCPE (110). Packets are dynamically sent to a CCPE (110) at the remote location, if available, and from the CCPE (110) at the remote location to its CPE-CE (124).
  • the CPE-CEs (124) and their CCPEs ( 10) use bi-directional control of network communications to establish a network overlay to provide improved network performance.
  • the network overlay for example provides desirable quality of service despite underlying network conditions that may otherwise result in a decrease in network performance.
  • the network system establishes and manages two or more network overlays.
  • a first network overlay (126) is established between the CPE-CE(A) (124a) and CCPE (110a); then, communications are transferred over the MPLS (112) without a network overlay; then, a second network overlay (129) is established between CCPE (110b) and CPE-CE(B) (124b).
  • IP transport is provided between Site A and Site B where this will provide better performance than the aggregated/bonded network connections. Bonding/aggregation in effect is distributed across the locations, rather than attempting to span the distance between the locations with end to end bonding/aggregation.
  • Embodiments therefore provide distributed bonding/aggregation.
  • Embodiments also provide a network system that automatically provides distributed bonding/aggregation in a way that bonding/aggregation is proximal, and beyond proximal connections IP transport is used, with proximal bonded/aggregated connections and fast Internet being used as part of end- to-end improved service.
  • system elements enabling the monitoring and maintenance of Quality of Experience (QoE) and Quality of Services (QoS) may be optionally included in the CCPE and/or CPE-CE configuration.
  • QoE Quality of Experience
  • QoS Quality of Services
  • an intelligent packet distribution engine may be supported to implement QoE and QoS functionality.
  • the QoE and QoS elements may be implemented as part of the underlying link aggregation technology.
  • Embodiments may offer advantages over the prior art technologies, including, for example:
  • Carrier diversity including network aggregation and failover protection
  • QoS Quality of service
  • the cloud concentrator would bridge the MPLS portion of a customer's network to the broadband portion using network aggregation delivering MPLS to the CPE device (MPLS added to link aggregation technology as a supported Protocol).
  • one or more CCPEs can be implemented at a given physical location, as part of a Point-of Presence (PoP) (130).
  • a PoP 130
  • a PoP 130
  • a plurality of PoPs 130
  • a plurality of PoPs (130) may be established based on network topology or service requirements in a given area.
  • each PoP (130) may have one or more network backbone connections (132), because in some locations different network backbones, such as a wireless Internet, a private data network, or the MPLS network, may be available.
  • the PoP (130) may be implemented so that it dynamically interoperates with surrounding networks.
  • the PoP (130) is a collection of network components, established at the periphery of the network backbone (112), associated with a plurality of networks, and cumulatively providing network communication service to one or more clients in a defined geographic area.
  • the server/concentrators or CCPEs (110) located within the PoP (130) functions as a network access server for connecting to the Internet or the MPLS (112).
  • the network access server ( 0) acts as the access point to the Internet ( 2) for a plurality of CPE devices (124) that are connected to the PoP (130).
  • the servers/concentrators or CCPEs (110) may be configured to communicate with one another to share information regarding network conditions.
  • Servers/concentrators and CCPEs (110) provide connectivity to CPEs and CPE-CEs (124) and may also run a networking protocol such as BGP to route servers and other network backbone connections (112).
  • servers/concentrators and CCPEs (110) are configured to detect changes in their network environment.
  • the CPE-CE (124) may be configured to collect information from network components in its vicinity including from one or more available PoPs (130) and their CCPEs (110).
  • the CPE-CE (124) for example connects to a closest available CCPE (124), implemented as part of a PoP (130), and thereby having access to a connection to the MPLS network core (112). Whether the connection to the network core ( 12) is direct or indirect, the network connections are established so as to minimize long haul effects.
  • each CPE-CE (124) establishes a connection by dynamically advertising its IP address, and receiving replies from associated CCPE (110) along with their current network performance information.
  • the CPE-CE (124) initiates a bonded/aggregated connection with a CCPE (110) that is proximal (to minimize long haul effects between the CPE-CE (124) to the MPLS network core (1 2)), and also performing well based on network conditions relevant to the particular CCPE.
  • a network device is deployed that bonds or aggregates multiple, diverse links.
  • the network device may be WAN aggregator or a link aggregator.
  • QoS quality of services
  • One or more CPE-CEs and one or more CCPEs can create various different network configurations that may improve network performance in relation to network communications there between.
  • the CPE-CEs and CCPEs are designed to be self-configuring and self-healing, and to interoperate with one another to manage traffic in a more effective way.
  • Proximal means a distance such that based on relevant network conditions; long haul network communication and associated effects are avoided.
  • the distance between the CPE-CE and the CCPE may be proximal.
  • the CCPE (110) can be located at an access point to the MPLS network core (112) or in some other way to minimize the long haul effect, for example, by the CCPE being located proximal to an access point so as to further avoid long haul network communication.
  • the bonded/aggregated connection at Site A and the bonded/aggregated connection at Site B may be different.
  • each may include different types of network connections and that may be associated with different carriers.
  • the network overlay provided operates notwithstanding such diversity.
  • the network backbone (112) could be any high performance network including for example a private WAN, the Internet, or an MPLS network.
  • one or more network overlays are established, thereby in one aspect providing a multi-POP network that exploits multiple points of presence so as to provide a persistent, configurable/reconfigurable network configuration that provides substantial network performance improvements over prior art methods.
  • the CPE-CEs/CCPEs may monitor network performance, including in the areas proximate to their position, and may reconfigure the network overlay dynamically, across multiple locations (including multiple PoPs) based on changes in MPLS network performance while providing continuity of service.
  • the network overlay may be made up of multiple virtual connections, such as virtual edge and virtual core connections, as described herein.
  • the network components of embodiments described herein are intelligent, and iteratively collect network performance information.
  • each CPE-CE is able to direct associated concentrator(s)/CCPE and any CPE-CE to in aggregate re-configure the network overlay.
  • management of the network may be centralized or decentralized, depending on the configuration that provides the best overall performance. This is in contrast to prior art solutions that generally require central management for example of termination of connection which results in traffic being carrier over bonded/aggregated connection that involve long haul transmission that fail to take advantage of network paths that may provide inherently better performance than the bonded/aggregated connection paths.
  • decentralized managed is made possible by peer-to-peer functionality implemented to the network components of the embodiments described herein.
  • a plurality of CCPEs may be established in multiple locations covering a plurality of different access points.
  • Each CCPE may be used for multiple clients associated with different CPE-CEs to improve network performance for such multiple clients by providing termination of their bonded/aggregated connection, routing of communications, and encapsulation of packets to the MPLS network core.
  • the network solution therefore may include multiple Points-of-Presence, distributed geographically including for example in areas requiring network service, and through the network architecture bridging geographically disparate areas with improved network communication.
  • the present invention may be implemented in connection with any technology for bonding or aggregating links, and thereby reduce long haul effects.
  • the present invention may also be implemented with any kind of MPLS network, thereby providing a high-performance, secure, end-to-end network connection between various client or customer sites.
  • the system, method and network architecture may be implemented such that the aggregated/bonded network connections described are implemented using the link aggregation technology described in Patent No. 8,155,158.
  • the system, method and network architecture may be implemented using one or more Points-of-Presences as described in Patent Application No. 13/958,009.
  • Link aggregation/bonding in combination with an MPLS network emphasizing the creation and management of the bonded/aggregated connections between them, and the encapsulation at CCPEs, which in the network configuration of the present invention may form a part of the overall network overlay that incorporates the one or more portions that are carried over the network backbone.
  • Diverse network connections may be aggregated into virtual (logical) connections that provide higher throughput as well as independence of the network characteristics of the constituent (physical) network. Aggregation may be performed at a given CPE-CE.
  • a Metro Ethernet 10Mbps (E10) link and a T1 (DS1) link are aggregated in accordance with embodiments described herein, in order to provide higher fault tolerance and improved access speeds.
  • the aggregation of diverse carriers may extend to any broadband network connection including Digital Subscriber Line (DSL) communications links, Data over Cable Service Interface Specification (DOCSIS), Integrated Services Digital Network, Multi-protocol Label Switching, Asynchronous Transfer Mode (ATM), and Ethernet, etc.
  • the network connections may also include a WAN.
  • an apparatus for managing transfer of communication traffic over diverse network connections aggregated into a single autonomous connection, independent of the various underlying network connections.
  • the apparatus may include a network aggregation device and an aggregation engine.
  • the network aggregation device may be adapted to configure a plurality of network connections, and transfer communication traffic between a further network connection and the plurality of network connections, as an aggregated group for providing a transfer rate on the further communication link, and to allocate to the aggregate group a rate of transfer equal to the total available transfer rate of the underlying networks.
  • the aggregation engine may be adapted to manage the distribution of communication traffic received both to and from a plurality of network connections, establishing newly formed aggregated network connections.
  • the aggregation engine may be implemented in software for execution by a processor, or in hardware.
  • a plurality of diverse network connections may be aggregated to create an aggregated network connection.
  • the diversity of the network connections may be a result of diversity in provider networks due to the usage of different equipment vendors, network architectures/topologies, internal routing protocols, transmission media and even routing policies. These diversities may lead to different network connections with different latencies and/or jitter on the network connection. Also, variation within transmission paths in a single provider network may lead to latency and/or jitter variations within a network connection.
  • Latency and jitter typically affect all data communication across the network connection. Latency is the round-trip time for a transmission occurring end-to-end on a network connection.
  • Jitter is the variance in latency on a network connection for the same data flow.
  • High latency and jitter typically have a direct and significant impact on application performance and bandwidth.
  • Applications such as VOIP, and video delivery are typically highly sensitive to jitter and latency increases and can degrade as they increase.
  • Transparent aggregation of a plurality of network connections in an aggregated network connection requires the management of data transmitted over the aggregated connection by the aggregation engine and received from the aggregation traffic termination engine.
  • transparent aggregation does not require any configuration by a network provider.
  • the aggregation engine and the aggregation traffic termination engine may manage data transmission such that the variable path speeds and latencies on the plurality of network connections do not affect the application data transmitted over the aggregated network connection.
  • the network aggregation engine and the aggregation traffic termination engine may handle sequencing and segmentation of the data transmitted through the aggregated connection to transparently deliver application data through the aggregated connection with minimal possible delay while ensuring the ordered delivery of application data.
  • the network aggregation engine provides a newly aggregated network connection with a capacity equal to the sum of the configured maximum throughput of the network connections.
  • the aggregation engine and an aggregation traffic termination engine (further explained below) handle the segmentation of packets as required in confirmation with architectural specifications such as Maximum Segment Size (MSS) and Maximum Transmission Unit of the underlying network connections.
  • the network aggregation device is operable to handle assignment of sequence identifiers to packets transmitted through the aggregated network connection for the purpose of maintaining the ordering of transmitted data units over the aggregated network connection.
  • the network connection device includes or is linked to a connection termination device, and a plurality of fixed or hot swappable transceivers for transmitting communication traffic on respective sets of network connections, for the purpose of configuring a plurality of network connections as an aggregated connection or the management of multiple aggregated network connections and providing access to the aggregated network connection for any network communications traversing the device.
  • routing protocols or route selection mechanisms described are intended only to provide an example but not to limit the scope of the invention in any manner.
  • FIG. 2e shows an exemplary embodiment of a network solution with bonding/aggregation implemented at both Site A, Headquarter (HQ) A and Site C to connect to an MPLS network connecting to Headquarter (HQ) B, Headquarter (HQ) C, and Site B.
  • a number of customer sites (120a, 120b, 120c, 120d, 120e, and 120f) are connected to each other via a core network 112, which may provide a secured VPN network solution to multiple users.
  • the core network 112 may be an MPLS network.
  • the network backbone is typically provided by one carrier but multiple networks provided by multiple carriers may also be connected via multiple Points-of-Presence (POPs) to form a super network.
  • POPs Points-of-Presence
  • each of Site A 120a and Site C 120c has a CPE-CE (124a and 124c, respectively), which is then connected to a CCPE 110a with some form of link aggregation/ bonding technology as described elsewhere in this disclosure.
  • the CCPE 110a can be also connected to other CCPEs (not shown) within a Point-of-Presence 130a located closest to Site A 120a and Site C 120c.
  • CCPE 110 also acts as a PE router to a core network 112 in that it takes incoming or inbound traffic or packets, examines each packet and then encapsulates the packet with an appropriate label (e.g. MPLS label) based on a variety of factors.
  • an appropriate label e.g. MPLS label
  • MPLS can be layer 2 independent, it can work with any layer 2 protocol including but not limited to ATM, frame relay, Ethernet MAC layer, or PPP.
  • CCPE is operable to inspect/ examine the destination IP address and other information in the packet header, insert a label into the packet and forward the labeled packet to the output port.
  • LSR Label Switch Router
  • the LSR then swaps the old label with the new label and routes the newly labeled packet to the next output port.
  • Other LSRs within the MPLS network will perform the same tasks.
  • the labeled packet will reach another provider edge router.
  • the provider edge router can then examine the label and perform a table look-up at the forwarding table to find that the packet is to be sent to, for example, CCPE 110c connected to HQ C 120e and Site B 120f. It then removes the label and sends an unlabeled packet to CCPE 110c.
  • CCPE 110c will receive the unlabeled packet and examine the IP header information to determine the final destination e.g. HQ C 120e, Site B 120f, or another destination, such as, e.g., HQ A 120b.
  • CCPE can also act as the provider edge router for data packets exiting (e.g. "outbound data packets") the MPLS network core 112.
  • labeled packets traveling through the MPLS network core 112 can be routed to and reach a CCPE on the edge of the MPLS network.
  • the CCPE can then examine the label of the outbound data packet and perform a table look-up at the forwarding table to determine that the packet is to be sent to a CPE-CE ("destination CPE-CE”) connected to the CCPE
  • the CCPE can further remove the label from the outbound data packet and send it to the destination CPE- CE over ANA link aggregation connections.
  • each CCPE may determine that the destination CPE-CE may be associated or connected with another CCPE over a POP 130 or the MPLS network core 112, in which case the CCPE may re-encapsulate the data packet if necessary and send it back to the POP and/or MPLS network for further transmission to its final destination.
  • each CCPE may comprise a Network Aggregation Device 23 including a Network Aggregation Engine 11 and an MPLS Data Store 40.
  • encapsulation of data packets by a CCPE 110 can be done as an on-stack protocol implementation by a network aggregation engine 11 (further described below) based on information supplied by an MPLS data store 40 within or connected to the CCPE 10.
  • a network aggregation engine 11 further described below
  • network data can be transparently sent and received over link aggregation/ bonding network 116 by CCPE and CPE-CE.
  • the CPE-CE can also implement full MPLS network data encapsulation capabilities.
  • CCPE 110c may not be associated with a POP, such as CCPE 110c or 110b.
  • CCPE may change over time, as CCPE dynamically receives and analyzes real-time data regarding various network characteristics.
  • CCPE 110b may receive information indicating that a commonly used network path has failed due to power outage, it then may decide to seek alternative connection to the MPLS core via the closest POP 130d.
  • Cloud provisioning services 140 may also configure/ reconfigure the CCPEs in real time based on a plurality of network characteristics.
  • HQ B 120d HQ C 120e
  • Site B 120f do not have link aggregation/ bonding technologies. That is, an MPLS network as described herein and its associated CCPEs may take both link aggregation/ bonding connections or typical broadband connections without said link aggregation technology. Depending on what connection it is, a CCPE may adjust accordingly and encapsulates the incoming packets with appropriate labels before forwarding the packets to the MPLS network core 112. A CCPE may also de-label data packets before forwarding the packets to the final destination CPE-CEs for outbound data packets exiting the MPLS network core 112.
  • a CCPE may act as a provider edge router and provide, in a simultaneous manner, encapsulation and de-labeling functionalities for inbound and outbound data packets respectively.
  • some form of cloud provisioning (or zero touch provisioning ZTP) 140 may also be provided to dynamically configure and reconfigure some or all of the CCPEs and all the CPE-CEs.
  • Benefits of the exemplary embodiments described in this disclosure include: i) the proprietary link aggregation/ bonding technology described herein can utilize any kind of network connection, private or public, layer 2 or layer 3; and ii) the CPE-CEs and CCPEs can encapsulate the data packets for transparent interconnectivity across diverse carriers, with the lower-links aggregated.
  • the CPE-CEs and CCPEs can encapsulate over any carrier using any local physical loop, some times without the need to participate at layer 1 network.
  • the architecture of embodiments can be understood as a centralized architecture for aggregating network connections, broadband or otherwise. Diverse network connections are aggregated into a virtual (logical) connection that provides higher throughput as well as independence of the network characteristics of the constituent (physical) network. The virtual connection can then be connected to an MPLS network in manners as described herein. Aggregation may be performed to a given CPE-CE terminal.
  • a Metro Ethernet 10 Mbps (E10) link and a T1 (DS1) link can be aggregated in accordance with the invention as described below, in order to provide higher fault tolerance and improved access speeds.
  • the aggregation of diverse carriers in accordance with the present invention extends to any broadband network connection including Digital Subscriber Line (DSL) communications links, Data over Cable Service Interface Specification (DOCSIS), Integrated Services Digital Network, Multi-protocol Label Switching, Asynchronous Transfer Mode (ATM), and Ethernet, etc.
  • DSL Digital Subscriber Line
  • DOCSIS Data over Cable Service Interface Specification
  • ATM Asynchronous Transfer Mode
  • Ethernet etc.
  • the links to be aggregated can be any private or public Internet services such as cable, ADSL, T1 , Fibre, xOE (over Ethernet types), wireless, as well as other MPLS connections so long as the network path reaches a CCPE for lower-link processing from a CPE-CE terminal.
  • private or public Internet services such as cable, ADSL, T1 , Fibre, xOE (over Ethernet types), wireless, as well as other MPLS connections so long as the network path reaches a CCPE for lower-link processing from a CPE-CE terminal.
  • the various network configurations shown in FIGs. 2a to 2f allow the use of low cost Internet links on the client side and where appropriate, between a first MPLS network and a second MPLS network, in order to provide connectivity on the client side and manage connectivity to the one or more MPLS network(s).
  • this network architecture allows one or more MPLS networks to be brought to normal broadband users. Security is provided through the link aggregation/ bonding technologies described elsewhere in this disclosure.
  • the various network configurations can further allow various intelligent network performance features to be deployed.
  • FIG. 2f shows a network solution with bonding/aggregation implemented at Site A, Site B, Site C, Site D, HQ A, HQ C and Site E to connect to a first MPLS network from a first provider connecting and a second MPLS network from a second provider.
  • FIG. 2f shows a plurality of MPLS networks from different MPLS providers to provide a secure, fast network between different end users.
  • a first MPLS network 150a provided by a first MPLS provider is connected to HQ A 120f, HQ D 120g, and Site E 120e.
  • HQ A 120f and Site E 120e each has link aggregation (116f and 116e) facilitated by CCPEs 124f and 124e, respectively.
  • a second MPLS network 150b provided by a second MPLS provider is connected to Site D, HQ B and HQ C.
  • Each of the MPLS networks 150a and 160b can act as part of a POP in the overall network architecture 300. Even though only two MPLS networks are illustrated here, there can be a plurality of MPLS networks not limited to two or any particular total of networks. This way, one can extend an MPLS network to use other MPLS or non-MPLS connections to reach the end customer, whether using static or dynamic IP addressing, and without the participation of carriers.
  • a CCPE 110a can be connected to more than one CPE-CE devices 124a, 124b and 124c, supporting a multi-tenant service for multiple customers. That is, a CCPE 110a can treat each CPE-CE 124a, 124b or 124c connected to the CCPE independently, with link aggregation 116a, 116b and 116c between each CPE-CE and CCPE.
  • a CCPE can facilitate many CPE- CE's to one CCPE implementation, supporting a multi-tenant service for multiple customers on their own MPLS network. This can be serviced by a single CCPE treating each CPE-CE independently on a tenant instance or MPLS network.
  • FIG. 3 is a block diagram of a communication device incorporating a particular embodiment of the invention, demonstrating the device acting as a client or CPE-CE.
  • the network element/network aggregation device 23 includes (in this particular embodiment shown for illustration) a network connection termination module 25 that includes representative transceiver interfaces 14, 15 and 16. Each transceiver interface 14, 15 and 16 represents an interface to a physical communication medium through which communications may be established to network connections.
  • a possible implementation of the network aggregation device may use a single or multiple chassis with slots for multiple network connection termination modules and multiple network aggregation engine modules.
  • the multiple network connection termination modules may be grouped by protocol specific or medium specific transceiver/interfaces.
  • the network aggregation engine 11 may handle the configuration of the network aggregation device and all related interactions with external inputs.
  • An extended device configuration store with MPLS capacity 24 may provide persistent data storage for device configuration information such as a network aggregation policy and MPLS related configuration information and policies.
  • MPLS related configuration information may include label lookup table, forwarding table, routing table, labeling and mapping policies, and/or MPLS provider information.
  • the network aggregation engine 11 may handle queries from external sources, such as configuration parameters a network management protocol such as Simple Network Management Protocol, for example.
  • the interface 10 may be a protocol agent and may provide for communication with a Network Management System (NMS) or operator system for configuration of the aggregation engine by the definition of an aggregation policy.
  • NMS Network Management System
  • Control and management information may be transferred between the network aggregation device 23 and the NMS or operator system through the interface 10 via any available or specifically designated network connection 19, 20, 21 and 17 through any transceiver interface 14, 15 and 16.
  • the described system can transport MPLS packets back and forth between MPLS core network and ANA link aggregation connection(s) so as to enable extending communication of MPLS packets beyond the edge of the MPLS core network, using ANA link aggregation technology.
  • the system can include specific mechanisms for enabling the transport of the MPLS packets (e.g., data packets leaving MPLS core network and entering ANA) using transcoding/translating and then encapsulation for ANA link aggregation connection(s), in a way that maintains the integrity of the MPLS packet, including processing instructions such as those related to QoS.
  • MPLS packets e.g.
  • data packets leaving ANA and entering MPLS core network can be de- encapsulated to remove ANA protocol and where appropriate, transcoding/translation in order to obtain the original data packet without affecting integrity, and in such a way that can enable further, if any, MPLS processing to happen automatically.
  • MPLS-to-ANA Handler 55 can be implemented either as the ANA client, the ANA server and/or the ANA protocol itself.
  • multiple network connections may be combined to form an aggregated network connection 22, as disclosed in further detail herein.
  • Each individual network connection may be configured with a maximum communication traffic rate, which could be expressed as a bit rate in bits per second.
  • the network aggregation engine 11 may be implemented in software for execution by a processor in the network aggregation device 23, or in hardware such as by means of a Field Programmable Gate Array (FPGA) or other integrated circuit, or some combination thereof.
  • the network aggregation engine 11 may be implemented in a distributed manner by distributing aggregation engine intelligence to the network connection termination module 25, in a manner that is known.
  • the network aggregation engine 11 may receive traffic from client network connection device 18 through a network connection 17 provided through a transceiver interface 16.
  • the client network connection device 18 may be any device including, without limitation, a router, switch, or media converter that is capable of providing termination for a single or multiple client nodes, where nodes are any devices capable of connecting to a network irrespective of protocol or interface specificity.
  • traffic may be received over multiple network connections through a single or multiple transceiver interfaces.
  • the network aggregation engine 11 may accept all traffic from the client network connection, may provide encapsulation and segmentation services for the traffic for transmission through the aggregated network connection 22, and may transmit it over any of the network connections 19, 20 and 21 through any of the transceiver interfaces 14, 15 and 16.
  • the network aggregation engine 11 may handle segmentation in a manner that avoids the fragmentation of aggregated communication traffic received through the client network connection device 18, when transmission occurs over the aggregated network connection 22 through any of the network connections 19, 20 and 21 , by ensuring that the length of a packet/frame transmitted over any of the network connections 19, 20 and 21 is less than or equal to the configured or detected frame length for the respective connections in the aggregated network connection 22.
  • the network aggregation engine 11 may be connected to an MPLS to ANA Handler 55.
  • the engine 55 may comprise an MPLS PE/CE implementation module 50, an MPLS/ ANA encapsulation module 52 and an MPLS to IPDE QoS Translation module 53.
  • network aggregation engine 11 may send the packet to the MPLS to ANA Handler 55.
  • the data packet may be encapsulated via MPLS/ ANA Encapsulation 52 based on specific MPLS configuration data in the extended device configuration store 24.
  • the encapsulated data packet can then be sent to MPLS PE/CE implementation module 50, which may further provide segmentation in a manner that avoids the fragmentation of aggregated communication traffic received through the client network connection device 18, when transmission occurs over the aggregated network connection 22 through any of the network connections 19, 20 and 21 , by ensuring that the length of a packet/frame transmitted over any of the network connections 19, 20 and 21 is less than or equal to the configured or detected frame length for the respective connections in the aggregated network connection 22.
  • MPLS to link aggregation (or ANA) transcoding can be performed between the MPLS core and the Customer LAN via the MPLS to ANA Handler 55.
  • the CCPE MPLS protocol implementation can communicate with the MPLS core recognizing packets that are destined for the customer LAN located over the link aggregation session serviced by the a CCPE implementation.
  • the data packets with MPLS protocol can be transcoded and transmitted over the link aggregation session to the customer's CPE-CE device with labels intact.
  • the CPE-CE device can transcode from link aggregation ANA to MPLS again and deliver the packets on to the customer LAN.
  • the virtual (logical) link aggregated from a variety of diverse or dissimilar network connections through a single or multiple transceiver interfaces may be implemented over one physical link to encompass a single link aggregation for MPLS Edge with a bi-directional IP Quality of Service (QoS) achieved.
  • QoS IP Quality of Service
  • data packets with MPLS protocol may be transmitted across the MPLS core and arrive at the CPE-CE side of a network connection with MPLS label(s).
  • the MPLS labels can be retrieved and/or parsed by the CPE-CE device 124 (e.g. by an MPLS to ANA Handler 55) in order to determine further processing of the packet.
  • the MPLS labels can be acquired from the data packet with MPLS protocol (or also known as "MPLS packet"); (2) a table (such as a distribution table) maintained within or connected to the CPE-CE device 124 can cause the destination associated with the data packet and/or the MPLS label to be determined and accessed, and to retrieve corresponding rules (from e.g.
  • the MPLS packet can include a header that can be used for sub-processing.
  • the sub-processing can include IPDE to QoS transcoding or translation by MPLS/ IPDE QoS Translation module 53. This involves transcoding or translating the QoS request associated with a packet, as opposed to the packet itself.
  • ANA encapsulation may occur.
  • An encapsulation technique used can be MPLS network compatible or MPLS aware. This can be accomplished by using MPLS protocol as part of ANA encapsulation by MPLS/ANA Encapsulation module 52.
  • Extended Device Configuration Store 24 can allow ANA system to process MPLS packets. It may contain some of the same information that is used to perform the MPLS to IPDE QoS translation.
  • the system can continue to apply the QoS requests and therefore handling of MPLS packets continues to happen within ANA in a way that is consistent with transport of MPLS packets on an MPLS network.
  • the packets are not necessarily modified, rather, handling of the MPLS packet can occur based in part on ANA rules that are made to adhere dynamically to MPLS handling rules.
  • MPLS packets may come out of ANA link aggregation connection first by de-encapsulating, and then translating/transcoding so as to provide the MPLS data packets.
  • the network aggregation engine 11 may poll the state of network connections 19, 20 and 21 , for example, as per configured intervals stored in the device configuration store 24, to ensure that all network connections configured in an aggregated group are within configured acceptable tolerances. If a network connection 19, 20, and 21 exceeds acceptable tolerance values for any of the polled parameters, the network aggregation engine 11 may remove the network connection 19, 20, and 21 from within the aggregated network connection 22 without removing it from the polled network connections list. By leaving the removed network connection 19, 20, and 21 in the polled network connection list, the network aggregation engine 11 may aggregate the network connection into the aggregated network connection 22 once it has come back within acceptable tolerance values.
  • the network aggregation engine 11 may handle notifications to all end points configured within the device configuration store 24 with internal events such as changes in network connection state, threshold violations on configured thresholds for any number of configurable variables for any object within or connected to the network aggregation device 23.
  • the network aggregation engine 12 may also handle events such as changes in the state of a network connection 19, 20, and 21 included in the aggregated connection, changes in latency of a network connection included in the aggregated network connection 22, scheduling changes, event logging, and other events.
  • FIG. 4 is a block diagram of a communication device incorporating a particular embodiment, demonstrating the device acting as a server/concentrator or CCPE.
  • the network aggregation engine 11 may provide access to a network aggregation policy database 36 which stores configuration information related to the various aggregated network connections that terminate on the aggregated network connection device 28.
  • the network aggregation termination device 28 may be implemented in such a manner that each aggregated network connection defined in the network aggregation policy database 36 is handled by its own virtual instance, the use of which enables termination of each aggregated network connection from multiple customer premises equipment (CPE-CE).
  • CPE-CE customer premises equipment
  • an MPLS data store 40 may provide persistent data storage for MPLS related configuration information such as label lookup table, forwarding table, routing table, labeling and mapping policies, and/or MPLS provider information.
  • Network Aggregation Engine 11 may be operable to encapsulate incoming or inbound data from CPE-CE for transmission into core MPLS network.
  • Network Aggregation Engine 11 may remove MPLS label from outbound data packets exiting an MPLS network and forward the data packets to the appropriate CPE-CE based on a label look-up table or a forwarding table.
  • Network Aggregation Engine 11 is further operable to determine, based on the MPLS data store 40 and/or the MPLS label information on the outbound data packets, the final destination CPE-CE(s) to which each outbound data packet should be delivered.
  • FIG. 5 is a block diagram of a communication network incorporating a particular embodiment, demonstrating the function of the device acting as a client/CPE-CE and server/concentrator or CCPE.
  • aggregated network connections 70, 71 and 72 may be built by network aggregation devices 63, 64 and 65, which terminate to a single aggregated network connection termination device 61 through network connections 66 and 68 as their endpoint.
  • the aggregated network connection termination device 61 may access external communications networks through network connections 66 and 68 to access external/remote network resource 69.
  • Access to external communications networks may be provided by the aggregated network connection termination device 61 by using either network connection 66 or 68 through the use of a routing protocol, such as Border Gateway Protocol (BGP), Open Shortest Path (OSPF), or through the use of simpler mechanisms such as load sharing over multiple static routes within the communication network 74 that acts as the valid next-hop for the aggregated network connection termination device 61.
  • Border Gateway Protocol BGP
  • OSPF Open Shortest Path
  • Aggregated network connections 70, 71 and 72 may provide access to client network nodes 67 connected to the network aggregation devices 63, 64 and 65 through the aggregated network connections 70, 71 and 72 to communications networks 74 accessible by the aggregated network connection termination device 61.
  • a client network node 67 may request data provided by an external/remote network resource 69 accessible through a communication network 74.
  • This request for the external/remote network resource may be routed over the network connection 73 providing access from the client network node 67 over the aggregated network connection 70 to its end- point which is the aggregated network connection termination device 61. This may be done through the communication network 74 through the network connection 66 into the aggregated network connection termination device 61. Any data sent by the external/remote network resource 69 may be routed back through the aggregated network connection termination device.
  • a particular embodiment may use the Internet as the communication network 74 referenced in FIG 5, or another WAN network for example.
  • the communication network 74 may alternatively be built by multiple sub-networks created through the use of multiple network aggregation devices 63, 64 and 65 with aggregated network connection termination device 61 end points through multiple network connections 66 and 68. Furthermore, the communication network 74 may also be an MPLS network provided by an MPLS provider or carrier
  • FIG. 6 illustrates a method of providing redundancy and increased throughput through a plurality of network connections in an aggregated network connection.
  • the method 90 may begin with a step of configuring a plurality of network connections 91 through the creation of a network aggregation policy to form 92 the aggregated network connection.
  • the aggregated network connection may be initialized as per the network aggregation policy.
  • Control connections may be created 93 for the plurality of network connections configured as part of the aggregated connection to allow the aggregation engine 11 to manage the membership of a network connection within the aggregated connection.
  • the network aggregation engine 11 may accept packets for transmission 94 over the aggregated network connection 22.
  • the network aggregation engine 11 may choose a network connection 95 among the group of network connections configured 91 in the aggregate in the stored aggregation policy for transmission of the current packet being transmitted.
  • the choice of network connection for transmission of the current packet may be specified within the aggregation policy and may take into account data provided by the control connection built at 94.
  • a non-responsive network connection may be easily detected when using latency and packet loss as a measure.
  • the mechanism for detecting 96 and adapting to 97 the network connection change within an aggregated network connection may be implemented within the data transmission routine in the aggregation engine 11 or as a separate process in parallel to the transmission routine in the aggregation engine 11 to allow for further flexibility in provisioning redundancy within the aggregated network connection.
  • a single non-responsive network connection may not affect the aggregated network connection and may allow data transmission to continue regardless of the individual states of network connections so long as a single network connection within the aggregated network connection is available for data transmission.
  • Encryption may be provided for the link aggregation connections between a CPE-CE and a CCPE.
  • each lower-link connection handled and aggregated by a CCPE or CPE-CE may be encrypted by the Network Aggregation Engine 11 using transparent encryption.
  • an overlay of IPSEC may be implemented over the link aggregated connections, sometimes in conjunction with existing IPSEC Edge implementations.
  • IPSEC gateways or clients can be installed on the CPE-CE's connected to the various CCPEs.
  • the CPE-CEs with the IPSEC clients can terminate the IPSEC sessions on the CCPE or an existing carrier's IPSEC gateway on the MPLS network.
  • IPSEC may be implemented at the PE routers or device such as a CCPE.
  • a virtual edge overlay may provide transparent encryption for the aggregated connection between the CPE-CE and the CCPE.
  • An example is IPSEC.
  • the virtual edge may provide lower link transparent encryption as described herein.
  • FIGS. 7a and 7b illustrate network performance as discussed herein.
  • FIG. 7a illustrates performance with long haul effects.
  • FIG. 7b illustrates performance with reduction of long haul effects, based on embodiments in network conditions otherwise similar to those on which FIG. 7a is based.
  • FIG. 7b shows an improvement in performance over FIG. 7a, based on reduction of long haul effects in relatively long distance network communications are implemented using the network architecture.
  • Embodiments may provide improved network performance relative to speed.
  • a skilled reader will appreciate that the improvement in performance shown for the above example is significant.
  • Other aspects of network performance, e.g., latency may also be improved.
  • Embodiments may provide a network system for improving network communication performance between client sites at a distance from one another that is such that would usually require long haul network communication.
  • a Virtual Network Overlay for multiple networks, such as for example one or more WAN.
  • the Virtual Network Overly may allow multiple CPE devices to connect with CC devices and create an Over-The- Top Secure Network across Multiple Points-of-Presence between disparate sites.
  • the Virtual Network Overlay service can provide features such as optimized Internet access, secure WAN (or other secure networks), and diverse carrier failover, for example.
  • the Virtual Network Overly may support and integrate SCN, MDPS, and IPDE as described herein.
  • FIG. 8a there may be at least one client site network component 124a implemented at a client site A 120a for bonding or aggregating one or more diverse network connections so as to configure a bonded/aggregated connection 116a that has increased throughput.
  • the network server component 115a may be configured to connect to the client site network component 124a using the bonded/aggregated connection 116a.
  • the network server component 115a includes at least one concentrator element 110a implemented at a network access point to at least one network 112. As described, the network server component 115a automatically terminates the bonded/aggregated connection and passes the data traffic to an access point to at least one network 112.
  • a virtual edge 128 connects the network server component 115a and the client site network component 124a.
  • the virtual edge 128 may provide transparent lower-link encryption for the connection between the client site network component 124a and the network server component 115a.
  • the virtual edge 128 may implement a common access protocol for encapsulation of data packets for the data traffic carried over the bonded/aggregated connection 116a. This provides lower-link encapsulation support for protocols such as for example L2TP, PPPoE, PPTP, DHCP, UDP, and so on.
  • L2TP is a link-layer tunneling protocol to support VPNs.
  • the virtual edge 128 may provide transparent encryption of the tunneling protocol to provide security and confidentiality
  • the virtual edge 128 component addresses the Transparent Encryption Layer aspect of the SDN to SCN Mapping architecture as per the tables of system and network components herein.
  • the tunneling protocol allows for provision of network services that the underlying network does not provide directly.
  • a tunneling protocol may use a data portion of a data packet (e.g. payload) to carry the packets that provide the desired service.
  • L2TP may use L2TP packets to provide different network services.
  • the link layer is the lowest layer in the IP suite which may be referred to as TCP/IP which it the networking architecture of the Internet.
  • a link may be the physical and logical network component used to interconnect hosts or nodes in the network. Accordingly, the link layer relates to the links the physically connect the nodes of the network including the devices of the client site network component 124a and the network server component 115a.
  • the link layer may be described as a combination of the data link layer and the physical layer in the Open Systems Interconnection model.
  • Point-to- Point Protocol over Ethernet is a network protocol for frame encapsulation inside Ethernet frames.
  • Point-to-Point Tunneling Protocol may implement VPNs and may use a control channel over TCP and a GRE tunnel operating to encapsulate PPP packets. These are illustrative example protocols that may be used to support encapsulation of data packets using a common access protocol.
  • the virtual edge 128 lower-link tunneling protocol connections address the Site / Branch Infrastructure component of the SDN to SCN mapping for the Lower Plane infrastructure architecture as per the tables of system and network components herein.
  • a cloud network controller 140 is configured to manage the data traffic so as to provide a managed network overlay 126 that incorporates the at least the bonded/aggregated connection 116a and at least one long haul network path carried over the at least one wide area network 112.
  • the network overlay 126 may include one or more virtual edges 128.
  • the Network Overlay 126 addresses the Virtual Data Plane aspect of the SDN to SCN Mapping as per the tables of system and network components herein.
  • client site network component 124b implemented at a client site B 120b for bonding or aggregating one or more diverse network connections so as to configure a bonded/aggregated connection 116b that has increased throughput.
  • Network server components 115a, 115b connect through a WAN network 112.
  • the client site A 120a and client site B 120b may be at a distance from each other such that at least one long haul network path is required to transmit data there between.
  • the managed network overlays 126 may integrate to provide a single managed network overlay between disparate client sites and may include both virtual edges 128.
  • FIGs. 9a and 9b there may be multiple networks 112 connected by concentrator elements 110a, 110b, 110c.
  • concentrator elements 110a, 110b, 110c there may be a first concentrator element 110a implemented at the access point to the at least one WAN 112.
  • the first concentrator element 110a and the second concentrator element 110c are configured to interoperate to provide a virtual core (VC) connection 135a between the access points.
  • the VC connection 135 may be a virtual Ethernet tunnel in some example embodiments.
  • the third concentrator element 110b and the second concentrator element 110c are configured to interoperate to provide another VC connection 135b between the access points.
  • the VC connection 135a, 135b provides transparent encryption.
  • the cloud network controller 140 is configured to manage the data traffic so as to provide a managed network overlay 150 that incorporates at least one long haul network path carried over the WANs 112.
  • the managed network overlay 150 may be referred to herein as the Virtual Network Overlay 150. As shown in FIG.
  • the Virtual Network Overlay 150 may involve the VC connections 135a, 135b to provide a virtual connection between the concentrator elements 110a, 110b.
  • the VC connection 135a, 135b may provide a bonded/aggregated connection.
  • the Virtual Network Overlay 150 may involve a VC connection 135a to provide a virtual connection between the concentrator elements 110a, 110c.
  • a single managed virtual network overlay may integrate multiple Network Overlays 126, 150, multiple virtual edge connections 128, and multiple VC connections 135a, 135b.
  • the singled managed virtual network overlay may provide an end-to-end overlay connecting disparate client sites (e.g. site A 120a, site B 120b).
  • the Cloud Network Controller 140 addresses the Orchestration aspect of the SDN to SCN Mapping as per the tables of system and network components herein.
  • a cloud network controller 140 may be configured to manage the data traffic so as to provide the managed network overlay 150 that incorporates the other bonded/aggregated connection 116c.
  • Embodiments described herein may implement a cloud network controller 140 to implement Software Controlled Networking (SCN) to deliver bonded/aggregated connection and WAN virtualization between existing PoPs with concentrator elements.
  • SCN Software Controlled Networking
  • the solution may provide the ability to offer WAN-as-a-Service (WaaS) through a distributed PoP network.
  • WiaS WAN-as-a-Service
  • Embodiments described herein may implement SCN-edge into a core network to provide end-to-end Virtualized Networking and deliver next generation WAN solutions using a Virtual Network Overlay 150. Examples are shown in FIGs. 8a, 8b, 9a, 9b, 9c.
  • the VC connections may extend a bonded/aggregated connection to a core network 12.
  • FIGs. 10 and 12 Two additional illustrative examples are shown in FIGs. 10 and 12. As shown in FIG. 10, the extension of a bonded/aggregated connection from the edge to core may be provided using the following illustrative example options: 1) deploying a virtual network overlay strategy between PoP's with encryption (A); and 2) interconnecting PoP's with private lines (B). These are illustrative examples only.
  • the Virtual Network Overlay 145 may provide autonomy from any Carrier or Network in the core network 112.
  • the core network 112 may be a central component or part of a communications network and may be implemented using different networking technologies and protocols.
  • the Virtual Network Overlay 145 may be implemented as a virtual WAN backhaul between POPs 130 or concentrator elements 110.
  • the Virtual Network Overlay 145 may be meshed Generic Routing Encapsulation (GRE) or virtual Ethernet tunnel network (e.g. using VC connections 135a, 135b) connecting multiple cloud concentrator elements (e.g. from cloud concentrator 110a to cloud concentrator 110b).
  • GRE Generic Routing Encapsulation
  • the GRE protocol may belong to a specific VLAN by IP or Bridged.
  • Each concentrator element 110a, 110b may be part of a POP 130 or may be connected to a nearby POP 130.
  • the concentrator element 110 may be referred to as a virtual WAN cloud concentrator instance generated by network controller 140 accessible by way of an SCN portal.
  • Each concentrator element 110a, 110b may handle multiple bonded/ aggregated connections and may handle one process per network or customer.
  • the network controller 140 may be accessed using an SCN portal as an illustrative embodiment.
  • the SCN portal may be an interface to display real-time data about the network infrastructure and may be used to configure various components of the network infrastructure.
  • a CPE 124 a, 124b may be a virtual access CPE providing WAN or Internet access. It may have diverse carrier support with bandwidth aggregation. Additional optional features may include pre-emptive failover, lossless/ same IP and bi-directional IPQoS capabilities.
  • a private backhaul or backbone option 155 may also be deployed to provide WAN solution. The private backhaul may include private MPLS or P2P links between POPs 130.
  • VWAN Virtual Network Overlay
  • a VWAN can be a VLAN associated per network or customer.
  • virtual edge architecture may allow for the Layering of MPLS or other network protocol over the top of this implementation.
  • Embodiments described herein may provide a virtual edge for aggregated/ bonded connections with transparent lower-link encryption.
  • FIG. 8a shows an example virtual edge 128.
  • implementation of proximal aggregation connects multi-site customer CPE 124 devices to the nearest point-of-presence (POP) 130, thereby establishing an overlay network session with aggregated connections using the aggregated/ bonded connection technology described herein.
  • CPE 124 devices belonging to multi-site customers may use the larger non-aggregated Internet or backbone upstream connections to establish Internet access and build IPVPN connections for inter-office communications. This may eliminate the need to perform long-haul aggregation between sites which may degrade and/or negate the aggregated network performance when communicating at a distance.
  • CPE encryption for multi-tenant implementations add complexity to the practice of encrypted VPN when observed on a per customer basis and having to manage overlapping CPE LAN IP Subnets from various customers. Furthermore, this multi-tenant management of per customer IPVPN connections carries additional complexity when considering the distributed nature of these diverse VPN implementations and overlapping CPE LAN subnets.
  • a transparent Lower-Link protocol encryption technology or process may be deployed for the virtual edge that does not concern itself with the CPE LAN IP Subnet. This technology or process can encrypt the Lower-Link encapsulated traffic and moves the responsibility of the CPE LAN IP Subnet management up into the ANA and IP transport layers, where it can be addressed adequately without the complications of encryption management and complex encryption policy definitions in a multi-tenant deployment.
  • the Virtual Network Overlay may provide PoP-to- CPE Transparent Lower-Link Encryption for each aggregated/ bonded connection 116 using virtual edge connections and virtual core (VC) connections.
  • the VC connection may be implemented as a virtual Ethernet tunnel. This may eliminate the need for Customer IP intelligence in the encryption layer for Lower-Links.
  • the transparent lower-link encryption at concentrator elements 110 can encrypt all aggregated/ bonded encapsulation of Lower-Link connections transparently.
  • the Virtual Network Overlay is designed such that concentrator element 110 if and when CPE 124 is configured to enable lower-link encryption. This allows for both the Virtual Network Overlayand non-Virtual Network OverlayCPE implementations. Therefore, the Virtual Network Overlay can reach customers with a secure connection that may go faster and may cost less than traditional MPLS.
  • IPSEC encryption may be used for Lower- Link transport. This allows for multiple CPE customers with overlapping IP subnets by not triggering the policy based on customer LAN subnet.
  • lower-link encapsulation may have a 32 Byte overhead per packet implemented on the LMTU and LMRU settings.
  • the VifO or 'ana session' may also have an overhead of 8 bytes implemented on the LMRRU setting of 1508.
  • IPSec encryption for Lower-Links may require an additional 72 Bytes for ESP Tunnel Mode and may be accommodated in configuration in the LMTU and LMRU settings, which may require changes to the calibration and also template configuration in cloud network controller 140 for service type of the Virtual Network Overlay.
  • a CPE 124 or a third party device may be used to connect to concentrator element 110a through aggregated/ bonded connection 116.
  • the CPE 124 or a third party device may be situated at overlapping IP subnets and possibly dealing with cpelan conflicts.
  • the concentrator elements 110a may map Virtual Edge to CPE Vif and update routing accordingly, via for example RADIUS protocol, which provides overlay identifier (e.g. vwanid) and other attributes (e.g. cpelan attributes).
  • Concentrator elements 110a may also inject route to OSPF.
  • Concentrator elements 110a may also inject the route(s) into the Virtual Core's dynamic routing mechanism such as OSPF, RIP, or BGP.
  • various VC connections 135a, 135b can be established between various concentrator elements 110a, 110b, 110c. These VC connections form a POP-to-POP Network Overlay, where each POP may include one or more concentrator elements 110. Transparent Encryption may be provided for the Virtual Network Overlay core transport.
  • the Virtual Core connection 135 addresses the Virtual Control Plane aspect of the SDN to SCN Mapping as per the tables of system and network components herein.
  • the transparent encryption of the virtual core tunneling protocol connections address the Core /
  • Branch Infrastructure component of the SDN to SCN mapping for the Lower Plane infrastructure architecture as per the tables of system and network components herein.
  • VWAN Virtual Network Overlay
  • virtual WAN virtual WAN
  • the SCN Portal application may be extended to support the new VWAN Management monitoring and management requirements and provide a single sign-on unified Portal for VWAN customers.
  • the SCN Portal application may be modified to support the new VWAN / Provisioning requirements as an extension to the aggregated connection CPE device provisioning.
  • Virtual Control Concentrators may join VWAN CPE sessions with VWAN Core Routing Plane VRF w/OSPF to create secluded customer Route Domains managed dynamically using OSPF, a dynamic routing protocol. This may avoid a network trombone impact and may to support a split Internet & WAN access from the PoP for the Virtual Data Plane.
  • NAS Network Access Server
  • New RADIUS Remote Authentication Dial In User Service
  • New RADIUS Remote Authentication Dial In User Service
  • the SDN to SCN table provides an illustrative example mapping between IP networking, SDN, SCN and Virtual Network Overlay to highlight example features.
  • the terminology is used as an example illustration and other terminology may be used to reference various functionality.
  • the table summarizes example features to provide an illustrative mapping.
  • the table also lists example features for Over-The-Top (OTT) lower plane infrastructure as further illustrative mappings.
  • OTT Over-The-Top
  • Virtual Network Overlay with SCN may use cloud network controller 140 with SCN Cloud management and automation to create an Over-The-Top Secure High Performance Network that connects multiple WAN sites across Multiple Points-of- Presence between CPE devices.
  • the Network Overlay may provide Optimized Internet Access, Secure WAN, Diverse Carrier Failover, and Bi-Directional IPQoS. Carrier/Partner Features
  • the VWAN configuration can support multi-tenant implementations by providing features such as route domain separation for overlapping customer IP Subnets, star and/or mesh WAN topology options with multipath WAN trunking, and dynamic per-VWAN routing updates with OSPF.
  • the Virtual Network Overlay (which may be referred to as VWAN) may provide PoP-to-PoP transparent VWAN trunk encryption, which has features such as:
  • VWAN core trunks can be established for each multi-tenant customer as transparent Ethernet over IP tunnels that run on top of a single encryption session between CC's/PoPs;
  • Distributed PoPs provide a Virtual Point-of-Presence Network, enabling VWAN solutions to reach multi-site customers across North America.
  • the SCN Portal can be provided for accessing and configuring a cloud network controller 140 for ease of deployment and management of the VWAN.
  • the SCN Portal can provide the following exemplary features:
  • VWAN may have a distributed PoP network covering North America for aggregation/ bonded network services delivering speed, network efficiency, and reach for multi- site businesses.
  • a Virtual Point-of-Presence Carrier for the aggregated network system as described herein may provide customers with hot failover providing redundant and fault tolerant communications, supporting distributed points of presence for proximal aggregation throughout North America.
  • DPA Distributed Proximal Aggregation
  • DPA uses redundant Concentrators 110 established in multiple locations covering a multitude of Proximal Aggregation points known as Home-PoPs 130.
  • Each Concentrator 110 supports multi-tenant configurations used for multiple clients associated with different CPEs 124 to improve network performance for such multiple clients by providing termination of their aggregation service and transfer of communications to the network backbone / Internet 112.
  • This network solution may include multiple Points-of-Presence 130, distributed geographically bridging disparate areas with improved network communication with proximal aggregation to each customer CPE device 124.
  • PoP-to-PoP encryption for multi-tenant implementations adds complexity and may have limitations for the practice of Encrypted VPN between PoPs when observed on a per customer basis and having to deal with overlapping CPE LAN IP Subnets from various customers. Furthermore, the multi-tenant management of per customer IPVPN connections carries additional complexity when considering the distributed nature of these many diverse VPN implementations and overlapping CPE LAN subnets. Simplifying PoP-to-PoP Encryption
  • extrapolation of the CPE LAN transport over the VWAN core from the encryption layer may be implemented to simplify the PoP-to-PoP encryption management.
  • Ethernet over IP tunnel (VE/gif) implementations on a per customer VWAN basis provides transparent encryption of these combined tunnels to simplify customer VWAN encryption requirements between PoPs 130.
  • This method moves the management of CPE LAN IP Subnets away from the VWAN Trunk encryption layer and up into the IP transport and IP routing layers.
  • PoP-to-PoP Transparent VWAN Trunk Encryption may be implemented to eliminate the need for customer LAN intelligence in the encryption layer between PoPs, provide transparent customer WAN Core / trunk encryption between PoPs, and provide single encryption session between CC's/PoP's on top of which transparently create per customer multi-tenant Ethernet over IP tunnels (VE/gif) to facilitate VWAN Core Trunks.
  • VE/gif IP tunnels
  • an over-the-top or Virtual Network Overlay solution can be implemented for the PoP-to-PoP interconnection of the core network.
  • This solution can support multi-tenant implementations by providing route domain separation for overlapping customer IP Subnets, star and/or mesh WAN topology options with multipath WAN trunking, and dynamic per-VWAN routing updates with OSPF.
  • This addresses the Virtual Control Plane component of the SDN to SCN mapping as per the tables of system and network components herein.
  • the design associates VE PoP-to-PoP tunnels per customer VWAN with a distinct route domain by mapping VE trunks and ANA Vif sessions to unique FIBs/Route tables creating a per customer VWAN Route domain from one CPE to another CPE over the VWAN core.
  • the VE/gif interface can be a generic tunneling device for IPv4 and IPv6. It can tunnel IPv[46] traffic over IPv[46], thereby supporting four possible configurations.
  • the behavior of gif is mainly based on RFC2893 IPv6-over-IPv4 configured tunnel.
  • Aggregation sessions are generally established between PoP's on a per customer basis. As seen below, a Star or a full Mesh implementation may be provided to address the varying needs of the customer.
  • CPE LAN traffic destined for the Head Quarter's LAN can traverse the ANA PoP-to-PoP session with full IPSec encryption.
  • the PoP-to-PoP ANA sessions originate and terminate on the customer VWAN CC's and use the dedicated Multi-ANA instance which is associated to the dedicated customer FIB.
  • CPE LAN traffic destined for any other customer LAN can traverse the ANA PoP-to-PoP sessions with full IPSec encryption.
  • the Virtual Network Overlay may provide the ability to subscribe to specific PoP-to-PoP bandwidth controlled by ANA RLA.
  • Virtual Network Overlay may have the ability to use the IPDE RLA on lower-links for the Virtual Data Path (e.g. may be an aggregated product) and also between PoPs in the Virtual Control Plane (VC).
  • the Virtual Network Overlay may provide VC connections, for example.
  • SCN Lite - RAS & Open Architecture As shown in Fig. 16, routers with static ANA IP assignments can be implemented to connect as SCN-Lite for fixed sites. This embodiment opens up access to non- aggregated/bonded connection third party devices and software clients. In some embodiments, this may involve configuration of third party devices including both CPE and CCs.
  • a third party device may be a router.
  • third party devices, the CPE may be configured to support both non Aggregated and Aggregated implementations.
  • Embodiments described herein may involve particular configuration of third party network infrastructure for the Virtual Network Overlay, SCN, MDPS and IDPE functionality.
  • the network infrastructure may be configured to support bonded/aggregated connections with multi- POP to provide improved virtual networking functionality.
  • the Virtual Network Overlay may be implemented with carrier autonomy and independent CPE components supplied by third parties, for example. This may enable a user to avoid vendor lock as they update their CPE with particular configurations to support the Virtual Network Overlay.
  • third party routers may be upgraded with particular configurations described herein without requiring replacement of all hardware for the CPE.
  • both ANA2 and L2TP link types may be supported simultaneously. There may also be a need to support multiple ANA2 ports such as x.x.x.x:6666, 7777, and 8888.
  • ANA2-Server may support L2TP clients by configuring wildcard and NAT for Lower-Links security tasks on IPSec. Therefore, one solution may be implemented via mostly CLI and scripts.
  • new RADIUS attributes may be added for third party device identification. For instance, new attribute may be set to SCNLITE, with value set to 1 or 0, and default value set to 0.
  • CLI values may be changed to support both ANA2 and L2TP simultaneously.
  • a third party device may be configured to connect to an aggregate of multiple connections between concentrator elements using L2TP as the Lower-Links transport. This illustrative example uses L2TP which supports multilink and is used for connecting to ISP's and for remote access.
  • L2TP which supports multilink and is used for connecting to ISP's and for remote access.
  • the particular configurations may enable integration of third party devices into the Virtual Network Overlay infrastructure to turn the third party devices into concentrator elements or CPE devices.
  • an example illustrative embodiment may use MLPPP RFC 1990 with an aggregated/bonded connection as an overlay on top of common access protocols such as L2TP, PPPoE, or PPTP with multiple route tables and or static routes to manage and separate the Lower-Link traffic for aggregation. Once the traffic is separated we use MLPPP on the CPE to connect with CC elements.
  • the process may involve separating CPE traffic on the Lower-Links connecting the network infrastructure components. This may operation may involve
  • a third party router (as part of the CPE) to update Lower-Links and multiple network connections .
  • This may involve using a static IP route on each of the multiple interfaces or a dynamically assigned IP via DHCP or PPPoE or other protocol. This may further involve removing the default route on these interfaces or use of a separate routing table for each, such as a virtual routing and forwarding (VRF), for example.
  • VRF virtual routing and forwarding
  • Static routes or multiple route tables may be added on each respective Lower-Link for the corresponding the CC Lower-Link IP. This effectively separates the Lower-Links data traffic.
  • the process may involve CPE Links configuration for a Common Access Protocol.
  • the Common Access Protocol may be for encapsulation and aggregation of data packets.
  • This supports third party router equipment configuration for aggregated/bonded connection access using L2TP, PPPoE, PPTP, or other protocol.
  • This may involve setup of virtual dialer templates for the lower-link transport using L2TP, PPPoE, or PPTP, for example.
  • the virtual dialer templates allow for traditional MLPPP RFC 1990 to function over IP versus lower level serial type connections to T1 circuits. This may also involve setup of a multilink bundle with PPP multilink over the lower-link transport infrastructure.
  • the aggregated/bonded connection may be compatible for MLPPP once the lower-link transport is compliant with a supported protocol such as L2TP, PPPoE, or PPTP, for example. This may also involve configuration of the third party router / CPE to use the multilink virtual interface as the default gateway.
  • These process operations may be used for CPE based on a third party device such as a third party router. From a Lower-Links perspective before aggregation these operations may ensure each lower-link has a separate path, and adds a static route for lower level IP address link. This may provide support for aggregated/bonded connections with a common transport protocol (L2TP). This may configure routers with multi-link over IP and provide lower-link encapsulation of data packets. For example, this may provide lower link encapsulation support for L2TP and PPPoE and PPTP and other protocols such as DHCP, UDP.
  • L2TP common transport protocol
  • Further configurations may involve operations for CC to be compatible with lower links of configured third party device.
  • An operation may involve CC element configuration with MLPPP for Common Access Lower-Link Protocols.
  • a CC for aggregated/bonded connections may be configured with MLPPP support over common Lower-Link transport protocols such as L2TP, PPPoE, or PPTP. This adds transport compatibility on the encapsulation side.
  • embodiments described herein may provide a Virtual Network
  • the system may include an intelligent packet distribution engine (“IPDE") that incorporates or is linked to means for executing a decision tree.
  • IPDE intelligent packet distribution engine
  • the IPDE in real time, obtains data traffic parameters and, based on the data traffic parameters and performance criteria, selectively applies one or more techniques to alter the traffic over selected communication links to conform to the data traffic parameters. Further details are described in Applicant's U.S. Patent No. 8,737,214, which is incorporated by reference.
  • Another operation may involve CC element configuration for the IPDE which can manage outbound packets to the CPE for differing speed links and RLA QoS.
  • the CC element may use echo packets received from the CPE to implement aspects of the IPDE.
  • a third party router may not be configured to support the IPDE and may not support differing speeds upload to the CC.
  • the CC may be updated to provide this IPDE implementation. Some example embodiments may be limited to Nx (Least Common Speed link) for aggregation.
  • the configured CC element provides the aggregated/bonded connections.
  • a further operation may involve CC element configuration with MDPS support for fast failover and can use the third party Router configuration of Lower-Link transport LCP echo packets as control packets.
  • the CC makes its own calculations based on the LCP echo packets for QoE scores and fast advanced failover.
  • the third party router does not have MDPS and does not pre-emptively inform the CC over the other good links of a potential problem.
  • the third party router may not have MDPS and may not calculate QoE scores from the LCP echo packets in some embodiments.
  • the third party router may not have IPDE and pre-emptive failover.
  • the CC takes echo packets or requests from the router (an example CPE) and generates QoE scores.
  • the cloud controller may pull data from CC elements and augment data from router QoE to support IPDE, for example. Further details are described in Applicant's U.S. Patent No. 8,737,214, which is incorporated by reference.
  • An example embodiment may involve IPSec Transport Mode Required with NAT Traversal Support.
  • Example configuration details for third party devices are described herein and may be used for L2TP and IPSec implementations.
  • each CC 110 will be assigned a dynamic IP address Pool configured to support dynamic clients.
  • IPSec may be used to provide the transparent lower-link encryption for CPE devices to address the encryption layer of the lower-link access in the tables of system and network components herein.
  • the Virtual Network Overlay may implement a dynamic IP address strategy for RAS accounts and type.
  • individual Routing Domains may be designated in operating systems to map VE to Vif, creating a per customer Forwarding Information Base (FIB) to address the overlapping CPE LAN IP Subnets problem by implementing per VWAN Customer Routing Domains.
  • FIB Forwarding Information Base
  • individual Routing Domains may be designated for an example operating system using FIBs in AgniOS/FreeBSD to map VE to Vif.
  • BIRD can support for multiple instances per VWAN and iBGP filters out VWANs.
  • concentrator element 110 may advertise and receive routes from different FIBs over OSPF.
  • a new CLI node router-ospf may be added to configure, show, enable and disable OSPF routes.
  • a new configure editor may be needed for OSPF configurations.
  • Second option may be to use two different applications, BIRD for eBGP and iBGP, and BIRD-FIB for OSPF.
  • the second option may be use one application for both BGP and OSPF.
  • BIRD may be used with iBGP for propagating connected CPE devices on the concentrator element 110. BIRD may have support for multiple instances of OSPF that can be used for managing virtual network overlay route domains.
  • OSPF - Managing Per Customer Routing Domains [00280]
  • OSPF Open Shortest Path
  • BIRD and OSPF with multi- Fib support and filters for each FIB can be implemented to achieve dynamic routing for VWAN Mesh configuration.
  • IP addresses for CPE bonded connections may not be advertised, as instead they may be handled by the Internet.
  • concentrator element 110 can utilize RADIUS protocol, which provides an overlay identifier (e.g. vwanid) and other attributes (e.g. cpelan attributes). Concentrator elements 110 may also inject route to OSPF for centralized management of new vwanid & cpelan attributes [00284] In another embodiment, new concentrator element 110 RADIUS processing of new attributes can dynamically manage customer virtual network overlay mapping for ANA interface to virtual network overlay route domains.
  • RADIUS protocol which provides an overlay identifier (e.g. vwanid) and other attributes (e.g. cpelan attributes).
  • Concentrator elements 110 may also inject route to OSPF for centralized management of new vwanid & cpelan attributes
  • new concentrator element 110 RADIUS processing of new attributes can dynamically manage customer virtual network overlay mapping for ANA interface to virtual network overlay route domains.
  • attributes may be used by concentrator element 110 to inject LAN routes into a dynamic routing protocol such as RIP, OSPF, and iBGP.
  • a dynamic routing protocol such as RIP, OSPF, and iBGP.
  • an additional RADIUS attribute to identify the unique customer e.g. "VWANGROUP" may be needed.
  • An additional level of security on the ANA2 instance may be needed to inform RADIUS the "VWANGROUP” and therefore RADIUS allows this CC/ANA2 instance to authenticate CPE users that belong to the group identified by ID "VWANGROUP”.
  • An example configuration on concentrator element 110 may be to set the unique customer ID ("vwangroup") to a first customer ID customerl and a second customer ID customed.
  • variable $fib may be used to set values for the unique customer ID ("vwangroup").
  • Embodiments described herein may implement an Identity, Policy and Audit (IPA) suite or other type of authentication system.
  • IPA Identity, Policy and Audit
  • An Lightweight Directory Access Protocol (LDAP) is an open industry standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. LDAP may also be part of an authentication system.
  • Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication,
  • a custom attribute may be created in LDAP and enabled to be visible to concentrator element 110. Since everything in LDAP is hierarchical, including object-classes and attributes, to create a custom attribute, the appropriate scheme file needs to be edited. This is an example implement.
  • Embodiments described herein may provide an authentication backend for the Virtual Network Overlay which may include LDAP or RADIUS, or both.
  • LDAP LDAP
  • RADIUS Remote Authentication Dial Identity
  • An attribute may be created by matching objectClasses and attributeTypes exactly.
  • the attribute may be added into two files: attribute map and FreeRadius. These are illustrative example files.
  • a file can be created.
  • the file may be created as usr/share/freeradius" dictionary.yourName.
  • the Idap.attrmap can map dictionary attributes to LDAP directory to be used by LDAP authentication. For example, the attribute may be added in etc/raddb". When all changes are done, RADIUS or other authentication system may be restarted.
  • IPDE-RLA Dynamic [00297]
  • dynamic IPDE-RLA implemented on VWAN can bring dynamic bandwidth reservation for RLA allowing IPDE-RLA-bypass rules for traffic for which the reserve bandwidth can be specified and dynamically applied, if the traffic exists. When the traffic is no longer present, the bandwidth can be released for use by other applications.
  • Voice and Video with Data For instance, voice tends to be much easier to deal with in a static configuration. It requires relatively low bandwidth and the reservation of this bandwidth can be an acceptable sacrifice for the other applications.
  • Video conferencing tends to require large amounts of bandwidth (from upload perspective) and is not always on. The problem is that in order for a static system to support video, it needs to reserve the bandwidth all the time and this is not an acceptable sacrifice for other applications.
  • "dynamic, bandwidth, timeout” parameters can be added to support the new feature.
  • means to control certificates may be required within cloud manager 140.
  • the Virtual Network Overlay may provide a virtual WAN backhaul with multi-tenant support.
  • the Virtual Network Overlay may provide VC connection management.
  • Example configurations for VC connection management may include:
  • the Virtual Network Overlay may provide VC connection management.
  • Example configurations for fibs support may include:
  • An automated means may map the various VC interfaces with customer Route tables / VRF in the cloud that uses an API connection to the VC devices (Concentrators) and performs the otherwise manual task Map VC & Vif to FIB (RADIUS on CC)
  • An automated means may map the various VC interfaces with customer Route tables / VRF and also with customer ANA sessions in the cloud that uses an API connection to the VC devices (Concentrators) and performs the otherwise manual task.
  • Map Vif to FIB RADIUS on CC
  • CC can read the
  • CPEVWANID from CPE radius configuration and then can run commands such as: ifconfig $interface fib $CPEVWANID
  • Map VC to FIB (RADIUS on CC) [00310]
  • VC interfaces can be created only in the default FIB (FIB 0) and will manage traffic between this CC and other CCs. Firewall rules and routes will be added to distribute CPE VWAN traffic from/to each FIB.
  • VC interfaces can also be created in different FIB's, same as the CPE Vif interface.
  • RADIUS is an illustrative example authentication component. IP node, system node. CLI & scripts. SCN
  • IP nodes may provide FIB support for VE interface management.
  • system node may provide FIB support which may be required for any command with an interface specified Operating System support for 4096 or greater FIB's
  • different operating systems may be support multiple FIBs.
  • AgniOS v4.1.2+ may support multiple FIBs (e.g. up to 16 in some
  • VWAN there may be support for 4096 individual VWANs.
  • Each VWAN will not need multiple FIB's for each CPE as the CC brings them in on setfib $FIB ana2-server.
  • net-add addr allfibs 0 (ANA only affect SFIBCUST for ANA2-SCUST)
  • implementations may enable addition of routes on all FIBs for new interfaces by default. When this is set to 0, it will only allocate routes on interface changes for the FIB of the caller when adding a new set of addresses to an interface. Note that this tunable and is set to 1 by default.
  • Cloud manager 140 can provide for Ease of Deployment and Management via implementation of following functions and features:
  • Items for management can include: • CPE ANA Lower-Link Encryption/I PSec
  • Categories for management can include:
  • a new ID Table may be created for the Virtual Network Overlay by specifying variables such as vwanid, vwansubnet (RFC1918 /24), partnerid, custid.
  • VWANID variable may be set by specifying or searching for cloud concentrator pairs and selecting a topology (e.g. star or mesh).
  • topology e.g. star or mesh.
  • Core Virtual Network Overlay e.g. VC connections
  • PoPs/Concentrator elements may be set up. Concentrator elements can be configured for VC connections.sending via AGNIAPID VC connections require private IP assigned from
  • Figs. 19a and 19b illustrate exemplary relationship diagrams for cloud manager 140 and SCN Database and tables.
  • ACL Portal Access Control List
  • FIGs. 19a and 19b New Dynamic IP Address Pool for RAS
  • each concentrator element may need a dynamic IP address Pool configured to support dynamic clients.
  • dynamic IP pool may be assigned to each concentrator element, and/ or each concentrator element may be further configured for a dynamic pool.
  • This method can allow traveling users to connect with proximal remote access termination for optimal service.
  • ANA GRID Routing and Firewall can be controlled from the cloud and achieve software defined networking and global denial of service with intrusion detection protection.
  • centralized control of all BGP devices may be required.
  • Dissemination of Flow Specification Rules may be achieved by using RFC 5575.
  • RFC 5575 Global Denial of Service Detection
  • a Denial of Service Attack can be detected at any device and a global defence may be triggered according. This attack can be filtered to prevent entry to any ANA Grid controlled Network.
  • Global Intrusion Detection can be detected at any device and a global defence may be triggered according. This attack can be filtered to prevent entry to any ANA Grid controlled Network.
  • a simplified Intrusion detection software instance running on all BGP devices controlled by cloud manager 140 can inform the cloud manager 140, which can make a centralized intrusion detection decision with threat level analysis.
  • the system can propagate a deny rule for said traffic to all devices and the culprit traffic will be filtered out from all PoPs. This technology can also extend to the CPE devices.
  • WiFi access security may be implemented for various operating systems, such as, for example, AgniOS.
  • CPE devices can provide WiFi for the Enterprise using Virtual Access Point technology with centralized authentication and security, managed central portal of cloud manager 140 in the cloud.
  • Virtual Access Point technology with centralized authentication and security, managed central portal of cloud manager 140 in the cloud.
  • VAP Virtual Access Point
  • SSID Service Set Identification
  • WLAN Wireless Local Area Network
  • VWAN can support Enterprise grade Wi-Fi services using a combination of cloud management features, CPE firewall, and CPE VPN remote access VPN capabilities that work with the customer's corporate authentication mechanisms such as Active Directory or RADIUS.
  • the CPE ⁇ pptp-server> node can use the corporate Active Directory security, or Customer RADIUS database for assigning users to special remote access groups which in turn assigns users to VLANs on the CPE device.
  • CC's 110 for Large Enterprise customers may be used to provide private meshes between PoPs for transport of WAN traffic with Over-The-Top control from both Edge (CPE to Home-PoP) and Core (PoP-to-PoP between CC's).
  • CPE to Home-PoP Edge
  • Core PoP-to-PoP between CC's.
  • the embodiments described herein may improve network performance between disparate locations by leveraging network bonding/aggregation technology, but by implementing a system, method and network configuration that provides intervening network components disposed adjacent to access points so as to manage traffic between two or more sites such that bonded/aggregated connections are terminated and traffic is directed to a network backbone, and optionally passed to one or more further bonded/aggregated connections associated with a remote additional site.
  • the network solutions of the present invention are flexible, responsive, scalable and easy to implement. New sites, optionally having their own CPE-CE and/or CCPE can be easily added, and the network solution supports various types of multi-point network communications, and various network performance improvement strategies including various QoS techniques.
  • the network solution is easily updated with new programming or logic that is automatically distributed on a peer to peer basis based on the interoperation of network components that is inherent to their design, as previously described.
  • embodiments of the present invention may offer advantages over the prior art technologies, including, for example:
  • Network providers or partners can deliver an "any/any/any” experience to their customers - BYOMPLS (Bring Your Own MPLS) ability to the network providers or partners.
  • BYOMPLS Back Your Own MPLS

Landscapes

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

Abstract

Un système de réseau est prévu entre au moins un premier site client et un second site client, le premier et le second site client étant séparés d'une certaine distance. Un composant de réseau de site client est implémenté au moins au premier site client, le composant de réseau de site client associant ou agrégeant une ou plusieurs connexions de réseau diverses de sorte à configurer une connexion associée/agrégée ayant un rendement accru. Au moins un composant de serveur de réseau peut être configuré pour se connecter au composant de réseau de site client au moyen de la connexion associée/agrégée. Un contrôleur de réseau en nuage peut être configuré pour gérer le trafic de données et un bord virtuel fournissant un cryptage de liaison inférieur transparent pour la connexion associée/agrégée entre le composant de réseau de site client et le composant de serveur de réseau.
PCT/CA2016/000185 2008-11-12 2016-06-30 Système, appareil, et procédé pour la fourniture d'un réseau virtuel edge ou overlay WO2017004693A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/738,056 US10523593B2 (en) 2008-11-12 2016-06-30 System, apparatus and method for providing a virtual network edge and overlay
CA2990045A CA2990045C (fr) 2015-07-03 2016-06-30 Systeme, appareil, et procede pour la fourniture d'un reseau virtuel edge ou overlay

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/791311 2015-07-03
US14/791,311 US9692713B2 (en) 2008-11-12 2015-07-03 System, apparatus and method for providing a virtual network edge and overlay

Publications (1)

Publication Number Publication Date
WO2017004693A1 true WO2017004693A1 (fr) 2017-01-12

Family

ID=57684649

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2016/000185 WO2017004693A1 (fr) 2008-11-12 2016-06-30 Système, appareil, et procédé pour la fourniture d'un réseau virtuel edge ou overlay

Country Status (2)

Country Link
CA (1) CA2990045C (fr)
WO (1) WO2017004693A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109756854A (zh) * 2017-11-06 2019-05-14 普天信息技术有限公司 一种集群业务释放方法
CN110365577A (zh) * 2019-07-24 2019-10-22 北京神州绿盟信息安全科技股份有限公司 一种安全资源池的引流系统
CN113839824A (zh) * 2020-06-08 2021-12-24 奇安信科技集团股份有限公司 流量审计方法、装置、电子设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014145363A2 (fr) * 2013-03-15 2014-09-18 Hughes Network Systems, Llc Compression de données pour un trafic de données basé sur la priorité, à un niveau de trafic agrégé, dans un système de communication à flux multiples
US20150003465A1 (en) * 2008-11-12 2015-01-01 Teloip Inc System, apparatus and method for providing improved performance of aggregated/bonded network connections with multiprotocol label switching

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150003465A1 (en) * 2008-11-12 2015-01-01 Teloip Inc System, apparatus and method for providing improved performance of aggregated/bonded network connections with multiprotocol label switching
WO2014145363A2 (fr) * 2013-03-15 2014-09-18 Hughes Network Systems, Llc Compression de données pour un trafic de données basé sur la priorité, à un niveau de trafic agrégé, dans un système de communication à flux multiples

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109756854A (zh) * 2017-11-06 2019-05-14 普天信息技术有限公司 一种集群业务释放方法
CN109756854B (zh) * 2017-11-06 2021-10-26 普天信息技术有限公司 一种集群业务释放方法
CN110365577A (zh) * 2019-07-24 2019-10-22 北京神州绿盟信息安全科技股份有限公司 一种安全资源池的引流系统
CN110365577B (zh) * 2019-07-24 2021-10-15 绿盟科技集团股份有限公司 一种安全资源池的引流系统及安全检查方法
CN113839824A (zh) * 2020-06-08 2021-12-24 奇安信科技集团股份有限公司 流量审计方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CA2990045A1 (fr) 2017-01-12
CA2990045C (fr) 2021-12-14

Similar Documents

Publication Publication Date Title
US11646964B2 (en) System, apparatus and method for providing a virtual network edge and overlay with virtual control plane
US20230224246A1 (en) System, apparatus and method for providing a virtual network edge and overlay with virtual control plane
US10523593B2 (en) System, apparatus and method for providing a virtual network edge and overlay
US9929964B2 (en) System, apparatus and method for providing aggregation of connections with a secure and trusted virtual network overlay
US11870753B2 (en) System, apparatus and method for providing a unified firewall manager
US10122829B2 (en) System and method for providing a control plane for quality of service
US9264350B2 (en) System, apparatus and method for providing improved performance of aggregated/bonded network connections with multiprotocol label switching
CN110635935B (zh) 为用户接口的相应服务接口使用多个evpn路由
CA2962185C (fr) Systeme, appareil et procede pour offrir des performances ameliorees de connexions reseau agregees/liees a commutation multiprotocole par etiquette
US20180013556A1 (en) System, apparatus and method for encrypting overlay networks using quantum key distribution
KR20110104484A (ko) 멀티-도메인 제공자 이더넷 네트워크 운영 방법
CA2912643A1 (fr) Systeme, appareil et methode de fourniture de limite de reseau virtuel et superposition de reseau virtuel au moyen d'un plan de controle virtuel
AU2014295861B2 (en) System, apparatus and method for providing improved performance of aggregated/bonded network connections between remote sites
CA2990045C (fr) Systeme, appareil, et procede pour la fourniture d'un reseau virtuel edge ou overlay
CA3029862C (fr) Systeme et procede de fourniture de plan de controle pour la qualite de service
CA2863901C (fr) Systeme, appareil et methode destines a fournir un rendement ameliore de connexions reseau regroupees ou liees au moyen de commutation d'etiquette multiprotocole
TW201616834A (zh) 用於利用多協定標籤切換提供經彙總/結合網路連接的改良的效能的系統、裝置及方法

Legal Events

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

Ref document number: 16820584

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2990045

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16820584

Country of ref document: EP

Kind code of ref document: A1