Pradeepkumar Mani

20200036778, Jan 30, 2020

Oct 3, 2019

16/592555

- Redmond WA, US
Pradeepkumar MANI - Issaquah WA, US
Nick HOLT - Seattle WA, US
David MALTZ - Bellevue WA, US
Jie LIU - Medina WA, US

H04L 29/08
H04L 12/26
H04L 29/12

N nodes are assigned to a first layer of nodes having a first domain name server (DNS) anycast Internet Protocol (IP) address and a first fully qualified domain name (FQDN). M nodes are assigned to a second layer of nodes having a second DNS anycast IP address and a second FQDN. When a request to resolve the first FQDN for the first layer of nodes is received by a DNS of a node of the first layer and a load on the ES of the node is less than a threshold, the DNS handles the request by returning an edge server (ES) anycast IP address for the ES of the node. When the load on the ES is greater than the threshold, the DNS offloads the request by returning the second FQDN so that the second FQDN of the second layer is resolved to the second DNS anycast IP address.

20180176295, Jun 21, 2018

Feb 15, 2018

15/897778

- Redmond WA, US
Pradeepkumar MANI - Issaquah WA, US
Nick HOLT - Seattle WA, US
David MALTZ - Bellevue WA, US
Jie LIU - Medina WA, US

H04L 29/08
H04L 29/12
H04L 12/26

N nodes are assigned to a first layer of nodes having a first domain name server (DNS) anycast Internet Protocol (IP) address and a first fully qualified domain name (FQDN). M nodes are assigned to a second layer of nodes having a second DNS anycast IP address and a second FQDN. When a request to resolve the first FQDN for the first layer of nodes is received by a DNS of a node of the first layer and a load on the ES of the node is less than a threshold, the DNS handles the request by returning an edge server (ES) anycast IP address for the ES of the node. When the load on the ES is greater than the threshold, the DNS offloads the request by returning the second FQDN so that the second FQDN of the second layer is resolved to the second DNS anycast IP address.

20170331716, Nov 16, 2017

Nov 16, 2016

15/353523

- Redmond WA, US
Shalabh Jain - Redmond WA, US
Pradeepkumar Mani - Issaquah WA, US
Chuanxiong Guo - Bellevue WA, US
David Aaron Maltz - Bellevue WA, US

H04L 12/26
H04L 12/46
H04L 12/26
H04L 12/26

Securely storing assets in a cloud computer storage service. Preparation to store assets for a user may comprise determining a location to store the assets, generating a write access signature, and sending the determined location and the signature to the user. A request is received from the user to store the assets. Such a request includes the assets, the location, and the signature. In response to receiving the request, a determination is made regarding the write access signature whether the request should be honored. When the request is honored, the assets are stored in the determined location and the write access signature is invalidated. Upon subsequent user requests to access the assets, short-term read access signatures are generated and provided to the user. The assets are written once per generated write access signature and reads are to be performed close in time to when short-term read access signatures are requested.

20160028847, Jan 28, 2016

Jul 23, 2014

14/339097

- Redmond WA, US
Ashley Ryan Flavel - Seattle WA, US
Kumar Ashutosh - Andhra Pradesh, IN
Jonathan Roshan Tuliani - Dublin, IE
Pradeepkumar Mani - Issaquah WA, US
Tushar Gupta - Telangana, IN
Vithalprasad Jayendra Gaitonde - Hyderabad, IN
V R Kishore Chintalapati - Andhra Pradesh, IN
Benjamin J. Black - Sammamish WA, US
William J. Griffin - Sammamish WA, US
David A. Maltz - Bellevue WA, US
Levon Hayrapetyan - Dublin, IE
Kresimir Bozic - Dublin, IE
Rajesh Kumar Maskara - Redmond WA, US
Sourav Sain - Hyderabad, IN
Andrew Lientz - Bellevue WA, US

Microsoft Technology Licensing, LLC - Redmond WA

H04L 29/08
H04L 29/12

Embodiments are directed to establishing caches that provide authoritative domain name system (DNS) answers to DNS requests. In one scenario, a computer system establishes a cache that stores authoritative DNS answers to DNS queries. The cache corresponds to a specified DNS zone that includes authoritative DNS answers for a subset of DNS queries. The cache is configured to store the authoritative DNS answers for at least a specified period of time during which the authoritative DNS answers are updatable. The cache then receives an update indicating that at least one cached DNS answer is out-of-date and the computer system purges the out-of-date DNS answer from the cache, ensuring that the cache continually provides authoritative DNS answers for DNS queries assigned to the specified DNS zone.

20150358401, Dec 10, 2015

Jun 5, 2014

14/297372

- Redmond WA, US
Pradeepkumar Mani - Issaquah WA, US
Nick Holt - Seattle WA, US
David Maltz - Bellevue WA, US
Jie Liu - Medina WA, US

H04L 29/08
H04L 12/26
H04L 29/12

An edge server node comprises an edge server, a DNS, and a load controller. The DNS is assigned to a layer of edge server nodes where each layer of edge server nodes has a DNS anycast IP address for the DNSs of that layer and a FQDN for that layer. The DNS either handles or offloads requests to resolve the FQDN for the assigned layer to balance the load on the edge server. A request is offloaded by returning the FQDN for another layer. The load controller monitors the load on the edge server and directs the DNS to offload requests to reduce the load on the edge server.