KR20030035995A - Management system of database for seal impression comparison and management service method thereof - Google Patents

Abstract

PURPOSE: To suppress a cost at the time of introducing a seal registration management system for a user and to provide a service simplifying even maintenance after introduction by utilizing a common management center by a seal registration agency. CONSTITUTION: A seal registration management center side system 100 which prepares, manages and provides a seal image DB 103, a seal information DB 105 and a user customization DB 107 and user side systems 200 and 300 which utilize the seal image DB 103 are connected by a network 10. The seal registration management center side system 100 is provided with a function 102 of storing read images, a function 104 of registering attributes of an owner of a seal and a utilization organ or the like, a function 101 of verifying whether or not read seal image data and seal information match with already registered seal image data and seal information, a function 106 of transferring customized seal information and a collated result to the user side system and a function 108 of referring to charging information of the user side system.

Description

Seal management database management system and management service method {MANAGEMENT SYSTEM OF DATABASE FOR SEAL IMPRESSION COMPARISON AND MANAGEMENT SERVICE METHOD THEREOF}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an image processing technique for identifying, recognizing, and matching a seal portion of a document read by an image scanner, and in particular, to create a seal contrast DB (database) for identifying, recognizing, and matching a seal. The present invention relates to a seal collation database management system and a management service method which manages and acts as a seal collation work.

Background Art Conventionally, for example, registration and management of customer seals in financial institutions are performed by financial institutions or by several branches. In addition, registration and management of a seal certificate issued by a municipality are also carried out for each municipality. Such a seal registration management system is used only for each institution and unit, and a DB (database) is often built separately. Therefore, financial institutions, local governments, etc. not only construct facilities using enormous costs, but also spend a considerable number of people and time for their management.

In this specification, financial institutions, self-governing bodies, insurance companies, etc. are called "consumers," and customers using these financial institutions, self-governing bodies, insurance companies, etc. are called "customers."

On the other hand, from a customer's point of view, a person usually uses a plurality of financial institutions, and in many cases, a seal may be lost due to various reasons, or it may be inconvenient to share one seal because the seal is old. Because we often transfer address because of job of customer, it is necessary to submit address change notification or other notification with seal to financial institution and transfer office and office of municipality of transfer place every time . Therefore, if the seal is managed separately by the financial institution and the municipality for the customer, the number of procedures increases and the procedures are cumbersome, and thus time may be wasted.

As described above, in the conventional system, for example, the use seal is registered for each financial institution. Therefore, when opening accounts at a plurality of financial institutions, the registration, renewal, and management of the seal is required at each financial institution. In addition, it is necessary to issue a seal proof in the municipality for each self-governing body in which the seal is registered, and it is necessary to register in the transfer-in municipality every time it moves.

In other words, there is a problem that the customer needs to register a seal at every user's institution, and even if there is a change in the seal or registration data, the procedure must be performed at all registered user's institutions.

On the other hand, in financial institutions, local governments, etc., there exists a problem as a side which introduces a seal registration management system, the initial investment for constructing a system is large, and maintenance cost is also required by each institution. In addition, a manufacturer providing a system had to build a system including a DB by customizing each user.

Therefore, the object of the present invention is to solve these conventional problems, to reduce the cost of introducing a seal registration management system in financial institutions, local governments, and the like, and to register and manage the seal in common. It is also possible to simplify the maintenance afterwards. On the other hand, customers can register with financial institutions and municipalities with one-time seal registration, and the database management system and management for seal matching that is not troublesome even when changing seals or addresses. It is to provide a service method.

In order to achieve the above object, the seal matching database management system of the present invention comprises a seal registration management center for collectively managing seal information and a plurality of user side systems using a seal registration DB managed by the seal registration management center. The control center extracts and reads a seal stamped on a document based on a seal collation DB that stores information for recognizing the type of seal, and determines the type of the seal. It provides an image processing system that contrasts whether or not.

In addition, the seal matching database management system of the present invention connects a seal registration management center side system that creates, manages, and provides a seal matching DB and a user side system using the seal matching DB via a network to seal the registration management center side system. These include: a function of accumulating the read image, a function of registering an attribute such as the owner or the user of the seal, a function of verifying whether the read seal image data and the seal information match the registered seal and the seal information; And a function of transmitting customized seal information and a matching result to a user side system, and a function of referring to billing information of the user side system. The user side system has a function for reading a document with a scanner and a read document. Extracting the portion of the seal from the image and sending it to the Seal Registration Management Center, and Seal Registration Management Function of displaying the determination result of a seal in contrast teocheuk system and, using a seal registration control center and provides the ability to charge the case where the contrast of the seal.

The seal matching database management service method of the present invention transmits the matching result from the seal registration management center to the user side system with respect to the inquiry from the management service user, and the user side system receives the provision of the matching result, thereby providing a service. The seal registration management center uses the charges charged by the number of times of use of the seal registration information or the addition or change of the seal check DB using the seal registration and related data. By claiming, it is possible to obtain a profit as an agency. As a result, it is possible to realize a service that is easy to use while reducing the system input cost on the user side.

In addition, when a seal verification DB does not exist in the seal registration management center, such as initial registration, in advance, it is recommended to transmit documents and desired registration data read by the user side system to the seal registration management center for further registration in the seal verification DB. It is possible.

When the registration seal is changed due to loss of the seal, or when the registration data accompanying the change of the personal information of the seal owner is changed, a document on which the new seal read by the user side system is stamped, or the changed registration data is changed. It is possible to send the seal registration management center and change the corresponding part of the seal check DB.

In addition, by using a function such as an IC card reader from a user side system, an item, a password, and a seal image data in registration data are transmitted to a seal registration management center, and a function of searching for the corresponding seal information is provided. It is possible to retrieve the seal information from the side system.

In the present invention, it is effective in institutions other than financial institutions and local governments, such as insurers, automobile dealers, and real estate agents, which require a publicly recognized seal for consumers to receive services.

1 is an overall configuration diagram of a seal contrast management system.

2 is a conceptual diagram illustrating an example of a seal service.

3 is a data configuration diagram of a management table managed by a seal image management server and registered in a seal image DB.

4 is a data configuration diagram of a management table managed by a seal information management server and registered in a seal information DB.

5 is a data configuration diagram of a management table managed by the user management server and registered in the user customization DB.

6 is a processing flowchart of the user management server.

7 is a processing flowchart of a seal image management server.

8 is a processing flowchart of a seal information management server.

9 is a processing flowchart of a charging information counting terminal.

10 is a processing flowchart of a seal image recognition server.

11 is a processing flowchart of a seal image processing terminal.

<Explanation of symbols for the main parts of the drawings>

10: network

100: seal registration management center side system

101: seal image recognition server

102: seal image management server

103: seal image DB

104: seal information management server

105: seal information DB

106: user management server

107: User Customization DB

108: billing information aggregation terminal

200, 300: user side system

201: seal image processing terminal

202: Scanner

203: data input device

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

(Overall configurations)

1 is an overall configuration diagram of a seal matching database management system showing an embodiment of the present invention.

In Fig. 1, reference numeral 100 denotes a seal registration management center which performs the matching and management of a seal using seal image data and provides a matching result, and reference numeral 200 denotes a financial institution, a local government, or the like using the provided seal information. It is a user side system. Reference numeral 300 denotes a user side system that is different from the user side system 200, and indicates other engines and other industries. That is, there are at least a first user side system and a second user side system. Reference numeral 10 denotes a network.

In the present invention, a seal registration management agency establishes a seal registration management center 100, and contracts a financial institution, a municipality, an insurance company, a guarantee company, or the like as a user, and replaces each financial institution or municipality on a large scale. A database is set up to provide services such as seal registration, registration of seal-related information, user registration, seal verification, and the like, thereby establishing a business model that charges a fee for use. As a result, the user does not need to establish a facility for seal registration and verification, and the cost and personnel can be saved. In addition, by registering a seal only once for customers, it is not necessary to go through the procedure for each financial institution for each municipality even before relocation or change, and it is possible to save time and hassle.

In the seal registration management center 100, reference numeral 101 is read by the scanner 202 of the user side systems 200 and 300, and the seal image DB 103 receives the seal image data received via the network 10. Seal image recognition server to check using the master data stored in the. Reference numeral 102 denotes a seal image management server that manages the seal image DB 103 and stores new registration and change seal image data read by the scanner 202. Reference numeral 104 denotes the management, registration, and change of the seal information DB 105 that stores registration data relating to a seal such as the owner of the seal, a user's institution, and a password, and the like, and registration data for the verification result or request of the seal. Seal information management server to transmit. Reference numeral 106 denotes a user management server which accumulates and manages the user customization DB 107 which edits and stores the contents of the matching result and the registration data notified to the user, and distributes them to the user-side systems 200 and 300, Reference numeral 108 denotes a charging information counting terminal that aggregates the charging information from the user side systems 200 and 300.

In the user-side systems 200 and 300, reference numeral 201 denotes a seal image processing terminal for transmitting a seal image read by the scanner 202 via the network 10, and reference numeral 203 denotes registration data such as personal data. A data input device for entering a search key or password.

In this manner, the seal registration management center 100 of the present invention divides the DB into three and manages each of them in order to accumulate a vast amount of seal images and their related information.

One is the seal image DB 103 which accumulates the seal image itself, and the other is the seal information DB 105 which accumulates registration data related to the seal such as the owner of the seal, the user's institution or the password, etc. A user customization DB 107 that stores information of a user who owns a seal. And the servers 102, 104, 106 which manage and control three DB103, 105, 107, respectively are provided.

The seal registration management center 100 is further provided with a seal image recognition server having a function of collating the seal image sent from the user side systems 200 and 300 with the registered seal image.

(Use example)

2 is a diagram showing an example of use for explaining the outline of the service of the present invention.

As an example, one customer a registers once in the seal registration management center 100 so that the registration data can be used in various contracts, checks, changes or transfers thereafter.

In Fig. 2, reference numeral 100 denotes a seal registration management center, reference numerals 103 and 105 denote a seal image and seal information DB, reference numeral 10 denotes a network, reference numeral 200 denotes A bank, B bank, C municipality, and D insurance. Company.

(1) In opening an account at Bank A, the customer a registers his / her seal with the personal information of the customer in the seal registration management center 100 (from the registration application, the DB of the seal registration management center 100 ( Thick arrow 201 to 103, 105).

(2) After that, the customer a comes to the D insurance company to enter into an insurance contract (thin arrow 203).

(3) The personal seal of the customer a is inquired into the seal registration management center 100 to obtain a collation result (a thick arrow 202 directed from the DB 103, 105 to the D insurance company).

(4) The seal registration management center 100 collects the billing information of the D insurance company and bills it to the D insurance company (the charge for the seal check for the contract).

(5) D insurance company pays the fee for use to seal registration management center 100 (payment to financial institution).

(Each database configuration)

Next, the function of this invention is demonstrated using FIGS.

3 is a data configuration diagram of a management table managed by the seal image management server 102 and registered in the seal image DB 103.

The seal image management server 102 is a server which manages and controls the seal image DB 103 in which the seal image is accumulated, and the seal data ID 301 and the seal image data 302 are registered in the management table. do.

The seal data ID 301 represents a storage place or file name of the seal image data in the seal image DB 103, and the seal image data 302 represents a unique number given for each seal image data. For example, since the address of the seal image DB 103 is uniquely assigned to the seal data ID of id-1, the place can be immediately accessed and read. In addition, since the seal image data of image-1 is a unique number assigned to the seal image, it is immediately possible to recognize which image.

The seal image management server 102 manages all seal image data and provides image data corresponding to a specified seal type. For example, when the seal image recognition server 101 collates the seal image sent from the user system 200, the designated seal data ID is read from the seal image DB 103, and the seal image recognition server 101 is read. To transmit.

4 is a data configuration diagram of a management table managed by the seal information management server 104 and registered in the seal information DB 105.

As shown in Fig. 4, this management table includes a seal data ID 311, personal information (registrant name, address, etc.) 312, an access code 313, and a plurality of use permission institutions (use authority 1). N) 314 is registered.

The seal data ID 311 indicates a unique number of the seal image data and corresponds to a unique number assigned to 302 in the management table of the seal image management server 102.

The seal information management server 104 owns a seal and also manages personal information about a registrant to use, an access code such as a password or a password, and a user organization that uses the seal for each kind of seal.

For example, reference numeral 312 is personal information indicating a registrant name, address, and the like. Reference numeral 313 denotes an access code, and when the access code is set as a password, the security in the case of referring to registration data can be strengthened. If the access code 313 is set as a password, the key for decrypting the password is stored in the IC card, and the data input device 203 of the user-side system 200 is equipped with the function of the IC card reader to provide the IC card. By reading, the security can be strengthened and the convenience can be improved.

In addition, the use permission institution 314 shows the user (financial institution, local government, etc.) authorized to use for each seal. The information on the registered seal is not available unless it is a user registered with the user permission authority 314.

When a customer who has already registered a seal checks the seal at a new user institution, the customer registers the seal by bringing the access code 313 or bringing it to the registered seal. It is confirmed that the user wishes to use the new use organization, and the user is added to the use permission organization 314.

5 is a table configuration diagram of a management table managed by the user management server 106 and registered in the user customization DB 107.

As shown in Fig. 5, the management table managed by the user management server 106 includes a user organization ID 321, an organization name 322, a use condition (registrant name, address, family register, date of birth, seal image). , Verification results, etc.) 323 and the billing information 324 are registered.

The organization name 322 is a unique number assigned to each of the use organization IDs 321 indicating the use organization. The user management server 106 manages for each user the type of registration data available and the charges aggregated by the billing information aggregation terminal 108 for each user's use, when the user contracts with the seal registration management center 100 side. Doing.

The registrant name in the use condition 323 indicates whether or not the registrant name can be displayed when displaying the matching result of the seal on the user side (○ can be displayed, and × cannot be displayed). In addition, as the usage condition 323, as an example of the data which can be used when the user contracts with the seal registration management center 100 side, the registrant's address, family register, date of birth, display of the seal image, whether or not the matching is matched, etc. (All, ○ can be displayed, × cannot be displayed.)

For example, in order to issue a proof of seal in a municipality, image data of the registrant's address and seal is required, but at the time of insurance contract with an insurer, only the seal of use is required, so the image data of the seal is necessary. none. In this way, it is possible to change and manage the use conditions for each user.

The billing information 324 is information billed for each user, and the numerical value is calculated by the billing information aggregation terminal 108 and represents billing information billed to the user. For example, at the end of the month, the charges aggregated for each user from the billing information aggregation terminal 108 are transmitted to the user management server 106, and the respective user side via the network 10 from the user management server 106. It is sent out as a bill to the systems 200 and 300.

(Operation of User Management Server)

6 is a process flow diagram of the user management server 106 showing one embodiment of the present invention. That is, it is a flowchart in which the manager 100 of FIG. 1 performs a registration task etc. in order to manage each user 200 and 300 etc. FIG.

First, in step 501, it is determined whether the user performs new registration. If new registration is performed, the user authority ID 321 is additionally registered in step 502 in the management table of the user customization DB 107. This makes it possible for a new user to enter into a contract with the seal registration management center 100 and to receive the services of the user's institution.

Next, in step 503, necessary use condition data of the user is read out from the user customization DB 107.

This is because the operation terminal checks when a new registration is completed or when a change is made. Although not shown in the figure, this operation terminal exists in the seal registration management center 100, and the new registration and change of the use condition of the user are performed on the seal registration management center 100 and not on the user side.

Next, it is determined whether to correct the data read in step 504. If correction is made, the correction part is read out in step 505 and stored in the user customization DB 107.

(Operation of Seal Image Management Server)

7 is a processing flow diagram of the seal image management server 102 showing one embodiment of the present invention.

First, in step 511, it is determined whether new registration of seal image data is performed. If new registration is performed, the seal image data newly registered in step 512 is stored in the seal image DB 103, and the process ends. Next, in step 513, it is determined whether to correct the read data, and if corrected, the correction part is read out in step 515 and stored in the seal image DB 103.

Next, the seal image data serving as a sample for reading and matching the seal image data necessary in step 514 is read out from the seal image DB 103.

Although not shown in the figure, step 514 is not necessary when an image of the registered seal is not required when the seal is not collated.

(Operation of seal information management server)

8 is a flowchart of a seal information management server according to an embodiment of the present invention.

First, in step 521, it is determined whether new registration of registration data related to a seal is performed, and if new registration is performed, in step 522, a new registration is performed with reference to the seal data ID 301 of the management table of the seal image DB 103. From the unique number assigned to the seal image data, new registration data is stored in the seal information DB 105 in step 523. Next, it is determined whether or not correction of the data read in step 524 is to be performed. If correction is to be made, the correction portion is read out in step 526 and stored in the seal information DB 105.

If it is necessary to read the registration data, the registration data necessary in step 525 is read out from the seal registration DB 105.

7 and 8 show that the seal image data is first registered, and then related information such as personal information of the registrant is registered. However, it is also possible to register personal information first.

(Operation of billing information counting terminal)

9 is a flowchart illustrating a billing information aggregation terminal according to an embodiment of the present invention.

First, in step 531, the user condition data 323 of the user is read from the user customization DB 107 to obtain billing information 324 relating to the user's usage fee and the amount of use. In step 532, the user's billing is calculated from the obtained billing information. Next, the usage fee newly calculated in step 533 is stored in the charging information 324 of the management table of the user customization DB 107.

In addition, when the billing information aggregation terminal 108 charges the user for the usage fee read from the user customization DB 107 on the determined schedule, and confirms that the payment of the bill is completed from the user, the billing information aggregation terminal 108 uses the value obtained by subtracting the charge from the user fee. The data is stored in the customization DB 107. Thereby, the seal registration management center 100 side can manage the billing information to a user, and can make payment request and storage to a user easily.

(Operation of the seal image recognition server)

10 is a flowchart of a seal image recognition server according to an embodiment of the present invention. First, in step 541, the seal image read by the scanner 202 via the network 10 is read out, and in step 542, a matching process is performed using the registered seal image data of the seal image DB 103. Next, the processing result is displayed on the seal image processing terminal 201 via the network 10 in step 543.

Next, the usage condition data customized for each user is read out from the user customization DB 107 in step 544, and the registration data which the user is allowed to start is determined (refer FIG. 5).

That is, according to the contract conditions exchanged between the user side and the seal registration management center 100 side, the information which is permitted to disclose to the user organization about the personal information concerning the registrant of a seal, and the information which is not allowed Screening. In step 545, the registration data that has been allowed to be used is read from the seal information DB 105 and the seal image DB 103. Next, the matching result and the registration data are displayed on the seal image processing terminal 201 via the network 10 in step 546.

The above has demonstrated the case where contrast of a seal is performed. Although not shown in the figure, registered personal information is inputted from the data input device 203 by inputting personal information such as the name and address of the seal registrant or information specifying the type of the seal such as a password stored in the IC card. It is also possible to display a search or seal image data. In this way, it is also possible to display the registered seal image data on the processing terminal 201 and perform the verification by visually confirming by the operator of the processing terminal 201.

(Operation of the seal image processing terminal)

11 is a processing flowchart of a seal image processing terminal showing an embodiment of the present invention. First, the seal image data is read from the image scanner 202 in step 551, and the seal image data read on the screen of the seal image processing terminal 201 is displayed in step 552. In step 553, it is determined whether registration is newly performed. If simply checking the seal, the data input device 203 inputs personal information or an access code such as an I-password or the like as required in step 554.

The data input device 203 includes a keyboard, a mouse, and an IC card reader. In step 555, the seal image data obtained in step 551 and the input data obtained in step 554 are transmitted to the seal image recognition server 101 via the network 10. In operation 556, the matching result of the seal image recognition server 101 is displayed via the network 10. In step 557, it is determined whether the seal image or the registration data is changed.

In the case where new registration is performed in step 553 or data change registration is performed in step 557, new data or change data is input to the data input device 203 in step 558, and the seal image is transmitted via the network 10 in step 560. After transmitting the data to the management server 102 or the seal information management server 104 and receiving the completion notification of the data registration process via the network 10 in step 561, the seal image processing terminal 201 receives the processing result. Mark on.

Accordingly, in the user side system, contract registration with a seal registration management center operated by a seal registration agent enables a simple registration of a seal, registration of information on a seal, registration of user information, and seal matching through a network. Since it can be performed, it is not necessary to build a database or facility for seal registration or seal matching.

In this way, users of financial institutions, municipalities, etc. can save expenses and labor costs, and the registration of the seal can be completed at the same time from the customer who is the counterpart of these users, so that the seal change and the personal information This is convenient because you do not have to go through the procedure several times when changing or relocating your address.

As described above, according to the present invention, the user-side system transmits the seal image data of the customer to the seal registration management center, so that it is not necessary to introduce and operate the seal registration management system on behalf of the seal matching. On the other hand, the seal registration management center can collect a usage fee from the user.

In addition, the customer does not need to manage the use seal for each use organization, and can easily perform new use and change of personal information. For example, in the business of opening an account of a financial institution through a bank window or the like, in the case where registration of a seal possessed by a customer and a comparison of the seal stamped on a document are used, it is particularly used by a plurality of financial institutions. Is available in some cases.

As a result, the customer does not need to register a seal at each of a plurality of financial institutions, so that the registration seal can be used at a plurality of financial institutions in a single registration procedure.

A financial institution does not need to manage the registration seal of the customer, and it is also possible to easily open a new customer account. It is also effective for registration, issuance and use of a seal proof in a municipality. Even if the proof of seal is invalid due to moving or the like, the re-registration procedure can be easily performed at the previous location. Even when a seal certificate is required for the purchase of a car, the seal can be queried by inquiring a seal of a customer seal in the seal registration management center, and the issuance of a seal certificate in a local government is unnecessary.

Claims (16)

In the seal management system which connected the center side system which creates or manages a seal database, and the user side system which uses the said seal database over a network, The center side system, Seal image management means for accumulating and managing seal image data; Seal information management means for registering and managing an attribute including a registrant of the seal and an institution using the seal, Transmission means for transmitting a result of matching between the seal image data received from the user side system and the seal image data accumulated in the seal image management means, to the user side system; The user side system, Reading means for reading the seal, Transmission means for transmitting the image data of the seal read by the reading means to the center side system; Receiving means for receiving a matching result from the center side system; Seal management system, characterized in that. The method of claim 1, And said seal information management means of said center side system manages a name of a licensed authority authorized to use in said user side system. The method of claim 1, And said seal information management means of said center side system manages password information used when a user uses a seal in said user side system. The method of claim 1, The center management system further comprises a user management means for accumulating and managing the use conditions used by the user for each user organization. The method of claim 4, wherein And said user management means stores information indicating whether the user's address or family register is displayed by the user. The method of claim 1, And said center side system further comprises billing information aggregating means for managing a usage fee each time said seal is used in said user side system. The method of claim 6, And said charging information counting means has means for charging said user side system a usage fee incurred in accordance with the number of times of use of said seal. In the seal management method in the seal management system which connected the center side system which creates or manages a seal database, and the user side system which uses the said seal database over a network, A seal is read by the user-side system and the image data of the read seal is transmitted to the center-side system, The center-side system registers the received seal image data corresponding to the registrant of the seal, and registers a user organization that permits the use of the seal; In the user-side system, when a seal is used in the registered user institution, the seal is read by the user-side system and the read seal image data is transmitted to the center-side system, The center side system judges whether or not the received seal image is permitted to be used by the registered user institution, and when it is determined that the use is permitted, contrasts with the already registered seal image data and checks the contrast. Send the result to the user-side system Seal management method comprising the process. The method of claim 8, And registering, by the center side system, a password used when the user uses the seal in the user side system in correspondence with the registrant of the seal. The method of claim 8, The center management system further comprises the step of registering the use condition which a user uses when using the said user side system. The method of claim 10, The seal management method includes information indicating whether at least the user's address or family register is displayed on the user side system. The method of claim 8, And registering the usage fee incurred each time the center side system uses the seal in the user side system. The method of claim 12, And the center side system bills the registered usage fee to the user side system. The method of claim 8, When we change registration seal by loss of seal or when we change registration data with change of personal information of seal owner, And a new seal or changed registration data read by the user side system to the center side system to make a change. The method of claim 14, Seal management method characterized in that for billing the user-side system billed charges incurred in accordance with the change of the seal. The method of claim 8, A seal management method, characterized in that the user side system transmits an item, a password and a seal image data in the registration data to a center side system by using a function such as an IC card reader together and retrieves the corresponding seal information.