Directory service for a computer network

• US 20050027795A1
• Filed: 08/04/2004
• Published: 02/03/2005
• Est. Priority Date: 08/24/1998
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Nolan, Sean P., Sanderman, David S., San Andres, Ramon J.
• Granted Patent: US 7,305,451 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

A distributed directory service for an on-line services network comprises multiple, separate services, referred to as “Directory Service Providers,” running on respective groups of application servers. Each Directory Service Provider stores and provides access to a respective hierarchical directory structure, with nodes of the directory structures representing the various on-line services and other content entities which may be accessed by end users of the network. Junction point nodes are used to provide user-transparent links between the different directory structures, so that the directory structures appear to end users as a single, hierarchical directory. A common application program interface (API) is implemented by all Directory Service Providers, allowing client applications running on computers of end users to access the different directory structures using a common set of software methods. Data items that are shared by multiple nodes, such as icon bitmaps and sound files, are optionally stored by the Directory Service Providers within a shared database (separately from the nodes), and are accessed via special API methods. Various forms of node filtering, including language-based filtering and access rights filtering, are performed by the Directory Service Providers to determine which nodes to show to end users.

Claims

1. A directory service for a computer network, comprising:

a first service application running on a first group of application servers to implement a first service, said first service storing a first plurality of content nodes that represent a first plurality of content entities of said computer network, said first plurality of content entities accessible to users of said computer network via said first service;

a second service application running on a second group of application servers to implement a second service, said second service storing a second plurality of content nodes that represent a second plurality of content entities of said computer network, said second plurality of content entities accessible to said users of said computer network via said second service; and

an interface that links said first service to said second service to provide an integrated directory service.

2. A directory service according to claim 1, wherein said first and second pluralities of content nodes represent on-line services and associated data entities of an on-line services network.

3. A directory service according to claim 1, wherein said interface comprises a junction point node, said junction point node being one of said first plurality of content nodes, said junction point node comprising a reference to a corresponding node of said second plurality of content nodes.

4. A directory service according to claim 3, wherein said junction point node provides a user-transparent link from said first service to said second service.

5. A directory service according to claim 3, wherein said junction point node serves as a proxy for said corresponding node.

6. A directory service according to claim 1, wherein each node of said first and second pluralities of content nodes comprises a respective list of node properties.

7. A directory service according to claim 6, wherein said list comprises a set of required properties that are required of all content nodes of the directory service.

8. A directory service according to claim 1, wherein at least one of said content nodes includes a service-specific property, said service-specific property corresponding to a particular on-line service other than said first service or said second service.

9. A directory service according to claim 1, wherein said first and second service applications provide access to said first and second pluralities of content nodes, respectively, via a common application program interface (API).

10. A directory service according to claim 9, wherein said API returns properties of said first and second pluralities of content nodes in response to requests from client applications.

11. A directory service according to claim 10, wherein at least some of said requests comprise language filters, and wherein said first and second services apply said language filters to determine which content nodes to return to said client applications.

12. A directory service according to claim 10, wherein at least some of said requests comprise geographic region filters, and wherein said first and second services apply said geographic region filters to determine which content nodes to return to said client applications.

13. A directory service according to claim 10, wherein at least some of said requests comprise variable-length lists of property names, and wherein said API returns properties to said client applications according to said variable-length lists, said API thereby conserving bandwidth over communications channels which link said client applications to said directory service by returning only those properties specifically requested by said client applications.

14. A directory service according to claim 1, wherein said first plurality of content nodes is arranged by said first service within a first acyclic graph structure, and wherein said second plurality of content nodes is arranged by said second service within a second acyclic graph structure.

15. A directory service according to claim 14, further comprising a client application configured to run on a computer of a user, said client application configured to send requests to said first and second services for properties of said first and second pluralities of content nodes, said client application further configured to receive said properties from said first and second services and to reconstruct said first and second acyclic graph structures on a screen of said computer.

16. A directory service according to claim 15, wherein said client application is configured to reconstruct said first and second acyclic graph structures on said screen as a single, integrated graph structure, so that said user sees a single hierarchical directory of said first and second pluralities of content entities.

17. A directory service according to claim 1, wherein said first group of application servers comprises a first plurality of applications servers, and wherein said second group of application servers comprises a second plurality of applications servers.

18. A directory service according to claim 17, wherein each node of said first plurality of content nodes is stored on each server of said first plurality of application servers, and wherein each node of said second plurality of content nodes is stored on each server of said second plurality of application servers.

19. A directory service according to claim 17, wherein said application servers of said first and second groups are interconnected by a local area network.

20. A directory service according to claim 1, wherein at least one of said content nodes includes an icon identifier, said icon identifier referencing a bitmap of an icon for said at least one content node, said icon bitmap stored separately from said at least one content node.

21. A directory service according to claim 1, wherein said first service implements a remote properties cache, said remote properties cache storing node properties received from a remote service, said remote service implemented on a separate group of application servers from said first group of application servers, said remote properties stored in said cache in association with individual nodes of said first plurality of content nodes.

22. A directory service according to claim 21, wherein said first service generates requests to said remote service for said remote properties in response to requests from client applications.

23. A directory service according to claim 21, wherein said first service periodically deletes node properties from said remote properties cache so that property data stored in said cache is up-to-date.

24. A directory service according to claim 1, wherein said first service provides a general-purpose directory service which stores content nodes of multiple different online services, and wherein said second service provides a service-specific directory service which stores content nodes of a single on-line service.

25. A directory service according to claim 1, wherein at least some content nodes of said first plurality of content nodes represent content entities stored on application servers other than said application servers of said first and second groups.

26. A directory service according to claim 1, further comprising a plurality of shared data items stored on said first group of application servers separate from said first plurality of nodes, each of said shared data items being shared by multiple nodes of said first plurality of content nodes, said shared data items downloadable via said first service to computers of said users.

27. A directory service according to claim 26, wherein said shared data items comprise at least one of:

icon bitmaps, sound files, banner objects, and download-and-run files.

28. A directory service according to claim 26, wherein at least some nodes of said first plurality of content nodes comprise shared data item identifiers which identify individual ones of said shared data items.

69. A directory service system according to claim 1, further comprising a client application that runs on a computer of a user and communicates with the first and second service applications via the navigation API, the client application configured to request node properties from the first and second service applications over a network in response to actions of the user, and to use node properties returned by the first and second service applications to generate and display a browsable directory structure of content nodes.

29-68. -68. (Canceled)

70-71. -71. (Canceled)