KR101158534B1 - A dynamic process management system for processing data in various environment - Google Patents

Abstract

The present invention relates to a dynamic process management system for data processing in various environments, the process-based management unit for mapping the memory using the process information according to the interface unit receives a specific command from the user and the command input through the interface unit And a code base unit for storing a class related to the process information, so that only a desired data can be obtained by using a user-defined process.

Process, data, system

Description

A dynamic process management system for processing data in various environment}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a dynamic process management system for data processing in various environments, and to convey semantic information on real-time data to a user by mapping a process defined by a user to a memory.

Various software technologies have been developed to process large amounts of data. In the 1970s, a large computer called mainframe was used for large-capacity processing. However, in recent years, an environment in which a small computer can handle a large amount of data has been prepared.

In general, database technology has been developed to store and process large amounts of data. In particular, relational databases that store attribute associations and object-based databases that add methods for processing data in the relational database are most commonly used.

However, with the recent development of wired and wireless network technology, a considerable amount of data is continuously input through wireless and wired lines, and database technology has a limitation in processing this. A representative example of data processing in this environment is STREAM, developed at Stanford. In the STREAM, data is shortened and stored in real time with respect to data input from various sources, and a user acquires information using a query language similar to a structured query language (SQL). However, even if a large amount of data is reduced and stored, two problems arise. First, as time goes by, there is not enough data storage space for one computer, and second, it is difficult to check whether the data stored in abbreviation is meaningful.

An object of the present invention is to provide a dynamic process management system for data processing in a variety of environments that allows the user to obtain only the desired data by using a user-defined process through process management rather than a method of storing data for massive data processing. To provide.

In order to achieve the above object, a dynamic process management system for processing data in various environments of the present invention includes an interface unit for receiving a specific command from a user; A request manager unit for analyzing a command input through the interface unit, a class manager unit for determining which class the process defined in the command analyzed by the request manager unit inherits, and a class determined by the class manager unit A class loader that reads the code base unit into the memory and loads it into a memory, and a process manager that creates objects from classes according to the topology defined in the instruction analyzed by the request manager unit and maps these objects to the memory in the order of topology. A process based management unit comprising a unit; And a code base unit that stores a class related to the process information.

delete

The analysis of the input command is characterized by determining whether or not the command by a legitimate authority.

And an authority information storage unit for storing the authority information, wherein the request manager unit analyzes the command using the information stored in the authority information storage unit.

Analysis of the input command is characterized in that it includes an analysis of the specification that is a relationship between a plurality of processes.

 The specification may be a linear topology, a join topology, a distributed topology, a hub topology, a recursive topology, or a feedback topology.

The process defined in the analyzed instruction is characterized in that it comprises a primary entity.

The process defined in the analyzed command includes a listener for inputting data, a processor for processing the data, and a reporter for transmitting the data.

After the mapping is completed, the processing result is transmitted to the URL defined in the specification.

According to the present invention, it is possible to obtain only the data desired by the user using a user defined process.

BRIEF DESCRIPTION OF THE DRAWINGS The foregoing and further aspects of the present invention will become more apparent from the following detailed description of preferred embodiments with reference to the accompanying drawings. Hereinafter, the present invention will be described in detail to enable those skilled in the art to easily understand and reproduce the present invention.

1 is a diagram showing the configuration of a dynamic process management system for data processing in various environments of the present invention. As shown, the dynamic process management system for data processing in various environments includes an interface unit 100, a process based management unit 110, and a code base unit 120.

The interface unit 100 receives a specific command from the user. The interface unit 100 receives a command from an external user to allow a dynamic process management system for data processing in various environments to perform a specific operation.

As shown in FIG. 2, the process-based management unit 110 may include a request manager 200, an authority information storage unit 210, a class manager unit 220, and a class loader unit. A Class Loader 230 and a Process Manager 240.

The request manager unit 200 analyzes a command input through the interface unit 100. The request manager unit 200 determines whether the command input through the interface unit 100 is a command by a valid authority. The request manager unit 200 determines by receiving an ID or a specific access number for proving that the command is a right authority through the interface unit 100 to determine whether the command is a command by a right authority. However, the determination as to whether or not the right authority is not limited to the above, it is also possible to check the operation by receiving any information that can confirm the characteristics of the connected authority.

In addition, the request manager unit 200 analyzes the contents of the command. The command input through the interface unit 100 defines a specification that is a relationship between a plurality of processes.

3 shows a first embodiment of the specification as defined above. As shown, the specification defined by the command input through the interface unit is a linear topology. The linear topology refers to a structure in which two or more processes are connected in one direction. This topology is the most basic structure and method used in most middleware systems. That is, it receives one input and has one output through processing. The figure shows a connection relationship when there are processes P1, P2 and P3, and this is expressed as {P1-> P2, P2-> P3} when expressed in PML (Process Management Language).

4 shows a second embodiment of the specification as defined above. As shown, the specification defined by the command input through the interface unit is a join topology. The join topology is a structure that receives two or more inputs and processes them to produce one output. This topology is used when two or more inputs have meaning to each other. The figure shows the connection relationship when there are processes P1, P2, P3 and P4, which is expressed as PML as {P1-> P3, P2-> P3, P3-> P4}.

5 is a view showing a third embodiment of the specification defined above. As shown, the specification defined by the command input through the interface unit is a distributed topology. The distributed topology is a structure that receives one input and processes it and delivers it to two or more different processes. Depending on the information entered, which process to pass to can be added when the process is designed. The figure shows the connection relationship when there are processes P1, P2, P3 and P4, which is expressed as PML as {P1-> P2, P2-> P3, P2-> P4}.

6 shows a fourth embodiment of the specification as defined above. As shown, the specification defined by the command input through the interface unit is a hub topology. The hub topology refers to a topology that transmits information to two or more processes after receiving and processing two or more inputs. Like the join topology, the input information collects information related to each other and transfers the information to other processes according to conditions. The figure shows the connection relationship when there are processes P1, P2, P3, P4 and P5, which is expressed in PML as {P1-> P3, P2-> P3, P3-> P4, P3-> P5}.

7 is a view showing a fifth embodiment of the specification defined above. As shown, the specification defined by the command input through the interface unit is a recursion topology. The recursive topology is an application of the linear topology, and the output of one process is brought back into the input of its own process. Recursive topologies are used when repetitive work on specific information is required. The figure shows a connection relationship when there is a process P2, which is expressed as {P2-> P2} in PML.

8 illustrates a sixth embodiment of the specification as defined above. As shown, the specification defined by the command input through the interface unit is a feedback (feed-back) topology. The feedback topology is an application of the preceding topology, and the output of one process is brought back into the input of its own process. Feedback topologies are used when repetitive work on specific information is required. The figure shows the connection relationship when there are P1 and P3, which is expressed as {P1-> P3, P3-> P1}.

The authority information storage unit 210 stores the authority information. The authority information storage unit 210 stores information required for confirming whether the authority to which the request manager unit 200 is connected is a legitimate authority. The authority information storage unit 210 transmits the stored information according to the request of the request manager unit 200.

The class manager 220 determines which class the process defined in the command analyzed by the request manager 200 inherits. The structure of the process defined in the command is defined as a Process Schema. 9 is a diagram illustrating the structure of a process schema. As shown, the primitive object 900 at the top of the process schema inherits from all classes, and is defined by the administrator as the system's default name. The subclasses of the primary entity, the listener 910, the processor 920, and the reporter 930, are the most basic classes of the system. Each of the above classes plays a role for data input, processing and transmission, and may be generated as classes to be used for each user by inheriting these classes. The classes to be used for each user only have a data definition part and a method declaration part. Therefore, in general, general users inherit the interface and use the data definition unit to define methods according to the user's usage.

The class loader 230 loads a class determined by the class manager 220 into a memory. The class loader 230 reads the class determined by the class manager 220 from the code base unit 120 and loads the class into the memory.

The process manager 240 generates objects from classes according to the topology defined in the command analyzed by the request manager 200 and maps these objects to memory in the order of topology. After the mapping is completed in the memory, the processing result is transmitted to the URL defined in the specification.

The code base unit 120 stores a plurality of classes. The code base unit 120 stores classes newly defined in the process schema structure. A particular class of the plurality of stored classes is read by the class loader 230.

So far I looked at the center of the preferred embodiment for the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

1 is a diagram showing the configuration of a dynamic process management system for data processing in various environments of the present invention.

2 is a diagram illustrating the process-based management unit in detail.

3 shows a first embodiment of the specification as defined above;

4 shows a second embodiment of the specification as defined above;

5 shows a third embodiment of the specification as defined above;

6 shows a fourth embodiment of the specification as defined above;

7 shows a fifth embodiment of the specification as defined above;

8 shows a sixth embodiment of the specification as defined above;

9 illustrates the structure of a process schema.

Claims (9)

delete An interface unit for receiving a specific command from a user; A request manager unit for analyzing a command input through the interface unit, a class manager unit for determining which class the process defined in the command analyzed by the request manager unit inherits, and a class determined by the class manager unit Class loader for reading the code from the code base unit and loading it into the memory, and a process manager unit for generating objects from classes according to the topology defined in the command analyzed by the request manager and mapping these objects to memory in the order of topology. A process-based management unit including; And Dynamic process management system for processing data in various environments including a code base unit for storing the class related to the process information. 3. The method of claim 2, Dynamic process management system for data processing in a variety of environments, characterized in that the analysis of the input command is determined whether the command by a legitimate authority. The method of claim 3, Includes an authority information storage unit for storing the authority information, The request manager unit analyzes a command using information stored in the authority information storage unit. The dynamic process management system for processing data in various environments. The method of claim 3, The analysis of the input command comprises a analysis of a specification that is a relationship between a plurality of processes, the dynamic process management system for processing data in various environments. The method of claim 5, The specification is a linear topology, join topology, distributed topology, hub topology, recursive topology or feedback topology, dynamic process management system for data processing in various environments. The method of claim 5, The process defined in the analyzed command includes a primary entity, dynamic process management system for processing data in various environments. 8. The method of claim 7, The process defined in the analyzed command is A listener for inputting data; A processor for processing data; And A reporter for transmitting data; Dynamic process management system for data processing in a variety of environments comprising a. The method of claim 5, Dynamic processing management system for processing data in a variety of environments, characterized in that after the mapping to the memory, the processing result is transmitted to the URL defined in the specification.

Images