PROVIDING LOCALIZED INDIVIDUALLY CUSTOMIZED UPDATES FROM A SOCIAL NETWORK SITE TO A DESKTOP APPLICATION

• US 20090319577A1
• Filed: 06/23/2008
• Published: 12/24/2009
• Est. Priority Date: 06/23/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ming, Paul Richard Chen, Liu, Jiahe, Chandramouli, Deepa, Longino, Austin, Dolin, Robert M., Obasanjo, Oludare Victor
• Granted Patent: US 8,635,248 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method of providing updates from a social network to a desktop application is provided. An update is created in an application and if the application has permission, it creates an entry in a recent activity queue. The queue is then subject to analysis to reduce the number of entries in the queue. Subscribers that have permission to receive updates from the publisher and the publishing application then receive updates from the publisher.

Claims

1. A method of creating a notification of a change to a resource on a network comprising:

making the change to the resource in an application;

creating an update in the application to be communicated to a distribution list wherein the distribution list comprises a subscriber that selected to receive the update from a publisher and have permission to receive the update;

using the application to publish the update to a recent activity queue, wherein the update comprises at least one selected from a group comprising;

an application identifier wherein the application identifier comprises an identifier of the application that published the update;

a publisher identifier wherein the publisher identifier comprises an identifier of the publisher wherein the publisher pushes the update to the subscriber and wherein the subscriber opts to receive the update from the publisher;

a subscriber reference wherein the subscriber reference comprises the subscriber who should receive the update;

a reference to a user list wherein the user list comprises users who have access to the resource;

data and metadata related to the update to the resource being added to a queue; and

a template reference wherein the template reference comprises a template that should be used to determine how to render the update;

adding additional metadata as an object to the update, wherein the additional metadata comprises one selected from a group comprising;

action data that describes an action that caused the update;

description data that provides a description of the update;

a notion of the timeline in which updates happen; and

summary data that provides a textual summary of the update;

storing the update in the queue for distribution to the distribution list;

reviewing the queue using a collapse condition;

if elements in the queue match the collapse condition, collapsing the queue;

communicating the update from the queue to the distribution list where the update is received by a notification application.

2. The method of claim 1, further comprising receiving a response from the subscriber to the distribution list wherein the response comprises format data that represents supported a format wherein the format comprises a language.

3. The method of claim 2, further comprising responding to a computing device of the subscriber with the update in an acceptable format.

4. The method of claim 1, wherein the distribution list is an intersection of a provided list of the subscriber that has opted in to be notified and a list of users that have access to the resource.

5. The method of claim 1, wherein the distribution list is modifiable by the publisher.

7. The method of claim 1, wherein the network is a social network.

8. The method of claim 1, wherein the update is added to the queue according to a queue rule wherein the queue rule is at least one selected from a group comprising:

if the queue has a maximum number of entries, not adding the update to the queue;

if a contact has more than a threshold of entries in the queue, not adding the update to the queue; and

if an owner of the distribution list is listed as an initiator of the update, not adding entries to the queue.

9. The method of claim 1, wherein the collapse condition comprises at least one selected from a group comprising:

ensuring that old updates in the queue are replaced with new updates to the object;

allowing only one entry in the queue per the resource; and

replacing the update that is older for the resource with the update that is newer for the resource.

10. The method of claim 1, wherein if the publisher removes the update from the queue, it is removed from the notification application on a computing device of the subscriber.

11. The method of claim 1, wherein the update comprises at least one selected from a group comprising:

a public information update;

a media file; and

an advertisement.

12. The method of claim 11, wherein the update is matched to a relevancy condition and the update is communicated to members of the distribution list that matches the relevancy condition.

13. The method of claim 1, wherein the update that are previous are stored in a memory and are searchable.

14. The method of claim 1, wherein a subscriber name is specific to the application and the subscriber name from the application are matched against a second application subscriber name.

6. The method of claim 6, further comprising matching a permission list from the application to the permission list on a second application.

15. An application on a computing device of a subscriber for receiving notification of an update by a publisher to a resource on a social network comprising computer executable instructions for:

receiving the update from a distribution list;

analyzing the update comprising;

if there is an application identifier, reviewing the application identifier wherein the application identifier comprises an identifier of the application;

if there is a publisher identifier, reviewing the publisher identifier wherein the publisher identifier comprises an identifier for the publisher;

if there is a subscriber list reference, reviewing the subscriber list reference wherein a subscriber list comprises the subscriber that should receive the update;

if there is a user list reference, reviewing the user list reference wherein a user list comprises users who have access to the resource;

if there is data and metadata of the update, reviewing the data and the metadata of the update;

if there is a reference to a template, reviewing the reference to the template wherein the template comprises the template that should be used to determine how to render the update item;

analyzing metadata attached to the update as an object, wherein the metadata comprises at least one selected form a group comprising;

update data that describes an action that caused the update;

description data that provides a description of the update;

a notion of the timeline in which updates happen; and

summary data that provides a textual summary of the update;

using the template to open the update;

displaying the update on the application using the template.

16. The method of claim 15, further comprising responding with formats that are available on the application on the computing device of the subscriber wherein the formats comprise languages.

17. The method of claim 15, wherein the distribution list is an intersection of a provided list of subscribers to be notified and a list of users that have access to the resource.

18. The method of claim 15, wherein if a provider removes the update from a recent activity queue, it is removed from the application on the computing device of the subscriber.

19. The method of claim 15, wherein the update comprises at least one selected from a group comprising:

public information update;

a media file; and

an advertisement.

20. The method of claim 19, wherein the update is matched to a relevancy condition and the update is communicated to members of the distribution list that matches the relevancy condition.