KR102011694B1 - Public institutional income property linkage data verification system and its recording medium - Google Patents

Abstract

The present invention relates to a system for verifying income property-associated data of a public institution which shortens a verification time of public data, and to a recording medium thereof. The system of the present invention comprises: a physical numerical module; an associated environment module for checking validation of a server certificate and a license; a fault pattern type module; a fault number statistic module having the number of temporal service faults in statistics; an error module for managing errors for data matching violation of an associated server; a non-fault cycle module for managing unprocessed information; a first pre-error detection tool of public data; a second pre-error detection tool; a data re-request tool for re-requesting the public data; and a server storage tool of data determined as appropriate data.

Description

Public institutional income property linkage data verification system and its recording medium}

The present invention relates to a system for verifying income data linked to public institutions and its recording medium, and more specifically, to minimize disability by preliminary measures through the prediction of disability, and to clearly classify and monitor the disability (judgment, speculation) factors. A physical numerical value (Hardware Zone) module for classifying and storing the associated server CPU, memory, storage, and process operation proper values and reference values and statistics; An Environment Zone module that checks the S / W related server certificate and license validity of the linked server; Trouble Pattern Zone for storing network connection failure information (No Connection, Long Data Error) information of the linked server, processing error and delay information of database, and service down and error information of linked S / W module; A trouble counting zone module for statisticing the number of temporary service failures by the corresponding system load of the related server; An error (Data Error Zone) module for managing an error regarding a data integrity violation of the linked server; Trouble Period Zone module for managing the unprocessed information within a specific period of the linked server, including, reducing the verification time of the public data, increase the efficiency of pre-detection of the data in error, and the error occurrence data It relates to a public institution income data linkage verification system to provide a data verification tool that can formalize and specifically implement the flow of re-request patterns to increase the suitability and accuracy of the data and to improve the quality and reliability of public services.

In general, the number of information-linked species and data has increased continuously since the opening of the Social Security Information System, but the fragmentation rule-based data verification has a very low hit rate compared to the time required to check the normal status of each data. .

As a result, the overburden and the error data of each person in charge may cause a negative effect on the public welfare service provision.

Checklists of conventional monitoring include data validity rate, maximum / minimum value, format, duplicate status, and number.

However, in the fragmentary verification method of public data, the hit ratio against the time required to check whether the suspicious data is normal is very low, resulting in inefficiency.

Therefore, it is necessary to identify and apply verification patterns suitable for the characteristics of public data.

Korean Patent No. 1100241 Korean Registered Patent No. 1219364

The present invention has been made to solve the above problems, and an object of the present invention is to provide a tool for determining the formal error and the actual content error verification pattern of the official data received from the related organizations to determine relatively quickly.

In addition, the present invention, by formalizing the format error pattern of the various public data provided from a number of the related institutions, it is possible to detect in advance before the error verification of the actual content, so that the error has already occurred at the beginning of data generation Another purpose is to increase the efficiency of pre-detection of collected data, select only suitable data, and lead to verification of contents, thereby reducing the amount of work required by reducing a considerable amount of data verification time.

In addition, the present invention provides a standardized and reliable verification tool for the verification of the secondary content of public data that has undergone the first formal error pattern, thereby shortening a series of processes of storing and databaseting only the data whose validity is verified on the server. In addition, the aim of the present invention is to improve the reliability of the public service by improving the accuracy of the data stored on the server and the quality of the public service provided therefrom.

In order to solve the above problems, the present invention minimizes the failures by preliminary measures through the prediction of the failures, and in order to clearly classify and monitor the failures (decisions, guesses), the connection server CPU, memory, storage, and process operation proper values and reference values And a physical numerical value (Hardware Zone) module that classifies and stores the data as storage. An Environment Zone module that checks the S / W related server certificate and license validity of the linked server; Trouble Pattern Zone for storing network connection failure information (No Connection, Long Data Error) information of the linked server, processing error and delay information of database, and service down and error information of linked S / W module; A trouble counting zone module for statisticing the number of temporary service failures by the corresponding system load of the related server; An error (Data Error Zone) module for managing an error regarding a data integrity violation of the linked server; And a trouble period zone module for managing unprocessed information within a specific period of the linked server.

The linked server is a government server 100, a consignment management system 200, a government linked server 300, a consignment linked server 400, a target department server linked to the social security information system (government) ( 500) is connected with one or more servers of the new all-administration system 600 of the central administrative agency (Ministry of Administration and Security) of the country.

The input / output or status of the data is monitored by a monitoring server, and the warning or failure is diagnosed by determining the connection status of the prediction server, and manual or minor failure through manual for each case is automatically taken. In addition, it provides uninterrupted linked service by checking warning contents and taking notice or taking action in advance.

The internal connection server and the external connection server application among the linked servers collect CPU, memory, storage, and process information to generate a file, and generate files, and the ESB (Enterprise Service Bus) or other EAI (Enterprise) in the linked server. Application Intergration) transmits the file to the monitoring server, and the monitoring server application reads the file, stores the status of the status in the linked DB, and pools the linked DB on a regular basis to display the status in the Hardware Zone.

When the number of failures within the Check Start Time and Check End Time range is more than 80% in the associated DB related to the storage of the linked server, the screen is displayed as a temporary failure due to service overload when there is no result corresponding to the failure pattern type. When there is a result corresponding to the failure pattern type, the prediction result of the failure pattern is displayed first.

The linked DB is inquired in units of 1 hour, the data is analyzed within 1 hour based on the current time, the error information is registered in the Log DB, and the Log DB is inquired to display a Trouble Pattern Zone Error.

Generates group data by classifying the total number of inputs and error totals up to 1 hour before the current time in the linked DB, and generates data data based on the linked ID in the group data screen, and results based on the transaction ID. You can create data and check the error content in the Result data.

The monitoring server transmits the data to the associated server, and the associated server encrypts the data. When the failure occurs, the monitoring server normally displays the error, but the error is displayed on the screen.

The linked DB generates monthly, weekly, and yearly mapping data for batch processing, and if the data does not exist in the log DB, it is processed in process units according to the attributes of the data and displayed in the monitoring chart zone if the unprocessed date is more than 1 day. do.

When the number of faults within the Check Start Time and Check End Time range is above 80% in the linked DB, if there is no result corresponding to the failure pattern, it is indicated as a temporary failure due to service overload and the result corresponding to the failure pattern. If is present, the prediction result of the disability pattern is displayed first, so the prediction result by the number of failures is excluded.

The self-diagnostic function of the linked server determines whether there is a failure by executing a predetermined rule to prevent the failure in advance, and separates the failure unit and continues operation when necessary.

The present invention manages the CPU, Memory, Storage, Process, and is divided into Inner (internal linkage) and Outer (external mandatory linkage, external semi-mandatory linkage).

Internal linkage is a linked server managed by the Ministry of Welfare (Development Institute) and checks the status every 5 minutes.

The external linkage is a linked server managed by an external organization. The external mandatory linkage checks the status in 1 hour units and the external semi-mandatory linkage in 12 hours.

If the utilization rate of each status is more than 75%, a red box is displayed, and if it is more than 90%, it is indicated as a predictive failure in the Monitoring Chart Zone.

The present invention made as described above is relatively fast by formalizing formal errors and actual content error verification patterns of public data generated to provide public services for not only 17 related agencies that are currently distributed but also a number of related organizations that may occur in the future. The ability to make judgments can dramatically reduce the time required to verify public data, providing an effective tool that can reduce the time required to verify significant amounts of data.

In addition, the present invention improves the error detection efficiency of data by distinguishing formal errors from public data and errors of actual contents, thereby storing only the data whose validity is verified on the server and providing a database by providing a reliable verification tool. It is expected to shorten the process, but to improve the accuracy of the data, the quality of services provided to them, and the reliability of the services.

1 is a view showing a configuration diagram.
2 is a view showing a monitoring linkage range (integration control + linkage + security).
3 is a diagram illustrating a screen configuration diagram.
4 shows a process summary.
6 is a view illustrating a detailed hardware area (Zone) function.
7 is a diagram showing a processing step (Hardware Zone processing process).
8 is a diagram illustrating a data processing relationship diagram.
9 is a diagram illustrating a system linkage (process) relationship diagram.
10 is a diagram showing processing logic (error and prediction indication).
As shown in FIG. 11, a query showing a failure and a prediction failure in a log DB as Real Time is displayed on a screen.
12 is a diagram illustrating a log zone.
13 is a view showing a trouble pattern zone.
14 is a diagram illustrating an environment zone.
15 is a diagram illustrating a trouble counting zone.
16 shows a full text display.
17 is a diagram illustrating a data error zone.
18 is a diagram illustrating a process of processing a Trouble Period Zone.
19 is a diagram illustrating a business process configuration diagram.
20 is a view showing an example of the official data list.
21 is a diagram illustrating a new association process.
22 is a diagram illustrating a description of a linked information registration function.
23 is a diagram showing a verification criteria process.
24 is a diagram illustrating a verification item registration state.
25 is a diagram illustrating validity setting.
26 is a view showing verification item / validation criteria setting.
27 is a view illustrating a pattern to be verified.
28 is a diagram showing a common verification pattern of association.
29 is a diagram illustrating an example of verification items and verification criteria Rule Base.
30 is a diagram showing a maximum / minimum value setting.
31 is a diagram showing a sample verification distribution setting.
32 is a diagram showing sample verification graph settings.
33 is a diagram illustrating sample verification table setting.
34 is a view showing an example of public data sample verification in the sample verification query.
35 is a view showing an embodiment of a data verification batch process.
36 is a view showing the business reflection verification criteria of the National Tax Service business registration certificate as an example.
37 shows suspicious data types.
38 is a view showing data in detail the complex pattern of the suspect data types.
39 is a diagram illustrating an abnormal trial data processing process.
40 is a screen illustrating the status of public data transmission / reception as a function of public data transmission / reception status.
Fig. 41 is a description of the official data abnormality data inquiry function. Inquiry and processing of the data detected by the abnormality quality criterion is shown.
42 is a view showing a functional verification dashboard functional description.
Fig. 43 is a view showing a description of the function of official data processing;
44 is a view showing the functional data daily reporting description.
45 is a diagram illustrating linkage meta information.
46 is a view showing a public data link information registration screen.
47 is a view showing a public data linkage information modification screen.
48 is a view showing a public information link information correction history view screen.
As shown in FIG. 48, when the history button is clicked, the modified public data meta information is inquired.
49 is a view showing a detail screen when the other button is clicked.
50 is a view showing a screen for modifying public data linkage information verification criteria.
As shown in FIG. 50, when the registration button is clicked, the verification standard registration management screen pop-up of the link is moved.
FIG. 51 is a view showing a linked inquiry (verification item / verification standard) of data verification registration data.
52 is a view illustrating verification criteria registration.
53 is a view showing a reception table setting.
54 is a view illustrating validity and verification criteria setting.
55 is a view showing a maximum value / minimum value setting.
56 is a diagram showing a sample verification setup.
57 is a diagram illustrating manual division.
58 is a diagram illustrating automatic division.
Fig. 59 is a view showing a user-defined graph for the public received data.
60 shows table settings.
Fig. 61 is a view showing the details of the abnormal trial data as verification items.
Fig. 62 is a view showing (screen) association type protocol registration (message tracker).

In order to fully understand the present invention, preferred embodiments of the present invention will be described with reference to the accompanying drawings. Embodiment of the present invention may be modified in various forms, the scope of the invention should not be construed as limited to the embodiments described in detail below. This embodiment is provided to more completely explain the present invention to those skilled in the art. Therefore, the shape of the elements in the drawings and the like may be exaggerated to emphasize a more clear description. It should be noted that the same members in each drawing are sometimes shown with the same reference numerals. In addition, detailed descriptions of well-known functions and configurations that are determined to unnecessarily obscure the subject matter of the present invention are omitted.

Each term used below may be understood as the following meanings, unless specially defined otherwise.

"Business" means to generate, manage and provide the required information by processing various data in the business server. For example, an integrated welfare management system that includes the happiness and social security information system (government) that is currently under construction. For example, the income, property, or age of the applicant may be computerized to be paid or paid to the applicant. It may be to generate, manage, and provide information on the welfare benefit or service, and statistical information thereon.

"Business server" means a server that processes the business.

"Business information" means information generated as a result of the business process or result. For example, information on welfare benefits or services to be paid or paid to the applicant, and statistical information thereon.

"Institution" means a target organization (eg Health Insurance Corporation) to which a business server intends to make a connection in order to use or provide data.

"Institutional server" means a target server (eg, health insurance information server) to which the work server is to be linked.

"Source information" means information that an institution server holds as a process or result of a process of the institution. For example, the information may be information on income, property or age of the applicant, and statistical information about the applicant.

"Message" means a unit of information for requesting and receiving data between servers.

"Object message" means a message generated in class format by a predefined rule.

"Provide" means to give information to the institution server to which the link.

"Use" means receiving information from the institution server to which the link.

"Real-time" means that the link is made by the screen event generated from the user terminal, and is mainly used in the screen lookup, etc. in the form of the link receiving an immediate result.

"Batch" is a form of linkage that periodically transmits or receives information from a server, and is used mainly for data exchange of large amounts of data.

"Business DB" is a DB built on a business server, and means a DB that stores and manages business information.

"Service DB" is a DB built in a linked server, and means a DB constructed with a kind of proxy concept of data frequently used for a providing service or a summary data among data built in a work DB. It can be understood as a kind of data warehouse.

"Linked log DB" is a DB built in the associated server, and means a DB that stores and manages the history data on the request / response and processing status of the service or the provided service and the history data on the occurrence of an error.

"Linked DB" is a DB built in a linked server, and according to a predefined linking rule, for linkage ID for identifying each linkage service, linkage type information, service type information, pattern information and linkage solution information of the linkage service. It means DB which defined etc. as meta information.

The "monitoring log DB" is a DB built in the monitoring server, and means a DB that stores and manages various failure-related history data that are determined to be failures or prediction failures by various analysis modules of the monitoring server.

In addition, the terms or details of the related services, which are not separately described, may be referred to through the contents of Korean Patent Nos. 1219364 and 1100241 registered and registered by the present inventors.

The present invention provides a tool for formalizing and determining formal errors and actual content error verification patterns of public data received from related agencies, thereby reducing the verification time of public data and increasing the efficiency of prior detection of errors. In order to provide a data verification tool to formalize and concretely implement the pattern of error re-request data, increase the suitability and accuracy of the data, and improve the quality and reliability of public services. In order to minimize the failure by preliminary measures through the prediction of the failure and to clearly classify and monitor the failure (judgment, speculation) factors, physical storage that classifies and stores them as the relevant server CPU, memory, storage, and process operation proper values and reference values and statistics. Numerical module; Link environment module for validating the S / W-related server certificate and license of the link server; A failure pattern type module for storing network connection failure information of the connection server, processing error and delay information of the database, and connection failure information of the connection S / W; A failure statistics module for statisticing the number of temporary service failures by the corresponding system load of the related server; An error module for managing an error about a data consistency violation of the linked server; Non-disability cycle module for managing unprocessed information within a specific period of the linked server; including the formal error of the official data and the error of the actual content to increase the error detection efficiency of the data to provide a reliable verification tool by providing Verifying data linkage with public institutions that shorten the process of storing and databaseting only the data whose data is verified, while improving the accuracy of the data, the quality of services provided to the public, and the reliability of the public services. Provide a system.

In addition, the present invention, by formalizing the format error pattern of a variety of public data provided from a number of related agencies public data primary prior error detection tool detectable before error verification of the actual content; A secondary prior error detection tool for verifying the content of selected public data in a suitable format; A data re-request tool for re-requesting data of public data identified as an error from the first and second dictionary error detection tools; A server storage tool for data determined to be suitable through the first and second advance error detection tools; The present invention provides a computer-readable recording medium that records a program of a public institution's income property linked data verification system to reduce a certain amount of data verification time and reduce work overload.

In addition, the present invention, the linked server is one of the new administration system of the government server, the commissioned management system, the government linked server, the commissioned connection server, the target ministries server linked to the social security information system, the central administrative agency of the country Connected with more servers,

A first judgment process for determining whether there is an error in the format of the data received from the relevant government agencies;

Public data determined as an error after the first decision process is returned to the corresponding institution to request correction of information;

A second judging process of judging an error of substantial contents of public data having appropriate requirements through the first judging process;

Public data determined as an error of the contents of the public data through the second judging process;

It is to make it possible to provide public service by using database tool of public data modified through

Hereinafter, an embodiment according to an embodiment of the present invention will be described with reference to the drawings.

1 is a view showing a configuration diagram.

As shown in FIG. 1, the present invention provides a connection server CPU, memory, storage, and process operation proper values in order to minimize the failure by preliminary measures through the prediction of the failure, and to clearly classify and monitor the failure (decision, guess) factors. A physical numerical value (Hardware Zone) module for classifying and storing the data as reference values and statistics; An Environment Zone module that checks the S / W related server certificate and license validity of the linked server; Trouble Pattern Zone for storing network connection failure information (No Connection, Long Data Error) information of the linked server, processing error and delay information of database, and service down and error information of linked S / W module; A trouble counting zone module for statisticing the number of temporary service failures by the corresponding system load of the related server; An error (Data Error Zone) module for managing an error regarding a data integrity violation of the linked server; And a trouble period zone module for managing unprocessed information within a specific period of the linked server.

The linked server is a government server 100, a consignment management system 200, a government linked server 300, a consignment linked server 400, a target department server linked to the social security information system (government) ( 500) is connected with one or more servers of the new all-administration system 600 of the central administrative agency (Ministry of Administration and Security) of the country.

2 is a view showing a monitoring linkage range (integration control + linkage + security).

As shown in FIG. 2, the linkage is a type of hub that serves as a data or file transmission *? * Receive and tunneling function between an external agency and a work server.

At this time, the data or file must be encrypted at the time of transmission, decrypted at the time of reception, and data conversion is also provided at the time of data or file reception.

, y-

)는 Monitoring Chart Zone의 박스 기준 좌표이다.As shown in FIG. 3, the coordinates (x, y) and coordinates (x +) in the screen coordinates.

, y-

) Is the box reference coordinate of the Monitoring Chart Zone.

는 Monitoring Chart Zone에서 일시간을 24hour로 등분할 길이이다.

Is the length of time divided into 24hours in the Monitoring Chart Zone.

는 Monitoring Chart Zone에서 예측시간을 60hour로 등분할 길이이다.

Is the length to divide the forecast time into 60 hours in the Monitoring Chart Zone.

y 'is the starting y-coordinate of the critical values (H / W and S / W Critical Value).

[Equation 1] Monitoring Chart Zone coordinate drawing

Specific x coordinate point =

Specific y coordinate point =

Specific threshold y coordinate point =

= 예측시간,

= 기준치(%)※

= Forecast time,

= Baseline (%)

Table 1 shows the types of suspected errors, and FIG. 3 is a diagram illustrating a screen configuration.

4 shows a process summary.

As shown in Fig. 4, 1) Data Input / Output or Status is monitored. ② The forecasting system determines the linkage status and alerts you of any warnings or failures. ③ Diagnose and take measures for the failure, but the method is manual or manual failure through the manual for each case. ④ Provides non-disruptive linked service by checking and alerting the warning contents. .

FIG. 5 is a diagram illustrating a predictive failure process (state of H / W or linked S / W of a server and information physically transmitted and received).

6 is a view illustrating a detailed hardware area (Zone) function.

As shown in FIG. 6, CPU, Memory, Storage, and Process are managed, and are divided into Inner (internal linkage) and Outer (external mandatory linkage and external semi-mandatory linkage).

Internal linkage is a linked server managed by the Ministry of Welfare (Development Institute) and checks the status every 5 minutes.

The external linkage is a linked server managed by an external organization. The external mandatory linkage checks the status in 1 hour units and the external semi-mandatory linkage in 12 hours.

If the utilization rate of each status is more than 75%, a red box is displayed, and if it is more than 90%, it is indicated as a predictive failure in the Monitoring Chart Zone.

7 is a diagram showing a processing step (Hardware Zone processing process).

As shown in FIG. 7, ① the internal connection server and the external connection server application operate by a predetermined time unit to generate a file by collecting CPU, memory, storage, and process information. ② Sends the file to the monitoring server by ESB (Enterprise Service Bus) or other enterprise application integration (EAI). ③ The monitoring server application reads the file and saves the status status in the linked DB. ④ Display the status in the Hardware Zone by pooling the associated DB on a regular basis.

As shown in FIG. 8 and FIG. 9, an analysis module Div IDNumber exists for each zone, and a screen is displayed as a decision module Div ID Number.

8 is a diagram illustrating a data processing relationship diagram.

9 is a diagram illustrating a system linkage (process) relationship diagram.

As shown in FIG. 9, when the CPU, memory, and process critical values reach 90%, a screen is displayed.

And it displays in (sysdate, H / W Critical Value), minute / hour / day.

In addition, it displays the time zone where the storage failure threshold reaches 90%.

Also, the expiration date of the server certificate is displayed on the screen within 3 days.

      [Equation 2]

 ⇒ (sysdate (h), EER (T))

As shown in FIG. 10, the failure pattern element for the network includes a real-time firewall check (AMPN01) result and a java.net. * Exception log check (AMPN02) result of the associated log DB data, and a packet rate of the associated log DB data. At least one of the results of the check (AMPN03), the failure pattern element for the associated log DB element, java.sql. Exception log check (AMPD01) results are included, and the failure pattern element for the associated software includes an ESB (Enterprise Service Bus) health check (AMPS01) result.

[Equation 3]

The present invention determines the presence or absence of a failure by executing a predetermined predetermined rule in order to prevent the failure in advance by the self-diagnosis function (check) of the computer, and separates the failure unit and continues operation when necessary. Predetermined rules can determine the presence or absence of a failure according to the application of a predetermined data match.

10 is a diagram showing processing logic (error and prediction indication).

When the number of faults in Equation 3 is greater than 80% within the Check Start Time and Check End Time ranges in the linked DB, if there is no result corresponding to the fault pattern (type), it is indicated as a temporary fault due to service overload. When there is a result corresponding to the pattern (type), the prediction result of the failure pattern (type) is displayed in priority, so the prediction result by the number of failures (statistics) is excluded.

[Equation 4]

 (sysdate (h), ER (%))

Errors should not be displayed in the Monitoring Chart Zone.

If non-disability (cycle) is more than 1 day in Log DB, it is displayed as disability.

11 is a Core View: Monitoring Chart Zone (monitoring prediction chart)

12 is a diagram illustrating a log zone.

As shown in FIG. 11, the log DB is displayed on the screen by searching for failures and predictive failures in real time.

13 is a view showing a trouble pattern zone.

As shown in FIG. 13, the linkage DB and the linkage S / W are analyzed to analyze network, DB, and S / W failure information.

For example: ① Search the linked DB on an hourly basis and analyze the data within 1 hour based on the current time. ② Network registers all java.net. * Types, DB registers all java.sql. * Types, and S / W registers error information through ESB health check in Log DB. ③ Display Log DB and display Trouble Pattern Zone Error.

14 is a diagram illustrating an environment zone.

As shown in FIG. 14, the effective organization of the server certificate for data encryption *? * Decryption is managed when the ESB vs. ESB and the institution are linked.

For example ① Application is run on a daily basis to manage expiration date and remaining period of certificate. ② If remaining period is less than 3 days, it will be displayed in Monitoring Chart Zone.

15 is a diagram illustrating a trouble counting zone.

As shown in FIG. 15, the failure occurring when the connection occurs in real time is monitored, and color is appropriately displayed according to the failure occurrence rate, thereby improving awareness.

[Equation 5]

For example: ① Group data is generated by classifying the total number of inputs and the total number of errors up to one hour before the current time. ② Create Data data based on the linkage ID in the Group screen. ③ Create Result data based on transaction ID in Data screen. ④ It is possible to check the error contents in the Result screen.

16 shows a full text display.

As shown in Fig. 16, ① a pop-up window appears and a request message is displayed on the left screen, and a blank message is displayed on the right screen. ② Click 'Run' button to send data from the monitoring server to the relevant server, and the server encrypts the data. ③ Send the data to the receiving authority through the linked ESB and receive the result and display the full text on the right screen. ④ In case of temporary failure, it is displayed normally, but in case of failure, the error content is displayed on the screen. Click the Reading button to see a simple process.

17 is a diagram illustrating a data error zone.

As shown in FIG. 17, an error generated when reading or writing batch (file) data is clicked. When the corresponding row (cell) is clicked, an error detail log is displayed.

For example, if an error detail log is analyzed and processed, it is deleted from the Data Error Zone, and the person in charge of the action takes action.

18 is a diagram illustrating a process of processing a Trouble Period Zone.

As shown in FIG. 18, the screen manages batch (file) data, and checks whether data are periodically generated and transmitted *? * On the corresponding date.

For example, ① Application is operated every 1 hour and generates monthly, weekly and yearly mapping data for batch processing. ② If Data does not exist in Log DB, it is processed in the above process unit according to the data attribute (send or receive). ③ If unprocessed date is more than 1 day, it is displayed in Monitoring Chart Zone.

19 is a diagram illustrating a business process configuration diagram.

For example, as shown in FIG. 19, 47 types of public data are currently received from 17 related agencies. The meta information on the linkage of the official data is registered and the changes are modified and managed.

Establish standards for suspected abnormalities for each link and data distribution information.

It executes a batch program for loading the above-mentioned core data verification work and the statistical information on the basis of the request data loading and the meta information for each receiving linkage.

The linkage detected by the abnormal heart data is monitored and processed by abnormal heart types.

The public data link information, transmission and reception status, public data processing statistics information is inquired.

Here, the meta information is information that collectively refers to a transmission / reception association ID and a connection name associated with public data linkage.

20 is a view showing an example of the official data list.

21 is a diagram illustrating a new association process.

As shown in FIG. 21, new association information is received from an institution name, a department name, and an associate name.

Then, verification meta information such as link name, organization name, department name, transmission / reception link ID, and transmission / reception document code is registered.

Through the analysis of linked data, the verification criteria for the verification items and the verification items are derived.

22 is a diagram illustrating a description of a linked information registration function.

As shown in FIG. 22, the public data meta information is registered and corrected for schedules and changes.

After inputting the information to be searched in the related institution or condition search item, click the [Search] button to search the public data meta information.

Enter one of link name, organization name, department name, transmission / reception link ID, transmission / reception document code as condition search inquiry condition and click button.

If you click on the sorting condition, you can search the linked information sorted by department / organization / linked name.

First, if you need to register the information for linking new public data, click the [Register] button to register. New connection information is sequentially entered.

If you click the auto-complete button after inputting the sending link ID and receiving link ID, information about the organization name, link name, link method, send document code, and receive document code is automatically entered.

In addition, if multiple linkages are used as one linkage ID (ex private school retirement pension, private school employee contribution), the number can be selected and stored.

23 is a diagram showing a verification criteria process.

As shown in FIG. 23, it is possible to inquire linked meta information for registering verification criteria.

After selecting and inquiring public data, it is possible to register public data verification items, such as selecting detailed output of abnormal data and selecting validity check.

Select whether to use the effective rate, input the effective rate, and enter the validity criteria.

In addition, verification criteria such as verification items and verification conditions can be set.

It is possible to select the maximum value / minimum value amount column and search period, and to select whether to use the minimum / maximum value inquired.

Distribution information can be set, manually divided or automatically divided and saved for the amount column saved in the verification criteria, graph items can be added, and table items can be added.

24 is a diagram illustrating registration of verification items.

As shown in FIG. 24, an effective rate is set for a column to be used for validity checking after storing table schema information for use in verification criteria.

25 is a diagram illustrating validity setting.

As shown in FIG. 25, the effective rate is set to a default 5% and can be modified by changing the number when a change occurs.

In the effective rate setting, only two digits can be written. An effective criterion case is a criterion that enables checking the validity rate only for data more than the number of data set for the daily transmission / reception data.

26 is a view showing verification item / verification criteria setting.

As illustrated in FIG. 26, verification conditions may be set for each verification type for the items stored in the verification schema in the verification item addition and verification item criteria storage.

Registration of the verification condition is possible only for the user-defined method.

The verification types include a minimum value, a maximum value, a zero check, and a user definition (WHERE condition, FULL SQL).

The minimum, maximum and zero check types can be registered only for the Amount column.

27 is a verification target pattern, and FIG. 28 is a common verification pattern of association.

29 is a diagram illustrating an example of verification items and verification criteria Rule Base.

30 is a diagram showing a maximum / minimum value setting.

As shown in FIG. 30, the use of the maximum value / minimum value is set for the amount data entered in the inquiry period for each link.

In the case of a wrong amount of money during the period, the use of the maximum value / minimum value is set as unused and excluded.

31 is a diagram showing a sample verification distribution setting.

As illustrated in FIG. 31, the distribution information for each section may be searched for data to be used as distribution information.

In the case of manual division, the user enters the minimum and maximum amounts up to 10 divisions.

In the case of automatic partitioning, after inputting the minimum value and the maximum value, an equal fraction can be selected and saved. Saved distribution information is selected by using ON / OFF button.

32 is a diagram showing sample verification graph settings.

As shown in FIG. 32, a user-defined graph is set for the public received data.

The graph type is set by selecting a desired graph type from two types of line and bar graph.

Then select the graph title and type to use. The screen UI sort order specifies the order to be displayed. Click the Add Graph Item button to enter a query in the SQL item.

33 is a diagram illustrating sample verification table setting.

As shown in FIG. 33, a user-defined table is set for the publicly received data.

The graph type is set by selecting the desired graph type among two types of line and bar graph. Also enter a table title and description to use.

Click the Add Table Item button to enter column names to be displayed in the grid and create an SQL query to query.

34 is a view showing an example of public data sample verification in the sample verification query.

As shown in Fig. 34, the inquiry period selection, the public data link selection, the request type selection (existing type, government, child allowance, etc.) and then the inquiry are clicked.

The public data bar graph or line graph is displayed according to the specimen verification graph setting.

35 is an embodiment of a data verification batch process. As shown in FIG. 35, it is possible to query by receiving and loading received data for each reception connection and unrequested response.

It is loaded as a temporary table and executed only when it is an ALL type for each linkage.

The abnormality data on the received data loaded as the verification item meta information for each received connection is checked, and the number and detailed information are registered in the corresponding table.

Load monitoring effective rate information for each request type. The validity information corresponding to the request type for the government, child allowance and other request types is loaded into the data verification table.

The request date value of the linked reception temporary table is NULL, and the number of unsolicited requests is registered in the data verification table based on the received transaction ID.

Generate statistical information of the request type (ALL) as statistical information on the registered request type government, child allowance, and other request types, and load the request type ALL monitoring effective rate information in the data verification table.

As a criterion for verifying the above data, 0% of efficiency, (++ 5%) of code for checking the efficiency, code of no data received, code of no request data, code of integrity verification, code of duplicate occurrence, and validity Fragmentary verification methods such as validity 0% verification code value and validity check target (-+ 5%) code value are applied.

Also, it checks below the minimum value (existing Min value range over code value), exceeds the maximum value (existing Max value range over code value) check, 0 won check (existing 0 won check target (some) code value, 0 won check target (all)) Code value) and user-defined verification conditions (WHERE condition, FULL SQL) are registered.

Register the number of statistics for each section of the received data loaded as the statistical section meta information on the data set in the amount column by the receiving connection.

The validity rate here is the ratio of incoming requests to incoming requests.

For example, if there are 100,000 requests for old data and 90,000 received, the effective rate is 90,000 / 100,000 (%), or 90%.

In addition, it is possible to grasp the distribution and characteristics of the data of each item of public data by setting the maximum value and the minimum value for a specific item for each public data item.

If the maximum value of the National Pension Service of the National Pension Service on January 2 is 100 million, it can be set as an ideal trial data when the salary item exceeds 100 million.

FIG. 36 is a diagram showing a business reflection verification standard of the IRS business registration certificate as an example.

FIG. 37 is a type of suspicious data, FIG. 38 is a detailed representation of a complex pattern among types of suspicious data, and FIG. 39 is a diagram illustrating a process of processing abnormal data.

As shown in FIG. 39, abnormality data such as seriousness, warning, interest, attention, and confirmation are inquired based on the request date of the public data.

Any abnormalities that can be processed by themselves are processed by the person in charge after confirmation.

Due to the nature of the data, abnormal data that need to be confirmed by the related organizations should be processed normally after the verification.

After file correction, reprocess the file and complete verification. The unreceived file among the files is processed after being received by the relevant authority.

Finally, it is confirmed by the operation manager and finally by the operation manager.

40 is a screen illustrating the status of public data transmission and reception as a function description of the public data transmission and reception status.

As shown in FIG. 40, after inputting a period to be inquired first, click the [Query] button to inquire a list of transmission / reception statuses by request date of public data.

The mandatory fields here are 'start month of decision month', 'end month of decision month', and initial values: M-2 month to M month.

In the initial inquiry screen, only the error list (type verification error, preload error, unsent, unreceived, file send error, file scheduled to be received) is inquired.

If you click the number of each error, you can search the list only for the error. If you click the whole number, you can see the entire list of official data for the request date.

Fig. 41 is a description of the official data abnormality data inquiry function. Inquiry and processing of the data detected by the abnormality quality criterion is shown.

As shown in FIG. 41, after inputting the request date of the official data, the [inquiry] button is clicked to search the list of abnormal data of the request date. The inquiry list displays the abnormal data in order of seriousness, warning, attention, attention, and confirmation.

The above inquiry conditions are classified into request date, official data name, organization, contact status, and request type selection. Each search condition can be selected in duplicate.

The inquired data can be classified by color (severity, warning, attention, attention, confirmation) for each step.

The progress status for each processing person in charge is displayed on the screen.

42 is a view showing a functional verification dashboard functional description.

As shown in FIG. 42, the data verification status such as the current status, public data transmission / reception status, public data verification status, income property transmission / reception status, internal connection monitoring status, new connection status, and procedure work status information can be inquired as shown in FIG. 42. .

Fig. 43 is a view showing a description of the function of official data processing;

As shown in Fig. 43, after inputting the period, the inquiry button is clicked to inquire. By selecting specific public data name as search condition, statistics are extracted.

44 is a view showing the functional data daily reporting description.

As shown in FIG. 44, after selecting the request date of the public data to be inquired, the [inquiry] button can be clicked to search the public data daily report. When searching, specify the request type (existing type, government, children's allowance, etc.).

45 is a diagram illustrating linkage meta information.

As shown in FIG. 45, after inputting information to be queried in a related agency or condition search item in the method for searching public data meta information, the search button is clicked to search public data meta information.

At this time, enter one of link name, organization name, department name, sending / receiving ID, sending / receiving document code as condition search inquiry condition and click button.

In addition, if you click the sorting condition, you can search the linked information sorted by department / organization / linked name.

If it is necessary to register the information for new linkage with new public data, ② click the link registration button to register it.

46 is a view showing a public data link information registration screen.

As illustrated in FIG. 46, new connection information is sequentially entered in the public data link information registration screen.

After entering the transmission linkage ID and the reception linkage ID and click the auto-complete button, information on the organization name, linkage name, linkage method, transmission document code, and reception document code is automatically entered.

In addition, if multiple linkages are used as one linkage ID (ex.

Clicking the Excel button downloads the retrieved public data meta information into Excel.

47 is a view showing a public data linkage information modification screen.

As shown in FIG. 47, when modifications are made to the stored public data information, the modified information is clicked to store the changed information.

Possible modifications include the base year, pre-emptive reference, transmission time, reception time, availability, contact person in charge, and connection details.

The autocomplete function through the autocomplete button is available only when registering the link.

48 is a view showing a public information link information correction history view screen.

As shown in FIG. 48, when the history button is clicked, the modified public data meta information is inquired.

49 is a view showing a detail screen when the other button is clicked.

As shown in FIG. 49, when the details button is clicked, the details screen of the official data meta is displayed.

50 is a view showing a screen for modifying public data linkage information verification criteria.

As shown in FIG. 50, when the registration button is clicked, the verification standard registration management screen pop-up of the link is moved.

FIG. 51 is a view showing a linked inquiry (verification item / verification standard) of data verification registration data.

52 is a view illustrating verification criteria registration.

As shown in FIGS. 51 and 52, the order of data registration is to first check the public data to register the verification criteria by registering the verification criteria, and after selecting the public data table schema, selecting the type, detailed output of abnormal data, and selecting whether to check validity. Save, select whether to use the effective rate, input the effective rate, enter the valid criteria, save and save after inputting the verification condition. After selecting the maximum / minimum value column and querying the period, select whether to use the minimum / maximum value inquired.

As the sample verification registration, the distribution information is set for the amount column stored in the inspection criteria, the manual division or the automatic division is selected and stored, the graph item is added, and the table item is added.

On the other hand, in order to search the linkage, select the department, agency, and official data name and inquire. Only one association can be selected.

Receive table setting, verification criteria registration, validity rate, maximum value / minimum value are set for the selected public data.

By setting the reception table, the main loading or preloading table schema information of the selected public data is retrieved and the columns to be used for the verification criteria are stored.

Select a type (request month, link request number, request sequence, transaction ID, data, amount) for the preload / main load table columns and select a column to be used as the validity check.

At this time, only one request year, link request number, request sequence, and transaction ID can be selected. Data items can be multi-selected.

Also, when selecting whether to check validity, validity check can be selected for only one column.

53 is a view showing a reception table setting.

54 is a view illustrating validity and verification criteria setting.

As shown in FIG. 54, an effective rate is set for a column to be used for validity checking after storing table schema information to be used for verification criteria according to an embodiment of the present invention.

The effective rate is set to the default 5% and can be modified by changing the number if a change occurs.

For the effective rate setting, only two digits can be entered. An effective criterion case is a criterion that enables checking the validity rate only for data more than the number of data set for the daily transmission / reception data.

Verification conditions can be set for each type of verification for the items stored in the verification schema. Registration of verification conditions is possible only for user defined methods.

As the verification type, minimum value, maximum value, zero won check, user defined (WHERE condition, FULL SQL) minimum value, maximum value, zero won check type can be registered only for the amount column.

55 is a view showing a maximum value / minimum value setting.

As shown in FIG. 55, the use of the maximum value / minimum value is set for the amount data entered in the inquiry period for each link.

In the case of a wrong amount of money during the period, the use of the maximum value / minimum value can be excluded to exclude the use.

FIG. 56 is a diagram showing data distribution information, graphs, and table settings for each request type (existing type, government, child allowance, etc.).

As shown in FIG. 56, data distribution information, graphs, and tables may be set for each request type (existing type, government, child allowance, etc.).

FIG. 57 is a diagram for setting distribution information inquiry by section for data to be used as distribution information.

As illustrated in FIG. 57, the distribution information for each section may be searched for data to be used as distribution information.

In the case of manual division, the user can directly input the minimum / maximum amount up to 10 divisions.

In the case of automatic partitioning, after inputting the minimum value and the maximum value, an equal fraction can be selected and saved. Saved distribution information can be selected by using ON / OFF button.

For example, save after inputting minimum / maximum amount according to equal fraction.

58 is a diagram illustrating inputting a maximum amount of salt solution, and storing the same after determining the number of portions using a select box.

As shown in FIG. 58, the maximum amount of the minimum amount is input, and the number of equal portions is determined and stored using the select box.

Fig. 59 is a diagram for setting a user-defined graph for the public received data.

As shown in FIG. 59, a user-defined graph can be set for the official received data.

The graph type can be set by selecting the desired graph type among two types (line and bar graph).

For example, in order to select the graph title and type to use, enter the order to display the screen UI sort order, enter 1 for the first registration, and enter the query in the SQL item by clicking the Add graph item button. .

Here, the graph can be flexibly represented by the query entered by the user.

60 is a diagram showing a table setting for publicly received data.

As shown in FIG. 60, a user-defined table may be set for the official received data.

The graph type is set by selecting the type of graph (line and bar graph can be used together) among two types of line and bar graph.

For example, ① Click the Add Table button, ② Enter the title and description of the table to be used. UI Sort Order Enter the order to display, and there is an input check function for the first registration.

③ Click the Add Table Item button to enter the column name to be displayed in the grid, and there is a check function to create an SQL query to search.

Fig. 61 shows detailed data of abnormal lead data as verification items.

As shown in FIG. 61, there is a storage check function after writing an abnormal trial person in charge processing state step and details of each processing step.

There is a check function to check the details of abnormal data corresponding to the verification conditions.

The present invention has a basic verification (Basic Verification) example, there is a social security number, account number, phone number, mobile phone number check function.

Also, as an example of limited verification, there are minimum, maximum, and average value check functions.

In addition, examples of Construction Verification include Separator, Overall Length, Mandatory, Header, and Tailer Check.

In addition, as an example of the outer logic verification (Outer Logic Verification), there is a check function, except for the standard, including the standard.

Examples of volume verification include low-size and average-size full-size checks.

Statistical Verification is an example of checking the average value of a specific item.

An example of a duplicated verification is a check function.

Fig. 62 is a view showing a screen for defining link search (message tracker).

63 is a diagram illustrating a format protocol setting screen and the like after loading of the link definition document.

64 is a diagram showing a format agreement result screen and a data consistency verification history.

65 is a diagram showing a data consistency error result screen.

Embodiments of the invention include a computer readable medium containing program instructions for performing various computer-implemented operations. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical recording media such as CD-ROMs, DVDs, magnetic-optical media such as floppy disks, and ROM, RAM, flash memory, and the like. Hardware devices specifically configured to store and execute the same program instructions are included. The medium may be a transmission medium such as an optical or metal wire, a waveguide, or the like including a carrier wave for transmitting a signal specifying a program command, a data structure, or the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

100: pan government
200: consignment management system
300: linked government server
400: consignment connection server
500: target department server
600: new all administration system

Claims (12)

In the verification system for linking income property of public institutions,
A physical numerical module that classifies and stores the associated server CPU, memory, storage, and process operation proper values and reference values and statistics;
Link environment module for validating the S / W-related server certificate and license of the link server;
A failure pattern type module for storing network connection failure information of the connection server, processing error and delay information of the database, and connection failure information of the connection S / W;
A failure statistics module for statisticing the number of temporary service failures by the corresponding system load of the related server;
An error module for managing an error about a data consistency violation of the linked server;
A non-failure cycle module for managing unprocessed information within a specific period of the linked server;
A public data primary pre-error detection tool detectable before formal error verification by formalizing the format error pattern of various public data provided by a number of related agencies;
A secondary prior error detection tool for verifying contents of selected public data having a certain format;
A data re-request tool for re-requesting data of public data identified as an error from the first and second dictionary error detection tools;
Including server storage tool of the data determined to be suitable through the first and second error detection tools; including
The linked server selects whether to use the effective rate, inputs an effective rate, inputs an effective criterion, saves it, sets a verification item and a verification criterion
Select max / min value column and search period, select whether to use the min / max value,
Save and set distribution information, manual division or automatic division for the amount column saved in the verification criteria,
The effective rate is set to the basic 5%, the effective criteria case can be checked the effective rate only for the data more than the number set for the daily transmission and reception data,
In the verification item addition and storage of the verification item criteria, verification conditions are set for each item stored in the verification schema.The verification type includes a minimum value, a maximum value, a zero check, and a user definition.
The minimum value, maximum value, and zero won check type can be registered only for the amount column.
As a criterion for verifying the above data, the efficiency 0%, the code value for checking the efficiency, the value of the data not received, the code value without the requested data, the code value of the consistency verification, the code value of the occurrence of duplicate cases, the validity 0% verification code value, Effective rate check target code value is applied.
The linked server is connected to at least one of a government server, a consignment operation system, a government linked server, a consignment linked server, a target department server linked to a social security information system, and a new all-administration system among national administrative agencies. ,
A first judgment process for determining whether there is an error in the format of the data received from the relevant government agencies;
Public data determined as an error after the first decision process is returned to the corresponding institution to request correction of information;
A second judging process of judging an error of a substantial content of public data having a predetermined requirement through the first judging process;
Public data determined as an error of the contents of the public data through the second judging process;
It is possible to provide public service with the database utilization tool of public data modified through
By providing a formal verification tool for the verification of the secondary content of public data that has undergone a primary format error pattern, only the validated data is stored on the server and made into a database to shorten a series of processes, and the input / output or status of the data is reduced. Monitor and monitor the monitoring server and determine the linkage status of the prediction server to diagnose and take measures.However, the measures or manual faults through the manual for each case are automatically taken.
The screen is displayed when the number of failures within the Check Start Time and Check End Time range is more than 80% in the linked DB related to the storage of the linked server, the linked DB is searched in units of 1 hour, and the data is analyzed within 1 hour based on the current time. And registering the error information in the log DB, and querying the log DB to display a trouble pattern zone error.
delete delete delete delete delete The method of claim 1,
The group data is generated by classifying the total number of inputs and the total number of errors up to 1 hour before the current time through the failure pattern type module in the linked DB, and the data data is generated based on the linked ID on the screen of the group data. And generating a result data based on the transaction ID and checking the error content in the result data.
The method of claim 1,
The monitoring server transmits the data to the associated server, and the linked server encrypts the data. The data is displayed normally in case of temporary failure through the failure statistics module, but in case of failure, the error contents are displayed on the screen. Public institution income data linkage verification system.
delete The method of claim 1,
The linked DB generates monthly, weekly, and yearly mapping data for batch processing, and if the data does not exist in the log DB, it is processed in process units according to the attributes of the data. Public institution income data verification system characterized in that displayed in the Monitoring Chart Zone.
The method of claim 1,
When the number of failures is over 80%, the screen is displayed, and when there is no result corresponding to the failure pattern, it is indicated as a temporary failure due to service overload, and when there is a result corresponding to the failure pattern, the prediction result of the failure pattern is preferentially displayed. Verification system linked to income property of public institutions, characterized in that.
The method of claim 1,
The self-diagnostic function of the linked server determines whether there is a disorder by executing a predetermined rule in order to prevent a failure in advance, and separates the unit of failure and continues to operate. Verification system.

Images