Reference data aggregate service population

• US 20060271384A1
• Filed: 05/31/2005
• Published: 11/30/2006
• Est. Priority Date: 05/31/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Honeyman, Josh W., Anderson, Jeffrey R., Munson, Ryan A., Healy, John A.
• Application Number:
  US11/140,712
• Publication Number:
  US 20060271384A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

The present invention provides a method for registering a service with an aggregation service, and storing data within the aggregate service. The process of registration is performed by a service explicitly notifying or being discovered by the aggregation service. In one embodiment there are four steps to the registration process. The first step is determining existence of a service and there are two ways this can happen, discovery and explicit notification. The second step of the process is metadata retrieval. Once the existence of the service is determined, the aggregation service attempts to retrieve relevant metadata about the service. The third step is setting up how the aggregation service is populated. If it is to be populated via a push synchronization, entity create, update, and delete event subscriptions are created with the service so it will push its data to the aggregation service. If pull synchronization is used, a scheduled retrieval process is configured on the aggregation service so the service can pull data at scheduled intervals. The fourth step in the process is the initial population of the aggregation data store.

Claims

1. A method for registering a service with an aggregation service, comprising:

determining that the service is ready to register with the aggregation service;

obtaining metadata related to the new service;

obtaining existing data from the service; and

storing that existing data at the aggregation service.

2. The method of claim 1 further comprising:

generating subscriptions between the aggregation service and the new service.

3. The method of claim 2 wherein the subscriptions includes information related to the type of data and when it will be updated.

4. The method of claim 2 further comprising:

updating the data using the subscription.

5. The method of claim 3 wherein the update occurs at a predetermined time interval.

6. The method of claim 3 wherein the update occurs after a predetermined number of changes have occurred.

7. The method of claim 3 wherein the update occurs after each data change in the new service.

8. The method of claim 1 wherein determining comprises:

receiving a message from the service indicating that it is ready to register.

9. The method of claim 1 wherein determining comprises:

querying the network to determine if there are new services to be registered.

10. The method of claim 1 wherein obtaining metadata comprises:

querying the service for the metadata.

11. The method of claim 1 wherein obtaining metadata comprises:

receiving the metadata from the service.

12. The method of claim 1 wherein obtaining data comprises:

querying the new service for the data; and

receiving the data from the new service.

13. The method of claim 2 wherein generating a subscription comprises:

receiving a subscription request from the aggregation service; and

receiving a confirmation from the new service.

14. The method of claim 2 wherein generating a subscription comprises:

receiving subscription information from the new service at the aggregation service.

15. A computer readable medium configured with computer executable instructions to register a service with an aggregation service that when executed cause a computer to:

determine that the service is ready to register with the aggregation service;

obtain metadata for service public data;

obtain existing data from the service; and

store the existing data at the aggregation service.

16. The computer readable medium of claim 15 further including instructions to:

generate a subscription between the aggregation service and the new service.

17. The computer readable medium of claim 16 further including instructions to:

update the data in the aggregate service using the subscription.

18. The computer readable medium of claim 15 wherein the medium is further configured to:

receive a message from the service indicating that it is ready to register.

19. The computer readable medium of claim 18 wherein the medium is further configured to:

send a query to the service.

20. The computer readable medium of claim 15 wherein the medium is further configured to:

query the service for the data; and

receive the data from the new service.