UNIFIED ACTIVITY SERVICE

• US 20170140025A1
• Filed: 11/17/2015
• Published: 05/18/2017
• Est. Priority Date: 11/17/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Milvaney, Douglas L., Harris, Andrew W., Wong, Candy Hoi Mei, Shukla, Manish Kumar, Chattan, Daniel J.
• Granted Patent: US 10,353,926 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/164 File meta data generation
• CPC Class Codes: G06F 16/24573 using data annotations, e.g. user-defined metadata
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06F 40/194 Calculation of difference between files
• CPC Class Codes: G06Q 10/101 Collaborative creation, e.g. joint development of products or services

Abstract

Aspects of the present disclosure relate to a unified activity service. In one aspect, a first file stored on a first storage platform may be rendered on a first user interface. One or more activities associated with the first file may be obtained from the activity service. A second file stored on a second storage platform may be rendered on a second user interface. One or more activities associated with the second file may be obtained from the activity service. In another aspect, activity metadata corresponding to at least one activity associated with a first file stored on a first storage platform and activity metadata corresponding to at least one activity associated with a second file stored on a second storage platform may be received at and stored in the activity service.

Claims

1. A system comprising:

one or more computer readable storage media; and

program instructions stored on the one or more computer readable storage media that, when executed by at least one processor, cause the at least one processor to at least;

render, on a first user interface, a file stored on a first storage platform;

obtain one or more activities associated with the file from the activity service, wherein the one or more activities include corresponding activity metadata;

render, on a second user interface, another file stored on a second storage platform; and

obtain one or more activities associated with the another file from the activity service, wherein the one or more activities include corresponding activity metadata.

2. The system of claim 1, wherein the first user interface and the second user interface are the same, and wherein the file is rendered on a client computing device, and wherein the another file is rendered on the client computing device.

3. The system of claim 1, wherein the file is rendered on a first client computing device, and wherein the another file is rendered on a second client computing device.

4. The system of claim 1, wherein the first storage platform is independent of the activity service.

5. The system of claim 1, wherein the second storage platform is independent of the activity service.

6. The system of claim 1, wherein the program instructions further cause the at least one processor to at least determine whether a user associated with the file has permission to access the one or more activities before obtaining the one or more activities associated with the file from the activity service.

7. The system of claim 1, wherein the program instructions further cause the at least one processor to at least determine whether a user associated with the another file has permission to access the one or more activities before obtaining the one or more activities associated with the another file from the activity service.

8. The system of claim 1, wherein the activity metadata includes at least one of an identifier, a timestamp, a type, a location, and a link.

9. A computer-implemented method for storing activity metadata in an activity service, the method comprising:

receiving an indication of an occurrence of at least one activity associated with a file stored independently of the activity service;

generating activity metadata corresponding to the at least one activity associated with the file; and

sending the generated activity metadata to the activity service for storing the generated activity metadata.

10. The computer-implemented method of claim 9, wherein the file is stored on a client computing device.

11. The computer-implemented method of claim 9, wherein the file is stored on a first storage platform.

12. The computer-implemented method of claim 11, further comprising:

receiving an indication of an occurrence of at least one activity associated with another file stored on a second storage platform;

generating activity metadata corresponding to the at least one activity associated with the another file; and

sending the generated activity metadata to the activity service for storing the generated activity metadata.

13. The computer-implemented method of claim 12, wherein the second storage platform is independent of the activity service.

14. A system comprising:

at least one processor; and

memory encoding computer executable instructions that, when executed by the at least one processor, perform a method for storing activity metadata in an activity service, the method comprising;

receiving, at the activity service, activity metadata corresponding to at least one activity associated with a file stored on a first storage platform;

storing the activity metadata corresponding to the at least one activity associated with the file stored on the first storage platform;

receiving, at the activity service, activity metadata corresponding to at least one activity associated with another file stored on a second storage platform; and

storing the activity metadata corresponding to the at least one activity associated with the another file stored on the second storage platform.

15. The system of claim 14, further comprising:

generating activity metadata corresponding to a plurality of activities associated with the file stored on the first storage platform; and

sending the generated activity metadata to the first storage platform.

16. The system of claim 14, further comprising:

generating activity metadata corresponding to a plurality of activities associated with the another file stored on the second storage platform; and

sending the generated activity metadata to the second storage platform.

17. The system of claim 14, further comprising:

receiving, from a third party entity, a request for activity metadata corresponding to a plurality of activities associated with the file stored on the first storage platform; and

sending the requested activity metadata to the third party entity, wherein the third party entity is independent of the activity service, the first storage platform, and the second storage platform.

18. The system of claim 14, wherein the file stored on the first storage platform has a first global identifier, and wherein the another file stored on the second storage platform has a second global identifier.

19. The system of claim 14, wherein the activity service stores activity metadata corresponding to a plurality of activities associated with a plurality of files stored on a plurality of storage platforms.

20. The system of claim 14, further comprising:

receiving, at the activity service, activity metadata corresponding to at least one activity associated with another file stored on a third storage platform; and

storing the activity metadata corresponding to the at least one activity associated with the another file stored on the third storage platform.