Systems and methods for providing secure network exchanged for a multitenant virtual private cloud

Description

TECHNICAL FIELD

This disclosure relates generally to the communication networking field, and more specifically to new and useful systems and methods for providing secure network exchange for a multitenant virtual private cloud in the communication networking field.

BACKGROUND

Many companies, products, and services use cloud-hosted computing resources during operation. Often times the cloud hosted computing resources are accessed over a public internet connection. However, use cases have legal or business restrictions or objectives that make a public internet connection not viable. In one case, the security of a connection to the cloud-hosted computing resource is not secure when established over the public internet. For example, a voice call from a customer support system may not be permitted to use public internet connections since social security or credit card numbers may be exchanged during a voice call. In another case, the quality of the connection may not be satisfactory. The bandwidth restrictions and/or the uptime of a connection through the public internet connection may not provide the level of service desired by a company. While, cloud-hosted computing resources can use network exchange solutions. There are no solutions that enable a multi-tenant platform as a service product to provide such network exchange solutions. Thus, there is a need in the communication field to create a new and useful system and method for providing a secure network exchange for a multitenant virtual cloud. These embodiments disclosed herein provide such a new and useful system and method.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of a system of a preferred embodiment;

FIG. 2 is a schematic representation of an exemplary configuration interface;

FIG. 3 is a flow diagram representation of a method of a preferred embodiment;

FIGS. 4A-4C are schematic representations of a systems of preferred embodiments;

FIGS. 5A-5D are flow diagram representations of methods of preferred embodiments;

FIG. 6 is an architecture diagram of a Virtual Private Cloud system of a preferred embodiment; and

FIG. 7 is an architecture diagram of a regional exchange system of a preferred embodiment.

DETAILED DESCRIPTION

The following description of preferred embodiments is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.

1. System

As shown in FIG. 1, a system (e.g., 100) for providing a secure network exchange for a multitenant virtual cloud of a preferred embodiment can include a set of regional exchange systems (e.g., 120, 130) that include a set of secure connection interfaces (e.g., VPN, Cross Connect, MPLS), a multitenant platform (e.g., 113) in a virtual private cloud (e.g., 110), and a configuration system (e.g., 112). The system can additionally include a virtualized IP (internet protocol) system. The system functions to enable a multitenant platform (e.g., 113) to offer network exchange functionality to a variety of entities (e.g., Customer A, Customer B, Customer C) using the multitenant platform (e.g., 113). The system is particularly applicable to a multitenant platform as a service product that is hosted in an infrastructure as a service cloud computing product such as Amazon Web Services or other suitable hosting solutions. Current exchange solutions do not address the challenge of offering network exchange capabilities to multiple entities for a platform built in a virtual private cloud (VPC) (e.g., 110). The system can be used by entities (e.g., Customer A, Customer B, Customer C) that require or desire to have a more secure or reliable data link to the multi-tenant platform (e.g., 113). For example, a company building a phone or messaging system that deals with sensitive information such as social security numbers, credit card numbers, bank account numbers, medical health records, and other sensitive information may require a network connection that is secured, where access over public internet routing is not acceptable. In another example, a company building a product that has high performance requirements relating to media quality, bandwidth, uptime, or other communication properties may find basic public internet access to be infeasible.

A set of regional exchange systems (e.g., 120, 130) functions to provide physical collocated networking infrastructure to facilitate establishing secure connections. The set of regional exchange systems (e.g., 120, 130) are preferably regionally distributed in distinct geographic locations. There may be multiple regional exchange systems in the United States and in other regions of the world. There can be any suitable geographic distance between any two regional exchange systems (e.g., 120, 130). One exemplary implementation may have over one hundred or even a thousand miles between different regional exchange systems. For example, the United States may have at least one regional exchange system based in the Western side and a second based in the Eastern side. The regional exchange systems are preferably established in collocated infrastructure environments where direct secured connections can be established to other computing resources accessible at the collocated site. Preferably, an edge computing resource is also established at the collocated site and the outside entity wanting to establish a secure connection can have a physical computing resource presence at the same collocated site. A secured connection can be made between at least one edge computing resource of the multitenant platform (e.g., 113) and a computing resource of the outside entities (e.g., Customer A, Customer B, Customer C).

Preferably, the regional exchange systems include a set of secure connection interface options that include a VPN connection, a cross connect connection, and an MPLS (Multiprotocol Label Switching) connection. The system can provide one or multiple secure connection interface options, which may include the above variations and/or any suitable alternative type of secure connection interface options. The types of secure connection interface options can be uniform in each regional exchange system but may alternatively be different for at least two subsets of regions.

A VPN (Virtual Private Network) connection interface functions to provide a straightforward and possibly faster setup time for a secure connection. The VPN can make the connection over a secured tunnel. The VPN connection interface can provide strong authentication and encrypted (e.g., IPSec) communication across the internet. The VPN can enable a secure connection while still using connectivity via the internet. The VPN connection interface can be used by an outside entity in combination with a physical or virtual router that supports IPSec VPN or other suitable internet security protocol.

A cross connect interface functions to establish a communication connection over a dedicated physical link that could be additionally encrypted. The cross connect interface can utilize a piece of circuit-switched network equipment. The cross connect interface provides a physical link to the multitenant platform, wherein the physical link is dedicated to the traffic of the outside entity. The physical link can be a fiber link, an optical link, or any suitable type of connection link. The cross connect interface can include quality of service controls. The outside entity preferably uses an established gateway presence in at least one of the collocation sites to establish a connection to the regional network exchange system through a cross connect interface. The gateway resources of the outside entity are preferably peered with the cross connect interface of the regional exchange system.

A MPLS connection interface functions to establish a connection via a private carrier network. The MPLS connection interface can be encrypted. The MPLS connection interface puts traffic of the outside entity on a separate virtual network inside a physical private network. The MPLS connection interface can provide quality of service management as part of the MPLS-based private cloud offering used by the outside entity. The MPLS connection interface offers a data-carrying service that directs data from one network node to another based on short path labels, which may avoid complex lookups in a routing table. Various access technologies may be used.

In one embodiment, the set of exchange system includes a set of customer entities leveraging a customer exchange subsystem and a set of service providers used by the multitenant platform using a service exchange subsystem. In a telecommunication platform variation, user entities such as customer care systems, business phone solutions, VoIP products, messaging services may establish secure network connections through a customer exchange subsystem, and voice and messaging carriers may establish secure network connections through a service exchange subsystem.

The multitenant platform (e.g., 113) functions to provide an operational service that involves network connections to a plurality of entities. A multitenant platform can enable multiple accounts to use the platform in facilitating various operations performed by the multitenant platform tasks. Additionally, each account within the multitenant platform may itself have a subaccount. Accordingly, an account may support multiple use-case scenarios for different sub-account holders wherein communication, data/analytics, billing, and/or other aspects can be scoped to an account, a sub-account, or any suitable scope. The multitenant platform preferably is hosted in a virtual private cloud (VPC) (e.g., 110). In other words, the multitenant platform can be built on top of third-party cloud computing resources (e.g., IaaS solutions such as AWS). The multitenant platform (e.g., 113) can be a server, a server cluster, a collection of components on a distributed computing system, or any suitable network accessible computing infrastructure. The multitenant platform (e.g., 113) can be implemented in part through a service-directed architecture wherein different operational responsibilities of the platform can be subdivided between different internal services. Those services can be composed of multiple servers or machine nodes, which can preferably be scaled out horizontally and workload balanced across the set of nodes.

The multitenant platform (e.g., 113) can provide any suitable computing service. In one preferred implementation, the multitenant platform is a communication platform. The communication platform can be designed for one or more mediums of communication. The communication platform may support various forms of communication in addition to the mediums described herein. A communication platform can provide voice communication connectivity (e.g., PSTN, SIP, etc.), messaging (SMS, MMS, IP messaging, etc.), communication business logic, conferencing, broadcasting, data streaming, and/or any suitable communication operations. The communication functions to provide communication services to developer applications and services. Various outside entities can build service and products that can leverage the functionality of the communication platform to perform one or multiple communication tasks. The system is preferably implemented in combination with a communication platform such as the one described in patent application Ser. No. 12/417,630 filed 2 Apr. 2009, entitled “System and Method for Processing Telephony Sessions”, which is hereby incorporated in its entirety by this reference. The communication platform preferably enables application execution in connection to communication sessions and/or messages; the communication platform may additionally or alternatively provide an application programming interface (API) as an alternative for interacting with communication functionality of the communication platform. Herein the multitenant platform is primarily described as being applied to the telecommunication networking space, but the platform may provide any suitable type of computing service such as financial transactions, data warehousing/processing, and/or any suitable computing service.

The multitenant platform of the system is preferably hosted in a virtual private cloud (VPC) (e.g., 110). A VPC can be an on-demand configurable pool of shared computing resources from an IaaS cloud environment. The VPC is preferably a set of resources provisioned from a third-party cloud solution provider to the operator of the multitenant platform. The cloud environment generally does not provide network exchange solutions to address the needs of a multitenant platform operating within their cloud. The system in part addresses the challenges of providing a networking solution when the physical resources are provisioned by another party.

In one implementation, the computing resources within the multitenant platform are preferably operated within two subnets an edge subnet and a private subnet. A subnet is generally a block of contiguous IP addresses. Services and products can be designed so that they configure edge servers within the edge subnet and internal resources operate within the private subnet. The edge subnet includes a set of edge nodes. The edge nodes can be different services or products offered by the multitenant platform. For example, in a telecommunications platform there may be a SIP edge server, a messaging edge server, a video streaming edge server, an IP Client communication edge server, and/or any suitable type of service edge server. The edge nodes are the computing resources exposed to the outside entities connecting through the exchange system. These edge servers are preferably configured for the various services or products to talk to computing resources within the private subnet. The private subnet includes a variety of services that preferably provide the core service functionality.

A routing manager can be used to govern how the hosts in the edge subnet can reach outside entities through the network exchange system. The routing manager can include a network address translation layer. For example, each outside entity can be given particular IP addresses. The routing manager can transparently figure out to which gateway the traffic could be forwarded. The routing manager can additionally address challenges of routing based on geographic region. Traffic may be routed to one of a set of regional exchange systems depending on various factors.

The routing manager or an alternative system can enable virtualized IP settings to provide a level of abstraction between the IP address used by an outside entity and the actual IP of the computing resources.

The system can additionally include a configuration system (e.g., 112), which functions to enable provisioning, deprovisioning, and modifying of network exchange settings for an outside entity. An outside entity that wants to begin using a network exchange can enable such a feature through one of a variety of different interfaces.

One possible configuration interface can include a programmatic interface. More specifically, the programmatic interface is an application programming interface (API). The configuration interface is preferably a RESTful API but may alternatively be any suitable API such as SOAP or custom protocol. The RESTful API works according to an application layer request and response model. An application layer request and response model may use an HTTP-based protocol (HTTP or HTTPS), SPDY, or any suitable application layer protocol. Herein, HTTP may be used, but should not be interpreted as being limited to the HTTP protocol. HTTP requests (or any suitable request communication) to the communication platform preferably observe the principles of a RESTful design. RESTful is understood in this document to describe a Representational State Transfer architecture as is known in the art. The RESTful HTTP requests are preferably stateless, thus each message communicated contains all necessary information for processing the request and generating a response. The API service can include account exchange setting resources, which act resources that can in part define network exchange operation.

The configuration system can be a control portal user interface accessible through a website, an application, or other graphical user interface. An administrator of an account can preferably navigate to the control panel and select an option for adding and configuring one or more network exchanges used by the account as shown in FIG. 2.

The system can additionally include a metering and billing system. The metering subsystem of the preferred embodiment functions to monitor and log activity by an account through a network exchange. The metering and logging system operates in coordination with the system. The metering subsystem can track data activity including throughput, types of service traffic, and other properties of network exchange usage. The metering subsystem can be used in providing programmatic hooks (e.g., callback URI triggering, application execution, and the like), billing/crediting an associated entity (e.g., charging for services or controlling resource access), creation of an audit trail, and/or other suitable functionality.

A billing engine may operate independently of the metering subsystem, but may alternatively be integrated. A billing engine preferably calculates amount owed by a particular account/sub-account. The billing engine can additionally facilitate collecting and distributing of funds as appropriate. Such accounting may be used in billing or crediting an entity/account for metered usage, which functions to allow a sustainable media intelligence platform to be operated. In another variation, usage accountability can be used in limiting and balancing usage of a particular entity. As the platform is preferably multitenant, usage is preferably balanced across multiple entities. Rate limiting and action limits may be imposed at various times. Additionally, as use of a communication infrastructure is often accompanied with significant financial cost, fraudulent behavior by accounts or users of an account can be harmful to users of the platform and to the platform itself. Fraud detection can additionally be accounted for during usage of the platform.

As shown in FIG. 3, a method for configuring network exchange for a multitenant platform in a virtual private cloud can include setting configuration of an account S110, establishing network connection to at least one of a regional exchange systems S120, and routing traffic through the regional exchange system S130.

The method functions to enable a multitenant platform (e.g., 113) to offer network exchange functionality to a variety of entities using the multitenant platform. The method is particularly applicable to a multitenant platform as a service product that is hosted in an infrastructure as a service (IaaS) cloud computing product such as Amazon Web Services or other suitable hosting solutions. Current exchange solutions do not address the challenge of offering network exchange capabilities to multiple entities for a platform built in a virtual private cloud (VPC). The method can be used by entities that require or desire to have a more secure or reliable data link to the multi-tenant platform.

The processes of the method are preferably implemented by multiple entities. In one implementation, the method may be used repeatedly so that multiple end users of the multitenant platform establish independently managed network exchange integrations. For example, the method may be implemented in association with various customers of a telecommunication platform to establish voice or messaging communication through independent, secured network connections for each customer. In another implementation, the method may be used repeatedly so that multiple service providers of the multitenant platform. For example, the method may be implemented with various carrier networks used by a telecommunication platform. The carrier networks may not be end customers but rather resources used in facilitating performing operations on the multitenant platform. In a telecommunication platform, customers and service providers can preferably both use the network exchange.

The method is preferably implemented by a system substantially similar to the one described above (e.g., 100), but any suitable system may be used.

Block S110, which includes setting configuration of an account, functions to define settings for a network exchange of an account. The multitenant platform (e.g., 113) can have a plurality of different accounts. As described above, these accounts may be end user accounts, internal accounts (e.g., used for various outside vendors or service providers), and/or any suitable outside entity. The set of accounts can include a subset of accounts that use the network exchange functionality, but a second subset of accounts may not use the network exchange functionality. An account without a configured network exchange can provision or add a new network exchange option. Setting configuration of a new network exchange can include selecting the type of network exchange, setting account system settings, setting a region, and enrolling the account for the selected type of network exchange. As described above, a variety of network exchange interfaces may be used. The set of possible network exchange interfaces can include a VPN connection, a cross connect connection, and an MPLS connection. Additionally, multiple different network exchange instances can be provisioned. Multiple network exchange instances for one account may provide regional performance enhancements, redundancies, and/or other benefits.

Setting configuration of a VPN can involve receiving or setting authentication credentials (e.g., username and password) and determining the IP address to be used. Cross connect may involve initializing a workflow for signing of a legal document to authorize use of the cross connect. Once confirmed, automated integration instructions can be issued. The integration issues may specify a port number and location to be used in a collocated environment to establish the cross connect integration. In one variation, a wire can be physically plugged in at the appropriate port in the regional exchange system. In another variation, the wires are prepopulated and a routing service configures the router to establish a cross connection between appropriate ports. MPLS may involve establishing a three-way agreement between appropriate entities if the outside entity is in the network. If the entity establishing the network exchange integration is not in the network, then a workflow can be initiated to onboard the entity into the network.

Setting configuration of an account may additionally include updating at least one previously provisioned network exchange instance. An authorized account could update the settings in any suitable manner.

Setting configuration of an account may additionally include deprovisioning a network exchange instance, which functions to deactivate, end, or suspend an accounts usage of a private and secured network integration.

Setting configuration can be performed through a programmatic interface or a user interface.

Block S120, which includes establishing network connection to at least one of a regional exchange systems (e.g., 120, 130), functions to connect the outside computing resources of the account holder (e.g., outside computing resources of Customer A, Customer B, Customer C) to those of the multitenant platform (e.g., 113). The network connection can be established over VPN, a cross connect connection, or an MPLS connection.

Block S130, which includes routing traffic through the regional exchange system, functions to receive and transmit data through the established regional exchange network. Routing traffic can include IP translation, which functions to translate between the public IP address used by a customer and the actual resource IP addressed of the hosts. Routing traffic can additionally include routing between the edge subnet and the private subnet. As mentioned, multiple entities may have a network exchange connection. In some cases, a communication may be established through two or more network exchanges. For example, a phone call may be established from a customer's network exchange and that communication may have at least one leg connected to a carrier through a network exchange of the carrier.

Additionally, the method can include monitoring and responding to usage of the network connection. The usage, amount of traffic, types of services used and/or other activities may be tracked based on individual accounts. The accounts are preferably billed or credited for individual usage.

Systems

FIGS. 4A-C are schematic representations of systems 400a-c in accordance with embodiments. In some embodiments, the systems 400a-c include at least one virtual private cloud (VPC) system 401, and at least one regional exchange system (e.g., 420, 430).

In some embodiments, the VPC system 401 includes at least one virtual private cloud (e.g., VPC 410a-c).

In some embodiments, the VPC system 401 (FIG. 4A) includes a VPC (e.g., 410a, 410b) for each regional exchange system (e.g., 420, 430). In some embodiments, the VPC system 401 (FIG. 4A) includes a VPC (e.g., 410a, 410b) for each regional exchange system (e.g., 420, 430), each regional exchange system is communicatively coupled one VPC (e.g., 410a, 410b), and each regional exchange system is communicatively coupled to a different VPC. In some embodiments, each VPC (e.g., 410a, 410b) that is communicatively coupled to a regional exchange system is not communicatively coupled to the Internet 460. In some embodiments, the VPC system 401 (FIG. 4A) includes a VPC (e.g., 411) that is communicatively coupled to the Internet 460.

In some embodiments, the VPC system 401 (FIG. 4B) includes a VPC (e.g., 410c) for multiple regional exchange systems (e.g., 420, 430).

In some embodiments, the VPCs 410a and 410b of FIG. 4A, and the VPC 410c of FIG. 4B each include a multi-tenant platform system (e.g., 413a-c). In some embodiments, the VPCs 410a-c each include a configuration system (e.g., 412a-c). In some embodiments, the multi-tenant platform systems 413a-c include at least one platform service (e.g., 414a-c).

In some embodiments, the VPC 411 of FIG. 4A includes a multi-tenant platform system, as described herein. In some embodiments, the VPC 411 of FIG. 4A includes a configuration system, as described herein. In some embodiments, the VPC 411 is communicatively coupled to a PSTN network.

In some embodiments, as shown in system 400c of FIG. 4C, the VPCs 410a-b do not include a configuration system, the VPC 411 includes a configuration system 412d (similar to configuration systems 412a-c as described herein), the VPCs 410a and 410b are communicatively coupled to the configuration system 412d of the VPC 411, and the configuration system 412d of the VPC 411 is communicatively coupled to the Internet 460.

In some embodiments, the VPC 410a is communicatively coupled to the VPC 410b.

In some embodiments, the systems 400a and 400b are similar to the system 100 of FIG. 1. In some embodiments, the system 400c is similar to the system 100 of FIG. 1. In some embodiments, the regional exchange system 420 is similar to the regional exchange systems of FIG. 1. In some embodiments, the regional exchange system 430 is similar to the regional exchange systems of FIG. 1. In some embodiments, the configuration systems 412a-d are similar to the configuration system of FIG. 1. In some embodiments, the multi-tenant platform systems 413a-c are similar to the multi-tenant platform system of FIG. 1. In some embodiments, the VPCs 410a-c are similar to the VPC 110 of FIG. 1. In some embodiments, the VPC 411 is similar to the VPC 110 of FIG. 1. In some embodiments, the VPC system 401 is similar to a system of a IaaS cloud environment as described herein for FIG. 1. In some embodiments, the VPC system 401 is similar to a system of a third-party cloud solution provider as described herein for FIG. 1.

In some embodiments, the VPC system 401 is a VPC system of a IaaS (Infrastructure as a Service) provider.

In some embodiments, the VPC system 401 is an Amazon Web Services™ VPC system.

In some embodiments, the VPC 411 is managed by the first entity.

In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) is associated with an account of the PaaS provider of the VPC that is communicatively coupled to the regional exchange system (e.g., 410a-c). In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) uses at least a first service (e.g., 414a-c) of the respective multi-tenant platform system (e.g., 413a-c) provided by the PaaS provider of the VPC (e.g., 410a-c) that is communicatively coupled to the regional exchange system, and each entity system uses the first service (e.g., 414a-c) by communicating with the multi-tenant platform system (e.g., 413a-c) via a respective regional exchange system (e.g., 420, 430).

In some embodiments, the VPCs 410a-c are managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs 410a-c are VPCs of the first VPC account, and the first entity is a SaaS (Software as a Service) provider. In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) is associated with an account of the SaaS provider of the VPC that is communicatively coupled to the regional exchange system (e.g., 410a-c). In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) uses at least a first service provided by the SaaS provider of the VPC that is communicatively coupled to the regional exchange system (e.g., 410a-c), and each entity system uses the first service by communicating with the VPC (that is communicatively coupled to the regional exchange system e.g., 410a-c) via a respective regional exchange system (e.g., 420, 430).

In some embodiments, the multi-tenant platform systems 413a-c are communicatively coupled to a respective configuration system 412a-c. In some embodiments, a multi-tenant platform system (e.g. of the VPC 411) is communicatively coupled to the Internet. In some embodiments, the multi-tenant platform systems 413a-c are communicatively coupled to at least one PSTN network (Public Switched Telephone Network).

In some embodiments, the multi-tenant platform systems are communicatively coupled to one regional exchange system (e.g., 420, 430). In some embodiments, the multi-tenant platform systems are communicatively coupled to one regional exchange system (e.g., 420, 430) via a private network connection. In some embodiments, the multi-tenant platform system 413a is communicatively coupled to regional exchange system 420 via a private network connection. In some embodiments, the multi-tenant platform system 413b is communicatively coupled regional exchange system 430 via a private network connection.

In some embodiments, the multi-tenant platform system 413c is communicatively coupled to regional exchange system 420 via a private network connection. In some embodiments, the multi-tenant platform system 413c is communicatively coupled regional exchange system 430 via a private network connection.

In some embodiments, the private network connection is a VLAN private network connection. In some embodiments, the private network connection is an 802.1Q VLAN private network connection. In some embodiments, the private network connection is an AWS (Amazon Web Services) Direct Connect private network connection.

In some embodiments, the regional exchange system 420 is communicatively coupled to at least one outside entity system (e.g., 441-446) via a private network exchange by using a secure connection interface (e.g., 421-423) of the regional exchange system 420. In some embodiments, the regional exchange system 420 is communicatively coupled to at least one customer outside entity system (e.g., 441-446) via a private network exchange. In some embodiments, the regional exchange system 420 is communicatively coupled to at least one service provider outside entity system (e.g., 441-446) via a private network exchange.

In some embodiments, the regional exchange system 430 is similar to the regional exchange system 420.

In some embodiments, the regional exchange system 430 is communicatively coupled to at least one outside entity system (e.g., 441-446) via a private network exchange by using a secure connection interface (e.g., 431-433) of the regional exchange system 430. In some embodiments, the regional exchange system 430 is communicatively coupled to at least one customer outside entity system (e.g., 441-446) via a private network exchange. In some embodiments, the regional exchange system 430 is communicatively coupled to at least one service provider outside entity system (e.g., 441-446) via a private network exchange.

In some embodiments, each regional exchange system (e.g., 420, 430) includes at least one secure connection interface (e.g., 421-423, 432-433). In some embodiments, each regional exchange system (e.g., 420, 430) includes a VPN secure connection interface (e.g., 421, 431), a cross connect secure connection interface (e.g., 422, 432), and an MPLS secure connection interface (e.g., 423, 433).

In some embodiments, each regional exchange system (e.g., 420, 430) is managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs (e.g., 410a-c) are VPCs of the first VPC account, and the first entity is a PaaS (Platform as a Service) provider. In some embodiments, each regional exchange system (e.g., 420, 430) is managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs (e.g., 410a-c) are VPCs of the first VPC account, and the first entity is a SaaS (Software as a Service) provider.

In some embodiments, each regional exchange system (e.g., 420, 430) is managed by an entity that is different from an entity that manages the VPC system 401. In some embodiments, each regional exchange system (e.g., 420, 430) is managed by a first entity that is an account holder of a VPC account of the VPC system 401, and the VPC system 401 is managed by a second entity that is different from the first entity. In some embodiments, the first entity is a PaaS (Platform as a Service) provider, and the second entity is a IaaS (Infrastructure as a Service) provider. In some embodiments, the first entity is a SaaS (Software as a Service) provider, and the second entity is a IaaS (Infrastructure as a Service) provider.

In some embodiments, each outside entity system (e.g., 441-446) is a router. In some embodiments, at least one outside entity system (e.g., 441-446) is a router. In some embodiments, each outside entity system (e.g., 441-446) is communicatively coupled to a PBX system of the respective entity. In some embodiments, at least one outside entity system (e.g., 441-446) is communicatively coupled to a PBX system of the respective entity. In some embodiments, each PBX system is communicatively coupled to at least one communication client device. In some embodiments, at least one PBX system is communicatively coupled to at least one communication client device.

In some embodiments, each hardware server of the multi-tenant platform systems 413a-c is managed by the VPC system 401. In some embodiments, each hardware server of the configuration systems 412a-d is managed by the VPC system 401. In some embodiments, the VPC system 401 is a hardware system. In some embodiments, the VPC system 401 of FIG. 4A includes at least one hardware server of the VPCs 410a-b and at least one hardware server of a VPC (not shown in FIG. 4A) of an entity different from an entity of the VPCs 410a-b. In some embodiments, the VPC system 401 of FIG. 4B includes at least one hardware server of the VPC 401c and at least one hardware server of a VPC (not shown in FIG. 4B) of an entity different from an entity of the VPC 410c.

In some embodiments, the platform services 414a-c are communication services. In some embodiments, the platform services 414a-c are real-time voice communication services. In some embodiments, the platform services 414a-c are messaging communication services. In some embodiments, the platform services 414a-c are SIP (Session Initiation Protocol) communication services that are constructed to communicate SIP data. In some embodiments, the platform services 414a-c are message communication services that are constructed to communicate asynchronous message data. In some embodiments, the platform services 414a-c are video communication services that are constructed to communicate video data. In some embodiments, the platform services 414a-c are IP Client communication services that are constructed to communicate IP Client communication data. In some embodiments, the platform services 414a-c are WebRTC (Web Real-Time Communication) communication services that are constructed to communicate WebRTC data.

In some embodiments, regional exchange system 420 is external to the VPC system 401 and the entity systems 441-446. In some embodiments, regional exchange system 430 is external to the VPC system 401 and the entity systems 441-446. In some embodiments, the entity systems 441-446 are external to the VPC system 401.

Methods

FIGS. 5A-D are flow diagram representations of methods in accordance with embodiments. In some embodiments, the method 500 is performed by the system 100 of FIG. 1. In some embodiments, the method 500 is performed by the system 400a of FIG. 4A. In some embodiments, the method 500 is performed by the system 400b of FIG. 4B. In some embodiments, the method 500 is performed by the system 400c of FIG. 4C.

In some embodiments, the method 500 includes: setting configuration of a first account (process S510), establishing a first private network exchange between a first regional exchange system (e.g., one of 420 and 430) and a first outside entity system (e.g., on of 441-446) of the first account (process S520); and routing traffic through the regional exchange system (process S530). In some embodiments, setting configuration of a first account (process S510) includes: a virtual private cloud (VPC) system (e.g., 401) receiving first configuration for a first private network exchange for the first account of the VPC system (process S511), and the VPC system assigning the first regional exchange system (e.g., one of 420 and 430) to the first private network exchange based on the first configuration (process S512). In some embodiments, establishing a first private network exchange between a first regional exchange system and a first outside entity system of the first account (process S520) includes mapping an identifier of the first account to the first private network exchange (process S521). In some embodiments, routing traffic through the regional exchange system (process S530) includes routing communication data for the first account from a first service (e.g., 414a-c) of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531).

In some embodiments, the method 500 is similar to the method 300 of FIG. 3. In some embodiments, the process S510 is similar to the process S110 of FIG. 3. In some embodiments, the process S520 is similar to the process S120 of FIG. 3. In some embodiments, the process S530 is similar to the process S130 of FIG. 3.

In some embodiments, the first account is an account of a first multi-tenant platform system (e.g., 413a-c) of a first VPC (e.g., 410a-c) of the VPC system (e.g., 401), and the first service (e.g., 414a-c) is a service of the first multi-tenant platform system. In some embodiments, the first VPC is a VPC of a PaaS provider. In some embodiments, the first VPC is a VPC of a SaaS provider. In some embodiments, an entity of the first account uses a service (e.g., 414a-c) provided by the first multi-tenant platform system (e.g., 413a-c). In some embodiments, an entity of the first multi-tenant platform system (e.g., 413a-c) uses a service provided by the VPC system, and the VPC system and the multi-tenant platform system are managed by different entities.

In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412a-c) of a first VPC (e.g., 410a-c) of the VPC system receiving the first configuration. In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412d) that is communicatively coupled to a first VPC (e.g., 410a-c) of the VPC system receiving the first configuration. In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412a-c) of a first VPC of the VPC system receiving the first configuration and storing the first configuration in the first VPC in association with the first account. In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412d) communicatively coupled to a first VPC of the VPC system receiving the first configuration and storing the first configuration in association with the first account. In some embodiments, the VPC system receiving the first configuration (process S511) includes a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system receiving the first configuration. In some embodiments, a VPC system receiving the first configuration (process S511) includes a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system receiving the first configuration and storing the first configuration in the first VPC in association with the first account.

Private Network Exchange

In some embodiments, the first private network exchange is a layer 2 network exchange in accordance with a layer 2 network protocol.

Process S512: Assigning a Regional Exchange System

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a configuration system (e.g., 412a-c) of a first VPC of the VPC system assigning the first regional exchange system to the first private network exchange.

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a configuration system (e.g., 412d) communicatively coupled to a first VPC of the VPC system assigning the first regional exchange system to the first private network exchange.

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system assigning the first regional exchange system to the first private network exchange. In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a routing manager of a first VPC (e.g., 410a-c) of the VPC system assigning the first regional exchange system to the first private network exchange.

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes: selecting the first regional exchange system from a plurality of regional exchange systems (e.g., 420, 430) based on the first configuration, and the plurality of regional exchange systems are external to the VPC system.

In some embodiments, the first configuration specifies selection of one of a plurality of private network exchange types (e.g., VPN, Cross Connet, MPLS), and the first regional exchange system is selected from a plurality of regional exchange systems (e.g., 420, 430) responsive to a determination that the first regional exchange system includes a secure connection interface (e.g., 421-423) for the private network exchange types specified by the first configuration. In some embodiments, the first private network exchange is a network exchange of the type specified by the first configuration.

In some embodiments, the first configuration specifies a bandwidth, and the first regional exchange system is selected from a plurality of regional exchange systems (e.g., 420, 430) responsive to a determination that the first regional exchange system can provide the bandwidth specified by the first configuration.

In some embodiments, the first configuration specifies a geographic location, and the first regional exchange system is selected from a plurality of regional exchange systems (e.g., 420, 430) responsive to a determination that the first regional exchange system is located in the geographic location specified by the first configuration.

Routing Communication Data

In some embodiments, a routing manager of a first VPC (e.g., 410a-c) of the VPC system routes the communication data based on the mapping. In some embodiments, the first service routes the communication data based on the mapping. In some embodiments, the first regional exchange system routes the communication data based on the mapping.

Services

In some embodiments, the first service (e.g., 414a-c) is a real-time voice communication service and the communication data is real-time voice communication data.

In some embodiments, the first service (e.g., 414a-c) is a real-time voice communication service, and the communication data includes voice call data received by the VPC system from a PSTN device via a PSTN network. In some embodiments, the first account is associated with a phone number of a PSTN network, and communication data for the first account is communication data for the associated phone number.

In some embodiments, the first service (e.g., 414a-c) is a SIP communication service and the communication data is SIP data. In some embodiments, the first account is associated with a SIP endpoint. In some embodiments, the first account is associated with a SIP endpoint, and communication data for the first account is communication data for the associated SIP endpoint.

In some embodiments, the first service (e.g., 414a-c) is a WebRTC communication service and the communication data is WebRTC data. In some embodiments, the first account is associated with a WebRTC endpoint. In some embodiments, the first account is associated with a WebRTC endpoint, and communication data for the first account is communication data for the associated WebRTC endpoint.

In some embodiments, the first service (e.g., 414a-c) is a messaging communication service and the communication data is messaging communication data.

In some embodiments, the first account is associated with a messaging endpoint.

In some embodiments, the VPC system 401 maps the identifier of the first account to the first private network exchange. In some embodiments, the configuration system (e.g., 412a-d) maps the identifier of the first account to the first private network exchange. In some embodiments, the platform system (e.g., 413a-c) maps the identifier of the first account to the first private network exchange. In some embodiments, a routing manager of the VPC (e.g., 410a-c) maps the identifier of the first account to the first private network exchange.

Mapping the Account Identifier to the Private Network Exchange

In some embodiments, the first regional exchange system (e.g., 420, 430) maps the identifier of the first account to the first private network exchange. In some embodiments, the first regional exchange system receives the identifier of the first account and maps the received identifier to the first private network exchange. In some embodiments, the first regional exchange system receives the identifier of the first account from the VPC system (e.g., 401). In some embodiments, the first regional exchange system receives the identifier of the first account from a first VPC (e.g., 410a-c) of the VPC system (e.g., 401). In some embodiments, a configuration system (e.g., 412a-c) of a first VPC (e.g., 410a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, a configuration system (e.g., 412d) communicatively coupled to a first VPC (e.g., 410a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, a routing manager of a first VPC (e.g., 410a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, a multi-tenant platform system (e.g., 413a-c) of a first VPC (e.g., 410a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, the first regional exchange system receives the identifier of the first account from an outside system of the first account.

In some embodiments, the first regional exchange system establishes the first private network exchange between the first regional exchange system and the first outside entity system. In some embodiments, the first regional exchange system advertises a network route for the established first private network exchange to the VPC that is communicatively coupled to the first regional exchange system.

In some embodiments, the identifier of the first account is an IP address assigned to the first account for the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning an IP address within a subnet of the first regional exchange system to the first private network exchange. In some embodiments, assigning the first regional exchange system (process S512) includes assigning an IP address within a subnet of the first regional exchange system to the first private network exchange, and the identifier of the first account is the IP address assigned to the first private network exchange, and the first private network exchange is associated with the first account.

In some embodiments, assigning the first regional exchange system (process S512) includes a routing manager of a first VPC (e.g., 410a-c) of the VPC system assigning an IP address within a subnet of the first regional exchange system to the first private network exchange, and the identifier of the first account is the IP address assigned to the first private network exchange, and the first private network exchange is associated with the first account.

In some embodiments, assigning the first regional exchange system (process S512) includes a configuration system (e.g., 413a-c) of a first VPC (e.g., 410a-c) of the VPC system assigning an IP address within a subnet of the first regional exchange system to the first private network exchange, and the identifier of the first account is the IP address assigned to the first private network exchange, and the first private network exchange is associated with the first account.

In some embodiments, the identifier for the first account is associated with the first account at the VPC system 401. In some embodiments, the identifier for the first account is associated with the first account at the configuration system (e.g., 412a-d). In some embodiments, the identifier for the first account is associated with the first account at platform system (e.g., 413a-c). In some embodiments, the identifier for the first account is associated with the first account at a routing manager of the VPC (e.g., 410a-c).

In some embodiments, the identifier for the first account is associated with the first private network exchange at the first regional exchange system (e.g., 420, 430). In some embodiments, the first account is an account of a customer entity, and the first outside entity system (e.g., one of 441-446) is a customer system.

In some embodiments, the first account is an account of a service provider, and the first outside entity system (e.g., one of 441-446) is a service provider system. In some embodiments, the service provider system provides PSTN communication data that includes voice call data received by the service provider system from a PSTN device via a PSTN network, and the service provider system provides PSTN communication data to the VPC system via the first private network exchange. In some embodiments, the service provider system provides SIP communication data that includes voice call data received by the service provider system from a SIP device, and the service provider system provides SIP communication data to the VPC system via the first private network exchange. In some embodiments, the service provider system provides WebRTC communication data that includes voice call data received by the service provider system from a WebRTC device, and the service provider system provides WebRTC communication data to the VPC system via the first private network exchange.

In some embodiments, the service provider system provides asynchronous message communication data that includes message data received by the service provider system from a messaging client device, and the service provider system provides message communication data to the VPC system via the first private network exchange.

Sub-Accounts

In some embodiments, the first account is a first sub-account of a first entity, a second private network exchange is configured for a second sub-account of the first entity, and the second private network exchange is a network exchange for communication between the VPC system and a second outside entity system of the first entity.

Multi-Tenancy

In some embodiments, the first account is an account of a first VPC (e.g., 410a-c) of the VPC system (e.g., 401). A second private network exchange is configured for a second account of the first VPC (e.g., 410a-c), and the second account is associated with a second outside entity that uses a service of the first VPC. The second private network exchange is a network exchange for communication between the VPC system (e.g., 401) and a second outside entity system of the second entity.

Configuration

In some embodiments, the VPC system receives the first configuration via a public Internet connection.

In some embodiments, the first configuration is received from a system of an account holder of the first account via one of a programmatic interface and a graphical user interface, and the first configuration is stored in association with the first account at the VPC system. In some embodiments, the first configuration is received by a configuration system (e.g., 412a-c), of a first VPC of the VPC system, from a system of an account holder of the first account via one of a programmatic interface and a graphical user interface, and the first configuration is stored in association with the first account at the first VPC. In some embodiments, the first configuration is received by a configuration system (e.g., 412d), communicatively coupled to a first VPC of the VPC system, from a system of an account holder of the first account via one of a programmatic interface and a graphical user interface, and the first configuration is stored in association with the first account.

In some embodiments, a configuration system (e.g., 412a-c), of a first VPC of the VPC system, receives the first configuration from a system of an account holder of the first account via a public Internet interface, and the configuration system receives second configuration for a second account from a system of an account holder of the second account via the public Internet interface.

In some embodiments, a configuration system (e.g., 412d), communicatively coupled to a first VPC of the VPC system, receives the first configuration from a system of an account holder of the first account via a public Internet interface, and the configuration system receives second configuration for a second account from a system of an account holder of the second account via the public Internet interface.

Communication Between the VPC System and Regional Exchange Systems

In some embodiments, the VPC system and the first regional exchange system (e.g., 420) communicate via a private network connection. In some embodiments, the private network connection is a VLAN private network connection. In some embodiments, the private network connection is an 802.1Q VLAN private network connection. In some embodiments, the private network connection is an AWS (Amazon Web Services) Direct Connect private network connection.

Process S531: Routing Communication Data to the Outside Entity System

In some embodiments, routing communication data for the first account from a first service of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531) includes: the VPC system providing the communication data to the first regional exchange system via the private network connection between the VPC system and the first regional exchange system, the first regional exchange system determining that the first private network connection is to be used for the communication data, and providing the received communication data to the first outside entity system via the determined first private network exchange. In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based on the mapping performed at the process S521.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a destination IP address of the communication data. In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a destination IP address of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a source IP address of the communication data. In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a source IP address of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a destination communication endpoint identifier specified by the communication data.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a destination communication endpoint identifier of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a source communication endpoint identifier specified by the communication data.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a source communication endpoint identifier of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system uses an edge computing resource of the first regional exchange system to identify a destination communication endpoint identifier specified by the communication data, and the first regional exchange system determines that the first private network connection is to be used for the communication data based the identified destination communication endpoint identifier.

In some embodiments, the first regional exchange system uses an edge computing resource of the first regional exchange system to identify a source communication endpoint identifier specified by the communication data, and the first regional exchange system determines that the first private network connection is to be used for the communication data based the identified source communication endpoint identifier.

In some embodiments, the communication data is SIP data, the edge computing resource includes a SIP edge server, and the destination communication endpoint identifier is specified by a SIP “To” header of the SIP data.

In some embodiments, the communication data is SIP data, the edge computing resource includes a SIP edge server, and the source communication endpoint identifier is specified by a SIP “From” header of the SIP data.

In some embodiments, the communication data is WebRTC data, and the edge computing resource includes a WebRTC edge server.

In some embodiments, the communication data is WebRTC data, the edge computing resource includes a WebRTC edge server, and the source communication endpoint identifier is specified by a SIP “From” header of the WebRTC data.

In some embodiments, the communication data is WebRTC data, the edge computing resource includes a WebRTC edge server, and the destination communication endpoint identifier is specified by a SIP “To” header of the WebRTC data.

In some embodiments, the communication data is IP Client communication data, and the edge computing resource includes a IP Client communication server.

In some embodiments, the communication data is video data, and the edge computing resource includes a video streaming server.

In some embodiments, the communication data is asynchronous message data, and the edge computing resource includes a messaging server.

Authorization for Communication Via Private Network Exchange

In some embodiments, routing communication data for the first account from a first service (e.g., 414a-c) of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531) includes: the VPC system providing the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412d) communicatively coupled to a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, routing communication data for the first account from a first service (e.g., 414a-c) of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531) includes: the VPC system providing the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412d) communicatively coupled to a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, the VPC system identifies the destination endpoint by using the first service. In some embodiments, the VPC system identifies the source endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412a-c) of a first VPC of the VPC system identifies the destination endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412a-c) of a first VPC of the VPC system identifies the source endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412d) communicatively coupled to a first VPC of the VPC system identifies the destination endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412d) communicatively coupled to a first VPC of the VPC system identifies the source endpoint by using the first service.

In some embodiments, a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system identifies the destination endpoint by using the first service.

In some embodiments, a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system identifies the source endpoint by using the first service.

In some embodiments, the communication data is SIP data, the first service a SIP service, and the destination communication endpoint identifier is specified by a SIP “To” header of the SIP data.

In some embodiments, the communication data is SIP data, the first service a SIP service, and the source communication endpoint identifier is specified by a SIP “From” header of the SIP data.

In some embodiments, the communication data is WebRTC data, the first service a WebRTC service, and the destination communication endpoint identifier is specified by a SIP “To” header of the WebRTC data.

In some embodiments, the communication data is WebRTC data, the first service a WebRTC service, and the source communication endpoint identifier is specified by a SIP “From” header of the WebRTC data.

Information Identifying an Account

In some embodiments, communication data routed from the first outside entity system to the first service via the regional exchange system includes information identifying the first account. In some embodiments, the information identifying the first account is an IP address. In some embodiments, the information identifying the first account is a communication endpoint identifier.

Routing Communication Data from an Entity System to the VPC System

In some embodiments, routing traffic through the regional exchange system (process S530) includes: routing communication data for the first account from the first outside entity system to the first service of the VPC system via the first private network exchange by performing IP translation between a public IP address of the first service used by the first outside entity system and a private IP address of the first service used within the VPC system.

In some embodiments, a first VPC (e.g., 410a-c) of the VPC system assigns a first private IP address of the first VPC to the first service, the first regional exchange system maps a first public IP address of the first regional exchange system to the first private IP address of the first service, assigns the first public IP address to the first account, and communication data for the first account received by the first regional exchange system from the first outside entity system specifies the first public IP address as a destination IP address. In some embodiments, the first regional exchange system performs IP address translation by replacing the first public IP address of the communication data received from the first outside entity system with the first private IP address, and providing the communication data with the first private IP address to the first service at the VPC system.

In some embodiments, communication data for the first account received by the first regional exchange system from the first service specifies the first private IP address as a source IP address, and the first regional exchange system performs IP address translation by replacing the first private IP address of the communication data received from the first service with the first public IP address, and providing the communication data with the first public IP address to the first outside entity system.

In some embodiments, the first VPC (e.g., 410a-c) of the VPC system updates the first service by assigning a second private IP address of the first VPC to the first service, the first VPC provides the second private IP address of the updated first service to the first regional exchange system, and the first regional exchange system updates the mapping for the first public IP address of the first service with the second private IP address. In some embodiments, the first regional exchange system updates the mapping for the first public IP address by replacing the mapping of the first private IP address to the first public IP address with a mapping of the second private IP address to the first public IP address.

In some embodiments, a routing manager of the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, a configuration system (e.g., 412a-c) of the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, a configuration system (e.g., 412d) communicatively coupled to the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, a multi-tenant platform system (e.g., 413a-c) of the first VPC updates the first service and provides the second private IP address to the first regional exchange system.

In some embodiments, a multi-tenant platform system (e.g., 413a-c) of the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, an orchestration system of the first VPC updates the first service and provides the second private IP address to the first regional exchange system.

Voice Communication

In some embodiments, a first communication domain is associated with the first account and the first communication domain includes a set of communication endpoint identifiers.

In some embodiments, a multi-tenant platform system (e.g. 413a-c) of a first VPC of the VPC system maps a communication domain (that includes a set of communication endpoints) of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, and a multi-tenant platform system (e.g. 413a-c) of a first VPC of the VPC system maps a communication domain of the first account to the first IP address assigned to the first private network exchange. In some embodiments, communication data received at the multi-tenant platform system that specifies a destination communication endpoint identifier that is included in the communication domain of the first account is provided to the first outside entity system via the first private network exchange.

SIP Communication

In some embodiments, the communication data is SIP data, the first service a SIP service, and a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system maps a SIP domain of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, the communication data is SIP data, the first service a SIP service, and a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system maps a SIP domain of the first account to the first IP address assigned to the first private network exchange. In some embodiments, SIP communication data received at the multi-tenant platform system that specifies a destination SIP endpoint identifier that is included in the SIP domain of the first account is provided to the first outside entity system via the first private network exchange.

WebRTC Communication

In some embodiments, the communication data is WebRTC data, the first service a WebRTC service, and a multi-tenant platform system (e.g. 413a-c) of a first VPC of the VPC system maps a SIP domain (for WebRTC communication) of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, the communication data is WebRTC data, the first service a WebRTC service, and a multi-tenant platform system (e.g. 413) of a first VPC of the VPC system maps a SIP domain (for WebRTC communication) of the first account to the first IP address assigned to the first private network exchange. In some embodiments, WebRTC communication data received at the multi-tenant platform system that specifies a destination SIP endpoint identifier that is included in the SIP domain of the first account is provided to the first outside entity system via the first private network exchange.

Messaging Communication

In some embodiments, the communication data is asynchronous message data, the first service a messaging service, and a multi-tenant platform system (e.g. 413a-c) of a first VPC of the VPC system maps a messaging domain (that includes messaging communication endpoint identifiers) of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, the communication data is asynchronous message data, the first service a messaging service, and a multi-tenant platform system (e.g., 413a-c) of a first VPC of the VPC system maps a messaging domain of the first account to the first IP address assigned to the first private network exchange. In some embodiments, asynchronous message communication data received at the multi-tenant platform system that specifies a destination messaging endpoint identifier that is included in the messaging domain of the first account is provided to the first outside entity system via the first private network exchange.

System Architecture: VPC System

FIG. 6 is a diagram depicting system architecture of a VPC system, according to embodiments. FIG. 6 is an architecture diagram of a VPC system (e.g., VPC system 401 of FIG. 4) according to an embodiment in which the VPC system is implemented by a server device. In some embodiments, the VPC system is implemented by a plurality of devices.

In some embodiments, the VPC system is implemented by a server device that includes machine-executable instructions (and related data) for the VPCs 410a-b and 411.

In some embodiments, the VPC system is implemented by a plurality of devices, and the plurality of devices include machine-executable instructions (and related data) for the VPCs 410a-b and 411.

In some embodiments, the VPC system is implemented by at least one server device that includes machine-executable instructions (and related data) for a plurality of VPCs including the VPCs 410a-b and 411, and at least two of the plurality of VPCs are VPCs of different entities having different VPC accounts at the VPC system.

In some embodiments, the VPC system is an Amazon Web Services™ VPC system.

In some embodiments, the bus 601 interfaces with the processors 601A-601N, the main memory (e.g., a random access memory (RAM)) 622, a read only memory (ROM) 604, a processor-readable storage medium 605, and a network device 611. In some embodiments, the platform system includes at least one of a display device and a user input device.

In some embodiments, the processors 601A-601N may take many forms, such as ARM processors, X86 processors, and the like.

In some embodiments, the VPC system includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).

In some embodiments, the processors 601A-601N and the main memory 622 form a processing unit 699. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more VPCs (e.g., 410a-b, 411).

In some embodiments, the network device 611 provides one or more wired or wireless interfaces for exchanging data and commands between the VPC system and other devices, such as a regional exchange system (e.g., 420, 430), a device communicatively coupled to the VPC system via the Internet, and a device communicatively coupled to the VPC system via a PSTN network. Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, an optical interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.

Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 622 (of the processing unit 699) from the processor-readable storage medium 605, the ROM 604 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 601A-601N (of the processing unit 699) via the bus 601, and then executed by at least one of processors 601A-601N. Data used by the software programs are also stored in the memory 622, and such data is accessed by at least one of processors 601A-601N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 605 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. In some embodiments, the processor-readable storage medium 605 includes machine-executable instructions (and related data) for an operating system 612, software programs 613, device drivers 614, the VPCs 410a-b and 411.

System Architecture: Regional Exchange System

FIG. 7 is a diagram depicting system architecture of a regional exchange system, according to embodiments. FIG. 7 is an architecture diagram of a regional exchange system (e.g., regional exchange system 420 of FIGS. 4A-C) according to an embodiment in which the regional exchange system is implemented by a server device. In some embodiments, the regional exchange system is implemented by a plurality of devices.

In some embodiments, the regional exchange system is implemented by a server device that includes machine-executable instructions (and related data) for the VPN interface 421, the cross connect interface 422, and the MPLS interface 423.

In some embodiments, the regional exchange system is implemented by a plurality of devices, and the plurality of devices include machine-executable instructions (and related data) for the VPN interface 421, the cross connect interface 422, and the MPLS interface 423.

The bus 701 interfaces with the processors 701A-701N, the main memory (e.g., a random access memory (RAM)) 722, a read only memory (ROM) 704, a processor-readable storage medium 705, and a network device 711. In some embodiments, the regional exchange system includes at least one of a display device and a user input device.

The processors 701A-701N may take many forms, such as ARM processors, X86 processors, and the like.

In some embodiments, the regional exchange system includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).

The processors 701A-701N and the main memory 722 form a processing unit 799. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more of a VPN interface (e.g., 421), a cross connect interface (e.g., 422), and a MPLS interface (e.g., 423).

The network device 711 provides one or more wired or wireless interfaces for exchanging data and commands between the regional exchange system and other devices, such as a VPC system (e.g., 401 of FIG. 4) and an entity system (e.g., 441-446 of FIG. 4). Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, an optical interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.

Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 722 (of the processing unit 799) from the processor-readable storage medium 705, the ROM 704 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 701A-701N (of the processing unit 799) via the bus 701, and then executed by at least one of processors 701A-701N. Data used by the software programs are also stored in the memory 722, and such data is accessed by at least one of processors 701A-701N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 705 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. In some embodiments, the processor-readable storage medium 705 includes machine-executable instructions (and related data) for an operating system 712, software programs 713, device drivers 714, the VPC interface 421, the cross connect interface 422, and the MPLS interface 423.

Machines

The systems and methods of the preferred embodiments and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.

CONCLUSION

As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments without departing from the scope of this invention defined in the following claims.

Claims

1. A method comprising: providing, by a service provider, a multitenant platform inside a cloud computing service delivered by a cloud solution provider that is different from the service provider, the cloud computing service delivering computing services to a plurality of users, the multitenant platform providing network exchange functionality to the plurality of users;establishing, by the service provider, a network connection from the multitenant platform to a regional exchange system of the service provider at a first location, the regional exchange system providing a plurality of private network exchange interfaces for connecting users to the multitenant platform through the regional exchange system, each network exchange interface providing a different type of network connection with a different communications protocol, wherein the plurality of private network exchange interfaces at the regional exchange system includes a virtual private network (VPN) connection, a cross connect connection, and a multiprotocol label switching (MPLS) connection;configuring, by the service provider, the regional exchange system to provide secure network communications, for a first user from the plurality of users, to communicate with the cloud computing service through one of the plurality of private network exchange interfaces of the regional exchange system; anddelivering, via the service provider, the secure network communications for the first user using the configured regional exchange system.
2. The method as recited in claim 1, wherein the multitenant platform and the regional exchange system are managed by the service provider and the cloud computing service is managed by the cloud solution provider.
3. The method as recited in claim 1, further comprising: providing a user interface for adding and configuring one from the plurality of private network exchanges at the regional exchange system for connecting devices of the first user to the regional exchange system.
4. The method as recited in claim 1, wherein the regional exchange system provides physical collocated networking infrastructure for the plurality of private network exchange interfaces to facilitate the secure network communications.
5. The method as recited in claim 1, wherein delivering the secure network communications includes: routing real-time voice communication data for the first user through the regional exchange system and through a real-time voice communication service of the multitenant platform inside the cloud computing service.
6. The method as recited in claim 1, wherein the multitenant platform is a communication platform that provides voice communication connectivity, messaging, conferencing, broadcasting, and data streaming.
7. The method as recited in claim 1, wherein the cloud computing service is a virtual private cloud (VPC) with resources provisioned from a third-party cloud solution provider.
8. The method as recited in claim 1, wherein delivering the secure network communications for the first user comprises: providing real-time voice communication data to the regional exchange system responsive to a determination that a destination endpoint is authorized to receive the real-time voice communication data via the regional exchange system; andproviding the real-time voice communication data to the regional exchange system responsive to a determination that a source endpoint identified by the real-time voice communication data is authorized to provide the real-time voice communication data via the regional exchange system.
9. The method as recited in claim 1, wherein configuring one or more regional exchange systems includes determining an internet protocol (IP) address for the secure network communications.
10. A system comprising: a multitenant platform of a service provider, the multitenant platform executing on a first computer processor and situated at a cloud computing service of a cloud solution provider that delivers computing services to a plurality of users, the cloud solution provider being different from the service provider, the multitenant platform providing network exchange functionality to the plurality of users; anda regional exchange system, of the service provider at a first location and executing on a second computer processor, configured for establishing a network connection to the multitenant platform, the regional exchange system providing a plurality of private network exchange interfaces for connecting users to the multitenant platform through the regional exchange system, each network exchange interface providing a different type of network connection with a different communications protocol, wherein the plurality of private network exchange interfaces at the regional exchange system includes a virtual private network (VPN) connection, a cross connect connection, and a multiprotocol label switching (MPLS) connection, wherein the regional exchange system is configurable to provide secure network communications, for a first user from the plurality of users, to communicate with the cloud computing service through one of the plurality of private network exchange interfaces of the regional exchange system, wherein the regional exchange system and the multitenant platform deliver the secure network communications for the first user utilizing the cloud computing service.
11. The system as recited in claim 10, wherein the multitenant platform and the regional exchange system are managed by the service provider and the cloud computing service is managed by the cloud solution provider.
12. The system as recited in claim 10, wherein the multitenant platform provides a user interface for adding and configuring one from the plurality of private network exchanges at the regional exchange system for connecting devices of the first user to the regional exchange system.
13. The system as recited in claim 10, wherein the regional exchange system provides physical collocated networking infrastructure for the plurality of private network exchange interfaces to facilitate the secure network communications.
14. The system as recited in claim 10, wherein delivering the secure network communications includes routing real-time voice communication data for the first user through the regional exchange system and through a real-time voice communication service of the multitenant platform.
15. A non-transitory machine-readable storage medium including instructions that, when executed by a machine, cause the machine to perform operations comprising: providing, by a service provider, a multitenant platform inside a cloud computing service delivered by a cloud solution provider that is different from the service provider, the cloud computing service delivering computing services to a plurality of users, the multitenant platform providing network exchange functionality to the plurality of users;establishing, by the service provider, a network connection from the multitenant platform to a regional exchange system of the service provider at a first location, the regional exchange system providing a plurality of private network exchange interfaces for connecting users to the multitenant platform through the regional exchange system, each network exchange interface providing a different type of network connection with a different communications protocol, wherein the plurality of private network exchange interfaces at the regional exchange system includes a virtual private network (VPN) connection, a cross connect connection, and a multiprotocol label switching (MPLS) connection;configuring, by the service provider, the regional exchange system to provide secure network communications, for a first user from the plurality of users, to communicate with the cloud computing service through one of the plurality of private network exchange interfaces of the regional exchange system; anddelivering, via the service provider, the secure network communications for the first user using the configured regional exchange system.
16. The non-transitory machine-readable storage medium as recited in claim 15, wherein the multitenant platform and the regional exchange system are managed by the service provider and the cloud computing service is managed by the cloud solution provider.
17. The non-transitory machine-readable storage medium as recited in claim 15, wherein the machine further performs operations comprising: providing a user interface for adding and configuring one from the plurality of private network exchanges at the regional exchange system for connecting devices of the first user to the regional exchange system.
18. The non-transitory machine-readable storage medium as recited in claim 15, wherein the regional exchange system provides physical collocated networking infrastructure for the plurality of private network exchange interfaces to facilitate the secure network communications.
19. The non-transitory machine-readable storage medium as recited in claim 15, wherein delivering the secure network communications includes: routing real-time voice communication data for the first user through the regional exchange system and through a real-time voice communication service of the multitenant platform inside the cloud computing service.

CLAIM OF PRIORITY

This application is a Continuation application under 35 USC § 120 of U.S. patent application Ser. No. 15/425,934, entitled “Systems and Methods for Providing Secure Network Exchanged for a Multitenant Virtual Private Cloud,” filed on Feb. 6, 2017, which claims the benefit of U.S. Provisional Application No. 62/291,327, filed on Feb. 4, 2016, all of which are incorporated herein by reference.

US Referenced Citations (769)

Number	Name	Date	Kind
5274700	Gechter et al.	Dec 1993	A
5526416	Dezonno et al.	Jun 1996	A
5581608	Jreij et al.	Dec 1996	A
5598457	Foladare et al.	Jan 1997	A
5867495	Elliott et al.	Feb 1999	A
5934181	Adamczewski	Aug 1999	A
5978465	Corduroy et al.	Nov 1999	A
6026440	Shrader et al.	Feb 2000	A
6034946	Roginsky et al.	Mar 2000	A
6094681	Shaffer et al.	Jul 2000	A
6138143	Gigliotti et al.	Oct 2000	A
6185565	Meubus et al.	Feb 2001	B1
6192123	Grunsted et al.	Feb 2001	B1
6206564	Adamczewski	Mar 2001	B1
6223287	Douglas et al.	Apr 2001	B1
6232979	Shochet	May 2001	B1
6269336	Ladd et al.	Jul 2001	B1
6317137	Rosasco	Nov 2001	B1
6363065	Thornton et al.	Mar 2002	B1
6373836	Deryugin et al.	Apr 2002	B1
6425012	Trovato et al.	Jul 2002	B1
6426995	Kim et al.	Jul 2002	B1
6430175	Echols et al.	Aug 2002	B1
6434528	Sanders	Aug 2002	B1
6445694	Swartz	Sep 2002	B1
6445776	Shank et al.	Sep 2002	B1
6459913	Cloutier	Oct 2002	B2
6463414	Su et al.	Oct 2002	B1
6493558	Bernhart et al.	Dec 2002	B1
6496500	Nance et al.	Dec 2002	B2
6501739	Cohen	Dec 2002	B1
6501832	Saylor et al.	Dec 2002	B1
6507875	Mellen-Garnett et al.	Jan 2003	B1
6571245	Huang et al.	May 2003	B2
6574216	Farris et al.	Jun 2003	B1
6577721	Vainio et al.	Jun 2003	B1
6600736	Ball et al.	Jul 2003	B1
6606596	Zirngibl et al.	Aug 2003	B1
6614783	Sonesh et al.	Sep 2003	B1
6625258	Ram et al.	Sep 2003	B1
6625576	Kochanski et al.	Sep 2003	B2
6636504	Albers et al.	Oct 2003	B1
6662231	Drosset et al.	Dec 2003	B1
6704785	Koo et al.	Mar 2004	B1
6707889	Saylor et al.	Mar 2004	B1
6711129	Bauer et al.	Mar 2004	B1
6711249	Weissman et al.	Mar 2004	B2
6738738	Henton	May 2004	B2
6757365	Bogard	Jun 2004	B1
6765997	Zirngibl et al.	Jul 2004	B1
6768788	Langseth et al.	Jul 2004	B1
6771955	Imura et al.	Aug 2004	B2
6778653	Kallas et al.	Aug 2004	B1
6785266	Swartz	Aug 2004	B2
6788768	Saylor et al.	Sep 2004	B1
6792086	Saylor et al.	Sep 2004	B1
6792093	Barak et al.	Sep 2004	B2
6798867	Zirngibl et al.	Sep 2004	B1
6807529	Johnson et al.	Oct 2004	B2
6807574	Partovi et al.	Oct 2004	B1
6819667	Brusilovsky et al.	Nov 2004	B1
6820260	Flockhart et al.	Nov 2004	B1
6829334	Zirngibl et al.	Dec 2004	B1
6831966	Tegan et al.	Dec 2004	B1
6834265	Balasuriya	Dec 2004	B2
6836537	Zirngibl et al.	Dec 2004	B1
6842767	Partovi et al.	Jan 2005	B1
6850603	Eberle et al.	Feb 2005	B1
6870830	Schuster et al.	Mar 2005	B1
6873952	Bailey et al.	Mar 2005	B1
6874084	Dobner et al.	Mar 2005	B1
6885737	Gao et al.	Apr 2005	B1
6888929	Saylor et al.	May 2005	B1
6895084	Saylor et al.	May 2005	B1
6898567	Balasuriya	May 2005	B2
6912581	Johnson et al.	Jun 2005	B2
6922411	Taylor	Jul 2005	B1
6928469	Duursma et al.	Aug 2005	B1
6931405	El-shimi et al.	Aug 2005	B2
6937699	Schuster et al.	Aug 2005	B1
6940953	Eberle et al.	Sep 2005	B1
6941268	Porter et al.	Sep 2005	B2
6947417	Laursen et al.	Sep 2005	B2
6947988	Saleh et al.	Sep 2005	B1
6961330	Cattan et al.	Nov 2005	B1
6964012	Zirngibl et al.	Nov 2005	B1
6970915	Partovi et al.	Nov 2005	B1
6977992	Zirngibl et al.	Dec 2005	B2
6981041	Araujo et al.	Dec 2005	B2
6985862	Strom et al.	Jan 2006	B2
6999576	Sacra	Feb 2006	B2
7003464	Ferrans et al.	Feb 2006	B2
7006606	Cohen et al.	Feb 2006	B1
7010586	Allavarpu et al.	Mar 2006	B1
7020685	Chen et al.	Mar 2006	B1
7039165	Saylor et al.	May 2006	B1
7058042	Bontempi et al.	Jun 2006	B2
7062709	Cheung	Jun 2006	B2
7065637	Nanja	Jun 2006	B1
7076037	Gonen et al.	Jul 2006	B1
7076428	Anastasakos et al.	Jul 2006	B2
7089310	Ellerman et al.	Aug 2006	B1
7103003	Brueckheimer et al.	Sep 2006	B2
7103171	Annadata et al.	Sep 2006	B1
7106844	Holland	Sep 2006	B1
7111163	Haney	Sep 2006	B1
7136932	Schneider	Nov 2006	B1
7140004	Kunins et al.	Nov 2006	B1
7143039	Stifelman et al.	Nov 2006	B1
7197331	Anastasakos et al.	Mar 2007	B2
7197461	Eberle et al.	Mar 2007	B1
7197462	Takagi et al.	Mar 2007	B2
7197544	Wang et al.	Mar 2007	B2
7225232	Elberse	May 2007	B2
7227849	Rasanen	Jun 2007	B1
7245611	Narasimhan et al.	Jul 2007	B2
7260208	Cavalcanti	Aug 2007	B2
7266181	Zirngibl et al.	Sep 2007	B1
7269557	Bailey et al.	Sep 2007	B1
7272212	Eberle et al.	Sep 2007	B2
7272564	Phillips et al.	Sep 2007	B2
7277851	Henton	Oct 2007	B1
7283515	Fowler	Oct 2007	B2
7286521	Jackson et al.	Oct 2007	B1
7287248	Adeeb	Oct 2007	B1
7289453	Riedel et al.	Oct 2007	B2
7296739	Mo et al.	Nov 2007	B1
7298732	Cho	Nov 2007	B2
7298834	Homeier et al.	Nov 2007	B1
7308085	Weissman	Dec 2007	B2
7308408	Stifelman et al.	Dec 2007	B1
7324633	Gao et al.	Jan 2008	B2
7324942	Mahowald et al.	Jan 2008	B1
7328263	Sadjadi	Feb 2008	B1
7330463	Bradd et al.	Feb 2008	B1
7330890	Partovi et al.	Feb 2008	B1
7340040	Saylor et al.	Mar 2008	B1
7349714	Lee et al.	Mar 2008	B2
7369865	Gabriel et al.	May 2008	B2
7370329	Kumar et al.	May 2008	B2
7373660	Guichard et al.	May 2008	B1
7376223	Taylor et al.	May 2008	B2
7376586	Partovi et al.	May 2008	B1
7376733	Connelly et al.	May 2008	B2
7376740	Porter et al.	May 2008	B1
7412525	Cafarella et al.	Aug 2008	B2
7418090	Reding et al.	Aug 2008	B2
7428302	Zirngibl et al.	Sep 2008	B2
7440898	Eberle et al.	Oct 2008	B1
7447299	Partovi et al.	Nov 2008	B1
7454459	Kapoor et al.	Nov 2008	B1
7457249	Baldwin et al.	Nov 2008	B2
7457397	Saylor et al.	Nov 2008	B1
7467227	Nguyen	Dec 2008	B1
7473872	Takimoto	Jan 2009	B2
7486780	Zirngibl et al.	Feb 2009	B2
7496054	Taylor	Feb 2009	B2
7496188	Saha et al.	Feb 2009	B2
7496651	Joshi	Feb 2009	B1
7500249	Kampe et al.	Mar 2009	B2
7505951	Thompson et al.	Mar 2009	B2
7519359	Chiarulli et al.	Apr 2009	B2
7522711	Stein et al.	Apr 2009	B1
7536454	Balasuriya	May 2009	B2
7542761	Sarkar	Jun 2009	B2
7552054	Stifelman et al.	Jun 2009	B1
7571226	Partovi et al.	Aug 2009	B1
7606868	Le et al.	Oct 2009	B1
7613287	Stifelman et al.	Nov 2009	B1
7623648	Oppenheim et al.	Nov 2009	B1
7630900	Strom	Dec 2009	B1
7631310	Henzinger	Dec 2009	B1
7644000	Strom	Jan 2010	B1
7657433	Chang	Feb 2010	B1
7657434	Thompson et al.	Feb 2010	B2
7668157	Weintraub et al.	Feb 2010	B2
7672275	Yajnik et al.	Mar 2010	B2
7672295	Andhare et al.	Mar 2010	B1
7675857	Chesson	Mar 2010	B1
7676221	Roundtree et al.	Mar 2010	B2
7685280	Berry et al.	Mar 2010	B2
7685298	Day et al.	Mar 2010	B2
7715547	Ibbotson et al.	May 2010	B2
7716293	Kasuga et al.	May 2010	B2
7742499	Erskine et al.	Jun 2010	B1
7779065	Gupta et al.	Aug 2010	B2
7809125	Brunson et al.	Oct 2010	B2
7875836	Imura et al.	Jan 2011	B2
7882253	Pardo-Castellote et al.	Feb 2011	B2
7920866	Bosch et al.	Apr 2011	B2
7926099	Chakravarty et al.	Apr 2011	B1
7929562	Petrovykh	Apr 2011	B2
7936867	Hill et al.	May 2011	B1
7949111	Harlow et al.	May 2011	B2
7962644	Ezerzer et al.	Jun 2011	B1
7979555	Rothstein et al.	Jul 2011	B2
7992120	Wang et al.	Aug 2011	B1
8023425	Raleigh	Sep 2011	B2
8024785	Andress et al.	Sep 2011	B2
8045689	Provenzale et al.	Oct 2011	B2
8046378	Zhuge et al.	Oct 2011	B1
8046823	Begen et al.	Oct 2011	B1
8069096	Ballaro et al.	Nov 2011	B1
8078483	Hirose et al.	Dec 2011	B1
8081744	Sylvain	Dec 2011	B2
8081958	Soderstrom et al.	Dec 2011	B2
8103725	Gupta et al.	Jan 2012	B2
8126128	Hicks, III et al.	Feb 2012	B1
8126129	Mcguire	Feb 2012	B1
8130750	Hester	Mar 2012	B2
8139730	Da Palma et al.	Mar 2012	B2
8145212	Lopresti et al.	Mar 2012	B2
8149716	Ramanathan et al.	Apr 2012	B2
8150918	Edelman et al.	Apr 2012	B1
8156213	Deng et al.	Apr 2012	B1
8165116	Ku et al.	Apr 2012	B2
8166185	Samuel et al.	Apr 2012	B2
8169936	Koren et al.	May 2012	B2
8175007	Jain et al.	May 2012	B2
8185619	Maiocco et al.	May 2012	B1
8196133	Kakumani et al.	Jun 2012	B2
8204479	Vendrow et al.	Jun 2012	B2
8214868	Hamilton et al.	Jul 2012	B2
8233611	Zettner	Jul 2012	B1
8238533	Blackwell et al.	Aug 2012	B2
8243889	Taylor et al.	Aug 2012	B2
8249552	Gailloux et al.	Aug 2012	B1
8266327	Kumar et al.	Sep 2012	B2
8295272	Boni et al.	Oct 2012	B2
8306021	Lawson et al.	Nov 2012	B2
8315198	Corneille et al.	Nov 2012	B2
8315620	Williamson et al.	Nov 2012	B1
8319816	Swanson et al.	Nov 2012	B1
8326805	Arous et al.	Dec 2012	B1
8346630	Mckeown	Jan 2013	B1
8355394	Taylor et al.	Jan 2013	B2
8413247	Hudis et al.	Apr 2013	B2
8417817	Jacobs	Apr 2013	B1
8429827	Wetzel	Apr 2013	B1
8438315	Tao et al.	May 2013	B1
8462670	Chien	Jun 2013	B2
8467502	Sureka et al.	Jun 2013	B2
8477926	Jasper et al.	Jul 2013	B2
8503639	Reding et al.	Aug 2013	B2
8503650	Reding et al.	Aug 2013	B2
8509068	Begall et al.	Aug 2013	B2
8532686	Schmidt et al.	Sep 2013	B2
8542805	Agranovsky et al.	Sep 2013	B2
8543665	Ansari et al.	Sep 2013	B2
8547962	Ramachandran et al.	Oct 2013	B2
8565117	Hilt et al.	Oct 2013	B2
8572391	Golan et al.	Oct 2013	B2
8576712	Sabat et al.	Nov 2013	B2
8577803	Chatterjee et al.	Nov 2013	B2
8582450	Robesky	Nov 2013	B1
8594626	Woodson et al.	Nov 2013	B1
8601136	Fahlgren et al.	Dec 2013	B1
8611338	Lawson et al.	Dec 2013	B2
8613102	Nath	Dec 2013	B2
8621598	Lai et al.	Dec 2013	B2
8649268	Lawson et al.	Feb 2014	B2
8656452	Li et al.	Feb 2014	B2
8667056	Proulx et al.	Mar 2014	B1
8675493	Buddhikot et al.	Mar 2014	B2
8688147	Nguyen et al.	Apr 2014	B2
8695077	Gerhard et al.	Apr 2014	B1
8728656	Takahashi et al.	May 2014	B2
8751801	Harris et al.	Jun 2014	B2
8755376	Lawson et al.	Jun 2014	B2
8767925	Sureka et al.	Jul 2014	B2
8781975	Bennett et al.	Jul 2014	B2
8806024	Toba Francis et al.	Aug 2014	B1
8819133	Wang	Aug 2014	B2
8825746	Ravichandran et al.	Sep 2014	B2
8837465	Lawson et al.	Sep 2014	B2
8838707	Lawson et al.	Sep 2014	B2
8843596	Goel et al.	Sep 2014	B2
8855271	Brock et al.	Oct 2014	B2
8861510	Fritz	Oct 2014	B1
8879547	Maes	Nov 2014	B2
8938053	Cooke et al.	Jan 2015	B2
8948356	Nowack et al.	Feb 2015	B2
8954591	Ganesan et al.	Feb 2015	B2
8964726	Lawson et al.	Feb 2015	B2
8990610	Bostick et al.	Mar 2015	B2
9014664	Kim et al.	Apr 2015	B2
9015702	Bhat	Apr 2015	B2
9031223	Smith et al.	May 2015	B2
9071677	Aggarwal et al.	Jun 2015	B2
9137127	Nowack et al.	Sep 2015	B2
9141682	Adoc, Jr. et al.	Sep 2015	B1
9161296	Parsons et al.	Oct 2015	B2
9204281	Ramprasad et al.	Dec 2015	B2
9294393	Mullooly	Mar 2016	B1
9306982	Lawson et al.	Apr 2016	B2
9307094	Nowack et al.	Apr 2016	B2
9325624	Malatack et al.	Apr 2016	B2
9338190	Eng et al.	May 2016	B2
9344573	Wolthuis et al.	May 2016	B2
9378337	Kuhr	Jun 2016	B2
9456008	Lawson et al.	Sep 2016	B2
9456339	Hildner et al.	Sep 2016	B1
9596274	Lawson et al.	Mar 2017	B2
9628624	Wolthuis et al.	Apr 2017	B2
9632875	Raichstein et al.	Apr 2017	B2
9774495	Okita et al.	Sep 2017	B1
20010038624	Greenberg et al.	Nov 2001	A1
20010043684	Guedalia et al.	Nov 2001	A1
20010051996	Cooper et al.	Dec 2001	A1
20020006124	Jimenez et al.	Jan 2002	A1
20020006125	Josse et al.	Jan 2002	A1
20020006193	Rodenbusch et al.	Jan 2002	A1
20020025819	Cetusic et al.	Feb 2002	A1
20020057777	Saito et al.	May 2002	A1
20020064267	Martin et al.	May 2002	A1
20020067823	Walker et al.	Jun 2002	A1
20020077833	Arons et al.	Jun 2002	A1
20020126813	Partovi et al.	Sep 2002	A1
20020133587	Ensel et al.	Sep 2002	A1
20020136391	Armstrong et al.	Sep 2002	A1
20020165957	Devoe et al.	Nov 2002	A1
20020176378	Hamilton et al.	Nov 2002	A1
20020176404	Girard	Nov 2002	A1
20020184361	Eden	Dec 2002	A1
20020198941	Gavrilescu et al.	Dec 2002	A1
20030006137	Wei et al.	Jan 2003	A1
20030012356	Zino et al.	Jan 2003	A1
20030014665	Anderson et al.	Jan 2003	A1
20030018830	Chen et al.	Jan 2003	A1
20030023672	Vaysman	Jan 2003	A1
20030026426	Wright et al.	Feb 2003	A1
20030046366	Pardikar et al.	Mar 2003	A1
20030051037	Sundaram et al.	Mar 2003	A1
20030058884	Kallner et al.	Mar 2003	A1
20030059020	Meyerson et al.	Mar 2003	A1
20030060188	Gidron et al.	Mar 2003	A1
20030061317	Brown et al.	Mar 2003	A1
20030061404	Atwal et al.	Mar 2003	A1
20030088421	Maes et al.	May 2003	A1
20030097330	Hillmer et al.	May 2003	A1
20030097447	Johnston	May 2003	A1
20030097639	Niyogi et al.	May 2003	A1
20030103620	Brown et al.	Jun 2003	A1
20030123640	Roelle et al.	Jul 2003	A1
20030149721	Alfonso-nogueiro et al.	Aug 2003	A1
20030162506	Toshimitsu et al.	Aug 2003	A1
20030195950	Huang et al.	Oct 2003	A1
20030195990	Greenblat et al.	Oct 2003	A1
20030196076	Zabarski et al.	Oct 2003	A1
20030204616	Billhartz et al.	Oct 2003	A1
20030211842	Kempf et al.	Nov 2003	A1
20030231647	Petrovykh	Dec 2003	A1
20030233276	Pearlman et al.	Dec 2003	A1
20040008635	Nelson et al.	Jan 2004	A1
20040011690	Marfino et al.	Jan 2004	A1
20040044953	Watkins et al.	Mar 2004	A1
20040052349	Creamer et al.	Mar 2004	A1
20040071275	Bowater et al.	Apr 2004	A1
20040101122	Da Palma et al.	May 2004	A1
20040102182	Reith et al.	May 2004	A1
20040117788	Karaoguz et al.	Jun 2004	A1
20040136324	Steinberg et al.	Jul 2004	A1
20040165569	Sweatman et al.	Aug 2004	A1
20040172482	Weissman et al.	Sep 2004	A1
20040199572	Hunt et al.	Oct 2004	A1
20040205101	Radhakrishnan	Oct 2004	A1
20040205689	Ellens et al.	Oct 2004	A1
20040213400	Golitsin et al.	Oct 2004	A1
20040216058	Chavers et al.	Oct 2004	A1
20040218748	Fisher	Nov 2004	A1
20040228469	Andrews et al.	Nov 2004	A1
20040236696	Aoki et al.	Nov 2004	A1
20040240649	Goel	Dec 2004	A1
20050005109	Castaldi et al.	Jan 2005	A1
20050005200	Matenda et al.	Jan 2005	A1
20050015505	Kruis et al.	Jan 2005	A1
20050021626	Prajapat et al.	Jan 2005	A1
20050025303	Hostetler, Jr.	Feb 2005	A1
20050038772	Colrain	Feb 2005	A1
20050043952	Sharma et al.	Feb 2005	A1
20050047579	Mansour	Mar 2005	A1
20050060411	Coulombe et al.	Mar 2005	A1
20050083907	Fishler	Apr 2005	A1
20050091336	Dehamer et al.	Apr 2005	A1
20050091572	Gavrilescu et al.	Apr 2005	A1
20050108770	Karaoguz et al.	May 2005	A1
20050125251	Berger et al.	Jun 2005	A1
20050125739	Thompson et al.	Jun 2005	A1
20050128961	Miloslavsky et al.	Jun 2005	A1
20050135578	Ress et al.	Jun 2005	A1
20050141500	Bhandari et al.	Jun 2005	A1
20050147088	Bao et al.	Jul 2005	A1
20050177635	Schmidt et al.	Aug 2005	A1
20050181835	Lau et al.	Aug 2005	A1
20050198292	Duursma et al.	Sep 2005	A1
20050228680	Malik	Oct 2005	A1
20050238153	Chevalier	Oct 2005	A1
20050240659	Taylor	Oct 2005	A1
20050243977	Creamer et al.	Nov 2005	A1
20050246176	Creamer et al.	Nov 2005	A1
20050286496	Malhotra et al.	Dec 2005	A1
20050289222	Sahim	Dec 2005	A1
20060008065	Longman et al.	Jan 2006	A1
20060008073	Yoshizawa et al.	Jan 2006	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060015467	Morken et al.	Jan 2006	A1
20060021004	Moran et al.	Jan 2006	A1
20060023676	Whitmore et al.	Feb 2006	A1
20060047666	Bedi et al.	Mar 2006	A1
20060067506	Flockhart et al.	Mar 2006	A1
20060080415	Tu	Apr 2006	A1
20060098624	Morgan et al.	May 2006	A1
20060129638	Deakin	Jun 2006	A1
20060143007	Koh et al.	Jun 2006	A1
20060146792	Ramachandran et al.	Jul 2006	A1
20060146802	Baldwin et al.	Jul 2006	A1
20060168334	Potti et al.	Jul 2006	A1
20060203979	Jennings	Sep 2006	A1
20060209695	Archer, Jr. et al.	Sep 2006	A1
20060212865	Vincent et al.	Sep 2006	A1
20060215824	Mitby et al.	Sep 2006	A1
20060217823	Hussey	Sep 2006	A1
20060217978	Mitby et al.	Sep 2006	A1
20060222166	Ramakrishna et al.	Oct 2006	A1
20060235715	Abrams et al.	Oct 2006	A1
20060256816	Yarlagadda et al.	Nov 2006	A1
20060262915	Marascio et al.	Nov 2006	A1
20060270386	Yu et al.	Nov 2006	A1
20060285489	Francisco et al.	Dec 2006	A1
20070002744	Mewhinney et al.	Jan 2007	A1
20070036143	Alt et al.	Feb 2007	A1
20070038499	Margulies et al.	Feb 2007	A1
20070043681	Morgan et al.	Feb 2007	A1
20070050306	McQueen	Mar 2007	A1
20070064672	Raghav et al.	Mar 2007	A1
20070070906	Thakur	Mar 2007	A1
20070070980	Phelps et al.	Mar 2007	A1
20070071223	Lee et al.	Mar 2007	A1
20070074174	Thornton	Mar 2007	A1
20070088836	Tai et al.	Apr 2007	A1
20070091907	Seshadri et al.	Apr 2007	A1
20070107048	Halls et al.	May 2007	A1
20070112574	Greene	May 2007	A1
20070116191	Bermudez et al.	May 2007	A1
20070121651	Casey et al.	May 2007	A1
20070127691	Lert	Jun 2007	A1
20070127703	Siminoff	Jun 2007	A1
20070130260	Weintraub et al.	Jun 2007	A1
20070133771	Stifelman et al.	Jun 2007	A1
20070147351	Dietrich et al.	Jun 2007	A1
20070149166	Turcotte et al.	Jun 2007	A1
20070153711	Dykas et al.	Jul 2007	A1
20070167170	Fitchett et al.	Jul 2007	A1
20070192629	Saito	Aug 2007	A1
20070201448	Baird et al.	Aug 2007	A1
20070208862	Fox et al.	Sep 2007	A1
20070232284	Mason et al.	Oct 2007	A1
20070239761	Baio et al.	Oct 2007	A1
20070242626	Altberg et al.	Oct 2007	A1
20070255828	Paradise	Nov 2007	A1
20070265073	Novi et al.	Nov 2007	A1
20070286180	Marquette et al.	Dec 2007	A1
20070291734	Bhatia et al.	Dec 2007	A1
20070291905	Halliday et al.	Dec 2007	A1
20070293200	Roundtree et al.	Dec 2007	A1
20070295803	Levine et al.	Dec 2007	A1
20080005275	Overton et al.	Jan 2008	A1
20080025320	Bangalore et al.	Jan 2008	A1
20080037715	Prozeniuk et al.	Feb 2008	A1
20080037746	Dufrene et al.	Feb 2008	A1
20080040484	Yardley	Feb 2008	A1
20080049617	Grice et al.	Feb 2008	A1
20080052395	Wright et al.	Feb 2008	A1
20080091843	Kulkarni	Apr 2008	A1
20080101571	Harlow et al.	May 2008	A1
20080104348	Kabzinski et al.	May 2008	A1
20080120702	Hokimoto	May 2008	A1
20080123559	Haviv et al.	May 2008	A1
20080134049	Gupta et al.	Jun 2008	A1
20080139166	Agarwal et al.	Jun 2008	A1
20080146268	Gandhi et al.	Jun 2008	A1
20080152101	Griggs	Jun 2008	A1
20080154601	Stifelman et al.	Jun 2008	A1
20080155029	Helbling et al.	Jun 2008	A1
20080162482	Ahern et al.	Jul 2008	A1
20080165708	Moore et al.	Jul 2008	A1
20080172404	Cohen	Jul 2008	A1
20080177883	Hanai et al.	Jul 2008	A1
20080192736	Jabri et al.	Aug 2008	A1
20080201426	Darcie	Aug 2008	A1
20080209050	Li	Aug 2008	A1
20080212945	Khedouri et al.	Sep 2008	A1
20080222656	Lyman	Sep 2008	A1
20080229421	Hudis et al.	Sep 2008	A1
20080232574	Baluja et al.	Sep 2008	A1
20080235230	Maes	Sep 2008	A1
20080256224	Kaji et al.	Oct 2008	A1
20080275741	Loeffen	Nov 2008	A1
20080307436	Hamilton	Dec 2008	A1
20080310599	Purnadi et al.	Dec 2008	A1
20080313318	Vermeulen et al.	Dec 2008	A1
20080316931	Qiu et al.	Dec 2008	A1
20080317222	Griggs et al.	Dec 2008	A1
20080317232	Couse et al.	Dec 2008	A1
20080317233	Rey et al.	Dec 2008	A1
20090018489	Babaev	Jan 2009	A1
20090037428	Achtermann	Feb 2009	A1
20090046838	Andreasson	Feb 2009	A1
20090052437	Taylor et al.	Feb 2009	A1
20090052641	Taylor et al.	Feb 2009	A1
20090059894	Jackson et al.	Mar 2009	A1
20090063502	Coimbatore et al.	Mar 2009	A1
20090074159	Goldfarb et al.	Mar 2009	A1
20090075684	Cheng et al.	Mar 2009	A1
20090083155	Tudor et al.	Mar 2009	A1
20090089165	Sweeney	Apr 2009	A1
20090089352	Davis et al.	Apr 2009	A1
20090089699	Saha et al.	Apr 2009	A1
20090092674	Ingram et al.	Apr 2009	A1
20090093250	Jackson et al.	Apr 2009	A1
20090125608	Werth et al.	May 2009	A1
20090129573	Gavan et al.	May 2009	A1
20090136011	Goel	May 2009	A1
20090170496	Bourque	Jul 2009	A1
20090171659	Pearce et al.	Jul 2009	A1
20090171669	Engelsma et al.	Jul 2009	A1
20090171752	Galvin et al.	Jul 2009	A1
20090182896	Patterson et al.	Jul 2009	A1
20090193433	Maes	Jul 2009	A1
20090216835	Jain et al.	Aug 2009	A1
20090217293	Wolber et al.	Aug 2009	A1
20090022131	Chen et al.	Sep 2009	A1
20090220057	Waters	Sep 2009	A1
20090222341	Belwadi et al.	Sep 2009	A1
20090225748	Taylor	Sep 2009	A1
20090225763	Forsberg et al.	Sep 2009	A1
20090228868	Drukman et al.	Sep 2009	A1
20090232289	Drucker et al.	Sep 2009	A1
20090234965	Viveganandhan et al.	Sep 2009	A1
20090235349	Lai et al.	Sep 2009	A1
20090241135	Wong et al.	Sep 2009	A1
20090252159	Lawson et al.	Oct 2009	A1
20090262725	Chen et al.	Oct 2009	A1
20090276771	Nickolov et al.	Nov 2009	A1
20090288012	Hertel et al.	Nov 2009	A1
20090288165	Qiu et al.	Nov 2009	A1
20090300194	Ogasawara	Dec 2009	A1
20090316687	Kruppa	Dec 2009	A1
20090318112	Vasten	Dec 2009	A1
20100027531	Kurashima	Feb 2010	A1
20100037204	Lin et al.	Feb 2010	A1
20100054142	Moiso et al.	Mar 2010	A1
20100070424	Monk	Mar 2010	A1
20100071053	Ansari et al.	Mar 2010	A1
20100082513	Liu	Apr 2010	A1
20100087215	Gu et al.	Apr 2010	A1
20100088187	Courtney et al.	Apr 2010	A1
20100088698	Krishnamurthy	Apr 2010	A1
20100094758	Chamberlain et al.	Apr 2010	A1
20100103845	Ulupinar et al.	Apr 2010	A1
20100107222	Glasser	Apr 2010	A1
20100115041	Hawkins et al.	May 2010	A1
20100138501	Clinton et al.	Jun 2010	A1
20100142516	Lawson et al.	Jun 2010	A1
20100150139	Lawson et al.	Jun 2010	A1
20100167689	Sepehri-Nik et al.	Jul 2010	A1
20100188979	Thubert et al.	Jul 2010	A1
20100191915	Spencer	Jul 2010	A1
20100208881	Kawamura	Aug 2010	A1
20100217837	Ansari et al.	Aug 2010	A1
20100217982	Brown et al.	Aug 2010	A1
20100232594	Lawson et al.	Sep 2010	A1
20100235539	Carter et al.	Sep 2010	A1
20100250946	Korte et al.	Sep 2010	A1
20100251329	Wei	Sep 2010	A1
20100251340	Martin et al.	Sep 2010	A1
20100265825	Blair et al.	Oct 2010	A1
20100029191	Sanding et al.	Nov 2010	A1
20100281108	Cohen	Nov 2010	A1
20100299437	Moore	Nov 2010	A1
20100312919	Lee et al.	Dec 2010	A1
20100332852	Vembu et al.	Dec 2010	A1
20110026516	Roberts et al.	Feb 2011	A1
20110029882	Jaisinghani	Feb 2011	A1
20110029981	Jaisinghani	Feb 2011	A1
20110053555	Cai et al.	Mar 2011	A1
20110078278	Cui et al.	Mar 2011	A1
20110081008	Lawson et al.	Apr 2011	A1
20110083069	Paul et al.	Apr 2011	A1
20110083179	Lawson et al.	Apr 2011	A1
20110093516	Geng et al.	Apr 2011	A1
20110096673	Stevenson et al.	Apr 2011	A1
20110110366	Moore et al.	May 2011	A1
20110014981	Koren et al.	Jun 2011	A1
20110131293	Mori	Jun 2011	A1
20110138453	Verma et al.	Jun 2011	A1
20110143714	Keast et al.	Jun 2011	A1
20110145049	Hertel et al.	Jun 2011	A1
20110149950	Petit-Huguenin et al.	Jun 2011	A1
20110151884	Zhao	Jun 2011	A1
20110158235	Senga	Jun 2011	A1
20110167172	Roach et al.	Jul 2011	A1
20110170505	Rajasekar et al.	Jul 2011	A1
20110176537	Lawson et al.	Jul 2011	A1
20110179126	Wetherell et al.	Jul 2011	A1
20110211679	Mezhibovsky et al.	Sep 2011	A1
20110251921	Kassaei et al.	Oct 2011	A1
20110253693	Lyons et al.	Oct 2011	A1
20110255675	Jasper et al.	Oct 2011	A1
20110258432	Rao et al.	Oct 2011	A1
20110265168	Lucovsky et al.	Oct 2011	A1
20110265172	Sharma	Oct 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110274111	Narasappa et al.	Nov 2011	A1
20110276892	Jensen-Horne et al.	Nov 2011	A1
20110276951	Jain	Nov 2011	A1
20110280390	Lawson et al.	Nov 2011	A1
20110283259	Lawson et al.	Nov 2011	A1
20110289126	Aikas et al.	Nov 2011	A1
20110289162	Furlong et al.	Nov 2011	A1
20110299672	Chiu et al.	Dec 2011	A1
20110310902	Xu	Dec 2011	A1
20110313950	Nuggehalli et al.	Dec 2011	A1
20110320449	Gudlavenkatasiva	Dec 2011	A1
20110320550	Lawson et al.	Dec 2011	A1
20120000903	Baarman et al.	Jan 2012	A1
20120011274	Moreman	Jan 2012	A1
20120017222	May	Jan 2012	A1
20120023531	Meuninck et al.	Jan 2012	A1
20120023544	Li et al.	Jan 2012	A1
20120027228	Rijken et al.	Feb 2012	A1
20120028602	Lisi et al.	Feb 2012	A1
20120036574	Heithcock et al.	Feb 2012	A1
20120039202	Song	Feb 2012	A1
20120059709	Lieberman et al.	Mar 2012	A1
20120079066	Li et al.	Mar 2012	A1
20120083266	Vanswol et al.	Apr 2012	A1
20120089572	Raichstein et al.	Apr 2012	A1
20120094637	Jeyaseelan et al.	Apr 2012	A1
20120101952	Raleigh et al.	Apr 2012	A1
20120110564	Ran et al.	May 2012	A1
20120114112	Rauschenberger et al.	May 2012	A1
20120149404	Beattie et al.	Jun 2012	A1
20120166488	Kaushik et al.	Jun 2012	A1
20120017361	Bleau et al.	Jul 2012	A1
20120170726	Schwartz	Jul 2012	A1
20120174095	Natchadalingam et al.	Jul 2012	A1
20120179646	Hinton et al.	Jul 2012	A1
20120180021	Byrd et al.	Jul 2012	A1
20120180029	Hill et al.	Jul 2012	A1
20120185561	Klein et al.	Jul 2012	A1
20120198004	Watte	Aug 2012	A1
20120201238	Lawson et al.	Aug 2012	A1
20120208495	Lawson et al.	Aug 2012	A1
20120221603	Kothule et al.	Aug 2012	A1
20120226579	Ha et al.	Sep 2012	A1
20120239757	Firstenberg et al.	Sep 2012	A1
20120240226	Li	Sep 2012	A1
20120246273	Bornstein	Sep 2012	A1
20120254828	Aiylam et al.	Oct 2012	A1
20120266258	Tuchman et al.	Oct 2012	A1
20120281536	Gell et al.	Nov 2012	A1
20120288082	Segall	Nov 2012	A1
20120290706	Lin et al.	Nov 2012	A1
20120304245	Lawson et al.	Nov 2012	A1
20120304275	Ji et al.	Nov 2012	A1
20120316809	Egolf et al.	Dec 2012	A1
20120321058	Eng et al.	Dec 2012	A1
20120321070	Smith et al.	Dec 2012	A1
20130018960	Knysz	Jan 2013	A1
20130029629	Lindholm et al.	Jan 2013	A1
20130031158	Salsburg	Jan 2013	A1
20130031613	Shanabrook et al.	Jan 2013	A1
20130036213	Hasan	Feb 2013	A1
20130036476	Roever et al.	Feb 2013	A1
20130047232	Tuchman et al.	Feb 2013	A1
20130054517	Beechuk et al.	Feb 2013	A1
20130054684	Brazier et al.	Feb 2013	A1
20130058262	Parreira	Mar 2013	A1
20130067232	Cheung et al.	Mar 2013	A1
20130067448	Sannidhanam et al.	Mar 2013	A1
20130097298	Ting et al.	Apr 2013	A1
20130110658	Lyman	May 2013	A1
20130132545	Schultze	May 2013	A1
20130132573	Lindblom	May 2013	A1
20130139148	Berg et al.	May 2013	A1
20130156024	Burg	Jun 2013	A1
20130166580	Maharajh et al.	Jun 2013	A1
20130179942	Caplis et al.	Jul 2013	A1
20130188634	Magee	Jul 2013	A1
20130201909	Bosch et al.	Aug 2013	A1
20130204786	Mattes et al.	Aug 2013	A1
20130212603	Cooke et al.	Aug 2013	A1
20130244632	Spence et al.	Sep 2013	A1
20130268676	Martins et al.	Oct 2013	A1
20130325934	Fausak et al.	Dec 2013	A1
20130328997	Desai	Dec 2013	A1
20130336472	Fahlgren et al.	Dec 2013	A1
20140013400	Warshavsky et al.	Jan 2014	A1
20140025503	Meyer et al.	Jan 2014	A1
20140058806	Guenette et al.	Feb 2014	A1
20140064467	Lawson et al.	Mar 2014	A1
20140072115	Makagon et al.	Mar 2014	A1
20140073291	Hildner et al.	Mar 2014	A1
20140095627	Romagnino	Apr 2014	A1
20140101058	Castel et al.	Apr 2014	A1
20140101149	Winters et al.	Apr 2014	A1
20140105372	Nowack et al.	Apr 2014	A1
20140106704	Cooke et al.	Apr 2014	A1
20140122600	Kim et al.	May 2014	A1
20140123187	Reisman	May 2014	A1
20140126715	Lum et al.	May 2014	A1
20140129363	Lorah et al.	May 2014	A1
20140153565	Lawson et al.	Jun 2014	A1
20140185490	Holm et al.	Jul 2014	A1
20140254600	Shibata et al.	Sep 2014	A1
20140258481	Lundell	Sep 2014	A1
20140269333	Boerjesson	Sep 2014	A1
20140274086	Boerjesson et al.	Sep 2014	A1
20140282473	Saraf et al.	Sep 2014	A1
20140289391	Balaji et al.	Sep 2014	A1
20140304054	Orun et al.	Oct 2014	A1
20140317640	Harm et al.	Oct 2014	A1
20140037251	Fausak et al.	Dec 2014	A1
20140355600	Lawson et al.	Dec 2014	A1
20140372508	Fausak et al.	Dec 2014	A1
20140372509	Fausak et al.	Dec 2014	A1
20140373098	Fausak et al.	Dec 2014	A1
20140379670	Kuhr	Dec 2014	A1
20150004932	Kim et al.	Jan 2015	A1
20150004933	Kim et al.	Jan 2015	A1
20150023251	Giakoumelis et al.	Jan 2015	A1
20150026477	Malatack et al.	Jan 2015	A1
20150066865	Yara et al.	Mar 2015	A1
20150081918	Nowack et al.	Mar 2015	A1
20150082378	Collison	Mar 2015	A1
20150100634	He et al.	Apr 2015	A1
20150119050	Liao et al.	Apr 2015	A1
20150146560	Johnsson	May 2015	A1
20150181631	Lee et al.	Jun 2015	A1
20150236905	Bellan et al.	Aug 2015	A1
20150281294	Nur et al.	Oct 2015	A1
20150339136	Suryanarayanan	Nov 2015	A1
20150365480	Soto et al.	Dec 2015	A1
20150370788	Bareket et al.	Dec 2015	A1
20150381580	Graham, III et al.	Dec 2015	A1
20160001758	Sugio	Jan 2016	A1
20160011758	Dornbush et al.	Jan 2016	A1
20160012465	Sharp	Jan 2016	A1
20160028695	Binder	Jan 2016	A1
20160065448	Loveless	Mar 2016	A1
20160077693	Meyer et al.	Mar 2016	A1
20160112475	Lawson et al.	Apr 2016	A1
20160112521	Lawson et al.	Apr 2016	A1
20160119291	Zollinger et al.	Apr 2016	A1
20160127254	Kumar et al.	May 2016	A1
20160149956	Birnbaum et al.	May 2016	A1
20160162172	Rathod	Jun 2016	A1
20160205519	Patel et al.	Jul 2016	A1
20160226937	Patel et al.	Aug 2016	A1
20160226979	Lancaster et al.	Aug 2016	A1
20160234391	Wolthuis et al.	Aug 2016	A1
20160239770	Batabyal et al.	Aug 2016	A1
20160315857	Lubashev	Oct 2016	A1
20170063614	Hartwig	Mar 2017	A1
20170214545	Cheng	Jul 2017	A1
20170339283	Chaudhary et al.	Nov 2017	A1
20180026877	Mysyk	Jan 2018	A1
20190274070	Hughes	Sep 2019	A1

Foreign Referenced Citations (20)

Number	Date	Country
1684587	Mar 1971	DE
0282126	Sep 1988	EP
1464418	Oct 2004	EP
1522922	Apr 2005	EP
1770586	Apr 2007	EP
2053869	Apr 2009	EP
2134107	Sep 1999	ES
10294788	Nov 1998	JP
2004166000	Jun 2004	JP
2004220118	Aug 2004	JP
2006319914	Nov 2006	JP
WO-9732448	Sep 1997	WO
WO-2002087804	Nov 2002	WO
WO-2006037492	Apr 2006	WO
WO-2009018489	Feb 2009	WO
WO-2009124223	Oct 2009	WO
WO-2010037064	Apr 2010	WO
WO-2010040010	Apr 2010	WO
WO-2010101935	Sep 2010	WO
WO-2011091085	Jul 2011	WO

Non-Patent Literature Citations (18)

Entry
“Aepona's API Monetization Platform Wins Best of 4G Awards for Mobile Cloud Enabler”, 4G World 2012 Conference & Expo, [Online]. [Accessed Nov. 5, 2015]. Retrieved from the Internet: <URL: https://www.realwire.com/releases/%20Aeponas-API-Monetization>, (Oct. 30, 2012), 4 pgs.
“U.S. Appl. No. 15/425,934, Final Office Action dated Sep. 17, 2019”, 15 pgs.
“U.S. Appl. No. 15/425,934, Non Final Office Action dated Mar. 19, 2019”, 19 pgs.
“U.S. Appl. No. 15/425,934, Notice of Allowance dated Jan. 14, 2020”, 14 pgs.
“U.S. Appl. No. 15/425,934, Response filed Nov. 14, 2019 to Final Office Action dated Sep. 17, 2019”, 10 pgs.
“U.S. Appl. No. 15/425,934, Response filed Jun. 5, 2019 to Non-Final Office Action dated Mar. 19, 2019”, 12 pgs.
“Archive Microsoft Office 365 Email I Retain Unified Archiving”, GWAVA, Inc., Montreal, Canada, [Online] Retrieved from the internet: <http://www.gwava.com/Retain/Retain for_Office_365.php>, (2015), 4 pgs.
“Complaint for Patent Infringement”, Telinit Technologies, LLC v. Twilio Inc 2:12-cv-663, (Oct. 12, 2012), 17 pgs.
“Ethernet to Token ring Bridge”, Black Box Corporation, [Online] Retrieved from the internet: <http://blackboxcanada.com/resource/files/productdetails/17044.pdf>, (Oct. 1999), 2 pgs.
“Twilio Cloud Communications—APIs for Voice, VoIP, and Text Messaging”, Twilio, [Online] Retrieved from the internet: <http://www.twilio.com/docs/api/rest/call-feedback>, (Jun. 24, 2015), 8 pgs.
Abu-Lebdeh, et al., “A 3GPP Evolved Packet Core-Based Architecture for QoS-Enabled Mobile Video Surveillance Applications”, 2012 Third International Conference on the Network of the Future {NOF), (Nov. 21-23, 2012), 1-6.
Barakovic, Sabina, et al., “Survey and Challenges of QoE Management Issues in Wireless Networks”, Hindawi Publishing Corporation, (2012), 1-29.
Berners-Lee, T., “RFC 3986: Uniform Resource Identifier (URI): Generic Syntax”, The Internet Society, [Online], Retrieved from the Internet: <URL: http://tools.ietf.org/html/rfc3986>, (Jan. 2005), 57 pgs.
Kim, Hwa-Jong, et al., “In-Service Feedback QoE Framework”, 2010 Third International Conference on Communication Theory. Reliability and Quality of Service, (2010), 135-138.
Matos, et al., “Quality of Experience-based Routing in Multi-Service Wireless Mesh Networks”, Realizing Advanced Video Optimized Wireless Networks. IEEE, (2012), 7060-7065.
Mu, Mu, et al., “Quality Evaluation in Peer-to-Peer IPTV Services”, Data Traffic and Monitoring Analysis, LNCS 7754, 302-319, (2013), 18 pgs.
Subramanya, et al., “Digital Signatures”, IEEE Potentials, (Mar./Apr. 2006), 5-8.
Tran, et al., “User to User adaptive routing based on QoE”, ICNS 2011: The Seventh International Conference on Networking and Services, (2011), 170-177.

Related Publications (1)

	Number	Date	Country
	20200244572 A1	Jul 2020	US

Provisional Applications (1)

	Number	Date	Country
	62291327	Feb 2016	US

Continuations (1)

	Number	Date	Country
Parent	15425934	Feb 2017	US
Child	16845291		US

Systems and methods for providing secure network exchanged for a multitenant virtual private cloud

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract