JP2022037332A - Customer information management server, customer information management method, and program - Google Patents

Abstract

To provide a customer information management server configured to periodically manage validity of mobile-phone numbers of customers.SOLUTION: A customer information management server includes: a storage unit which stores customer information and a deletion candidate DB which is personal information of candidate customers to be deleted from the customer information; a telephone number list acquisition unit which acquires a telephone number list indicating telephone numbers of customers who use an application provided by a mobile carrier and are registered on a service for managing the customer information provided in the application; and a customer information maintenance unit which determines, by using the telephone number list, whether a telephone number of a customer registered in the customer information exists in the telephone number list, and causes the deletion candidate DB, when a determination is made that the telephone number of the customer registered in the customer information does not exist in the telephone number list, to store at least the telephone number in the customer information of the customer for whom it has been determined that the telephone number has not existed in the list.SELECTED DRAWING: Figure 6

Description

The present invention relates to a customer information management server, a customer information management method, and a program.

On the Internet, various services such as Internet banking, Internet securities, provision of credit card usage details, and Internet shopping are provided. Customers who use these services must register customer information such as their names and addresses with the businesses that provide each service. This is because, in principle, customer information is stored and managed in the database of the business operator that provides each service.

In this way, when the customer information is managed for each business operator that provides each service, the customer who uses many services must register the customer information for each business operator. Therefore, the procedure becomes very complicated. In particular, when the address changes due to a move, etc., the change in the address registered as customer information must be notified to each business operator. In order to reduce the burden on customers that occurs in such procedures for registering and changing customer information, we collectively accept notifications of changes in customer information registered by multiple businesses, and each of the received information is received. (For example, see Patent Document 1-3).

Japanese Unexamined Patent Publication No. 2002-215844 JP-A-2002-366872 Japanese Unexamined Patent Publication No. 2004-13428

As a service for registering or updating information with a business operator, for example, a mode of using the telephone number of a customer's mobile phone can be considered. When contracting for a mobile phone, the mobile carrier has a contract to use the mobile phone on the condition of strict identity verification, so confirm the validity of the customer's mobile phone through the mobile carrier. It can be expected that the certainty of the identity verification of the customer will be guaranteed. However, the phone number may be canceled. Therefore, there is a need for a mechanism for regularly managing and maintaining whether the telephone number of the customer's mobile phone is valid.

The present invention has been made in view of such a situation, and is a customer information management server capable of periodically managing whether or not a customer's mobile phone telephone number is valid, a customer information management method, and a customer information management method. The purpose is to provide a program.

In order to solve the above-mentioned problems of the present invention, the present invention is a customer information management server that manages customer information, which is customer's personal information, based on the information notified from the customer terminal. , A storage unit that stores a deletion candidate DB that is personal information of a customer who is a candidate to be deleted from the customer information, and a customer who uses an application provided by a mobile carrier and provides the customer information provided in the application. Using the phone number list acquisition unit that acquires a phone number list indicating the customer's phone number registered in the service to be managed and the phone number list, the customer's phone number registered in the customer information is the phone number list. If it is determined whether or not the customer's telephone number registered in the customer information does not exist in the telephone number list, at least one of the customer information of the customer determined to be nonexistent is telephone. It is a customer information management server including a customer information maintenance unit that stores numbers in a deletion candidate DB.

Further, in the above-mentioned customer information management server, the present invention determines that the customer information maintenance unit does not exist when the customer information maintenance unit determines that the customer's telephone number registered in the customer information does not exist in the telephone number list. The customer information of the customer may be deleted.

Further, according to the present invention, in the above-mentioned customer information management server, the telephone number list acquisition unit periodically acquires the telephone number list, and the customer information maintenance unit exists in the telephone number list acquired this time. Moreover, it is determined whether or not the resurrected telephone number registered in the deletion candidate DB exists, and if the resurrected telephone number exists, the resurrected telephone number registered in the deletion candidate DB is deleted. Delete from the candidate DB.

Further, in the above-mentioned customer information management server, the present invention periodically acquires the telephone number list by the telephone number list acquisition unit, and the customer information maintenance unit periodically acquires the telephone number list of the customer registered in the customer information. When it is determined whether or not the number exists in the telephone number list and it is determined that the telephone number of the customer registered in the customer information does not exist in the telephone number list, the customer of the customer who determines that the number does not exist. When the information is stored in the deletion candidate DB and it is determined that the telephone number of the customer registered in the customer information does not exist in the telephone number list, the customer information of the customer determined not to exist is deleted and the customer is deleted. Based on the telephone number list acquired after the time when the information is stored in the deletion candidate DB, whether or not there is a resurrection candidate telephone number that exists in the telephone number list and is not registered in the customer information. When the determination is made and the revival candidate telephone number is registered in the deletion candidate DB, the customer information stored in the deletion candidate DB is restored, and the restored customer information is transferred from the deletion candidate DB. delete.

Further, the present invention is a customer information management server that manages customer information, which is customer's personal information, based on the information notified from the customer terminal, and is a candidate for deletion from the customer information and the customer information. A storage unit that stores a deletion candidate DB that is a customer's personal information. A customer information management method for a customer information management server, and a telephone number list acquisition unit is a customer who uses an application provided by a mobile carrier. The customer information maintenance department obtains a phone number list indicating the customer's phone number registered in the service for managing the customer information provided in the above, and the customer information maintenance department uses the phone number list to obtain the customer registered in the customer information. If it is determined whether or not the telephone number of the customer exists in the telephone number list, and if it is determined that the telephone number of the customer registered in the customer information does not exist in the telephone number list, the customer who determines that the telephone number does not exist is determined. This is a customer information management method in which at least a telephone number of the customer information is stored in a deletion candidate DB.

Further, the present invention is a program for operating the computer as the customer information management server described above, and is a program for operating the computer as each part included in the customer information management server.

According to the present invention, it is possible to periodically manage whether the telephone number of the customer's mobile phone is valid.

It is a schematic diagram which shows the example of the structure of the management system 1 to which the customer information management server 10 which concerns on 1st Embodiment is applied. It is a block diagram which shows the example of the structure of the customer information management server 10 which concerns on 1st Embodiment. It is a figure explaining the process in the management system which concerns on 1st Embodiment. It is a flowchart which shows the flow of the process performed by the customer information management server 10 which concerns on 1st Embodiment. It is a flowchart which shows the flow of the process performed by the customer information management server 10 which concerns on 1st Embodiment. It is a schematic diagram which shows the example of the configuration of the management system 1 to which the customer information management server 100 which concerns on 2nd Embodiment is applied. It is a figure which shows the example of the structure of the customer information 131 which concerns on 2nd Embodiment. It is a figure which shows the example of the structure of the registration DB 132 which concerns on 2nd Embodiment. It is a figure which shows the example of the structure of the deletion candidate DB 133 which concerns on 2nd Embodiment. It is a flowchart which shows the flow of the process performed by the customer information management server 100 which concerns on 2nd Embodiment.

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

FIG. 1 shows an outline of a management system 1 to which the customer information management server 10 according to the first embodiment is applied. As shown in FIG. 1, the customer information management server 10 is accessiblely connected from a customer terminal 20 such as a smartphone via a communication network NW such as the Internet. Further, the customer information management server 10 is accessiblely connected to and the user institution system 50 (in this example, the A bank system, the B bank system, the C securities system, the D life system, and the like).

A customer of a user institution system 50 such as a bank or a securities company uses an application program such as a message application (interactive messenger is preferable) provided by a mobile carrier (mobile phone operator) on the customer terminal 20 to provide a mobile carrier server. Connect to 30. In this case, information indicating a menu or a link selected when requesting registration or update of customer information having a common procedure is displayed on a predetermined page such as a chat room of the application program displayed on the customer terminal 20. Is shown. The customer selects those menus and performs an operation to send data such as identity verification documents and account information necessary for registration and renewal. Then, the customer information management server 10 is notified of the data transmitted from the customer terminal 20. The customer information management server 10 makes an inquiry to, for example, an integrated ATM network (not shown) based on the data notified from the customer terminal 20. The integrated ATM network here is a network that interconnects ATMs and the like between banks. By inquiring to this network, it is possible to confirm the existence and validity of the deposit account. The customer information management server 10 performs predetermined confirmation processing such as identity confirmation and account confirmation by using the integrated ATM network.

When these confirmation processes are completed, the customer information management server 10 registers or updates the customer information managed by the customer information management server 10. Further, the customer information management server 10 obtains the consent of the customer himself / herself, and then, with the consent of the customer himself / herself, the information necessary for registering or updating the customer information associated with the account or the like in the user institution system 50 in the user institution system 50 to which the customer is related. To send. The user institution system 50 processes the registration or update of the customer information in the user institution system 50 after approval based on the information received from the customer information management server 10, and when the processing is completed, the customer terminal 20 receives the customer information. Notify that the registration or renewal process is complete.

As described above, in the first embodiment, the customer terminal 20 is requested to register or update the customer information by using the application program such as the message application provided by the mobile carrier. That is, the application program provided by the mobile carrier that the customer uses on a daily basis is used as an interface to request registration or update of customer information. Therefore, it is possible to improve the operability of the customer when registering or updating the customer information. Further, in the present embodiment, the request for registration or update of customer information is received after the authentication by the mobile carrier via the mobile carrier server 30. Mobile carriers have signed contracts to use mobile phones on the condition of strict identity verification. Therefore, in the management of customer information by the customer information management server 10 of the present embodiment, the certainty of the identity verification of the customer is guaranteed. In cases where a child uses a mobile phone purchased by a parent, the certainty of the identity verification may not be guaranteed only by the identity verification of the carrier at the time of the mobile contract.

FIG. 2 is a block diagram showing an example of the configuration of the customer information management server 10 according to the first embodiment. As shown in FIG. 2, the customer information management server 10 is connected to the customer terminal 20 and the mobile carrier server 30 via a general-purpose or dedicated network or the like.

As the customer information management server 10, a computer having an auxiliary storage device such as a CPU, a main memory, and an HDD and having a connection function with a communication network NW including the Internet is used. Various functions included in the customer information management server 10 are realized by reading a program stored in the auxiliary storage device into the main memory and executing arithmetic processing in the CPU.

The physical configuration of the computer constituting the customer information management server 10 is not particularly limited. Functions other than the customer information management function in the present embodiment may be provided in the same computer or may be provided in separate computers. Further, the various functions required for the present embodiment may be physically realized by one computer or may be realized by using a plurality of computers.

Each functional unit such as the one-time URL generation unit 11 of the customer information management server 10, the customer information processing unit 13, the identity verification unit 14, the account confirmation unit 15, the customer information provision unit 17, and the notification transmission unit 18 is limited as a function. Is to be done. Each functional unit of the customer information management server 10 is realized by, for example, a CPU executing a program (software) for arithmetic processing, but is not limited to this, and is realized by hardware such as an LSI. It may be realized by the collaboration of software and hardware.

A predetermined storage area of an auxiliary storage device such as an HDD is allocated to the one-time URL storage unit 12 and the customer information storage unit 16 of the customer information management server 10. These storage areas are not required to be physically provided in one computer, but may be provided in a plurality of computers such as a computer constituting a database server.

As the customer terminal 20, a mobile terminal such as a smartphone to which a telephone number is assigned is used. The customer terminal 20 can use the application program provided by the mobile carrier. The application program has a function of authenticating the caller's telephone number and communicating with the customer terminal 20. The contractor information storage unit 31 of the mobile carrier server 30 is assigned a predetermined storage area of an auxiliary storage device such as an HDD of a computer corresponding to the mobile carrier server 30.

In the user institution system 50-52 or the like, for example, a host computer that manages a deposit account operated by a bank can be used. In the following, a case where information transmission / reception with the customer information management server 10 directly communicates with a core computer system such as a user institution system 50 will be described as an example. However, it is not limited to this. The customer information management server 10 may send and receive information via a network terminal such as a PC or a Web server capable of communicating with such a core computer system.

On the premise of the above configuration, a method of managing customer information by the customer information management server 10 in the first embodiment will be described with reference to FIGS. 3 to 5.

FIG. 3 shows a customer information management server 10 and peripheral external devices (customer terminal 20, mobile carrier server 30, and user institution system 50) when customer information is registered or updated in the first embodiment. The relationship between the above and the outline of the data flow inside the customer information management server 10 are shown.

As shown in FIG. 3, for example, the customer performs an operation of activating the message application provided by the mobile carrier using the customer terminal 20. The customer uses the service provided by the customer information management server 10 to obtain customer information requested by a plurality of businesses (here, Bank A, Bank B, Securities C, Life D, etc.) that have transactions with the customer. In order to register and update (customer's personal information) all at once, perform the operation to start the message application. In this case, the customer operates by using the customer terminal 20 such as a smartphone to which he / she is a contractor and is assigned a telephone number.

This message application is an application program provided by a mobile carrier authenticated by a caller's telephone number, and is installed in a customer terminal 20. When the message application is started on the customer terminal 20, a request to start the application program is transmitted to the mobile carrier server 30. Upon receiving the activation request, the mobile carrier server 30 authenticates the telephone number. In the telephone number authentication here, the caller's telephone number (the telephone number read from the SIM card inserted in the customer terminal 20) is stored in the contractor information storage unit 31, which is a database of mobile phone contractors. The process of matching with the stored valid phone number is performed. When the caller's telephone number is a valid telephone number stored in the contractor information storage unit 31, the mobile carrier server 30 determines that a legitimate activation request from the contractor has been received. When the mobile carrier server 30 receives a legitimate activation request from the contractor, the mobile carrier server 30 permits the customer terminal 20 to activate the message application.

As illustrated in FIG. 3, a list of menus including "account information registration" and "address change" is displayed on the operation screen of the message application of the customer terminal 20. These menus are services provided by the customer information management server 10. When either "account information registration" or "address change" is selected from these menus, the mobile carrier server 30 performs "account information registration" together with the telephone number of the customer terminal 20 authenticated earlier. The customer information management server 10 is notified that a menu such as "Change address" or "Change address" has been selected.

Here, the case where the customer's telephone number is notified from the mobile carrier server 30 to the customer information management server 10 has been described as an example, but the present invention is not limited to this. The information notified from the mobile carrier server 30 to the customer information management server 10 may be at least information that can identify the customer who operates the customer terminal 20. For example, instead of the customer's telephone number, an identification key such as a customer ID uniquely associated with the telephone number may be notified from the mobile carrier server 30 to the customer information management server 10. Alternatively, the mobile carrier server 30 notifies the customer information management server 10 of the customer's telephone number, and the customer information management server 10 associates the customer ID and other identification keys uniquely associated with the telephone number with the identification key. The key may be used to manage customer information. In consideration of security, it may be preferable to use an identification key such as a customer ID uniquely associated with the telephone number instead of using the telephone number itself.

The flowchart of FIG. 4 shows a flow of processing related to registration or update of customer information performed by the customer information management server 10 according to the first embodiment. As shown in FIG. 4, the customer information management server 10 receives a customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) from the mobile carrier server 30 (step S01). The customer information management server 10 receives the customer's telephone number and the like together with the information that "account information registration", "address change" and the like are selected in the menu of the message application on the customer terminal 20. Next, in the customer information management server 10, the one-time URL generation unit 11 is started, and the one-time URL is generated (step S02). The one-time URL is a unique network address assigned to the page that the customer accesses when registering or updating his / her customer information.

The one-time URL generated by the one-time URL generation unit 11 is associated with the customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) received from the mobile carrier server 30, and is one-time. It is temporarily stored in the time URL storage unit 12 (step S03). Further, the customer information management server 10 transmits the one-time URL generated by the one-time URL generation unit 11 to the mobile carrier server 30 (step S04).

When the mobile carrier server 30 receives the one-time URL from the customer information management server 10, it generates a registration / update button in which a link in which the received one-time URL is embedded is set (see FIG. 3). The registration / update button is an operation button provided in the file of the operation screen displayed on the message application activated by the customer terminal 20. The mobile carrier server 30 transmits a file of the operation screen provided with the operation buttons to the customer terminal 20. The customer terminal 20 receives the file of the operation screen and displays the received file on the screen. As a result, on the screen of the customer terminal 20, a button for requesting registration or update of customer information, in which a link to a one-time URL is set, is displayed. The method of setting a link to the one-time URL on the operation screen displayed on the message application is not limited to the method of displaying the operation button on the screen and causing the customer to press the operation. It may be in a display format other than the operation buttons, such as setting a hyperlink in the text.

The customer visually recognizes the screen displayed on the customer terminal 20 and performs an operation as necessary. For example, consider a case where a customer uses a service provided by the customer information management server 10 to register or update customer information of the customer himself / herself, which is shared by a plurality of usage periods. In this case, depending on the customer, data such as identity verification documents required for identity verification (“identification data” in FIG. 3) and customer's own information to be registered or updated (“registration / update data” in FIG. 3”. ) Is entered. When the data is input, the operation button for requesting the registration or update of the customer information displayed on the operation screen is pressed.

When the operation button is pressed by the customer, the customer terminal 20 transmits a registration or update request for customer information including identity verification data and registration / update data to the customer information management server 10. A link to a one-time URL is set on the operation button. Therefore, a request for which a one-time URL is specified as an address is transmitted to the customer information management server 10. A link to the one-time URL is not set for the image or the like displayed on the screen displayed after the operation buttons such as "account information registration" and "address change" are selected in the menu of the message application.

The customer information management server 10 receives a request in which a one-time URL is specified as an address. Upon receiving this request, the customer information management server 10 activates the customer information processing unit 13 and executes the process shown in the flowchart of FIG. The flowchart of FIG. 5 shows a flow of processing related to registration or update of customer information performed by the customer information management server 10 according to the first embodiment. The customer information management server 10 receives the update request and the data associated with the update request (step S11). The update request here is a notification that the one-time URL requests the registration or update of the customer information specified in the address. The data associated with the update request here are identity verification data and registration / update data. The customer information management server 10 confirms the information temporarily stored in the one-time URL storage unit 12, and the customer's telephone number (or telephone number) stored in association with the one-time URL specified in the request. The uniquely associated identification key such as the customer ID) is specified (step S12).

The identity verification unit 14 confirms the identity of the customer from the identity verification data or the like received from the customer terminal 20 (step S13), and confirms whether or not it corresponds to spoofing (step S14). The account confirmation unit 15 confirms the existence and validity of the deposit account, if necessary (step S15). When it is confirmed by these confirmations that the predetermined requirements for registration or renewal are satisfied (Yes in all steps S13-S15), the customer information processing unit 13 is stored in the customer information storage unit 16. Of the customer information, the customer information of the customer identified by the telephone number (or the identification key such as the customer ID uniquely associated with the telephone number) specified in step S12 is the customer information received from the customer terminal 20. Update based on the registration / update data included in the registration or update request (step S16).

The customer information management server 10 starts the customer information providing unit 17. The customer information providing unit 17 has a transaction with a customer whose customer information has been registered or updated, and the customer's consent or instruction is given to a user institution system 50-52 or the like that requires the registered or updated customer information. Then, the registered or updated customer information is transmitted together with other necessary information such as an image file of an identity verification document (step S17). After that, the customer information management server 10 activates the notification transmission unit 18 after waiting for approval by the destination user system 50-52 or the like and confirming that the approval has been obtained. The notification transmission unit 18 transmits a notification in which customer information is registered or updated to the customer terminal 20.

In the identity verification unit 14 confirms the customer's identity (step S13), confirms whether the customer does not correspond to spoofing (step S14), or confirms the existence and validity of the deposit account in the account confirmation unit 15 (step S15). If it is confirmed that any of the requirements is not satisfied (one of steps S13 to S15 is No), the registration or update process of the customer information is not accepted and the error process is performed (step S18).

(Second embodiment)
Next, the second embodiment will be described. The customer information management server 100 of the present embodiment is different from the above-described embodiment in that the customer information is maintained. In the following description, the same components as those of the customer information management server 10 of the above-described embodiment are designated by the same reference numerals, and the description thereof will be omitted. Further, when the customer information management server 10 and the customer information management server 100 are not particularly distinguished, the customer information management server 10 (100) or the like is described.

As described above, in the present embodiment, the customer information management server 10 (100) registers or updates customer information based on the telephone number (or the identification key such as the customer ID uniquely associated with the telephone number). I do. When the customer information management server 100 of the present embodiment stores (registers or updates) the attribute information of the customer in the customer information 131 in accordance with the registration or update of the customer information, the customer's telephone number is also stored in the registration DB 132. Remember.

However, the phone number may be canceled. In this case, the telephone number not belonging to the customer himself / herself will continue to be registered in the customer information of the customer information management server 10. Further, when the telephone number is canceled, the canceled telephone number is generally assigned to the telephone number of another person's smartphone or the like after a predetermined period has elapsed after the cancellation. Therefore, the customer's telephone number may be canceled and the canceled number may be assigned to another person. In this case, in the customer information of the customer information management server 10, the telephone number of one customer (the one that has already been canceled but the renewal procedure has been neglected) and the telephone number of another customer (the one newly contracted) are the same. There is a possibility that it will be registered as a number. In this case, there is a possibility that the customer information management server 10 may erroneously transmit the customer information of a certain customer as the customer information of another customer to the user institution systems 50-52 and the like. be.

As a countermeasure, in the present embodiment, maintenance-related processing is performed by periodically checking whether the customer's telephone number is the latest.

FIG. 6 is a diagram illustrating a process related to maintenance performed by the customer information management server 100 of the second embodiment. As shown in FIG. 6, the customer information management server 100 receives customer information from the customer terminal 20. The customer information received here is information notified from the customer terminal 20 of the customer who requests the registration or update of the customer information by operating the menu or the like of the message application by the customer.

Further, the customer information management server 100 stores the customer information received from the customer terminal 20 in the storage unit 130 as the customer information 131. Further, the customer information management server 100 transmits the registered or updated customer information or the like to the user institution system 50 together with the telephone number (or identification key) received from the customer terminal 20.

The customer information management server 100 periodically (for example, once a day) requests the mobile carrier server 30 to receive the telephone number list by the telephone number list acquisition unit 110. The telephone number list is a list showing the telephone numbers of customers who have contracted with a mobile carrier and are using services such as "account information registration" on a predetermined message application (hereinafter referred to as customer information management service). The predetermined message application here is a message application corresponding to the customer information management service provided by the customer information management server 10. For example, the customer terminal 20 can use the customer information management service by following the account of the customer information management server 10 that provides the customer information management service in a predetermined message application.

Then, the customer information management server 10 performs a process related to the maintenance of the customer information by the customer information maintenance unit 120 using the telephone number list. The processing related to the maintenance performed by the customer information maintenance unit 120 will be described in detail later.

The customer terminal 20 notifies the mobile carrier server 30 of the telephone number via a message application or the like. Further, the customer terminal 20 notifies the customer information management server 100 of the customer information by operating the operation button for registering or updating the customer information displayed on the menu or the like of the message application. The mobile carrier server 30 transmits a telephone number list to the customer information management server 100 in response to a request from the customer information management server 10.

As described above, the telephone number list is a list showing the telephone numbers of customers who have contracted with a mobile carrier and are using a predetermined message application. Therefore, when the customer cancels the mobile phone, the canceled telephone number does not exist in the telephone number list notified after the cancellation. In the present embodiment, this property is used to perform processing related to maintenance of customer information. For example, the customer information management server 100 may delete a telephone number that no longer exists in the telephone number list from the customer information.

However, mobile phone numbers have a system called Mobile Number Portability (hereinafter referred to as MNP). With MNP, it is not necessary to change the mobile phone number even if the mobile carrier is changed.

Some of the phone numbers that no longer exist in the phone number list are due to the cancellation of the phone, or due to the fact that the customer information management service on the specified message application is no longer used (unfollowed). It is considered that there are some that are caused by the change of the mobile carrier due to MNP. Therefore, if a phone number that no longer exists in the phone number list is immediately deleted from the customer information, the phone number of the customer who no longer uses the customer information management service or the customer who has changed the mobile carrier by MNP. However, even though the phone number has not changed, it will be deleted.

As a countermeasure, in the present embodiment, the customer information management server 100 stores the customer information 131, the registration DB 132, and the deletion candidate DB 133 in the storage unit 130 when performing the processing related to the maintenance. The customer information 131 is the personal information of the customer himself / herself. The registration DB 132 is information indicating a customer's telephone number registered in the customer information 131. The registration DB 132 is used for maintaining the customer information 131. The deletion candidate DB 133 is information about a customer whose telephone number registered in the customer information 131 may be deleted for some reason.

In this way, by registering the telephone number that may be deleted later in the deletion candidate DB 133, the telephone number that no longer exists in the telephone number list is a predetermined one caused by the cancellation of the telephone. It is possible to determine whether it is caused by not using the customer information management service on the message application (unfollowing) or by changing the mobile carrier by MNP. For example, the deletion candidate DB 133 is monitored regularly, and a certain period (for example, a period such as one week or one month is considered) has elapsed from the deletion date (the day when the telephone number no longer exists in the telephone number list). It is possible to perform a process such as deleting the customer information 131 corresponding to the telephone number.

FIG. 7 is a diagram showing an example of the configuration of the customer information 131 according to the second embodiment. The customer information 131 includes, for example, an identification key and items such as attribute information. The identification key is identification information that identifies the customer uniquely associated with the telephone number. The attribute information is information indicating the attributes of the customer, and is composed of the customer information notified from the customer terminal 20 and the customer's telephone number notified from the mobile carrier server 30. The attribute information includes items such as a name, an address, a date of birth, a telephone number, an individual number, a driver's license number, and an account number.

In this example, as attribute information, it is shown that the name is TF Taro, the address is Chiyoda-ku, Tokyo, the date of birth is August 14, 1991, and the telephone number is 090-1234-5678. In this example, there is an item of My Number as attribute information. As described above, the customer information management server 10 may have a configuration in which the customer's My Number can be registered in the customer information 131. This is because there is an increasing momentum to link bank account information to My Number Card.

In other words, a bill linking My Number Card and bank account information is being put in place. When it is obligatory to link the bank account information to the My Number card, the My Number needs to be stored in the customer information held by the user institution system 50 (mainly the bank). In this case, for example, when the customer information is registered via the customer information management server 100, the customer information management server 100 requests the provision of the customer's My Number as registration / update data, and receives the customer information from the customer terminal 20. Notify the user institution system 50 of my number as customer information.

On the other hand, even if it is obligatory to link the bank account information to the Individual Number Card, it may be prohibited for a third party other than the bank to hold the Individual Number. In such a case, the customer's My Number cannot be registered in the customer information 131. In this case, the customer information management server 100, for example, notifies the user institution system 50 of the My Number based on the personal information received from the customer terminal 20, and then uses the customer information excluding the My Number as the customer information. Make it memorize in 131.

FIG. 8 is a diagram showing an example of the configuration of the registration DB 132 according to the second embodiment. The registration DB 132 includes items such as an identification key, a telephone number, an addition date, and an update date. The identification key is the same as the identification key in the customer information 131. The telephone number is a telephone number associated with the identification key. The addition date is the date on which the customer's attribute information and the like are added. The update date is the date on which the customer's attribute information and the like are updated. The addition date and update date may be set for each attribute information.

FIG. 9 is a diagram showing an example of the configuration of the deletion candidate DB 133 according to the second embodiment. The deletion candidate DB 133 includes items such as an identification key, a telephone number, and a deletion date. The identification key is the same as the identification key in the customer information 131. The telephone number is a telephone number associated with the identification key. The deletion date is the date on which the customer information corresponding to the identification key is deleted from the customer information 131 when the telephone number that no longer exists in the telephone number list is immediately deleted from the customer information 131. Alternatively, if a telephone number that no longer exists in the telephone number list is registered in the deletion candidate DB 133 without being immediately deleted from the customer information 131, and the telephone number is retained in the customer information 131 for a certain period of time, the deletion date Is the date when the customer information corresponding to the identification key no longer exists in the phone number list.

Here, the processing related to the maintenance performed by the customer information management server 100 will be described with reference to FIG. FIG. 10 is a flowchart showing a flow of processing related to maintenance of customer information performed by the customer information management server 100 of the second embodiment.

The customer information management server 100 acquires a telephone number list from the mobile carrier server 30 (step S20). The customer information management server 100 compares the acquired telephone number list with the registration DB 132 stored in the customer information management server 10 (step S21).

As a result of comparison, if the telephone number exists in the telephone number list and also exists in the registration DB 132, the customer information management server 100 updates the registration DB 132 assuming that the telephone number is valid (step). S22). The update here is to update that the information stored in the registration DB 132 is confirmed to be the latest, and for example, to update the update date of the registration DB 132. That is, there is no change in the contents of the telephone number of the registration DB 132.

As a result of comparison, the customer information management server 100 deletes the telephone number from the registration DB 132 when the telephone number does not exist in the telephone number list but exists in the registration DB 132 (step S23). Further, the customer information management server 100 adds the telephone number deleted from the registration DB 132 to the deletion candidate DB 133 (step S24).

As a result of comparison, the customer information management server 100 determines whether or not the telephone number exists in the deletion candidate DB 133 when the telephone number exists in the telephone number list but does not exist in the registration DB 132 (as a result of comparison). Step S25).

If the telephone number does not exist in the deletion candidate DB 133, the customer information management server 100 adds the telephone number to the registration DB 132 (step S26). The addition here means that new information is added to the registration DB 132 (new registration). Alternatively, if the telephone number has a record of being registered in the customer information 131 in the past (deleted thereafter), the addition here is a revival after the deletion. On the other hand, when the telephone number exists in the deletion candidate DB 133, the customer information management server 100 deletes the telephone number from the deletion candidate DB 133 (step S27). Then, the customer information management server 100 adds the telephone number deleted from the deletion candidate DB 133 to the registration DB 132 (step S28). The addition here is to add the information deleted in step S23 to the registration DB 132 again (revival registration).

In the above, the case where the customer information 131 and the registration DB 132 are managed as separate databases has been described as an example. However, it is not limited to this. The customer information 131 and the registration DB 132 may be one integrated database. In this case, the customer information 131 also serves as the registration DB 132. In this case, the deletion candidate DB 133 includes the same items as the attribute information (address, name, etc.) of the customer (deletion candidate) in the customer information 131. Further, the customer information management server 10 may be configured to include one integrated database for storing information including the deletion candidate DB 133 in the customer information 131 and the registration DB 132. In this case, the integrated database contains an entry for the delete flag. The deletion flag is information indicating whether or not it is a deletion candidate. This makes it possible for the integrated database to manage customer phone numbers using the delete flag. In this case, the integrated database is an example of "customer information", an example of "registration DB", and an example of "deletion candidate DB".

In this case, for example, the customer information management server 100 compares the telephone number list with the customer information 131 in step S21. In step S22, the customer information management server 100 registers a telephone number that exists in the telephone number list and does not exist in the customer information 131 in the customer information 131. In step S24, if there is a telephone number that does not exist in the telephone number list but exists in the customer information 131, the customer information management server 100 adds the telephone number to the deletion candidate DB 133. In this case, the customer information management server 100 also stores the customer attribute information (address, name, etc.) associated with the telephone number in the deletion candidate DB 133.

Further, the customer information management server 100 may immediately delete the telephone number added to the deletion candidate DB 133 from the customer information 131, or may not delete it immediately. In this case, the customer information management server 100 deletes the telephone number from the customer information 131 when the telephone number exists in the deletion candidate DB 133 after a certain period of time (for example, one week or one month). You may do so.

If the customer information management server 100 determines in step S26 that the telephone number does not exist in the deletion candidate DB 133 in the process of step S25, the telephone number newly provides the customer information management service on the predetermined message application. It is registered in the customer information 131 as the telephone number of the customer terminal 20 used (followed).

On the other hand, in the customer information management server 100, in step S26, in the process of step S27, the telephone number exists in the deletion candidate DB 133, and when the telephone number is deleted from the deletion candidate DB 133, the telephone number is changed to. It is regarded as the telephone number of the customer terminal 20 that has started (followed again) the customer information management service on the predetermined message application again. In this case, since the telephone number is already registered in the customer information 131, the process of registering the telephone number in the customer information 131 is not performed.

As described above, the customer information management server 100 of the second embodiment manages the customer information 131, which is the personal information of the customer, based on the information notified from the customer terminal 20. The customer information management server 100 includes a telephone number list acquisition unit 110, a customer information maintenance unit 120, and a storage unit 130. The storage unit 130 stores the customer information 131 and the deletion candidate DB 133. The telephone number list acquisition unit 110 is a customer who uses an application provided by a mobile carrier and is registered in a service for managing customer information 131 provided in the application (that is, a customer information management service). Get a list of phone numbers showing numbers. The customer information maintenance unit 120 uses the telephone number list to determine whether or not the customer's telephone number registered in the customer information 131 exists in the telephone number list, and the customer's telephone number registered in the customer information 131. When it is determined that the telephone number does not exist in the telephone number list, at least the telephone number of the customer information 131 of the customer determined to not exist is stored in the deletion candidate DB 133 as the personal information of the customer who is the candidate for deletion. In this case, when the customer information management server 100 determines that the customer's telephone number registered in the customer information 131 does not exist in the telephone number list, the customer information management server 100 deletes the customer's customer information 131 determined to not exist. You may.

As a result, in the customer information management server 100 of the second embodiment, the telephone number of the customer already registered in the customer information 131 is not registered in the customer information management service (for example, the telephone number has been changed or the telephone number has been changed). When the account is temporarily unfollowed), the phone number can be added to the deletion candidate DB 133. This allows you to monitor subsequent outcomes, taking into account the possibility that the customer's phone number has changed. Therefore, the customer information management server 100 of the second embodiment can periodically manage whether or not the telephone number of the customer's mobile phone is valid. For example, it is possible to suppress a situation in which erroneous customer information is notified to the user institution system 50, and to maintain a state in which the customer information 131 can be deleted according to the subsequent consequences of the deletion candidate. That is, if the MNP changes the mobile carrier that the customer contracts with, but later does not change the customer's mobile phone number, or if it turns out that the account was temporarily unfollowed but then followed again. The customer information 131 can be maintained. On the other hand, the customer information 131 of the customer can be deleted when it is highly probable that the mobile phone number of the customer has been changed, such as when the telephone number does not return to the telephone number list even after the lapse of a predetermined period.

Further, in the customer information management server 100 of the second embodiment, the telephone number list acquisition unit 110 periodically acquires the (latest) telephone number list. The customer information maintenance unit 120 determines whether or not a telephone number (recovery telephone number) that exists in the telephone number list acquired this time and is registered in the deletion candidate DB 133 exists. If the corresponding telephone number exists, the customer information maintenance unit 120 deletes the telephone number registered in the deletion candidate DB 133 from the deletion candidate DB 133 if the telephone number is registered in the deletion candidate DB 133. do. As a result, in the customer information management server 100 of the second embodiment, it is suspected that the customer's mobile phone may have been changed, but when it is later found that the customer's mobile phone number has not changed, Customer information 131 can be maintained. As a result, it is possible to suppress a time-consuming process such as re-registering immediately after deleting the customer information 131 of the customer.

The customer information management server 10 confirms that the customer's telephone number has been canceled based on the telephone number list even when the customer information management server 10 does not receive the customer information registration or update request notification from the customer terminal 20. If so, the user institution system 50 corresponding to the bank may be notified to that effect. As a result, the bank side can also confirm that the customer's telephone number has been canceled and update the customer information in the user institution system 50.

In addition, in at least one embodiment described above, the case where the information of the customer who followed the account of the customer information management service is registered in the customer information 131 has been described as an example. However, strictly speaking, when the account of the customer information management service is followed, the customer's telephone number is registered only in the registration DB 132, and the customer information 131 is not registered. This is because when the account follows, only the customer's mobile phone number is notified to the customer information management server 10 via the mobile carrier server 30.

The customer information management service is a service provided on an application provided by a mobile carrier. Therefore, when the account of the customer information management service is followed, the mobile carrier server 30 can recognize it. Then, the customer information management server 10, which is the provider of the customer information management service, periodically makes an inquiry to the mobile carrier server 30, and acquires the telephone number of the customer who follows the account of the customer information management service. The customer information management server 10 creates a customer registration DB 132 based on the acquired telephone number.

Then, when the customer who follows the account of the customer information management service registers the use of the customer information management service, the customer information management server 10 is notified of the customer's name and the like entered in the process of the usage registration. The customer information management server 10 creates customer customer information 131 based on the notified customer name and the like.

The customer information management server 10 (100) in the above-described embodiment may be fully or partially realized by a computer. In that case, a program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by a computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, and a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" is a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short period of time. It may also include a program that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or a client in that case. Further, the above program may be for realizing a part of the above-mentioned functions, and may be further realized for realizing the above-mentioned functions in combination with a program already recorded in the computer system. It may be realized by using a programmable logic device such as FPGA.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs and the like within a range that does not deviate from the gist of the present invention.

1 ... Management system 10, 100 ... Customer information management server 20 ... Customer terminal 30 ... Mobile carrier server 50 ... User institution system 110 ... Phone number list acquisition unit 120 ... Customer information maintenance department 130 ... Storage unit 131 ... Customer information 132 ... Registration DB
133 ... Deletion candidate DB

Claims (5)

A customer information management server that manages customer information, which is customer's personal information, based on the information notified from the customer terminal.
A storage unit that stores the customer information, a deletion candidate DB that is personal information of a customer who is a candidate to be deleted from the customer information, and a storage unit.
A telephone number list acquisition unit that acquires a telephone number list indicating the telephone numbers of customers who use an application provided by a mobile carrier and is registered in the service for managing the customer information provided in the application.
Using the telephone number list, it is determined whether or not the telephone number of the customer registered in the customer information exists in the telephone number list, and the telephone number of the customer registered in the customer information is the telephone number list. When it is determined that it does not exist in, the customer information maintenance unit that stores at least the telephone number of the customer information of the customer determined to be nonexistent in the deletion candidate DB, and
Customer information management server. When the customer information maintenance unit determines that the telephone number of the customer registered in the customer information does not exist in the telephone number list, the customer information maintenance unit deletes the customer information of the customer who has determined that the telephone number does not exist.
The customer information management server according to claim 1. The telephone number list acquisition unit periodically acquires the telephone number list and obtains the telephone number list.
The customer information maintenance unit determines whether or not there is a restored telephone number that exists in the telephone number list acquired this time and is registered in the deletion candidate DB, and if the restored telephone number exists, the customer information maintenance unit determines whether or not the restored telephone number exists. , The revival telephone number registered in the deletion candidate DB is deleted from the deletion candidate DB.
The customer information management server according to claim 1 or 2. It is a customer information management server that manages customer information that is customer's personal information based on the information notified from the customer terminal, and is the customer information and the personal information of a customer that is a candidate to be deleted from the customer information. It is a customer information management method of a customer information management server provided with a storage unit for storing a deletion candidate DB.
The telephone number list acquisition unit acquires a telephone number list indicating the telephone number of a customer who uses an application provided by a mobile carrier and is registered in the service for managing the customer information provided by the application. ,
The customer information maintenance unit uses the telephone number list to determine whether or not the telephone number of the customer registered in the customer information exists in the telephone number list, and the telephone of the customer registered in the customer information. When it is determined that the number does not exist in the telephone number list, at least the telephone number of the customer information of the customer determined to not exist is stored in the deletion candidate DB.
Customer information management method. A program for operating a computer as the customer information management server according to any one of claims 1 to 3, and for operating the computer as each part included in the customer information management server.

Images