Microsoft Technology Licensing, LLC

Microsoft Corporation

Lijiang Fang

Winnie C Wu

Mark H Lucovsky

Shaun Douglas Pierce

Paul Andrew Steckler

Eric J Horvitz

Michael B Taylor

Paul J Leach

Richard Bruce Ward

Burra Gopal

Lei Zhao

Peter Sewall Ford

Jay Christopher Jacobs

Samuel John George

Steven D White

Jagadeesh Kalki

William Raymond Hoffman

Ramu Movva

Yanbiao Zhao

Suresh Kannan

Walter C Hsueh

Kendall D Keil

David Benjamin Auerbach

Philip Michael Smoot

Hua Yuan

Yun-Qi Yuan

Yi-Wen Guu

Chao Li

Nigel Robin Ellis

George M Moore

Johannes Klein

Rodger N Kline

David Michael Sauntry

Jian H Li

Maxim Mazeev

Michael Eric Deem

Srinivasmurthy P Acharya

Rhae-Christie Shaw

Ke Ma

Richard Critchlow

Ramesh Nagarajan

Edward G Sheppard

John M Gehlsen

Amit Shukla

James David Ryseff

Chang Luo

Siddhartha Singh

Prakash Sundra Krishnamoorthy

Paul A Steckler

Shaun D Pierce

The claimed subject matter provides a system and/or a method that facilitates rendering a portion of an image from a server on a client. A portion of an image can be hosted by a server. A client can utilize a device to interact with the portion of an image via a network. The client can established two or more TCP/IP connections with the server in order to interact with the portion of the image. A pipe component can enforce an isolated pipeline and a processing thread for each of a user manipulation of the portion of the image, a transmission of a user request to manipulate the portion of the image via the network, a rendering of the portion of the image on the server, a compression of the portion of the image on the server, a transmission of the compressed portion of the image via the network, a decompression of the portion of the image on the client, and a display of the portion of the image on the client.

Pipeline for network based server-side 3D image rendering

Various embodiments of the present invention are directed to a storage platform comprising: a data store in which data stored therein is defined in terms of items, elements, and relationships, wherein an item is a unit of data storable in the data store and comprises one or more elements, an element is an instance of a type comprising one or more fields, and a relationship is a link between at least two items; a set of schemas that define different types of items, elements, and relationships; and an application programming interface comprising a class for each of the different items, elements, and relationships defined in the set of schemas. Data may also be stored in the data store in the form of an extension to an existing item type, and wherein the application programming interface comprises a class for each different item extension.

Systems and methods for interfacing application programs with an item-based storage platform

Optimized storage and query of multi-value properties is enabled by generating a base table for single value properties associated with a user-defined schema and a number of row-based tables for each different type of multi-value properties. By combining multi-value properties into row-based tables or even into compatible type tables, a number of tables to be created for a database system such as SQL system is reduced at the same time optimizing create/read/update/delete operations.

Multi-value property storage and query support

In order to efficiently handle change notification requests to a storage system based on a database data store and a database engine, the change notification requests are multiplexed. This can be done by issuing a query which refers, for information about what changes are being tracked, to a data structure. The information about what changes to track for each request to be multiplexed is stored in the data structure. Additionally, information about the request can be stored in the data structure. By adding information to the data structure, the query can be altered without needing to directly modify or reissue the query.

Change notification query multiplexing

To provide data from a database in response to an application query, the database is queried an initial time to provide a first set of data. For example, a 'fast first page' may be requested, by requesting that all data which might appear on a first page to be displayed is obtained from the database first. After this, one or more subsequent asynchronous queries obtain the remaining information responsive to the query. Or, certain columns from the database ('spine columns') may be requested in the initial query of the database, and the rest of the data requested subsequently. Thus, information needed to make an initial presentation to a user can be obtained first, and other information filled in subsequently.

Fast rich application view initiation

Search and filtering of documents with different metadata schemata is enabled using a single index that supports a single schema through decorated namespaces. Each metadata schema submitted to a system is assigned a unique identifier and property names associated with the schema are prefixed with the unique identifier. A single-valued, decorated property is used to indicate whether a submitted document is part of a registered schema in the system. The single-valued properties are converted to a search index table that enables resource-optimized searching and filtering of documents eliminating documents of other schemata by simply checking the association property.

Searching a document based on a customer defined metadata schemata

A schema-based service for Internet access to per-user services data, wherein access to data is based on each user's identity. The service includes a schema that defines rules and a structure for each user's data, and also includes methods that provide access to the data in a defined way. The services schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the services schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user's identification, defined role and scope for that role. In this way, data can be accessed by its owner, and shared to an extent determined by the owner.

Schema-based services for identity-based data access

Described is a schema-based notification platform that provides regularized notification handling including user control and normalization of the operation of policies across different information types and contexts. Information-service schemas and services are combined to build a content-sensitive and context-sensitive information service to communicate information to recipient devices of users that subscribe to those services. An information agent service collects the information, and based on various criteria, determines if, when, and how to send and render the information, and to which subscribing client device or devices. The set of schemas include a notification schema that represents the subscription of a service to an information source and details about that information, and a device schema that represents information about user devices. The information agent service accesses criteria including user preferences and user contextual information, including presence information, location information, and schedule information along with people and groups data and extended-context data. Preferences about subscriptions and information handling policies may be stored and used at notification sources or in more central preference encodings. Access to multiple preferences is maintained, and a user interface is provided that allows users to inspect and control multiple subscriptions in one conceptual place.

Schemas for a notification platform and related information services

Described is a schema-based notification platform that provides regularized notification handling including user control and normalization of the operation of policies across different information types and contexts. Information-service schemas and services are combined to build a content-sensitive and context-sensitive information service to communicate information to recipient devices of users that subscribe to those services. An information agent service collects the information, and based on various criteria, determines if, when, and how to send and render the information, and to which subscribing client device or devices. The set of schemas include a notification schema that represents the subscription of a service to an information source and details about that information, and a device schema that represents information about user devices. The information agent service accesses criteria including user preferences and user contextual information, including presence information, location information, and schedule information along with people and groups data and extended-context data.

A framework for data change notification includes a notification queue storing event notifications. Client applications can request event information regarding various data change events. For example, a client application can subscribe, via one or more APIs, to receive event information. The framework allows for session specific event notification mechanisms as well as durable event notification mechanisms that can be preserved across client sessions as well as server restarts. Innovative aspects of this invention include guaranteed delivery of event notifications, APIs to allow applications get summary of past events on the subscribed objects, automatic garbage collection/cleanup of notifications when a client session terminates.

Providing change notifications to an entity-regarding a change of a specific type to data in a relational database

A schema-based device service that provides centralized access to per-user device data, wherein access to the device data is based on each user's identity. The device service includes a schema that defines rules and a structure for each user's data, and also includes methods that provide access to the data in a defined way. The device schema thus corresponds to a logical document containing the data for each user. A service such as a notification/alerts service accesses data in the logical document by data access requests through defined methods, such as in order to customize or modify a notification for a device based on the device characteristics. In one implementation, the device schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user's identification, defined role and scope for that role.

Schema-based services for identity-based access to device data

Growing community of inventors

Sammamish, WA, United States of America

Lijiang Fang