Profile service

• US 6,542,515 B1
• Filed: 05/19/1999
• Issued: 04/01/2003
• Est. Priority Date: 05/19/1999
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Kumar, Ravi, Weschler, Paul William Jr.
• Primary Examiner(s): Kizou, Hassan
• Assistant Examiner(s): Hoang, Thai D
• Application Number:
  US09/314,789
• Time in Patent Office: 1,413 Days
• Field of Search: 370/401, 370/466, 370/467, 370/352, 370/463, 709/201-203, 709/220-222, 709/223, 709/225, 707/3-6, 707/8-10, 707/102, 707/103-R-1
• US Class Current: 370/463
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A mechanism for managing a plurality of profile data structures including a plurality of profile objects having an interface for sending and receiving information and a profile service mechanism having an interface for sending and receiving information. A protocol layer operatively coupled to the profile objects interface and the profile service interface, the protocol layer defining a plurality of request elements and a plurality of response elements. A protocol layer interface within the protocol layer receives user-entity specified set of request elements from the user entity and sends a responsive set of response elements to the user entity. A first set of methods within the profile service mechanism that create instances of the profile objects, where each of the first set of methods correspond to one of the request elements and one of the response elements. A second set of methods within the profile objects that manipulate instances of the profile objects, where each of the second set of methods correspond to one of the request elements and one of the response elements.

Claims

1. A mechanism for managing a plurality of profile data structures, each profile data structure comprising a hierarchical structure of attributes, where each attribute comprises information about an entity, the mechanism comprising:

a plurality of profile objects having an interface for sending and receiving information;

a profile service mechanism having an interface for sending and receiving information;

a protocol layer operatively coupled to the profile objects interface and the profile service interface, the protocol layer defining a plurality of request elements and a plurality of response elements;

protocol layer interface within the protocol layer receiving user-entity specified set of request elements from the user entity and sending a responsive set of response elements to the user entity;

a first set of methods within the profile service mechanism that create instances of the profile objects, wherein each of the first set of methods correspond to one of the request elements and one of the response elements; and

a second set of methods within the profile objects that manipulate instances of the profile objects, wherein each of the second set of methods correspond to one of the request elements and one of the response elements.

2. The mechanism of claim 1 wherein the protocol layer defines a mark-up language document in which a set of request elements selected by the user entity are embedded.

3. The mechanism of claim 1 wherein the protocol layer defines a mark-up language document in which a set of response elements selected by the user entity are embedded.

4. The mechanism of claim 2 wherein the markup language document comprises an XML document.

5. The mechanism of claim 1 wherein the protocol layer interface comprises a hypertext transfer protocol (HTTP).

6. The mechanism of claim 1 wherein each request element has a unique ID and each response element is given an ID corresponding to the request ID to which it is responsive.

7. The mechanism of claim 1 wherein the first set of methods comprise factory methods, profile retrieval methods, profile search methods, schema methods, and external data store methods.

8. The mechanism of claim 1 wherein the second set of methods comprise attribute manager methods, meta-data manager methods, subprofile binding methods, profile search methods, schema methods, template methods, and control methods.

9. The mechanism of claim 1 further comprising a plurality of entity profile objects that are extensions of the profile objects, the entity profile objects including a distinct set of entity methods with respect to the profile objects, wherein each of the entity methods correspond to one of the request elements and one of the response elements.

10. The mechanism of claim 1 further comprising a plurality of profile list objects that are extensions of the profile objects, the profile list objects including a distinct set of profile list methods with respect to the profile objects, wherein each of the profile list methods correspond to one of the request elements and one of the response elements.

11. A program interface for integration with a service software program having a plurality of defined methods, each method configured to receive one or more arguments, the interface comprising:

a client software program generating a set of service request messages to be satisfied by the service software program, each request message specifying one of the plurality of methods and including any necessary arguments for the specified method;

a client-side protocol mechanism formatting the service request messages into a mark-up language request document;

a client-side transport protocol layer embedding the mark-up language request document into a transportable data packet;

a server-side transport protocol layer receiving the transportable data packet and extracting the mark-up language request document from the transportable data packet; and

a service-side protocol layer coupled to receive the mark-up language document, extract a set of request messages and pass each request messages to the service software program specified in the request message.

12. The interface of claim 11 wherein the service-side protocol layer is further coupled to receive response messages generated by the service software application and format the response messages into a markup language response document for transport to the client software program.

13. The interface of claim 11 wherein the transport protocol layers comprise hypertext transport protocol (HTTP) devices.

14. The interface of claim 13 wherein the transportable data packet comprises an HTTP post packet.

15. The interface of claim 13 wherein the transportable data packet comprises an HTTP get packet.

16. The interface of claim 11 wherein the client-side protocol mechanism comprises an extensible markup language mechanism.

17. The interface of claim 16 wherein the markup language document comprises an extensible markup language (XML) document having a data type definition (DTD) including a number of request elements, each request element indicating a specified method and an argument required by the specified method.

18. The interface of claim 12 wherein:

each markup language request document comprises a plurality of request elements, each request element having a unique ID associated therewith; and

the markup language response document comprises a plurality of response elements each response element having a tag indicating the unique ID of a request element to which it is responsive.

19. A method for accessing a profile server, the profile server managing a plurality of profile objects, each of the profile objects including a first set of methods for manipulating attributes contained in the profile object, the method comprising the steps of:

creating an instance of a profile service mechanism having a second set of methods defining a first interface for communicating with a user entity and a second interface for communicating the plurality of profile objects;

using an external software application, generating a request message identifying one of the methods in the first and second set of methods;

formatting the request message as an extensible markup language (XML) request document;

embedding the XML document in an HTTP transport packet;

communicating the HTTP transport packet to the profile service mechanism;

extracting the embedded, formatted request message from the XML document; and

directing the extracted request message to the method identified in the request message.

20. The method of claim 19 further comprising the step of including argument data with the request message.

21. The method of claim 19 further comprising the steps of:

using the identified method, generating a response message in response to the request message;

formatting the response message as an XML response document;

embedding the XML response document as an HTTP transport packet; and

communicating the HTTP transport packet to the external software application.

22. The method of claim 21 wherein the request document uniquely identifies each formatted request message and the response document includes a tag indicating the formatted request message to which it is responsive.

23. A computer program product embodied in a tangible form comprising:

computer program devices readable by a data processor coupled to receive the propagating signal for interfacing with a profile data service, the computer program product comprising;

first program code devices configured to cause a data processor to create an creating an instance of a profile service mechanism having a second set of methods defining a first interface for communicating with a user entity and a second interface for communicating the plurality of profile objects;

second program code devices configured to cause a data processor to generating a request message identifying one of the methods in the first and second set of methods;

third program code devices configured to cause the data processor to format the request message as an extensible markup language (XML) request document;

fourth program code devices configured to cause the data processor to embed the XML document in an HTTP transport packet;

fifth program code devices configured to cause the data processor to communicate the HTTP transport packet to the profile service mechanism;

sixth program code devices configured to cause the data processor to extract the embedded, formatted request message from the XML document; and

seventh program code devices configured to cause the data processor to direct the extracted request message to the method identified in the request message.

24. The computer program product of claim 23 wherein the tangible form comprises a magnetic disk.

25. The computer program product of claim 23 wherein the tangible form comprises an optical disk.

26. The computer program product of claim 23 wherein the tangible form comprises a propagating signal.

27. The computer program product of claim 23 wherein the tangible form comprises a random access memory device.

28. A mechanism for accessing a profile server comprising:

means within the profile server for managing a plurality of profile objects, each of the profile objects including a first set of methods for manipulating attributes contained in the profile object, the method comprising the steps of;

means for creating an instance of a profile service mechanism having a second set of methods defining a first interface for communicating with a user entity and a second interface for communicating the plurality of profile objects;

means for generating a request message identifying one of the methods in the first and second set of methods;

means for formatting the request message as an extensible markup language (XML) request document;

means for embedding the XML document in an HTTP transport packet;

means for communicating the HTTP transport packet to the profile service mechanism;

means for extracting the embedded, formatted request message from the XML document; and

means for directing the extracted request message to the method identified in the request message.