Updating mobile agents

• US 20030046443A1
• Filed: 09/06/2001
• Published: 03/06/2003
• Est. Priority Date: 09/06/2001
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Emako, Bertrand Lenou, Glitho, Roch, Pierre, Samuel
• Application Number:
  US09/950,236
• Publication Number:
  US 20030046443A1
• Time in Patent Office: Days
• US Class Current: 719/317
• CPC Class Codes: G06F 9/4875 with migration policy, e.g. auction, contract negotiation

Abstract

The invention relates to various embodiments of a method for updating a mobile agent (MA) providing services. The MA resides in a site in a data communications network. In a preferred embodiment a new MA, comprising the desired services, is created. The new MA moves to the site of the old MA where its data is customised. The method then waits until none of the old services in the old MA is running before it deactivates the old MA and activates the new MA. In addition, two further embodiments are provided. Furthermore, an interface manager (IM) for use with interpreted object-oriented programs is provided. The IM acts as a proxy for inter-object calls and has a redirection table in order to redirect object calls to objects that replaced old objects. Also, a method for updating an MA with an IM is provided.

Claims

1. A method for updating a first mobile agent (MA) providing at least one service, wherein the first MA resides in a site in a data communications network, the method comprising the steps of:

creating a second MA;

moving the second MA to the site of the first MA;

customising the data of the second MA;

verifying if the first MA is running any services; and

if so, waiting for the services to stop running;

when no services are running, deactivating the first MA and activating the second MA.

2. A method for updating a first mobile agent (MA) providing at least one service, wherein the first MA resides in a site in a data communications network, the method comprising the steps of:

creating a second MA;

customising the data of the second MA;

noting which services are running;

stopping the running services;

deactivating the first MA;

sending a notification to the second MA;

moving the second MA to the site of the first MA;

activating the second MA; and

restarting the services that were stopped.

3. A method for updating a first mobile agent (MA) providing at least one service, wherein the first MA resides in a site in a data communications network, the method comprising the steps of:

creating a second MA;

customising the data of the second MA;

verifying if the first MA is running any services; and

if so, waiting for the services to stop running;

when no services are running, deactivating the first MA;

sending a notification to the second MA;

moving the second MA to the site of the first MA; and

activating the second MA.

4. A method for updating a mobile agent (MA), the MA being at least partially programmed as classes of an interpreted object-oriented language, the MA providing at least one service and where no part that is to be updated is active, the method comprising the steps of:

creating new classes;

moving the classes to the MA;

customising the data for the new classes; and

putting each new class in its proper place.

5. The method according to claim 4, wherein the step of putting each new class in its proper place comprises the step of replacing an old class with the new class.

6. A method for updating a mobile agent (MA), the MA being at least partially programmed as classes of an interpreted object-oriented language, the MA providing at least one service and where no part that is to be updated is active, the method comprising the steps of:

creating new classes;

customising the data for the new classes;

moving the classes to the MA; and

putting each new class in its proper place.

7. The method according to claim 6, wherein the step of putting each new class in its proper place comprises the step of replacing an old class with the new class.

8. An interface manager (IM) for handling object calls in a object-oriented language, the IM comprising:

a redirection table for providing a translation of a first object call; and

a call handler for;

receiving a first object call from a first object;

requesting a translation of the first object call from the redirection table;

calling a second object using the translation of the first object call;

receiving a result from the second object; and

forwarding the result to the first object.

9. The interface manager according to claim 8, further comprising an object creator for creating new objects.

10. The interface manager according to claim 9, further comprising an object list for created objects.

11. A method for updating a mobile agent (MA), the MA being at least partially programmed as classes of an interpreted object-oriented language, the method comprising the steps of:

creating an update message;

sending the update message to the MA;

storing information from the update message in the MA; and

updating classes and objects in the MA using the stored information.

12. The method according to claim 11, wherein the update message comprises code for the new classes, information as to where the code is to be used, and redirection information for object calls.

13. The method according to claim 12, wherein the step of storing information from the update message in the MA comprises the step of storing the redirection information and the code for the new classes.

14. The method according to claim 13, wherein a new class is stored in the place of an old class if this is indicated by the update message.

15. The method according to claim 11, wherein the step of updating classes and objects in the MA comprises using an object list to create new versions of objects of updated classes.