Microsoft Technology Licensing, LLC

Other

Steven James Bailey

John David Rodrigues

Filip Chelarescu

David John Nettleton

Adam Christopher Czeisler

Andrew Keith Glover

Meir Elie Abergel

Jose Araujo Barreto

Benjamin N Truelove

Aninda Ray

John D Fan

Coyle Brett Marl

Eric Robert Berman

Jose Emmanuel Miranda-Steiner

Kevin Andrew Chan

Roger Lueder

Gregory Powell Young

Parthipan Thayanithy

Jyotsana Rathore

Dennis Joel David Myren

Jackson Stuart Cowan

Hansel Ivan Gene Ip

Andrew James Koltz

Filip C Lazar

Anne Catherine Feldman

Joerg Perieno Germann

Jacob C Schieber

Vivek Khurana

Gregor Noriskin

Luis Talavera

Aleksandra Dorota Kopczynska-Dobosz

Edgar Hernandez Gonzalez

Naman Kanakiya

Meir E Abergel

Andrew Glover

David J Nettleton

The techniques disclosed herein provide a synchronization engine that operates in conjunction with a service worker to dynamically store and update a working set of user data and single page application (SPA) resources from a network server to a user device. The working set can be hosted across several domains and identified by association with a user account. Accordingly, the synchronization engine retrieves the working set from the network server to enable offline execution of the single page applications. As such, subsequent requests for interacting with a single page application are then serviced by the synchronization engine using the working set retrieved from the network server. For instance, the service worker can bind user data to the application resources to enable progressive rendering through an application controller using locally available resources. In this way, the disclosed system provides a consistent user experience irrespective of network connectivity.

Domain agnostic offline runtime for single page applications

A system is provided for controlling access to data stored in a cloud-based storage service. Data associated with a user account is stored at the cloud-based storage service. A first request to cause a portion of the data to be associated with a heightened authentication protocol is received. In response, the portion of the data is caused to require the heightened authentication protocol for access. A second request for a file that is stored in the area that is associated with the heightened authentication protocol is received. The second request is authenticated based on the heightened authentication protocol. In response to authenticating the second request, permission is granted to access the file. In response to a failure to authenticate the second request, access to the file is denied, while access to files stored in other areas associated with the user account is allowed.

Secure area in a file storage system

The techniques described herein improve an item (e.g., photo) sharing experience on mobile devices. In one embodiment, an application presents items in a stacked configuration and receives swipe-based touch gestures that reflect user intent with regard to whether or not a photo is to be shared to a network destination. After a directional swipe occurs on the top-most item, the next item in the stacked configuration is displayed for a next directional swipe. This process is repeated until all the items in the stacked configuration have been displayed to the user. In another embodiment, the application receives a continuous user gesture that traverses a set of photos laid out in a grid configuration. When performing the continuous user gesture, whether or not the user pauses on a photo reflects a user intent with regard to whether or not the photo is to be shared to a network destination.

User interactions and feedback signals for sharing items to a network destination

A system and method for providing automated service-based malware remediation. When a computing device is attacked by malware such as ransomware, multiple manual steps are usually needed to fully remediate the device. Users are typically required to follow several steps to remove the ransomware, and potentially must engage in the challenging task of reimaging the impacted device as well as choosing a restore point for point-in-time recovery. The disclosed systems provide a mechanism by which a cloud-based service manages a fully automated remediation and file recovery process for the user.

Automated malware remediation and file restoration management

A system and method for detection and management of atypical synchronization sessions of electronic content. The system is configured to determine whether a pending or ongoing synchronization session between a client device and cloud storage service is associated with a condition that will delay the synchronization process. The proposed system and method can significantly improve the ability of users to safeguard their documents as well as reduce the likelihood of data loss.

Long upload time detection and management

A cloud storage server receives a request from a client device to store a file. The cloud storage server stores the file in a storage device of the cloud storage server. The cloud storage server determines features of the server-stored file and detects ransomware activity based on the features of the server-stored file. The cloud storage server sends a notification of the ransomware activity to the client device. The client device confirms the presence or an absence of the ransomware activity in the server-stored file. The cloud storage server updates an operation of the detection of the ransomware activity based on the received ransomware confirmation.

Service identification of ransomware impacted files

As users increasingly shift to cloud services, devices are less likely to be pre-loaded with applications that support the multitudes of different file types that exist today and are continuing to be created. Thus, embodiments are directed to editing and sharing unsupported files through an instantly generated preview without having to install applications that support each file type and/or subscribe to services. For example, in response to detecting a user's request to access a file that is stored locally and determining a lack of a local application or previewer associated with the file, a preview that includes a presentation of the file using a registered previewer may be instantly generated. The preview may be rendered such that the file can be edited and/or shared through the previewer based on a level of editing and/or sharing functionality, respectively, where the levels of functionality are based on the user's subscription status.

Edit and share unsupported files through instantly generated preview

Identification of an entity performing a deletion or modification action on locally stored files and notification to mitigate risks to cloud stored files is provided. A local or remote file watcher may monitor locally stored files and detect a deletion or modification action. The file watcher may also identify an entity performing the deletion or modification action. The entity may be an application, a process, a user other than the user that is the owner of the files, or the user himself/herself. The file watcher may further determine one or more alert conditions or rules associated with the affected file(s) and/or the entity, that is under which circumstances an alert is to be issued. The alert notification(s) may be issued to the user, an administrator, a cloud storage service, and/or a data protection service such that protective measures can be taken if necessary.

Identification of entity performing operation on local file(s) and notification to reduce misuse risk

Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Conventionally, if locally stored content is deleted from a device, the delete would be propagated to the storage service causing the content to not only be deleted from the storage service but from any other devices where the content was locally stored and synchronized with the storage service. Embodiments are directed to retainment of locally deleted content at the storage service to prevent accidental or nefarious deletions of locally stored content on a device from further causing the content to be deleted universally from the storage service and/or multiple other devices. For example, the storage service may be configured to receive content stored locally on the device, detect a deletion of the content on the device, and retain the content at the storage service.

Retain locally deleted content at storage service

Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Embodiments are directed to retainment of locally deleted content at the storage service to prevent accidental or nefarious deletions of locally stored content on a device from being propagated to the storage service. For example, a selectable feature to retain locally deleted content, at the storage service may be presented through a display of a client device. A deletion of the content from the client device may be detected. The retained content may be prevented from being downloaded and stored locally on the client device when content at the storage service and the client device are synchronized if the feature was selected. If the feature was not selected, deletion options for the content may be presented through the display.

Retainment of locally deleted content at storage service by client device

Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Embodiments are directed to detection of bulk operations associated with content stored at a storage service to protect users both proactively and remedially from accidental and/or nefarious content alterations propagating to the storage service and/or other devices. A model may be created based on a usage pattern associated with the content, an attempted operation performed on the content may be detected, and the attempted operation may be compared to the model to determine whether the operation deviates from the usage pattern. If the attempted operation deviates from the usage pattern, a preservation policy for the content at the storage service may be modified and a notification of the attempted operation may be provided to obtain user approval.

Detection of bulk operations associated with remotely stored content

Cloud-based storage services are provided for storing data across multiple devices, where access to the data is subject to a first authentication process. Embodiments are directed to a data protection feature to prevent accidental deletion or modification of the data stored at the cloud via unintended user actions on the clients or actions by nefarious software or hackers. For example, a data protection feature for a portion of data stored at the storage service may be selected, where the feature includes elevation of the first authentication process. An attempted operation performed on the portion of data may be detected. If the attempted operation is deletion or modification of the portion of data, a second authentication process may be prompted to enable the attempted operation to be performed on the portion of data at the storage service. The second authentication process may be elevated compared to the first authentication process.

Protection feature for data stored at storage service

Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Embodiments are directed to detection of bulk operations associated with content stored at a storage service to protect users both proactively and remedially from accidental and/or nefarious content alterations propagating to the storage service and/or other devices. A model based on a usage pattern monitored and provided by a client device may be received at the client device from the storage service. An attempted operation performed on the content may be detected, and the attempted operation may be compared to the model to determine whether the operation deviates from the usage pattern. If the attempted operation deviates from the usage pattern, execution of the attempted operation and synchronization of the content with the storage service may be prevented until the attempted operation is approved.

Detection of bulk operations associated with remotely stored content by client device

Systems and methodologies are provided for efficiently performing concurrent transactions by multiple users, and tracking data at a logical level beneath a physical level of the object being modified. Each transaction can copy a committed version of the data segment to be modified to its respective space, and can update such copy during modification. A detect component detects whether any data segment being operated upon requires updating as a result of other transactions committing, and a merge component synchronizes the data segment with its committed version. Various optimization procedures can also be incorporated as part of the commit stage, upon completion of the detect and merge process.

Growing community of inventors

Redmond, WA, United States of America

Steven James Bailey