Method for transmitting a mobile agent in a network, associated transmitter, receiver and mobile agent

• US 20040037315A1
• Filed: 12/20/2002
• Published: 02/26/2004
• Est. Priority Date: 06/30/2000
• Status: Abandoned Application

• Current Assignee: Thales SA
• Original Assignee: Thales SA
• Inventors: Ruiz, Pascal, Delautre, Antoine, Gillardeau, Sebastien
• Application Number:
  US10/311,851
• Publication Number:
  US 20040037315A1
• Time in Patent Office: Days
• US Class Current: 370/466
• CPC Class Codes: G06F 9/4862 the task being a mobile agent, i.e. specifically designed to migrate
• 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/323 in the physical layer [OSI layer 1]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The invention relates to the transmission of autonomous executable code and/or of associated data in a network. It includes the placing into bitstream form of the executable code C (stage T2) and of the associated data D (stage T3) of a mobile agent A before converting them into a bitstream to be sent f_A (stage T4). After the conventional digital processing operations on reception (stages R1 to R5), the receiving node N_R receiving this stream f_A extracts the code C and the parameters D (stages R8 and R9). The code C is run autonomously (stage E2) then the code C and its runtime context (associated parameters and resulting data) are again converted into a bitstream f_A transmitted to the next node (stages T). The final node recovers the data D_R resulting from the running of the code C on the nodes N of the route P (stage R11).

Claims

1. A method of transmitting a mobile agent (A) in a network (R) including at least executable code (C) and/or associated data D, characterized in that it includes at least the following stages:

the conversion (A/F) of said mobile agent (A) into a bitstream (f_A) to be sent, and

the sending of said bitstream (f_A) by a sender node (N_E) towards at least one node (N) in said network (R).

2. The transmission method as claimed in the preceding claim, characterized in that it includes at least the following stages:

the conversion of the executable code (C) of said mobile agent (A) into bitstreams upon said conversion (A/F),

the conversion of the data (D) associated with said mobile agent (A) into bitstreams upon said conversion (A/F),

the combining of several bitstreams into a bitstream including said mobile agent (A) upon said conversion (A/F),

and/or the creation of a link between said node (N_E) and at least one node (N) in said network (R) on which said bitstream (fA) is sent.

3. The transmission method as claimed in the preceding claim, characterized in that this link creation includes at least the following stages:

the running of the method (P) of routing through the target nodes (Nc) on which the mobile agent (A) has to be run,

the generation of a transfer parameter upon the running of said routing method (P),

the use of a transfer parameter upon creation of said link,

the opening of a communications channel constituting the creation of said link,

and in that said transmission method includes the breaking-off of said link created.

4. The transmission method as claimed in one of the preceding claims, characterized in that it includes at least one of the following stages:

one or more digital processing operations (TN) carried out, upon said conversion (A/F), on a bitstream including said mobile agent (A), the set of said processing operation or operations {TN} delivering a bitstream to be sent (fA),

the marking of said sender node (N_E) by an identifier of said mobile agent (A).

5. The transmission method according to any one of the preceding claims, characterized in that it includes at least the following stages:

the receiving of a bitstream (f_A),

the extraction of the mobile agent (A) from said received bitstream (f_A).

6. The method of transmitting a mobile agent (A) as claimed in the preceding claim, characterized in that it includes at least the following stages:

the extraction of the executable code (C) from said received bitstream (f_A) upon the extraction of said mobile agent (A),

the extraction of the data (D) associated with said received bitstream (f_A) upon the extraction of said mobile agent (A),

the setting of the runtime parameters D_E comprised or not comprised in the extracted data (D).

7. The method of transmitting a mobile agent (A) as claimed in either of claims 5 and 6, characterized in that it includes at least one of the following stages:

one or more digital processing operations (TN<sup>−

1</sup>) on said received bitstream (f_A),

verification of the authorization to run, on said node (N_R), the mobile agent (A) contained in said received bitstream (f_A), triggering the extraction of said mobile agent (A),

the marking of said receiver node (N_R) by an identifier of said mobile agent (A).

16. A node of a network (R) including a mobile-agent sender (EA) as claimed in either of claims 5 and 6 and/or a mobile-agent receiver (RA) as claimed in either of claims 7 and 8, characterized in that it includes at least one or more of the following devices:

a mobile-agent source (SA), characterized in that it includes at least the following means;

an interface (I) including at least one or more of the following inputs;

an input receiving the choice of the executable code (C) of the mobile agent (A),

an input receiving the choice of the data (D) associated with the mobile agent (A),

an input receiving the choice of the method of selection S and/or of route (P) of the target nodes (N_c),

an input receiving the choice of a method TR of transferring the data D_R resulting from the running of the mobile agent (A),

a reading member (L) including at least one or more of the following attributes;

a link with said interface,

a pointer associating an address with the incoming data in at least one internal or external memory (MEM), the address at which at least some or all of the mobile agent (A) is located,

an output delivering the mobile agent (A) read to a sender,

a microprocessor (μ

P) including an interface with a mobile agent allowing said mobile agent (A) including code (C) to manage, autonomously, at least the running of said code (C) by said microprocessor.

17. Mobile agent including at least executable code (C) and/or associated data (D) and an interface with a node as claimed in the preceding claim, called host node (N_H), characterized in that it includes at least the following functions:

the verification that the host node (N_H) belongs to the set of nodes {N} on which the mobile agent (A) is to be run, including at least one or more of the following functions;

the triggering of the management of the running of the code (C) of the mobile agent (A), if the verification is positive,

the transmission of said mobile agent (A) to the mobile-agent sender of the said host node, if the verification is negative,

the transmission of said updated mobile agent (A) to the mobile-agent sender of said host node (N_H),

the testing of the method TR for transferring data D_R resulting from the running of the code (C) including at least one or more of the following functions;

the triggering of the management of the running of said method TR, if the test is positive,

the transmission of said mobile agent (A) including at least the code (C) and the updated data (D) to which the data D_R have been added, to the mobile-agent sender of the said host node, if the test is negative

18. A mobile agent as claimed in the preceding claim, characterized in that it includes at least one or more of the following functions:

the management of the running of the code (C) of the mobile agent (A),

the updating of the associated data (D) of the mobile agent (A) on the basis of one or more of the following data items;

the context D_E of said running,

the data D_R resulting from said running,

19. The mobile agent as claimed in either of claims 17 and 18, characterized in that it includes at least the management of the running of the method TR for transfer of the resulting data D_R including:

either the creation of a data D_R-transfer means and transmission of said data D_R-transfer means to a sender of said host node (N_H),

or the creation of a results mobile agent (A′

) including at least the data D_R and transmission of said results mobile agent (A′

) to the mobile-agent sender of said host node (N_H).

8. A sender of a mobile agent in a network (R), characterized in that it includes at least the following means:

a general, mobile agent into bitstream to be sent (A/F), converter, including at least the following attributes;

an input receiving a mobile agent (A),

an output delivering the resulting bitstream (f_A) to be sent,

a bitstream sender (EF) including an input receiving said bitstream (f_A) to be sent.

9. The sender as claimed in the preceding claim, characterized in that said general converter (A/F) includes at least the following attributes:

an individual, executable code into bitstream, converter (C/F) receiving the executable code (C) of said mobile agent (A),

an individual, data into bitstream, converter (D/F), receiving the data (D) associated with said mobile agent (A),

a bitstream combiner (SF) including at least;

several inputs each receiving a bitstream of which none, one or more are each linked to the output of an individual converter,

an output delivering a bitstream including said mobile agent (A),

10. The sender as claimed in either of claims 8 and 9, characterized in that it includes a link controller (CL) between said mobile-agent sender (EA) and at least one receiver (RA) of the network (R) including at least the following attributes:

a means for managing the running of the method (P) for routing through the target nodes (N_C) on which the mobile agent (A) has to be run, running generating at least one of the following commands;

a link-generation command,

an order for opening of a communications channel constituting said link,

a link-generation command including the transfer parameters generated upon the running of said routing method (P),

an order for opening of a communications channel constituting said link including the transfer parameters generated upon the running of said routing method (P),

an output on which is delivered a signal including at least one of the following commands;

for generation of said link,

for opening of a communications channel constituting said link,

for breaking off said created link.

11. The sender as claimed in one of claims 8 to 10, characterized in that said bitstream sender (EF) includes at least:

either an output via which said stream (f_A) is broadcast to all the nodes (N) of said network (R),

or an output via which said stream (f_A) is transmitted to one or more predetermined nodes (N) in said network (R).

12. The sender as claimed in one of claims 8 to 11, characterized in that it includes at least:

one or more devices (TN) for digital processing of the bitstream including said mobile agent (A), delivering a bitstream (f_A) to be sent, as output of the set of said processing device or devices {TN}, and/or

a device (MQ) for marking said sender node (N_E) with an identifier of said mobile agent (A).

13. A mobile-agent receiver characterized in that it includes at least the following means:

a bitstream receiver (RF) receiving a bitstream (f_A),

a mobile-agent extractor (Exa), extracting the mobile agent from a bitstream and including at least one of the following attributes;

an input receiving said received bitstream (f_A),

an output delivering said extracted mobile agent (A).

14. The mobile-agent receiver as claimed in the preceding claim, characterized in that it includes at least one or more of the following means:

a verifier (VA) of the authorization to run the mobile agent (A) on the receiving node (N_R) including at least the following attributes;

an input linked to the output of the bitstream receiver receiving the received bitstream (f_A),

an output delivering said bitstream (f_A) to said mobile-agent extractor, if the verification is positive,

said mobile-agent extractor (Exa) including the following attributes;

an executable-code extractor linked to the input receiving said stream (f_A) and delivering the executable code (C) of the mobile agent (A) extracted from said stream (f_A),

a data extractor linked to the input receiving said stream (f_A) and delivering the data (D) associated with the mobile agent (A) and extracted from said stream (f_A),

a means (PP) for setting said runtime parameters D_E comprised or not comprised in the extracted data (D).

15. The mobile-agent receiver as claimed in either of claims 13 or 14, characterized in that it includes at least:

one or more devices for digital processing (TN<sup>−

1</sup>) of said received bitstream (f_A), and/or

a device (MQ) for marking said receiving node (N_R) with an identifier of said-mobile agent (A).