Method and system for realizing a rendezvous service in a management operations center implemented in a global ecosystem of interrelated services

• US 20020147611A1
• Filed: 03/29/2002
• Published: 10/10/2002
• Est. Priority Date: 05/22/2000
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Greene, William S., Pierret, Matthew C.
• Granted Patent: US 8,856,087 B2
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 10/063112 Skill-based matching of a person or a group to a task
• CPC Class Codes: G06Q 10/06314 Calendaring for a resource
• CPC Class Codes: G06Q 10/06398 Performance of employee with respect to a job function
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0661 by reconfiguring faulty entities
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 61/4553 Object oriented directories, e.g. common object request broker architecture [CORBA] name server
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/123 : received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/54 : Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: Y10S 707/99931 : Database or file accessing

Abstract

In accordance with an exemplary embodiment of the present invention, a rendezvous service is presented for the NewWave service platform. Events are accessed and bound with other events and associated data based on the type of initial event received. A key function of the rendezvous service is to reduce the number of simultaneously active duplicative works that are created due to events being mis-categorized. This is achieved is several ways. First, where events are accessed and bound into a work item with other associated data based on the type of event, the rendezvous service binds later arriving events to the work item, thus reducing the possibility of an additional work item being created for the newly-arrived event. Second, the rendezvous service compares entire work items based on rules and appropriate logic to determine whether two work items are so related that they may be combined or handled by an existing work item. Third, multiple rendezvous services can be deployed simultaneously using different rules for determining overlap by different parameters, such as having different services consulting different views of topology. Thus, existing work items are compared for perspectives different that the perspective which originally caused the work item to be created.

Claims

1. A data processing system implemented method for rendezvousing events comprising:

receiving a plurality of events;

accessing each of the plurality of events to identify a plurality of types of events;

aggregating at least some of the plurality of events into a plurality of items, wherein each of the plurality of items is aggregated by;

binding an other event of the plurality of events to an event identified as a particular type of event of the plurality of types of events based on a correspondence between the other event and the particular type of event; and

binding additional information to the event identified as the particular type of event of the plurality of types of events based on a relationship between the additional information and the particular type of event; and

rendezvousing one of the plurality of items with an event of the plurality of events.

2. The method recited in claim 1, wherein rendezvousing one of the plurality of items with the event is based on a relationship between the one of the plurality of items and the event.

3. The method recited in claim 2, wherein the event is aggregated into another one of the plurality of items, the method further comprises:

combining an other event of the plurality of events with the one of the plurality of items, wherein the an other event of the plurality of events was bound to the another one of the plurality of items; and

removing the event from the another one of the plurality of items.

4. The method recited in claim 2, wherein the event is aggregated into another one of the plurality of items, the method further comprises:

combining an other event of the plurality of events with the one of the plurality of items, wherein the an other event of the plurality of events was bound to the another one of the plurality of items;

combining additional information with the one of the plurality of items, wherein the additional information was bound to the another one of the plurality of items; and

deactivating the another one of the plurality of items.

5. The method recited in claim 2, wherein the event is aggregated into another one of the plurality of items and additional information is bound to the another one of the plurality of items, the method further comprises:

acting on the additional information is bound to the another one of the plurality of items.

6. The method recited in claim 5, wherein the additional information is a contact for the another one of the plurality of items and acting on the additional information comprises:

communicating with the contact for the another one of the plurality of items, wherein a communication includes the particular type of event identified in the one of the plurality of items, the other event of the plurality of events bound to the particular type of event of the plurality of types of events, and the additional information bound to the event identified as the particular type of event.

7. The method recited in claim 5, wherein the additional information includes invitations for inviting contacts to participate in the another one of the plurality of items and acting on the additional information comprises:

inviting contacts to participate in the one of the plurality of items which have been invited to participate on the another one of the plurality of items.

8. The method recited in claim 1, wherein rendezvousing one of the plurality of items to an event of the plurality of events reduces the total amount of items in the plurality of items.

9. The method recited in claim 1, wherein rendezvousing is performed by a plurality of rendezvous services, such that each of the plurality of rendezvous services employs different rules for determining whether a relationship exists between the one of the plurality of items and the event.

10. The method recited in claim 1, wherein the event of the plurality of events is not identifiable as a type of the plurality of types of events and is not bound to any event identified as a particular type of event of the plurality of types of events.

14. The program product recited in claim 2, wherein the event is aggregated into another one of the plurality of items, the program product further comprises:

instruction for combining an other event of the plurality of events with the one of the plurality of items, wherein the an other event of the plurality of events was bound to the another one of the plurality of items;

instruction for combining additional information with the one of the plurality of items, wherein the additional information was bound to the another one of the plurality of items; and

instruction for deactivating the another one of the plurality of items.

11. A data processing system implemented program product embodied on a data processing system readable medium for implementing a method for rendezvousing events, said program product comprising:

instruction for receiving a plurality of events;

instruction for accessing each of the plurality of events to identify a plurality of types of events;

instruction for aggregating at least some of the plurality of events into a plurality of items, wherein each of the plurality of items is aggregated by;

instruction for binding an other event of the plurality of events to an event identified as a particular type of event of the plurality of types of events based on a correspondence between the other event and the particular type of event; and

instruction for binding additional information to the event identified as the particular type of event of the plurality of types of events based on a relationship between the additional information and the particular type of event; and

instruction for rendezvousing one of the plurality of items with an event of the plurality of events.

12. The program product recited in claim 11, wherein the instruction for rendezvousing one of the plurality of items with the event is based on a relationship between the one of the plurality of items and the event.

13. The program product recited in claim 12, wherein the event is aggregated into another one of the plurality of items, the program product further comprises:

instruction for combining an other event of the plurality of events with the one of the plurality of items, wherein the an other event of the plurality of events was bound to the another one of the plurality of items; and

instruction for removing the event from the another one of the plurality of items.

15. The program product recited in claim 12, wherein the event is aggregated into another one of the plurality of items and additional information is bound to the another one of the plurality of items, the program product further comprises:

instruction for acting on the additional information is bound to the another one of the plurality of items.

16. The program product recited in claim 15, wherein the additional information is a contact for the another one of the plurality of items and the instruction for acting on the additional information comprises:

communicating with the contact for the another one of the plurality of items, wherein a communication includes the particular type of event identified in the one of the plurality of items, the other event of the plurality of events bound to the particular type of event of the plurality of types of events, and the additional information bound to the event identified as the particular type of event.

17. The program product recited in claim 15, wherein the additional information includes invitations for inviting contacts to participate in the another one of the plurality of items and the instruction for acting on the additional information comprises:

instruction for inviting contacts to participate in the one of the plurality of items which have been invited to participate on the another one of the plurality of items.

18. The program product recited in claim 11, wherein the instruction for rendezvousing one of the plurality of items to an event of the plurality of events reduces the total amount of items in the plurality of items.

19. The program product recited in claim 11, wherein instruction for rendezvousing is performed by a plurality of rendezvous services, such that each of the plurality of rendezvous services employs different rules for determining whether a relationship exists between the one of the plurality of items and the event.

20. The program product recited in claim 11, wherein the event of the plurality of events is not identifiable as a type of the plurality of types of events and is not bound to any event identified as a particular type of event of the plurality of types of events.