Content based messaging for e-learning including the extension of a remote procedure call

• US 20040045017A1
• Filed: 09/03/2002
• Published: 03/04/2004
• Est. Priority Date: 09/03/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Dorner, Elmar, Grossmann, Markus
• Granted Patent: US 7,146,616 B2
• Time in Patent Office: Days
• US Class Current: 719/330
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 12/1895 for short real-time information, e.g. alarms, notifications, alerts, updates
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A content based messaging-remote procedure call (CBM-RPC) protocol is provided as an extension of a CBM system that allows an application to directly access a remote procedure and, for example, obtain data returned by the procedure (e.g., stored in an associated database or storage device). An application may specify a procedure name (e.g., a unique identification (ID), such as a uniform resource identification (URI)) and parameters (e.g., a list of name/value-pairs) in a request (or a CBM-RPC), which is published to a CBM network. One or more, procedures or functions may subscribe to the request and generate responses (e.g., the requested information or a fault if the request is not valid) that are published to the CBM network.

Claims

1. A content based messaging (CBM) system including the extension of a remote procedure call (RPC) comprising:

an application to publish a CBM-RPC request;

a CBM network to receive the published CBM-RPC request and to transmit a request notification; and

a remote procedure subscribing to the notification request to receive the notification request, process the request, publish a return.

2. The system of claim 1 wherein the CBM network is configured to receive the published return, determine the application subscribing to the return, and to publish the return event.

3. The system of claim 1 wherein the CBM network determines the remote procedure based on a subscription to the CBM network from the remote procedure.

4. The system of claim 1 wherein the CBM network determines the remote procedure based on a subscription to the CBM network from the remote procedure and a request identifier.

5. The system of claim 4 wherein the request identifier includes a namespace to distinguish between procedures that have the same name.

6. The system of claim 4 wherein the request identifier includes a service class used to group one or more procedures into a logical family of one or more procedures.

7. The system of claim 4 wherein the request identifier includes a procedure name.

8. The system of claim 4 wherein the request identifier request includes an identifier of the application, a namespace, a service class.

9. The system of claim 4 wherein the request identifier includes a request identification to distinguish between calls from the same application and to match calls to returns.

10. The system of claim 1 wherein the request includes a procedure identification and parameters.

11. The system of claim 10 wherein the parameters are name and value pairs.

12. The system of claim 1 wherein the return includes information requested by the application.

13. The system of claim 1 wherein the return includes a fault if the request is not valid.

14. The system of claim 1 wherein the request includes an request identifier.

15. The system of claim 14 wherein the request identifier includes a namespace to distinguish between procedures that have the same name.

16. The system of claim 14 wherein the request identifier includes a service class used to group one or more procedures into a logical family of one or more procedures.

17. The system of claim 14 wherein the request identifier includes a procedure name.

18. The system of claim 14 wherein the request identifier request includes an identifier of the application, a namespace, a service class.

19. The system of claim 14 wherein the request identifier includes a request identification to distinguish between calls from the same application and to match calls to returns.

20. The system of claim 2 further comprising a database wherein the remote procedure is configured to access the database and to include information in the published return based on the accessed data.

21. The system of claim 2 wherein the remote procedure is a state access function to access learner information stored in the database.

22. A method for making a content based messaging (CBM)-remote procedure call (RPC) comprising:

receiving a published CBM-RPC request from an application;

transmitting a request notification to a remote procedure; and

receiving a published return from the remote procedure, which subscribes to the notification request.

23. The method of claim 22 further comprising receiving the published return, determining the application subscribing to the return, and publishing the return event.

24. The method of claim 22 further comprising determining the remote procedure based on a subscription from the remote procedure.

25. The method of claim 22 further comprising determining the remote procedure based on a subscription from the remote procedure and based on a request identifier of the CBM-RPC request.

26. The method of claim 25 wherein determining the remote procedure includes determining a namespace of the request identifier to distinguish between procedures that have the same name.

27. The method of claim 25 wherein determining the remote procedure includes determining a service class of the request identifier used to group one or more procedures into a logical family of one or more procedures.

28. The method of claim 25 wherein determining the remote procedure includes determining a procedure name of the request identifier.

29. The method of claim 25 wherein determining the remote procedure includes determining an identifier of the application, a namespace, a service class.

30. The method of claim 25 wherein the determining the remote procedure includes determining a request identification to distinguish between calls from the same application and to match calls to returns.

31. The method of claim 22 wherein receiving the request includes receiving a procedure identification and parameters.

33. The method of claim 22 wherein receiving the return includes receiving information requested by the application.

34. The method of claim 22 wherein receiving the return includes receiving a fault if the request is not valid.

35. The method of claim 22 wherein receiving the request includes receiving a request identifier of the CBM-RPC request.

36. The method of claim 35 wherein receiving the request identifier includes receiving a namespace to distinguish between procedures that have the same name.

37. The method of claim 35 wherein receiving the request identifier includes receiving a service class used to group one or more procedures into a logical family of one or more procedures.

38. The method of claim 35 wherein receiving the request identifier includes receiving a procedure name.

39. The method of claim 35 wherein receiving the request identifier includes receiving an identifier of the application, a namespace, a service class.

40. The method of claim 35 wherein receiving the request identifier includes receiving a request identification to distinguish between calls from the same application and to match calls to returns.

41. The method of claim 23 wherein receiving the return includes receiving information based on data accessed from a remote database wherein the remote procedure is configured to access the database.

42. The method of claim 23 wherein receiving a return from the remote procedure includes receiving a return from a state access function that accesses learner information stored in the database.

32. The method of claim 32 wherein receiving the request includes receiving parameters that are name and value pairs.