KR100272094B1 - Object migration system and method - Google Patents

Abstract

PURPOSE: A system and a method for an object transition is provided to effectively use whole functions of a system by transmitting state information of an object, and by migrating the object after class information of the relevant object is transmitted, and a class is created in case that the object is migrated to a processor without the class of the object to be migrated. CONSTITUTION: An object transition system is composed of an object allocation manager(500), a transmission node(510) and a reception node(560). The object allocation manager(500) manage an object allocation in order to distribute a workload. The transmission node(510) is composed of a migrating object(520) and a class information provider(530). In case of receiving an object transition command from the object allocation manager(500), the migrating object(520) outputs an object generation message to the reception node(560). In case that object state information is transmitted to a new object of the reception node(560), a transmission object is taken off. The reception node(560) is composed of an object generation manager(570), a new object(580) and a dynamic class composer(590). The object generation manager(570) receives an object generation request message. The dynamic class composer(590) receives class information from the class information provider(530) of the transmission node(510).

Description

Object transition system and method

1 is a diagram illustrating the structure of an object transmitting node and a receiving node of a conventional object transition system.

Figure 2 (a) shows the structure of a system that dynamically generates non-element classes at runtime using element classes.

Figure 2 (b) shows a conceptual diagram of the dynamic class composition scheme based on the element class.

3 is a diagram illustrating a configuration of a dynamic class system that analyzes objects and classes, provides information about them, and dynamically generates classes at runtime using a runtime dynamic class generation system.

4 shows a flowchart of the operation of FIG.

5 is a block diagram of an embodiment of an object transition system according to the present invention, which dynamically generates a required class using the dynamic class system of FIG. 3 to transfer an object.

6 shows a flowchart of the operation of FIG.

7 illustrates a process of transferring a complex object from a transmitting node to a receiving node by using a dynamic class composition technique.

The present invention relates to an object transition system and method, and more particularly, to an object transition system and method for managing the common parts of the classes constituting the system and dynamically generating the required classes.

Improvements in computer manufacturing and network technologies have enabled the construction of various types of multiprocessor and distributed systems. Effective use of these systems requires system software with more complex forms and functions than conventional single processor systems. As the complexity of software increases, the cost and effort to develop and manage the software increases rapidly. Recently, object-oriented methods for developing system software of multiprocessor systems or distributed systems have been developed. The case is increasing.

On the other hand, in a multiprocessor system or a distributed system, problems that may not be seen in a conventional single processor system have occurred. One of them is a workload bias. In other words, a task is intensively allocated to some of the processors constituting the system, so that the tasks that can be processed throughout the system are delayed or not processed, and the overall efficiency of the system is reduced. To prevent this, object migration is being attempted.

In the past, a process migration method of moving a process from a processor with a large workload to a small processor and executing the process has been proposed, but it is applied to a real system because of the high overhead required in the process migration. There was a problem.

In order to solve this problem, it is necessary to reduce the amount of data required for the process transition process. To this end, many methods for transferring objects on a coarse-grained scale have been attempted. Unlike a process that is a mixture of operations and data, an object is divided into two parts representing a method and a state. Therefore, class information of an object to be transferred on a receiver processor to be transferred is provided. If is present, passing the state in the form of a message allows the object to be restored to the receiving processor. In this case, since the amount of information to be delivered is much smaller than that delivered in the form of a process, there is an advantage that the overload that the entire system has to transfer objects is greatly reduced.

However, the object transition methods proposed up to now have to use inefficient methods such as object transfer is impossible or simply move the object image in memory when there is no class information of the object to be transferred to the receiving processor.

FIG. 1 shows the structure of an object transfer node (hereinafter, used in the same sense as a transfer process) and a receiver node (hereinafter, used in the same meaning as a receive process) of a conventional object migration system. In FIG. 1, the Allocation Manager 120 sends the transition message 100 to the transition object 135 on the transmission node 130. The transition object 135 that has received the transition message 100 stops the operation 101 once receiving a request from the outside, and a message 108 requesting the object creation to the object creation manager 145 of the receiving node 140. ). The object creation manager 145 received the object creation request generates a new object creation message 104 using the class information of the object. The new object 140 on the receiving node 140 determines whether it is generated by the transition (105), and receives the information transmitted by the transition object of the transmitting node 130 (109) if it is due to the transition. Meanwhile, after the transfer object 130 transmits a new object creation message (108), it prepares (102) a state capable of transmitting its own state and transmits it. The object of the receiving node 140 sets the current state using the transferred object state (106), and continues operation. (107) Meanwhile, the object of the transmitting node transmitted to the current state is destroyed by itself. (103)

However, the conventional method described above load balances the overall workload of the system by using two techniques of creating an object on another processor or transferring a running object to another processor according to a local workload. The biggest condition is that the receiving processor must have the class information of the object. If there is no class information of the object, the object cannot be created. Therefore, the object's transition is abandoned, or the other processor tries to transfer the object with the class information. Therefore, in the current state, it is impossible to make the most efficient equalization of the workload, or, in the worst case, to prevent objects from being transferred if the other class's information is not available to the other processors despite the immense workload. It can happen. In other words, conventional object transition techniques have a limitation in that both processors have the same processor or both processors have information about the same class. As a result, in the case of a multiprocessor system, a distributed system, or a system having different user-defined classes composed of different processors, it was difficult to distribute objects evenly across the system.

Therefore, the present invention was devised to solve the above-mentioned problems, and the first object of the present invention is to dynamically reduce the constraints that were required in the existing object transition technique while reducing the workload required in the object transition process. It provides a runtime dynamic class generation system for generating classes.

The second object of the present invention is to analyze the objects and classes in one system by using the runtime dynamic class generation system to extract and manage information about the class, and thereby to dynamically generate the class at runtime. It provides a system and dynamic class creation method.

The third object of the present invention is to manage the common parts of the classes constituting the system into an elementary class pool in order to reduce the workload required in the object transition process while reducing the constraints required in the existing object transition technique. In addition, the present invention provides an object transition system and method for dynamically generating a required class using the element class pool to transfer an object.

In the object-oriented system, if there is an inheritance relationship between classes, the top class, if there is an association, both classes, the nested class, and the remaining classes from which the nested relationship is removed, When the above is duplicated, when the smallest class among the classes created according to the relationship is called an element class, and all classes that can be generated by combining the element classes are called non-element classes,

A system for dynamically generating a non-element class at runtime using an element class to achieve the first object includes an element class pool for managing and storing information of the element classes;

Receives the non-element class information described by using relationship description means for describing the relationship existing between the element class and the predetermined non-element class, converts the input into a form that can be processed in a computer system, and stores the input. A conversion module for processing;

A relationship verification unit for verifying whether inheritance, nesting, and association relationships between classes converted by the conversion module are valid; And

And a class generation unit configured to generate a new class by constructing the element class as a non-element class by the relationship verified by the relationship verification unit.

In order to achieve the above second object, a runtime dynamic class system comprises: class information providing means for converting all object and non-element classes included in one system into element classes and relations between element classes (conversion information); And

And dynamic class constructing means for generating and restoring non-element classes and objects by receiving element classes and conversion information generated by the class information providing means.

In addition, a method for dynamically generating a new class at runtime to achieve the second object

Creating an element class pool that manages and stores information about the element classes;

Analyzing inheritance, association, and nesting relationship of the state information of the object and the non-element class with input of state information of the object and the non-element class;

An element class extraction step of extracting the element class based on the analysis result;

A relation description means conversion step of displaying and analyzing the analyzed non-element class information by using relation description means for describing a relationship existing between the element class and the predetermined non-element class;

Receiving non-element class information described by the relation description means converted through the relation description means conversion step, converting the input into a form that can be processed in a computer system, and storing and processing the input;

Verifying whether inheritance, nesting, and association between classes converted by the conversion module are valid; And

And generating a new class by constructing the element class as a non-element class by the relationship verified in the verification step.

In order to achieve the above-mentioned third purpose, an object-oriented system performed in a distributed or parallel processing environment consisting of at least two or more processors and a communication network connecting them, from one processor (transmitting node) to the other processor (receiving node). In the object transition system that transfers objects to

The transmitting node

When receiving the object transition command, the object creation message is output to the receiving node without receiving an external processing request, and the object information is prepared to be transmitted while the object state information is transmitted to the receiving node. Transition object that destroys; And

When receiving the class information request message from the following object creation manager of the receiving node, characterized in that it comprises a class information providing unit for outputting the class information.

The receiving node

Receives the object creation request message of the transport node and checks whether the class to which the object of creation request belongs exists, outputs a new object creation message if the class exists, and if the class does not exist, corresponds to the class information provider of the transport node. Object generation management unit for requesting class information;

Receiving a new object creation message from the object generation management unit or the following dynamic class constructing unit, a new object receiving new state information of the object from the transition object of the transmitting node and creating a new object; And

It receives the class information from the class information provider of the transport node to dynamically create a new class, characterized in that it comprises a dynamic class constructor for outputting an object creation message to the new object.

In addition, in order to achieve the above-mentioned third purpose, an object-oriented system performed in a distributed or parallel processing environment consisting of at least two or more processors and a communication network connecting them to one processor (transmission node) from the other processor (receive) Node transition method to transfer objects to

Outputting, by the object allocating manager who performs object allocation, a message indicating object transition to the transport load;

Outputting an object creation message to the receiving node without receiving an external processing request and preparing to transmit status information of the object when receiving an object transition command;

Receiving an object creation request message of the transport node and checking whether a class to which a creation request target object belongs is present;

Outputting a new object creation message if a class exists in the checking step, and requesting corresponding class information from a transmission node if the class does not exist;

Outputting corresponding class information when receiving a class information request message from a receiving node;

Receiving class information from a transmitting node and dynamically creating a new class and outputting an object creation message; And

Receiving the new object creation message, characterized in that it comprises the step of receiving a status information of the object from the transmission node to create a new object.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. Terms necessary to describe the present invention will be defined as follows.

In the object-oriented system, if there is an inheritance relation between classes, the uppermost class, if there is an association relation, both classes, and if there is an nested relation, the nested class and the remaining classes from which the nested relation is removed, In case two or more of,, and nested relations overlap, the smallest class among the classes created according to each relation is called an element class, and all classes that can be created by combining the element classes are defined as non-element classes. .

FIG. 2 (a) shows a configuration diagram of a dynamic class generation system that dynamically generates the non-element class at runtime using the element class under the above definition. The element class pool 200 serves as a kind of database for managing and storing element classes as a set of element classes.

The conversion module 210 may receive as input non-element class information described using relationship description means for describing a relationship existing between the element class and the arbitrary non-element class, and process the input in a computer system. This module converts form (intermediate code), stores it, and processes it. Here, the relation description means is a language for describing the specification and interface relationship of the class, and is commonly referred to as Class Specification and Interface Description Language (CSIDL). The CSIDL is a unique number (id) information of the element class constituting the non-element class, the unique number information of the class already transmitted, inheritance relationship, association between the class, information indicating the nesting relationship, information about the interface of the class and class It should be possible to describe information about the behavior of the company. And although not essential to the CSIDL, in order to avoid confusion with other versions of the CSIDL, information on the unique number (id) of the CSIDL is also required.

The relationship verification unit 220 verifies whether the inheritance, association, and aggregation relationship between classes is valid with the information converted by the conversion module 210. The class generation unit 230 generates a new class by constructing the element class as a non-element class by the relationship verified by the relationship verification unit 220.

FIG. 2 (b) shows a conceptual diagram of a dynamic class construction scheme based on an element class. Each figure of the element class 280 represents basic objects. These can be used to represent the objects 270 present on the system. CSIDL 250 exists to represent between the element class and the objects on the system, which are interpreted by the dynamic class constructor 260, and more complex objects are created using the element objects according to the interpreted result.

The operation of the runtime dynamic class generation system for dynamically generating a class at runtime shown in FIG. 2 (a) will be described below. First, when a file or data described in the CSIDL having information on a class to be generated from the outside is input to the conversion module 210, the file is converted into a form (intermediate fund) that can be processed in a computer system. .

Then, the relationship verification unit 220 analyzes the intermediate code, and verifies whether the contents regarding inheritance, nesting, association, behavior, and interface of the class are valid. If it is determined that the result of the verification is valid, the required element class in the element class pool 200 is taken and a new class is generated according to the relationship and interface between the classes verified above. As mentioned above, by dividing the class into small class called element class and describing the relation and interface by using CSIDL, the class can be created dynamically at runtime. In addition, by transmitting the information of the CSIDL it can be transferred by restoring the class to another node with a small workload (overload).

3 is a block diagram of a dynamic class system that analyzes objects and classes in a system by using the runtime dynamic class generation system, extracts and manages information on classes, and dynamically generates classes at runtime. As shown, the dynamic class system is composed of a class information providing unit 300 and the dynamic class configuration unit 370.

The class information providing unit 300 is a module for converting all object and non-element classes included in one system into element classes and relations (conversion information) between element classes. The relationship analysis unit 310 and element class And an extracting unit 320 and a related technology converting unit 330.

The relationship analysis unit 310 inputs the state information of the object and the non-element class, and analyzes the inheritance, association, and nesting relationship of the state information of the object and the non-element class, and the element class extractor 320 The element class is extracted based on the analysis result of the relationship analysis unit 310. In addition, the relationship description means conversion unit 330 converts the analyzed non-element class information into a CSIDL file or data using a relationship description means (CSIDL) describing a relationship existing between the element class and the predetermined non-element class. Indicates.

The dynamic class constructing unit 350 is a module for generating and restoring non-element classes and objects by receiving element classes and transformation information generated by the class information providing unit 300. The runtime dynamic class generating system Is applied.

FIG. 4 is a flowchart illustrating the operation of FIG. 3. The dynamic class system and the dynamic class generation method will be described with reference to FIG. 4 and the runtime dynamic class generation system shown in FIG. 1.

First, the element class pool 200 shown in FIG. 1 should be created (step 407). Then, the relationship analysis unit 310 receives the information about the state of the object and the non-element class. The object state information, inheritance, association, nesting relationship, class behavior, and interface of the class are analyzed (step 410). The element class extracting unit 320 based on the information analyzed above. Extracts the element class constituting the non-element class and adds the element class to the element pool (step 420). Then, through the relation description means conversion unit 330, the information of the analyzed non-element class is stored using the CSIDL file. Or output as a data string (step 430).

The CSIDL file or data converted by the relation describing means conversion unit 330 is input to the conversion module 210 of the runtime dynamic class generation system shown in FIG. The following description is the same as the operation of the runtime dynamic class generation system shown in FIG.

That is, in step 430, non-element class information described in the converted CSIDL is received as an input, and the input is interpreted in a form that can be processed in a computer system, converted, stored in the memory, and processed. (Step 440) Then, it is verified whether the inheritance, nesting, and association between the classes converted in the conversion module is valid. (Step 450) The element class is configured as a non-element class based on the relationship verified in the verification step. Create a class (step 460).

5 is a diagram illustrating an object transition from one processor (transmitting node) to another processor (receiving node) in an object-oriented system which is performed in a distributed or parallel processing environment composed of at least two processors and a communication network connecting them. In order to reduce the workload required in the existing object transition scheme while reducing the required workload, the object transition system according to the present invention, by dynamically generating the required class using the dynamic class system of FIG. It shows a block diagram for one embodiment of the.

The object transition system according to the present invention is composed of an object allocation manager (500), a transmitting node 510 and a receiving node (560), the object allocation manager 500, the workload is concentrated on one processor This module manages object allocation to distribute them when they are created.

The transmission node 510 is composed of a migrating object 520 and a class information provider 530. The transition object 520 receives an object transition command from the object assignment manager 500. The object creation message is output to the receiving node without receiving the processing request of the receiving node (523), the state information of the object is prepared to be transmitted (524), and the object state information is received from the new object of the receiving node (560). The transmission target object is destroyed after the transmission (528) to the (580). (526) And the class information provider 530 receives the class information request message from the object creation manager 500 of the receiving node (573) The class information providing unit 300 illustrated in FIG. 3 is used as a module for outputting class information 531.

The receiving node 560 includes an object creation manager 570, a new object 580, and a dynamic class constructor 590. The object creation manager 570 receives the object creation request message of the transport node 510 and checks whether a class to which a creation request object belongs belongs exists and outputs a new object creation message if the class exists (572). If the class does not exist, the corresponding class information is requested to the class information provider 530 of the transmitting node 510. (573) The new object 580 is the object creation manager 570 or the dynamic class constructor 590. When a new object creation message is received from the received object (571, 592), the state information 528 of the object is received from the transition object 520 of the transmitting node and recorded as state information of the new object (584).

The dynamic class constructor 590 receives class information from the class information provider 530 of the transmitting node and dynamically creates a new class and outputs an object creation message to the new object. The dynamic class shown in FIG. The configuration unit 350 is used.

FIG. 6 is a flowchart illustrating the operation of FIG. 7. The object transition system and method will be described with reference to FIG. 6 and the dynamic class system shown in FIG.

As shown in FIG. 5, the newly proposed method has an improved function by adding a class information provider 530 to a transmitting node and a dynamic class constructor 590 to a receiving node without greatly changing the existing method. .

In FIG. 5, the message 502 transmitted from the object assignment manager 500 to the object of the transmitting node and the object assignment manager 100 of FIG. 1 perform the same role. In addition, the three critical steps 522,524, 526 on the transition node of the transmitting node and the three critical steps 582, 584, 586 on the new object 580 of the receiving node correspond to 101, 102, 103 and 105, 106, 107 of FIG. . The message 523 transferred from the transition object 520 to the object creation manager 570 and the message 528 transferred to the new object 580 correspond to 108 and 109 of FIG. 1, respectively. Creation messages 572 and 592 transmitted from the object creation manager 570 or the dynamic class constructor 590 of the receiving node to the new object correspond to 104 in FIG. It is only the object creation manager 570 of the receiving node that is changed among the components as in the conventional technique, and the other elements have no change in function and form.

The core of the present invention is to describe the information of the class that defines the behavior of the object using small sized classes called element class, and at this time, the class is created on the receiving node even with a small overload by sending and receiving only the information described. Is in the technology

The flow of FIG. 6 will be described based on the above description. First, the object assignment manager 500 outputs a message 502 indicating the object transition to the transmitting node 510. (Step 600) When the transition object 520 receives an object transition command, the transition object 520 does not receive an external processing request. (Step 610), an object creation message 523 is output to the receiving node 560 (step 620), and the state information of the corresponding object is prepared for transmission (step 630).

On the other hand, the object creation manager 570 receives the object creation request message 523 of the transport node and checks whether a class to which a creation request target object belongs is present (step 640).

If the class exists in the checking step, the object creation manager 570 outputs a new object creation message 572 (step 680). If the class does not exist in the checking step, the corresponding class information is requested to the class information provider 530 of the transmitting node (step 650). In step 650, the class information provider 530 receives the corresponding class information request message. The class information is output to the dynamic class constructor 590 of the receiving node (step 660). A detailed description thereof follows the description of the class information provider 300 of FIG. The dynamic class constructor 590 receives class information from the class information provider 530 of the transmitting node to dynamically create a new class (step 670), and outputs an object creation message 592 (step 680). The detailed description follows the description of the dynamic class constructor 590 of FIG.

Meanwhile, when the receiving node 560 receives the new object generation message, the receiving node 560 receives state information about the corresponding object from the transmitting node 510 (step 690), creates a new object, and starts the generated object. step)

FIG. 7 illustrates the process of transferring an object 520 of a non-element class from a transmitting node 510 to a receiving node 560 using a dynamic class composition technique. In FIG. 7, the object 520 is first analyzed with class information by the class information provider 530. Accordingly, the analyzed information 710 is an element class by the dynamic class constructor 590 of the receiving node 560. Are used to create a class 580, such as a class of object 520. Thereafter, the object state transmitting module 700 of the transmitting node 510 transmits the state of the current object as a message 720, which is transmitted to the object generating module 730 of the receiving node 560, and used to restore the object. do. Through this series of processes, the object 520 transitions from the transmitting node 510 to the receiving node 560 (580).

As described above, according to the present invention, in the multi-processor system and the distributed system using the object-oriented concept, the system needs to balance the workload and the communication load of the entire system, which is intended to be obtained through the object transition. It's easy.

In addition, the concept of dynamically constructing a complex class based on an element class can be used to reduce the amount of memory occupied by converting to a simpler CSIDL once a class is used once. This makes it possible to configure an object-oriented system for a more dynamic environment.

According to the present invention, when a object is transferred to a processor that does not have a class of an object to be transferred, the class information of the object is first delivered to create a class, and then the state information of the object is transferred to obtain an effect of transferring the object. It becomes possible. This technique has the advantage of realizing the system-wide object transition that has not been realized by the technology up to now, and the advantage of effectively utilizing the system-wide performance.

The present invention will facilitate the configuration and operation of multiprocessor and distributed systems that will ultimately become the mainstream of computing environments, while enabling efficient use of the resources of these systems.

Claims (13)

In the object-oriented system, if there is an inheritance relationship between classes, the top class, if there is an association, both classes, if there is an nested relationship, the nested class and the remaining classes from which the nested relationship is removed, When the above is duplicated, when the smallest class among the classes created according to the relationship is called an element class, and all classes that can be generated by combining the element classes are called non-element classes, the element class is used. A system for dynamically generating non-element classes at runtime, comprising: an element class pool for managing and storing information of the element classes; Receives the non-element class information described by using relationship description means for describing the relationship existing between the element class and the predetermined non-element class, converts the input into a form that can be processed in a computer system, and stores the input. A conversion module for processing; A relationship verification unit for verifying whether inheritance, nesting, and association relationships between classes converted by the conversion module are valid; And a class generation unit configured to generate the new class by constructing the element class into a non-element class based on the relationship verified by the relationship verification unit. The method of claim 1, wherein the relation description means comprises: unique number information of an element class constituting the non-element class; Unique number information of a class already transmitted; Information representing inheritance, association, and nesting relationships between classes; Information about the interface of the class; And information regarding the behavior of the class. In the object-oriented system, if there is an inheritance relationship between classes, the top class, if there is an association, both classes, if there is an nested relationship, the nested class and the remaining classes from which the nested relationship is removed, When the above is duplicated, the smallest class among the classes created according to each relationship is called an element class, and all classes that can be generated by combining the element classes are included in one system when called non-element classes. Class information providing means for converting all the object and non-element classes into element relations between element classes and element classes (conversion information); And dynamic class constructing means for receiving and converting element classes generated by the class information providing means and creating and restoring non-element classes and objects. The apparatus of claim 3, wherein the class information providing unit comprises: a relationship analysis unit configured to analyze the inheritance, association, and nesting relationship of the state information of the object and the non-element class by inputting state information of the object and the non-element class; An element class extracting unit extracting the element class based on an analysis result of the analysis unit; And a relation description means converting section for representing the analyzed non-element class information using relation description means for describing a relationship existing between the element class and the predetermined non-element class. 4. The apparatus of claim 3, wherein the dynamic class constructing means comprises: an element class pool for managing and storing information of the element classes; Receives the non-element class information described by using relationship description means for describing the relationship existing between the element class and the predetermined non-element class, converts the input into a form that can be processed in a computer system, and stores the input. A conversion unit for processing; A relationship verification unit for verifying whether inheritance, nesting, and association relationships between classes converted by the conversion module are valid; And a class generation unit configured to generate a new class by configuring the element class as a non-element class based on the relationship verified by the relationship verification unit. The method according to claim 4 or 5. The relation description means includes unique number information of an element class constituting the non-element class; Unique number information of a class already transmitted; Information representing inheritance, association, and nesting relationships between classes; Information about the interface of the class; And class information about the behavior of the class. In the object-oriented system, if there is an inheritance relationship between classes, the top class, if there is an association, both classes, if there is an nested relationship, the nested class and the remaining classes from which the nested relationship is removed, If the above is duplicated, the smallest class among the classes created according to the relationship is called an element class, and all classes that can be generated by combining the above element classes are non-element classes, dynamically at runtime. A method of creating a new class, the method comprising: generating an element class pool that manages and stores information about the element classes; Analyzing inheritance, association, and nesting relationship of the state information of the object and the non-element class with input of state information of the object and the non-element class; An element class extraction step of extracting the element class based on the analysis result and adding the element class to an element class pool; A relation description means conversion step of displaying and analyzing the analyzed non-element class information by using relation description means for describing a relationship existing between the element class and the predetermined non-element class; Receiving non-element class information described by the relation description means converted through the relation description means conversion step, converting the input into a form that can be processed in a computer system, and storing and processing the input; Verifying whether inheritance, nesting, and association between classes converted by the conversion module are valid; And generating a new class by constructing the element class into a non-element class based on the relationships verified in the verifying step. 8. The method according to claim 7, wherein said relationship describing means comprises: unique number information of an element class constituting said non-element class; Unique number information of a class already transmitted; Information indicating an inheritance relationship and nesting relationship between classes; Information about the interface of the class; And information about the behavior of the class. An object-oriented system that transfers objects from one processor (transmitting node) to the other (receiving node) in an object-oriented system that is implemented in a distributed or parallel processing environment consisting of at least two processors and a communication network connecting them. When the transmitting node receives the object transfer command, the transmitting node outputs an object creation message to the receiving node without receiving an external processing request, and prepares to transmit the state information of the corresponding object, and then returns the object state information to the receiving node. A transition object that destroys the object to be transmitted after the transmission; And a class information providing unit for outputting corresponding class information when receiving a class information request message from an object creation manager of a receiving node, wherein the receiving node receives an object creation request message of the transmitting node and is a target of creation request. An object creation management unit which checks whether a class to which an object belongs exists, outputs a new object creation message if the class exists, and requests the class information to the class information providing unit of a transmitting node if the class does not exist; Receiving a new object creation message from the object generation management unit or the following dynamic class configuration unit, a new object receiving the state information of the object from the transition object of the transmitting node and creating a new object; And a dynamic class constructor that dynamically receives a class information from a class information providing unit of a transmitting node and dynamically creates a new class, and outputs an object generation message to the new object. 10. The method according to claim 9, wherein a class is inherited between classes in an object-oriented system, a top class in case of an inheritance relationship, both classes in a case of association, a nested class in case of a nested relationship, and a remaining class in which the nested relationship is removed. When two or more of the relationships are duplicated, the smallest class among the classes created according to the relationship is called an element class, and all classes that can be generated by combining the element classes are called non-element classes. The class information providing unit comprises a state analysis unit for inputting the state information of the object and the non-element class, and analyzing the inheritance, association, and nesting relationship of the state information and the non-element class of the object and adding them to the element class pool; An element class extracting unit extracting the element class based on an analysis result of the analysis unit and adding the element class to an element class; And a relation description means converting section for representing the analyzed non-element class information using relation description means for describing a relationship existing between the element class and the predetermined non-element class. An element class pool that manages and stores information of the element classes; Receives the non-element class information described by using relationship description means for describing the relationship existing between the element class and the predetermined non-element class, converts the input into a form that can be processed in a computer system, and stores the input. A conversion unit for processing; A relationship verification unit for verifying whether inheritance, nesting, and association relationships between classes converted by the conversion module are valid; And a class generation unit configured to generate a new class by constructing the element class into a non-element class based on the relationship verified by the relationship verification unit. In an object-oriented system in which an object-oriented system is performed in a distributed or parallel processing environment consisting of at least two processors and a communication network connecting them, an object transition method of transferring an object from one processor (transmission node) to the other processor (receiving node). The method comprising: outputting, by the object allocating manager who assigns an object, a message indicating an object transition to the transmitting node; Outputting an object creation message to the receiving node without receiving an external processing request and preparing to transmit status information of the object when receiving an object transition command; Receiving an object creation request message of the transport node and checking whether a class to which a creation request target object belongs is present; Outputting a new object creation message if a class exists in the checking step, and requesting corresponding class information from a transmission node if the class does not exist; Outputting corresponding class information when receiving a class information request message from a receiving node; Receiving class information from a transmitting node and dynamically creating a new class and outputting an object creation message; And receiving the new object creation message and receiving state information of the corresponding object from a transmission node to create a new object. The method of claim 11, wherein the outputting of the class information upon receiving the class information request message from the receiving node comprises inputting state information of the object and the non-element class, and inheriting the state information of the object and the non-element class. Analyzing associations and nesting relationships; An element class extraction step of extracting the element class based on the analysis result; And a conversion step of representing and outputting the analyzed non-element class information by using relationship describing means for describing a relationship existing between the element class and the predetermined non-element class. Receiving class information and dynamically creating a new class and outputting an object generation message may receive the non-element class information described by the relation description means converted through the conversion step, and process the input in a computer system. Converting, storing, and processing the same in the present form; Verifying whether inheritance, nesting, and association between the classes converted by the conversion module are valid; And generating a new class by constructing the element class into a non-element class based on the relationship verified in the verifying step. 13. The method of claim 12, wherein the relationship description means comprises: unique number information of an element class constituting the non-element class; Information about an interface of an information class representing a unique number information of a class that has already been transmitted, an inheritance relationship association between classes, and a nesting relationship; And information about the behavior of the class.