KR20010053766A - Automation device of intelligent network service customer data change management and method thereof - Google Patents

Abstract

The present invention relates to an automated apparatus and method for intelligent network service subscriber data change history management for automatically generating and managing change history of service subscriber data in a service management system (SMS) of an intelligent network system. By automating similar and repetitive tasks in writing and maintaining the program code for managing the history, it saves the development time and cost of the new service data system and has the advantage of facilitating the change history management of the service data.

Description

Automation device and intelligent network service customer data change management and method

The present invention relates to an automated apparatus and method for managing an intelligent network service subscriber data change history, and more particularly, to an apparatus for automatically generating and managing change history of service subscriber data in a service management system (SMS) of an intelligent network system. It is about a method.

In general, a physical function entity in an intelligent network system is composed of a service exchange function (SSF), a service control function (SCF), and a service data function (SDF). By performing these functions properly, smooth intelligent network service is provided. The intelligent network service controls the service using a large amount of service data by using a memory resident database in the service controller to enable various control in service request.

Since the service control device receives the intelligent network call generated from the service signal processing device and processes the service in real time, the function of maintaining a large amount of subscriber data is performed in the service management system.

Since there are many copies of the subscriber service data in the intelligent network, it is very important to match these data. Redundancy, node management and service data management functions are integrated to match multiple duplicate data.

In order to match the data between the service control device and the service management device, the two systems can be interworked with each other by a LAN. The data changed from the service control device is periodically applied to the counterpart system so that the changed contents are the same. It is also an important function to leave a history management for managing the changed contents in order to match the service subscriber data managed in this way.

The service subscriber information having a function closely related to the service function is predefined in a database table, and the service data management function is programmed in the service subscriber data management program development environment to manage the service data in order to implement the service management system function.

To this end, in order to manage the change history of the subscriber data in the service management system (SMS), a separate application management program has been developed to manage the change history of the subscriber data.

However, this environment has a problem in that it requires a long effort for maintenance because the development of the service data management system is prolonged and the service has to be changed even if the characteristics of the service are slightly changed.

Therefore, according to the development of intelligent network service, it is required to accept various requirements for users' intelligent network service and to develop and apply prompt service.

The present invention, in view of the above-described problems and requirements as described above, by automating the repetitive tasks in the creation and maintenance of program code for managing the change history of the intelligent network service subscriber data, the new service data system of The aim is to reduce development time and costs.

1 is a block diagram showing a process of subscriber data change history management according to the present invention;

2 is a flowchart illustrating a data change flow in automating service subscriber data change history according to the present invention.

3 is a structure diagram of change history management information according to the present invention;

<Description of Symbols for Major Parts of Drawings>

1: service subscriber data table schema 2: analyzer

3: service subscriber data table information 4: change history management generator

5: change history management information storage

6: change history management program code

7: service control system 8: service management system

9: service subscriber data table 11: change history table

111: serial number field 112: change time recording field

113: Service Number Field

114: Data Table Name Field

115: change classification field 116: user name field

117: change history content field

In order to achieve the above object, in the change history management apparatus of the service subscriber data,

A service subscriber data table schema analyzer for analyzing items requiring change history by analyzing a service subscriber table schema;

A change history management information storage unit for storing change history management information provided when the data of the service subscriber table information for which the analysis is completed is changed;

A generator for generating a change history management program code using information provided from the change history management information storage unit and the analyzed table information;

And a change history table for storing the changed history information when data is changed by executing the generated change history management program code.

In addition, in order to achieve the above object, in the change history management method of the service subscriber data,

Analyzing a service subscriber table schema to analyze items requiring change history;

Generating a change history management program code by using data change history management information on the analyzed service subscriber table;

And a third process of storing the changed history information in a change history table when data is changed by executing the generated change history management program code.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

First, the theoretical matters of the present invention will be described.

As mentioned above, in a diversified network environment, access and change management of service subscriber data is required by various access methods such as telephone and Internet. In such an environment, a change history management function of service subscriber data is essential. Service data managed in service management system must manage redundancy of redundant distributed data according to service data change by various access interfaces.

The data to be changed should be managed in the same way as the data of the service control device and the data of the service management device. When data change occurs on one side in order to match the data between the two systems, the changed contents are changed to the counterpart system by the upward downward transmission method. It should be reflected equally.

When the change of subscriber data occurs in the service control system, it is delivered to the service management system by the up-delivery method to match the data.

In this way, the service subscriber data of the service management system is changed to match data from the redundantly distributed system, and the change history is managed by the trigger of the change table. The change history management function of the subscriber data is complicated and the program workload is similarly simple due to the difference in the structure of the service subscriber table rather than a special algorithm. Program code of this part can be automatically generated according to the structure of the service subscriber table.

That is, by automating the function that is sensitively changed according to the structure of the service table, it is possible to immediately reflect the change required by the requirement change during the provision of the service or during the development.

1 is a block diagram illustrating a process of managing subscriber data change history according to the present invention. When a service subscriber data table schema 1 is input, the table name, key field name, After analyzing the record configuration field name and the data type item of each field, the service data table information 3 is generated based on the analysis information.

In the change history management information storage section 5, which stores information to be changed history management in accordance with the input, change, and deletion of service subscriber data in the above state, the value before and after the change is changed when the input information is changed. It provides information about and when deleting, it provides information to manage the value before it is deleted.

Subsequently, when the service subscriber data table information 3 is generated, the change history management generator 4 generates a subscriber according to the analyzed service subscriber table information 3 and the information provided by the change history management information storage 5. Program code for generating a history to be generated upon input of data, program code for generating a change history to be generated upon change, and program code 6 for generating a delete history to be generated upon deletion is generated.

FIG. 2 is a flowchart illustrating a data change flow in automating service subscriber data change history through each program code generated in FIG. 1, wherein the change of subscriber data from the service control system 7 is transferred to the service management system by an upward transmission method. 8), and then the data of the service subscriber table 9 starts to be processed (10) according to the generated change history program code, wherein the generated change history program code is a program code for service subscriber data input. In this case, it manages the contents of each newly input field. If it is a program code about change, it manages to compare the current value with the value before change. If the subscriber data is deleted, it manages the value before it is deleted.

At the same time, the changed subscriber data information is extracted and stored in the change history table 11.

3 shows the structure of the change history table for recording the change history of the service data according to the present invention, which is a table set in the service management system 8.

The structure of the change history table 11 includes a serial number field 111 for separately managing change history;

A change time record field 112 for recording a change history time of the service data;

A service number field 113 for recording a subscriber's intelligent network service number;

A data table name field 114 for recording a table name where a change history of service data has been generated;

A change classification field 115 for recording a change mode such as an input / change / delete / error;

A user name field 116 for recording a user account name which has changed the service data;

And a change history content field 117 for recording the name, value, key value, and the like of each field in which the change has occurred.

In this case, the change history field 117 is generated by the service subscriber data change history management program code.

As described in detail above, the present invention saves the development period and cost of a new service data system by automating similar and repeated tasks in writing and maintaining program code for managing change history of intelligent network service subscriber data. This has the advantage of facilitating change history management of service data.

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, those skilled in the art will be able to various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims You will have to look.

Claims (9)

In the change history management device of the service subscriber data, A service subscriber data table schema analyzer for analyzing items requiring change history by analyzing a service subscriber table schema; A change history management information storage unit for storing change history management information provided when the data of the service subscriber table information for which the analysis is completed is changed; A generator for generating a change history management program code using information provided from the change history management information storage unit and the analyzed table information; And a change history table for storing the changed history information when data is changed by executing the generated change history management program code. The method of claim 1, An item analyzed by the schema analyzer includes a table name, a key field name, a record configuration field name, and a data type item of each field. The method of claim 1, The change history management information storage device provides information about the input data when data is input, and provides information about the value before and after the change when the input information is changed, and the value before the deletion when the data is deleted. Intelligent network service subscriber data change history management automation device, characterized in that for providing information to manage. The method of claim 1, The program code generated by the program code generator includes program code for generating a history to be generated upon input of subscriber data, program code for generating a change history generated at the time of change, and deletion history generated at the time of deletion. An automated device for intelligent network service subscriber data change history management, characterized by comprising a program code. The method of claim 1, The change history table includes a serial number field for distinguishing and managing change history; A change time record field for recording a change history time of the service data; A service number field for recording the subscriber's intelligent network service number; A data table name field for recording a table name where a change history of service data is generated; A change discrimination field for recording a change mode such as input / change / delete / error; A user name field for recording a user account name which has changed the service data; And a change history contents field for recording a name, a value, a key value, and the like of each field in which a change has occurred. In the change history management method of the service subscriber data, Analyzing a service subscriber table schema to analyze items requiring change history; Generating a change history management program code by using data change history management information on the analyzed service subscriber table; And a third process of storing the changed history information in a change history table when data is changed by executing the generated change history management program code. The method of claim 6, An item to be analyzed in the first process includes a table name, a key field, and a data type item. The method of claim 6, In the second process, if the data change history management information is information about service subscriber data input, the contents of each newly input field are managed. If the program code is related to change, the previous value and the current value can be compared. If the deletion of the subscriber data, the intelligent network service subscriber data change history management method characterized in that to manage the value before being deleted. The method of claim 6, In the third process, the change history table includes a serial number field for classifying and managing change history; A change time record field for recording a change history time of the service data; A service number field for recording the subscriber's intelligent network service number; A data table name field for recording a table name where a change history of service data is generated; A change discrimination field for recording a change mode such as input / change / delete / error; A user name field for recording a user account name which has changed the service data; And a change history content field for recording a name, a value, a key value, and the like of each field in which a change has occurred.