Microsoft Technology Licensing, LLC

Szymon Madejczyk

Jaskaran Singh

Roberto Ribeiro Da Fonseca Mendes

Kevin D Morrison

Shiraz Jitendra Cupala

Eric Jonathan Hull

Sina Hakami

James Paul Kardos

Julia Nancy Foran

Lan Ye

Dipak Sarjerao Pawar

Shivaram Prabhakar

Balasubramanian Ramachandran

Carolyn Amy McKenna

Jaya Matthew

Julia Foran Schearer

Anna Aleksandrovna Pablo

Julia Foran

Aaron Eugene Stout

Traditionally, meetings are widely utilized in business and personal communications, whether in-person and/or virtual. Organizing such meetings typically involves multiple exchanges of content and messages between users before, during, and after the meeting. In some cases, meetings may occur impromptu and may result in inefficient and unproductive collaboration. A collaboration object configured to enable users to dynamically collaborate before, during, and after a meeting is provided. In aspects, the collaboration object links content generated before, during, and after the meeting in a single location and provides functionality for concurrent multi-user interaction and synchronization of the content across applications. The collaboration object may be available from a variety of application platforms, enabling and persisting real-time editing and collaboration before, during and after the meeting.

Object for pre- to post-meeting collaboration

Auto-generated object for impromptu collaboration

The techniques described herein facilitate sharing electronic cloud-based calendars via online application and collaboration services, e.g., Microsoft Office 365&#xae;. In an implementation, a method of operating an online application and collaboration service for sharing electronic calendars between mailboxes is disclosed. The method includes receiving a request to share a master calendar owned by a first user of the online application and collaboration service with a second user. The master calendar is stored in the first user's mailbox. The method further includes communicating a response indicating acceptance of the request to share the master calendar, generating a copy of the master calendar in the second user's mailbox, and synching the copy of the master calendar with the master calendar using pre-cached data to populate an initial view.

Techniques for sharing electronic calendars between mailboxes in an online application and collaboration service

A system for validating data migrated from a first data store with source data to a second data store for destination data. A comparator is configured to access entity data for a particular entity which has been migrated from a first data store to a second data store. The comparator queries the first data store to a first set of comparison data from the first data store and obtains a second set of comparison data from the second data store. It then compares the first set of data with the second set of data to validate the migration of the data from the first to the second data store.

Data migration validation

A calendar sharing invitation is received, and a receiver of the information is identified. The calendar sharing information is sent to the receiver, and the sharer's calendar data is synchronized to a computing system corresponding to the receiver. The sharer's calendar data is synchronized to a pre-accept memory, where it is hidden from the receiver until the receiver provides an input indicating that the receiver accepts the calendar sharing invitation. The sharer's calendar data is then exposed to the receiver for interaction by the receiver.

Controlling a computing system to generate a pre-accept cache for calendar sharing

Adding an instance to a series in a fashion that preserves the series for both modern and legacy systems, even when the addition would not ordinarily be compatible with the legacy system. A method includes identifying a master message. The master message includes default values for events in the series. The method further includes identifying user input for a new event in the series. The user input identifies exceptions to the default values. The method further includes creating an instance message that includes default values from the master message for which there are no exceptions identified in the user input and includes the exceptions from the user input.

Add a new instance to a series

Using a set of alternative events with both modern and legacy systems. A method includes identifying a master message including a set of alternative events formatted for a modern system. The master message includes default information for all events in the set of alternative events as well as exception information representing exceptions to the default information for individual events in the set of alternative of events. A plurality of instance messages is identified. Each of the instance messages includes default information from the master message and exception information for a given event in the set of alternative events. The master message and the instance messages are sent to other systems without regard to whether the other systems are modern or legacy systems so as to allow modern systems to select event alternatives using the master message and to allow legacy systems to select event alternatives using the instance messages.

Consensus scheduling for business calendar

Migrating data from a source data store to a destination data store and validating the migrated data. The method includes migrating data from a first data store to a second data store using a first protocol to create a first set of comparison data. The method further includes migrating the data from the first data store to the second data store using a second protocol to create a second set of comparison data. The method further includes comparing the first set of comparison data to the second set of comparison data. The method further includes validating migration of the data from the first data store to the second data store based on comparing the first set of comparison data and the second set of comparison data.

Validating migration data by using multiple migrations

Providing series level updates for a series. A method includes identifying a master message. The master message is a series level message that includes a plurality of default properties for an ordered series. An ordered series of instance messages related to the series level message is identified. For each instance message in the ordered series of instance messages, one or more properties are identified that are not yet defined with default property values from the master message and that have not been defined as valid exceptions to the default properties from the master message. A default property value from a corresponding property of the master message is propagated to each of the identified properties. The ordered series is propagated to one or more legacy clients that are unable to consume certain series level messages by propagating the ordered series of instance messages with the updated property values.

Command propagation optimization

A method includes identifying a series of events formatted for a modern system. The series of events includes a master message usable by modern systems. The master message includes default information for all events in the series. The method further includes identifying a plurality of instance messages. Each of the instance messages includes default information and exception information for a given event in the series of events. The method further includes sending both the master message and the instance messages to other systems without regard to whether the other systems are modern or legacy systems.

Interoperability with legacy clients

Ordering a series of messages when there is a possibility that the messages will be received out of order. A method includes receiving a plurality of messages in a series of messages. Each of the messages in the plurality of messages is stored in a temporary storage container; in anticipation of receiving a master message. A master message is received. The master message defines an ordering for the plurality of messages. The messages in the series of message from the temporary storage to a destination container accessible by a user according to the ordering defined in the master message.

Growing community of inventors

Sammamish, WA, United States of America

Szymon Madejczyk