Microsoft Technology Licensing, LLC

Anish Desai

Humayun Mukhtar Khan

Gursharan Singh Sidhu

Jonathan A Silvera

Mansoor Jafry

John David Bruner

Mahendra D Sekaran

Jeffrey B Kay

Vishal Soni

Marc David McClure

Ranveer Chandra

Thomas W Kuehnel

John Mark Miller

Ruchir Astavans

Rao Salapaka

Hagen Green

Ray Froelich

Jon Morris

Eugen Pajor

Paul J Leach

Rod G Fleck

Vishal Vikram Ghotge

Shaun Douglas Pierce

Dhigha D Sekaran

Henry L Sanders

Sankaran Narayanan

Namendra Kumar

Shivakumar Seetharaman

Arvind M Murching

Anil K Ruia

Krishnan Ananthanarayanan

Amey Parandekar

Abhilash Chandrasekharan Nair

Rajesh Sundaram

Robert Paul St Pierre

Eric S Hamilton

Kerry Woolsey

Frank Stephen Serdy, Jr

Adrian Dragomir

Matthew R Cox

Reid Joseph Kuhn

John D Skovron

Ganapathy V Raman

Kevin Grey

Vijay Kishen Hampapur Parthasarathy

Gaurav Pancholi

Jianping Yin

Tript Singh Lamba

Eric B Stenson

George V Reilly

Ramkumar Natarajan

Tony Bell

Ken Wolfe

Bayo Olatunji

Andrew Peter Schoorl

Rick James

Systems and methods for email synchronization may include a computing device with a token bucket. The token bucket allows for temporary storage of tokens, each token authorizing a synchronization of at least one email application running on the computing device. The device may determine a frequency of received email communications associated with an email account managed by the at least one email application and hosted by an email server. The determining may be based on one or more characteristics associated with the token bucket. The determined frequency may be compared with a threshold value. When the determined frequency is equal to or lower than the threshold value, a push communication channel may be established with the email server, the push communication channel for receiving server-initiated email push communications. The at least one email application may be synchronized with the email account by receiving push communications using the push communication channel.

Battery efficient synchronization of communications using a token bucket

Signaling from a mobile device is transparently tunneled through a cellular voice network to a Voice over Internet Protocol ('VoIP') core network so that multi-party calls, including conference calls and call waiting, can be managed entirely within the VoIP core network. The tunneled signals enable call control to be implemented in the VoIP core network and also establish a way to communicate requests, instructions, and call state. The signaling is transparent to the cellular network because that network does not receive and interpret the signaling. Instead, the cellular network's existing and unmodified control plane is repurposed by the mobile device by placing new, brief outgoing calls through the cellular network to the VoIP core network where the called party number (i.e., the caller-ID) encodes specific information. The VoIP core network immediately releases the new cellular call once the caller-ID is received and the encoded information is interpreted.

Tunneling VoIP call control on cellular networks

A continual learning process is applied to a class of risk estimate-based algorithms and associated risk thresholds used for deciding when to initiate a handoff between different types of network connections that are available to a mobile device having telephony functionality. The process is implemented as a virtuous loop providing ongoing tuning and adjustment to improve call handoff algorithms and risk thresholds so that handoffs can be performed with the goals of minimizing dropped calls and unacceptable degradation in call quality as well as avoiding premature handoffs. Device characteristics, environmental context, connection measurements, and outcomes of call handoff decisions are crowd-sourced from a population of mobile devices into a cloud-based handoff decision enabling service. The service evaluates potentially usable handoff decision algorithms and risk thresholds against archived crowd-sourced data to determine how they would have performed in real world situations and delivers improved algorithms and risk thresholds to the mobile devices.

Call handoff initiation in hybrid networks

Described are embodiments directed to enabling the retrieval of content from a peer-to-peer network. In embodiments, a client requesting content from a server can indicate in an HTTP request that it is capable of retrieving content from a peer-to-peer network. When the server receives the HTTP request it will recognize the indication that the client is capable of retrieving content from a peer-to-peer network and may send content information instead of sending the requested content. The content information allows the client to retrieve the content from the peer-to-peer network.

Enabling peer-to-peer content retrieval in HTTP

A mobile device utilizes a two-stage dialing solution when roaming on a visited mobile operator (MO) network to implement centralized routing so that a home network portion of a hybrid network is inserted into the path of outbound calls. A remote centralized routing (CR) service interoperates with a CR client on the mobile device. When a call is initiated to a remote party, the CR client calls into an arbitrary roaming routing number that is terminated in the home network. Once the call is connected between the mobile device and home network, the CR client sends a dialing string that includes a destination number of the remote party. The CR service calls the destination number and then bridges the calls to the mobile device and remote party to establish an end-to-end call path between the local and far ends of the call that traverses the home network.

Centralized routing in hybrid networks

Voice call continuity is provided for calls that are carried over a hybrid network infrastructure in which access connections are distributed over loosely coupled network portions including a backend network such as a core VoIP (Voice over Internet Protocol) service network, one or more cellular mobile networks, and a public switched telephone network ('PSTN'). The calls are routed through the core VoIP network regardless of their points of origination or termination in other network portions so that signaling and call context are anchored in the core VoIP network. The conditions under which user equipment operate are continuously monitored so that when a connection is determined to have been unacceptably degraded or is likely to be interrupted, and/or a more optimal connection is available, a handover of the call to another connection is initiated so that call continuity is maintained using the lowest cost connection that provides acceptable call quality.

Voice call continuity in hybrid networks

An invalid digital certificate can be saved and subsequently compared to an incoming digital certificate when performing a security check. If a subsequently provided digital certificate does not match the saved digital certificate, an error condition can be generated. Because a digital certificate can be invalid for non-malicious reasons, such technologies can be useful for improving software security.

Securely handling server certificate errors in synchronization communication

A client system and a server system use a Hypertext Transfer Protocol (HTTP) authentication mode preference header to negotiate an HTTP authentication mode. The client system sends an HTTP request to the server system. In response to the HTTP request, the server system sends an HTTP response to the client system. The HTTP response includes an HTTP authentication mode preference header. The HTTP authentication mode preference header indicates whether a preferred HTTP authentication mode is connection-based HTTP authentication or request-based HTTP authentication. In subsequent HTTP requests to the server system, the client system uses the HTTP authentication mode indicated by the HTTP authentication mode preference header.

Predictive HTTP authentication mode negotiation

A namespace management module utilizes a persistent reservation store that associates URI namespaces with one or more permissions. The reservation store can contain a number of reservation entries that each include a URI identifying a URI namespace and a corresponding Access Control List ('ACLs') that includes permissions for the identified URI namespace. When a request to register a URI namespace is received, the permissions of an appropriate ACL can be checked to determine if the registration is approved. When a resource request is received, permissions of the ACLs can also be checked to determine if the resource request should be routed to a registered process. Preemptive wildcards can be included in aggregated URIs to identify aggregated URI namespaces. Aggregated URIs can be included in registration requests to override the registration of unauthorized processes.

Securing uniform resource identifier namespaces

Growing community of inventors

Bellevue, WA, United States of America

Anish Desai