JP7662992B2 - Information management server, information management method, and program - Google Patents

Description

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

When moving, people need to individually notify various government agencies and private businesses of their name, new address, and other information, which creates a burden for them each time they move. Furthermore, the procedures required vary from person to person, and there are a wide variety of parties to whom procedures must be carried out. For this reason, people are unable to grasp the full picture of the necessary procedures, and they are prone to missing out on procedures.

In response to these problems, services are being promoted to reduce the burden of procedures associated with moving and to prevent oversight of procedures. Such services provide, for example, a portal site that serves as a one-stop window for procedures associated with moving with government agencies (local governments) and private businesses. By registering information such as their name and new address on the portal site, users can complete procedures associated with moving online with government agencies and private businesses in one go via the portal site. For example, Patent Document 1 discloses a technology that accepts notifications of changes to user information such as name and address registered with multiple businesses, such as government agencies and private businesses, in one go, and provides the accepted information to each business.

JP 2002-215844 A

In these types of services, registration is handled based on personal information, such as mobile phone numbers, entered by users via a portal site. However, in this case, there is a high likelihood of errors in the mobile phone number due to input errors, etc., and there is a problem that if the entered mobile phone number is used as is, there is a possibility that the correct procedure will not be carried out.

The present invention was made in consideration of such circumstances, and aims to provide an information management server, an information management method, and a program that can check whether there are any errors in the mobile phone number applied for by the user.

In order to solve the above-mentioned problems of the present invention, the present invention is an information management server that includes a number determination unit that obtains a message notified from a user terminal of a user who has requested a procedure using a calling application addressed to a mobile phone number, and determines that the user's mobile phone number is correct if the mobile phone number applied for when the user requested the procedure matches the mobile phone number that is the source of the message, a telephone number acquisition unit that acquires the user's mobile phone number determined to be correct by the number determination unit, and a procedure execution unit that executes the procedure requested by the user using the user 's mobile phone number acquired by the telephone number acquisition unit, wherein the number determination unit acquires information including an encryption code in which user identification information identifying the user in the message is encrypted and the mobile phone number applied for by the user, determines whether the user identification information has been tampered with, and determines that the user's mobile phone number is correct if the user identification information has not been tampered with and the mobile phone number notified in the message matches the mobile phone number that is the source of the message .

In addition, the information management server of the present invention further includes a memory unit that stores customer information regarding a customer who uses a corporate account set in the calling application, the customer information including a mobile phone number that the customer has a contract with a mobile carrier, and further includes an identity verification unit that performs identity verification to determine whether the user and the procedure subject that is the subject of the procedure requested by the user are the same person based on the telephone number acquired by the telephone number acquisition unit and the customer information stored in the memory unit, and the procedure execution unit executes the procedure requested by the user depending on the result of the identity verification by the identity verification unit.

The present invention also provides an information management method performed by an information management server which is a computer device, in which a number determination unit obtains a message notified using the calling application from a user terminal of a user who has requested a procedure, and if the mobile phone number applied for by the user when the procedure was requested by the user matches the mobile phone number that is the source of the message, determines that there is no error in the user's mobile phone number, a telephone number acquisition unit obtains the user's mobile phone number determined to be free of error by the number determination unit, and a procedure execution unit executes the procedure requested by the user using the user's mobile phone number acquired by the telephone number acquisition unit, and the number determination unit obtains information including an encryption code in which user identification information identifying the user in the message is encrypted and the mobile phone number applied for by the user, determines whether the user identification information has been tampered with, and if the user identification information has not been tampered with and the mobile phone number notified in the message matches the mobile phone number that is the source of the message, determines that there is no error in the user's mobile phone number .

The present invention also provides a program for operating a computer as the information management server described above, and for causing the computer to function as each unit of the information management server.

According to the present invention, it is possible to check whether the mobile phone number applied for by the user is correct.

A diagram showing an overview of the processing flow in a moving procedure service providing system 1 to which an information management server 30 according to an embodiment is applied. 1 is a block diagram showing an example of a configuration of a user terminal 10 according to an embodiment. 2 is a block diagram showing an example of the configuration of a moving procedure window server 20 according to an embodiment. FIG. FIG. 2 is a diagram showing an example of the configuration of moving information 220 according to the embodiment. FIG. 2 is a block diagram showing an example of a configuration of an information management server 30 according to the embodiment. FIG. 2 is a diagram showing an example of the configuration of customer information 320 according to the embodiment. A figure showing an example of the configuration of procedure information 321 relating to the embodiment. FIG. 11 is a sequence diagram showing a process flow for creating customer information 320 according to the embodiment. 1 is a sequence diagram showing the flow of processing performed by a moving procedure service providing system 1 according to an embodiment. FIG. FIG. 4 is a diagram showing an example of a screen displayed on a display unit 14 according to the embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit 14 according to the embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit 14 according to the embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit 14 according to the embodiment. 1 is a sequence diagram showing the flow of processing performed by a moving procedure service providing system 1 according to an embodiment. FIG. A sequence diagram showing the flow of processing performed by a moving procedure service providing system 1 in a modified example of an embodiment.

The following describes an embodiment of the invention with reference to the drawings. The following describes, as an example, a case where procedures related to moving are performed, but is not limited to this. This embodiment can be widely applied to cases where various procedures for government agencies, private businesses, etc. are performed in one go via a portal site that serves as a window.

Figure 1 is a diagram showing an overview of the process flow in a moving procedure service providing system 1 to which an information management server 30 according to an embodiment is applied.

The moving procedure service providing system 1 is a system that provides a moving procedure service. The moving procedure service is a service that collectively carries out various procedures that arise in association with a move online.

In moving procedure service providing system 1, procedures associated with moving are divided into procedures that do not require identity verification and procedures that do, and each procedure is carried out separately. Identity verification here means confirming the identity of the person applying for the procedure and the person who is the subject of the procedure. For procedures that require identity verification, moving procedure service providing system 1 carries out the procedure after confirming the identity of the user and the subject of the procedure.

The following describes procedures that occur when moving, such as procedures with government agencies, procedures related to lifelines, and other procedures related to moving. Procedures with government agencies include, for example, procedures for submitting a moving-out notification and a moving-in notification to move one's residence certificate. Procedures related to lifelines include procedures related to the use of water, electricity, gas, and the like. Procedures related to lifelines include, for example, procedures related to stopping or starting the use of lifelines, and procedures that arise when applying for direct debit to pay usage fees. Procedures related to other moves include procedures that occur when moving other than the use of lifelines, such as procedures for canceling a contract with an Internet provider that was in place at the move-out location, or for signing up with a new Internet provider at the move-out location, and procedures that arise when applying for direct debit to pay provider fees. In addition, the following describes procedures that require identity verification, such as procedures with government agencies, and procedures related to the use of lifelines and direct debit among other procedures related to moving.

However, this is not limited to the above, and which procedures associated with moving require identity verification may be determined at will. For example, procedures for which identity verification is required by law, etc. may be determined to require identity verification, and specific procedures that are not required by law, etc., but which require identity verification in consideration of the content of the procedure, from the perspective of preventing crime or protecting personal information, may be determined to require identity verification.

As shown in FIG. 1, the moving procedure service providing system 1 includes, for example, a user terminal 10, a moving procedure counter server 20, an information management server 30, an administrative procedure counter server 40, a local government server 50, a lifeline operator server 60, a contractor server 70, and a mobile carrier server 80.

The user terminal 10 is a computer device of a user who uses the moving procedure service. The user terminal 10 is, for example, a smartphone, a tablet terminal, a mobile phone, a PC, etc.

(Step S11)
The user terminal 10 submits a usage application to the moving procedure window server 20. The usage application is an application to use the moving procedure service.
(Step S12)
The user terminal 10 receives a result notification from the moving procedure window server 20. The result notification is a notification of the result of the procedure requested by the application for use, etc.

The moving procedure counter server 20 is a computer device that operates a portal site that serves as a counter for the moving procedure service. The moving procedure counter server 20 is, for example, a server device or a PC. The moving procedure counter server 20 accepts a usage application from the user terminal 10 and obtains from the user terminal 10 the information necessary to use the moving procedure service. The moving procedure counter server 20 uses the moving information 220 to carry out the procedure requested by the user.

(Step S13)
The moving procedure window server 20 submits procedures to the contractor server 70 for some of the procedures requested by the user, and receives the results of the procedures. Here, the procedures requested by the moving procedure window server 20 to the contractor server 70 are administrative procedures and procedures other than the use of lifelines that occur with moving, such as procedures that do not require identity verification.

(Step S14)
The moving procedure window server 20 submits an application for other procedures among the procedures requested by the user to the lifeline operator server 60 and receives the results of the procedures. Here, the procedures requested by the moving procedure window server 20 to the lifeline operator server 60 are procedures related to the use of a lifeline, and are, for example, procedures that do not require identity verification.

(Step S15)
The moving procedure counter server 20 notifies the information management server 30 of information regarding procedures that require identity verification among the procedures requested by the user, and requests the information management server 30 to execute the procedures that require identity verification. The moving procedure counter server 20 receives the results of executing the procedures that require identity verification from the information management server 30.

The information management server 30 is a computer device that executes procedures that require identity verification among the procedures requested by the user. The information management server 30 is, for example, a server device or a PC operated by a company. The information management server 30 acquires information about the user from the moving procedure counter server 20, and uses the acquired information to verify the identity of the user and the person who will be the subject of the procedure. The information management server 30 uses information obtained from the mobile carrier server 80 to verify the identity of the user and the person who will be the subject of the procedure (symbol M). The method by which the information management server 30 verify the identity of the user and the person who will be the subject of the procedure will be explained in detail later.

(Step S16)
The information management server 30 submits procedures to the lifeline operator server 60 for some of the procedures requested by the moving procedure counter server 20, and receives the results of the procedures. Here, the procedures requested by the information management server 30 to the lifeline operator server 60 are procedures related to the use of a lifeline, and require identity verification.

(Step S17)
The information management server 30 submits procedures to the contractor server 70 for other procedures among those requested by the moving procedure counter server 20, and receives the results of the procedures. Here, the procedures requested by the information management server 30 to the contractor server 70 are administrative procedures and other procedures that occur with the move other than the use of lifelines, and require identity verification.

(Step S18)
The information management server 30 submits an application for administrative procedures among the procedures requested by the moving procedure counter server 20 to the administrative procedure counter server 40 and receives the results of the procedures.

The administrative procedure counter server 40 is a computer device that operates a portal site that serves as a counter for administrative procedure services. The administrative procedure counter server 40 is, for example, a server device or a PC operated by a government ministry or agency. The administrative procedure counter server 40 accepts applications for administrative procedures from the information management server 30 and obtains the information necessary for the administrative procedures.

(Step S19)
The administrative procedure counter server 40 uses the information acquired from the information management server 30 to apply for an administrative procedure to the local government server 50 and receives the results of the procedure from the local government server 50.

The local government server 50 is a computer device that performs administrative procedures. The local government server 50 is, for example, a server device or a PC operated by a local government. The local government server 50 receives from the administrative procedure counter server 40 an application for an administrative procedure and information required for the administrative procedure, and performs the administrative procedure based on the received information. The local government server 50 notifies the administrative procedure counter server 40 of the procedure results.

The lifeline operator server 60 is a computer device that performs procedures related to the use of lifelines such as water, electricity, and gas. The lifeline operator server 60 is, for example, a server device, a PC, etc. operated by a lifeline operator. The lifeline operator server 60 performs procedures based on an application from the moving procedure counter server 20 for a procedure that does not require identity verification, and notifies the moving procedure counter server 20 of the results of the procedure. The lifeline operator server 60 also performs procedures based on an application from the information management server 30 for a procedure that requires identity verification, and notifies the information management server 30 of the results of the procedure.

The contractor server 70 is a computer device that performs procedures that occur in association with moving, other than for lifelines. The contractor server 70 is, for example, a server device or a PC operated by a private business operator. The contractor server 70 performs procedures based on an application from the moving procedure counter server 20 for a procedure that does not require identity verification, and notifies the moving procedure counter server 20 of the results of the procedures. The contractor server 70 also performs procedures based on an application from the information management server 30 for a procedure that requires identity verification, and notifies the information management server 30 of the results of the procedures.

The mobile carrier server 80 is a computer device that provides communication and call services via mobile phones. The mobile carrier server 80 is a server device, PC, etc. operated by a mobile carrier (mobile phone operator) with which the user has a contract. The mobile carrier server 80 provides an application program (hereinafter referred to as a calling app) that allows mobile phones to send and receive messages such as text, photos, still images, and moving images. In the calling app, messages are sent and received using the phone number of the mobile phone as the destination.

Corporate accounts (hereafter referred to as corporate accounts) are set up on the calling app. Mobile phone subscribers can follow (use) a corporate account on the calling app to exchange messages and information with that company.

In order to provide a place for such companies and contractors to exchange information, the calling app has a mechanism to improve the security of transactions between companies and contractors. Specifically, corporate accounts set up in the calling app are limited to companies that have passed the screening of mobile phone carriers. In addition, when the calling app is used, the phone number of the mobile phone using the calling app is checked to see if it is an unauthorized number, and only numbers that have been confirmed to be unauthorized are notified to the company. As a result, only mobile phones that have been confirmed to be unauthorized numbers can use the calling app. An unauthorized number here is the phone number of a mobile phone that has been obtained fraudulently, for example, the phone number of a mobile phone for which the mobile phone carrier has not conducted identity verification at the time of contract.

The moving procedure service providing system 1 uses the mechanism of this calling app to verify the identity of the user. Specifically, it is assumed that a corporate account related to the information management server 30 (e.g., the corporate account of the company that operates the information management server 30) is set in the calling app. It is also assumed that the calling app is installed in the user terminal 10, and that the corporate account related to the information management server 30 is followed by the user terminal 10. In other words, it is assumed that the mobile phone number of the user terminal 10 has been notified to the company related to the information management server 30, unless the user terminal 10 has been obtained illegally.

FIG. 2 is a block diagram showing an example of the configuration of the user terminal 10 according to the first embodiment. The user terminal 10 includes, for example, a communication unit 11, a storage unit 12, a control unit 13, and a display unit 14. The communication unit 11 communicates with the moving procedure counter server 20 and the information management server 30. The storage unit 12 stores programs for executing various processes of the user terminal 10, and temporary data used when performing various processes. For example, the storage unit 12 stores an application program downloaded when installing a calling app. The display unit 14 includes a display screen, and displays an image on the display screen based on the control of the control unit 13.

The control unit 13 provides overall control over the user terminal 10. For example, the control unit 13 accesses a specific URL (Uniform Resource Locator) corresponding to a portal site provided by the moving procedure counter server 20 in response to an input operation by the user. The control unit 13 acquires a specific input form screen for applying to use the moving procedure service from the accessed site, and displays the acquired screen on the display unit (not shown). When the information required for the application is entered into the displayed input form screen by the user's operation, etc., and an operation is performed to send the entered information, the control unit 13 transmits information related to the move to the moving procedure counter server 20. This causes the user terminal 10 to apply to the moving procedure counter server 20.

Figure 3 is a block diagram showing an example of the configuration of the moving procedure counter server 20 according to the first embodiment. The moving procedure counter server 20 includes, for example, a communication unit 21, a storage unit 22, and a control unit 23. The communication unit 21 communicates with the user terminal 10, the information management server 30, the lifeline operator server 60, and the contractor server 70.

The memory unit 22 stores programs for executing various processes of the moving procedure counter server 20, and temporary data used when performing various processes. The memory unit 22 stores, for example, moving information 220. The moving information 220 is information related to the user's move. The moving information 220 is composed of information notified from the user terminal 10, for example, in conjunction with an application to use the moving procedure service by the user terminal 10. The moving information 220 is information indicating, for example, the user's name, old address, new address, moving date, and the contents of the procedures to be performed using the moving procedure service.

The control unit 23 performs overall control of the moving procedure counter server 20. For example, the control unit 23 executes various processes related to the portal site. In response to a request from a user terminal 10 that has accessed the portal site, the control unit 23 notifies the user terminal 10 of information such as a specified input form screen for using the moving procedure service. Furthermore, when the communication unit 21 receives information related to an application for use of information entered into the input form screen from the user terminal 10, the control unit 23 acquires the information via the communication unit 21, creates moving information 220 using the acquired information, and stores the created moving information 220 in the memory unit 22.

In addition, if the procedures requested in the application for use include a procedure that requires identity verification, the control unit 23 notifies the information management server 30 of the moving information 220. If the procedures requested in the application for use include a procedure to be performed with a lifeline provider, the control unit 23 notifies the lifeline provider server 60 of the moving information 220. If the procedures requested in the application for use include a procedure with another provider, the control unit 23 notifies the provider server 70 of the moving information 220.

When the control unit 23 notifies the information management server 30 of the moving information 220, the control unit 23 receives the procedure result from the information management server 30. When the control unit 23 notifies the lifeline operator server 60 of the moving information 220, the control unit 23 receives the procedure result from the lifeline operator server 60. When the control unit 23 notifies the contractor server 70 of the moving information 220, the control unit 23 receives the procedure result from the contractor server 70.

Figure 4 is a diagram showing an example of the configuration of the moving information 220 according to the embodiment. The moving information 220 is created, for example, for each application for use in the moving procedure service. The moving information 220 includes items such as a moving information ID, user attribute information, and moving-related information. The moving information ID is identification information that uniquely identifies the moving information 220. The user attribute information is information indicating the attributes of the user who applied to use the moving procedure service, and is information indicating at least a user code and the user's mobile phone number. In the example of this figure, the user attribute information includes a user code, a name, a mobile phone number, a date of birth, a kana name, a kanji name, and the like. The user code is information that identifies a user. The user code is created, for example, by the moving procedure window server 20 when a user applies for use. The moving-related information is information related to the move applied for at the time of the application for use identified by the moving information ID. The moving-related information includes items such as moving date, old address, new address, procedure 1, procedure 2, etc. The moving date is information indicating the date on which the move is planned to take place. The old address is information indicating the address from which the move is to be made. The new address is information indicating the address to which the move is to be made. Procedure 1, procedure 2, etc. are information indicating the procedures to be carried out using the moving procedure service.

Figure 5 is a block diagram showing an example of the configuration of the information management server 30 according to an embodiment. The information management server 30 includes, for example, a communication unit 31, a storage unit 32, and a control unit 33. The communication unit 31 communicates with the user terminal 10, the moving procedure counter server 20, the administrative procedure counter server 40, the lifeline operator server 60, the contractor server 70, and the mobile carrier server 80.

The storage unit 32 is configured with a storage medium, such as a hard disk drive (HDD), flash memory, electrically erasable programmable read only memory (EEPROM), random access read/write memory (RAM), read only memory (ROM), or any combination of these storage media. The storage unit 32 stores programs for executing various processes of the information management server 30, and temporary data used when performing various processes.

The memory unit 32 stores, for example, customer information 320 and procedure information 321. The customer information 320 is information about mobile phone subscribers (customers) who follow (use) a company account set up in the calling app. The customer information 320 includes at least information indicating the customer's mobile phone number. The customer's mobile phone number is notified to the company's device (e.g., information management server 30) by the mobile carrier server 80 when the customer follows the company account and creates a customer account for the customer to exchange information with the company account.

Procedure information 321 is information about procedures that require identity verification among procedures requested by users in the moving procedure service. Procedure information 321 is information created using all or part of the moving information 220 notified by the moving procedure counter server 20.

The control unit 33 controls each component of the information management server 30. The control unit 33 is realized, for example, by the CPU (Central Processing Unit) of the information management server 30 executing a program pre-stored in the storage unit 52. The control unit 33 may also be realized as an integrated circuit such as an ASIC (Application Specific Integrated Circuit). The control unit 33 includes, for example, a company account control unit 330, a moving information acquisition unit 331, a personal identification unit 332, a procedure execution unit 333, a device control unit 334, and a number determination unit 335.

The corporate account control unit 330 provides services via a corporate account set in the calling app. The content of the services via the corporate account may be arbitrary, but may be, for example, a service that holds personal information of a customer, and, with the customer's consent, links the customer's personal information with a procedure destination to perform various procedures online. By using the services via the corporate account, customers can perform various procedures safely and with less effort.

For example, the corporate account control unit 330 acquires the customer's mobile phone number notified by the mobile carrier server 80. The customer's mobile phone number here is a mobile phone number assigned to a subscriber (customer) who has signed a contract for a mobile phone that follows the corporate account. The corporate account control unit 330 uses the acquired information to create new customer information 320 for that customer. The corporate account control unit 330 also notifies a message to the acquired mobile phone number of the customer.

The message sent here, for example, encourages registration for a service via a corporate account. In response to the guidance in the message, the customer inputs, for example, a login password for using the service via the corporate account, the procedure to be performed using the service, and personal information required for the procedure, and performs a send operation after confirming the input contents. As a result, the corporate account control unit 330 acquires the customer's personal information, etc., updates the customer's customer information 320 based on the acquired information, and stores the updated customer information 320 in the memory unit 32.

In the above, the functional unit (corporate account control unit 330) of the information management server 30 operates a corporate account, but this is not limiting. The information management server 30 only needs to store at least customer information 320. For example, the corporate account may be operated by an external server different from the information management server 30, and the customer's mobile phone number and personal information may be notified to the information management server 30. In this case, when the information management server 30 is notified of the customer's mobile phone number from the external server, it uses that information to create new customer information 320, and when the information management server 30 is notified of the customer's personal information, it updates the customer information 320 for that customer.

The moving information acquisition unit 331 acquires the moving information 220 notified from the moving procedure counter server 20. The moving information acquisition unit 331 creates procedure information 321 using the acquired information, and stores the created procedure information 321 in the storage unit 32. The moving information acquisition unit 331 outputs the user's mobile phone number from the acquired moving information 220 to the identity verification unit 332.

Here, the moving information acquisition unit 331 only needs to acquire at least the user's mobile phone number from the moving information 220 in the identity verification performed before the procedure, and output the acquired phone number to the identity verification unit 332. This is because the user's mobile phone number is used for identity verification by the identity verification unit 332. In this case, when the identity of the user and the subject of the procedure requested by the user is confirmed in the identity verification, the moving information acquisition unit 331 acquires the remaining information (information other than the user's mobile phone number from the moving information 220).

The identity verification unit 332 verifies the identity of the user and the entity related to the procedure requested by the user. The identity verification unit 332 references the procedure information 321 and acquires the user's mobile phone number. The identity verification unit 332 uses the acquired mobile phone number to search the customer information 320 and determines whether or not there is customer information 320 in which a telephone number the same as the user's mobile phone number is registered. If there is customer information 320 in which a telephone number the same as the user's mobile phone number is registered, it is determined that the customer who signed up for a mobile phone with the same telephone number as the user's mobile phone number is an actual person and not a fictitious person. It is also determined that the customer's mobile phone was not obtained illegally.

Furthermore, if there is customer information 320 in which the same mobile phone number as the user is registered, the identity verification unit 332 verifies that the user matches the customer (the corresponding customer) corresponding to the customer information 320 linked to the same phone number. If the user matches the corresponding customer, the identity verification unit 332 determines that the identity of the user and the entity related to the procedure requested by the user has been confirmed.

In this embodiment, the user is asked to respond with information (specific information) that can identify the corresponding customer, thereby confirming that the user and the corresponding customer match. The specific information is, for example, information about matters that only the corresponding customer can know (presumably). By having the user respond with "matters that only the corresponding customer can know," it is confirmed that the user and the corresponding customer match. In the following, an example will be described in which the "password that the corresponding customer uses to log in to the company account" is used as the "matters that only the corresponding customer can know."

The password here may be at least information shared between the corresponding customer and the corporate account and not disclosed to anyone else. It may be something that is notified by the corporate account when the corresponding customer follows the corporate account, or it may be something that is set by the corresponding customer and notified to the corporate account, or it may be something that is changed by the corresponding customer after being set by the corporate account. Furthermore, "matters that only the corresponding customer can know" are not limited to passwords. "matters that only the corresponding customer can know" may be information that is shared between the corresponding customer and the corporate account in the process of the corresponding customer following the corporate account and subsequently exchanging information with the corporate account, and it may be information that is not disclosed to anyone else. Instead of a password, biometric information such as the user's fingerprint or face may be used as the identifying information.

If there is customer information 320 of a customer with the same registered mobile phone number as the user, the identity verification unit 332 creates a message displaying a one-time URL. A one-time URL is a URL with restrictions, such as being accessible only once, or only during a limited time period or number of times. The identity verification unit 332 then sends the created message to the telephone number of the user terminal 10. Here, it is assumed that the site corresponding to the one-time URL is set to display a screen showing an input field for the customer to enter a password to log in to the company account, and a send button for sending the text entered in the input field.

In this case, the message may include a comment along with the one-time URL. The comment may, for example, include a request to access the one-time URL indicated in the message and verify the user's identity, and may also include information such as that the move procedure will not be carried out unless the user's identity is verified and the expiration date of the one-time URL.

The user visually checks the message sent from the information management server 30 and accesses the one-time URL indicated in the message. The user enters a password (a password for the corresponding customer to log in to the company account) in the input field according to the screen displayed on the site corresponding to the URL. The user also touches the send button after checking the password entered in the input field. This causes the password entered by the user to be notified to the information management server 30.

The identity verification unit 332 acquires the password entered by the user. The identity verification unit 332 checks the acquired password against the customer information 320 of the corresponding customer. If the acquired password matches the password set in the customer information 320 of the corresponding customer, the identity verification unit 332 determines that the user and the corresponding customer are the same. In other words, it determines that the identity of the user and the entity related to the procedure requested by the user has been confirmed. The identity verification unit 332 outputs the result of the identity verification (confirmation result) to the procedure execution unit 333.

The procedure execution unit 333 executes the procedure requested by the user. The procedure execution unit 333 obtains the result of identity verification from the identity verification unit 332. When the identity verification unit 332 confirms that the user is the subject of the procedure requested by the user, the procedure execution unit 333 executes the procedure.

The procedure execution unit 333 first performs a process to obtain consent from the user to link information. Here, "linking information" means sending personal information used in the procedure to the procedure destination device (administrative procedure window server 40, lifeline operator server 60, or contractor server 70). For example, the procedure execution unit 333 creates a message asking whether the user agrees to link information, and sends the created message to the telephone number of the user terminal 10. When the procedure execution unit 333 receives a response from the user terminal 10 indicating consent to linking information, the procedure execution unit 333 obtains information necessary for the procedure from the procedure information 321 or the moving procedure window server 20, and transmits the obtained information to the procedure destination (administrative procedure window server 40, lifeline operator server 60, or contractor server 70). The procedure execution unit 333 then receives the procedure result from the procedure destination.

The device control unit 334 controls the information management server 30 in an integrated manner. For example, the device control unit 334 outputs the moving information 220 received by the communication unit 31 from the moving procedure counter server 20 to the moving information acquisition unit 331. The device control unit 334 transmits messages created by the identity verification unit 332 and the procedure execution unit 333 to the user terminal 10 via the communication unit 31, and when a response to the message is obtained from the user terminal 10, outputs the contents of the response to the identity verification unit 332 and the procedure execution unit 333.

The number confirmation unit 335 cooperates with the moving procedure counter server 20 to determine (confirm) whether there is any error in the mobile phone number of the user applied for by the user. If the number confirmation unit 335 determines that there is no error in the user's mobile phone number, it confirms the number. In other words, if the number confirmation unit 335 determines that there is no error in the user's mobile phone number, it causes the error-free (confirmed) mobile phone number to be acquired by the moving information acquisition unit 331.

For example, the number determination unit 335 notifies the moving procedure counter server 20 that the mobile phone number has been determined. As a result, the moving procedure counter server 20 notifies the information management server 30 of the determined mobile phone number (and all or part of the corresponding moving information 220). Alternatively, the number determination unit 335 may notify the moving procedure counter server 20 that the mobile phone number has been determined, and output the determined mobile phone number to the moving information acquisition unit 331. The method by which the number determination unit 335 determines the mobile phone number will be explained in detail later.

FIG. 6 is a diagram showing an example of the configuration of customer information 320 according to an embodiment. Customer information 320 is created for each customer when a customer account is created for following a corporate account and exchanging information with the corporate account. When a customer account is created, the information management server 30, for example, performs identity verification of the customer, and if the identity is verified, acquires customer information 320 and stores the acquired information in the storage unit 32. The customer information 320 includes items such as a customer information ID, a mobile phone number, a login PW (password), and customer attribute information. The customer information ID is identification information that uniquely identifies the customer information 320. The mobile phone number is a telephone number notified by the mobile carrier server 80 when the customer follows the corporate account. The login PW is a password for logging in to the corporate account. The customer attribute information is attribute information of a customer corresponding to the customer information 320 identified by the customer information ID. The customer attribute information includes items such as a name, an address, a date of birth, a driver's license number, and an account number. Personal information such as the customer's name, address, date of birth, driver's license number, and account number is obtained by entering the customer's name when registering for a company account.

FIG. 7 is a diagram showing an example of the configuration of the procedure information 321 according to the embodiment. The procedure information 321 is created for each moving information 220 notified from the moving procedure window server 20. The procedure information 321 includes items such as a procedure information ID, a moving information ID, a result of identity verification, consent to information sharing, user attribute information, and moving-related information. The procedure information ID is identification information that uniquely identifies the procedure information 321. The moving information ID is the moving information ID of the moving information 220 associated with the procedure information 321 identified by the procedure information ID. The result of identity verification is the result of identity verification performed by the identity verification unit 332. The consent to information sharing is information indicating whether consent to information sharing performed by the procedure execution unit 333 has been obtained. The user attribute information is the user attribute information of the moving information 220 identified by the moving information ID. The moving-related information is the moving-related information of the moving information 220 identified by the moving information ID.

FIG. 8 is a sequence diagram showing the flow of a process for creating customer information 320 according to the embodiment.
(Step S30)
When a user performs an operation to start a calling application, such as by touching an icon of the calling application displayed on the screen, the user terminal 10 transmits a request to start the calling application to the mobile carrier server 80 .
(Step S31)
When the mobile carrier server 80 receives a request to start the calling application from the user terminal 10, the mobile carrier server 80 starts the calling application on the user terminal 10, for example, by sending a chat screen of the calling application to the user terminal 10.
(Step S32)
When a user performs an operation to follow a corporate account set in a calling app, such as by touching a corporate account displayed on the screen of the calling app, the user terminal 10 sends a request to follow the corporate account to the mobile carrier server 80.

(Step S33)
Meanwhile, the information management server 30 periodically (for example, once a day) queries the mobile carrier server 80 and requests a list (customer list) showing the mobile phone numbers of customers who follow the company account.
(Step S34)
In response to an inquiry from the information management server 30, the mobile carrier server 80 transmits to the information management server 30 a list of mobile phone numbers of customers who follow the company account, excluding fraudulent numbers, as a customer list.
(Step S35)
The information management server 30 uses the customer list notified by the mobile carrier server 80 to create new customer information 320 relating to the customers who follow the company account.
(Step S36)
The information management server 30 notifies the customers who follow the company account of a message and prompts them to register their personal information in the company account. Here, the information management server 30 may set a password for the customers to log in to the company account.
(Step S37)
The user terminal 10 responds to the message sent from the information management server 30 and transmits the customer's personal information to the information management server 30 .
(Step S38)
The information management server 30 uses the personal information of the customer notified from the user terminal 10 to update the customer information 320 of that customer.

Figure 9 is a sequence diagram showing the flow of processing performed by the moving procedure service providing system 1 according to the embodiment.

This sequence diagram shows the process flow when first only a portion of the moving information 220 (the mobile phone number of the user terminal 10) is notified from the moving procedure counter server 20 to the information management server 30, and the remaining moving information 220 is notified after identity verification is completed.

(Step S40)
The user terminal 10 notifies the moving procedure window server 20 of an application to use the moving procedure service. The user terminal 10 applies for use, for example, by inputting the necessary information according to an input form related to the application displayed on the portal site of the moving procedure window server 20 and performing an operation to transmit the input information. When applying for use, the content of the procedure to be requested from the moving procedure service and the user's mobile phone number are notified to the moving procedure window server 20.
(Step S41)
The moving procedure window server 20 executes a process for determining the mobile phone number of the user (number determination process). The process for determining the mobile phone number of the user will be described in detail later.
(Step S42)
When the mobile phone number of the user is confirmed, the moving procedure window server 20 notifies the information management server 30 of the mobile phone number of the user. Prior to this process, the moving procedure window server 20 may obtain consent to link the moving information of the user with the information management server 30. In this case, for example, the moving procedure window server 20 displays a screen on a portal site where the user selects a link destination for the moving information. The moving procedure window server 20 displays the company account corresponding to the information management server 30 as a candidate for a link destination for the moving information. Then, when the moving procedure window server 20 receives a notification from the user terminal 10 to select the company account corresponding to the information management server 30 as a link destination for the moving information and the user's mobile phone number is confirmed, the moving procedure window server 20 notifies the information management server 30 of the user's mobile phone number.

(Step S43)
The information management server 30 acquires the user's mobile phone number and creates procedure information 321 based on the acquired phone number.
(Step S44)
The information management server 30 creates a one-time URL. Here, when the information management server 30 receives the user's mobile phone number from the moving procedure counter server 20, the information management server 30 refers to the customer information 320 based on the received mobile phone number of the user. When the information management server 30 stores customer information 320 of a customer (corresponding customer) who has contracted for a mobile phone to which the same number as the user's mobile phone number is assigned, the information management server 30 creates a one-time URL.
(Step S45)
The information management server 30 notifies the telephone number of the user terminal 10 of a message including the one-time URL that is displayed by the created one-time URL via the company account. The message may include a comment. The comment may include, for example, a request to access the one-time URL shown in the message and verify the user's identity, and may include information indicating that the moving procedure will not be carried out unless the user's identity is verified, the expiration date of the one-time URL, etc.

(Step S46)
The user accesses the site corresponding to the one-time URL according to the message notified from the information management server 30. The user inputs information that can identify the corresponding customer (such as a password used by the corresponding customer to log in to a corporate account, which is an example of "specific information") according to the screen displayed on the site, and performs an operation to transmit the input information. As a result, information that only the corresponding customer knows (such as a password used by the corresponding customer to log in to a corporate account) is notified to the information management server 30 as a response from the user terminal 10.

(Step S47)
The information management server 30 acquires the password entered by the user and performs identity verification based on the acquired password. The information management server 30 compares the password entered by the user with the password shown in the customer information 320 of the corresponding customer. If the two passwords match, the information management server 30 determines that identity verification has been successful. On the other hand, if the two passwords do not match, or if the password is not entered into the site corresponding to the one-time URL within a predetermined time limit, the information management server 30 determines that identity verification has not been successful. In this case, for example, the information management server 30 may notify the moving procedure window server 20 or the like that identity verification of the user has not been successful.

(Step S48)
If the information management server 30 can verify the identity of the user, it creates a message to the telephone number of the user terminal 10 to confirm consent to information sharing. The message may include, for example, a request for a response as to whether or not the user consents to sending personal information required for the procedure to the procedure destination, and a message indicating that personal information will not be sent to the procedure destination if the user does not consent. Note that the information sharing in this case includes the information management server 30 acquiring the user's moving information 220 from the moving procedure counter server 20.
(Step S49)
The information management server 30 notifies the user terminal 10 of the message created in step S48 via the company account. For example, the message may include a question such as "May I send personal information required for the procedure to the procedure destination?" along with selection buttons such as "Yes" and "No" for the user to indicate whether or not they agree.
(Step S50)
The user visually checks the message sent from the information management server 30 and touches either the selection button showing "Yes" or "No." As a result, a response message showing whether the user agrees or not is sent from the user terminal 10 to the information management server 30.

(Step S51)
If the response message from the user terminal 10 indicates that the user agrees, the information management server 30 requests the user's moving information 220 (information other than the mobile phone number) from the moving procedure counter server 20.
(Step S52)
In response to a request from the information management server 30 , the moving procedure counter server 20 transmits the user's moving information 220 (information other than the mobile phone number) to the information management server 30 .
(Step S53)
The information management server 30 acquires the user's moving information 220 (information other than the mobile phone number) and updates the procedure information 321 based on the acquired information.

Note that in the above sequence diagram, the flow is described for the case where customer information 320 is created in step S43, and then identity verification is performed in steps S44 to S47, but this is not limited thereto. Information management server 30 may create customer information 320 after identity verification is performed.

In addition, in step S45, the information management server 30 may notify the telephone number of the user terminal 10 of the one-time URL via the destination business with which the corporate account is linked. In this case, the information management server 30 sends the one-time URL, but to the user of the user terminal 10, it appears as if the one-time URL was notified by the destination business. Such aspects are included in the configuration in which "the information management server 30 notifies the telephone number of the user terminal 10 of the one-time URL."

Also, in step S49, a case has been described in which the information management server 30 notifies the telephone number of the user terminal 10 of a message confirming consent to information sharing. However, this is not limited to this. The moving procedure counter server 20 may also notify a message confirming consent to information sharing. In this case, in step S48, if the information management server 30 has been able to verify the identity of the user, it notifies the moving procedure counter server 20 of that fact. When the moving procedure counter server 20 receives notification from the information management server 30 that identity verification has been successful, it creates a message confirming consent to information sharing and notifies the created message to the telephone number of the user terminal 10.

Here, we will explain in detail the process of confirming the user's mobile phone number.

When the moving procedure window server 20 receives a usage application from the user terminal 10, it creates a user code. The user code is information that identifies the user. For example, the moving procedure window server 20 uses a randomly generated number or character string (random key) as the user code. Alternatively, the moving procedure window server 20 may use a randomly generated number or character string (random key) linked to the user's personal information (date of birth, kana name, etc.) as the user code. The user's personal information such as date of birth and kana name is notified to the moving procedure window server 20 from the user terminal 10 by, for example, entering the personal information into a specified input form screen for applying to use the moving procedure service at the time of application. Alternatively, all or part of the information stored in the user attribute information section of the moving information 220 may be used as the user's personal information.

The moving procedure counter server 20 creates an encryption code by encrypting the user code and mobile phone number. In the following explanation, the information before being encrypted in the encryption code (here, the user code and mobile phone number) is referred to as "pre-encryption information". The moving procedure counter server 20 creates the encryption code by encrypting the pre-encryption information using, for example, a pre-stored encryption key. Alternatively, the encryption may be performed by calculating a hash value of the pre-encryption information, and using the calculated hash value as the encryption code.

The moving procedure window server 20 displays the mobile phone number and encryption code applied for by the user on the screen on which the user applied for use. At this time, the moving procedure window server 20 displays information (hereinafter referred to as link information) indicating a link (so-called deep link) that leads to a talk room where messages are exchanged using a calling app, together with the encryption code, etc.

Figures 10A, 10B, and 10C show examples of screens that the moving procedure window server 20 displays on the portal site.

10A shows an example of a screen that the moving procedure window server 20 displays on the portal site when a user applies for use. As shown in the example of this figure, the moving procedure window server 20 displays the user's mobile phone number (reference N1), encryption code (reference N2), and button L along with the text indicating guidance "Click the button below...". Link information is embedded in button L. In the example of this figure, the user's mobile phone number is shown as "customer's phone number" and the encryption code is shown as "passcode".
The screen that the moving procedure window server 20 displays on the portal site is not limited to the example of FIG. 10A. For example, when link information is embedded in the button L such that a calling application is launched based on the user's mobile phone number (N1) and a cryptographic code (N2), the moving procedure window server 20 may display only the button L on the portal site. Also, for example, when link information is embedded in the button L such that a calling application is launched based on the user's mobile phone number (N1), but the contents of the message (e.g., cryptographic code (N2)) to be notified to the talk room of the launched calling application are not automatically set, it is necessary to display not only the button L but also the cryptographic code (N2) on the portal site.

The user visually checks a screen such as that shown in FIG. 10A displayed on the display unit 14, and, for example, checks the phone number and then taps (touches) button L. By tapping button L, a calling app is launched based on the link information embedded in button L, and the talk room of the launched calling app is displayed.

FIG. 10B shows an example of a screen displayed on the display unit 14 when button L is tapped. As shown in the example of this figure, when button L is tapped, a talk room of a calling app is displayed. In the example of this figure, a talk room with a corporate account as the communication partner is shown. The communication partner of the talk room is not limited to a corporate account, and may be set arbitrarily by link information embedded in button L. For example, the communication partner of the talk room may be set to the moving procedure window server 20.

Also, as shown in the example of this figure, the content of the message to be notified (e.g., encryption code) may be automatically set in the message input field MG of the chat room. In this case, the content of the message to be notified may be automatically set by link information embedded in the button L. Alternatively, the user may manually input the content of the message to be notified into the message input field MG. When the user taps the send button B, the message (encryption code) is sent to the communication partner.

Figure 10C shows an example of a screen that is displayed on the display unit 14 when the send button B is tapped. As shown in the example of this figure, when the send button B is tapped, a message is notified and is displayed, for example, as a speech bubble image MG1 containing the content of the notified message (encryption code). In the example of this figure, there is a response to the notified message, and speech bubble image MG2 is shown containing a response message indicating that the user's mobile phone number has been confirmed.

In this embodiment, the number determination unit 335 of the information management server 30 executes a process to determine the mobile phone number applied for by the user. If the communication partner in the talk room is a corporate account, the information management server 30 is notified of the contents of the message. In this case, the information management server 30 executes a process to determine the phone number using the number determination unit 335, and notifies the result of the process as a response to the notified message, as shown in FIG. 10C.

If the communication partner of the talk room is set to the moving procedure window server 20, the moving procedure window server 20 is notified of the contents of the message. In this case, the moving procedure window server 20 responds, for example, by expressing gratitude for receiving the message. The moving procedure window server 20 then transmits the contents of the received message (encryption code) and the mobile phone number (the mobile phone number notified to the moving procedure window server 20 by the carrier as the source of the message) to the information management server 30. The information management server 30 performs a process to determine the phone number using the number determination unit 335, and transmits the processing result to the moving procedure window server 20. The moving procedure window server 20 notifies the talk room of the processing result received from the information management server 30.

Figure 11 shows another example of a screen that the moving procedure window server 20 displays on the portal site. Figure 11 shows an example of a portal site provided by a web service (hereinafter referred to as a web portal site). When a user uses a PC or the like to use the moving procedure service, the user accesses the web portal site. In this case, when a user applies for use, the moving procedure window server 20 displays an image with a two-dimensional code C as shown in the example in this figure on the portal site. Link information is embedded in the two-dimensional code C. In this case, the user acquires the link information embedded in the two-dimensional code C by, for example, capturing an image of the two-dimensional code C with the user terminal 10, and based on the acquired link information, a talk room as shown in Figure 10B is displayed.

Figure 12 is a sequence diagram showing the flow of processing performed by the moving procedure service providing system 1 according to the embodiment.

(Step S60)
The user terminal 10 applies for use of the moving procedure service at the portal site provided by the moving procedure window server 20, similar to step S40.
(Step S61)
The moving procedure window server 20 creates a user code. The user code is identification information that uniquely identifies a user. For example, the moving procedure window server 20 uses a randomly generated number or character string (key) as the user code. Alternatively, the user code is created by concatenating a randomly generated number or character string (key) with the user's personal information (date of birth, kana name, etc.).
(Step S62)
The moving procedure window server 20 creates an encryption code. The encryption code is information obtained by encrypting the user code and mobile phone number (pre-encryption information). The moving procedure window server 20 encrypts the pre-encryption information using, for example, a pre-stored encryption key. Alternatively, the encryption code may be a hash value of the pre-encryption information.
(Step S63)
The moving procedure window server 20 creates link information. The link information is information that connects to a talk room. The moving procedure window server 20 may create link information that automatically sets the encryption code to be notified in the message input field MG of the talk room.
(Step S64)
The moving procedure window server 20 displays a button L with embedded link information on the portal site. In this case, the moving procedure window server 20 may display a guide such as "Click the button below..." as shown in Fig. 10A, as well as the mobile phone number and encryption code applied for by the user.
(Step S65)
The user clicks (tap) the button L of the portal site displayed on the display unit 14 of the user terminal 10. This causes the process indicated in the link information to be executed.
(Step S66)
The user terminal 10 launches the calling application based on the link information. If the calling application is not installed in the user terminal 10, a message prompting the user to install the calling application is displayed, and for example, a site from which the calling application can be downloaded is displayed.
(Step S67)
The user terminal 10 displays the talk room of the calling application based on the link information. The content of the message to be notified (encryption code) is automatically set in the message input field of the talk room. A mobile phone number is embedded in part of the encryption code. Alternatively, the content of the message to be notified (encryption code) is manually input by the user.
(Step S68)
When the user taps the send button B, a message is sent from the user terminal 10 to the information management server 30 , and the user's encryption code is sent to the information management server 30 .

(Step S69)
The information management server 30 receives a message from the user terminal 10 and acquires the user's encryption code. The number determination unit 335 of the information management server 30 decrypts the encryption code. If the encryption code has been encrypted using an encryption key, the number determination unit 335 decrypts the encryption code using a decryption encryption key corresponding to the encryption of the encryption code. Note that if the encryption code is a hash value, the number determination unit 335 does not decrypt the encryption code.

(Step S70)
The number determination unit 335 determines (confirms) whether the notified encryption code has been tampered with. If the encryption code has been encrypted using an encryption key, the number determination unit 335 determines whether the encryption code has been tampered with based on the result of decrypting the encryption code. For example, if the number determination unit 335 cannot decrypt the encryption code, it determines that the encryption code has been tampered with. On the other hand, if the number determination unit 335 can decrypt the encryption code, it determines that the encryption code has not been tampered with.

If the encryption code is a hash value, the number determination unit 335 determines whether the hash value received in the message (called the first hash value) matches the hash value calculated from the pre-encryption information (the second hash value). If the first hash value and the second hash value match, the number determination unit 335 determines that the encryption code has not been tampered with. On the other hand, if the first hash value and the second hash value do not match, the number determination unit 335 determines that the encryption code has been tampered with.

When the number determination unit 335 calculates a hash value (second hash value) from pre-encryption information, the number determination unit 335 needs to obtain the pre-encryption information in advance. In this case, for example, when the moving procedure window server 20 creates a user code in step S61, the moving procedure window server 20 may notify the information management server 30 of the user code and the mobile phone number of the user as pre-encryption information.
Alternatively, the number determination unit 335 may acquire a hash value (second hash value) in advance and determine whether the previously acquired hash value (second hash value) matches the hash value (first hash value) received in the message. In this case, for example, when the encryption code (hash value) is created by the moving procedure window server 20 in step S62, the number determination unit 335 notifies the information management server 30 of the encryption code by the moving procedure window server 20.
The number determination unit 335 may also perform identity verification based on a mobile phone number. For example, the number determination unit 335 determines that identity verification has been performed correctly when the mobile phone number of the user previously obtained matches the mobile phone number indicated in the currently obtained encryption code.

(Step S71)
The number determination unit 335 judges (confirms) whether there is an error in the mobile phone number. The number determination unit 335 judges whether the mobile phone number (called the first number) obtained by decrypting the encryption code received in the message matches the mobile phone number (called the second number) notified by the carrier as the source of the message. If the first number and the second number match, the number determination unit 335 judges that there is no error in the mobile phone number applied by the user. On the other hand, if the first number and the second number do not match, the number determination unit 335 judges that there is an error in the mobile phone number applied by the user.
If the encryption code received in the message has not been tampered with and the mobile phone number applied by the user is correct, the number confirmation unit 335 confirms the number. In this case, in addition to the mobile phone number of the user, it is possible to confirm whether the personal information of the user (date of birth, kana name, etc.) matches, and it is possible to confirm whether the personal information of the user is correct.
(Step S72)
When the number determination unit 335 determines the mobile phone number applied for by the user, it notifies the moving procedure window server 20 that the mobile phone number has been determined. When the number determination unit 335 determines the mobile phone number applied for by the user, it may be configured to link the number to the customer information 320. Specifically, the number determination unit 335 extracts the customer information 320 in which the determined mobile phone number is stored, and links the customer of the extracted customer information 320 with the user who applied for the determined mobile phone number. In this way, when linking with the customer information 320, it is possible to check whether the user's personal information (date of birth, kana name, etc.) matches in addition to the user's mobile phone number, and it is possible to improve the certainty that the user's personal information is free of errors.

As described above, the information management server 30 of the embodiment includes a number determination unit 335, a moving information acquisition unit 331 (an example of a "telephone number acquisition unit"), a storage unit 32, and a procedure execution unit 333. The storage unit 32 stores customer information 320. The customer information 320 is information about a customer who uses a corporate account set in a calling application, and includes the telephone number of a mobile phone that the customer has contracted with a mobile carrier. The number determination unit 335 acquires a message notified using the calling application from the user terminal of the user who requested the procedure. If the mobile phone number applied when the user requested the procedure matches the mobile phone number that is the source of the message, the number determination unit 335 determines that the mobile phone number of the user is correct. The moving information acquisition unit 331 acquires the mobile phone number of the user that is determined to be correct by the number determination unit 335. The procedure execution unit 333 executes the procedure requested by the user using the mobile phone number of the user acquired by the moving information acquisition unit 331.

In this way, the information management server 30 of the embodiment can carry out various procedures using the confirmed number. Therefore, if the mobile phone number applied for by the user is notified from another mobile phone to which that number has not been assigned, or if the customer applies for an incorrect number due to an input error, the number is not confirmed, thereby preventing a situation in which a message is notified to a terminal of another person other than the user's user terminal 10.

In addition, in the information management server 30 of the embodiment, the number determination unit 335 acquires information including the encryption code and the mobile phone number applied for by the user in the message. The encryption code is information obtained by encrypting the pre-encryption information. The pre-encryption information is information consisting of a user code and a mobile phone number, and is an example of "user identification information that identifies a user." The number determination unit 335 determines whether the encryption code has been tampered with. If the encryption code has not been tampered with and the mobile phone number notified in the message matches the mobile phone number that is the source of the message, the number determination unit 335 determines the mobile phone number of the user. In this way, in the information management server 30 of the embodiment, it is possible to prevent the number from being determined if the encryption code has been tampered with. Therefore, it is possible to suppress fraudulent procedures such as user impersonation.

The information management server 30 of the embodiment further includes an identity verification unit 332. The identity verification unit 332 performs identity verification to determine whether the user and the procedure subject who is the subject of the procedure requested by the user are the same person, based on the telephone number acquired by the moving information acquisition unit 331 and the customer information 320 stored in the memory unit 32. The procedure execution unit 333 executes the procedure requested by the user depending on the result of the identity verification by the identity verification unit 332. As a result, the information management server 30 of the embodiment can perform identity verification based on an error-free (confirmed) mobile phone number, and can perform the procedure more accurately.

(Modification of the embodiment)
13 is a sequence diagram showing the flow of processing performed by the moving procedure service providing system 1 according to a modified embodiment. In this modified embodiment, differences from the above-described embodiment will be described, and the same reference numerals will be used to designate the same components as those in the above-described embodiment, and their description will be omitted. Specifically, steps S80 to S81, S85 to S92, and S94 are similar to steps S60 to S61, S62 to S70, and S72 in the above-described embodiment, and therefore their description will be omitted. That is, in this embodiment, steps S82, S83, and S71 are different from the above-described embodiment.

(Step S82)
The moving procedure window server 20 transmits to the information management server 30 the user code created in step S81 and the mobile phone number applied for by the user.
(Step S82)
The information management server 30 receives the user code and the mobile phone number applied for by the user from the moving procedure counter server 20 , and stores the received information in the memory unit 32 .
(Step S84)
The moving procedure window server 20 creates an encrypted code by encrypting the user code. In this case, the pre-encryption information is only the user code, and does not include the mobile phone number. The method by which the moving procedure window server 20 performs encryption is the same as in step S63, so a description thereof will be omitted.
(Step S93)
The number determination unit 335 checks the mobile phone number. The number determination unit 335 determines whether the mobile phone number (referred to as the first number) received from the moving procedure window server 20 in step S82 matches the mobile phone number (referred to as the second number) notified by the carrier as the source of the message. If the first number and the second number match, the number determination unit 335 determines that the mobile phone number applied by the user has been confirmed. On the other hand, if the first number and the second number do not match, the number determination unit 335 determines that the mobile phone number applied by the user has not been confirmed. In this case, the device control unit 334 may also determine whether the user code (referred to as the first code) received from the moving procedure window server 20 in step S82 matches the user code (referred to as the second code) obtained by decrypting the encryption code notified by the carrier as the source of the message. In this case, in addition to the mobile phone number of the user, it is possible to check whether the user's personal information (such as date of birth and kana name) matches, and it is possible to check whether there are any errors in the user's personal information.

As described above, in the information management server 30 according to the modified embodiment, the number determination unit 335 obtains the mobile phone number applied for by the user from the moving procedure window server 20 (the procedure window server that accepts the procedure). The number determination unit 335 obtains information including the encryption code in the message. The encryption code is information obtained by encrypting the pre-encryption information. The pre-encryption information here is a user code, which is an example of "user identification information that identifies the user". The number determination unit 335 determines whether the encryption code has been tampered with. If the encryption code has not been tampered with and the mobile phone number notified by the moving procedure window server 20 matches the mobile phone number that is the source of the message, the number determination unit 335 determines the mobile phone number of the user. In this way, in the information management server 30 according to the embodiment, it is possible to prevent the number from being determined when the encryption code has been tampered with. Therefore, it is possible to suppress fraudulent procedures due to user impersonation, etc. The user code may be composed of only a random key. Although the accuracy may be lower than when using the user's personal information (such as date of birth or kana name), it is possible to check for errors in the user's personal information using only a random key. In addition, the pre-encryption information may consist only of the user's mobile phone number.

The above describes an embodiment of the present invention in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and includes designs that do not deviate from the gist of the present invention.

Reference Signs List 1: Moving procedure service providing system 10: User terminal 20: Moving procedure window server 30: Information management server 40: Administrative procedure window server 50: Municipality server 60: Lifeline operator server 70: Contractor server 80: Mobile carrier server 32: Storage unit 320: Customer information 321: Procedure information 330: Corporate account control unit 331: Moving information acquisition unit (telephone number acquisition unit)
332: Personal identification unit 333: Procedure execution unit 334: Device control unit 335: Number determination unit

Claims (6)

a number determination unit that receives a message sent from a user terminal of a user who has requested a procedure using a calling application addressed to the mobile phone number , and determines that the mobile phone number of the user is correct if the mobile phone number applied for when the user requested the procedure matches the mobile phone number sent as the message source;
a telephone number acquisition unit that acquires the mobile phone number of the user that is determined to be correct by the number determination unit;
a procedure execution unit that executes a procedure requested by the user using the mobile phone number of the user acquired by the telephone number acquisition unit;
Equipped with
The number determination unit
Acquire information including a cryptographic code in which user identification information identifying the user in the message is encrypted and a mobile phone number applied for by the user,
determining whether the user identification information has been tampered with;
If the user identification information has not been tampered with and the mobile phone number notified in the message matches the mobile phone number of the sender of the message, it is determined that the mobile phone number of the user is correct.
Information management server. a number determination unit that receives a message sent from a user terminal of a user who has requested a procedure using a calling application addressed to the mobile phone number , and determines that the mobile phone number of the user is correct if the mobile phone number applied for when the user requested the procedure matches the mobile phone number sent as the message source;
a telephone number acquisition unit that acquires the mobile phone number of the user that is determined to be correct by the number determination unit;
a procedure execution unit that executes a procedure requested by the user using the mobile phone number of the user acquired by the telephone number acquisition unit;
Equipped with
The number determination unit
The mobile phone number applied for by the user is obtained from a procedure window server that serves as a window for accepting procedures;
obtaining information including an encryption code obtained by encrypting user identification information that identifies the user in the message;
If the user identification information has not been tampered with and the mobile phone number acquired from the procedure window server matches the mobile phone number of the sender of the message, it is determined that there is no error in the user's mobile phone number.
Information management server. a storage unit that stores customer information regarding a customer who uses a company account set in the calling application, the customer information including a mobile phone number that the customer has contracted with a mobile carrier;
and an identity verification unit that performs identity verification to determine whether the user is the same as a procedure subject that is a subject of a procedure requested by the user, based on the telephone number acquired by the telephone number acquisition unit and the customer information stored in the storage unit,
the procedure execution unit executes the procedure requested by the user in accordance with a result of the identity verification by the identity verification unit.
3. The information management server according to claim 1 or 2 . An information management method performed by an information management server which is a computer device, comprising:
A number determination unit obtains a message sent from a user terminal of a user who has requested the procedure using a calling application addressed to the mobile phone number , and if the mobile phone number applied for when the user requested the procedure matches the mobile phone number sent as the message source, determines that the mobile phone number of the user is correct;
A telephone number acquisition unit acquires the mobile phone number of the user that is determined to be correct by the number determination unit,
a procedure execution unit executes a procedure requested by the user using the mobile phone number of the user acquired by the telephone number acquisition unit;
The number determination unit
Acquire information including a cryptographic code in which user identification information identifying the user in the message is encrypted and a mobile phone number applied for by the user,
determining whether the user identification information has been tampered with;
If the user identification information has not been tampered with and the mobile phone number notified in the message matches the mobile phone number of the sender of the message, it is determined that the mobile phone number of the user is correct .
How information is managed. A number determination unit obtains a message sent from a user terminal of a user who has requested the procedure using a calling application addressed to the mobile phone number , and if the mobile phone number applied for when the user requested the procedure matches the mobile phone number sent as the message source, determines that the mobile phone number of the user is correct;
A telephone number acquisition unit acquires the mobile phone number of the user that is determined to be correct by the number determination unit,
a procedure execution unit executes a procedure requested by the user using the mobile phone number of the user acquired by the telephone number acquisition unit;
The number determination unit obtains the mobile phone number applied for by the user from a procedure window server that serves as a window for accepting procedures,
obtaining information including an encryption code obtained by encrypting user identification information that identifies the user in the message;
If the user identification information has not been tampered with and the mobile phone number acquired from the procedure window server matches the mobile phone number of the sender of the message, it is determined that there is no error in the user's mobile phone number .
How information is managed. 4. A program for causing a computer to operate as the information management server according to claim 1 , the program causing the computer to function as each unit included in the information management server.

Images