JP2023119857A - Information processing apparatus, information processing method, and program - Google Patents

Abstract

To provide an information processing apparatus, an information processing method, and a program which suppress delivering a message to any other persons other than a user of destination.SOLUTION: The present invention is directed to a message distribution system having a distribution server, a communication business operator server, a communication terminal, and a Web server. The distribution server 1 has a communication unit 11, a storage unit 12, and a control unit 13. The communication unit 11 uses a message application installed in the communication terminal corresponding to a telephone number of a transmission destination to which the message is transmitted, thereby transmitting a link to an URL indicating candidates for designation of an authentication method for authenticating whether or not a contractor of the telephone number is a user of destination of transmission of the message. The control unit 13 controls determination whether or not the message can be transmitted, in response to a result of the user authentication based on the authentication method designated from the candidates.SELECTED DRAWING: Figure 2

Description

The present invention relates to an information processing device, an information processing method, and a program.

There are electronic notification services that post information online. Japanese Patent Application Laid-Open No. 2002-200000 discloses a technique for transmitting information to an email address that is highly likely to be immediately accessible to the user to whom the notification is to be sent.

Such electronic notification services include messaging services addressed to mobile phone numbers provided by carriers. Message services addressed to mobile phone numbers include, for example, RCS (Rich Communication Services). By using the mobile phone number as the destination, the message can be sent even if the e-mail address of the other party of the notification destination is unknown.

JP 2007-241732 A

When sending a message to a mobile phone number, the mobile phone number may be assigned to another user if the user has terminated the contract with the carrier that provides the mobile phone number. be. As a result, the message does not reach the intended user, but reaches another user. Since some messages have a high degree of importance depending on the content, it is desirable that the messages reach the intended users.

SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and its object is to provide an information processing apparatus and an information processing method that can prevent a message from being delivered to a user other than the intended user. It is in.

In order to solve the above-described problems, one aspect of the present invention provides a message app installed in a communication terminal corresponding to a destination phone number to which a message is to be sent, so that a subscriber of the phone number can send the message. A transmission unit that transmits a link to a URI (Uniform Resource Identifier) that indicates a candidate for specifying an authentication method for authenticating whether it is a user of the destination of transmission, and the authentication method specified from the candidate The information processing apparatus includes a control unit that performs control for determining whether or not to transmit the message according to a result of user authentication performed based on the information.

Further, in order to solve the above-described problems, an information processing method according to the present invention is an information processing method performed by a computer, in which a transmitting unit is installed in a communication terminal corresponding to a destination telephone number to which a message is to be transmitted. to a URI (Uniform Resource Identifier) indicating a candidate for specifying an authentication method for authenticating whether the subscriber of the phone number is the user to whom the message is to be sent, using the message application provided. and the control unit performs control to determine whether or not to transmit the message according to the result of user authentication based on the authentication method specified from the candidate.

Further, in order to solve the above-described problems, the present invention provides a program for operating a computer as the information processing apparatus described above, comprising: It's a program.

ADVANTAGE OF THE INVENTION According to this invention, it can suppress that a message reaches a user other than the user made into the destination.

It is a block diagram which shows the structural example of the message delivery system S which concerns on embodiment. 3 is a block diagram illustrating functions of the distribution server 1 according to the embodiment; FIG. It is a figure which shows the example of the delivery information 120 which concerns on embodiment. It is a figure which shows the example of the response information 121 which concerns on embodiment. It is a figure which shows the example of the message displayed on the communication terminal 4 which concerns on embodiment. 4 is a diagram showing an example of information B# associated with content B according to the embodiment; FIG. 4 is a diagram showing an example of a web page displaying options for authentication methods displayed on the communication terminal 4 according to the embodiment; FIG. 4 is a sequence diagram of a message delivery method executed by the message delivery system S according to the first embodiment; FIG. 4 is a sequence diagram of a message delivery method executed by the message delivery system S according to the first embodiment; FIG. FIG. 10 is a sequence diagram of a message delivery method executed by the message delivery system S according to the second embodiment; FIG. 10 is a sequence diagram of a message delivery method executed by the message delivery system S according to the second embodiment; FIG. 11 is a sequence diagram of a message delivery method executed by the message delivery system S according to the third embodiment; FIG. 11 is a flowchart showing the flow of processing performed by a distribution server 1 according to the third embodiment; FIG. 11 is a flowchart showing the flow of processing performed by a distribution server 1 according to the third embodiment; FIG. 11 is a flowchart showing the flow of processing performed by a distribution server 1 according to the third embodiment; FIG. 11 is a flowchart showing the flow of processing performed by a distribution server 1 according to the third embodiment; FIG. 14 is a sequence diagram of a message delivery method executed by the message delivery system S according to the fourth embodiment; FIG. 21 is a diagram showing an example of distribution information 120A according to the fifth embodiment; FIG. FIG. 14 is a diagram showing an example of a message displayed on the communication terminal 4 according to the fifth embodiment; FIG. FIG. 12 is a sequence diagram of a message delivery method executed by the message delivery system S according to the fifth embodiment; FIG. 12 is a sequence diagram of a message delivery method executed by the message delivery system S according to the fifth embodiment; FIG. 11 is a flowchart showing the flow of processing performed by a web server 6 according to the fifth embodiment;

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing a configuration example of a message delivery system S according to an embodiment. The message delivery system S includes, for example, a delivery server 1, a carrier server 3, a communication terminal 4, and a web server 6.

The distribution server 1 is a server device managed by an operator who provides a service of sending messages to the communication terminal 4 . The distribution server 1 transmits (distributes) a message to the communication terminal 4 via the carrier server 3 . Distribution server 1 transmits an RCS message using RCS (Rich Communication Services), which is a message service addressed to a telephone number. The distribution server 1 performs wireless or wired communication with the company server 2 and the carrier server 3 .

The company server 2 is a server device managed by a requester who requests the message delivery system S to deliver an RCS message to a destination user. The client is, for example, a company, organization, or the like (eg, bank, insurance company, etc.) that provides information to the destination user. The company server 2 performs wireless or wired communication with the distribution server 1 .

The carrier server 3 (3a, 3b) is a server device managed by the carrier. The communication carrier is, for example, an MNO (Mobile Network Operator) that provides the communication terminal 4 with a communication service using a telephone number using a communication line owned or operated by itself.
Communication services include communication using RCS. The carrier server 3 transmits the RCS message to the communication terminal 4 in response to the transmission request from the distribution server 1 . In a communication service using RCS, Webhook information for an RCS message sent to communication terminal 4 is sent to delivery server 1 via communication carrier server 20 . The Webhook information is information indicating the status of the RCS message, for example, the status that the RCS message was received by the communication terminal 4 or that a button in the RCS message was operated.
The carrier server 3 stores carrier contract information related to a contract with a user who has concluded a contract to use the communication terminal 4 in the storage unit. The carrier contract information includes, for example, the user's telephone number, name, address, date of birth, age, and the like. Further, the carrier contract information may include the contract period of the contract between the carrier and the contracted user. Further, the carrier contract information may be customer information about the user registered for services such as messaging services used by the user. The carrier server 3 performs wireless or wired communication with the distribution server 1 and the communication terminal 4 .
Here, when there are multiple carriers, the carrier server 3 is also provided for each carrier. The carrier server 3a is managed by the first carrier, and the carrier server 3b is managed by the second carrier. Hereinafter, when the carrier server is not particularly identified, it will be referred to as the carrier server 3 .

The communication terminal 4 is a communication device such as a smart phone or a mobile phone that can be associated with a phone number. The communication terminal 4 is contracted by a user or the like with the provider of the communication provider server 3 to use a communication service using the communication terminal 4 . The communication terminal 4 can communicate using a communication service provided by a contracted communication carrier. A telephone number is assigned to the communication terminal 4, and it has a function of performing communication with this telephone number as a transmission destination, that is, communication using RCS.
The communication terminal 4 has, for example, a display unit such as a liquid crystal display, and an operation unit such as a touch panel that receives user operations. The communication terminal 4 communicates with the communication carrier server 3 and the communication terminal 4 using the communication network NW. A user is, for example, a living person.

The signature verification server 5 is, for example, a server device that provides a public personal authentication service operated by J-LIS (Local Government Information System Organization).

The web server 6 is a server device managed by an operator who operates a website. A website is associated with a URL (Uniform Resource Locator). The web server 6 causes the communication device that has accessed the website to display a screen corresponding to an operation performed on the screen of the website. A URL is an example of a “URI (Uniform Resource Identifier)”.

As shown in FIG. 2 , the distribution server 1 includes a communication section 11 , a storage section 12 and a control section 13 . The communication unit 11 communicates with the carrier server 3 and the web server 6 . The storage unit 12 stores various information such as distribution information 120 , response information 121 , and collation information 122 .

FIG. 3 is a diagram showing an example of distribution information 120 according to the embodiment. Delivery information 120 is generated for each message. The distribution information 120 includes, for example, information corresponding to item specific identifiers, distribution unit specific identifiers, individual specific identifiers, and buttons (button 1, button 2, . . . ). The item specific identifier is an ID (Identification) that identifies the category of the message to be sent. A delivery unit specific identifier is an ID that identifies a message to be sent. A personal identifier is information that can be identified by a user, such as a telephone number to which a message is sent. The personal identification identifier is not limited to a telephone number as long as it is at least information that allows the user to identify it. For example, key information linked to a telephone number or information that can identify a user can be used as a personal identification identifier.
A button is content that can be included in a message and that can be manipulated by the user. A button includes, for example, information corresponding to each of the button ID, URL, and postback data. The button ID is an ID that identifies the button set in the message. URL is a URL accessed by operating a button. A URL is an example of a “URI (Uniform Resource Identifier)”. Postback data is information included in webhook information. In other words, when the button is operated, Webhook information is transmitted from carrier server 20 to distribution server 10, and the Webhook information includes the postback data set here.

In this embodiment, an identifier is set for postback data in the distribution information 120 . The identifier is information that specifies a combination of (project specific identifier, delivery unit specific identifier, button ID, individual specific identifier). As a result, when the button is operated, Webhook information including the identifier set here is transmitted from the carrier server 20 to the distribution server 10 . By receiving the Webhook information including the identifier, the distribution server 10 can grasp which button was operated in which message sent to the user terminal 30 .
In this embodiment, the URL in the distribution information 120 is provided with an identifier that identifies a combination of information similar to that of the postback data, that is, (issue specific identifier, distribution unit specific identifier, button ID, individual specific identifier). As a result, it is possible to ascertain whether or not the communication terminal that specified the URL and accessed the user terminal 30 accessed using the URL set in the message sent to the user terminal 30 .

It should be noted that the identifier in the postback data and the identifier assigned to the URL may be any information that can identify at least a combination of (issue specific identifier, delivery unit specific identifier, button ID, individual specific identifier). The identifier in the postback data and the identifier assigned to the URL may be the same information or different information.

FIG. 4 is a diagram showing an example of response information 121 according to the embodiment. The response information 121 is generated each time there is a response to a message sent to the user terminal 30, that is, each time a button included in the message is operated. The response information 121 includes, for example, information corresponding to each item of telephone number, postback data, and time stamp. These pieces of information in the response information 121, that is, the information corresponding to the respective items of telephone number, postback data, and time stamp are included in the Webhook information.
The phone number is the phone number of the communication device on which the button operation was performed. Postback data is postback data associated with an operated button. The time stamp is information indicating the time when the button was operated.

The collation information 122 can use, for example, user information that is information about the user, such as telephone number, account ID, name, address, date of birth, gender, and the like.
The telephone number is a number determined as a target telephone number to be used when the telecommunications carrier of the telecommunications carrier server 3 and the user conclude a contract for using the communication terminal 4 .
The account ID is identification information assigned to a user (consumer) who uses application software using the RCS message delivery service.
The storage unit 12 can store collation information, and this collation information may be stored in the company server 2 . Also, the matching information may be stored in a server other than the distribution server 1 and the company server 2 . If the collation information is stored in a place other than the distribution server 1, the storage unit 12 may not store the collation information.

The storage unit 12 includes a storage medium such as a HDD (Hard Disk Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read/write Memory), ROM (Read Only Memory). mory), or these Consists of any combination of storage media. A non-volatile memory, for example, can be used for the storage unit 12 .

Returning to the description of FIG. 2, the control unit 13 includes, for example, an acquisition unit 130, a generation unit 131, a determination unit 132, a display control unit 133, and a collation unit .
Acquisition unit 130 acquires various types of information. For example, the acquisition unit 130 acquires information about an RCS message generated by the generation unit 131, which will be described later, and causes the storage unit 12 to store the acquired information. By writing information about these RCS messages to the storage unit 12 , it becomes possible to use these information as the distribution information 120 .
The acquisition unit 130 acquires the webhook information received from the carrier server 3 and stores the acquired webhook information in the storage unit 12 . By writing the webhook information to the storage unit 12 , it becomes possible to use this webhook information as the response information 121 .
The acquisition unit 130 writes the user information received from the company server 2 to the storage unit 12 . By writing the user information in the storage unit 12 , it becomes possible to use this user information as the collation information 122 .

Upon receiving the message transmission request from the company server 2 , the generation unit 131 generates an RCS message and transmits the RCS message to the communication terminal 4 via the communication carrier server 3 by the communication unit 11 . The RCS message contains the content to be notified to the communication terminal 4 . The content to be notified includes, for example, data such as text, still images and moving images including drawings and photographs such as illustrations, and sounds. In transmitting the message, the company server 2 transmits a message transmission request to the distribution server 1, thereby transmitting the message from the distribution server 1 to the communication terminal 4 via the carrier server 3. can.

The generation unit 131 selects a plurality of authentication methods for authenticating whether the subscriber of the telephone number is the user of the destination to which the RCS message is to be sent, for the communication terminal 4 corresponding to the telephone number of the destination to which the RCS message is to be sent. An RCS message containing a link to a website containing candidates for designation is generated and transmitted from the communication unit 11. - 特許庁The website here may contain candidates for requesting one of a plurality of authentication methods to be specified, but it is explained that authentication by any single authentication method is initiated. or to confirm whether any single authentication method may be initiated.

Here, candidates for the authentication method include, for example, customer master authentication, public personal authentication, and the like.
Customer master authentication is an authentication method that performs identity verification using a customer master managed by the company that sent the message. Customer master authentication may also be referred to as "authentication using a registered ID".
Public personal authentication is an authentication method for verifying a person's identity using a personal card, which is a public certificate. More specifically, public personal authentication is an authentication method using JPKI (public personal authentication service). In this public personal authentication, a personal card is used. A personal card is, for example, an IC (integrated circuit) card capable of storing personal information. As a personal card, more specifically, it is a My Number card. When public personal authentication is performed, the user is asked to enter a password for using an electronic signature, and the My Number card is read by the communication terminal 4, so that the signature verification server 5 performs public personal authentication processing. , when the validity is confirmed, it is possible to obtain four basic information such as the user's name, address, date of birth, and gender. Also, the serial number of the electronic certificate used in the My Number Card and its alternative information may be used to confirm the validity of the serial number, thereby verifying the identity of the person.

Online personal authentication and carrier authentication may be included as candidates for the authentication method. Online personal authentication is an authentication method for online identity verification based on information including an image showing a person's appearance (eg, face), and is, for example, eKYC (electronic Know Your Customer). Carrier authentication is an authentication method that performs identity verification using carrier contract information relating to a contract between a contracted user and a telecommunications carrier of a communication terminal that provides communication services using telephone numbers.

The generation unit 131 generates and transmits to the communication terminal 4 an RCS message for prompting identity verification before transmitting the RCS message including important notification contents to the communication terminal 4 . Then, the distribution server 1 performs identity verification, and after confirming the identity of the person, transmits an RCS message including important notification contents to the communication terminal 4 . Here, the generation unit 131 generates an RCS message so as to include a link to a website (hereinafter also referred to as an authentication site) showing options that can be selected from authentication method candidates in the RCS message for prompting identity verification. .

Here, a method of generating an RCS message for prompting identity verification by the generation unit 131 will be described with reference to FIGS. 5 and 6. FIG.

FIG. 5 is a diagram showing an example of an RCS message for prompting identity verification displayed on the communication terminal 4 according to the embodiment. On the display screen of the communication terminal 4, before the message requested by the company server 2 is displayed, the contents (mark M01) prompting the identity verification are displayed, and the URL indicating the link to the authentication site is displayed. be.
As shown in the example of FIG. 5, the generating unit 131 generates a message usable in RCS, such as a content such as a rich card and a chip list, such as button B, as an RCS message for prompting identity verification. Generate an RCS message associated with a URL indicating a link to a site.

FIG. 6 is a diagram showing an example of information B# associated with button B according to the embodiment. FIG. 6 shows an example of information associated with button B shown in FIG. 5 as information B#. Information B# includes, for example, information corresponding to each item of URL and postback data. A URL is information indicating a specific website (for example, an authentication site). An identifier is assigned to the URL. The identifier is information that specifies a combination of (project specific identifier, delivery unit specific identifier, button ID, individual specific identifier). Postback data includes an identifier.
As shown in the example of FIG. 6, the generation unit 131 generates an RCS message in which the button B is associated with the URL of the authentication site to which the identifier is assigned and the postback data including the identifier.

Returning to the description of FIG. 2, the determination unit 132 determines whether or not the communication device that has accessed the authentication site is the communication terminal 4 that has transmitted the RCS message. When an RCS message associated with the URL of the authentication site is sent to the communication terminal 4, the URL of the authentication site becomes known to other users, and unauthorized access such as browsing the authentication site by other users is prevented. may be made. By determining whether or not the communication device that has accessed the authentication site is the communication terminal 4 that has transmitted the RCS message, the determination unit 132 can prevent such unauthorized access. A specific method for the determination by the determination unit 132 will be described later in detail.

The display control unit 133 controls the content displayed on the communication device. The communication device here includes the communication terminal 4 and terminal devices of other users. If the communication device that has accessed the authentication site is the communication terminal 4 that has transmitted the RCS message, the display control unit 133 displays a screen corresponding to the authentication site on the communication terminal 4 based on the determination result of the determination unit 132 . Let On the other hand, when the judgment part 132 judges that the communication device accessing the authentication site is not the communication terminal 4 that transmitted the message, the display control part 133 causes the communication device other than the communication terminal 4 to display an error screen. The error screen is, for example, a screen indicating that the authentication site cannot be accessed.

The verification unit 134 determines whether or not to transmit an RCS message containing important notification contents according to the result of user authentication based on the authentication method selected from the options displayed on the authentication site.
The collation unit 134 collates the collation information 122 with the authentication information and determines whether or not the confirmation conditions are satisfied, thereby determining whether or not the RCS message including the important notification content can be transmitted. The authentication information is information about the user obtained in response to the user's operation input in order to verify whether the user of the communication terminal 4 is the user to whom the message is to be sent.
Here, the confirmation conditions are, for example, the contents of any of the predetermined items such as name, address, date of birth, and gender among the items included in the verification information, and the contents of the predetermined items among the items included in the authentication information. may be consistent with
If the collation unit 134 determines that the confirmation condition is satisfied, it can determine that the identity has been verified. That is, it can be considered that the contractor of the telephone number to which the message is to be sent matches the user to which the message is to be sent, and that the person is the person himself/herself.
This collation may be performed by the distribution server 1, but may be performed by the company server 2, the carrier server 3, or the signature verification server 5. FIG. In this case, the control unit 13 performs control for determining whether or not to transmit an RCS message including important notification contents according to the result of user authentication based on the authentication method selected from the options.

FIG. 7 is a diagram showing an example when the authentication site is displayed on the display screen of the communication terminal 4. As shown in FIG. On the display screen of the communication terminal 4, an option (code M02) for selecting the authentication method is displayed. At least one option is displayed. The example in this figure shows a case where four options are displayed. The user selects an authentication method from these options, and taps (inputs an operation) the desired authentication method option on the screen. Thereby, the authentication method can be selected from the options. This screen shows a case where four options are displayed, but the number of options may be only one, or a plurality of options other than four may be displayed. When only one option is displayed, the user may be allowed to select the one option, or authentication based on the one option may be started directly without allowing the user to select.

[Message delivery method sequence]
The sequence of the message delivery method will be described below. In the following embodiment, a case where the company server 2 and the distribution server 1 are separate devices and operated by different companies will be described. may be operated by In this case, the company of the company server 2 can communicate with the carrier server 3 and send the RCS message without going through the provider of the distribution server 1 .
Also, the distribution server 1 equipped with the functions of the company server 2 may be operated by the provider of the distribution server 1 . In this case, the operator of the distribution server 1 can distribute the RCS message according to the intention of the operator of the distribution server 1 without receiving a request from an external company.

[First embodiment: when the distribution server has customer master authentication and verification information]
8A and 8B are sequence diagrams of the message delivery method executed by the message delivery system S according to this embodiment.
In this embodiment, identity verification is performed using information stored in advance as a customer master and information input by the user.
The customer master is not limited to information managed by the company that sent the message. For example, information managed by a company different from the sender of the message may be used as the customer master. Other companies different from the message sender here are companies such as GAFA that provide services used by a relatively large number of users, for example. In this way, customer master authentication may be performed using an account (customer master information) registered at a company other than the sender.

The company server 2 generates transmission data used when transmitting a message to the user. This transmission data includes information necessary to generate the body of the message to be transmitted and information about the user.
The company server 2 creates the message text based on the information stored in the company server 2 when creating the transmission data. The text of the message is, for example, the content that informs the user of the amount to be charged for using a certain service, and is the content that is output on the display screen of the communication terminal 4 or the like. More specifically, the contents are such as "This month's usage fee for XX service is XX yen."
The company server 2 reads the user information stored in the company server 2 for the information about the user when generating the transmission data.
User information includes, for example, telephone number, account ID, name, address, date of birth, gender, and the like. At least part of the information included in the user information can be used as verification information 122 used for verification when performing identity verification.

Also, here, the message text is not essential, but is generally included as the content to be conveyed when sending a message to the user. Also, the transmission data may include user information.

In this embodiment, the database that stores the customer master data may be provided in either the distribution server 1 or the company server 2, but the case in which the distribution server 1 is provided will be described.

The company server 2 transmits to the distribution server 1 a distribution request containing the telephone number of the destination user, verification information, and information necessary to generate the text of the message to be transmitted to the destination user (step S1101). The communication unit 11 of the distribution server 1 receives from the company server 2 a distribution request including the telephone number, verification information, and information necessary to generate the message text.
Here, a case will be described in which the message is sent from the company server 2 to one person, but the message can also be sent to a plurality of users.

The distribution server 1 receives the transmission data transmitted from the company server 2 and processes the data (step S1201). As data processing, the distribution server 1 extracts matching information contained in the transmission data, and extracts information contained in the transmission data necessary for generating the message text. After that, distribution server 1 writes the extracted collation information to storage unit 12 (step S1202).
The information stored in the storage unit 12 here is, for example, the telephone number, account ID, name, date of birth, address, and gender. This account ID may be a number assigned by the company server 2 or a number assigned by the provider of the distribution server 1 .

Distribution server 1 generates a message based on the information required to generate the extracted message text and the telephone number included in the collation information (step S1203). A message is data including a telephone number indicating a destination, a message text, and the like. The generation unit 131 of the distribution server 1 adds a sentence for prompting personal authentication and a URL indicating a link to an authentication site to the message text received from the company server 2 .
The options for selecting the authentication method for personal authentication shown on the authentication site may be arbitrary options, but the company of the company server 2, the provider of the distribution server 1, the carrier of the communication provider server 3 etc., or may be included in advance in the transmission data transmitted from the company server 2 to the distribution server 1 .

When the distribution server 1 generates the message including the content requesting the personal identification, the RCS is used to transmit the telephone number as the destination (step S1204). Here, the distribution server 1 transmits to the communication terminal 4 via the carrier server 3 of the carrier corresponding to the telephone number set in the RCS message, among a plurality of carriers.

The communication terminal 4 receives the RCS message including the contents of prompting the identity verification from the delivery server 1 via the carrier server 3 (step S1401). Here, the communication terminal 4 is installed with an application program (RCS application) related to RCS, and can receive RCS messages from the distribution server 1 . An RCS message that includes content that prompts identity verification includes content that prompts identity verification, for example, a character string such as "I have an important notice, so please confirm your identity." displayed on the screen.

The communication terminal 4 accesses the authentication site (Web server 6) when the user taps the URL of the authentication site indicated in the received RCS message (step S1402). As a result, information relating to the authentication site is transmitted from the Web server 6 to the communication terminal 4 , and the information relating to the authentication site is displayed on the display screen of the communication terminal 4 . If the authentication site also includes options for selecting authentication methods, those options are displayed. For example, four options are displayed: "Perform authentication using registered ID", "Perform my number authentication", "Perform carrier authentication", and "Perform online identification using other official documents". be. Here, "authentication using registered ID" corresponds to customer master authentication. In addition, "my number authentication" corresponds to public personal authentication.

The communication terminal 4 receives an operation input for options for selecting an authentication method for personal identification, which is input by the user (step S1403). When the user taps the "authentication using the registered ID" button on the touch panel, the communication terminal 4 accepts the operation input of "authentication using the registered ID", and uses the accepted operation input to access the Web. It communicates with the server 6, and displays an authentication screen for accepting input of authentication information based on the information received from the web server 6 (step S1404). For example, a character string indicating the contents for prompting the input of the authentication information such as "please enter the authentication information" is displayed.

The function of requesting input of authentication information may be implemented by application software separate from the RCS application, or may be implemented by a browser. It also asks the user for authentication information using an interactive messenger application or within an RCS message to be complete within an RCS scenario, such as "What is your date of birth?", "What is your authentication code?", etc. and ask the user to enter authentication information as an answer. You can ask one or more questions. When there are multiple questions, each question may be asked in order, and after each question is answered, whether or not the answer is correct may be checked, or each time an answer to the question is obtained, the answer may be given. is correct. An RCS scenario is a message in which a question is asked to a user and an answer input from the user can be accepted within the RCS message, and the content of the question and the order of the questions are prepared in advance. .
Here, the case where the authentication screen in step S1404 is displayed after the "authentication using registered ID" button is tapped in step S1403 will be described, but this authentication screen may not be displayed. For example, after tapping the "authentication using registered ID" button, the RCS application may display questions for entering authentication information and ask the user to enter authentication information as an answer. good.

Here, the authentication information is desirably information that can be known only by the user whose identity is to be verified. As the authentication information, for example, at least one of information such as a password, an authentication code, a zip code, a date of birth, and a name may be used.
The password is a character string issued to the user or designated by the user when registering information about the user in the customer master.

When the authentication information input screen is displayed, the user inputs the authentication information (step S1406). When the answer is input, the communication terminal 4 transmits the authentication information, which is the input answer, and the telephone number assigned to the communication terminal 4 to the web server 6 (step S1407).

When receiving the authentication information and the telephone number from the communication terminal 4, the web server 6 transmits (relays) the authentication information and the telephone number to the distribution server 1 (step S1601).
When the distribution server 1 receives the authentication information and the telephone number from the web server 6 (step S1208), the verification information associated with the received telephone number among the verification information stored in the storage unit 12 in step S1202; It is checked whether the received authentication information has a corresponding relationship (step S1209), and it is determined whether or not the confirmation condition is satisfied (step S1210).
Here, the confirmation condition is that the verification information and the authentication information match. When the name and date of birth are used as the authentication information, it is whether or not the name and date of birth input by the user match the name and date of birth included in the collation information.
Also, when a password is used as the authentication information, the password input by the user must match the password stored as collation information. Also, when an authentication code is used as the authentication information, the authentication code input by the user must match the authentication code issued to the user to whom the message is sent through another route.

When distribution server 1 determines that the confirmation condition is not satisfied (step S1210-NG), distribution server 1 generates a message indicating that the confirmation condition is not satisfied (step S1211). Thereafter, the same processes as steps S1212 and S1409 of the first embodiment are performed. As a result, the communication terminal 4 displays a message on the display screen indicating that the confirmation condition is not satisfied. In addition, when it is determined that the confirmation condition is not satisfied, the message indicating that the confirmation condition is not satisfied may not be transmitted from the distribution server 1 to the communication terminal 4 . Also, the communication terminal 4 does not have to display a message indicating that the confirmation condition is not satisfied.

If the distribution server 1 determines that the confirmation condition is satisfied (step S1210-OK), it generates a message based on the information necessary to generate the message body contained in the transmission data (step S1213). ). Thereafter, the same processes as steps S1214 and S1410 of the first embodiment are performed. Thereby, the communication terminal 4 displays the message transmitted from the distribution server 1 . The communication terminal 4 may display a message and display that the confirmation is completed (that the confirmation condition is satisfied).

[Effect of this embodiment]
According to this embodiment, it is possible to verify the identity of a person by using the verification information stored in the distribution server 1 as a customer master. Therefore, when performing identity verification, it is possible to perform identity verification without cooperating with other devices.
In the above-described embodiment, the case where the distribution server 1 determines whether or not the collation and confirmation conditions are satisfied has been exemplified and explained, but the present invention is not limited to this. For example, the web server 6 has collation information, determines whether the web server 6 satisfies the collation and confirmation conditions, and if the confirmation conditions are satisfied, notifies the distribution server 1 to that effect. It may be configured to issue an instruction to distribute the text.

[Second Embodiment: When Public Personal Authentication is Used]
9A and 9B are sequence diagrams of the message delivery method executed by the message delivery system S according to this embodiment.
In this embodiment, a case will be described in which personal identification is performed using personal information and verification information obtained by using public personal authentication in the signature verification server 5 .

In the second embodiment, steps S1101, steps S1201 to S1204, steps S1401, and S1402 are the same as those in the first embodiment, so the same reference numerals are assigned and the description thereof is omitted.

In step S1403A, the communication terminal 4 receives an operation input for options for selecting an authentication method for personal identification, which is input by the contracted user using the communication terminal 4 (step S1403A). When the user taps the button "Perform public personal authentication" on the touch panel, the communication terminal 4 accepts the operation input "Perform public personal authentication", and uses the received operation input to access the Web. Communicate with the server 6, execute application software for performing public personal authentication based on information received from the web server 6 (hereinafter referred to as public personal authentication application), and display a screen for public personal authentication. display (step S1404A). Here, a character string prompting the user to enter the password and read the personal card is displayed, such as "Enter your password and let the terminal read your personal card."

When a password is entered by the user and the personal card is brought close to the reader of the communication terminal 4, the communication terminal 4 accepts the input of the password and transmits the password to the personal card. If the entered password matches the password stored in the personal card (step S 1406 A-OK), the personal card outputs the electronic certificate stored in the personal card to communication terminal 4 . The communication terminal 4 receives the electronic certificate output from the personal card.
On the other hand, if the entered password does not match the password stored in the personal card (step S1406A-NG), the personal card outputs a response signal to communication terminal 4 indicating that the passwords do not match. When the communication terminal 4 receives this response signal, it displays a character string such as "The password did not match. Please re-enter the password" on the display screen, and proceeds to step S1405. If the number of times the password does not match reaches a certain number even after re-entering the password, the use of the personal card may be suspended (locked).

Here, the case where the communication terminal 4 performs the public personal authentication process and the case where the public personal authentication application is executed has been explained. Public personal authentication processing may be performed by accessing, inputting a password, reading a personal card, or the like. Alternatively, application software different from the public personal authentication application may be executed to accept password input, perform password match determination, and return the determination result to the public personal authentication application.
In addition, although the case where the communication terminal 4 communicates with the personal card and acquires an electronic certificate has been described here, the information stored in the personal card is stored in the memory provided in the communication terminal 4, and the personal This memory may be accessed instead of reading the card. For example, when a password is entered by the user, the communication terminal 4 may refer to the internal memory and, if the password matches, read the electronic certificate from the memory.

Also, instead of authentication using a password, biometric authentication may be performed. Biometric authentication may be, for example, fingerprint authentication, face authentication, iris authentication, or the like.

When the input password matches the password stored in the personal card and receives the electronic certificate from the personal card, communication terminal 4 transmits the received electronic certificate to Web server 6 (step S1407A). Here, the communication terminal 4 not only transmits the electronic certificate, but also uses information that can identify which user's electronic certificate this electronic certificate belongs to as association information (association key). Send with The associated key may be, for example, a telephone number assigned to the communication terminal 4, an account ID assigned in a public personal authentication application, or token information (for example, a one-time password, etc.). good. However, if it is possible to identify which communication terminal 4 is the transmission source of the electronic certificate, it is not necessary to transmit the linking key.

Upon receiving the electronic certificate and the binding key from the communication terminal 4, the Web server 6 transmits (relays) the electronic certificate and the binding key to the signature verification server 5 (step S1601A).
Here, the case where the electronic certificate and the binding key are transmitted from the communication terminal 4 to the Web server 6, and the Web server 6 transmits them to the signature verification server 5 has been described. The communication terminal 4 may transmit the electronic certificate and the linking key to the signature verification server 5 . If the Web server 6 does not relay, the communication terminal 4 sends to the signature verification server 5 the electronic certificate and the linking key as well as information indicating that the authentication result is to be notified to the Web server 6 .

Upon receiving the electronic certificate and the linking key from the distribution server 1, the signature verification server 5 performs authentication processing based on whether the electronic certificate is valid (step S1501). When the signature verification server 5 determines that the electronic certificate is valid (step S1502-OK), the signature verification server 5 reads the personal information corresponding to the electronic certificate from the storage unit, and sends the personal information and the linking key to the distribution server. 1, and if it is determined that the electronic certificate is invalid in the authentication process (step S1502-NG), a response signal to the effect that it is invalid is sent to the Web server 6. FIG. Here, the case where the signature verification server 5 transmits the confirmation result and the basic 4 information to the Web server 6 will be described, but the Web server 6 may also go to the signature verification server 5 to acquire the basic 4 information.
The personal information transmitted here includes, for example, the user's name, address, date of birth, and gender (four basic information).

When the Web server 6 receives the response signal indicating that the electronic certificate is invalid from the signature verification server 5, it transmits (relays) the response signal to the distribution server 1 (step S1602). Upon receiving the response signal from the Web server 6, the distribution server 1 generates a message indicating that the electronic certificate is invalid (step S1206), and transmits the generated message to the communication terminal 4 by RCS ( step S1207). The message generated here may include the content indicating that the electronic certificate is invalid, or may include the content indicating that the electronic certificate is invalid and prompting the user to re-authenticate. good.
When receiving the message from the distribution server 1 (step S1408), the communication terminal 4 displays the received message on the display screen. For example, on the display screen, a character string such as "Identification failed. Please re-authenticate" is displayed.

When distribution server 1 receives personal information (basic 4 information) and a linking key as a result of public personal authentication from signature verification server 5 in response to the determination that the electronic certificate is valid ( Step S1208A), the collation information memorize|stored in the memory|storage part 12 in step S1202 and the received personal information collate whether there exists a corresponding relationship (step S1209A). Here, the storage unit 12 stores verification information about a plurality of users, but based on the linking key received from the signature verification server 5 via the Web server 6 this time, the verification target is stored in the storage unit 12. The verification information can be read and the read verification information and personal information can be verified.
Also, when the personal card is a My Number card, the information (four basic information: address, name, date of birth, sex) obtained from the signature verification server 5 is the latest information. That is, even if there is a move, the new address after the move is registered in the signature verification server 5 by the user performing a moving procedure (notification of moving out, notification of moving in, etc.) to the local government. be. Therefore, the distribution server 1 can obtain the latest address. Further, when the name of the user is changed, the name after the change is registered in the signature verification server 5 by the user performing a procedure for changing the name with the local government. Therefore, the distribution server 1 can obtain the latest name.

Distribution server 1 compares the verification information with the personal information, and determines whether or not the verification conditions are satisfied (step S1210A).
Here, as a confirmation condition, for example, the content of any of the predetermined items such as name, address, date of birth, gender among the items included in the collation information is the content of the predetermined item among the items included in the personal information. It may be to match the content. For example, four items may match, or some items may match. Some items may be, for example, date of birth and name. This is because the address stored in the company server 2 and the address stored in the signature verification server 5 may not match due to a move or the like. As for the name, all of the first and last name may be used as a condition, or since the last name may be changed, it is possible to use as a condition whether or not a part of the first and last name (for example, first name) matches. good too.

Distribution server 1 compares the verification information with the personal information, and if it determines that the confirmation condition is not satisfied (step S1210A-NG), generates a message indicating that the confirmation condition is not satisfied (step S1211 ), the generated message is transmitted to the communication terminal 4 by the RCS (step S1212). The message generated here may include the content indicating that the verification information and the personal information do not match, or the content indicating that the verification information and the personal information do not match and prompting the user to re-authenticate. may be included. Here, a case will be described in which a message indicating that the confirmation condition is not satisfied is transmitted from the distribution server 1 to the communication terminal 4 when it is determined that the confirmation condition is not satisfied. good. Also, the communication terminal 4 does not have to display a message indicating that the confirmation condition is not satisfied.
When receiving the message from the distribution server 1 (step S1409), the communication terminal 4 displays the received message on the display screen. For example, the display screen displays a character string such as "The recipient of the message did not match the personal information. Please re-authenticate." Here, if there are multiple options for the authentication method received in step S1402, and there are options that have not been selected yet, the remaining options are displayed, and a character string prompting the user to select an option is also displayed. You may As a result, it is also possible to redo the identity verification using another authentication method.

Further, distribution server 1 performs verification in step S1209A, and after it is determined that the verification condition is not satisfied, another authentication method is selected by the user, and even if main verification based on that authentication method is performed, the verification condition is not met. If the condition is not met a predetermined number of times, an error may be notified to the company server 2, which is the source of the message transmission request. The error here may indicate that the message has not yet arrived (the message has not arrived at the communication terminal of the destination user specified by the company of the company server 2).
In addition, in step S1207, the distribution server 1 transmits a message including a request for personal identification, and even if a certain period of time has passed, the selection input of the authentication method is not performed, or the public personal authentication application is used. An error may be notified when the authentication cannot be performed. The error here may indicate that the message has not yet arrived (the message has not arrived at the communication terminal of the destination user specified by the company of the company server 2).

Distribution server 1 compares the verification information with the personal information, and if it determines that the verification conditions are satisfied (step S1210A-OK), the information necessary to generate the message body contained in the transmission data (step S1213), and the generated message is transmitted by RCS to the destination telephone number included in the transmission data (step S1214). The message generated here includes content with a high degree of importance, and includes content to be displayed when personal identification is obtained.

When the message is transmitted from distribution server 1 in step S1214, communication terminal 4 receives the transmitted message (step S1410) and displays the received message on the display screen. For example, the display screen displays a character string representing a message such as "This month's usage fee for XX service is XX yen."

When the transmission of the message to the communication terminal 4 is completed, the distribution server 1 may notify the company server 2 of the completion of transmission. In step S1209, the distribution server 1 may transmit the personal information transmitted from the signature verification server 5 to the company server 2 when the confirmation condition is satisfied using part of the personal information. As a result, the company server 2 can update the information about the user to the latest information. When transmitting personal information to the company server 2, it is desirable to obtain the user's consent in advance for transmitting the personal information to the company server 2. FIG.

[Effect of this embodiment]
According to this embodiment, matching information based on user-related information stored in the company server 2 and information obtained by a public personal authentication service are used for matching, and if the confirmation condition is met, to send messages based on As a result, when there is a corresponding relationship between the information about the user that the company has grasped in the company server 2 and the personal information of the user using the communication terminal 4, the telephone number to which the company intends to send the message as the destination of the message is displayed. A message can be sent when the user of the number is confirmed to be the person to whom the message is to be delivered. As a result, it is possible to prevent the message from being sent when the destination user specified by the company of the company server 2 is not the user of the communication terminal 4, thereby preventing the message from reaching another user. can be prevented.

In the above-described second embodiment, the case where the signature verification server 5 is used has been described. , the message delivery system S may not include the signature verification server 5 .

[Sequence in which communication terminal 4 accesses Web server 6]
The sequence for accessing the web server 6 will be described below. In the following embodiments, it is determined whether or not the communication terminal 4 that has accessed the URL in the RCS message is the communication terminal 4 that has received the RCS message. Then, when the communication terminal 4 that has accessed the URL is the communication terminal 4 that has transmitted the RCS message, access to the URL is permitted. This prevents the URL in the RCS message from being known to a user other than the destination user, thereby preventing the authentication site from being browsed by the other user.

[Third embodiment: When redirecting to the authentication site]
10 to 14 are diagrams showing the flow of processing for accessing an authentication site executed by the message delivery system S according to this embodiment.
In this embodiment, a case will be described in which access to an authentication site by the communication terminal 4 is executed by the redirection processing performed by the distribution server 1 .

As shown in FIG. 10, distribution server 1 generates an RCS message (step S1). The distribution server 1 generates an RCS message in which the button B is associated with the URL to which the identifier is assigned and the postback data including the identifier. The distribution server 1 makes a message transmission request to the carrier server 3 (step S2). Specifically, the distribution server 1 transmits an RCS message to the telecommunications carrier server 3 and requests that the RCS message be transmitted to the communication terminal 4 .

The carrier server 3 performs message distribution processing in response to the message transmission request received from the distribution server 1 (step S3). Specifically, the carrier server 3 transmits the RCS message received from the distribution server 1 to the communication terminal 4 . Communication terminal 4 receives the RCS message from carrier server 3 (step S4). As a result, the RCS message is displayed on the display screen of the communication terminal 4. FIG. The user operates by tapping the button B provided in the RCS message (step S5). As a result, control information (Webhook information) indicating that the button B has been operated is transmitted from the communication terminal 4 to the carrier server 3 .

Upon receiving the webhook information indicating that the button B has been operated, the carrier server 3 transmits the received webhook information to the distribution server 1 (step S6). When the distribution server 1 receives the Webhook information from the carrier server 3, the telephone number, the postback data, and the time stamp extracted from the received Webhook information are stored in the storage unit 12 as the response information 121 (step S7). .

On the other hand, in the processing shown in step S5, when button B is operated, access to the authentication site corresponding to the URL associated with button B is executed. In the example of this figure, instead of accessing the authentication site, the user is temporarily guided to a specific site (or resource) that the distribution server 1 has. That is, a site (or resource) owned by the distribution server 1 is set in the URL. In this way, when the access to the authentication site is associated with the button B, the URI (Uniform Resource Identifier) of the temporarily used resource may be set instead of the URL.

When the distribution server 1 receives an access to a specific site or resource (hereinafter referred to as a site or the like) owned by the distribution server 1, the access time is stored in the storage unit 12 (step S8). The distribution server 1 extracts the identifier given to the URL from the URL corresponding to the received access (step S9). The distribution server 1 refers to the corresponding response information 121 based on the extracted identifier, and executes determination processing (step S10). The determination process is a process of determining whether or not to redirect the accessing communication terminal 4 to the authentication site. Distribution server 1 determines to display the authentication site on the display screen of communication terminal 4 when the communication device that has accessed is communication terminal 4 that is the transmission destination of the RCS message. On the other hand, if the accessing communication device is not the communication terminal 4 to which the RCS message was sent, the distribution server 1 determines not to display the authentication site on the display screen of the communication terminal 4 . The details of the processing performed in authentication site display determination will be described in detail later.

The distribution server 1 determines whether the determination result of the determination process is OK or NG (step S11). The OK here is to display the authentication site on the display screen of the communication terminal 4 . The NG here is not to display the authentication site on the display screen of the communication terminal 4 . When the determination result of the determination process is NG, the distribution server 1 displays an error screen on the communication terminal 4 (step S12). The error screen is a screen that displays that the authentication site cannot be accessed.

When the determination result of the determination process is OK, the distribution server 1 requests the communication terminal 4 to redirect (step S13). Specifically, the distribution server 1 transmits the URL of the authentication site to the communication terminal 4 and requests the communication terminal 4 to access the transmitted URL. Upon receiving the redirect request from the distribution server 1, the communication terminal 4 performs redirect processing (step S14). Specifically, the communication terminal 4 accesses the URL indicated in the redirect request received from the distribution server 1 . As a result, the communication terminal 4 accesses the authentication site on the web server 6 . The web server 6 responds according to the access received from the distribution server 1 (step S15). Specifically, the Web server 6 causes the display screen of the communication terminal 4 to display a screen showing the authentication site. As a result, options for selecting, for example, one or a plurality of authentication methods are displayed on the communication terminal 4 (step S16).

FIG. 11 shows the flow of processing for executing the determination processing shown in step S10 of FIG. First, the distribution server 1 executes a process of acquiring response information (step S100). Next, distribution server 1 executes a process of verifying telephone numbers (step S101). The distribution server 1 then executes a process of comparing the operation time and the access time (step S102), terminates the process, and proceeds to step S11. The operation time here is the time when the button B was operated. The access time is the time when the distribution server 1 receives an access to a site or the like.

FIG. 12 shows the flow of processing for executing the processing of acquiring the response information shown in step S100 of FIG. Here, response information 121 corresponding to access to the site or the like associated with button B is acquired.

Here, the operation for the button B and the access to the site or the like associated with the button B are performed almost at the same time. That is, the timing at which the distribution server 1 receives Webhook information from the communication carrier server 3 due to the operation on the button B, and the timing at which the distribution server 1 receives access to a specific site, etc. is likely to occur at approximately the same time. For example, it took time to generate the Webhook information by the carrier server 3, or the communication line between the carrier server 3 and the delivery server 1 was congested. The timing of receiving information may be delayed. In this case, the distribution server 1 may receive access to a site or the like before the carrier server 3 receives the Webhook information.

If an access to a site or the like is received before the Webhook information is received, there will be a period of time during which the response information 121 corresponding to the access is not stored in the storage unit 12 . In this case, the distribution server 1 determines whether the corresponding response information 121 is not stored in the storage unit 12 due to the delay in receiving the Webhook information, or whether the button B has not been operated. Therefore, it is difficult to distinguish whether the corresponding response information 121 is not stored in the storage unit 12 or not.
As a countermeasure against this, in the present embodiment, when the response information 121 corresponding to the access is not stored, the distribution server 1 returns to the storage unit 12 again after a predetermined waiting time (for example, one second) has passed. , and performs a retry to confirm whether or not the response information 121 corresponding to the access is stored. As a result of executing the retry, if the corresponding response information 121 is stored in the storage unit 12 , the distribution server 1 acquires the corresponding response information 121 . As a result, even if the access is executed before the Webhook information is received, the response information 121 corresponding to the access can be obtained.
If the response information 121 corresponding to the storage unit 12 is not stored even when the number of retries reaches a predetermined threshold value (for example, 3 times), the distribution server 1 does not operate the button B, and responds. It is determined that the response information 121 to be sent is not stored in the storage unit 12 . As a result, when there is a high possibility that the URL has been accessed by another user's communication device, it can be regarded as unauthorized access and can be suppressed.

As shown in FIG. 12, first, the distribution server 1 initializes the number of retries as a variable to 0 (zero) (step S1001). Next, distribution server 1 refers to storage unit 12 based on the identifier extracted from the URL, and determines whether or not corresponding response information 121 is stored (step S1002). If the corresponding response information 121 is stored, the distribution server 1 terminates the process and proceeds to step S101. If the corresponding response information 121 is not stored, the distribution server 1 increments the number of retries (S1003). The distribution server 1 determines whether or not the number of retries is less than the threshold (step S1004). When the number of retries is less than the threshold, the distribution server 1 determines whether or not the waiting time has passed (step S1005). If the waiting time has passed, the distribution server 1 returns to step S1002. On the other hand, if the number of retries is equal to or greater than the threshold in step S1004, the distribution server 1 sets the determination result to NG (step S1006), terminates the process, and proceeds to step S11.

FIG. 13 shows the flow of processing for executing the telephone number verification processing shown in step S101 of FIG. Here, collation is performed by matching the telephone number included in the Webhook information with the telephone number (individual identification identifier) included in the identifier assigned to the URL. It should be noted that the telephone number or individual identification identifier here is not limited to a telephone number as long as it is at least information that can be specified by the user. For example, key information linked to a telephone number or information that can identify a user can be used as a personal identification identifier.

First, the distribution server 1 extracts the response information 121 corresponding to the identifier given to the URL (step S1011). Specifically, the distribution server 1 refers to the storage unit 12 and extracts the response information 121 including the postback data having the identifier corresponding to the identifier assigned to the URL from among the information stored as the response information 121. . Distribution server 1 determines whether or not the telephone numbers match (step S1012). The distribution server 1 matches the telephone number in the extracted response information 121 with the telephone number (production control number) included in the identifier given to the URL. For example, distribution server 1 determines whether or not two telephone numbers match. If the telephone numbers match, the distribution server 1 terminates the process and proceeds to step S102. If the telephone numbers do not match, the distribution server 1 sets the determination result to NG (step S1013), terminates the process, and proceeds to step S11.
Alternatively, in step S1012, the distribution server 10 or the personal identification identifier contained in the Webhook information (referred to as first information) and the information corresponding to the telephone number contained in the identifier assigned to the URI (second information ) indicates that the information is associated with the same user. If the first information and the second information match and indicate that the information is associated with the same user, the distribution server 10 terminates the process and proceeds to step S102. If the telephone numbers do not match, the distribution server 10 determines the determination result as NG (step S1013), terminates the process, and proceeds to step S11.

FIG. 14 shows a process flow for executing the process of comparing the operation time and the access time shown in step S102 of FIG. Here, the operation time when the button B is operated and the access time when the site or the like is accessed are compared.

First, the distribution server 1 acquires the access time (step S1021). The distribution server 1 refers to the storage unit 12 and acquires the access time stored in step S8. The distribution server 1 acquires the operation time indicated by the time stamp in the response information 121 acquired in step S1011 (step S1022). The distribution server 1 determines whether or not the access time is later than the operation time (step S1023). If the access time is after the operation time, the distribution server 1 determines whether the access time is before (operation time+permissible time) (step S1024). If the access time is before (operation time+permissible time), the distribution server 1 accepts the determination result (step S1025), terminates the process, and proceeds to step S11. On the other hand, when the distribution server 1 determines in step S1023 that the access time is before the operation time, and when it determines in step S1024 that the access time is after (operation time + allowable time). , the determination result is NG (step S1026), the process is terminated, and the process proceeds to step S11.

[Effect of this embodiment]
According to this embodiment, the communication terminal that accesses the URL included in the RCS message using the URL used for the access by the distribution server 1 and the Webhook information corresponding to the operation on the button B performs the RCS It is determined whether or not the communication terminal 4 is the destination of the message. As a result, the distribution server 1 can determine whether or not the communication terminal that accessed the URL included in the RCS message is the communication terminal 4 that was the destination of the RCS message. Therefore, when an RCS message containing a link to the authentication site is notified to the communication terminal 4, the URL in the link may become known to other users, and other users may access the authentication site. Even in the case of the authentication site, it is possible to prevent the user from being redirected to the authentication site, and it is possible to suppress the authentication site from being browsed by other users.

[Fourth Embodiment: When Web Server 6 Allows Access to Authentication Site]
FIG. 15 is a diagram showing the flow of processing for accessing an authentication site executed by the message delivery system S according to this embodiment.
In this embodiment, a case will be described in which the Web server 6 determines whether or not to permit access to the authentication site.

The processing shown in steps S21 to S27 in FIG. 15 is the same as the processing shown in steps S1 to S7 in FIG. 10, so description thereof will be omitted.
As shown in FIG. 15, when the communication terminal 4 accesses the URL, the web server 6 stores the access time in the storage unit of the web server 6 (step S28). Web server 6 extracts the identifier assigned to the received URL, and transmits the extracted identifier to distribution server 1 (step S29).
The distribution server 1 refers to the storage unit 12 based on the identifier received from the web server 6, and acquires the response information 121 corresponding to the identifier. The distribution server 1 transmits all or part of the acquired response information 121 to the web server 6 (step S30).
The web server 6 executes determination processing based on the response information 121 received from the communication terminal 4 (step S31). The determination process is a process of determining whether or not to display the information of the authentication site on the display screen of the communication terminal 4 that has accessed. The Web server 6 determines to display the authentication site on the display screen of the communication terminal 4 when the accessing communication device is the communication terminal 4 to which the RCS message has been sent. On the other hand, distribution server 1 determines not to display the authentication site on the display screen of communication terminal 4 when the accessing communication device is not communication terminal 4 to which the RCS message has been sent. Since the processing performed in the display determination processing is the same as the determination processing shown in step S11, the description thereof is omitted.
When the determination result of the determination process is NG, the Web server 6 causes the communication terminal 4 to display an error screen (step S33). On the other hand, if the determination result of the determination process is OK, the display control unit 432 causes the communication terminal 4 to display the screen of the authentication site in the web server 6 (step S34).

[Effect of this embodiment]
According to this embodiment, the web server 6 acquires the webhook information corresponding to the operation on the button B based on the URL used for access. As a result, the Web server 6 can determine whether or not the communication terminal that accessed the URL included in the RCS message is the communication terminal 4 to which the RCS message was sent. Therefore, when another user accesses the authentication site, access to the authentication site can be prohibited, and it is possible to prevent other users from viewing the authentication site. can.

[Fifth Embodiment: Including notification means other than RCS message]
16, 17, 18 (FIGS. 18A and 18B), and 19 are diagrams showing the flow of processing for accessing an authentication site executed by the message delivery system S according to this embodiment.
In this embodiment, a case will be described in which notification other than the RCS message is performed by the delivery server 1. FIG. Notifications other than RCS messages are notifications by SMS messages using SMS (Short Message Service), for example.

The communication terminals 4 are compatible with SMS, but some are compatible with RCS and some are not. For example, when an RCS application is installed and activation including acceptance of terms of use regarding communication using RCS is performed, the communication terminal 4 is a terminal compatible with RCS. On the other hand, if the RCS application is not installed, or if the RCS application is installed but not activated, the communication terminal 4 is a terminal that does not support RCS.
From such a point of view, the message delivery system S of this embodiment transmits an RCS message to the communication terminal 4 that supports RCS, and transmits an SMS message to the communication terminal 4 that does not support RCS. . This makes it possible to transmit messages to user terminals 30 that do not support RCS.

Specifically, the distribution server 1 generates two messages, an RCS message and an SMS message, for messages destined for the communication terminal 4 . As an RCS message, for example, the distribution server 1 provides content such as button B in a rich card or chip list, and generates a message in which the URL of the authentication site is associated with button B, as in the above-described embodiment. The distribution server 1 generates, as the SMS message, a text message containing, for example, the URL of the authentication site.
The distribution server 1 makes a transmission request to the carrier server 3 using the two created messages. The carrier server 3 sends an RCS message to the communication terminal 4 that supports RCS, and sends an SMS message to the communication terminal 4 that does not support RCS.

A method for the distribution server 1 to generate two messages will be described with reference to FIG.
FIG. 16 is a diagram showing an example of distribution information 120A according to the fifth embodiment. Delivery information 120A is generated for each message. The delivery information 120A includes, for example, information corresponding to item specific identifiers, delivery unit specific identifiers, individual specific identifiers, and items of RCS and SMS. The item specific identifier is an ID (Identification) that identifies the category of the message to be sent.
A delivery unit specific identifier is an ID that identifies a message to be sent. A personal identifier is information that can be identified by a user, such as a telephone number to which a message is sent.
The personal identification identifier is not limited to a telephone number as long as it is at least information that allows the user to identify it. For example, key information linked to a telephone number or information that can identify a user can be used as a personal identification identifier.
The RCS item stores information indicating the contents of the message when the RCS message is transmitted to the communication terminal 4 . The SMS item stores information indicating the content of the message when the SMS message is sent to the communication terminal 4 .

The information stored in the RCS includes, for example, information corresponding to items of buttons (button 1, button 2, . . . ). A button is content that can be included in a message and that can be manipulated by the user. A button includes, for example, information corresponding to each of the button ID, URL, and postback data. The button ID is an ID that identifies the button set in the message. URL is a URL accessed by operating a button. Postback data is information included in webhook information. In other words, when the button is operated, Webhook information is transmitted from carrier server 3 to distribution server 1, and the Webhook information includes the postback data set here.

In this embodiment, the first identifier is set in the postback data associated with the button. The first identifier is information that specifies a combination of (issue specific identifier, delivery unit specific identifier, button ID, individual specific identifier). As a result, when the button is operated, the Webhook information including the first identifier is transmitted from carrier server 3 to distribution server 1 . By receiving the Webhook information including the first identifier, the distribution server 1 can grasp which button was operated in which message sent to the communication terminal 4 .

Further, in the present embodiment, the first identifier is given to the URL associated with the button. The first identifier is information equivalent to the first identifier set in the postback data, and is information specifying a combination of (issue specific identifier, delivery unit specific identifier, button ID, individual specific identifier). The RCS identifier is information identifying a message transmitted using RCS.
The first identifier in the postback data and the first identifier attached to the URL may be information that can specify at least a combination of (issue specific identifier, delivery unit specific identifier, button ID, individual specific identifier). The first identifier in the postback data and the first identifier assigned to the URL may be the same information or different information.
Information equivalent to the postback data (first identifier) is attached to the URL, so that a communication terminal that accesses the URL uses the first identifier as a clue to operate the RCS message button on the terminal that accesses the URL. Whether or not there is can be grasped using Webhook information.

Furthermore, in this embodiment, an RCS identifier is added to the URL associated with the button. By assigning an RCS identifier to the URL, it is possible to recognize whether or not a communication terminal that has accessed by specifying the URL has accessed using the URL set in the RCS message without using Webhook information. can be done.

The information stored in the SMS includes, for example, information corresponding to each item of text and URL. Text is text information indicating the content of the message to be sent. A URL is a URL indicated in a message and accessed by manipulating the URL.
In this embodiment, the URL indicated in the SMS message is given a second identifier. The second identifier is information that can determine that the URL has not been tampered with, and is, for example, a check digit of the URL. A check digit is a check code added to detect an error in a URL, and is a code calculated by performing a specific operation using the URL.
By attaching the second identifier to the URL, it is possible to determine whether a communication terminal that has accessed the URL via an SMS message is an unauthorized terminal that has accessed using a tampered URL.

In this embodiment, an RCS identifier is added to the URL notified by the RCS message, and an identifier (SMS identifier) for identifying the SMS message is not added to the URL notified by the SMS message. This is because the number of characters that can be notified in an SMS message may be limited. For example, in some old models, the SMS message is divided by a predetermined number of characters (for example, 70 characters) and notified. Therefore, when a URL having a relatively long number of characters is notified by an SMS message, there is a possibility that the character string indicating the URL to be notified is divided into a plurality of character strings and notified. In such an SMS message that has a limited number of characters and may be divided, it is better to notify a message with as few characters as possible. For this reason, in this embodiment, the SMS identifier is not attached to the URL notified by the SMS message.
In addition, although the case where the SMS identifier is not attached to the SMS message has been illustrated and explained in the above-described embodiment, the present invention is not limited to this. It may be configured to assign an SMS identifier to the SMS message according to the operation mode of the service.

The SMS message transmitted in this embodiment will be explained using FIG. FIG. 17 is a diagram showing an example of an SMS message displayed on the user terminal 30 according to the embodiment. As shown in FIG. 17, the SMS message shows the message in text. In this figure, a URL is shown at the end together with a sentence such as "IR information has been disclosed." Further, as shown in FIG. 17, a second identifier is added to the URL indicated in the SMS message in this embodiment (symbol T).

FIG. 18 (FIGS. 18A and 18B) shows the flow of processing for accessing an authentication site executed by the message delivery system S according to this embodiment.

The distribution server 1 generates messages (RCS message and SMS message) (step S31). The distribution server 1 generates an RCS message in which the button B is associated with the first identifier, the URL to which the RCS identifier is assigned, and the postback data including the first identifier. Also, the distribution server 1 generates an SMS message including the URL to which the second identifier is assigned. The distribution server 1 stores the generated RCS message and SMS message in the storage unit 12 as the distribution information 120 .
The distribution server 1 makes a message transmission request to the carrier server 3 (step S32). Specifically, the distribution server 1 transmits the distribution information 120 to the carrier server 3 and requests the communication terminal 4 to transmit the message.

The carrier server 3 performs message distribution processing in response to the message transmission request received from the distribution server 1 (step S33). Specifically, the communication carrier server 3 determines whether or not the communication terminal 4 supports RCS, and transmits an RCS message to the communication terminal 4 that supports RCS. An SMS message is sent to the communication terminal 4 that does not support RCS.
The communication terminal 4 that supports RCS receives the RCS message from the carrier server 3 (step S34). As a result, the RCS message is displayed on the display screen of the communication terminal 4. FIG. Since the processing shown in steps S35 to S44 is the same as the processing shown in steps S5 to S14 in the third embodiment, description thereof will be omitted. The flow of processing (symbol Y) after step S44 will be described with reference to FIG. 18B.

The communication terminal 4 that is determined not to support RCS in step S33 receives the SMS message from the carrier server 3 (step S45). Thereby, the SMS message is displayed on the display screen of the communication terminal 4 . The user performs operations such as tapping the URL indicated in the SMS message (step S46). As a result, the communication terminal 4 accesses the site or the like indicated by the URL. The flow of processing (symbol X) after step S46 will be described with reference to FIG. 18B.

As shown in FIG. 18B, when step S44 or step S46 is executed (symbols X, Y), the web server 6 receives access to the URL by the communication terminal 4, and performs URL falsification determination processing (step S47). The URL tampering determination process is a process of determining whether the URL notified from the accessing terminal has been tampered with. Details of the URL falsification determination process will be described later. The Web server 6 determines whether or not the determination result of the URL falsification determination process is OK (step S48). If the URL has not been tampered with, the Web server 6 determines that the determination result of the URL tampering determination process is OK. When the URL has been tampered with, the Web server 6 determines that the determination result of the URL tampering determination process is NG. When the determination result of the URL falsification determination process is OK, the Web server 6 causes the display screen of the communication terminal 4 to display a screen showing the authentication site. As a result, the authentication site is displayed on the communication terminal 4 (step S49). On the other hand, when the determination result of the URL falsification determination process is NG, the web server 6 displays an error screen on the display screen of the communication terminal 4 (step S50). This presents options for selecting one or more authentication methods.

FIG. 19 shows the flow of the URL falsification determination process shown in step S47 of FIG. 18B. Here, when a URL is accessed via an SMS message, it is determined whether the URL has been tampered with. On the other hand, if the URL is accessed via an RCS message, it does not determine whether the URL has been tampered with. Alternatively, as a simple confirmation, a determination process different from the determination process performed on the SMS message may be performed. When the URL is accessed via the RCS message, the determination process shown in step S10 is executed, and it is determined that the URL is accessed by operating the button provided in the RCS message. This is because it has already been verified and the URL falsification determination process is considered unnecessary.
Note that if a URL is accessed via an RCS message, it may be determined whether the URL has been tampered with, as in the case of SMS messages. In this case, for example, the URL indicated in the RCS message is appended with the URL check digit.

First, the Web server 6 acquires the URL notified by the accessing communication terminal (step S470). The Web server 6 determines whether or not the acquired URL has an RCS identifier (step S471). If no RCS identifier is assigned to the URL, the Web server 6 determines whether the URL has been tampered with (step S472). The Web server 6 uses the second identifier attached to the URL to determine whether the URL has been tampered with. Specifically, the Web server 6 calculates the check digit of the URL and compares the calculated check digit with the second identifier. If the check digit and the second identifier match, the web server 6 determines that the URL has not been tampered with. On the other hand, if the check digit and the second identifier do not match, the web server 6 determines that the URL has been tampered with. If the URL has been tampered with, the Web server 6 determines that the result of the URL tampering determination process is NG (step S473), terminates the process, and proceeds to step S48.
On the other hand, if an RCS identifier is assigned to the URL in step S471, or if it is determined that the URL has not been tampered with in step S472, the Web server 6 accepts the URL tampering determination processing determination result (step S474). ), the process is terminated and the process proceeds to step S48.

[Effect of this embodiment]
According to this embodiment, when the RCS message is notified, it is determined whether or not the communication terminal that has accessed the URL included in the RCS message is the communication terminal 4 to which the RCS message was sent. made it When the SMS message is notified, it is determined whether or not the accessed URL included in the SMS message has been tampered with. As a result, even in a mixed environment in which either an RCS message or an SMS message is sent to the communication terminal 4, it is possible to prevent other users from viewing the authentication site.

In each of the above-described embodiments, the biometric information stored in the communication terminal 4 may be used to verify the identity after the identity verification is performed and the identity is confirmed.
Also, the authentication method may be set according to the importance of the notification content of the message. For example, it may be determined in advance that public personal authentication can be performed when the importance of the notification content of the message is of a predetermined level.
Also, for a user who has performed identity verification in the past, an authentication method different from the previous authentication method may be set. For example, for users who have never verified their identity, we ask them to select either public personal authentication or carrier authentication, and then, when performing identity verification for the same user for the second time or later, may be selected from any of the authentication method options. In other words, the options may be determined according to the degree of importance and whether or not the person has been successfully authenticated in the past.

In each of the above-described embodiments, the case of sending a message from the company server 2 has been described, but the company server 2 may be a company such as a bank or an insurance company, or a company that operates an electronic post office box. There may be. A company that operates an electronic post office box may accept messages from various other companies and send them to the destination user so that they can be viewed. For example, a company that operates an electronic post-office box may receive message transmission requests from a plurality of different companies and request the distribution server 1 to transmit the messages. At that time, as described above, options for selecting the authentication method may be displayed on the communication terminal 4 according to the importance of the message, and the user may select the authentication method.

Also, in the above-described embodiment, a case has been described in which a message is electronically transmitted when the identity is verified. can be For example, confirming the identity and intention to continue the contract is electronically performed according to the above-mentioned embodiment, and when the identity is confirmed, the contract completion document and the latest credit card are sent (mail, home delivery, etc.) You may do so.

Further, in the above-described embodiment, the case where authentication is performed at the authentication site was exemplified, but any website may be applied instead of the authentication site. For example, the URL of the link destination included in the message may be the URL of a site that does not perform authentication.

All or part of the message delivery system S and the delivery server 1 in the above-described embodiment may be realized by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed. It should be noted that the "computer system" here includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. Furthermore, "computer-readable recording medium" refers to a program that dynamically retains programs for a short period of time, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing a part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system. It may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design and the like are included within the scope of the gist of the present invention.

S... Message delivery system 1... Delivery server 2... Company server 3... Carrier server 4... Communication terminal 5... Signature verification server 6... Web server 11... Communication unit 12... Storage unit 120 ... distribution information, 121 ... response information (Webhook information), 122 ... verification information, 13 ... control unit, 130 ... acquisition unit, 131 ... generation unit, 132 ... determination unit, 133 ... display control unit, 134 ... verification unit

Claims (4)

Specify an authentication method for authenticating whether the subscriber of the phone number is the user of the destination of the message, using the message application installed on the communication terminal corresponding to the phone number of the destination of the message. A transmission unit that transmits a link to a URI (Uniform Resource Identifier) indicating candidates for receiving,
An information processing apparatus comprising: a control unit that performs control for determining whether or not to transmit the message according to a result of user authentication based on the authentication method designated from the candidates. The message application is an application program for sending and receiving messages using RCS (Rich Communication Services) via a telecommunications carrier,
The transmission unit transmits the link to which key information associated with the telephone number is added,
Webhook information notified by the telecommunications carrier when content contained in a message sent using the message application is operated, the time stamp indicating the operation time at which the content was operated, and the content being operated. an acquisition unit that acquires Webhook information including the phone number of the communication terminal that has been received;
When the access to the link is executed, the access is executed based on the access time when the access to the link is executed, the key information given to the accessed link, and the Webhook information. Further comprising a determination unit that determines whether the communication terminal is the communication terminal that received the message,
The information processing device according to claim 1 . An information processing method performed by a computer,
Authentication by which the transmission unit authenticates whether the contractor of the telephone number is the user to whom the message is to be sent, using a message application installed in the communication terminal corresponding to the telephone number of the destination to which the message is to be sent. Send a link to a URI (Uniform Resource Identifier) showing a candidate for having the method specified,
An information processing method in which a control unit performs control to determine whether or not the message can be transmitted according to a result of user authentication performed based on the authentication method designated from the candidates. 3. A program for causing a computer to operate as the information processing apparatus according to claim 1 or 2, the program for causing the computer to function as each unit included in the information processing apparatus.

Images