Remote service invocation in heterogeneous networks

• US 20060248206A1
• Filed: 04/01/2003
• Published: 11/02/2006
• Est. Priority Date: 11/05/2002
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Elburg, Johannes Van, Bascunana-Munoz, Alejandro, Boersma, Eltjo, Moerdijk, Adriaan Jan, Karremans, Paulus
• Application Number:
  US10/533,327
• Publication Number:
  US 20060248206A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The invention provides a system and a method for providing those client applications having access to services in a first domain with access to services in another domain via a standardized interface such as the one specified under OSA/PARLAY standardization bodies. Therefore, in accordance with the invention, there is provided a framework-to-framework interface whereby a number of domains are enabled to offer services to another number of domains, and whereby a particular first framework in a first domain can proceed to discover available service enablers in other domains via corresponding second frameworks in said other domains. Thus, in accordance with the invention, a first domain is enabled to offer services to its client applications from a second domain in addition to those services already offered by said first domain itself. In addition the invention expands the system and method with ways to specify, communicate and enforce the agreements between the domains involved.

Claims

1. A telecommunications system arranged for providing client service applications with access to service capability features via a standardized interface, the system comprising:

a number of application servers where providing client service applications;

a number of first service enablers where first service capability features are specified in a first network domain;

a first Framework for providing a controlled access to said first service capability features;

a number of core network elements;

a number of second service enablers where second service capability features are specified in a second network domain;

a second Framework for providing a controlled access to said second service capability features;

wherein said first Framework is arranged for communicating with said second Framework for accessing said second service capability features specified in said number of second service enablers of said second network domain.

2. The telecommunications system of claim 1, wherein the first and second Frameworks comprise protocol means for allowing a framework-to-framework communication.

3. The telecommunications system of claim 2, wherein said protocol means includes means for advertising toward a first framework in a first network domain the existence of a second framework in a second network domain with which service capability features can be shared.

4. The telecommunications system of claim 3, wherein said protocol means includes means for advertising from a second framework in a second network domain towards a first framework in a first network domain that service capability features can be offered from service enablers of said second network domain to client applications of said first network domain.

5. The telecommunications system of claim 3, wherein the means for advertising towards a first framework the existence of a second framework includes means for the second framework registering itself in the first framework.

6. The telecommunications system of claim 3, wherein the means for advertising towards a first framework in a first domain the existence of a second framework in a second domain includes means for the operator of said first domain registering the second framework in the first framework.

7. The telecommunications system of claim 4, wherein the means for advertising service capability features that can be offered from service enablers of a second network domain includes means for notifying from a second framework in said second network domain towards a first framework in a first network domain at least one element of service information selected from a group of elements that comprises:

service identifier, service type, service availability, service properties and service interface.

8. The telecommunications system of claim 7, wherein the means for advertising the existence of service capability features available at service enablers of a second network domain includes means for creating, from a first framework in a first network domain toward a second framework in a second network domain, criteria for notification of such element of service information.

9. The telecommunications system of claim 1 further comprising means for carrying out security management mechanisms between a first framework in a first network domain and a second framework in a second network domain.

10. The telecommunications system of claim 9, wherein the means for carrying out security management mechanisms between said first and said second frameworks includes means for capturing service agreements between first and second domains, the service agreements representing a policy applied between said first and second domains.

11. The telecommunications system of claim 9, wherein the means for carrying out security management mechanisms between said first and said second frameworks includes means for handing over service assertions and signatures.

12. The telecommunications system of claim 1 further comprising means for discovering service capability features available at service enablers of a second network domain between a first framework in a first network domain and a second framework in a second network domain.

13. The telecommunications system of claim 12, wherein the means for discovering available service capability features between said first framework and said second framework includes means for negotiating specific capabilities as required by a client application in a first domain.

14. The telecommunications system of claim 13, further comprising means for returning from a second framework in a second network domain towards a first framework in a first network domain a reference to a service instance created at a service enabler of said second network domain, for allowing an application in the first network domain make use of corresponding service of the second network domain.

15. The telecommunications system of claim 1 further comprising a Service Enabler Proxy interposed between a first domain and a second domain and intended for acting as a Proxy for service requests from applications in the first domain toward service enablers of the second domain as well as communications in the opposite direction.

16. The telecommunications system of claim 15, wherein said Service Enabler Proxy is provided in a first domain and comprises a number of dedicated service capability features of said first domain for storing references of corresponding service capability features of a second domain.

17. The telecommunications system of claim 15, further comprising means for creating a Service Enabler Proxy automatically in the first domain based on information received from a framework in a second domain, said information including at least one element of service information selected from a group of elements that comprises:

service type, service properties and service interface.

18. The telecommunications system of claim 15, further comprising means for downloading source code or run-time code from the second domain intended to create a Service Enabler Proxy in the first domain.

19. The telecommunications system of claim 15, wherein a particular service enabler of a second domain is registered in a first framework of a first domain for acting as a Service Enabler Proxy towards a second domain.

20. The telecommunications system of claim 1, wherein the first network domain includes a Home core network of a user whereas the second network domain includes a Visited core network where the user is roaming.

21. A method of providing client service applications with access to service capability features via a standardized interface, the method comprising the steps of:

(a) registering first service capability features in a first network domain with a first Framework and second service capability features in a second network domain with a second Framework;

(b) carrying out security management mechanisms for authentication and authorization of a number of players selected from a group that includes user, network, a requester application, and combinations thereof, in each network domain through each respective Framework; and

(c) discovering first service capability features that are available for use by a requester application in said first network domain;

(d) determining in the first network domain that service capability features at a second network domain may be available for the requester application;

(e) carrying out security management mechanisms for authentication and authorization from a first Framework of said first network domain, through a second Framework of said second network domain; and

(f) discovering second service capability features that are available for use by said requester application in said second network domain.

22. The method of claim 21, wherein the step of determining that service capability features are available at a second network domain includes a step of requesting to the first Framework in the first network domain for an access to the second service capability features available in the second network domain for the requester application.

23. The method of claim 22, wherein the step of determining that second service capability features are available at a second network domain includes a step of receiving such information from a first service capability feature selected in the first network domain.

24. The method of claim 21, wherein the step of discovering second service capability features that are available in the second network domain comprises a step of negotiating capabilities from the first Framework of the first network domain with the second Framework of the second network domain.

25. The method of claim 24, wherein the step of negotiating capabilities includes a step of creating an instance of a selected service capability feature at a service enabler of a second domain, and a step of returning back a reference to such instance from the second Framework of the second network domain to the first Framework of the first network domain.

26. The method of claim 21, further comprising a step of registering a second Framework of a second network domain with a first Framework of a first network domain.

27. The method of claim 26, wherein the step of registering frameworks includes a step of registering the second Framework itself in the first Framework, and another step of registering the first Framework itself in the second Framework.

28. The method of claim 26, wherein the step of registering frameworks includes a step where the operator of a second (Donor) network domain registers a first Framework of a first network domain in a second Framework, and another step where the operator of a first network domain registers a second Framework of a second network domain in a first Framework.

29. The method of claim 26, further comprising a step of publishing at least one interface that allows said first and said second Frameworks to access the service capability features respectively controlled by each other.

30. The method of claim 21, further comprising a step of exchanging information between a first and a second Framework about available service capability features in a first and a second network domain respectively, with or without explicit indication of the interface required to access such service capability features.

31. The method of claim 30, further comprising a step of indicating to at least one first service capability feature in a first network domain the at least one second service capability feature available in a second network domain, and vice versa.

32. The method of claim 21, further comprising a step of capturing Service Level Agreements between the network operator of a network domain and a service provider of a requester application.

33. The method of claim 32, further comprising a step of capturing Service Level Agreements between a first and a second network domains through corresponding first and second Frameworks.

34. The method of claim 33, wherein said Service Level Agreements are extended between second domains and first domains in a telecommunication network with multiple domains, the method further comprising the steps of:

creating and assigning a Federation Service Profile on a Donor Framework;

signing a Federation Service Agreement on a Donor Framework;

installing in a Receiver Framework necessary information about a Donor Service for a client application being able to discover the Donor Service; and

requesting a Receiver Application Service Agreement within the bounds of a Federation Service Agreement from a Donor Framework.

35. The method of claim 34, wherein a Receiver Application Service Agreement serves as a partition of a Federation Service Agreement.

36. The method of claim 21, wherein the steps of carrying out security management mechanisms include the steps of handing out and handing over an Assertion that gives a practitioner the right to use a service in a federated framework setup.

37. The method of claim 36, further comprising the steps of:

handing over an Assertion by a Receiver Framework to any other entity;

signing an Agreement about the hand-out and/or hand-over of an Assertion;

requesting an Assertion; and

a Donor Service Enabler checking the validity of a received Assertion with a Donor Framework.

38. The method of claim 21, further comprising a step of creating in a first domain a Service Enabler Proxy arranged to act as a proxy for communicating with an instance of a selected second service capability feature at a service enabler of the second domain.

39. The method of claim 38, further comprising a step of enforcing service agreements and policies at the Service Enabler Proxy.

40. The method of claim 38, wherein the step of creating a Service Enabler Proxy in a first Framework of a first network domain includes a step of obtaining service information at the first network domain from a second network domain for least one element of service information selected from a group of elements that comprises:

service type, service properties and service interface.

41. The method of claim 38, wherein the step of creating a Service Enabler Proxy in a first Framework of a first network domain includes a step of downloading source code or run-time code from a second domain.

42. The method of claim 41, wherein the step of downloading source code or run-time code includes a step of downloading local policy enforcement rules.

43. The method of claim 38, wherein the step of creating a Service Enabler Proxy in a first Framework of a first network domain includes a step of registering a Service Enabler of a second domain in the first Framework of the first domain where both domains are allowed to set-up agreements and policies that need to be enforced by the Service Enabler.

44. The method of claim 38, wherein a Service Enabler Proxy is created by the first Framework for each client application.

45. The method of claim 38, wherein the step of creating a Service Enabler Proxy in a first Framework of a first network domain includes a step of creating instances of said Service Enabler Proxy for each client application.