Information processing system and information processing method

Abstract

To determine, when a message indicating a link has been sent using RCS or SMS, whether a communication device that has accessed the destination of the link has accessed from a link in the message that uses which of RCS or SMS.SOLUTION: An information processing system includes: a generation unit that generates a first message including content associated with information in which a first identifier and an RCS identifier are assigned to a URI, and a second message including information in which a second identifier is assigned to the URI; and a sorting processing unit that, when the URI is accessed, determines whether the RCS identifier is assigned to the accessed URI, performs a first process if the RCS identifier is assigned, and performs a second process different from the first process if the RCS identifier is not assigned.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing system and an information processing method. [Background technology]

[0002] There are electronic notification services that notify information online. Patent Document 1 discloses a technology for sending information to an email address that is likely to be immediately accessible by the recipient user.

[0003] Such electronic notification services may notify users of a message that includes a link to a website. For example, a message such as "Click here to check your registration details" may be sent along with a link to a website where the registration details can be checked. This allows users to keep the message concise while still being able to find detailed information on the website, thereby providing a service that is more convenient for users.

[0004] Another type of electronic notification service is a messaging service provided by a telecommunications carrier that sends messages to mobile phone numbers. Examples of messaging services that send messages to mobile phone numbers include RCS (Rich Communication Services) and SMS (Short Message Service). SMS and RCS have different specifications; for example, SMS can send text-only messages, while RCS can send messages that include images.

[0005] Because some users' mobile phones support RCS and others do not, a messaging service addressed to a mobile phone number may provide two types of messages. One is an RCS message sent using RCS, and the other is an SMS message sent using SMS. The service then requests the carrier to send RCS messages to mobile phones that support RCS and SMS messages to mobile phones that do not. This allows messages to be sent even if the recipient's email address is unknown, and also makes it possible to handle whether or not the recipient supports RCS. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-241732 Summary of the Invention [Problem to be solved by the invention]

[0007] However, when a message containing a link is sent using RCS or SMS, it is unclear whether the communication device that accessed the link came from an RCS or SMS message. RCS and SMS have different specifications. For example, with RCS, it is possible to determine whether an action corresponding to a read mark has been taken on the message, but with SMS, it is not possible to determine this. When a link is accessed, it is desirable to be able to distinguish between RCS messages, which indicate that an action such as a read mark has been taken, and SMS messages, which do not indicate this, and to handle them differently.

[0008] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an information processing system and an information processing method that, when a message containing a link is sent using RCS or SMS, can determine whether a communication device that accessed the linked destination accessed the link in the message using either RCS or SMS. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems, the information processing system of the present invention is an information processing system that sends a first message using RCS (Rich Communication Services) to a user terminal that supports RCS via a telecommunications carrier, and sends a second message using SMS (Short Message Service) to a user terminal that does not support RCS, and is equipped with a generation unit that generates the first message including content in which information in which a first identifier and an RCS identifier are assigned to a Uniform Resource Identifier (URI), and the second message including information in which a second identifier is assigned to the URI, and an allocation processing unit that, when access to the URI is performed, determines whether the RCS identifier is assigned to the accessed URI, and performs a first processing if the RCS identifier is assigned, and performs a second processing different from the first processing if the RCS identifier is not assigned.

[0010] In addition, in order to solve the above-mentioned problems, the information processing method of the present invention is an information processing method that sends a first message using RCS (Rich Communication Services) to a user terminal that supports RCS via a telecommunications carrier, and sends a second message using SMS (Short Message Service) to a user terminal that does not support RCS, in which a generation unit generates the first message including content in which information in which a first identifier and an RCS identifier are assigned to a URI (Uniform Resource Identifier) ​​is associated, and the second message including information in which a second identifier is assigned to the URI, and when access to the URI is performed, an allocation processing unit determines whether the RCS identifier is assigned to the accessed URI, and if the RCS identifier is assigned, performs a first processing, and if the RCS identifier is not assigned, performs a second processing that is different from the first processing. [Effects of the Invention]

[0011] According to the present invention, when a message containing a link is sent using RCS or SMS, it is possible to determine whether the communication device that accessed the link destination accessed it from a link in the message using RCS or SMS. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a block diagram showing an example of the configuration of an information processing system 1 according to an embodiment. [Figure 2] FIG. 2 is a diagram showing an example of distribution information 120 according to the embodiment. [Figure 3] FIG. 10 is a diagram showing an example of response information 121 according to the embodiment. [Figure 4] FIG. 2 is a diagram showing an example of an RCS message displayed on the user terminal 30 according to the embodiment. [Figure 5] FIG. 2 is a diagram showing an example of an RCS message displayed on the user terminal 30 according to the embodiment. [Figure 6] 10 is a diagram showing an example of information B# associated with a button B according to the embodiment. FIG. [Figure 7] FIG. 10 is a diagram illustrating an example of Webhook information WH according to an embodiment. [Figure 8] FIG. 2 is a diagram showing an example of an SMS message displayed on the user terminal 30 according to the embodiment. [Figure 9A] 2 is a sequence diagram showing the flow of processing performed by the information processing system 1 according to the embodiment. FIG. [Figure 9B] 2 is a sequence diagram showing the flow of processing performed by the information processing system 1 according to the embodiment. FIG. [Figure 10] 3 is a flowchart showing the flow of processing performed by the distribution server 10 according to the embodiment. [Figure 11] 3 is a flowchart showing the flow of processing performed by the distribution server 10 according to the embodiment. [Figure 12] 3 is a flowchart showing the flow of processing performed by the distribution server 10 according to the embodiment. [Figure 13]3 is a flowchart showing the flow of processing performed by the distribution server 10 according to the embodiment. [Figure 14] 4 is a flowchart showing the flow of processing performed by a Web server 40 according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0014] 1 is a block diagram showing an example of the configuration of an information processing system 1 according to an embodiment. The information processing system 1 includes, for example, a distribution server 10, a telecommunications carrier server 20, a user terminal 30, and a web server 40. These components of the information processing system 1 (the distribution server 10, the telecommunications carrier server 20, the user terminal 30, and the web server 40) are communicatively connected via a communication network NW.

[0015] The distribution server 10 is a server device managed by a business that provides a service for transmitting messages to the user terminal 30. The distribution server 10 transmits (distributes) messages to the user terminal 30 via the telecommunications carrier server 20. The distribution server 10 transmits RCS messages using RCS (Rich Communication Services), which is a message service addressed to a telephone number, or SMS messages using SMS (Short Message Service).

[0016] The telecommunications carrier server 20 is a server device managed by a telecommunications carrier. The telecommunications carrier is, for example, an MNO (Mobile Network Operator) that provides a communication service using a telephone number to the user terminal 30 using a communication line that the carrier owns or operates. The communication service includes communication using RCS and SMS. In response to a transmission request from the distribution server 10, the carrier server 20 transmits an RCS message or an SMS message to the user terminal 30. The carrier server 20 transmits an RCS message to a user terminal 30 that supports RCS, and transmits an SMS message to a user terminal 30 that does not support RCS. In a communication service using RCS, Webhook information for an RCS message sent to a user terminal 30 is sent to the distribution server 10 via the communication carrier server 20. The Webhook information is information indicating the status of the RCS message, for example, whether the RCS message has been received by the user terminal 30, or whether a button in the RCS message has been operated.

[0017] The user terminal 30 is a communication device, such as a smartphone or a mobile phone, that can be associated with a telephone number. A contract is made by a user or the like with a carrier of the telecommunications carrier server 20 to use a communication service using the user terminal 30. The user terminal 30 can communicate using the communication service provided by the contracted telecommunications carrier. A telephone number is assigned to the user terminal 30. Some user terminals 30 support SMS, but some support RCS and some do not. For example, if an RCS application is installed and activation, including consent to terms of use regarding communications using RCS, has been performed, the user terminal 30 is a terminal that supports RCS. On the other hand, if an RCS application is not installed, or if an RCS application is installed but not activated, the user terminal 30 is a terminal that does not support RCS. The user terminal 30 has, for example, a display unit such as a liquid crystal display and an operation unit such as a touch panel that accepts operations by a user. The user terminal 30 communicates using the communication network NW with the communication carrier server 20 and the user terminal 30 as communication partners. The user is, for example, a consumer.

[0018] Web server 40 is a server device managed by a business operator that operates a website. A URL (Uniform Resource Locator) is associated with each website. Web server 40 transmits information for displaying a screen corresponding to the website to a communication device that accesses the website by specifying the URL. A URL is an example of a "Uniform Resource Identifier (URI)."

[0019] As shown in Fig. 1, the distribution server 10 includes a communication unit 11, a storage unit 12, and a control unit 13. The communication unit 11 communicates with the telecommunications carrier server 20 and the web server 40. The storage unit 12 stores various information, for example, distribution information 120 and response information 121. The distribution information 120 is information related to RCS messages and SMS messages to be sent to the user terminal 30. The response information 121 is information related to responses to RCS messages sent to the user terminal 30.

[0020] The storage unit 12 is configured by a storage medium such as a hard disk drive (HDD), a flash memory, an electrically erasable programmable read-only memory (EEPROM), a random access read / write memory (RAM), a read-only memory (ROM), or any combination of these storage media. The storage unit 12 may be, for example, a nonvolatile memory.

[0021] The control unit 13 includes, for example, an acquisition unit 130, a generation unit 131, a determination unit 132, and a display control unit 133. The acquisition unit 130 acquires various types of information. For example, the acquisition unit 130 acquires information related to RCS messages and SMS messages generated by the generation unit 131 (described later), and stores the acquired information in the storage unit 12. By writing the information related to the RCS messages and SMS messages in the storage unit 12, it becomes possible to use this information as delivery information 120. Furthermore, the acquisition unit 130 acquires Webhook information received from the telecommunications carrier server 20, and stores the acquired Webhook information in the storage unit 12. By writing the Webhook information in the storage unit 12, it becomes possible to use this Webhook information as response information 121.

[0022] The generation unit 131 generates an RCS message. The RCS message is transmitted to the user terminal 30 that supports RCS. The generation unit 131 uses messages that can be used in RCS, such as a rich card (see FIG. 4) and a tip list (see FIG. 5), as the RCS message, and generates an RCS message that associates a website URL with content that can use these, such as a button B1 (see FIG. 4) or a button B2 (see FIG. 5). The generation unit 131 generates an SMS message. The SMS message is sent when the user terminal 30 does not support RCS. The generation unit 131 generates an SMS message consisting of text including a website URL. By sending a message including the URL of a website, access to the website specified by the URL is executed in response to a user operation. A specific method for generating a message by generation unit 131 will be described in detail later.

[0023] The determination unit 132 determines whether the communication device that has accessed the website is the user terminal 30 that sent the RCS message. If a message associated with the URL of a website is sent to the user terminal 30, the URL (Uniform Resource Locator) of the website may become known to other users, which may result in unauthorized access such as the website being viewed by other users. By determining whether the communication device that has accessed the website is the user terminal 30 that sent the RCS message, the determination unit 132 can prevent such unauthorized access. The specific method by which the determination unit 132 makes this determination will be described in detail later.

[0024] The display control unit 133 controls the content to be displayed on the communication device. The communication device here includes the user terminal 30 and the terminal devices of other users. If, based on the determination result by the determination unit 132, the communication device that has accessed the website is the user terminal 30 that sent the RCS message, the display control unit 133 causes the user terminal 30 to display a screen corresponding to the website. On the other hand, if the determination unit 132 determines that the communication device that has accessed the website is not the user terminal 30 that sent the message, the display control unit 133 causes the communication device that is not the user terminal 30 to display an error screen. The error screen is, for example, a screen indicating that the website cannot be accessed.

[0025] As shown in FIG. 1, the web server 40 includes, for example, a communication unit 41, a storage unit 42, and a control unit 43. The communication unit 41 communicates with the distribution server 10 and the user terminal 30 via the communication network NW. The storage unit 42 is configured with a storage medium and stores programs for executing various processes of the web server 40 and temporary data used when performing the various processes. The control unit 43 comprehensively controls the web server 40. The control unit 43 includes a website processing unit 430 and an allocation processing unit 431. The website processing unit 430 implements services provided by the website. For example, in response to an operation performed on a website screen, the website processing unit 430 transmits information for displaying a screen corresponding to the operation.

[0026] The sorting processor 431 performs processing on a communication device that has accessed a website by specifying its URL, depending on whether the communication device is a device that has accessed the website from a message using RCS. This allows the website to handle devices that have accessed the website from a message using RCS differently from devices that have not. For example, if the status of the RCS message can be grasped in detail, the device that has accessed the website from the RCS message can be determined to be a legitimate device and the website screen can be displayed on the device. On the other hand, if the status of the SMS message cannot be grasped in detail, the device that has accessed the website from the SMS message can be determined to be a legitimate device, and if it is determined to be a legitimate device, the website screen can be displayed on the device. The method by which the sorting processor 431 determines whether the communication device that has accessed the website by specifying its URL is a device that has accessed the website from an RCS message will be described in detail later.

[0027] 2 is a diagram showing an example of delivery information 120 according to an embodiment. The delivery information 120 is generated for each message. The delivery information 120 includes, for example, a case-specific identifier, a delivery unit-specific identifier, an individual-specific identifier, and information corresponding to each of the items RCS and SMS. The case-specific identifier is an ID (Identification) that identifies the category of the message to be sent. The delivery unit specific identifier is an ID that identifies the message to be sent. The individual specific identifier is information that can identify the user, such as a telephone number that is the destination of the message. The personal identifier is not limited to a telephone number as long as it is information that can at least identify the user. For example, key information linked to a telephone number or information that can identify the user can be used as the personal identifier. The RCS item stores information indicating the content of a message when an RCS message is sent to the user terminal 30. The SMS item stores information indicating the content of a message when an SMS message is sent to the user terminal 30.

[0028] The information stored in the RCS includes, for example, information corresponding to each item of buttons (button 1, button 2, . . . ). A button is content that can be included in a message and that can be operated by a user. A button includes, for example, information corresponding to a button ID, a URL, and postback data. The button ID is an ID that identifies the button set in the message. The URL is a URL that is accessed when the button is operated. The postback data is information included in the Webhook information. In other words, when the button is operated, Webhook information is sent from the telecommunications carrier server 20 to the distribution server 10, and the Webhook information includes the postback data set here.

[0029] In this embodiment, a first identifier is set in the postback data associated with the button. The first identifier is information that identifies a combination of (a case-specific identifier, a delivery unit-specific identifier, a button ID, and an individual-specific identifier). As a result, when the button is operated, Webhook information including the first identifier is sent from the telecommunications carrier server 20 to the distribution server 10. By receiving the Webhook information including the first identifier, the distribution server 10 can determine which button in which message sent to the user terminal 30 was operated.

[0030] In this embodiment, a first identifier is assigned 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 that identifies a combination of (a case-specific identifier, a delivery unit-specific identifier, a button ID, and an individual-specific identifier). The RCS identifier is information that identifies the message as having been sent using RCS. The first identifier in the postback data and the first identifier assigned to the URL may be information that can identify at least a combination of (a case-specific identifier, a delivery unit-specific identifier, a button ID, and an 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. By adding information (first identifier) ​​equivalent to the postback data to the URL, the first identifier can be used as a clue to determine using Webhook information whether the communication terminal that accessed the URL is a terminal that accessed it by operating the button on the RCS message.

[0031] Furthermore, in this embodiment, an RCS identifier is assigned to the URL associated with the button. By assigning an RCS identifier to the URL, it is possible to determine whether a communication terminal that has accessed by specifying a URL has accessed using the URL set in the RCS message, without using Webhook information.

[0032] The information stored in an SMS includes, for example, information corresponding to each of the following items: text and URL. The text is text information indicating the content of the message to be sent. The URL is a URL indicated in the message and is accessed by operating that URL. In this embodiment, a second identifier is assigned to the URL indicated in the SMS message. The second identifier is information that can determine whether the URL has been tampered with, such as a check digit of the URL. The check digit is an inspection code added to detect errors in the URL and is calculated by performing a specific calculation using the URL. By assigning the second identifier to the URL, it is possible to determine whether the communication terminal that has accessed the URL via an SMS message is an unauthorized terminal that has accessed the URL using a tampered URL.

[0033] In this embodiment, an RCS identifier is assigned to a URL notified in an RCS message, but an identifier (SMS identifier) ​​that identifies the message as an SMS message is not assigned to a URL notified in an SMS message. This is because there may be a limit on the number of characters that can be notified in an SMS message. For example, in some older models, SMS messages are divided into a predetermined number of characters (e.g., 70 characters) before being notified. Therefore, if a URL with a relatively long number of characters is notified in an SMS message, there is a possibility that the character string indicating the notified URL will be divided into multiple character strings before being notified. In SMS messages that have a limit on the number of characters or that may be divided, it is preferable to notify a message with as few characters as possible. For this reason, in this embodiment, an SMS identifier is not assigned to a URL notified in an SMS message.

[0034] 3 is a diagram illustrating an example of response information 121 according to an embodiment. The response information 121 is generated each time there is a reaction to an RCS message sent to the user terminal 30, that is, each time a button included in the RCS message is operated. The response information 121 includes, for example, information corresponding to each of the following items: a phone number, postback data, and a timestamp. This information in the response information 121, that is, information corresponding to each of the following items: a phone number, postback data, and a timestamp, is included in the Webhook information. The telephone number is the telephone number of the communication device on which the button was operated. The postback data is postback data associated with the button on which the operation was performed. The timestamp is information indicating the time when the button was operated.

[0035] The RCS messages applied in the information processing system 1 will be described with reference to FIGS. 4 and 5 are diagrams showing examples of RCS messages displayed on the user terminal 30 according to the embodiment. FIG. 4 shows an example of an RCS message using a rich card. The rich card shows an example in which a button B1 displaying the words "Register for My Page here" is set. FIG. 5 shows an example of an RCS message using a tip list. The tip list shows an example in which a button B2 displaying the words "Go to My Page (Login)" is set. Such buttons B (buttons B1 and B2) can be associated with information such as a URL and postback data. If a URL is associated with button B, when button B is operated, such as by tapping, the URL associated with button B is accessed. If postback data is associated with button B, when button B is operated, Webhook information including the postback data associated with button B is sent from the telecommunications carrier server 20 to the distribution server 10. In this embodiment, the generation unit 131 generates an RCS message in which the button B is associated with a URL to which the first identifier and the RCS identifier are assigned, and postback data including the first identifier.

[0036] FIG. 6 is a diagram showing an example of information B# associated with button B according to an embodiment. In FIG. 6, an example of information associated with button B1 shown in FIG. 4 or button B2 shown in FIG. 5 is shown as information B#. Information B# includes, for example, information corresponding to each item of URL and postback data. The URL is information indicating a specific website. An identifier is assigned to the URL. The identifier is information that identifies a combination of (project-specific identifier, delivery unit-specific identifier, button ID, individual-specific identifier). The postback data includes an identifier.

[0037] FIG. 7 is a diagram showing an example of Webhook information WH according to an embodiment. FIG. 7 shows an example of Webhook information WH sent from the telecommunications carrier server 20 to the distribution server 10 when button B associated with information B# shown in FIG. 6 is operated. The Webhook information WH includes information corresponding to each of the following items: phone number, postback data, timestamp, and RCS message ID. The phone number is a phone number assigned to a communication device on which button B is operated. The postback data is postback data associated with button B on which the operation was performed. The timestamp is the time when button B is operated. The RCS message ID is an ID that identifies an RCS message notified from the user terminal 30 to the telecommunications carrier server 20 when button B is operated. The RCS message ID is assigned by a telecommunications carrier.

[0038] The SMS message applied in the information processing system 1 will be described with reference to FIG. 8. FIG. 8 is a diagram showing an example of an SMS message displayed on the user terminal 30 according to the embodiment. As shown in FIG. 8, the SMS message displays a message in text. In this figure, a URL is displayed at the end along with a phrase such as "IR information has been disclosed." Furthermore, as shown in FIG. 8, a second identifier is assigned to the URL displayed in the SMS message according to the embodiment.

[0039] The processing performed by the information processing system 1 will be described with reference to Fig. 9 to Fig. 13. Fig. 9 (Fig. 9A and Fig. 9B) is a sequence diagram showing the flow of processing performed by the information processing system 1 according to the embodiment. The distribution server 10 generates a message (step S1). The distribution server 10 generates an RCS message that associates a button B with a URL to which a first identifier and an RCS identifier are assigned, and postback data including the first identifier. The distribution server 10 also generates an SMS message that includes a URL to which a second identifier is assigned. The distribution server 10 stores the generated RCS message and SMS message in the storage unit 12 as distribution information 120. The distribution server 10 makes a message transmission request to the carrier server 20 (step S2). Specifically, the distribution server 10 transmits the distribution information 120 to the carrier server 20, requesting that the user terminal 30 transmit a message.

[0040] The telecommunications carrier server 20 performs message delivery processing in response to the message transmission request received from the delivery server 10 (step S3). Specifically, the telecommunications carrier server 20 determines whether the user terminal 30 supports RCS, and transmits an RCS message to the user terminal 30 that supports RCS. It transmits an SMS message to the user terminal 30 that does not support RCS. The user terminal 30, which supports RCS, receives the RCS message from the telecommunications carrier server 20 (step S4). As a result, the RCS message is displayed on the display screen of the user terminal 30. The user operates button B provided in the RCS message, for example by tapping it (step S5). As a result, the user terminal 30 transmits control information (Webhook information) to the telecommunications carrier server 20 indicating that button B has been operated.

[0041] When the telecommunications carrier server 20 receives the control information indicating that button B has been operated, it generates Webhook information by, for example, adding an RCS message ID to the received control information, and sends the generated Webhook information to the distribution server 10 (step S6). When the distribution server 10 receives the Webhook information from the telecommunications carrier server 20, it stores the phone number, postback data, and timestamp extracted from the received Webhook information as response information 121 in the storage unit 12 (step S7).

[0042] On the other hand, in the process shown in step S5, when button B is operated, access to a website corresponding to the URL associated with button B is executed. In the example shown in this figure, before accessing the website, the user is temporarily guided to a specific site (or resource) owned by distribution server 10. That is, the site (or resource) owned by distribution server 10 is set as the URL. In this way, when button B is associated with access to a website, the URI (Uniform Resource Identifier) ​​of the resource to be temporarily used may be set instead of the URL.

[0043] When the distribution server 10 receives an access to a specific site or resource (hereinafter referred to as a site, etc.) owned by the distribution server 10, the distribution server 10 stores the access time in the storage unit 12 (step S8). The distribution server 10 extracts an identifier assigned to the URL corresponding to the received access from the URL (step S9). Based on the extracted identifier, the distribution server 10 references the corresponding response information 121 and performs a website display determination (step S10). The website display determination is a process of determining whether or not to display the website on the display screen of the accessing communication terminal. If the accessing communication device is a user terminal 30, the distribution server 10 determines that the website should be displayed on the display screen of the user terminal 30. On the other hand, if the accessing communication device is not a user terminal 30, the distribution server 10 determines that the website should not be displayed on the display screen of the user terminal 30. The details of the website display determination process will be described in detail later.

[0044] The distribution server 10 determines whether the result of the website display determination is OK or NG (step S11). Here, OK means that the website is displayed on the display screen of the user terminal 30. NG means that the website is not displayed on the display screen of the user terminal 30. If the result of the website display determination is NG, the distribution server 10 causes the user terminal 30 to display an error screen (step S12). The error screen is a screen that displays a message that the website cannot be accessed.

[0045] If the determination result of the website display determination is OK, the distribution server 10 requests the user terminal 30 to redirect (step S13). Specifically, the distribution server 10 transmits the URL of the website to the user terminal 30 and requests the user terminal 30 to access the transmitted URL. In this case, the distribution server 10 assigns an RCS identifier to the URL of the website transmitted to the user terminal 30. Upon receiving the redirect request from the distribution server 10, the user terminal 30 performs a redirect process (step S14). Specifically, the user terminal 30 accesses the website indicated in the URL. The flow of the process (symbol Y) from step S14 onwards will be described with reference to FIG. 9B.

[0046] On the other hand, if the user terminal 30 is determined not to support RCS in step S3, it receives an SMS message from the carrier server 20 (step S15). As a result, the SMS message is displayed on the display screen of the user terminal 30. The user operates the URL indicated in the SMS message, for example by tapping it (step S16). As a result, the user terminal 30 accesses the website indicated in the URL. The flow of the process (symbol X) from step S16 onwards will be described with reference to FIG. 9B.

[0047] As shown in FIG. 9B, by executing step S14 or step S16 (symbols X and Y), the web server performs a URL tampering determination process (step S17). The URL tampering determination process is a process for determining whether the URL notified from the accessing terminal has been tampered with. The URL tampering determination process will be described in detail later. The web server 40 determines whether the determination result of the URL tampering determination process is OK (step S18). If the URL has not been tampered with, the web server 40 determines that the determination result of the URL tampering determination process is OK. If the URL has been tampered with, the web server 40 determines that the determination result of the URL tampering determination process is NG. If the determination result of the URL tampering determination process is OK, the web server 40 displays a screen showing the website on the display screen of the user terminal 30. As a result, the website is displayed on the user terminal 30 (step S19). On the other hand, if the determination result of the URL tampering determination process is NG, the Web server 40 displays an error screen on the display screen of the user terminal 30.

[0048] In this embodiment, the screen showing the website may be, for example, an authentication screen. The authentication screen is a screen for verifying whether the operator of the communication terminal accessing the website is the user who sent the RCS message or SMS message.

[0049] Here, the authentication method candidates to be used on the authentication screen include, for example, public personal authentication, online personal authentication, carrier authentication, customer master authentication, and the like.

[0050] Public personal authentication is an authentication method that uses a personal card, which is a public certificate, to verify identity. More specifically, public personal authentication is an authentication method that uses JPKI (Public Personal Authentication Service). This public personal authentication uses a personal card. The personal card is, for example, an IC (integrated circuit) card that can store personal information. More specifically, an individual number card is used as the personal card. When performing public personal authentication, the user enters a password for using an electronic signature, and the individual number card is read by the user terminal 30. This causes the signature verification server (not shown) to process the public personal authentication. If the validity is confirmed, four basic pieces of information, such as the user's name, address, date of birth, and gender, can be obtained. Alternatively, the serial number of the electronic certificate used in the individual number card or its alternative information can be used to verify its validity for identity verification.

[0051] Online personal authentication is an authentication method that verifies an individual's identity online based on information that is different from that on a personal card and that includes at least an image of the individual's appearance (for example, face). Online personal authentication is also called "online identity verification using other official documents." The technology used for online personal authentication may be eKYC (electronic Know Your Customer). Online personal authentication may also use the My Number card described above to obtain information (four basic pieces of information) embedded in the IC chip.

[0052] Carrier authentication is an authentication method for verifying identity using carrier contract information relating to the contract between the contracted user and a telecommunications carrier of a communication terminal that provides communication services using a telephone number.

[0053] Customer master authentication is an authentication method that verifies the identity of a person using, for example, a customer master managed by the company that is the sender of the message. Customer master authentication is also sometimes called "authentication using a registered ID." The customer master is not limited to information managed by the company that is the sender of the message. For example, information managed by a company other than the sender of the message may be used as the customer master. Here, the company other than the sender of the message is, for example, a company that provides services used by a relatively large number of users, such as GAFA. In this way, customer master authentication may be performed using an account (customer master information) registered by a company other than the sender.

[0054] On the website, an authentication screen is displayed to prompt identity verification before a screen including the user's personal information, such as the user's My Page, is displayed on the user terminal 30. Then, after identity verification is performed and it is confirmed that the user is the user, the user's My Page, etc. is displayed on the user terminal 30.

[0055] FIG. 10 is a flow diagram showing the flow of processing performed by the distribution server 10 according to the embodiment. FIG. 10 shows the flow of processing for executing the website display determination shown in step S10 of FIG. 9A. First, the distribution server 10 executes processing for acquiring response information (step S100). Next, the distribution server 10 executes processing for verifying telephone numbers (step S101). Then, the distribution server 10 executes processing for comparing the operation time with the access time (step S102), and ends the processing and proceeds to step S11. The operation time here is the time when button B is operated. The access time is the time when the distribution server 10 receives access to a site, etc.

[0056] Fig. 11 is a flow diagram showing the flow of processing performed by the distribution server 10 according to the embodiment. Fig. 11 shows the flow of processing for acquiring response information shown in step S100 of Fig. 10. Here, response information 121 corresponding to access to a site or the like associated with button B is acquired.

[0057] Here, the operation on button B and the access to the site, etc. associated with button B are performed almost simultaneously. In other words, it is highly likely that the timing at which the distribution server 10 receives Webhook information from the telecommunications carrier server 20 due to the operation on button B and the timing at which the distribution server 10 receives access to a specific site, etc. owned by the distribution server 10 will be almost the same. For example, there may be a delay in the timing at which the distribution server 10 receives the Webhook information due to reasons such as the telecommunications carrier server 20 taking time to generate the Webhook information or congestion on the communication line between the telecommunications carrier server 20 and the distribution server 10. In this case, the distribution server 10 may receive access to the site, etc. before the telecommunications carrier server 20 receives the Webhook information.

[0058] If access to a site or the like is received before receiving Webhook information, there will be a period of time during which response information 121 corresponding to the access is not stored in the storage unit 12. In this case, it will be difficult for the distribution server 10 to distinguish whether the corresponding response information 121 is not stored in the storage unit 12 because the timing of receiving the Webhook information was delayed, or whether the corresponding response information 121 is not stored in the storage unit 12 because button B was not operated. As a countermeasure, in this embodiment, if the response information 121 corresponding to the access is not stored, the distribution server 10 performs a retry after a predetermined waiting time (for example, one second) has elapsed, in which the distribution server 10 refers to the storage unit 12 again and checks whether the response information 121 corresponding to the access is stored. If the result of the retry is that the corresponding response information 121 is stored in the storage unit 12, the distribution server 10 acquires the corresponding response information 121. This makes it possible to acquire the response information 121 corresponding to the access even if the access is performed before receiving the Webhook information. If the number of retries reaches a predetermined threshold (for example, three times) or more and the corresponding response information 121 is not stored in the storage unit 12, the distribution server 10 determines that no operation has been performed on the button B and that the corresponding response information 121 is not stored in the storage unit 12. As a result, if there is a high possibility that the URL has been accessed by another user's communication device, it can be considered as an unauthorized access and suppressed.

[0059] First, the distribution server 10 initializes the number of retries as a variable to 0 (zero) (step S1001). Next, the distribution server 10 refers to the 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 corresponding response information 121 is stored, the distribution server 10 ends the process and proceeds to step S101. If corresponding response information 121 is not stored, the distribution server 10 increments the number of retries (S1003). The distribution server 10 determines whether or not the number of retries is less than a threshold (step S1004). If the number of retries is less than the threshold, the distribution server 10 determines whether or not a waiting time has elapsed (step S1005). If the waiting time has elapsed, the distribution server 10 returns to step S1002. On the other hand, if the number of retries is equal to or greater than the threshold value in step S1004, the distribution server 10 determines the result as NG (step S1006), ends the process, and proceeds to step S11.

[0060] Fig. 12 is a flow diagram showing the flow of processing performed by the distribution server 10 according to the embodiment. Fig. 12 shows the flow of processing for executing the process of verifying the phone number shown in step S101 of Fig. 10. Here, the verification is performed by matching the phone number included in the Webhook information with the phone number or individual identifier included in the identifier assigned to the URL.

[0061] First, the distribution server 10 extracts response information 121 corresponding to the identifier assigned to the URL (step S1011). Specifically, the distribution server 10 refers to the storage unit 12 and extracts, from the information stored as the response information 121, response information 121 including postback data having an identifier corresponding to the identifier assigned to the URL. The distribution server 10 determines whether the telephone numbers match (step S1012). The distribution server 10 compares the telephone number in the extracted response information 121 with the telephone number (production control number) included in the identifier assigned to the URL. For example, the distribution server 10 determines whether the two telephone numbers match. If the telephone numbers match, the distribution server 10 terminates the process and proceeds to step S102. If the telephone numbers do not match, the distribution server 10 determines that the determination result is NG (step S1013), terminates the process, and proceeds to step S11. Alternatively, in step S1012, the distribution server 10 may determine whether the personal identifier included in the personal identifier Webhook information (referred to as first information) and the information corresponding to the telephone number included in the identifier assigned to the URI (referred to as second information) indicate that they are information linked to the same user. If the first information and the second information are consistent and indicate that they are information linked to 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 that the determination result is NG (step S1013), terminates the process, and proceeds to step S11.

[0062] Fig. 13 is a flow diagram showing the flow of processing performed by the distribution server 10 according to the embodiment. Fig. 13 shows the flow of processing for executing the process of comparing the operation time and the access time shown in step S102 of Fig. 10. Here, the operation time when button B is operated is compared with the access time when a site or the like is accessed.

[0063] First, the distribution server 10 acquires the access time (step S1021). The distribution server 10 refers to the storage unit 12 and acquires the access time stored in step S8. The distribution server 10 acquires the operation time indicated in the timestamp in the response information 121 acquired in step S1011 (step S1022). The distribution server 10 determines whether the access time is later than the operation time (step S1023). If the access time is later than the operation time, the distribution server 10 determines whether the access time is earlier than (the operation time + the allowed time) (step S1024). If the access time is earlier than (the operation time + the allowed time), the distribution server 10 determines the determination result as OK (step S1025), ends the process, and proceeds to step S11. On the other hand, if the distribution server 10 determines in step S1023 that the access time is earlier than the operation time, or if it determines in step S1024 that the access time is later than (the operation time + the allowed time), it determines the result as NG (step S1026), terminates the processing, and proceeds to step S11.

[0064] FIG. 14 is a flow diagram showing the flow of processing performed by the web server 40 according to the embodiment. FIG. 14 shows the flow of the URL tampering determination processing shown in step S17 of FIG. 9B. Here, when a URL is accessed via an SMS message, it is determined whether the URL has been tampered with. On the other hand, when a URL is accessed via an RCS message, it is not determined whether the URL has been tampered with. Alternatively, as a simple check, a determination process different from the determination process performed for SMS messages may be performed. This is because when a URL is accessed via an RCS message, the process for determining whether the website is displayed shown in step S10 described above is performed, and it has been verified that the URL was accessed by operating the button provided in the RCS message, and therefore the URL tampering determination process is considered unnecessary.

[0065] First, the Web server 40 acquires the URL notified by the accessing communication terminal (step S170). The Web server 40 determines whether an RCS identifier is assigned to the acquired URL (step S171). If an RCS identifier is not assigned to the URL, the Web server 40 determines whether the URL has been tampered with (step S172). The Web server 40 determines whether the URL has been tampered with using the second identifier assigned to the URL. Specifically, the Web server 40 calculates a check digit for the URL and compares the calculated check digit with the second identifier. If the check digit and the second identifier match, the Web server 40 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 40 determines that the URL has been tampered with. If the URL has been tampered with, the Web server 40 determines that the URL tampering determination process result is NG, terminates the process, and proceeds to step S18. On the other hand, if an RCS identifier is assigned to the URL in step S171, or if it is determined in step S172 that the URL has not been tampered with, the Web server 40 determines the result of the URL tampering determination process as OK, terminates the process, and proceeds to step S18.

[0066] As described above, the information processing system 1 according to the embodiment is a system that transmits an RCS message (an example of a first message) to a user terminal that supports RCS via a telecommunications carrier, and transmits an SMS message (an example of a second message) to a user terminal that does not support RCS. The information processing system 1 includes a generation unit 131 and an allocation processing unit 431. The generation unit 131 generates an RCS message including a button (an example of content). The button is associated with information in which a URL (an example of a URI) is assigned a first identifier and an RCS identifier. The generation unit 131 generates an SMS message including information in which a URL is assigned a second identifier. When a URL is accessed, the allocation processing unit 431 determines whether an RCS identifier is assigned to the URI notified by the access. If an RCS identifier is assigned to the URL, the allocation processing unit 431 performs processing (an example of a first processing) to display a screen corresponding to the website, such as an authentication screen. If an RCS identifier is not assigned to the URL, the allocation processing unit 431 performs processing (an example of a second processing) to determine whether the URL has been tampered with. As a result, the information processing system 1 according to the embodiment can determine whether an accessing communication terminal accessed the URL from a link in a message using either RCS or SMS, based on whether an RCS identifier is assigned to the URL. Therefore, when a message containing a link is sent using either RCS or SMS, it can determine whether a communication device that accessed the linked destination accessed the URL from a link in a message using either RCS or SMS.

[0067] Furthermore, in the information processing system 1 of the embodiment, the second identifier includes a check digit calculated from the URL. As a URL tampering determination process, the sorting processor 431 calculates a check digit from the URL and compares the calculated check digit with the check digit included in the second identifier to determine whether the URL has been tampered with. As a result, in the information processing system 1 of the embodiment, when a website is accessed from an SMS message, it can determine whether the URL notified as a link destination has been tampered with.

[0068] Furthermore, in the information processing system 1 according to the embodiment, the generation unit 131 generates an RCS message in which postback data including a first identifier is associated with a button. By creating such a message, when a button in the RCS message is operated, the telecommunications carrier server 20 notifies the telecommunications carrier server 20 of Webhook information indicating that the button was operated, the Webhook information including the postback data. The information processing system 1 further includes a determination unit 132. When a URL is accessed, the determination unit 132 determines whether Webhook information corresponding to the access to the URL has been notified based on the first identifier. When the determination unit 132 determines that Webhook information corresponding to the access to the URL has been notified, the allocation processing unit 431, as a first process, displays a screen corresponding to the website on the communication terminal that accessed the URL. This allows the information processing system 1 according to the embodiment to use the Webhook information to determine whether the access was made by operating a button in the RCS message. Therefore, it is possible to accurately determine that the access came from the user terminal 30 that received the RCS message.

[0069] The information processing system 1, distribution server 10, and web server 40 in the above-described embodiments may be implemented in whole or in part by a computer. In this case, a program for implementing the functions may be recorded on a computer-readable recording medium, and the program may be loaded into the computer system and executed. Note that the term "computer system" as used herein includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into the computer system. Furthermore, the term "computer-readable recording medium" may also include devices that dynamically store programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, or devices that store programs for a fixed period of time, such as volatile memory within the computer system serving as the server or client. The program may be designed to implement some of the functions described above, or may be capable of implementing the functions in combination with a program already stored in the computer system, or may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0070] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention. [Explanation of symbols]

[0071] 1...information processing system, 10...distribution server, 20...telecommunications carrier server, 30...user terminal, 40...web server, 11...communication unit, 12...storage unit, 120...distribution information, 121...response information (webhook information), 13...control unit, 130...acquisition unit, 131...generation unit, 132...determination unit, 133...display control unit, 431...allocation processing unit

Claims

1. An information processing system that transmits a first message using Rich Communication Services (RCS) to a user terminal that supports RCS via a telecommunications carrier, and transmits a second message using Short Message Service (SMS) to a user terminal that does not support RCS, a generating unit that generates the first message including content in which information in which a first identifier and an RCS identifier are assigned to a Uniform Resource Identifier (URI) is associated with the first message, and the second message including information in which a second identifier is assigned to the URI; an allocating processor that, when the URI is accessed, determines whether the RCS identifier is assigned to the accessed URI, performs a first process if the RCS identifier is assigned, and performs a second process different from the first process if the RCS identifier is not assigned; An information processing system comprising:

2. the second identifier includes a check digit calculated from the URI; As the second process, the sorting processing unit calculates a check digit from the URI and compares the calculated check digit with a check digit included in the second identifier to determine whether the URI has been tampered with. The information processing system according to claim 1 .

3. the generating unit generates the first message by associating the content with postback data including the first identifier; When the content in the first message is operated, the telecommunications carrier notifies the user of Webhook information indicating that the content has been operated, the Webhook information including the postback data; a determination unit that, when access to the URI is executed, determines whether or not the Webhook information corresponding to the access to the URI has been notified based on the first identifier; When the determination unit determines that the Webhook information corresponding to the access to the URI has been notified, the allocation processing unit, as the first process, causes the communication terminal that has accessed the URI to display a screen corresponding to a website.

3. The information processing system according to claim 1.

4. An information processing method for transmitting a first message using Rich Communication Services (RCS) to a user terminal that supports RCS via a telecommunications carrier, and transmitting a second message using Short Message Service (SMS) to a user terminal that does not support RCS, a generation unit generates the first message including content in which information in which a first identifier and an RCS identifier are assigned to a Uniform Resource Identifier (URI) is associated with the first message, and the second message including information in which a second identifier is assigned to the URI; When the URI is accessed, the sorting processing unit determines whether the RCS identifier is assigned to the accessed URI, and if the RCS identifier is assigned, performs a first process, and if the RCS identifier is not assigned, performs a second process different from the first process. Information processing methods.

Images