KR20030054301A - An apparatus and a method for data management in IMT-2000 system - Google Patents

Abstract

PURPOSE: A device for managing data of a mobile communication system and a method therefor are provided to supply a method of periodically collecting and managing data when automatically or manually collecting and measuring a large amount of data, when storing the collected information in a storage, and when obtaining results from the stored information, thereby reducing time for retrieving the storage and preventing network traffic from overlapping. CONSTITUTION: A schedule job execution module(201) collects data by measured periods based on absolute time, and outputs results. A periodic data collecting module(203) decides which job collects the data, based on absolute time from network nodes. A data storage module(204) has a storage for storing the collected data, and determines size of the storage. A data collection controlling module(205) controls various functions related to the data collection. A schedule data inquiry module(202) inquires of data results for a specific period.

Description

{An apparatus and a method for data management in IMT-2000 system}

The present invention relates to an asynchronous IMT 2000 system. In particular, in an asynchronous IMT-2000 system environment, a large amount of data, such as performance data generated from a plurality of network nodes, is generated in real time using a periodic method based on an absolute time. In the case of automatic and manual collection and measurement in order to obtain a result of a certain time period, the information collected in such a storage location is stored in a storage location, and then inquired to obtain a result of a certain time period from the information stored in the storage location in the future. The present invention relates to an apparatus and method for managing data in an operation preservation device of an asynchronous IMT-2000 system for efficiently reducing the time required to search a storage location and verifying a result thereof, and to prevent generation of unnecessary network traffic. .

As a prior art in this field, Korean Patent Registration No. 1998-62374 is disclosed. The present invention relates to a method of periodically collecting, storing, and inquiring data in an operation preservation apparatus of a network management system or a mobile communication system, but does not propose a method of efficiently storing and managing data generated from a plurality of network nodes. It also fails to disclose a technique for preventing the generation of unnecessary network traffic.

Also, in general, when managing time unit data of each network node's measurement type in one directory, the log file names are defined as [node] [measurement type] [year] [month] as defined in FIG. Can be used in order of [day] [hour] or [measurement type] [node] [year] [month] [day] [hour], but it is not systematically managed and the file is increased as the number of log files increases. The time spent searching is increased.

Also, in general, when managing daily data for each network node's measurement type in one directory, the log file name is defined as [node] [measurement type] [year] [month] as defined in FIG. Can be used in order of [day] or [measurement type] [node] [year] [month] [day], but this also is not systematically managed like FIG. The time spent searching is increased.

In order to distinguish the log files even when the weekly data of each network node is managed in one directory, the log file name is defined as [node] [measurement type] [year] [week] or [measurement] as defined in FIG. Type] [Node] [Year] [Week] can be used in order, but as in FIG. 1 and FIG. 2, it is not systematically managed and the time used for searching the file increases as the number of log files increases. There is a disadvantage.

SUMMARY OF THE INVENTION The present invention has been made in an asynchronous IMT-2000 system environment using a periodic method based on an absolute time based on a large amount of data such as performance data generated from a plurality of network nodes. Searching for a storage location, such as when collecting and measuring automatically and manually to obtain a result, and storing such collected information in a storage location, and later retrieving a specific time zone result from the information stored in the storage location. It is to provide a data management system and method that can efficiently reduce the time required to check the results.

In addition, it is to prevent the generation of unnecessary network traffic in order to obtain a result of a plurality of overlapping measurement time zones from one network node.

1 to 3 are diagrams illustrating a method of naming log files in order to distinguish log files when managing unit data for each measurement type of a general network node in one directory.

4 is a block diagram of an operation preservation apparatus in the asynchronous IMT-2000 system.

5 is a detailed block diagram of a data management apparatus according to an embodiment of the present invention.

6 is a block diagram illustrating a data storage method and a size of a storage location between a periodic data collection module and the data storage module.

7A to 7D are diagrams illustrating a method of managing a log file, which is a storage location for each time data storage module, which stores data in units of time, and a method of naming a log file.

8A and 8B are diagrams illustrating a method of managing a log file, which is a storage location for each data storage module, and a method of naming a log file, in which a unit of data is stored.

9A and 9B are diagrams illustrating a method of managing a log file, which is a storage location for each main data storage module, which stores data on a weekly basis, and a method of naming a log file.

10 is a flow chart for storing data in periodic automatic collection and log files.

11 is a flowchart illustrating periodic manual collection and storage using a log file.

12 is a flow chart illustrating periodic manual collection and storage using a shared memory space.

13 is a flowchart for explaining periodic automatic and manual collection termination.

14 is a flowchart for explaining collection data inquiry.

Data management apparatus according to an aspect of the present invention for solving this problem,

A data management device for collecting, storing, and inquiring statistical measurement data generated at a network node of a mobile communication system,

A job executing module for each schedule performing a function of collecting data by measurement period based on an absolute time and outputting a result;

A periodic data collection module that performs a function of determining which job among the execution jobs in the job execution module for each schedule, the data collection for each measurement period on an absolute time basis from the network nodes;

A data storage module having a storage location for storing the collected data and determining a size of the storage location;

A data collection control module in charge of various controls related to data collection;

It includes a schedule-specific data inquiry module for performing a function for inquiring the data results for any particular period stored in the storage location of the data storage module for each measurement cycle.

Next, the present invention will be described with reference to the accompanying drawings so that the present invention can be easily implemented by those skilled in the art as follows.

4 is a block diagram of an operation preservation apparatus in the asynchronous IMT-2000 system.

Referring to FIG. 4, the operation maintenance device of the asynchronous IMT 200 system includes a data management device 10, and the data management device 10 periodically and automatically collects, stores, and retrieves measurement statistical data. Communication is performed with the network nodes 3, 4, 5 generating measurement statistical data and the network 2 transmitting such data.

5 is a detailed block diagram of the data management apparatus 20 according to the embodiment of the present invention.

Referring to FIG. 5, a data management apparatus according to an embodiment of the present invention includes a job execution module 201 for each schedule, a data inquiry module 202 for each schedule, a periodic data collection module 203, and a data storage module 204. And a data collection control module 205.

In the job execution module 201 for each schedule, the execution job for each time slot (2011) collects data for each measurement period by a time zone defined in an end time (year, month, date, minute) at a specific start time (year, month, day, hour) on an absolute time basis. To print the result. The hourly execution job (2012) performs a function of collecting data for each measurement period by the time defined in the end time (year, month, date) from a specific start time (year, month, date) on an absolute time basis, and outputting the result by time. The daily execution job (2013) collects data for each measurement period by the time defined in the end time (year month date) from a specific start time (year month date) on an absolute time basis, and outputs the result daily. Weekly Execution Job (2014) collects data by measurement period and outputs the results by the start and end (hour and minute) time zones defined at the end time (year and day) from a specific start time (year and date) on an absolute time basis. . The monthly execution job (2015) collects data for each measurement period as the time defined in the end time (year month) from a specific start time (year month) on the basis of absolute time and outputs the result monthly. The infinite execution job 2016 performs a function of periodically collecting data on an absolute time basis without a predetermined time limit.

In the schedule-specific data inquiry module 202, the time-based inquiry job 2021 inquires the data result from the specific start time (year, month, date, minute) stored at the storage location for each measurement period at the end time (year, month, date, minute). Perform the function. The hourly inquiry job 2022 performs a function of inquiring by time the data result from the specific start time (year, month, date) stored at the storage location for each measurement period to the end time (year, month, date, time). The daily inquiry job 2023 performs a function for inquiring on a daily basis the data result from the specific start time (year month date) stored at the storage location for each measurement period to the end time (year month date). The weekly inquiry job 2024 performs a function of inquiring the data results of the start and end (hour and minute) time zones defined at the end time (year and month date) at a specific start time (year and date) stored in the storage for each measurement cycle. The monthly inquiry job 2025 performs a function of inquiring a data result from a specific start time (year month) stored at a storage location to an end time (year month) for each measurement cycle.

The periodic data collection module 203 is a module that performs a function of determining which job among the execution jobs in the job execution module 201 for each schedule to collect data for each measurement period on an absolute time basis from network nodes. At the same time, data collection from a network node is performed in only one job, and the automatic collection unit 2031 performs a function of periodically collecting data through the infinite execution job 2016, and a manual collection unit ( 2032 performs a function of periodically collecting data through the time running job (2011), hourly running job (2012), daily running job (2013), weekly running job (2014), monthly running job (2015). do.

The data storage module 204 is a module for determining a size of a storage location. The time unit storage 2041 stores a time unit at a storage place, and the daily unit storage 2042 is a unit of storage at a storage place. The main unit storage 2043 performs a function of storing in a storage unit on a weekly basis.

The data collection control module 205 is a module that is in charge of all the control related to data collection, and the node / measurement type collection operator identifier 2051 is a schedule type job at a node of a measurement type or a measurement type of a node at present. The execution module 201 determines which execution job is operating, and the collection completion identifier 2052 for each node / measurement type uses the measurement type of the corresponding node when data of a certain measurement period is used in a plurality of execution jobs. Alternatively, the function of identifying whether the data of the node of the measurement type has been collected by the job is completed, and the node / measure type pause identifier 2053 temporarily collects the data of the node of the measurement type or the measurement type of the node. The node / measurement type restart identifier 2054 may perform the measurement function or the measurement type of any paused node. Restarts node data of type.

6 is a block diagram illustrating a data storage method and a size of a storage location between the periodic data collection module 203 and the data storage module 204. The periodic data collection module 203 uses an automatic and manual collection method. By collecting the data of each network node by the measurement type or the node of the measurement type periodically by the measurement period based on the absolute time and to store in the data storage module 204, if the storage location is configured by the time unit time data storage module 3021 ), The data storage module 3021 is configured as a day unit, and the main data storage module 3021 is configured as a week unit, and a new data storage module 3021, 3022, 3023). The size of the data storage module 3021, 3022, 3023, that is, the size of the storage location in the data storage module is determined by a case where a measurement type of a node or a node of a measurement type is not collected temporarily or by a termination process. In the case of not collecting data, the size of the storage locations 3031, 3032, 3033 is variable because no data exists in the storage location during the period.

7A to 7D illustrate a method of managing a log file, which is a storage location for each time data storage module, and a method of naming a log file, which store data in units of time. By managing log files on the directory system 411, 413, 421, and 423 defined in FIG. 7D, the files can be efficiently managed, and the searching time required to find the log files during execution can be minimized. The log file names (412, 414, 422, 424) can be simplified and managed.

8A and 8B illustrate a method of managing a log file, which is a storage location for each data storage module, and a method of naming a log file, in which a daily data is stored. By managing log files on the directory systems 511 and 513 defined in FIG. 8B, the files can be managed efficiently, the search time required to find the log files during execution can be minimized, and the name of the log files. (512, 514) can be simplified and managed.

9A and 9B illustrate a method of managing a log file, which is a storage location for each main data storage module, and a method of naming a log file. FIG. 9A and 9B illustrate an increase in log files. By managing log files on the directory systems 611 and 613 defined in FIG. 9B, the files can be managed efficiently, the search time required to find the log files during execution can be minimized, and the name of the log files. 612 and 614 can be simplified and managed.

The operation of the data collection device according to the embodiment of the present invention having such a structure will now be described in detail.

10 is a flow chart for storing data in periodic automatic collection and log files.

First, when the automatic collection is started (S701), the process transitions to the multi-thread generation and driving (S702) step for collecting data for generating and driving a plurality of threads for performing data collection and storage.

In the multi-thread generation and driving (S702) step of collecting data, the data collection control module 205 preferentially establishes a connection operation identifier 2051 for each measurement type of the node or for each node of the measurement type, and restarts it. The identifier 2054 is set (S703).

Thereafter, after performing the step of waiting (S704) by an absolute time basis (measurement period + delay time) in order to synchronize data before each thread is driven, if the corresponding time has elapsed, the measurement type of the corresponding node or corresponding The process proceeds to step S705 in which a log file exists to check whether a log file capable of storing time zone information of each node of the measurement type exists.

In the log file existence check (S705) step, if the log file exists, a pause identifier for checking whether the measurement type of the corresponding node or the pause identifier for each node of the measurement type is in the pause state is determined. The process proceeds directly to the status check step (S707), and if the log file does not exist, the process proceeds to the pause identifier status check step (S707) after performing the log file generation step (S706) that executes a function of generating a log file.

In the pause identifier status check step (S707), the data collection control module 205 determines whether the pause identifier 2053 for each measurement type of the corresponding node or for each node of the measurement type is in the pause state and if the corresponding node is in the pause state. The log file of each measurement type or the node of the measurement type of the transition to the log file end time check step (S710) to determine whether the end of the time, day or week unit, and if the status is not paused, or by the measurement type of the node The endlessly running job for each node of the corresponding measurement type is transferred to the manual operation identifier access check step (S708) to determine whether data collection is possible from the network node.

In step S708, it is determined whether or not data is collected from the network node through the infinite execution job (2016), and when the network node data is not collected through the infinite execution job (2016), the log file end point is checked. Step S710), and if the network node data is collected through the infinitely running Job (2016), the log after performing the data collection / log file storage step (S709) to collect the data for each cycle and store in the log file, the log Transfer to the end of the file check step (S710).

In the log file end point check (S710) step, it is determined whether the end point of time, day, or week is performed. If the log point ends, the log file ends (S711). Transitioning to standby (S704) by an absolute time basis (measurement period + delay time) to perform, and transitioning to standby (S704) step by (measurement period + delay time) on an absolute time basis immediately if not an end point. Repeat to run.

11 is a flowchart illustrating periodic manual collection and storage using a log file.

When manual collection starts (S8101), the manual collection unit (2032) is transferred to the input parameter normal check step (S8102) to determine whether parameters such as network node, measurement type, Job type and time information has been input normally. do.

In step S8102, the input parameter is normally checked to determine whether an error occurs in the parameter and terminates (S8120). If the parameter is normal, the same thread exists to determine whether the same job is currently being executed (S8103). Metastasize.

If the same thread exists in the step of checking whether the same thread exists (S8103), the process is terminated (S8120). Otherwise, the relevant parameter is set to set a common parameter related to the corresponding job and to create and run a thread for each node of a measurement type or node of a measurement type. Transfers to setting / managing thread creation / drive (S8104).

In the step of setting the parameter and creating / running a thread for each management target (S8104), the corresponding thread is driven, and the driven thread waits (S8105) by the absolute time basis (measurement period + delay time) to synchronize. Then, when the corresponding time has elapsed, it is determined whether the job is a time zone / time / day / week / month job by executing a job-by-schedule job determination step (S8106) to determine a job by schedule using input parameters related to the job type. To perform the job of the unit, first, a transition to the pause identifier status checking step (S8107) confirming whether the pause identifier of the job for each node of the measurement type or the node of the measurement type is in the pause state.

In the pause identifier status check (S8107) step, if the status of the corresponding job is in the paused state, the process is transferred to the end of measurement check step (S8116) which determines whether the thread should be terminated when the end time is reached. In step S8108, the mobile terminal identifies whether the network node data is collected through the driven execution job.

In the manual MID connection check (S8108), when network node data is collected through the currently run execution job, data collection / calculation (S8114) is performed to collect and calculate network node data, and the data collected from the network node is logged. After performing the step of saving the collected data log file (S8115) to save to a file, the process transitions to the end of measurement (S8116) to check the end point of the thread, and the data from the network node through the currently run Job Job. If it is not collected, the process proceeds to the step S8109 of determining whether the network node data is collected from the running job other than the currently running running job.

In the other passive movable identifier connection check step (S8109), if the network node data is not collected through the execution job other than the currently executed execution job, the connection operation identifier of the currently running execution node by measurement type or node by measurement type is set. After performing the manual operation identifier access setting (S8112) step of granting the data collection priority from the network node, perform the data collection / calculation (S8114) step of collecting and calculating data from the network node. After performing the step of storing the collected data log file (S8115) to store the collected data in the log file, the process proceeds to the measurement termination check (S8116) step of confirming the end point of the thread, and any other operation other than the currently run JobJob. When data is collected from the network node through a running job, the data collection is completed and stored in the log file. Confirmed complete collection identifier completed to determine transitions to (S8110) step.

In the step of checking whether the collection completion identifier is completed (S8110), if data collection is completed from the network node through any execution job other than the currently executed execution job and is not stored in the log file, the operation is repeatedly performed (S8111). When the data collection is completed and stored in the log file, after performing the data collection / calculation (S8113) step of executing the process of collecting and calculating the data from the log file, whether the end time is reached and the thread should be terminated. Transition to step (S8116) to determine whether the measurement is terminated.

In step S8116, if the thread is not terminated, the process transitions to waiting (S8105) to collect and calculate data of the next cycle (S8105). The process proceeds to step S8117 of manually operating identifier connection for checking whether the collector movable identifier of the execution Job is connected.

In the manual movable identifier connection setting step (S8117), if the collector identifier of the currently executed running job is connected, a thread termination for performing a collector identifier disconnection (S8118) step of disconnecting the collector identifier is performed and terminating the thread. After performing the step (S8119), the manual collection function is terminated (S8120), and if the collector operation identifier of the currently run execution job is not connected, the thread is terminated (S8119). The function ends (S8120).

12 is a flow chart related to periodic manual collection and storage using a shared memory space, which performs the processing as shown in FIG. 8-1, but does not collect data using a log file, but instead stores data in a shared memory for a corresponding measurement cycle time. There is only a difference to collect and calculate (S8213).

13 is a flowchart for processing of ending periodic automatic collection and manual collection.

When the termination process by request starts (S901), the process proceeds to the input parameter check whether the parameters such as the network node, the measurement type and the job type has been normally input (S902).

In step S902, the parameter analysis is performed. If an error occurs in the parameter, the process is terminated (S910). If the parameter is normal, the infinite execution job (2016) is determined to determine whether the request job is an infinite job (S903). Transition to step).

In step S903, if the requested job is infinitely executed job (2016) in step S903, the step of infinitely executing job collection movable identifier connection setting for checking the connection status of the collection movable identifier 2051 of the corresponding job is performed (S908). If the collector identification identifier is set to be connected at the step of confirming whether or not the unlimited execution job collecting operation identifier is set (S908), after performing a collection operation identifier access release step (S909) of releasing a connection state of the collection identifier, End (S910) processing, and if the collecting operation identifier is not set to connect immediately end (S910) processing.

In addition, if the requested job is not an infinitely running job in step S903, the step of checking whether the job exists is determined to determine whether or not a thread related to the job exists (S904). If the job does not exist in the step (S904) step is terminated (S910) processing, and if the job exists, check whether the job collection movable identifier connection setting to check the connection status of the collection movable identifier of the job (S905) step Perform

If the collection identifier is connected in the step of confirming whether the Job Collecting Identifier is set to be connected (S905), the collection operation identifier is released (S906) to release the connection state of the Collecting Identification Identifier (2051), and the corresponding Job After performing the corresponding Job Thread Termination (S907) step to terminate the associated thread, processing is terminated (S910), and if the Collective Operation Identifier is not set, the corresponding Job Thread Termination (S907) is performed and then terminated (S910). Process.

14 is a flowchart for inquiring collected data stored in a log file;

When the data inquiry is started (S1001), the process proceeds to step S1002 of checking whether the parameter is normally input or not.

In the step of checking whether the input parameter is normal (S1002), if the error occurs in the parameter, the process is terminated (S1007). If it is normal, the corresponding log file selection (S1003) step of selecting a log file that satisfies the corresponding period is performed. After the execution, the process proceeds to step S1004 to check whether data exists in the log file.

In the step of checking whether the data exists (S1004), if the data does not exist, the process proceeds to the step of checking whether or not it is necessary to search for further data (S1006). After performing step S1005), the process proceeds to step S1006.

In step S1006, if more data retrieval is required, that is, if there are more log files satisfying the corresponding period, the process proceeds to the corresponding log file selection step (S1003). S1007).

In addition, this embodiment of the present invention is disclosed for the purpose of illustration, various modifications, changes, substitutions and additions are possible to those skilled in the art through the spirit and scope of the present invention disclosed in the appended claims.

As described above, in the embodiment of the present invention, in the asynchronous IMT-2000 system environment, a large amount of data such as performance data generated in a plurality of network nodes is used in real time using a periodic method on an absolute time basis. In the case of automatic and manual collection and measurement to obtain the result of a certain time period, and storing the collected information in the storage location, and later inquiring to obtain the result of a certain time period from the information stored in the storage location, By providing a method of collecting and managing data periodically, the time required to search the storage location and confirm the result can be effectively reduced, and unnecessary duplication of network traffic can be prevented.

Claims (18)

A data management device for collecting, storing, and inquiring statistical measurement data generated at a network node of a mobile communication system, A job execution module according to a schedule which performs a function of collecting data for each measurement period based on an absolute time and outputting a result; A periodic data collection module configured to determine which job is to be executed during the execution job in the job execution module for each schedule by the measurement period on an absolute time basis from the network nodes; A data storage module having a storage location for storing the collected data and determining a size of the storage location; A data collection control module in charge of various controls related to data collection; And And a data inquiry module for each schedule which performs a function for inquiring a data result for a specific period stored in a storage location of the data storage module for each measurement period. The method of claim 1, The job execution module for each schedule includes: A time-phased execution job that collects data for each measurement period and outputs the result as much as the time zone defined in the end time from the specific start time in the unit of year, month, day, hour, and hour based on the absolute time; An hourly execution job that collects data for each measurement period and outputs the results by time as defined by the end time from a specific start time in the unit of the year, month, date and time based on the absolute time; A daily execution job that collects data for each measurement cycle and outputs the result daily by the time defined in the end time from the specific start time in the unit of the month and the month, and A weekly execution job that collects data for each measurement period and outputs the results from the start time and end time zone defined in the end time from the specific start time in the unit of year and month, and A monthly execution job that collects data for each measurement period and outputs the results monthly by the time defined in the end time from the specific start time of the year and month basis, And an infinite execution job that performs a function of periodically collecting data on an absolute time basis without a predetermined time limit. According to claim 1 or 2, wherein the schedule-specific data inquiry module, A time-based inquiry job that inquires the data result of the end time at a specific start time stored in the storage location by measurement cycle, An hourly inquiry job that performs a function of inquiring hourly data results from a specific start time to an end time stored in a storage location for each measurement cycle; A daily inquiry job which performs a function of inquiring daily data results from a specific start time to an end time stored in a storage location for each measurement cycle; A weekly inquiry job that performs a function of querying the data results of the start and end time zones defined at the end time at any specific start time stored in the storage location by measurement cycle; A data management device including a monthly inquiry job which performs a function of inquiring a data result of an end time at a specific start time stored in a storage place for each measurement cycle. The method of claim 1, wherein the periodic data collection module, An automatic collector performing a function of periodically collecting data through the infinite execution job; And a manual collector configured to periodically collect data through the time slot execution job, the hourly execution job, the daily execution job, the weekly execution job, and the monthly execution job. The method of claim 1 or 4, wherein the data storage module, A time unit storage for storing data in a time unit at a storage location; Daily storage for storing data on a storage location by day, A data management device including weekly storage for performing a function of storing data on a weekly basis in a storage location. The method of claim 1, wherein the data collection control module, A collector / operator identifier per node / measurement type that performs a function of identifying which execution job in the job execution module for each schedule is operating in a measurement type of a node or a node of a measurement type; When the data of a measurement cycle is used in a plurality of execution jobs, a collection completion identifier for each node / measurement type that performs the function of identifying the measurement type of the node or the collection of node data of the measurement type by the job; Perform the function of temporarily not collecting measurement data of a node or node of a measurement type, and a pause identifier by node / measurement type, And a node / measurement type restart identifier for performing a function of restarting a measurement type of a paused node or node data of a measurement type. The method of claim 1, wherein the periodic data collection module, Using the automatic and manual collection method, data of each network node by type of measurement or by node of measurement type is collected periodically by measurement period based on the absolute time and stored in the data storage module. It is a storage module, which consists of a daily data storage module when configured in units of days, and a main data storage module when configured in units of weeks, and configures a new time, day, or week data storage module for each time, day, or week. And the size of the storage module is variable in case of not collecting the measurement type of a node or node data of a certain measurement type temporarily or collecting data by the termination process. 8. The method of claim 7, wherein the time data storage module is used to efficiently manage a log file, which is a storage location for each time data storage module, to reduce a search time required to find a log file, and to simply manage a name of a log file. A log file, which is a storage location for each module, is managed in a directory system in the order of (node-measurement type-year-month-day), and a log file name is assigned at a corresponding time. 8. The method of claim 7, wherein the time data storage module is used to efficiently manage a log file, which is a storage location for each time data storage module, to reduce a search time required to find a log file, and to simply manage a name of a log file. And a log file which is a storage location for each module in a directory system of (measurement type node-year-month-day), and gives a log file name at a corresponding time. The method of claim 7, wherein And a log file which is a storage location for each time data storage module in a directory system in the order of (node-measurement type-year-month) and give a log file name to a corresponding day and time. The method of claim 7, wherein And a log file which is a storage location for each time data storage module in a directory system of (measurement type node-year-month) order, and give a log file name to a corresponding day and time. The method of claim 7, wherein In order to efficiently manage the log file which is the storage location for each daily data storage module, reduce the search time required to find the log file, and simply manage the name of the log file, the log which is the storage location for the daily data storage module A data management apparatus comprising managing a file in a directory system in the order of (node-measurement type-year-month) and assigning a log file name to the corresponding day. The method of claim 7, wherein In order to efficiently manage the log file which is the storage location for each daily data storage module, reduce the search time required to find the log file, and simply manage the name of the log file, the log which is the storage location for the daily data storage module A data management apparatus characterized by managing files in a directory system of (measurement type node-year-month) order and giving log file names to the corresponding days. The method of claim 7, wherein In order to efficiently manage log files, which are storage locations for each main data storage module, reduce search time required to find log files, and simply manage log file names, log, which is a storage location for each main data storage module, A data management apparatus for managing files in a directory system in the order of (node-measurement type-year) and giving log file names to the corresponding weeks. The method of claim 7, wherein In order to efficiently manage log files, which are storage locations for each main data storage module, reduce search time required to find log files, and simply manage log file names, log, which is a storage location for each main data storage module, A data management apparatus characterized by managing a file in a directory system of (measurement type node-year) order and giving a log file name to the principal. A data management method for collecting, storing, and inquiring statistical measurement data generated at a network node of a mobile communication system, Collecting data by a predetermined measurement period based on an absolute time; Terminating the collection when the collection end condition is reached; Determining the size of a storage location and storing the collected data in a predetermined place; And Querying the data result for a specific period stored in the storage location for each measurement period. The method of claim 16, The data collection step, the data management method characterized in that to collect data automatically and manually according to the user's selection. The method according to claim 16 or 17, The data inquiry step, Step 1 for determining whether the parameter is entered correctly, Step 2 of analyzing the parameters in the step 1 and terminating if an error occurs in the parameters, Step 3 of selecting the log file that satisfies the period if the parameter does not occur by analyzing the parameter in step 1, Step 4 of checking whether or not the data exists in the log file in step 3, Step 5, if the data does not exist in the step 4 to transition to the end of the step of confirming whether or not to search for further data using another log file; If the data exists in step 4, after calculating the data, step 6 of transitioning to the step of confirming whether the end of the step of checking whether or not to search for further data using another log file, Step 7 of selecting the log file that satisfies the period if the data search using the other log file is necessary in the step of checking whether the termination; And an eighth step of performing termination processing if data retrieval using another log file is not required in the termination check step.