System and method for providing notifications in a communities framework

• US 7,590,687 B2
• Filed: 03/06/2006
• Issued: 09/15/2009
• Est. Priority Date: 11/17/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Pepper, Stephen L., Frender, Kevin Blair, Beartusk, Brodi, Bales, Christopher E., Olander, Daryl B., O'Neil, Edward K., Feit, Richard
• Primary Examiner(s): Chan; Wing F
• Assistant Examiner(s): WILLIS, JONATHAN U
• Application Number:
  US11/368,865
• Publication Number:
  US 20070110231A1
• Time in Patent Office: 1,289 Days
• Field of Search: 380/30, 709/220, 709/221, 709/229, 709/228, 709/216, 709/213, 709/214, 709/215, 709/205, 709/248, 709/203, 709/200, 709/207, 718/104, 718/107, 711/150, 711/100, 707/201, 707/203, 707/205, 707/102, 707/9, 707/8, 707/100
• US Class Current: 709/203
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A community enables user membership in a distributed collaborative computing environment. The members can have access to a repository of resources. Dynamic notifications between client and server can be provided. A member can be logged onto a client which pings the server computer through no interaction of the user. A notifications manager located on the server can retrieve updates available for the member in response to each ping. The notifications manager can look up any changes to the resources that the member has subscribed to. The server can subsequently notify the client of the available updates. The client'"'"'s user interface can be updated to reflect the relevant changes. A dynamic and granular interaction between the server and the client can be enabled instead of updating the entire portal page. Each ping can carry an id of the member and community, which the server can use to determine the relevant updates.

Claims

1. A notification system for a communities framework, comprising:

a client and a server connected to a network and configured to communicate with each other, wherein the client consecutively pings the server for notifications; and

a repository connected to the network, wherein the repository contains a set of resources in a plurality of nodes; and

a community of user members that can access and share the resources wherein at least one member is logged onto the client computer; and

a notification manager located on the server wherein the notifications manager retrieves updates to the set of resources from the repository in response to each ping; and

an extensible control for performing create, read, update and delete (CRUD) operations on a node contained in the repository; and

a generic control for wrapping the extensible control, wherein the generic control handles business logic using a content object associated with the node contained in the repository;

wherein the notification manager notifies the member logged onto the client computer of announcements about the updates to the set of resources in the repository, wherein the notification manager uses the generic control to notify proper recipients of their respective announcement associated with different nodes within the repository after receiving a ping, wherein the generic control uses the extensible control to handle interactions with the different nodes contained in the repository;

wherein each of the plurality of nodes interacts directly with the extensible control, and is also associated with the node wrapper that provides simplified and indirect access to the node for the generic control.

2. The notification system of claim 1 further comprising:

a subscription service that allows the at least one member to register to receive notifications of updates to a specified resource.

3. The notification system of claim 2 wherein the notification manager updates the client'"'"'s user interface with a new data determined from the subscription service in response to the ping.

4. The notification system of claim 1 further comprising:

a timer listener object that invokes the notification manager upon expiration of a specified time period.

5. The notification system of claim 1 further comprising:

a notification resource created and stored in the repository wherein the notification resource is sent and displayed to the at least one member logged onto the client computer.

6. The notification system of claim 1 wherein the client is configured to consecutively ping the server after every expiration of a time period specified by a user.

7. The notification system of claim 1 wherein a user is notified of updates to at least one of announcements, emails, tasks and invitations.

8. The notification system of claim 1 further comprising:

a notification center portlet for displaying and organizing a new data available for the client on the client'"'"'s user interface.

9. The notification system of claim 1 wherein the members are provided a portal interface to access the resources of the community, the portal interface containing a portal page.

10. The notification system of claim 9 wherein a portion of the portal page is dynamically updated by the notification manager in response to the ping.

11. The notification system of claim 1 further comprising:

an announcement resource stored in a database, wherein the announcement resource contains a message directed to one or more members of the community wherein the announcement resource has an expiration date attribute that determines when an announcement expires.

12. The notification system of claim 11 wherein a notification resource is created for the announcement and sent to appropriate recipient member of the announcement.

13. The notifications system of claim 11 wherein each ping carries an identification of the at least one member logged onto the client that the notifications manager can use to determine which notifications need to be provided to the client.

14. A method for providing notifications in a communities framework, comprising:

providing a network with a server and client connected thereto, wherein the server and the client communicate with each other;

providing a repository connected to the network, wherein the repository contains a set of resources in a plurality of nodes;

providing a notification manager on the server for sending notifications to users on the client;

providing an extensible control for performing create, read, update and delete (CRUD) operations on a node contained in the repository; and

providing a generic control for wrapping the extensible control, wherein the generic control handles business logic using a content object associated with the node contained in the repository;

pinging the server by the client;

determining the identity of the user on the client by the notification manager;

determining relevant new data available for the user;

acquiring the relevant new data; and

notifying the client with an announcement that indicates that the new data is available, wherein the notification manager uses the generic control to notify proper recipients of their respective announcement associated with different nodes within the repository after receiving a ping, wherein the generic control uses the extensible control to handle interactions with the different nodes contained in the repository;

wherein each of the plurality of nodes interacts directly with the extensible control, and is also associated with the node wrapper that provides simplified and indirect access to the node for the generic control.

15. The method of claim 14 wherein the user is allowed to register to receive notifications of updates to a specified resource.

16. The method of claim 14 wherein the notification manager updates the client'"'"'s user interface with the new data determined from a subscription service in response to the ping.

17. The method of claim 14 further comprising:

providing a timer listener object that invokes the notification manager upon expiration of a specified time period.

18. The method of claim 14 further comprising:

creating a notification resource and storing said notification resource in a repository wherein the notification resource is sent and displayed to the user logged onto the client computer.

19. The method of claim 14 wherein the client is configured to consecutively ping the server after every expiration of a time period specified by the user.

20. The method of claim 14 wherein the user is notified of updates to at least one of announcements, emails, tasks and invitations.

21. The method of claim 14 further comprising:

displaying and organizing the new data available for the user on the client'"'"'s user interface.

22. The method of claim 14 wherein the user is provided a portal interface to a community, the portal interface containing a portal page.

23. The method of claim 22 wherein a portion of the portal page is dynamically updated by the notification manager in response to the ping.

24. The method of claim 14 further comprising:

providing an announcement resource stored in a repository, wherein the announcement resource contains a message directed to one or more members of a community and wherein the announcement resource has an expiration date attribute that determines when the announcement expires.

25. The notification system of claim 24 wherein a notification resource is created for the announcement and sent to appropriate recipient member of the announcement.

26. A computer-readable storage medium having instructions stored thereon that when executed by one or more processors cause one or more processors to:

provide a network with a server and client connected thereto, wherein the server and the client communicate with each other;

provide a repository connected to the network, wherein the repository contains a set of resources in a plurality of nodes;

provide a notification manager on the server for sending notifications to users on the client;

provide an extensible control for performing create, read, update and delete (CRUD) operations on a node contained in the repository;

provide a generic control for wrapping the extensible control, wherein the generic control handles business logic using a content object associated with the node contained in the repository;

ping the server by the client;

determine the identity of the user on the client by the notification manager;

determine relevant new data available for the user;

acquire the relevant new data; and

notify the client with an announcement that indicates that the new data is available, wherein the notification manager uses the generic control to notify proper recipients of their respective announcement associated with different nodes within the repository after receiving a ping, wherein the generic control uses the extensible control to handle interactions with the different nodes within contained in the repository;

wherein each of the plurality of nodes interacts directly with the extensible control, and is also associated with the node wrapper that provides simplified and indirect access to the node for the generic control.