Microsoft Technology Licensing, LLC

Christopher James Antos

Jonathan Bailor

Mark Rolland Knight

Ethan Joseph Bernstein

Simon Clarke

Miko Arnab Sakhya Singha Bose

Brian M Jones

Edgar Mark Sunderland

David Benjamin Robins

Andrew Richard Simonds

Andrew Grey Carlson

Andrew Sean Watson

Simon Skaria

Naresh Kannan

Mitesh Patel

Don Adam Hedgpeth

Elena Petrova

Darren Alexander Apfel

Hai Liu

Artem Yevgenyevich Livshits

Steve Rayson

David M Buchthal

Jason Buckingham

Chuck Reeves

Josue Leobardo Noriega De La Vega

Manasi V Velhankar

Fred Monteiro Da Cruz Filho

Brian Michael Jones

Jonathan Beckett Bailor

Simon Peter Clarke

A collaborative authoring application provides an authoring environment in which two or more users can edit a document concurrently. Each user edits a copy of the document, sends updates to a master copy of the document, and receives updates from the master copy of the document. The authoring environment generally inhibits the users from providing conflicting editing instructions to the master copy of the document. For example, each user can generate a content lock about one or more data units within the document. The authoring environment may synchronize content locks automatically and content only at the request of the user.

Collaborative authoring

Various embodiments of the present technology generally relate to smarter code review tools. More specifically, some embodiments relate to code review tools that include the ability to perform a 'rebased' diff of code iterations. As a result, the code review tool has the ability to diff a file from a first iteration (e.g., iteration) that was based on an initial base file (i.e., baseFile), against updates from a second iteration (i.e., iteration) that was based on an updated base file (i.e., baseFile) without identifying the differences that occur between the initial base file and the updated base file. This allows a reviewer to view only the differences that the author of the code review made between successive iterations while filtering out or suppressing the extra noise that occurs because of updates to the base file.

Code review rebase diffing

A collaborative authoring application provides an authoring environment in which two or more users can edit a document concurrently. Each user edits a copy of the document, sends updates to a master copy of the document, and receives updates from the master copy of the document. The authoring environment may be configured into a public mode of operation, in which content and metadata are synchronized automatically, or into a private mode of operation, in which metadata is synchronized automatically and content is synchronized only at the request of the user. The authoring application may edit documents offline in public or private mode.

Collaborative authoring modes

A mobile device executes a background process under an on demand model that queries a remote service exposed by a mobile broadband network to receive status updates as to the capabilities of devices, such as the ability to stream video, that are associated with contacts that are stored on the mobile device. When a mobile device user invokes an action like using a dialer application that causes a contact to be displayed on the device's user interface (UI) such as in a contact card or contact list format, the background process immediately retrieves status for that contact card or list. While waiting for the status retrieval to complete, the background process will trigger the display of a temporary UI on the mobile device which can show either unknown capabilities status or show the most recently retrieved status that is read out of a cache.

Efficient retrieval of 4G LTE capabilities

Client-server interaction frequency control may be provided. First, a collaborative electronic document may be loaded at a client device in a document collaboration session. The client device may then request a client-server interaction with a server hosting the collaboration session. Next, the client may receive input from the server indicating a state of the server. This input may then be used by the client device to adjust a rate at which the requested client-server interaction may occur.

Client-server interaction frequency control

Example systems and methods are directed at maintaining and retrieving presence metadata. One example method includes receiving a request from a first client to edit a document file, and sending short-term check out metadata to the first client to begin an editing session. The method also includes writing the transition ID to a transition table stored in a cache, wherein the presence of another transition ID in the cache indicates that a document has switched from a single-client mode to a multi-client mode. An example system includes a processing unit operative to receive a document, the document including short-term check out metadata indicating an editing session has begun, ping a cache to determine if another transition ID is stored in the cache, and send a transition ID to a transition table stored in a cache to switch from a single-client mode to a multi-client mode.

Caching infrastructure

Examples are related to systems and methods for controlling access to document files on a document server. One example system includes document files stored on a document server, at least one of the document files referencing a file lock, and a document access processing module. The example document access processing module includes a file sharing processing module that determines a coauthoring status of a software application of a client computer requesting access to the document file, and a file lock processing module that stores one or more file locks and that controls the setting and resetting of file locks. The example document access processing module uses the coauthoring status of the software application and the file lock status of a document file to determine whether a software application is permitted to have write access to the document file.

Controlling access to documents using file locks

Client side locking

Tools and techniques for synchronizing metadata and document content across client systems using different communication channels are provided. These tools may define logical communication channels between client software components, and may allocate one of these channels to synchronizing updates to the contents of documents shared between these client components. These tools may allocate another one of the communication channels to synchronizing metadata between the client components, with the metadata describing activity pertaining to the shared documents. The client components may receive indications of activity made by users to the document contents, and may create metadata representing the activity. These client components may then transmit this metadata, using the further communication channel, to any number of other client components automatically in real time with the updates.

Synchronizing metadata describes user content updates and an indication of user gestures being performed within the document, and across client systems using different communication channels

A computing device includes a processing unit, and a memory with instructions that, when executed by the processing unit, cause the processing unit to create: a document processing module that processes the creation and editing of document content; and a metadata processing module that generates, monitors and stores metadata for a document on the computing device, the metadata processing module generating lock creation metadata that include information about a new lock that is created when a user begins to edit a portion of a document, lock removal metadata that includes information about removing a lock, and lock deletion metadata that includes information about deleting a lock, the metadata processing module writing lock creation metadata to both a data channel and to a separate metadata channel, the metadata processing module writing lock removal metadata to the data channel and the metadata processing module writing lock deletion metadata to the metadata channel.

Cross-channel coauthoring consistency

Methods and systems of merging a first document with at least a second document to generate a third document. Each of the first and second documents includes at least one data unit. Each data unit is associated with a unit identifier and an edit identifier. The unit identifiers of each of the documents are compared to the unit identifiers of the other document to determine whether each unit identifier is a matching or non-matching unit identifier. Edit identifiers of the data units associated with the matching unit identifiers are compared to each other. Data units associated with the non-matching unit identifiers are inserted directly into the third document. Data units associated with the matching unit identifiers and the matching edit identifiers are inserted directly into the third document. Data units associated with the matching unit identifiers and the non-matching edit identifiers are merged into the third document.

Document merge

Growing community of inventors

Bellevue, WA, United States of America

Christopher James Antos