JP2019061492A - Address management device, address management method, and address management program - Google Patents

Abstract

To provide an address management device, an address management method, and an address management program that can accurately perceive claim information including a mortgage borrowed by a same person.SOLUTION: An address management device 100 normalizes name data included in claim data and obtains the normalized name data and/or the normalized last name data. The same normalizes address data included in the claim data and obtains the normalized address data. It then generates, based on point masters, divided data in which the normalized address data is identified and divided by layers and, compares the divided data, the normalized name data and/or the normalized last name data one another, and identifies the same claim data for a same debtor from the claim data.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an address management device, an address management method, and an address management program.

  Patent Document 1 separates a character string included in an address into a character string indicating a municipality and a character string indicating a ground number, and normalizes a ground number notation in credit screening using an unmanned contract machine of consumer finance, etc. The structure which judges identity by doing is disclosed.

  In Patent Document 2, in the address search service, the address data to be searched is hierarchically stored, the place name, the place number, etc. are normalized, the character string included in the address is divided, and there is no prefecture city character. However, the structure which specifies an address by cost calculation is described.

JP, 2009-110359, A JP 2012-155356 A

  However, in Patent Document 1-2 described above, a configuration is not described in which the identity of bond information (collateralized property information) is determined using address and name normalization, and the same person is not There was a problem that it was not possible to accurately capture the mortgage loaned by

  The present invention has been made in view of the above problems, and provides an address management device, an address management method, and an address management program that can accurately capture bond information such as a mortgage loaned by the same person. Intended to be provided.

  In order to solve the problems described above and achieve the object, an address management apparatus according to the present invention is an address management apparatus including a storage unit and a control unit, and the storage unit includes name data of a debtor The control unit comprises: bond data storage means for storing bond data storing bond data including address data; and point storage means for storing a point master including point data hierarchically representing point names; A name normalization means for normalizing said name data included in said bond data stored in said bond data storage means, and obtaining normalized Mr. data and / or normalized name data, and storing in said bond data storage means Address normalization means for normalizing the address data included in the bond data, and obtaining normalized address data, and hierarchically arranging the normalized address data based on the point master Divided data generation means for generating divided data specified and divided, the divided data, the normalized name data and / or the normalized Mr. data are compared with each other, and the receivables stored in the receivables data storage means And the same identifying means for identifying the debt data of the same debtor from the data.

  In the address management apparatus according to the present invention, the control unit further comprises divided data storage means for associating the divided data with the bond data and storing the divided data in the bond data storage means.

  Further, in the address management device according to the present invention, the divided data storage unit further determines the accuracy of the address data from the matching result of the divided data, the normalized Mr. data and the normalized name data for the point master. It is characterized in that matching level data shown is acquired, the matching level data is linked to the bond data, and the bond data is stored in the bond data storage means.

  In the address management device according to the present invention, the spot data may further include a spot code for each hierarchy, and the division data generation unit may include the spot code for each hierarchy based on the spot master. It is characterized by generating data.

  In the address management device according to the present invention, the spot data may further include a spot code for each hierarchy, and the division data generation unit may include the spot code for each hierarchy based on the spot master. Data is generated, and the division data storage unit further acquires position coordinates based on the division data including the point master, the normalized name data, the normalized Mr data, and the point code for each hierarchy. The position data is linked to the bond data and stored in the bond data storage means.

  Further, in the address management apparatus according to the present invention, the name normalization means may perform full normalization on the name data included in the bond data stored in the bond data storage, and a position of space data included in the name data. Normalizing the name data based on the determination of the name and the name by the user and / or the deletion of the space data included in the name data, and acquiring the normalized Mr data and / or the normalized name data It is characterized by

  Further, in the address management device according to the present invention, the address normalization unit may perform full normalization on the address data included in the bond data stored in the bond data storage unit, and delete space data included in the address data. And / or normalizing the address data based on deletion of specific character data included in the address data, and acquiring the normalized address data.

  Further, in the address management device according to the present invention, the divided data generation unit specifies the position of the break position data included in the normalized address data, and the normalized address data divided by the break position data and the divided address data. It is characterized in that the divided data is generated by specifying and dividing the normalized address data for each hierarchy based on the comparison with the hierarchically expressed spot data included in the spot master.

  Further, in the address management device according to the present invention, the division position data may include: city, road, prefecture, prefecture, city, ward, group, town, village, first, last, first, last or second letter data, hyphen data, and And / or numerical data.

  Further, the address management device according to the present invention is characterized in that the specific character data is large character data and / or hyphen data.

  Further, an address management method according to the present invention is an address management method for causing an address management apparatus including a storage unit and a control unit to execute, wherein the storage unit includes name data and address data of a debtor. Bond data storage means for storing bond data storing the bond data to be included; and point storage means for storing a point master including point data hierarchically representing point names, and the control unit is made to execute A name normalization step of normalizing the name data included in the bond data stored in the bond data storage means and acquiring normalized Mr. data and / or normalized name data; and the bond data storage means stored in the bond data storage means An address normalization step of normalizing the address data included in the bond data and obtaining normalized address data; and based on the point master, the normalized address Step of generating divided data by specifying the data for each hierarchy and generating divided data, comparing the divided data, the normalized name data and / or the normalized Mr. data, and storing them in the bond data storage means And the same identifying step of identifying the debt data of the same obligor from the debt data.

  Further, an address management program according to the present invention is an address management program for causing an address management apparatus including a storage unit and a control unit to execute, wherein the storage unit includes name data and address data of a debtor. Bond data storage means for storing bond data storing the bond data to be contained; and point storage means for storing a point master including point data hierarchically representing point names; and in the control unit, the bond data A name normalization step of normalizing the name data included in the bond data stored in the storage means and acquiring normalized Mr. data and / or normalized name data; and the bonds stored in the bond data storage means An address normalization step of normalizing the address data included in the data and obtaining normalized address data; and the regularity based on the point master. Divided data generation step of specifying divided address data for each hierarchy and generating divided data, comparing the divided data, the normalized name data and / or the normalized Mr. data, and And the same identifying step of identifying the debt data of the same obligor from the debt data stored.

  According to the present invention, the address data can be specified from the collateral property information of each mortgage loan held, and the position data of the map can be automatically linked and registered. Further, according to the present invention, even if there is distortion of held character information, there is an effect that it becomes possible to treat as information with high accuracy by cleaning. Further, according to the present invention, it is possible to specify correct position information even with information not held by a code. In addition, when the address data is held as character data, there are a plurality of patterns for expressing the same address, but according to the present invention, correct discrimination can be made by character data cleaning and data division. It plays an effect. Further, according to the present invention, when the same person newly borrows a new mortgage, it is possible for the lender to capture accurate information.

FIG. 1 is a block diagram showing an example of the configuration of the address management device. FIG. 2 is a view showing an example of a bond data file according to the present embodiment. FIG. 3 is a diagram showing an example of a prefecture master in the present embodiment. FIG. 4 is a diagram showing an example of the municipality master in the present embodiment. FIG. 5 is a diagram showing an example of a town street master in the present embodiment. FIG. 6 is a diagram showing an example of a block master in the present embodiment. FIG. 7 is a diagram showing an example of a ground number nameplate master in the present embodiment. FIG. 8 is a diagram showing an example of another master in the present embodiment. FIG. 9 is a flowchart showing an example of processing of the address management device in the present embodiment. FIG. 10 is a diagram showing an example of the address management process in the present embodiment. FIG. 11 is a diagram showing an example of the address normalization process according to the present embodiment. FIG. 12 is a diagram showing an example of the address normalization processing in the present embodiment. FIG. 13 is a diagram showing an example of the address normalization processing in the present embodiment. FIG. 14 is a diagram showing an example of the address normalization process in the present embodiment. FIG. 15 is a diagram showing an example of the name normalization process in the present embodiment. FIG. 16 is a diagram showing an example of the name normalization process in the present embodiment. FIG. 17 is a diagram showing an example of the name normalization process in the present embodiment. FIG. 18 is a diagram showing an example of the name normalization process according to the present embodiment. FIG. 19 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 20 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 21 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 22 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 23 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 24 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 25 is a diagram showing an example of a point code identification process according to the present embodiment. FIG. 26 is a diagram showing an example of the address normalization process in the present embodiment. FIG. 27 is a diagram showing an example of point code identification processing in the present embodiment. FIG. 28 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 29 is a diagram showing an example of a point code identification process according to the present embodiment. FIG. 30 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 31 is a diagram showing an example of a point code identification process according to the present embodiment. FIG. 32 is a diagram showing an example of point code identification processing according to the present embodiment. FIG. 33 is a diagram showing an example of a lot number specifying process in the present embodiment. FIG. 34 is a diagram showing an example of a lot number specifying process in the present embodiment. FIG. 35 is a diagram showing an example of a lot number specifying process according to the present embodiment. FIG. 36 is a diagram showing an example of a lot number specifying process in the present embodiment. FIG. 37 is a diagram showing an example of a lot number specifying process according to the present embodiment. FIG. 38 is a diagram showing an example of a lot number specifying process in the present embodiment. FIG. 39 is a diagram showing an example of position registration processing in the present embodiment. FIG. 40 is a diagram showing an example of position registration processing in the present embodiment. FIG. 41 is a diagram showing an example of position registration processing in the present embodiment. FIG. 42 is a diagram showing an example of position registration processing in the present embodiment. FIG. 43 is a diagram showing an example of a position registration process in the present embodiment. FIG. 44 is a diagram showing an example of position registration processing in the present embodiment.

  Embodiments of the present invention will be described in detail based on the drawings. The present invention is not limited by this embodiment.

[1. Overview]
First, the outline of the present invention will be described.

  In the past, in the mortgage business, such as mortgages, the number of customer transaction data may reach several millions, and since address data matching was performed by the person who relied on the inspection of the person in charge, registration was simple. There were cases where leaks occurred and cases where it was not possible to capture accurate information on newly added bond data by the same person.

  Therefore, in the present embodiment, although the data is originally the same data, the bond data that was captured as different data due to the undescribed state of the prefecture, the presence of a space in the address, or the difference in full width and half width etc. Since it is possible to specify as debt data by the same obligor by automatically linking by raising the matching accuracy, it is possible to prevent the creditors from defaulting.

[2. Constitution]
An example of the configuration of the address management device 100 according to the present embodiment will be described with reference to FIGS. 1 to 8. FIG. 1 is a block diagram showing an example of the configuration of the address management device 100. As shown in FIG.

  The address management device 100 is a commercially available desktop personal computer. The address management apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, but may be a portable personal computer such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smartphone, a tablet personal computer, etc. It may be an information processing apparatus.

  The address management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the address management device 100 are communicably connected via an arbitrary communication path.

  The communication interface unit 104 communicably connects the address management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with another device via a communication line. Here, the network 300 has a function of communicably connecting the address management device 100 and the server 200, and is, for example, the Internet, a local area network (LAN), or the like.

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving instructions to a central processing unit (CPU) in cooperation with an operating system (OS) to perform various processes. As the storage unit 106, for example, a memory device such as a random access memory (RAM) or a read only memory (ROM), a fixed disk device such as a hard disk, a flexible disk, an optical disk or the like can be used. The storage unit 106 includes a bond data file 106a and a point master 106b.

  The bond data file 106a stores bond data (basic data) including name data and address data of the debtor.

  Here, with reference to FIG. 2, an example of the bond data file 106a in the present embodiment will be described. FIG. 2 is a view showing an example of the bond data file 106a in the present embodiment.

  As shown in FIG. 2, in the present embodiment, the bond data stored in the bond data file 106a includes customer / credit data including a customer number, a customer application name kanji name, a construction site code, etc., and an address code, It may be composed of security data including prefecture kanji names, city / gun kanji names, address of town village kanji names, etc.

  Returning to FIG. 1, the point master 106 b is a master that includes point data representing the point names hierarchically. Here, the point data may include a point code for each hierarchy. In addition, the point master 106b may include a prefecture master, a city master, a town master, a town master, a street number card label master, and a separately mentioned master. Here, the ground number card label master and the separately mentioned master may be data provided with map data (point data) provided by the map data providing service, or may be data collected uniquely.

  Here, an example of the point master 106 b in the present embodiment will be described with reference to FIGS. 3 to 8. FIG. 3 is a diagram showing an example of a prefecture master in the present embodiment. FIG. 4 is a diagram showing an example of the municipality master in the present embodiment. FIG. 5 is a diagram showing an example of a town street master in the present embodiment. FIG. 6 is a diagram showing an example of a block master in the present embodiment. FIG. 7 is a diagram showing an example of a ground number nameplate master in the present embodiment. FIG. 8 is a diagram showing an example of another master in the present embodiment.

  As shown in FIG. 3, in the present embodiment, the prefecture master may include a prefecture No, a prefecture name, and the like in accordance with the JIS standard. Further, as shown in FIG. 4, in the present embodiment, the municipality master may include a municipality No, a municipality name, etc. in accordance with the JIS standard. Further, as shown in FIG. 5, in the present embodiment, the town chome master may include a town chome No and a town chome name in accordance with the JIS standard. Further, as shown in FIG. 6, in the present embodiment, the block master may include a municipality No, a town chome No, a block No, a map X coordinate, a map Y coordinate, and the like. Further, as shown in FIG. 7, in the present embodiment, the ground number nameplate master includes an attribute type code (CD), a municipality No, a town district No, a block No, a ground number, a door number, an attribute name, a building floor number, a map It may include an X coordinate and a map Y coordinate. Further, as shown in FIG. 8, in the present embodiment, the separately-described master may include an attribute type CD, a floor number type, a floor number, a room name, a separately-described attribute name, and the like.

  Returning to FIG. 1, the input device 112 and the output device 114 are connected to the input / output interface unit 108. For the output device 114, in addition to a monitor (including a touch panel), a speaker or a printer can be used. The input device 112 can be a keyboard, a mouse, a microphone, and a monitor that cooperates with the mouse to realize a pointing device function. Hereinafter, the output device 114 may be described as the monitor 114 or the printer 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

  The control unit 102 is a CPU or the like that controls the address management apparatus 100 in an integrated manner. The control unit 102 has an internal memory for storing control programs such as the OS, programs defining various processing procedures, required data, etc., and performs various information processing based on the stored programs. Run. The control unit 102 conceptually includes a name normalization unit 102a, an address normalization unit 102b, a divided data generation unit 102c, a divided data storage unit 102d, and an identical specification unit 102e.

  The name normalization unit 102a normalizes the name data included in the bond data stored in the bond data file 106a, and acquires normalized Mr. data and / or normalized name data. Here, the name normalization unit 102a performs full normalization on the name data included in the bond data stored in the bond data file 106a, determines the name and the name according to the position of the space data included in the name data, and / or The name data may be normalized based on the deletion of space data included in the name data to obtain normalized Mr data and / or normalized name data. In addition, the name normalization unit 102a may normalize the name data included in the bond data stored in the bond data file 106a and acquire the normalized name data.

  The address normalization unit 102b normalizes the address data included in the bond data stored in the bond data file 106a, and acquires the normalized address data. Here, the address normalization unit 102b performs full normalization of the address data included in the bond data stored in the bond data file 106a, deletion of the space data included in the address data, and / or specific characters included in the address data. Based on the data removal, the address data may be normalized to obtain normalized address data. Here, the specific character data may be alphabetic character data and / or hyphen data.

  The divided data generation unit 102c generates divided data in which the normalized address data is specified and divided for each hierarchy based on the point master 106b. Here, the divided data generation unit 102c may generate divided data including a point code for each hierarchy based on the point master 106b. Further, the divided data generation unit 102c specifies the position of the break position data included in the normalized address data, and the hierarchically represented points included in the normalized address data and the point master 106b divided by the break position data. Based on comparison with data, normalized address data may be specified for each hierarchy and divided data may be generated. Here, the zoning position data is character data, hyphen data, and / or numerical data of city, road, prefecture, prefecture, city, ward, group, town, village, armor, armor, armor and / or ding May be

  The divided data storage unit 102d associates the divided data with the bond data and stores the bond data in the bond data file 106a. Here, the divided data storage unit 102d acquires matching level data indicating the accuracy of the address data from the divided data for the point master 106b, the matching result of the normalized Mr. data and the normalized name data, and matches the credit data to the matching level data. May be linked and stored in the bond data file 106a. The division data storage unit 102d acquires position coordinates based on division data including the point master 106b, normalized name data, normalized Mr. data, and point codes for each hierarchy, and associates position coordinates with bond data. May be stored in the bond data file 106a. Further, the divided data storage unit 102d may store the data of the bond in the bond data file 106a by correlating the normalized data with normalized data, normalized name data, normalized name data and / or normalized address data.

  The same specifying unit 102e compares the divided data, the normalized name data, and / or the normalized Mr. data, and specifies the bond data of the same obligor from the bond data stored in the bond data file 106a. The same identification unit 102e may associate an identifier for identifying the bond data of the same obligor with the bond data, and store the identifier data in the bond data file 106a.

[3. Concrete example]
Specific examples of the present embodiment will be described with reference to FIGS. 9 to 44.

Address Management Process
Here, with reference to FIG. 9, an example of the address management process in the present embodiment will be described. FIG. 9 is a flowchart showing an example of processing of the address management device 100 in the present embodiment.

  As shown in FIG. 9, the name normalization unit 102a performs full normalization on the name data included in the bond data stored in the bond data file 106a, and determines the name and the name according to the position of the space data included in the name data; And, based on deletion of space data included in the name data, the name data is normalized, and normalized Mr. data, normalized name data and normalized name data are acquired (step SA-1).

  Then, the address normalization unit 102b is full normalization of the address data included in the bond data stored in the bond data file 106a, deletion of the space data included in the address data, and specific character data included in the address data. The address data is normalized based on the deletion of the Japanese character data and the hyphen data to obtain normalized address data (step SA-2).

  Then, the divided data generation unit 102c is character position data of a city, a road, a prefecture, a prefecture, a city, a group, a group, a town, a village, a shell, a collar, a collar and a branch which are divisional position data included in normalized address data Normalized address data based on hyphenated data and comparison between the normalized address data separated by the separated position data and the hierarchically represented point data included in the point master 106b by specifying the position of the numeric data The division data is generated including the point code for each hierarchy, which is specified and divided for each hierarchy (step SA-3).

  Then, the division data storage unit 102d acquires matching level data indicating the accuracy of the address data from the division data for the point master 106b, the matching result of the normalized Mr. data and the normalized name data, and the point master and the normalized name data , Based on divided data including normalized Mr. data and point code for each hierarchy, obtain position coordinates, and to bond data, divided data including point code for each hierarchy, matching level data, position coordinates, normalized Mr. data And the normalized name data is stored in the bond data file 106a (step SA-4).

  Then, the same specifying unit 102e compares the divided data stored in the bond data file 106a with the bond data, the normalized name data, and the normalized Mr. data, and compares the bond data stored in the bond data file 106a. The bond data of the same obligor is specified, an identifier for identifying the bond data of the same obligor is associated with the bond data, and stored in the bond data file 106a (step SA-5), and the process is ended.

  Here, details of the address management process in the present embodiment will be described with reference to FIGS.

  First, with reference to FIG. 10, the entire configuration of the address management process in the present embodiment will be described. FIG. 10 is a diagram showing an example of the address management process in the present embodiment.

  As shown in FIG. 10, in a relational database such as a SQL server in this embodiment, position registration target data which is address matching target data by normalizing basic data (address data and name data included in bond data). (Normalized address data) is generated (step SB-1), and divided data is generated by performing matching (comparison) with the point data included in the point master 106b (step SB-2). Then, in the relational database in the present embodiment, position data (position coordinates) is acquired based on the point master 106b (step SB-3), position coordinates are linked to bond data, and stored in bond data file 106a. (Step SB-4).

  An example of the address normalization processing according to the present embodiment will be described with reference to FIGS. 11 to 14. 11 to 14 are diagrams showing an example of the address normalization process according to the present embodiment.

  As shown in FIG. 11, in the present embodiment, character string data of prefecture kanji names, city / gun kanji names and Machimura address kanji names included in the basic data are combined. Then, as shown in FIG. 12, in the present embodiment, normalization may be performed by trimming space data before or after the first character data.

  Further, as shown in FIG. 13, in the present embodiment, normalization may be performed by converting half-width data in character string data into full-width data. Further, as shown in FIG. 14, in the present embodiment, the normalized address data used for matching is “2-4-15, Kyobashi, Chuo-ku, Tokyo” by deleting full-width space data in character string data. It may be acquired as 14 characters.

  An example of the name normalization process according to the present embodiment will be described with reference to FIGS. 15 to 18. FIG. 15 to FIG. 18 are diagrams showing an example of the name normalization process in the present embodiment.

  As shown in FIG. 15, in the present embodiment, normalization may be performed by trimming space data after the final character data. Further, as shown in FIG. 16, in the present embodiment, normalization may be performed by converting half-width data in character string data into full-width data. Further, as shown in FIG. 17, in the present embodiment, character string data up to full-width space data in character string data may be acquired as normalized Mr. (last name) data of a debtor. Further, as shown in FIG. 18, in the present embodiment, full-width space data in the character string data may be deleted to obtain normalized name (full name) data of the debtor.

  Moreover, with reference to FIGS. 19-32, an example of the point code identification process in this embodiment is demonstrated. FIGS. 19 to 25 and FIGS. 27 to 32 are diagrams showing an example of point code identification processing according to the present embodiment. FIG. 26 is a diagram showing an example of the address normalization process in the present embodiment.

  In the present embodiment, when the prefecture part in the address data is specified, the data from the left 3 characters to the left 4 characters in the address data to be determined is the determination target, and “city” in the character string to be determined If there is any character data of Michi, "Fu", and "Prefectural", it is the search target of the prefecture master. For example, as shown in FIG. 19, in the present embodiment, when the kanji address data is "Tokyo Chuo Ward ~," "Tokyo" is acquired as three-character data to be checked (judged), and "Tokyo You may acquire a prefecture code by searching for a prefecture master with "." Also, as shown in FIG. 20, in the present embodiment, when the kanji address data is “Yokohama City, Kanagawa Prefecture,” “Kanagawa” is acquired as three-character data to be checked (judged), and “Kanagawa” The prefecture master is searched, and since there is no corresponding data, "Kanagawa prefecture" is acquired as 4-character data to be checked (judged), and the prefecture master code is acquired by "Kanagawa prefecture" to acquire a prefecture code May be Also, as shown in FIG. 21, in the present embodiment, when the kanji address data is “Chuo-ku, Yokohama-shi”, “Yokohama-shi” is acquired as 3-character data to be checked (judged), “Yokohama-shi The prefecture master is searched by "", and because there is no corresponding data, "Yokohama city" is acquired as 4-character data for checking (judgment), and the prefecture master is searched by "Yokohama city", and the corresponding There is no data, that is, there is no prefecture value (data), so the prefecture code is not acquired.

  Further, in the present embodiment, when the prefecture code can be acquired among the address data to be determined, the character string data is deleted from the left of the address data by the number of characters of the prefecture name and character string data to be determined is acquired. Do. For example, as shown in FIG. 22, in the present embodiment, character string data such as “Tokyo” or “Chiba” may be deleted from the left of the address data. And in this embodiment, you may search a municipality master in order from the character string data of the left two characters of the character string data of determination object (A complete match is finally made using a forward match search. May identify the city name of In the present embodiment, the reason for searching from the left two-character string data is that the minimum character unit of the municipality is two characters (for example, "Tsu City", "Kashiwacho" or "Minami Ward", etc.) This is because For example, as shown in FIG. 23, in the present embodiment, as shown in FIG. 24, the address data and the municipality master are sequentially searched from the left two-character string data in a forward match. It is possible to specify a completely matched character string data of “Niigata City Kita Ward” (longest character string data that is one round before and a round) and to obtain a city code. In the present embodiment, the number of characters of the municipality name may be acquired (held) along with the municipality code.

  Further, in the present embodiment, if the city code can be acquired among the determined address data, only the character string data of the prefecture and the city among the determined address data is deleted from the left Then, the character string data to be judged is acquired. For example, as shown in FIG. 25, in the present embodiment, character string data obtained by deleting character string data such as "Fuchu City, Tokyo Prefecture" and "Ichikawa City, Chiba Prefecture" from address data is acquired, and the character string data In the case where “O” is attached at the beginning of the above, as shown in FIG. 26, it may be deleted. Then, in the present embodiment, the position where the character type changes in the kanji address is specified for the address data determined (after the character string data of the municipality). For example, as shown in FIG. 27, in the present embodiment, the position where “Ding” of the kanji address appears is specified, and the position where “Ding” appears is from the left of the character string data to be determined. It may be specified that it is the 4'th position. In addition, as shown in FIG. 28, in the present embodiment, when it is not possible to specify the position where the "Ding" of the kanji address appears, -1 of the position where the "numerical value" of the The position of “previous” may be specified, and the “3-1 = 2” -th position from the left of the character string data to be determined may be specified. Then, in the present embodiment, for the characters following the position at which the specified character type changes, a town match of a perfect match is finally identified using a forward match search. In the present embodiment, the search may be performed in a state in which the hyphen is converted to “chome”. For example, as shown in FIG. 29, in the present embodiment, as shown in FIG. 30, the address data and the town and town master are searched sequentially from the character string data after the position where the character type changes. The character string data of “Ashizuka” may be specified (the one which is immediately before the cross and the longest character string data which becomes a circle) may be specified, and the town code may be acquired. In the present embodiment, the number of characters of the town name may be acquired (held) along with the town code.

  Further, in the present embodiment, when the street address code can be acquired among the address data to be determined, only the character string data of the prefecture, the municipality and the city street among the address data to be determined are character string data from the left Is deleted to obtain character string data to be judged. In the present embodiment, if the character data of the first character of the address data from which the character string data of the prefecture, city, town and district is deleted is located immediately after the character data of the city (after the city data), the first character is used. delete. For example, as shown in FIG. 31, in the present embodiment, the character data of "-" immediately before "3" may be deleted. Then, in the present embodiment, the block master is searched based on the city code and the town code obtained by the processing up to this point, and if the block code does not exist, the block number is 0 (no block). Set as. On the other hand, in the present embodiment, when there is a block code corresponding to the block master, character data to be a block position (such as a hyphen or a number) is specified from the character string data to be determined. On the other hand, in this embodiment, when the character data used as the division | segmentation position of a town block can not be specified, the position where a thing other than a numerical value comes out is specified after the 1st character of character string data of judgment object. For example, as shown in FIG. 32, in this embodiment, it may be specified that it is the “2” -th from the left, which is the position of “next” of “3”. Then, in the present embodiment, when the division position can be specified, the block master is searched based on the city code, the town code, and the kanji address up to the front of the division position, and the block code is acquired. If the location can not be identified, the ground number name is identified as it is.

  Moreover, with reference to FIG. 33 to FIG. 38, an example of a ground lot name specifying process in the present embodiment will be described. 33 to 38 are diagrams showing an example of a ground lot name specifying process according to the present embodiment.

  In the present embodiment, when the block code can be acquired among the address data to be determined, only the character string data of the prefecture, city, city, town and street among the address data to be determined are character string data from the left Delete and acquire the character string data of the judgment target. And in this embodiment, a ground number is specified about character string data of judgment object. Here, in the present embodiment, when the two character string data from the left of the character string data to be determined are the character string data of “Kou”, “Otsu”, “Hey” or “Tai”, FIG. As shown in, each may be converted into character string data of kanji. Also, in the present embodiment, the character data after the character data of “K”, “K”, “K”, “D”, “K”, “K”, “S”, “K” or “Ki” is a space. In the case of data or hyphen data, space data or hyphen data may be deleted. For example, as shown in FIG. 34, in the present embodiment, when full-width space data exists after the character string data of “K” in the character string data to be determined, the character string data of “K” is “K” While converting into the character data of, it is possible to delete full-width space data. Further, as shown in FIG. 35, in the present embodiment, when hyphen character data is present after the character string data of “K” in the character string data to be determined, the character string data of “K” is While converting to character data, hyphen data may be deleted. Further, in the present embodiment, for the character string data of the determination target (Kanji address), the area from the left up to where the character data other than numeric data or hyphen data appears is specified as the address. That is, in the present embodiment, numerical data or hyphen data is checked sequentially from the first character data from the left (however, the first character is “K”, “K”, “K”, “D”). If the character data of the second character is numeric data, the character data of any of “、”, “己”, “己”, “庚” or “辛” is checked from the third character). For example, as shown in FIG. 36, in the present embodiment, when character data other than numeric data or hyphen data is not included, the character string data as it is may be specified as an address. Further, as shown in FIG. 37, in the present embodiment, the character string data of "3-33" until "A" appears may be specified as the address. Further, as shown in FIG. 38, in the present embodiment, the character string data of “A 4-5” until “H” appears may be specified as the address. Further, in the present embodiment, it may be converted into hyphen data matched with attribute information (attribute name) of a map (point data). Then, in the present embodiment, by applying these methods, together with specifying the ground number name, the number of characters of the ground number name may also be acquired (held).

  In addition, an example of the position registration process according to the present embodiment will be described with reference to FIGS. 39 to 44. 39 to 44 are diagrams showing an example of position registration processing according to the present embodiment.

  In the present embodiment, automatic position (XY) coordinates are registered for each bond data from the application name kanji name, construction site code, and address character string data based on the generated divided data. Here, as shown in FIG. 39, in the present embodiment, six matching levels may be used as the accuracy of the address data. Here, FIG. 40 shows the acquisition condition of the matching level 1. Here, as for FIG. 40 [1], in this embodiment, it is shown that (repeated) retrieval is performed using character string data from which the hyphen from the end of the ground number name is removed. For example, as shown in FIG. 41, in the present embodiment, a character string data (removed 1) obtained by removing "-404" from the original land number name, and a character removed by "-10" You may search by column data (removed one 2). Further, in FIG. 40 [2], in the present embodiment, since there is a possibility that plural items of name data may be extracted, it is shown that the matching of the name data is repeatedly performed after the extraction. Here, in the present embodiment, when the attribute name of the identified ground number card label master matches the kanji name (full name) of the basic data, the position coordinates may be held and the repetition may be ended. Further, in the present embodiment, when the attribute name of the identified ground number card label master matches the kanji name (surname) of the basic data, the position coordinates may be held and matched with the next data. For example, in the present embodiment, the normalized name data and the normalized Mr. data shown in FIG. 1 to No. First, when comparing with No. 3, normalized name data and No. The comparison with 1 makes it possible to identify that the full name is not identical and the last name is identical. The position coordinates of 1 are held, and as repeated processing, normalized name data and No. 1 are stored. The comparison with 2 can identify that the full name matches, so that the normalized Mr. data and No. No. 3 without comparison. The process may end by holding the position coordinates of 2. Further, in the present embodiment, the normalized name data and the normalized Mr. data shown in FIG. 1 to No. When comparing with 2 in order, first, normalized name data and No. The comparison with 1 makes it possible to identify that the full name is not identical and the last name is identical. The position coordinates of 1 are held, and as repeated processing, normalized name data and No. 1 are stored. By comparing with 2, it is possible to identify that the full name is not identical and the last name is not identical. The position coordinates of 1 may be held as it is. Further, with regard to FIG. 40 [3], in the present embodiment, it is shown that “-” is added to the end of the result of FIG. 40 [1] and the forward matching search is performed based on this.

[4. Other embodiments]
The present invention may be practiced in various different embodiments within the scope of the technical idea described in the claims in addition to the embodiments described above.

  For example, among the processes described in the embodiment, all or part of the process described as being automatically performed may be manually performed, or all the processes described as being manually performed. Alternatively, some of them can be performed automatically by known methods.

  In addition, information including processing procedures, control procedures, specific names, registered data of each processing, parameters such as search conditions, screen examples, and database configurations shown in the present specification and the drawings are described unless otherwise specified. Can be changed arbitrarily.

  Further, with regard to the address management device 100, each component shown in the drawings is functionally conceptual and does not necessarily have to be physically configured as shown.

  For example, with regard to processing functions included in the address management apparatus 100, in particular each processing function performed by the control unit 102, all or any part of the processing functions are realized by a CPU and a program executed by the CPU. May also be implemented as wired logic hardware. The program is recorded in a non-temporary computer-readable recording medium that includes a programmed instruction for causing the information processing apparatus to execute the processing described in the present embodiment, and the address management apparatus as needed. Mechanically read to 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into the RAM, and cooperates with the CPU to configure the control unit.

  Also, this computer program may be stored in an application program server connected to the address management device 100 via an arbitrary network, and it is possible to download all or a part of the computer program as required. is there.

  Further, the program for executing the processing described in the present embodiment may be stored in a non-temporary computer readable recording medium, or may be configured as a program product. Here, the "recording medium" means a memory card, a universal serial bus (USB) memory, a secure digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an erasable programmable read only memory (EPROM), and an EEPROM (registration). Trademarks (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Blu-ray (registered trademark) Disc etc. Any "portable physical media It is intended to include.

  The “program” is a data processing method described in any language or description method, and may be in any format such as source code or binary code. Note that the “program” is not necessarily limited to one that is configured in a single way, and achieves its function in cooperation with a separate program represented by a plurality of modules or libraries or a separate program represented by the OS. Including things. In addition, as a specific configuration and a reading procedure for reading a recording medium in each device shown in the present embodiment, an installation procedure after reading, and the like, a known configuration and procedure can be used.

  The various databases and the like stored in the storage unit 106 are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, storage means such as optical disks, etc. Stores programs, tables, databases, files for web pages, etc.

  In addition, the address management device 100 may be configured as an information processing device such as a known personal computer or a work station, or may be configured as the information processing device to which an arbitrary peripheral device is connected. In addition, the address management device 100 may be realized by implementing software (including a program or data or the like) that causes the device to realize the processing described in the present embodiment.

  Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them may be functionally or physically in any unit in accordance with various additions or according to functional load. It can be distributed and integrated. That is, the embodiments described above may be implemented in any combination, and the embodiments may be implemented selectively.

  The present invention is useful in, for example, the financial industry that manages address data included in bond data.

100 address management apparatus 102 control unit 102a name normalization unit 102b address normalization unit 102c division data generation unit 102d division data storage unit 102e identical identification unit 104 communication interface unit 106 storage unit 106a bond data file 106b point master 108 input / output interface unit 112 input device 114 output device 200 server 300 network

Claims (12)

An address management apparatus comprising a storage unit and a control unit, wherein
The storage unit is
Claim data storage means for storing claim data storing claim data including name data and address data of debtor;
Point storage means for storing a point master including point data hierarchically representing point names;
Equipped with
The control unit
Name normalization means for normalizing the name data included in the bond data stored in the bond data storage means, and obtaining normalized Mr. data and / or normalized name data;
Address normalization means for normalizing the address data contained in the bond data stored in the bond data storage means, and obtaining normalized address data;
Division data generation means for generating division data by specifying and dividing the normalized address data for each hierarchy based on the point master;
The same specification for identifying the bond data of the same obligee from the bond data stored in the bond data storage means by comparing the divided data, the normalized name data, and / or the normalized Mr. data Means,
An address management apparatus comprising: The control unit
Divided data storage means for associating the divided data with the bond data and storing the divided data in the bond data storage means,
The address management device according to claim 1, further comprising: The divided data storage unit
Furthermore, matching level data indicating the accuracy of the address data is obtained from the matching result of the division data, the normalized Mr. data and the normalized name data for the point master, and the matching level data is linked to the bond data. The address management apparatus according to claim 2, wherein the address data is stored in the bond data storage means. The point data is
Furthermore, it contains a point code for each hierarchy,
The divided data generation unit
The address management device according to any one of claims 1 to 3, wherein the division data including the point code for each hierarchy is generated based on the point master. The point data is
Furthermore, it contains a point code for each hierarchy,
The divided data generation unit
The division data including the point code for each hierarchy is generated based on the point master, and the division data storage unit
Further, position coordinates are obtained based on the divided data including the point master, the normalized name data, the normalized Mr data, and the point code for each hierarchy, and the position data is linked to the bond data. The address management device according to claim 2 or 3, wherein the address data is stored in the bond data storage means. The name normalization means is
Full-time normalization for the name data included in the bond data stored in the bond data storage means, discrimination between a name and a name according to the position of space data included in the name data, and / or included in the name data 6. The name data is normalized based on the deletion of the space data, and the normalized Mr data and / or the normalized name data is acquired, according to any one of claims 1 to 5. Address management device. The address normalization means is
Based on the full normalization of the address data included in the bond data stored in the bond data storage means, the deletion of space data included in the address data, and / or the deletion of specific character data included in the address data The address management apparatus according to any one of claims 1 to 6, wherein the address data is normalized to obtain the normalized address data. The divided data generation unit
The position of the break position data included in the normalized address data is specified, and the comparison is performed based on the comparison between the normalized address data divided by the break position data and the hierarchically represented point data included in the point master. The address management device according to any one of claims 1 to 7, wherein the divided address data generated by specifying and dividing the normalized address data for each hierarchy is generated. The division position data is
The character data of a city, a road, a prefecture, a prefecture, a city, a ward, a group, a town, a village, a car, a car, a car or a car, hyphen data, and / or numerical data. Address management device. The specific character data is
8. The address management device according to claim 7, wherein the address management device is alphabetic character data and / or hyphen data. An address management method for causing an address management apparatus comprising a storage unit and a control unit to execute the method.
The storage unit is
Claim data storage means for storing claim data storing claim data including name data and address data of debtor;
Point storage means for storing a point master including point data hierarchically representing point names;
Equipped with
Executed by the control unit,
A name normalization step of normalizing the name data included in the bond data stored in the bond data storage means and acquiring normalized Mr. data and / or normalized name data;
An address normalization step of normalizing the address data included in the bond data stored in the bond data storage means and acquiring normalized address data;
A division data generation step of generating division data by specifying and dividing the normalized address data for each hierarchy based on the point master;
The same specification for identifying the bond data of the same obligee from the bond data stored in the bond data storage means by comparing the divided data, the normalized name data, and / or the normalized Mr. data Step and
An address management method comprising: An address management program for causing an address management apparatus comprising a storage unit and a control unit to execute the program.
The storage unit is
Claim data storage means for storing claim data storing claim data including name data and address data of debtor;
Point storage means for storing a point master including point data hierarchically representing point names;
Equipped with
In the control unit,
A name normalization step of normalizing the name data included in the bond data stored in the bond data storage means and acquiring normalized Mr. data and / or normalized name data;
An address normalization step of normalizing the address data included in the bond data stored in the bond data storage means and acquiring normalized address data;
A division data generation step of generating division data by specifying and dividing the normalized address data for each hierarchy based on the point master;
The same specification for identifying the bond data of the same obligee from the bond data stored in the bond data storage means by comparing the divided data, the normalized name data, and / or the normalized Mr. data Step and
Address management program to run the.

Images