Arrangement for simplifying the design and implementation of mobile services in a communication system

• US 6,964,050 B1
• Filed: 10/05/1999
• Issued: 11/08/2005
• Est. Priority Date: 04/08/1997
• Status: Expired due to Term

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Do, Thanh Van
• Primary Examiner(s): An, Meng-Al T.
• Assistant Examiner(s): ANYA, CHARLES E
• Application Number:
  US09/412,334
• Time in Patent Office: 2,226 Days
• Field of Search: 455403-420, 455436-460, 455 301- 306, 709313-317, 709201-207, 709217-229, 709/249, 370200-545, 719/316
• US Class Current: 719/316
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• 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/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/03 Protocol definition or specification protocol conformance testing H04L1/244
• 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
• CPC Class Codes: H04Q 3/005 Personal communication services, e.g. provisions for portability of subscriber numbers
• CPC Class Codes: H04Q 3/0095 Specification, development or application of network management software, e.g. software re-use
• CPC Class Codes: H04W 12/084 using delegated authorisation, e.g. open authorisation [OAuth] protocol
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

The present invention relates to an arrangement for simplifying the design and implementation of mobile services in a communication system, especially a telecommunications system, said system comprising distributed hardware and software components which interact in order to provide services to one or more users, and for the purpose of this improved availability it is according to the present invention suggested a solution of introducing in said system a mobility transparency, for thereby enabling facilitated application design including inter alia terminal or personal mobility. Special emphasis is made on solutions based on realising mobility transparency by in-line solution, broker solution and proxy solution.

Claims

1. An arrangement for simplifying the design and implementation of mobile radio terminal services in a communications system, comprising:

distributed hardware and software components provided in accordance with a distributed processing environment (DPE) and configurable in use to provide one or more services to one or more users;

means for supporting one or more distribution transparencies in the DPE including access, location, or failure transparencies; and

means for supporting mobile radio terminal mobility transparency in the DPE such that an application program being executed at a mobile radio terminal located in one radio service area serviced via one radio base station is not interrupted or hindered in its execution when the mobile radio terminal moves to another radio service area serviced via another radio base station;

wherein the means for supporting mobile transparency in the DPE includes means for integrating a mobile radio terminal mobility function in the infrastructure of a software platform designed in the DPE, and wherein the means for supporting mobile radio terminal mobility transparency in the DPE includes an engineering object interceptor arranged at a boundary between a mobile radio terminal domain and a telecom system domain.

2. Arrangement as claimed in claim 1, wherein the access, location, or failure transparencies are already existing and are defined by Open Distributed Processing (ODP) and adopted by Telecommunication Information Networking Architecture (TINA-C), and wherein the means for supporting mobile radio terminal mobility transparency in the DPE is added to the already-existing the access, location, or failure transparencies.

3. Arrangement as claimed in claim 1, wherein the means for supporting mobile radio terminal mobility transparency in the DPE includes means for mapping computational objects to engineering objects (EO) so as to be non-visible in a computational model of the application program.

4. Arrangement as claimed in claim 1, wherein an engineering model may be developed by mapping each of one or more computational objects (COs) to one or more Basic Engineering Objects (BEOs), the arrangement further comprising:

means for effecting an interaction between computational objects belonging to a same cluster is effected directly using one or more method calls, and

means for effecting communication between computational objects located in a telecom system domain and in different clusters through a channel including stubs, binders, and protocols.

5. Arrangement as claimed in claim 1, wherein user domain computation objects and a telecom system domain computation object residing in different clusters communicate in a channel including an interceptor transparent to an application designer.

6. Arrangement as claimed in claim 1, wherein an application designer can decide from a computational model whether an object belongs to a user domain or a telecom system domain for use in generating application objects.

7. Arrangement as claimed in claim 1, further comprising:

means for sending a message to a routing broker asking for a server to perform a task,

wherein the routing broker is configured to implement a mobility function to locate the server and send the request to the server.

8. Arrangement as claimed in claim 7, wherein the routing broker is a cascade of two brokers.

9. Arrangement as claimed in claim 8, wherein the two brokers are configured to allow interactions between an object belonging to a user domain and an object belonging to a telecom system domain.

10. Arrangement as claimed in claim 9, wherein the two brokers support both a same interface type containing an invoke operation to allow a request to be built and invoked dynamically by client objects.

11. Arrangement as in claim 10, wherein the invoke operation includes an object name or identifier, an operation name, and a parameter list for the invoked operation.

12. Arrangement as claimed in claim 7, wherein the mobility function is a functional layer in a system architecture between an application layer and a DPE layer, where each layer may use services offered by another layer.

13. Arrangement as claimed in claim 7, wherein a derived computational model is configured for use in a transition from a computational model to an engineering model in the DPE to map interactions traversing a boundary between a user domain and a telecom system domain to interactions with the mobility function.

14. Arrangement as claimed in claim 13, wherein based on the derived computational model, an engineering model can be elaborated and engineering objects can be generated.

15. Arrangement as claimed in claim 7, further comprising:

a proxy object for acting on behalf of an entity in a transparent way.

16. Arrangement as claimed in claim 15, wherein the proxy object is adapted to generate an invoke operation for the mobility function.

17. Arrangement as claimed in claim 16, wherein the proxy object is a symmetrical constellation.

18. Arrangement as claimed in claim 15, wherein each proxy object is a Dynamic Object (DO), and a DO instance may be initiated from an object template corresponding to a Dynamic Object Implementation (DOI).

19. Arrangement as claimed in claim 15, wherein a proxy represents only one object and is deleted when the represented object terminates.

20. Arrangement as claimed in claim 15, wherein an object can be represented by multiple proxies.

21. Arrangement as claimed in claim 15, further comprising:

means for registering in the mobility function first and second objects in different domains, and

means for defining and registering a proxy for the object the proxy represents.

22. Arrangement as claimed in claim 21, wherein objects may be grouped into clusters, capsules, and nodes.

23. Arrangement as claimed in claim 1, further comprising:

means for introducing a redirection function on the DPE and for generating a special stub for a dynamic object.