JPH09106364A - Information controlling method and device therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prepare complete variable history data by separating the present status data table that a processing process utilizes and the log table that a data working process controlling the variation as a history and performing a statistic control of the variation utilizes. SOLUTION: A processing means 100 generates a log table 400 holding the contents of the changed record of a present status data table 300 as log data and a data working means 200 performs access to the table 400. The table 400 includes the additional time of the changed record of the table 300 and includes also the identification data showing the changed classification of any of the addition, the update and the deletion in the table 300. Thus, the present status data table 300 is generated and the record of the variation of the table 300 is stored in the log table 400 in the form of a successive addition, in the processing means 100, and the working means 200 refers to this table 400 and prepares various kinds of history information. Thus, the leakage of history information can be eliminated.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information management method and device, and more particularly to an information management method and device for managing information for performing various processes using a database in a computer system.

[0002] More specifically, when providing an information providing service to a customer in multimedia or the like, information such as when and what information was provided to the customer or transition information of a contract relationship between the customer and the service provider is provided. The present invention relates to an information management method and device for managing history information.

[0003]

2. Description of the Related Art Conventionally, when managing history information, processing or processing of information is performed using a current status data table representing the status of the current status. FIG. 19 shows the configuration of a conventional information management device. The apparatus shown in the figure comprises a processing unit 10, a data processing unit 20, and a current state data table 40. The current state data table 40 defines a time when an addition / update occurs by the processing unit 10 as an attribute, and the data processing unit 20 has a method of retrieving a change record by using the time attribute as a key. When the state as shown in the figure is set in the current data table 40, the data processing unit 20
Is accessed by a predetermined cycle or by some kind of trigger, and if the time range accessed last time is up to ta, this time, a record having a set time falling between ta and tb is searched. For example, in FIG. 19, when the data processing unit 20 reads the record (state 1, state 2, state 3) at the set time T1 at the time of the first record read, at the time of the second record read,
The record (state 1, state 2, state 3) at the set time T2 is read. The data processing unit 20 performs processing such as statistical processing and totalization processing on each read record.

[0004]

However, the above-mentioned conventional methods have the following problems. When a record is deleted from the current data table, everything including the set time is deleted, so it is impossible to recognize the fact that the record has been deleted in the data processing process.

When the data processing process accesses the current status data table once, and the same record is updated twice or more for the next access, only the latest update result and its update time remain in the current status data table. The data processing process reads the record. Therefore, the previous change history information is lost.

From the above, when the information providing service is provided to the customer by the computer system and the history of the customer and the history of the provided information (when, what information was provided, etc.) are managed, It will cause a point-like result. For example, as an event resulting from the above-mentioned problem, when the customer stops using the service, the record is simply deleted and cannot be detected by the data processing process. For this reason, it seems that the use continues forever. In addition, the fact that the information has been stopped cannot be detected.

Further, as an event resulting from the above problems, in the case of a system in which a customer can change a personal identification number or an ID for service access, the data processing unit must change the data two or more times before reading the record. If you do, you can recognize the latest PIN and the first change, but you cannot recognize the fact that it has been changed more than once. For this reason, it is difficult to accurately grasp the operation tendency of the customer. In other words, when statistical processing is performed once at the end of every month, if one record existing between the end of the previous month and the end of the current month is updated twice or more, the content of the record before the update is recognized. I can't.

The present invention has been made in view of the above points, and solves the above-mentioned conventional problems so that the change history in the middle is not lost even if the access cycle of the data processing process is extended. It is an object of the present invention to provide an information management method and device that can accurately recognize the fact that deleted records are deleted.

[0009]

FIG. 1 is a diagram for explaining the principle of the present invention. The present invention provides an information management method for managing, by a data processing process, a history of changes in a current status data table updated by a processing process performed using information in a current status data table that holds various status information. When the data table is updated (step 1), the changed record is sequentially added to the log table (step 2), and the processing process refers to the log table to generate history information (step 3). Then, the generated history information is referred to (step 4).

According to the present invention, when a change record of the current data table is added to the log table (step 2), the addition time is included as an attribute of the change record. According to the present invention, when a change record of the current data table is added to the log table (step 2), an identifier indicating any change type of addition, update or deletion is included as an attribute.

FIG. 2 is a diagram showing the principle of the present invention. The present invention is based on the present condition data table 3 which holds various status information.
00, processing means 100 for performing various processes using the state in the present situation data table 300, and updating, deleting, and adding the contents of the present situation data table 300 and updating the present situation data table 300, An information management apparatus comprising a data processing unit 200 for managing the history of deletion and addition changes, wherein the processing unit 100 stores a log table 400 that holds the contents of changed records in the current data table 300 as log data. The data processing unit 200 generates and accesses the log table 400.

Further, the log table 400 includes the addition time of the change record of the current data table 300. In addition, the log table 400 includes an identifier indicating a change type of addition, update, or deletion in the current data table 200.

As described above, according to the present invention, the processing means generates the current data table and stores the variation records of the current data table in the form of sequentially adding to the log table, and the data processing means stores the log. Various history information is created by referring to the table. In this way, by providing a log table for exclusively storing variation records as log information and sequentially adding them, it becomes possible to eliminate the leakage of history information.

In addition, when the data of the current data table is additionally registered in the log table, the registration time and the change type such as update, addition, and deletion are also recorded in the log table so that the data processing means can register the data. The processing according to the time can be performed, and the change state of the record registered in the log table can be grasped by the change type. Therefore, the data processing unit can generate the history information for all the records of the present condition data table generated by the processing unit.

[0015]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 3 shows the configuration of an information management device of the present invention. The information management device shown in FIG.
0, data processing unit 200, current data table 300,
It is composed of a log table 400 and a history information storage unit 600.

The processing unit 100 uses the present condition data table 30.
0 and the log table 400 are generated. Processing unit 100
Registers only status information in the current data table 300, and changes the contents of the current data table 300 (update,
When it is added or deleted), the time and its change type are set in the log table 400. When a record of the current status data table 300 is changed, the processing unit 100 first notifies the changed status of the current status data table 300 when a system (for example, a database system) notifies that the change has occurred. The record is read and additionally registered in the log table 400. At this time, the change occurrence time and change type acquired from the system are also acquired,
It is also possible to set in the log data table 400.

In the present invention, the set time information conventionally set in the current status data table 300 is unnecessary in the log table 400 because it is registered in the order of occurrence or the registered time is defined as a time attribute at the time of registration. . Also,
When the time attribute is not written in the log table 400, the processing unit 100 sets only the status information, and thus the current status data table 300 is set in order to prevent duplicate reading.
After reading the record, the read record of the current data is erased. Further, even when the log table 400 including the time attribute is generated, the present status table 300 may be deleted at the stage when the reading is completed due to the size problem on the memory or the like.

The data processing unit 200 includes a log table 40.
0 is read, history information for various purposes is generated, and stored in the history information storage unit 600. At this time, if the log table 400 does not include the time attribute, the data processing unit 2
At 00, the read record in the log table 400 is deleted to prevent duplicate reading. Further, even when the record including the time attribute is read, it may be deleted after the record of the log table 400 is read due to the size problem in the memory or the like. Further, the data processing unit 200 uses the generated history information to perform various kinds of processing such as statistics / survey processing.

The method of generating the log table 400 by the processing unit 100 will be described below. (1) When registering data that does not include a time attribute in the log table First, a case where data that does not include a time attribute is set in the log table 400 will be described. FIG. 4 shows the configuration of a log table that does not include time information according to the present invention. It is assumed that at least the first situation information is set in advance in the current situation data table 300 and the log table 400.

The processing unit 100 uses the present condition data table 30.
When there is a change in 0, the change information is overwritten in the current data table 300, and at the same time, the variation record of the changed current data table 300 is recorded in the log table 400.
The log table 400 is generated by additionally writing to the log table 400. Since the record of the log table 400 does not include the time information, the state information is simply written in the order of occurrence of the change. Therefore, since the record of the log table 400 does not include the time information of the occurrence, the processing unit 100
After reading the record, the current data table 300
Need to erase the record.

For example, when the following status information is set in the current status data table 300, status 1 = S11 status 2 = S11 status 3 = S11 These information are read out by the processing unit 100 and the log table When set to 400, the three pieces of status information in the current status data table 300 are deleted.

The data processing unit 200 reads the records of the log table 400 generated by the processing unit 100 and generates history information in chronological order. At this time, the creation time of the history information may be recorded in the history information storage unit 600 as the registration time. Further, when the history information to be stored in the history information storage unit 600 is generated in the data processing unit 200, in order not to read records of the same log table 400 in duplicate, the log table after the record of the log table 400 is read. It is necessary to delete 400 information.

Next, a procedure for the data processing unit 200 to access the records of the log table 400 and create a data table of time-series history information will be described. FIG.
FIG. 7 is a flow chart showing an operation of creating a time-series table of history information from a log table of the present invention. The operation described below is a case where only the state information is set in the log table 400 as shown in FIG.

Step 101) Data processing unit 200
4 searches the log table 400 shown in FIG. 4 and determines whether the status information is set in the log table 400. Step 102) Read out all the status information in the log table 400. Step 103) Since the log table 400 does not have an attribute indicating time, all the data in the log table 400 is erased after reading the record to prevent duplicate reading.

Step 104) Data processing unit 200
Compares the history information previously read and set in the history information storage unit 600 with the status information read in step 102. Step 105) As a result of collation, it is determined whether or not there is the same record. If so, the process proceeds to step 107, and if not, the process proceeds to step 106.

Step 106) Data processing unit 200
Adds the record read from the log table 400 to the history information storage unit 600 and sets the change history to "change". (Step 107) The data processing unit 200 performs a record deletion process. Specifically, the deletion flag is set to the record in the history information storage unit 600 without erasing the record information.

(2) When Registering Data Containing an Attribute Representing Time in the Log Table Next, the case of setting data containing an attribute indicating time in the log table 400 will be described. FIG. 6 shows the configuration of a log table including time information according to the present invention. Processing unit 10
0 acquires the system time passed from the system as the time when the current status data table 300 is changed, and
The variation record of the current data table 300 is acquired, and additional writing is performed to the log table 400.

When the current time data table 300 includes the occurrence time, the processing unit 100 does not acquire the system time, and logs the time acquired from the current status data table 300 as a time attribute together with the status information. Writing to the table 400 is also conceivable.

The data processing unit 200 includes a log table 40.
0 records are read in chronological order to generate history information,
It is stored in the history information storage unit 600. Further, when the history information is generated, the log table 400 may be deleted each time after the record of the log table 400 is read. If the log table 400 is large enough, it is not necessary to delete it.

Next, the log table 40 shown in FIG. 6 above.
A case where the data processing unit 200 generates history information from 0 will be described. FIG. 7 is a flowchart showing the operation of creating history information from the log table of the present invention. In the operation described below, the reading of the log table 400 may be performed in a predetermined cycle or in a non-cycle.

Step 201) The time is T1 = T in advance.
2, T2 = current time is set. Step 202) The data processing unit 200 reads all records in the data of the log table 400 whose set time value t is between T1 and T2.

Step 203) History information storage unit 600
Is searched to collate the individual data of the read log table. (Step 204) As a result of the collation, it is determined whether or not there is the same content.

Step 205) If a record having the same content exists, the record is deleted from the history information storage unit 600, a deletion flag is set, and the process proceeds to step 207. Step 206) If there is no record having the same content, the record read from the log table 400 is additionally written in the history information storage unit 600, and the change attribute is set to “update”.

Step 207) In the data of the log table 400, the record whose set time value t falls between T1 and T2 is deleted. (3) When registering data including time and change type in the log table 400 A case of setting data including an attribute indicating time and a change attribute in the log table 400 will be described.

FIG. 8 shows the structure of a log table including time attributes and change attributes according to the present invention. When a change occurs in the current status data table 300, the processing unit 100
The time and change type are acquired from the system, and additional writing is performed in the log table 400 together with the status information of the current status data table 300. The log table 400
Contains a change attribute indicating the time of occurrence and the content of the update, so there is no need to determine the deletion.

Next, an operation of generating history information from the log table 400 including the time attribute and the change attribute shown in FIG. 8 will be described. FIG. 9 is a flowchart of the operation of creating history information from the log table (FIG. 8) of the present invention.

Step 301) The time is T1 = T in advance.
2, T2 = current time is set. Step 302) The data processing unit 200 reads all the records in the data of the log table 400 whose set time value t is within the range of T1 and T2.

Step 303) Data processing unit 200
Refers to the change attribute, and if change attribute = delete,
The process moves to step 304. If the change attribute = addition / update, the process moves to step 305. (Step 304) If the change attribute is "delete", it is determined that the record is deleted, and a deletion flag is set to the corresponding history information in the history information storage unit 600, and then step 30
Move to 6.

Step 305) When the change attribute is "addition or update", additional writing is performed in the history information storage unit 600 as addition or update of the record. Step 306) In the data of the log table 400, the records with the set time value t within the range of T1 and T2 are deleted.

In general, when creating various history information, the data processing unit 200 creates a time-ordered table as original data for counting up for each history item. For example, as shown in FIG. 10, in order to manage the history of service subscription conditions for each customer, the history of start and end of provision of each piece of provided information, the history of provided prices, etc., a change history table 610 for each customer In the case where it is necessary to define a change history table 620 for each provided information, and the statistical processing unit 220 in the data processing unit 200 aggregates various contents to create statistical information and search for past states and the like. There is a method of searching each of the above tables 610 and 620 and displaying them on the display unit 230 in the data processing unit 200.

[0041]

An embodiment of the present invention will be described below with reference to the drawings. In the embodiment described below, a time attribute is given to the data in the log table 400, and an example is shown in which the data processing unit 200 generates history information from the log table 400.

FIG. 11 shows an example of the current data table according to the embodiment of the present invention. The same figure shows customer contract information. In the figure, the current data table 300 does not have a time attribute and a change attribute, but has a customer number and a contract status as status information. In this example, the contract status can be directly used as a change flag. The change flag is 0 = new subscription (addition), 1 =
Update, 2 = indicates withdrawal (deletion). FIG. 12 shows an example of the log table according to the embodiment of the present invention. At the same time that the processing unit 100 performs the process of changing the content shown in FIG.
Generate

The log table 400 in FIG. 12 is an example including a time attribute and a change type. Six records are registered as variation data of the present condition data table 300 shown in FIG. 11, and the processing unit 100 While acquiring the variation data, the time attribute and the change type are acquired from the system, and the log table 400 shown in FIG. 12 is generated. In the log table 400, a, b, c, d,
Six records e and f are registered. The record a of the log table 400 shown in FIG.
This is a generated record because the content of 00 has been changed (added) to 11:10:30 on January 10, 1995.
In the record b, the content of the current data table 300 is 95
The record is generated because it was changed (added) at 9:05 on January 15, 2015.

The meaning of this log table 400 is: a. The customer with the customer number “80” is January 10, 1995.
New to the day. b. Customer with customer number "90" is January 15, 1995
New to the day. c. The customer with the customer number “80” is February 25, 1995.
Updating to the day. d. The customer with the customer number "90" has left the group on March 3, 1995. e. The customer with the customer number “80” is updated on April 1, 1995. f. The customer with the customer number "70" newly joined on May 5, 1995. It has become.

FIG. 13 shows an example of history information before updating according to an embodiment of the present invention, and FIG. 14 shows history information after updating. The history information is sorted and managed using the customer number as a key. The update date of this history information is May 1, 1995, and the information up to April 30, 1995 is history information. Last updated on January 12, 1995
The day 13 shows the last update date (January 12, 1995)
Day). Therefore, the data processing unit 200
Then, the record of the log table 400 within the range from the last update date (January 13, 1995 to April 30th) is read and history information is generated. Therefore, the record of a in FIG. Since it is included in the history information generated last time, it is not read when the history information is generated this time.

As shown in FIG. 13, the history information storage unit 60
At 0, as of the last update date (January 12, 1995),
Only the information of the customer number “80” is set. The data processing unit 200 generates history information as follows. First, the data processing unit 200 reads the record of b of the log table 400 shown in FIG. 12 and sets it in the data column of the customer number “90” of the history information. At this time,
Since the change attribute is "new", "0" is displayed in the change information column.
Set (new subscription).

Next, the data processing unit 200 reads c of the log table 400 and sets it in the data column of the customer number “80” of the history information. At this time, since the change attribute is “update”, “1” (update) is set in the change information field. Next, the data processing unit 200 uses the log table 400.
Is read and set in the data field of the customer number “90” in the history information. At this time, since the change attribute is “delete”, “2” (delete) is set in the change information field.

Next, the data processing unit 200 reads e of the log table 400 and sets it in the data column of the customer number “80” of the history information. At this time, since the change attribute is “update”, “1” (update) is set in the change information field. The result set in this way is the history information shown in FIG.

Next, the data processing unit 200 deletes the data b, c, d, and e corresponding to January 13, 1995 to April 30, 1995 in the log table 400. In addition, the log table 400 is a table having a sufficient size,
If the unset area is larger than a predetermined size, it may not be erased.

Further, another example of one embodiment of the present invention will be shown. FIG. 15 shows another example of the current data table according to the embodiment of the present invention. The current data table 300 of FIG.
Customer number as status name, terminal ID as status information,
It consists of the contract information number.

The processing section 100 generates the present condition data table 300 shown in FIG.
The acquisition time and change type of each record of 0 are as follows. Customer number (state name) 80 Change type = new (= 0), acquisition time = 95,09,01
/ 10: 30: 30 Customer number (state name) 70 Change type = new (= 0), acquisition time = 95,09,01
/ 10: 30: 30: 20 Customer number (state name) 80 Change type = update (= 1), acquisition time = 95,09,10
/ 14: 00: 00 Customer number (state name) 70 Change type = update (= 1), acquisition time = 95,09,10
/ 14: 00: 10 Customer number (state name) 90 Change type = Delete (= 2), Acquisition time = 95,09,10
/ 14: 00: 20 As a result, the processing unit 100 reads out the change contents corresponding to the acquisition time, the change type, and the state name from the current state data table 300, and the log table 4 shown in FIG.
00 is generated. When the processing unit 100 reads the current status data to generate the log table 400 from the current status data table 300, the processing unit 100 erases the current status data table 300.

Further, the data processing section 200 generates history information from this log table 400. At this time, the time range for reading the log table 400 is designated as 0:00 on September 1, 1995 to 24:00 on September 10. As a result, FIG.
The history information shown in 8 is generated. 17 shows the history information storage unit 6 before reading the log table 400 shown in FIG.
This is an example of history information stored in 00, and only information regarding the customer number “90” is stored.

The data processing unit 200 reads the log table 400 shown in FIG.
One piece of history information of "0" was added, and finally the customer of customer number "90" withdrew from the information service on September 10, 1995, so the change flag has "2" (deleted).
Is set.

From such data, the customer number "9"
Since the “0” customer newly joined on June 10, 1995, when the data processing unit 200 aggregates the number of subscribers in each month, for example, as one of the subscribers as of June The customer with the customer number “90” can also be counted, and accurate counting can be performed.

Further, customer numbers "80" and "7"
Focusing on "0", it can be seen that both parties have finally changed the contract provision information number to "4" at the same time. In such a case, it becomes possible to use the history information as a statistical material such as at what time and at what time the provided information tends to shift to the provided information. That is,
Present data table 30 due to memory size issues, etc.
Even if 0 is deleted in a predetermined cycle or when the log table 400 is generated, by setting the time attribute and the change type in the log table 400, history information edited for various purposes can be created. Is possible.

Further, even if the present status data table 300 and the log table 400 are deleted from the viewpoint of memory size, by leaving the history information, the data processing unit 200 can perform various statistical processings. In addition, in the above-described embodiment, an example in which one piece of history information is generated from one log table 400 is shown, but the present invention is not limited to this example, and as shown in FIG. When the information of the item type is registered, the log table 400 is generated based on the information of the present status data table 300, and a plurality of types of history information is generated from one log table 400 for each purpose / item. It is also possible.

The present invention is not limited to the above embodiment, but can be variously modified and applied within the scope of the claims.

[0058]

As described above, according to the present invention, by separating the present data table used by the processing process and the log table used by the data processing process for managing and statistically managing the variation of the current data table as a history, Change history data can be created.

When the current data table is shared by the processing process and the data processing process, table access competition between the data processing process and the processing process may occur and the performance of the processing process may deteriorate. When the log table is separated, the process of adding the change code of the current data table to the log table is a standby process and can be separated from the process process, so that the problem of the above performance degradation can be avoided.

[Brief description of the drawings]

FIG. 1 is a diagram for explaining the principle of the present invention.

FIG. 2 is a principle configuration diagram of the present invention.

FIG. 3 is a block diagram of an information management device of the present invention.

FIG. 4 is a configuration diagram of a log table configured only by status information according to the present invention.

FIG. 5 is a flowchart showing an operation of creating history information from the log table (FIG. 4) of the present invention.

FIG. 6 is a configuration diagram of a log table including time information and state information according to the present invention.

FIG. 7 is a flowchart showing an operation of creating history information from the log table (FIG. 6) of the present invention.

FIG. 8 is a configuration diagram of a log table including a time attribute and a change attribute according to the present invention.

FIG. 9 is a flowchart showing an operation of creating history information from the log table (FIG. 8) of the present invention.

FIG. 10 is a diagram for explaining the creation of history information according to the present invention.

FIG. 11 is a diagram showing an example of a current data table according to an embodiment of the present invention.

FIG. 12 is a diagram showing an example of a log table according to an embodiment of the present invention.

FIG. 13 is a diagram showing an example of history information before updating according to an embodiment of the present invention.

FIG. 14 is a diagram showing an example of updated history information according to an embodiment of the present invention.

FIG. 15 is a diagram showing another example of the current data table according to the embodiment of the present invention.

FIG. 16 is a diagram showing another example of the log table according to the embodiment of the present invention.

FIG. 17 is a diagram showing another example of history information before updating according to an embodiment of the present invention.

FIG. 18 is a diagram showing another example of updated history information according to an embodiment of the present invention.

FIG. 19 is a block diagram of a conventional information management device.

[Explanation of symbols]

 100 processing unit, processing unit 200 data processing unit, data processing unit 210 history information generation unit 220 statistical processing unit 230 display unit 300 current data table 400 log table 600 history information storage unit 610, 620 change history table

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] October 16, 1995

[Procedure amendment 1]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

Claims (6)

[Claims] 1. An information management method for managing, by a data processing process, a history of changes in a current status data table updated by a processing process performed using information in the current status data table that holds various status information. Records that are changed in the table are sequentially added to the log table, the processing process refers to the log table to generate history information, and the data processing process refers to the history information. Method. 2. The addition time is added as an attribute of the change record when the change record of the current data table is added to the log table.
Information management method described. 3. When adding a change record of the current data table to the log table, an identifier indicating a change type of addition, update, or deletion is included as an attribute of the change record. Information management method. 4. A current status data table holding various status information, various processing using the status in the current status data table, and updating, deleting or adding contents of the current status data table as necessary. An information management device comprising a processing means and a data processing means for collectively managing the history of update, deletion, and addition changes of the current status data table, wherein the processing means stores the contents of the changed record of the current status data table. An information management apparatus, wherein a log table to be retained as log data is generated, and the data processing unit accesses the log table. 5. The information management device according to claim 4, wherein the log table includes an addition time of a change record of the current status data table. 6. The information management device according to claim 4, wherein the log table includes an identifier indicating a change type of addition, update, or deletion in the current status data table.