Microsoft Technology Licensing, LLC

Eric S Vandenberg

Joseph S Beda, Iii

Adam M Smith

Thomas W Olsen

Gerhard A Schneider

Kevin T Gallo

Robert Albert Wlodarczyk

David L Albert

Donald B Curtis

Tomasz S M Kasperkiewicz

Richard S Turner, Jr

Robert E Sinclair, Ii

Peter Alexi Gurevich

Rajat Goel

Michael Dean Stokes

Leonardo Esteban Blanco

Greg D Schechter

Sriram Subramanian

Shai Herzog

Cyra S Richardson

Anthony John Rolls Hodsdon

Michael Eric Deem

Matthew W Calkins

Rahul V Patil

Richard Shailer Turner, Jr

Marie Hagman

Don Curtis

Frank Alva Krueger

Radu C Magarint

A stateful cache layer is created at a mobile device client that tracks the state on both the mobile device and management service. The states are synchronized between the mobile device and the management service on every management session. Through the statefulness of the cache layer, unauthorized changes on the mobile device are detected and accordingly handled such as internal correction or reporting to the management service for actionable instructions. A cache layer on the management server is configured to identify organizational policy changes that affect specific devices and initiate unsolicited immediate management sessions to update the configuration to the specific devices.

Node monitor client cache synchronization for mobile device management

A method and architecture for reading and updating metadata. A policy component is arranged to receive a request to read or update metadata that may include metadata from a plurality of standards. Each metadata format potentially includes a field corresponding to the request. The policy component determines which fields to read or update in satisfying the request by consulting a repository. The repository includes mappings that map information included in the request (e.g., a path) to locations in the metadata corresponding to the request. The policy component uses the locations to read or update the metadata.

Abstracted metadata policy component and related architecture

A media integration layer including an application programming interface (API) and an object model allows program code developers to interface in a consistent manner with a scene graph data structure in order to output graphics. Via the interfaces, program code adds child visuals to other visuals to build up a hierarchical scene graph, writes Instruction Lists such as geometry data, image data, animation data and other data for output, and may specify transform, clipping and opacity properties on visuals. The media integration layer and API enable programmers to accomplish composition effects within their applications in a straightforward manner, while leveraging the graphics processing unit in a manner that does not adversely impact normal application performance. A multiple-level system includes the ability to combine different media types (such as 2D, 3D, Video, Audio, text and imaging) and animate them smoothly and seamlessly.

Media integration layer

An improved system and method for an extensible codec architecture for digital images is provided. Executable software code may be operably coupled to a codec manager for requesting imaging operations to be performed on a digital image. The codec manager may receive the request to perform an imaging operation on the digital image and may select an imaging component, such as a codec, from one or more imaging components registered in the computer system for performing an imaging operation on the digital image. An arbitration manager may include functionality for requesting enumeration of the operations an imaging component may perform on a particular digital image. One or more pixel format converters may then convert the pixel format in the digital image to a pixel format supported by an imaging component installed on the system.

System and method for providing an extensible codec architecture for digital images

A method and system implemented in an application programming interface (API) and an object model allows program code developers to interface in a consistent manner with a scene graph data structure to output graphics. Via the interfaces, program code writes drawing primitives such as geometry data, image data, animation data and other data to visuals that represent a drawing surface, including validation visual objects, drawing visual objects and surface visual objects. The code can also specify transform, clipping and opacity properties on visuals, and add child visuals to other visuals to build up a hierarchical scene graph. A visual manager traverses the scene graph to provide rich graphics data to lower-level graphics components.

Visual and scene graph interfaces

Described is the adding of padding to a content file (e.g., image and/or audiovisual file) for anticipated subsequent use such that the content file need not be re-encoded to add metadata and other data to it. For example, padding may be added to an image file directly after an image file directory, whereby the directory can grow as needed into the padded space. Metadata can likewise be added to the padding, e.g., from the opposite direction that the directory extends into the padding. The padding may be added on the first re-encoding of the file, reducing or eliminating the need for subsequent re-encoding. The padding also may be used to track dead space in the file, with adjacent regions of dead space coalesced into a single region of dead space.

Padding management for content files

Growing community of inventors

Seattle, WA, United States of America

Eric S Vandenberg