Microsoft Technology Licensing, LLC

Alibaba Group Holding Limited

Wei Zhao

Deepak Bansal

Gang Cheng

Li Han

Saad Syed

Sushant Pramod Rewaskar

Abhishek Kumar Singh

Gaurav Jagtiani

Thiruvengadam Venketesan

Akram Hassan

Abhishek Abhishek

Yi Lu

Parveen Kumar Patel

Ajay Mani

Taroon Mandhana

Xinyan Zan

Yue Chen

Olivier M Contant

Anirban Banerjee

Nisheeth Srivastava

Hong Liu

Abhishek Singh

Sushant Pramad Rewaskar

The techniques discussed herein include storing a fast-path and a slow-path table in a memory associated with a programmable switch, such as a cache of the programmable switch. An offload controller may control the contents of the fast-path and/or slow-path table and may thereby control behavior of the programmable switch. The programmable may route a received packet to a gateway if the packet generates a hit in the slow-path table. If the received packet generates a hit in the fast-path table, the packet may be forwarded directly to a virtual private cloud (VPC), virtual switch thereof, and/or to a virtual machine (VM).

Overlay network routing using a programmable switch

The techniques described herein include isolating network traffic between tenants using a programmable switch that routes network traffic directly to the appropriate virtual private cloud (VPC) and/or virtual machine (VM).

ASIC for routing a packet

A method and system that include techniques for an offload controller that controls functionality of a programmable switch. The offload controller may handle hash management and/or hash collision resolution for the programmable switch. The offload controller may additionally or alternatively configure the programmable switch to forward packets directly to a virtual private cloud (VPC) and/or virtual machine (VM), bypassing a gateway in some instances.

Offload controller control of programmable switch

The techniques discussed herein include an offload controller, a virtual routing controller, and/or virtual routing objects. In some instances the virtual routing controller may be configured and/or positioned to peer client premises equipment (CPE). This may include establishing an external gateway protocol session with CPE and generating a virtual routing object based at least in part on the session. In some examples, this virtual routing object may be used to configure routes between a switch and a virtual private cloud (VPC) and/or virtual machine (VM).

Client-equipment-peering virtual route controller

Systems and methods for accessing cloud services by managing network routes are provided. A network switch may receive network routes and forward the network routes to a route server where the network routes are saved and calculated. The route server may select a subset of the calculated network routes on which the network switch is able to directly forward data packets and configure a switch forwarding table. The network switch may receive the switch forwarding table, forward data packets having destination IP addresses in the switch forwarding table to the destination IP addresses directly, and forward other data packets to the default gateway server. A default gateway server may receive the calculated network routes from the route server enabling the gate server to forward any received data packets, and receive, from the network switch, the other data packets for forwarding to their destination IP addresses.

Method and system for accessing cloud services

Embodiments described herein are directed to migrating affected services away from a faulted cloud node and to handling faults during an upgrade. In one scenario, a computer system determines that virtual machines running on a first cloud node are in a faulted state. The computer system determines which cloud resources on the first cloud node were allocated to the faulted virtual machine, allocates the determined cloud resources of the first cloud node to a second, different cloud node and re-instantiates the faulted virtual machine on the second, different cloud node using the allocated cloud resources.

Healing cloud services during upgrades

In some embodiments, a wireless management service provides the capability to manage connectivity between a device and one or more wireless networks on a differentiated basis. For example, network profiles may be managed in a way that is influenced by the identity of the user, such that profiles which are customized for a specific user may be established. Connectivity may also be managed in a way that is influenced by a session type ongoing on a device, such that when certain events occur (e.g., a request by one user to connect to or disconnect from a wireless network is processed), wireless connectivity employed by other users sharing the device is appropriately managed.

Differentiated management of wireless connectivity

A network enabled computer receives connection profile information in a generic form and creates one or more native mode profiles to establish connections. By accepting profile information in a generic form, profile information can be readily provided from one or more ways, including from a policy server, through a user interface or from a third party application. The profile information can be provided with an order of precedence so that profile information from different sources may be combined appropriately. Additionally, the profile information may be provided in an extensible format to allow profile information to be distributed to multiple computers, even if some have different hardware or software configurations and are not programmed to recognize extensions of the profile information.

Profile deployment using a generic format

Growing community of inventors

Bellevue, WA, United States of America

Wei Zhao