Microsoft Technology Licensing, LLC

Mark Ledsome

Neil Scott Fishman

Marc E Seinfeld

Don Kadyk

Brent E Curtis

Duncan Wayne Lee

Methods, systems, and computer program products for customizing content based on at least one operating characteristic of a mobile client. A mobile gateway receives content from a content source, such as an email server, a Web server, or some other content server. For example, content may include email, calendar, contact, task, Web, notification, financial, sports data, configuration information, etc. The mobile gateway customizes the content based on transforms assigned to each mobile client. Transforms account for differences in the software, display, processor, memory, communication channel, and the like, of each mobile client, without imposing additional processing burdens on the content server. Processing that is common among several transforms may be shared. Mobile clients may be any type of computer, including telephones, pagers, PDAs, laptops, and other mobile gateways.

Pushing rich content information to mobile devices

Methods, systems, and computer program products for caching content that has been customized based on one or more operating characteristics of a mobile client. A mobile gateway receives content from a content source and customizes the content using transforms assigned to each mobile client. Transforms account for differences between mobile clients without imposing significant processing burdens on the content server. Copies of the content, the transformed content, and a transform identifier are cached at the mobile gateway so that subsequent requests for the content may be satisfied without requiring access to the content source. Processing that is common among several transforms may be shared. Mobile clients may be any type of computer.

Caching transformed content in a mobile gateway

A method and system for synchronizing directories containing information about computer mail users. In a preferred embodiment, a computer mail facility synchronizes a user directory stored in a responding directory node with a more current user directory stored in an originating directory node. Directory update transactions are received in the originating node and assigned a sequence number to denote the consecutive order of acquisition. The sequence number is relative to an originating sequence number which tracks the completed transmission of the transactions to the responding node. The transactions are processed by the originating node and subsequently transmitted to the responding directory node. Upon receipt of the transactions, the responding node transmits a confirmation message indicating the largest consecutive sequence number of a received transaction. This is used by the originating directory node to determine whether the responding node has received a complete set of the transactions. The sequence number in the confirmation message is then used to set the originating sequence number.

Growing community of inventors

Seattle, WA, United States of America

Mark Ledsome