KR20090103371A - Method for caching mobile agents and agent platform - Google Patents

Abstract

PURPOSE: A method for caching mobile agents and an agent platform are provided to cache a mobile agent based on a visit frequency of a mobile agent and reliability between platforms, thereby reducing network traffic and freezing time of mobile agents. CONSTITUTION: A method for caching mobile agents comprises the following steps. A moving request about a mobile agent is received(710). A visit frequency of the mobile agent is calculated(735). A caching level is determined using the visit frequency and the reliability level(740). Code information about the mobile agent is stored according to a determined caching level(745).

Description

Method for caching mobile agents and agent platform

The present invention relates to a mobile agent, and more particularly, to a mobile agent caching method and an agent platform that can improve the performance of a mobile agent by caching the mobile agent based on trust between platforms and visit frequency of the mobile agent.

A mobile agent is a program that freely moves between nodes on a network and performs a specific operation by a user's command. For example, a navigation robot that automatically collects and databases information on the Internet is a type of mobile agent. Such a mobile agent dynamically and flexibly adapts to changes in the network environment, and works asynchronously, thereby enabling smooth operation even in a low bandwidth network environment. The characteristics of the mobile agent may be more usefully used in various distributed network environments such as information retrieval, network management, and e-commerce.

To this end, it is natural that communication between mobile agents must be fundamentally assumed. Various communication models for communication between mobile agents have been proposed. In particular, group communication is most widely used to ensure transparent message transmission between mobile agents constituting a group.

An object of the present invention is to provide a mobile agent caching method and an agent platform capable of caching a mobile agent based on the reliability between platforms and the visit frequency of the mobile agent.

In addition, the present invention is to provide a mobile agent caching method and agent platform that can improve the performance of the mobile agent by reducing the network traffic and the freezing time of the mobile agent.

According to an aspect of the present invention, a method for caching code information by determining a caching level according to a visit frequency of a mobile agent in an agent platform, and a recording medium recording a program for performing the method are provided.

According to an embodiment of the present invention, a method of caching information about a mobile agent in an agent platform, the method comprising: receiving a migration request for a mobile agent; Calculating a visit frequency of the migration agent requested for migration; Determining a caching level using the visit frequency and confidence level; And storing code information for the mobile agent according to the determined caching level.

Determining whether the mobile agent is an initial visit; And if the first visit is determined, generating and storing visit information about the mobile agent.

If not the first visit may further include updating and storing the visit information for the mobile agent.

In the calculating of the visit frequency of the mobile agent requested migration, the visit frequency may be calculated using the visit information.

The visit information may include one or more of identification information on the original agent platform, identification information on the last visited agent platform, distribution name, version information, date and time of the first migration, date and time of the last migration and the number of visits. have.

The platform visit frequency (PVF) is calculated using the following equation.

Where k is any natural number, Represents visit count information of the mobile agent, Represents the last migrated date and time information of the mobile agent, Represents the first migrated date and time information of the mobile agent.

The caching level is any one of a persistent level indicating to continuously store the code of the mobile agent, a temporary level indicating to store temporarily, and a moment level indicating to delete after destruction.

According to another embodiment of the present invention, a program of instructions, which are executed by a digital processing apparatus, is tangibly implemented to perform a method of caching information about the mobile agent in correspondence with the migration of the mobile agent. A recording medium having recorded thereon a program that can be read by a processing device, comprising: receiving a migration request for a mobile agent; Calculating a visit frequency of the migration agent requested for migration; Determining a caching level using the visit frequency and confidence level; And a recording medium recording a program for executing the step of storing the code information for the mobile agent according to the determined caching level.

According to another aspect of the present invention, an agent platform capable of caching code information by determining a caching level according to a visit frequency of a mobile agent is provided.

According to an embodiment of the present invention, an agent platform for caching code for a mobile agent, the agent platform comprising: a storage unit for storing reliability and visit information for one or more mobile agents; A communication unit receiving a migration request for the mobile agent; A frequency calculator configured to calculate a visit frequency by using the visit information on the mobile agent; And a caching unit configured to determine a caching level by using the visit frequency level and the reliability level, and to store code information of the mobile agent according to the caching level.

The method may further include an agent manager configured to determine whether the mobile agent is the first visit and to generate and store visit information about the mobile agent when the first visit is determined.

If it is determined that the mobile agent is not the first visit, the agent manager may extract and update the visit information for the mobile agent.

The frequency calculator may calculate the visit frequency by using the visit information on the mobile agent.

The frequency calculator calculates a visit frequency using the following equation.

Where k is any natural number, Represents visit count information of the mobile agent, Represents the last migrated date and time information of the mobile agent, Represents the first migrated date and time information of the mobile agent.

By providing a caching method and an agent platform according to the present invention, the mobile agent is cached based on the reliability between the platforms and the visit frequency of the mobile agent, and the mobile agent can be safely migrated.

In addition, the present invention has the effect of improving the performance of the mobile agent by reducing the network traffic and the freezing time of the mobile agent.

1 is a flowchart illustrating a method for migrating a mobile agent according to an embodiment of the present invention.

2 is a diagram showing the structure of a migration request message according to an embodiment of the present invention.

3 is a block diagram schematically illustrating internal components of an agent platform according to an embodiment of the present invention.

4 is a diagram showing the structure of visit information according to an embodiment of the present invention.

5 is an exemplary view for explaining a reliability level calculation according to an embodiment of the present invention.

6 illustrates a structure of a caching directory according to an embodiment of the present invention.

7 is a flowchart illustrating a method of caching code information of an agent according to a migration of a mobile agent according to an embodiment of the present invention.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all transformations, equivalents, and substitutes included in the spirit and scope of the present invention. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Hereinafter, in the present specification, a mobile agent autonomously moves one or more hosts (or platforms) to perform tasks independently by using resources provided by the host or to perform tasks desired by a user while interacting with other mobile agents. We will define this as a process that can be used.

In this specification, the agent platform may be a device that manages a plurality of mobile agents and determines whether to cache the code of the mobile agent by using the visit frequency and the reliability of the mobile agent. Of course, depending on the implementation method, the agent platform may be implemented in the form of software.

In order to facilitate understanding and explanation of the mobile agent caching method according to the present invention, a mobile agent migration method will first be described.

1 is a flowchart illustrating a method for migrating a mobile agent according to an embodiment of the present invention, and FIG. 2 is a diagram illustrating a structure of a migration request message according to an embodiment of the present invention.

For convenience of understanding and explanation, the agent platform currently registered by the mobile agent will be referred to as a 'source agent platform', and the agent platform to be migrated by the mobile agent will be referred to as a 'target agent platform'.

In step 110, the source agent platform generates a migration request message including information on the target mobile agent (referring to the mobile agent that requested migration) and transmits it to the target agent platform. The migration request message contains various information needed for the migration of the target mobile agent.

For example, as illustrated in FIG. 2, the migration request message may include information about the source agent platform to which the target mobile agent is currently registered, information about the original agent platform that generated the target mobile agent, information about the target mobile agent ( For example, version information, distribution name, etc.) and class list information. Here, the class list information is information about various objects (eg, instances) required for operation on the migration agent.

For example, a migration agent can be defined and created using one or more classes. In other words, each migration agent's definition and each function can be implemented as a class, and this information is stored in the class list.

In step 115, the target agent platform receives the migration request message, and analyzes and confirms the original platform corresponding to the target mobile agent.

For example, the target agent platform extracts information about the original platform corresponding to the target mobile agent (for example, the original platform identification information) from the migration request message and then searches the caching directory to see if the information about the same original platform exists. Check whether or not.

In operation 120, the target agent platform analyzes a distribution name corresponding to the target mobile agent.

For example, the target agent platform extracts the distribution name corresponding to the target mobile agent from the migration request message, and then searches the caching directory to check whether the distribution name exists.

In step 125, the target agent platform generates a code list to request.

For example, the target agent platform analyzes the information and distribution name of the original platform and then generates a code list to request the source agent platform.

For example, if the target mobile agent has migrated, the target agent platform stores information about the target mobile agent (eg, class list). As a result, the target agent platform may generate a required code list (ie, class information that is not required or have no change) corresponding to the target mobile agent and request the source agent platform.

For another example, the target agent platform may receive only the different class list information after transmitting the class list information existing corresponding to the target mobile agent to the source agent platform.

In step 130, the target agent platform generates a response message including a code list to request and transmits it to the source agent platform.

In step 135, the source agent platform obtains a code list from the response message, extracts corresponding code information, and transmits the corresponding code information to the target agent platform.

Accordingly, when the target agent platform receives the state information of the target mobile agent, the target agent platform registers and executes the target mobile agent.

3 is a block diagram schematically showing internal components of an agent platform according to an embodiment of the present invention, FIG. 4 is a diagram illustrating a structure of visit information according to an embodiment of the present invention, and FIG. 5 is an embodiment of the present invention. 6 illustrates an example of a reliability level calculation according to an embodiment of the present disclosure, and FIG. 6 illustrates a structure of a caching directory according to an embodiment of the present invention.

Referring to FIG. 3, the agent platform 300 according to the present invention includes a communication unit 310, an agent migration unit 315, an agent occupant unit 320, an agent manager 325, a frequency calculator 330, and a caching unit. 335, a security unit 340, a storage unit 345, and a control unit 350.

The communication unit 310 transmits and receives data with mobile agents or other agent platforms through a communication network.

For example, the communication unit 310 may receive and output a migration request message from another agent platform. In addition, the communication unit 310 may receive a response message from the agent migration unit under the control of the control unit 350 and transmit the response message to another agent platform through a communication network.

The agent migration unit 315 controls the stop of execution of the mobile agent according to the migration request of the mobile agent, and generates a migration request message including each code version information and name information of the mobile agent to the target agent platform. send.

For example, when a migration request is received (or entered) from any mobile agent, the agent platform may request a migration request that includes information about the mobile agent, version information for each code, agent platform identification information, original agent identification information, and the like. You can create a message. The agent migration unit 315 then transmits the migration request message to the target agent platform.

When the tenant 320 receives a move request for an arbitrary mobile agent from another agent platform (that is, when a migration request message is received), the agent mover 320 generates and transmits a migration response message by generating code list information necessary for moving in. It performs the function.

For example, the agent entering unit 320 extracts the original agent identification information and the distribution name from the received migration request message and determines whether the agent resides in the caching directory. Since the code list information required for moving in differs depending on the presence, the agent moving unit 320 may generate the necessary code list information according to the presence and transmit it to the source agent platform along with the migration response message.

The agent manager 325 performs a function of managing a lifecycle of the mobile agent. In other words, the agent manager 325 performs a function of managing overall operations for registering, executing, and deleting the mobile agent.

In addition, the agent manager 325 generates and manages agent visit information by using basic information on each mobile agent.

For example, the agent visit information may include original agent platform information, information on the most recently registered (migrated) agent platform, distribution name of the mobile agent, version information of the mobile agent, and the like as illustrated in FIG. 4. The mobile agent may include information about a move-in date when the mobile agent is initially registered on the agent platform, information about a move-in date when the mobile agent is most recently migrated (or registered) to the agent platform, and visit frequency information.

For example, when the agent management unit 325 receives a migration request for any mobile agent from the communication unit 310, the agent manager 325 determines whether the mobile agent is the first visit to the agent platform 300. For example, the agent manager 325 may determine whether the visit information for the corresponding mobile agent exists or not, or determine whether the visit is the first visit. If it is determined that the first visit, the agent manager 325 generates the visit information for the mobile agent. However, if it is not the first visit, the agent manager 325 obtains and updates visit information about the mobile agent from the caching directory.

In addition, the agent manager 325 calculates and stores the reliability between the agent platform and another agent platform connected through a communication network.

For convenience of understanding and explanation, a method of calculating the reliability level of the agent manager 325 according to the present invention will be briefly described with reference to FIG. 5. In this specification, it is assumed that the reliability between the agents is set in advance. That is, as shown in Figure 5, it is assumed that the reliability between the directly connected agent platform is set in advance.

In the present specification, the reliability between each agent platform may be calculated using Equation 1 below.

here, On the agent platform It represents the product of the reliability between each agent platform existing on each path to the agent platform.

For example, in FIG. 5A, since there is only one path from the first agent platform to the third agent platform, The reliability of Is calculated. However, as shown in (b) of FIG. 5, since there are two paths from the first agent platform to the fourth agent platform, Liver reliability Is calculated.

In the present specification, the reliability between each agent platform is calculated using a WTPL (Web of Trust based Platform List). Since this is obvious to those skilled in the art, a detailed description thereof will be omitted.

The frequency calculator 330 calculates a platform visit frequency (PVF) of the mobile agent using the visit information of the mobile agent.

For example, the frequency calculator 330 may calculate a visit frequency for the mobile agent using Equation 2 below.

Here, MAVI is the visit information of the mobile agent, the original platform ID (original platform ID) that is the identification information of the agent platform that created the mobile agent, the last platform identification information (last platform ID) that is the identification information of the most recently migrated agent platform ), The distribution name or agent release name of the mobile agent, the version that is information about the mobile agent's version, and the date and time when the mobile agent first migrated to the agent platform (first immigration date or less). ), The date when the mobile agent last moved to the agent platform (last immigration date, hereinafter referred to as 'last move-in date'), and the frequency of visits to the agent platform (visit frequency, hereinafter called 'visit_frequency'). '.'

In Equation 2, last_im_date is the last move-in date, first_im_date represents the first move-in date, and k represents identification information given to the mobile agent.

The caching unit 335 determines the caching level for the mobile agent by using the visit frequency calculated by the frequency calculator 330 and the previously stored reliability. The caching unit 335 may arbitrarily adjust the range of the caching level according to the overall system and the network environment.

In the present specification, a caching level will be described on the assumption that it is divided into a persistent level, a temporary level, and a moment level. Of course, the caching levels may be variously classified in policy other than the three caching levels described herein by the administrator managing the agent platform.

 The persistence level is defined as continuously storing code information of the mobile agent in the agent platform.

In addition, the temporary level is defined as temporarily storing code information of the mobile agent for a predetermined period of time.

In addition, the instantaneous level is defined as immediately deleting code information of the mobile agent from the agent platform when the mobile agent is destroyed or migrated.

The security unit 340 provides various security services to protect the mobile agent and the agent platform from attack.

The storage unit 345 stores an algorithm (or software) necessary for operating the agent platform or mobile agents according to the present invention. In addition, the storage unit 345 stores the visit information and the caching directory for the mobile agent according to the caching level determined by the caching unit 335. 6 illustrates a caching directory in which a mobile agent is stored according to a caching level determined by the caching unit 335.

The control unit 350 is an internal functional element of the agent platform 300 according to the present invention (for example, communication unit 310, agent migration unit 315, agent occupant 320, agent management unit 325, frequency calculation Unit 330, caching unit 335, security unit 340, the storage unit 345).

7 is a flowchart illustrating a method of caching code information of an agent according to a migration of a mobile agent according to an embodiment of the present invention. Each step described below is performed by each internal functional element of the agent platform 300, but will be collectively described as an agent platform for the convenience of understanding and description.

In step 710, the agent platform 300 receives a migration request message of the target mobile agent from the source agent platform. Correspondingly, the agent platform 300 performs a related process required for migration. Since the migration method corresponding to the migration request message for any mobile agent in the agent platform 300 has already been described with reference to FIG. 1, duplicate description thereof will be omitted. Hereinafter, assuming that the migration to the target mobile agent is determined by the agent platform 300 will be described in the following operation.

In step 715, the agent platform 300 determines whether the target mobile agent is the first visit to the agent platform.

As described above, the agent platform 300 may determine whether there is visit information corresponding to the target mobile agent and determine whether the target mobile agent is the first visit.

In addition, the agent platform 300 extracts the version information and the distribution name of the target mobile agent from the migration request message, and then determines whether the target mobile agent is the first visit by determining whether the version information and the distribution name corresponding to the caching directory exist. May be determined.

If it is determined that the first visit, the agent platform 300 generates visit information for the target mobile agent at step 720. The generated visit information is stored in a caching directory.

However, if it is determined that this is not the first visit, then at step 725 the agent platform 300 updates and stores the visit information for the target mobile agent.

For example, agent platform 300 extracts visit information for the target mobile agent from the caching directory. Subsequently, the agent platform 300 updates the visit frequency information in the extracted visit information and stores it in the caching directory.

In step 730, the agent platform 300 calculates the reliability between the agent platform 300 and the source agent platform.

That is, the agent platform 300 may calculate the reliability between the agent platform 300 and the source agent platform by the above-described method.

In step 735, the agent platform 300 calculates the visit frequency of the target mobile agent by using the visit information of the target mobile agent.

In step 740, the agent platform 300 calculates a caching level for the target mobile agent using the calculated reliability and visit frequency.

In operation 645, the agent platform 300 stores the code information of the target mobile agent in the caching directory according to the calculated caching level. Here, the code information may be class list information of the target mobile agent.

Although the above has been described with reference to a preferred embodiment of the present invention, those skilled in the art to which the present invention pertains without departing from the spirit and scope of the present invention as set forth in the claims below It will be appreciated that modifications and variations can be made.

Claims (14)

A method of caching information about a mobile agent on an agent platform, Receiving a migration request for the mobile agent; Calculating a visit frequency of the migration agent requested for migration; Determining a caching level using the visit frequency and confidence level; And Storing code information for the mobile agent according to the determined caching level. According to claim 1, Determining whether the mobile agent is an initial visit; And If determined to be the first visit, generating and storing visit information for the mobile agent. The method of claim 2, And if not the first visit, updating and storing the visit information for the mobile agent. The method of claim 3, wherein Computing the visit frequency of the mobile agent requested migration, Caching method, characterized in that for calculating the visit frequency using the visit information. The method of claim 4, wherein The visit information includes one or more of identification information on the original agent platform, identification information on the last visited agent platform, distribution name, version information, date of first migration, date of last migration, and number of visits. A caching method characterized by the above. The method of claim 5, Caching method, characterized in that the visit frequency is calculated using the following equation. Where k is any natural number, Represents visit count information of the mobile agent, Represents the last migrated date and time information of the mobile agent, Represents the first migrated date and time information of the mobile agent. According to claim 1, The caching level is any one of a persistent level indicating to continuously store the code of the mobile agent, a temporary level indicating to store temporarily, and a moment level indicating to delete after destruction. A caching method characterized by the above. In an agent platform that caches code for mobile agents, A storage unit for storing the reliability and the visit information for the one or more mobile agents; A communication unit receiving a migration request for the mobile agent; A frequency calculator configured to calculate a visit frequency by using the visit information on the mobile agent; And And a caching unit configured to determine a caching level by using the visit frequency level and the confidence level, and to store code information of the mobile agent according to the caching level. The method of claim 8, Determining whether the mobile agent is the first visit, and if determined as the first visit, the agent platform further comprises an agent management unit for generating and storing the visit information for the mobile agent. The method of claim 9, And if the mobile agent determines that the mobile agent is not the first visit, extracts and updates the visit information for the mobile agent and stores the mobile agent. The method of claim 10, And the frequency calculator calculates a visit frequency using the visit information on the mobile agent. The method of claim 11, wherein The frequency calculator is an agent platform, characterized in that for calculating the visit frequency using the following equation. Where k is any natural number, Represents visit count information of the mobile agent, Represents the last migrated date and time information of the mobile agent, Represents the first migrated date and time information of the mobile agent. The method of claim 8, The caching level is any one of a persistent level indicating to continuously store the code of the mobile agent, a temporary level indicating to store temporarily, and a moment level indicating to delete after destruction. Agent platform. In order to perform the method of caching information about the mobile agent in correspondence with the migration of the mobile agent, a program of instructions that can be executed by the digital processing device is tangibly implemented, and the program can be read by the digital processing device. In this recorded recording medium, Receiving a migration request for the mobile agent; Calculating a visit frequency of the migration agent requested for migration; Determining a caching level using the visit frequency and confidence level; And And recording a program for executing code information for the mobile agent according to the determined caching level.