Microsoft Technology Licensing, LLC

Other

Mircrosoft Corporation

Sachin C Patel

Yadhu Nandh Gopalan

Andrew Michael Rogers

Karan Mehra

Andrew D Rogers

David Michael Callaghan

Ravisankar V Pudipeddi

Shiv Kumar Rajpal

Andrew Martin Pearson

Geir Olsen

JianMing M Zhou

Dylan D'Silva

Richard Thomas Palm

Aman Kansal

Scott Randall Shell

Mark Plagge

Michael E Markley

Mark Scott Tonkelowitz

Jeffery D Glaum

Jianming Zhou

Pure compressed diamond (PCD), grown in a laboratory, is laser-shaped into dental implants with high tensile strength, high compressive strength, high thermal conductivity, and which are harder than any other substance on earth. PCD is harder than ceramic zirconia and harder than titanium. Because PCD is pure carbon, it is also 100% compatible with carbon-based living tissue. Unlike titanium, it does not provoke an immune response. PCD implants readily integrate into human jawbone. This drastically reduces post-surgery bone loss.

Solid diamond dental implant, composition and method

In a parity-based redundancy scheme, allocation information indicative of free and allocated portions of storage is accessed. In response to a request for a write operation, when the write request shares its parity with a non-free portion of the storage, a record of writes to the storage is updated to include the requested write and associated parity. The parity is updated with the requested write, and the write request is executed. When the write request shares its parity with a free portion of the storage or the write request spans all portions of storage that shares the parity, the write request is allowed to be executed in the free portion of the storage without updating the record.

Parity log with by-pass

In a parity-based redundancy scheme, a log is maintained that contains a record of storage writes and associated redundancy backups. A mapping of allocation information indicative of free and allocated portions of storage is stored. An indication is received of a change to the free and allocated portions of storage. An update to the mapping of allocation information is determined, and the update to the mapping of allocation information is stored. The stored update is accessed and the redundancy backup is synchronized with stored data in response to a power interruption.

Parity log with delta bitmap

Applications are stored on removable storage of a mobile device in an encrypted form to provide isolation and piracy protection. In one implementation, each application is encrypted using its own associated encryption key that is generated based on an identifier of the application and a master key that is associated with a trusted platform module of the mobile device. In another implementation, each application is encrypted using two associated encryption keys. One key is used to encrypt binary data associated with the application such as source code, and the other key is used to encrypt application data such as graphics and configuration files. The encryption keys are each generated using the identifier of the application, the master key, and identifiers of the folders where the corresponding data types are stored on the mobile device. The removable storage includes SD cards formatted using the FAT or exFAT file systems.

Content item encryption on mobile devices

A system for storing data in a dynamic fashion. The system includes a storage entity. The storage entity includes portions of a plurality of different persistent storage devices. Each storage device has a set of constraints. The storage entity is configured to store data in a dynamic fashion in a layout on the persistent storage devices of the storage entity that meets the different data requirements for the data while still being within the constraints for the persistent storage devices. The storage entity is configured to change the layout for a portion of the data as requirements related to at least one of performance or resiliency for a portion of the data change while the storage entity continues to provide the data from the storage entity.

Live configurable storage

A transaction safe file system uses two sets of file allocation tables and bitmap images to perform file modifications on one of the sets while the other set remains a last known good set. After a modification is complete, a pointer is changed to the newly modified set, and the newly modified set becomes the last known good set. The sets are then synchronized. The file allocation table is used to define cluster chains while the bitmap image is used to determine if a cluster is free or not. In some operations, only the bitmap image may need to be manipulated. The file system may be used in a transaction safe mode as well as a non-transaction safe mode.

Storage system format for transaction safe file system

Directories in a file system are defined with a dummy cluster in a file allocation table as the initial entry. Subsequent clusters in a directory's definition may define any data for the directory that can be changed in a transaction-safe mode. A directory may be modified in a transaction-safe mode by modifying any of the subsequent clusters while tracking changes in a second file allocation table. When the changes have been made to the directory, a pointer to the second file allocation table may be switched to indicate that the second file allocation table is now last known good. The first file allocation table may then be synchronized with the second.

Fat directory structure for use in transaction safe file system

Concepts for enhancing operation of transaction-safe file allocation table systems are described. The concepts include writing a file to non-volatile memory media and rendering an update of file size to the TFAT storage medium; and receiving a request to locate data in a non-volatile memory having a TFAT file management system, selecting a sector of the memory to parse to locate the data, determining when the selected sector is a first sector of a directory or subdirectory of the memory and when determining reveals that the selected sector is a first sector, skipping reading data from the selected sector. The concepts also include flushing a cache and synchronizing FATs.

Transaction-safe fat file system improvements

Various flash management techniques may be described. An apparatus may comprise a processor, a flash memory coupled to the processor, and a flash management module. The flash management module may be executed by the processor to receive a write request to write data to the flash memory, write a first control sector with a sequence number to the flash memory, and write the sequence number, an address for a logical sector, and data to at least one physical sector corresponding to the logical sector of the flash memory. Other embodiments are described and claimed.

Flash management techniques

An application issues an application command to a file system of the computing device, where the application command includes a location of data at a source. The file system allocates space on a medium for the data and compiles a list including an identification of each portion of the medium that is to be used to store the data. The file system then issues a file system command to a block driver of the medium, where the file system command includes the location of the data at the source and the compiled list. The block driver contacts the source, requests the data at the location thereof, and writes the data to the portions of the medium included in the compiled list.

Growing community of inventors

Redmond, WA, United States of America

Sachin C Patel