Message management systems, message management methods, programs

Abstract

It offers flexibility in specifying the elements to be included in the message while reducing the burden on the requester. [Solution] The system includes: a first acquisition unit that obtains a notification content display pattern from a requester requesting the sending of a message, which specifies which of several different elements the message should include; a second acquisition unit that obtains from the requester the embedded data to be embedded in the elements included in the notification content display pattern and the message recipient; a second message transmission unit that sends a confirmation message to the destination terminal device to verify the user's identity; an authentication unit that determines whether the user is the person in question based on the data transmitted from the terminal device that received the confirmation message; and, if the user is determined to be the person in question, a first message transmission unit that makes the message with the embedded data embedded in the notification content display pattern viewable by the destination terminal device.

Description

Technical Field

[0001] The present invention relates to a message management system, a message management method, and a program.

Background Art

[0002] There is an electronic notification service for notifying information online. In Patent Document 1, a technique for transmitting information to an email address with a high probability that the recipient user can immediately view it is disclosed.

[0003] Such an electronic notification service includes a message service that uses a mobile phone number provided by a telecommunications carrier as the destination. Examples of message services that use a mobile phone number as the destination include RCS (Rich Communication Services) and SMS (Short Message Service). By using a mobile phone number as the destination, a message can be sent even if the email address of the recipient is unknown. For example, there is a message distribution system that receives a message transmission request from a requester who requests message transmission and sends a message to a target terminal device.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] [[ID=四十]] However, depending on the matter to be notified to the user, the requester may want to change the target elements included in the message. For example, the requester may want to send a message that includes only the notification content represented by text or the like, or may want to send a message that includes a link button that can guide to another external site. In such cases, the requesting party has to generate a message that includes content tailored to the specific target elements for each user it is intended for, and then request the sending company to send the message. This is burdensome because the sender must rearrange the elements according to the content of the message notification.

[0006] This invention has been made in view of these circumstances, and its purpose is to provide a message management system, a message management method, and a program that can flexibly respond to the specification of elements to be included in a message while reducing the burden on the requester. [Means for solving the problem]

[0007] To solve the above-mentioned problems, one aspect of the present invention is a message management system comprising: a first acquisition unit that acquires a notification content display pattern from a requester requesting the sending of a message, which specifies which of a plurality of different elements the message should include; a second acquisition unit that acquires from the requester the embedding data to be embedded in the elements included in the notification content display pattern and the destination of the message; a second message transmission unit that sends a confirmation message to the destination terminal device to verify the identity of the user; an authentication unit that determines whether or not the user is the person in question based on data transmitted from the terminal device that received the confirmation message; and a first message transmission unit that, if it is determined that the user is the person in question, transmits a message in which the embedding data is embedded in the notification content display pattern to the destination terminal device so that it can be viewed.

[0008] Furthermore, one aspect of the present invention is a message management method performed by a computer, which includes obtaining a notification content display pattern from a requester requesting the transmission of a message, specifying which of a plurality of different elements the message should include; obtaining from the requester the embedding data to be embedded in the elements included in the notification content display pattern and the destination of the message; sending a confirmation message to the destination terminal device to verify the identity of the user; determining whether the user is the person in question based on the data transmitted from the terminal device; and, if the user is determined to be the person in question, sending a message with the embedding data embedded in the notification content display pattern to the destination terminal device and making it viewable.

[0009] Furthermore, one aspect of the present invention is a program executed by a computer that includes obtaining a notification content display pattern from a requester requesting the transmission of a message, which specifies which of a plurality of different elements the message should include; obtaining from the requester the embedding data to be embedded in the elements included in the notification content display pattern and the destination of the message; sending a confirmation message to the destination terminal device to verify the identity of the user; determining whether the user is the person in question based on the data transmitted from the terminal device; and, if the user is determined to be the person in question, sending a message with the embedding data embedded in the notification content display pattern to the destination terminal device and making it viewable. [Effects of the Invention]

[0010] As explained above, this invention allows for flexible handling of the elements to be included in the message while reducing the burden on the requesting party. [Brief explanation of the drawing]

[0011] [Figure 1]This is a schematic block diagram showing the configuration of a message distribution system S according to one embodiment of the present invention. [Figure 2] This figure shows an example of master information stored in the Message Management System 1. [Figure 3] This figure shows an example of elements included in a notification content display pattern. [Figure 4] This diagram illustrates an example of element ID combinations included in notification content display patterns. [Figure 5] This figure shows an example of transaction data. [Figure 6] This is a schematic functional block diagram explaining the functions of Message Management System 1. [Figure 7] This is a sequence diagram illustrating the operation of the message delivery system S. [Figure 8] This is a sequence diagram illustrating the operation of the message delivery system S. [Figure 9] This figure shows an example of a display screen where the second message is shown. [Figure 10] This figure shows an example of a display screen where the second message is shown. [Figure 11] This figure shows an example of a display screen where the second message is shown. [Figure 12] This figure shows an example of a display screen where the second message is shown. [Figure 13] This figure shows an example of a display screen where the second message is shown. [Figure 14] This figure shows an example of a display screen where the second message is shown. [Modes for carrying out the invention]

[0012] A message distribution system S according to one embodiment of the present invention will be described below with reference to the drawings. Figure 1 is a schematic block diagram showing the configuration of the message distribution system S according to one embodiment of the present invention. The message delivery system S includes a message management system 1, a corporate server 2, a plurality of communication carrier servers 3 (for example, communication carrier server 3a, communication carrier server 3b), a plurality of terminal devices 4 (for example, terminal device 4a, terminal device 4b), a settlement server 5, a web server 6, and a form server 7.

[0013] The message management system 1 is a system managed by an operator that provides a service for transmitting messages to the terminal device 4. The message management system 1 transmits messages to the terminal device 4 via the communication carrier server 3. The message management system 1 transmits RCS (Rich Communication Services) messages using RCS, which is a message service with a telephone number as the destination, or SMS (Short Message Service) messages using SMS. The message management system 1 communicates wirelessly or wiredly with the corporate server 2 and the communication carrier server 3.

[0014] The message management system 1 can transmit messages to the terminal device 4. The messages include a first message and a second message. The first message is a message transmitted to the terminal device when access to the authentication base server can be made based on the authentication URL and the identity verification is successful. For example, when electronically notifying content such as a parent exhibition, the first message can be viewed after the identity verification is successful. The second message is a message transmitted separately from the first message to confirm whether the user is the target of the first message or not.

[0015] Also, the first message can be of any content as long as it is notified from the corporate server 2 to the user, and it can also be related to the contract of the service provided from the requester, which is the company of the corporate server 2, to the user. More specifically, the first message may be a demand letter urging payment of fees, etc. Such a demand letter may be related to a credit service (e.g., cash advances) provided by the corporate server 2.

[0016] The message management system 1 includes a management server 10, a distribution infrastructure server 11, and an authentication infrastructure server 12. The management server 10 stores master information registered from the enterprise server 2, as well as transaction data. Figure 2 shows an example of master information stored in the message management system 1. Master information may be registered separately for each company on the corporate server 2, or separate master information may be registered for different message sets within a single company. Master information includes scenario information, notification content display patterns, and authentication patterns.

[0017] Scenario information is information that defines the first message and specifies the order in which messages should be sent based on responses from terminal device 4 to the first message that was sent. The notification content display pattern is a template data that specifies which of several different elements should be included in a message (the first message), as requested by the sender of the message. The notification content display pattern can be selected by the sender of the message.

[0018] An authentication pattern is an item used for authentication when verifying an individual's identity. More specifically, the identity verification process involves the authentication infrastructure server 12 sending questions to the terminal device 4, the terminal device 4 sending back the entered answers, and determining that the user of terminal device 4 is the legitimate individual if the answers match predetermined correct answer data, and determining that the user of terminal device 4 is not the legitimate individual if the answers do not match the correct answer data. The items used as the authentication pattern may be, for example, the "katakana" of the user's last name, the postal code corresponding to the user's address, or the beginning part of the user's address (for example, up to the city / ward / town / village). The authentication pattern is data that specifies which items to use as questions in this identity verification process.

[0019] Figure 3 shows an example of elements included in a notification content display pattern. Elements come in several different types. Each element has a unique identifier called an element ID. It will be assigned. Figure 3 shows the relationship between element IDs and their content, illustrating examples with element IDs from "0" to "4".

[0020] (A) Element ID "0": A display screen that appears after authentication and does not contain buttons to transition to other actions. The element with element ID "0" specifies that a display screen should be shown that does not include functions such as transitioning to other websites or sending instructions to generate PDF data. The display screen may contain text, tables, graphics, images, etc. More specifically, it may be a display screen that describes the contract date, payment amount, payee, contact information, etc.

[0021] (B) Element ID "1": An element that transitions to specific static content. For example, element ID "1" is an element that specifies that the first message should contain a link button that transitions to the site indicated by the specified URL. This link button may contain a URL that transitions to a website provided by corporate server 2 or a website provided by web server 6. Specifically, element ID "1" may include an FAQ page provided by corporate server 2 or various announcement pages provided by web server 6.

[0022] (C) Element ID "2": Operation button that enables single sign-on integration for pages that require login to the user's individual user page, etc. For example, element ID "2" specifies that the first message should contain a button to log in to a page exclusively for users where they can check their payment status and notifications about their next billing date.

[0023] (D) Element ID "3": An element that transitions to a payment site where payment can be made. For example, element ID "3" is an element that specifies that an operation button should be set in the first message, which, when incorporated into the message, will allow the necessary payment to proceed quickly. Such a payment site may be, for example, a payment site published by payment server 5. The server accessed in response to the operation button set based on element ID "3" being operated may also be payment server 5.

[0024] (E) Element ID "4": Linking and downloading files such as PDF (Portable Document Format). For example, element ID "4" may be an operation button that instructs the generation of a file in a specific file format. Specifically, it is an element that specifies that a file should be generated in PDF format, which will serve as a payment reminder notice, and that an operation button for linking and downloading this file should be set as the first message. The server that generates the PDF data in response to the input of an instruction to generate PDF data via the operation button set based on element ID "4" may be the document server 7.

[0025] The five types of elements mentioned above are just examples; other types of elements may also be used. Furthermore, if each of these elements is assigned an ID, the notification content display pattern may be data that specifies which elements should be included in the notification content by including at least one element ID.

[0026] Figure 4 illustrates an example of a combination of element IDs included in a notification content display pattern. Each notification content display pattern includes at least one element ID, and the element ID determines which element is included. Examples of notification content display patterns include patterns containing only one element ID "0", patterns containing one element ID "0" and one element ID "3", patterns containing one element ID "0", one element ID "3", and one element ID "4", patterns containing one element ID "0", one element ID "1", and one element ID "1", and patterns containing only one element ID "4". These notification display patterns can be specified from the corporate server 2. Furthermore, combinations of elements included in the notification content display pattern may be newly registered in response to a request from the administrator of the corporate server 2 and made available as specified by the corporate server 2. Furthermore, there may be rules when defining the notification content display patterns. For example, there may be rules such as not being able to register a notification content display pattern as a combination containing multiple elements if element ID "0" is not included, or that element ID "4" can be combined with other elements but cannot be included multiple times.

[0027] Figure 5 shows an example of transaction data. Transaction data is data relating to the content of the message to be sent to terminal device 4. More specifically, transaction data includes the message recipient, correct answer data, and embedded data. The recipient of the message can, for example, be the telephone number assigned to the terminal device 4 to which the message is to be sent. The correct answer data is data that shows the correct answers to the questions defined in the authentication pattern. Embedded data is the data to be embedded in the elements included in the notification content display pattern.

[0028] Embedded data is the data that constitutes the content to be notified as the first message. Among the embedded data, the embedded data corresponding to element ID "0" includes, for example, text, images, etc. The embedded data corresponding to element ID "1" is, for example, a string indicating the URL of the homepage published by the company on company server 2, or a string indicating the URL of the FAQ (Frequently Asked Questions) page regarding the services or products provided by the company on company server 2. The embedded data corresponding to element ID "2" is, for example, data used to execute a function for logging into a user page via single sign-on. The embedded data corresponding to element ID "3" is a string of characters indicating a URL to access a payment site where payment processing such as fee payments can be performed. The embedded data corresponding to element ID "4" is data used to execute the function of generating, linking, and downloading PDF data. The embedded data is prepared in advance on the corporate server 2, containing data corresponding to each element specified by the notification content display pattern of the master information, and is registered in the message management system 1. Alternatively, the message management system may prepare the necessary data from the master information.

[0029] These transaction data can utilize user information registered when a user enters into a contract or applies for the provision of services with the company operating the corporate server 2. User information includes the telephone number assigned to the terminal device 4 used by the user, the user's name, postal code, address, date of birth, gender, etc. For example, corporate server 2 can use the telephone number from the user information as the destination for sending messages. In addition, some of the user information, such as name, address, and date of birth, can be used as correct answer data. In this way, when corporate server 2 sends the first message to multiple users, it can generate and register transaction data for each target user.

[0030] The following describes how such master information and transaction data may be stored in the management server 10. However, they may also be sent from the management server 10 to the distribution infrastructure server 11 and the authentication infrastructure server 12, respectively, so that they are stored in the distribution infrastructure server 11 and the authentication infrastructure server 12.

[0031] Returning to Figure 1, the distribution infrastructure server 11 sends the second message to the terminal device 4 via the telecommunications carrier server 3. The authentication infrastructure server 12 performs authentication to verify that the user assigned a phone number who is the same user as the user expected by the company is indeed the person in question. For example, the distribution infrastructure server 11 sends a message (second message) to the terminal device 4 to verify whether the user is the person expected to receive the message. If the authentication infrastructure server 12 verifies the user's identity, it generates the first message by embedding the transaction data into a notification content display pattern based on the master information and transaction data, and sends the generated message (first message) to the terminal device 4 via the telecommunications carrier server 3. The distribution infrastructure server 11 also sends the second message to the terminal device 4 via the telecommunications carrier server 3. The authentication infrastructure server 12 performs authentication processing to verify that the user assigned a phone number is indeed the same user as the one expected by the company. For example, the distribution infrastructure server 11 sends a message (second message) to the terminal device 4 to verify whether the user is the person expected to receive the message. If the authentication infrastructure server 12 can verify the user's identity, it receives a control signal from the authentication infrastructure server 12 indicating that the user's identity has been verified. Upon receiving this control signal, the distribution infrastructure server 11 sends a message (first message) requested by the company server 2 to the terminal device.

[0032] Enterprise Server 2 is a server device managed by a requester who requests the message delivery system S to deliver RCS messages or SMS messages to recipient users. The requester is, for example, a company or organization that provides information to recipient users (e.g., a bank, an insurance company, etc.). Enterprise Server 2 communicates with the message management system 1 via wireless or wired communication. If there are multiple requesters who wish to have messages delivered to the message delivery system S, multiple corporate servers 2, each assigned to a requester, may be connected to the message delivery system S. For example, if there are two companies requesting message delivery, two corporate servers 2, such as corporate server 2a and corporate server 2b, may be provided.

[0033] The carrier server 3 (carrier server 3a, carrier server 3b) is a server device managed by a carrier. The carrier is, for example, an MNO (Mobile Network Operator) that provides telephone number-based communication services to terminal devices 4 using communication lines it owns or operates. Communication services include communication using RCS or SMS. The communication carrier server 3 sends an RCS message or an SMS message to the terminal device 4 in response to a transmission request from the message management system 1.

[0034] The telecommunications carrier server 3 stores carrier contract information in its storage unit, relating to contracts with users who have entered into agreements to use the terminal device 4. Carrier contract information includes, for example, the user's telephone number, name, postal code, address, date of birth, etc. Furthermore, carrier contract information may also include customer information about the user registered with the messaging service or other services used by the user. The telecommunications carrier server 3 communicates wirelessly or via wired connection with the message management system 1 and the terminal device 4. In this case, if there are multiple telecommunications carriers, a separate telecommunications carrier server 3 is provided for each carrier. Telecommunications carrier server 3a is managed by the first telecommunications carrier, and telecommunications carrier server 3b is managed by the second telecommunications carrier. Hereafter, unless a specific telecommunications carrier server is identified, it will be referred to as telecommunications carrier server 3.

[0035] Terminal device 4 is a communication device such as a smartphone or mobile phone. A user enters into a contract with the telecommunications carrier server 3 to use communication services provided by the contracted telecommunications carrier. Terminal device 4 can communicate using the communication services provided by the contracted telecommunications carrier. Terminal device 4 is assigned a telephone number and has the function of communicating using this telephone number as the destination, i.e., communication using RCS or SMS. Terminal device 4 has, for example, a display unit such as a liquid crystal display and an operation unit such as a touch panel that accepts user input. Terminal device 4 communicates using a communication network with the communication carrier server 3 as its communication partner. The user is, for example, a consumer.

[0036] Figure 6 is a schematic functional block diagram illustrating the functions of the message management system 1. The message management system 1 includes a storage unit 100, an acquisition unit 101, an authentication unit 102, a message generation unit 103, and a message transmission unit 104. The memory unit 100 stores master information and transaction data. The acquisition unit 101 has a first acquisition unit 1011 and a second acquisition unit 1012, and acquires various types of data. The first acquisition unit 1011 acquires the notification content display pattern from the corporate server 2. The second acquisition unit 1012 acquires the embedded data and the message recipient from the requester.

[0037] The authentication unit 102 receives a confirmation message to the destination terminal device to which the message is to be sent, and determines whether or not the user is the correct person based on the data transmitted from the terminal device. The message generation unit 103 generates a first message by embedding transaction data in accordance with the elements specified in the notification content display pattern of the master information, based on the master information and transaction data stored in the storage unit 100. The message transmission unit 104 transmits various messages. The message transmission unit 104 includes a first message transmission unit 1041 and a second message transmission unit 1042. If the first message transmission unit 1041 determines that the recipient is the person in question, it sends a message containing embedded data in the notification content display pattern to the destination terminal device, making it viewable. The first message transmission unit 1041 embeds embedded data indicating the content based on the contract into the notification content display pattern, and sends the first message to the target terminal device that has been determined to be the user, making it viewable. The first message transmission unit 1041 may transmit the first message via the telecommunications carrier server 3 or without the telecommunications carrier server 3, as long as it can deliver the first message to the destination terminal device. The second message transmission unit 1042 sends a confirmation message (second message) to the destination terminal device to verify the user's identity.

[0038] The storage unit 100, acquisition unit 101, authentication unit 102, message generation unit 103, and message transmission unit 104 described above may be provided in any one of the management server 10, distribution infrastructure server 11, and authentication infrastructure server 12, or they may be provided in a different device that belongs to the message management system 1 (for example, a server device). Furthermore, the storage unit 100, acquisition unit 101, authentication unit 102, message generation unit 103, and message transmission unit 104 may be provided on a single server device, or at least one of these functions may be provided on a separate server device connected to the management server 10, distribution infrastructure server 11, or authentication infrastructure server 12 via a communication network. In this case, the server device may be a physical server or a cloud server provided by a cloud computing service.

[0039] The storage unit 100 is composed of a storage medium, such as an HDD (Hard Disk Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read / write Memory), ROM (Read Only Memory), or any combination of these storage media. This storage unit 100 can, for example, use non-volatile memory.

[0040] The acquisition unit 101, authentication unit 102, message generation unit 103, and message transmission unit 104 may be composed of a processing unit such as a CPU (Central Processing Unit) or a dedicated electronic circuit.

[0041] Figure 7 is a sequence diagram illustrating the operation of the message distribution system S. This Figure 7 shows a sequence diagram related to the process of registering master information and transaction data. Here, the enterprise server 2a sends master information, including scenario information, notification content display patterns, and authentication patterns corresponding to the messages it distributes, to the management server 10 of the message management system 1 (step S001). When the management server 10 receives the master information from the enterprise server 2a, it stores the received master information (step S101) and then sends the master information to the distribution infrastructure server 11. When the distribution infrastructure server 11 receives the master information from the management server 10, it stores the received master information (step S201) and then sends the master information to the authentication infrastructure server 12. When the authentication infrastructure server 12 receives the master information from the distribution infrastructure server 11, it stores the received master information (step S301).

[0042] Furthermore, the corporate server 2b sends master information, including scenario information, notification content display patterns, and authentication patterns corresponding to the messages it distributes, to the management server 10 of the message management system 1 (step S011). Here, the communication content display patterns and authentication patterns of the master information sent from corporate server 2a and the master information sent from corporate server 2b may be different. This allows the message management system 1 to send messages that support customization of communication content display patterns and authentication patterns according to the intentions of each company, corporate server 2a and corporate server 2b. In addition, even for the same company, by registering multiple different master information sets for each message to be sent, it is possible to send messages with different notification content display patterns and authentication patterns for each message. The master information transmitted from the enterprise server 2b is stored in the management server 10 (step S102), then stored in the distribution infrastructure server 11 (step S202), and finally stored in the authentication infrastructure server 12 (step S302). Here, the master information sent from enterprise server 2a and the master information sent from enterprise server 2b are stored in the message management system 1 in a way that allows each enterprise server 2 to be identified.

[0043] When the enterprise server 2a sends the first message, it sends transaction data corresponding to the content to be sent to the management server 10 of the message management system 1 (step S003). This transaction data includes embedding data to be embedded in the pre-registered master information, correct answer data corresponding to the authentication pattern, and the telephone number to be sent. When the management server 10 receives transaction data from the enterprise server 2a, it performs a matching process to determine whether the received transaction data conforms to the rules defined in the master information. If it conforms to the rules, it stores the transaction data (step S103) and then sends the transaction data to the distribution infrastructure server 11.

[0044] For example, in the matching process, the management server 10 matches whether the embedded data corresponds to the elements defined by the notification content display pattern included in the master information, and whether it corresponds to the correct data corresponding to the authentication pattern included in the master information. For example, in the matching process for elements, if the notification content display pattern in the master information is a combination that includes element ID "0" and element ID "3", the management server 10 matches whether the embedded data included in the transaction data contains data corresponding to element ID "0" (for example, the text written in the message) and data corresponding to element ID "3" (for example, the URL for accessing the payment site). If these are included, the management server 10 determines that the embedded data matches the notification content display pattern. On the other hand, if at least one of the data is not included, or if the embedded data has different content (for example, data that executes a function to generate and download PDF data), the management server 10 determines that the data does not match and returns an error to the enterprise server 2.

[0045] Furthermore, in the matching process, the management server 10 performs a matching process to determine whether the data corresponds to the correct answer data corresponding to the authentication pattern included in the master information. For example, if the authentication pattern is specified as "postal code," the management server 10 determines whether the correct answer data corresponds to a string representing a postal code. For example, if the correct answer data is a 7-digit number, the management server 10 determines that it matches, but if it is not a 7-digit number (e.g., a string representing the katakana of the last name, part of an address, etc.), the management server 10 determines that it does not match and sends an error back to the enterprise server 2. By performing this matching process, it becomes possible to verify before sending whether the necessary data for sending the first and second messages is available, thereby ensuring that all the required data is collected.

[0046] When the distribution infrastructure server 11 receives transaction data from the management server 10, it performs a matching process on the received transaction data, stores the transaction data if a match is found (step S203), and then sends the transaction data to the authentication infrastructure server 12. When the authentication infrastructure server 12 receives transaction data from the distribution infrastructure server 11, it performs a matching process on the received transaction data, stores the transaction data if a match is found (step S303). Here, the authentication infrastructure server 12 needs to perform identity verification processing in order to send the first message based on the registered transaction data. The authentication infrastructure server 12 generates an authentication URL for identity verification, which is different for each transaction data to be distributed, stores it in association with the transaction data, and communicates with the distribution infrastructure server 11 by sending the authentication URL (step S304). The authentication URL generated here does not necessarily have to be created by the authentication infrastructure server 12; the management server 10 or the distribution infrastructure server 11 may generate it in advance and send it to the authentication infrastructure server 12 along with the transaction data. The authentication infrastructure server 12 matches and stores the transmitted authentication URL. Such an authentication URL is a URL that allows access to the authentication infrastructure server to perform authentication processing (identity verification) in order to authenticate whether or not the user is the recipient of the first message. As a result, each transaction data on the distribution infrastructure server 11 is associated with and stored as a corresponding authentication URL. In other words, a different authentication URL is prepared for each message.

[0047] When enterprise server 2b sends the first message, it sends transaction data corresponding to the content to be sent to the management server 10 of the message management system 1 (step S015). This transaction data is different from the transaction data sent from enterprise server 2a and the transaction data sent from enterprise server 2b. Transaction data sent from enterprise server 2b is matched by management server 10 and stored if a match is found (step S105). Subsequently, matching is also performed by distribution infrastructure server 11 and authentication infrastructure server 12, and the data is stored if a match is found (steps S205, step S305). Here, transaction data sent from enterprise server 2a and transaction data sent from enterprise server 2b are stored in the message management system 1 in a way that allows each enterprise server 2 to be identified. Furthermore, the matching process performed by the distribution infrastructure server 11 and the authentication infrastructure server 12 may be the same as the matching process performed by the management server 10.

[0048] Figure 8 is a sequence diagram illustrating the operation of the message delivery system S. This Figure 8 shows a sequence diagram related to the process of sending a message. The distribution infrastructure server 11 sends a second message containing an authentication URL to the telecommunications carrier server 3a, with the telephone number included in the transaction data as the destination. In this case, the distribution infrastructure server 11 sends the message to the telecommunications carrier server 3 (for example, telecommunications carrier server 3a) that is assigned to the telephone number to which the message is to be sent. The telecommunications carrier server 3a sends the second message requested by the distribution infrastructure server 11 to the terminal device 4a corresponding to the telephone number set as the destination (step S421).

[0049] After receiving the second message from the telecommunications carrier server 3a (step S621), terminal device 4a displays the second message when the user inputs an instruction to open the message (step S622). The displayed second message includes an authentication URL. The user inputs instructions for identity verification by touching the authentication URL included in the second message (step S623). Then, terminal device 4b sends an identity verification request by accessing the authentication URL based on the instructions for identity verification (step S624).

[0050] When the authentication infrastructure server 12 detects access to the authentication URL, it sends a request for authentication information input based on the authentication pattern set in the master information (for example, an authentication pattern that requires the user to enter their last name in kana) (step S321). Terminal device 4a displays a screen for accepting authentication information input based on a request from the authentication infrastructure server 12. After the user confirms this input screen, they enter the necessary authentication information. For example, the input screen displays an input box along with the text, "Please enter your last name in katakana." Based on this input screen, the user enters a string representing their last name in kana into the input field. Terminal device 4a sends the entered string as response data to the authentication infrastructure server 12 (step S625).

[0051] When the authentication infrastructure server 12 receives the response data sent from the terminal device 4a, it determines whether the response data is correct based on whether it matches the correct answer included in the transaction data (step S322). If the input response data does not match the correct answer data (step S322-NO), the authentication infrastructure server 12 determines that the response data is incorrect and notifies the terminal device 4a of an authentication error. When the terminal device 4a receives an authentication error, it displays that it is an authentication error on its display screen (step S626). In this case, since the first message is not sent from the distribution infrastructure server 11, the terminal device 4a cannot display the first message.

[0052] On the other hand, if the input response data matches the correct answer data (step S322-YES), the authentication infrastructure server 12 determines whether or not the notification content display pattern includes an operation button (step S323). If the notification content display pattern does not include an operation button (step S323-NO), it generates a first message that does not include an operation button based on the embedded transaction data and sends it to the terminal device 4a. When terminal device 4a receives the first message from the authentication infrastructure server 12, it displays the first message, which does not include any operation buttons, on the display screen (step S627). For example, a notice regarding the billing amount and billing details may be displayed.

[0053] On the other hand, if the notification content display pattern includes an operation button (step S323-YES), the authentication infrastructure server 12 generates a first message including the operation button based on the embedded transaction data and sends it to the terminal device 4a. When terminal device 4a receives the first message from the authentication infrastructure server 12, it displays the first message, which includes operation buttons, on the display screen (step S628). For example, in addition to a notice about the billing amount and billing details, operation buttons are displayed.

[0054] The user can view the displayed screen and press any of the operation buttons. When any operation button is pressed by the user, terminal device 4a executes a process corresponding to the pressed operation button (step S629). For example, the display screen has operation buttons for generating and downloading PDF data based on element ID "4". When pressed by the user, a request to generate PDF data is sent to the authentication infrastructure server 12 (step S629-A). When the authentication infrastructure server 12 receives a request to generate PDF data from the terminal device 4a, it generates metadata for the PDF data by assembling the data necessary to generate the PDF data (e.g., characters, figures, tables, symbols, marks, etc.) based on the embedded transaction data (step S324), and sends the generated metadata along with the PDF request to the form server 7 (step S325).

[0055] When the document server 7 receives a PDF request and metadata from the authentication infrastructure server 12, it generates PDF data based on the metadata (step S522) and sends it to the authentication infrastructure server 12. When the authentication infrastructure server 12 receives the PDF data sent from the document server 7, it sends the PDF data to the terminal device 4a that requested the PDF generation (step S326). When terminal device 4a receives PDF data transmitted from authentication infrastructure server 12, it stores the PDF data and displays it on the display screen (step S630).

[0056] Meanwhile, in step S629, terminal device 4a has an operation button on its display screen that has a URL set to access an external site based on element ID "1". When pressed by the user, it transitions to the external site set on the operation button (for example, a website published by Web server 6) (step S631). As a result, the enterprise server 2 accesses the website desired by the enterprise and the website corresponding to the URL specified by the transaction data, and the website screen is displayed.

[0057] On the other hand, in step S629, terminal device 4a has an operation button on its display screen that has a URL set to access a payment site based on element ID "3". When pressed by the user, it transitions to an external payment site (for example, a payment site where payment can be made for the invoiced amount notified by the first message) set on the operation button (step S632). As a result, the payment site screen is displayed on the display screen of terminal device 4a. This allows the user to make a payment for the invoiced amount notified as the first message, seamlessly from the first message through the payment site.

[0058] Figure 9 shows an example of a display screen G1 on terminal device 4a where the second message is displayed. For example, it is a display screen on which response data can be entered, such as in step S625 described above. The display screen G1 shows the name of the company that sent the second message (G101), along with input fields (G102) for entering response data and a send button (G103) for submitting the response data. In this case, input field G102 displays fields for entering the user's last name in katakana, the user's first name in katakana, and the date of birth. On this display screen, the user can enter their response data and press the submit button G103.

[0059] Figure 10 shows an example of the display screen for the first message shown on terminal device 4a when the response data matches the correct answer data. Figure 10 shows an example of display screen G2 when the notification content display pattern of the master information registered from enterprise server 2 contains only element ID "0". Display screen G2 does not show buttons for navigating to external sites, payment sites, or generating PDF data. Instead, the display area G201, which displays contract details, shows text based on the contract. Additionally, contact information G202 for inquiring about the company on the corporate server 2a is displayed. A notification display pattern containing only element ID "0" can provide a display screen that prevents users from being redirected to another site or similar location.

[0060] Figure 11 shows an example of the display screen for the first message shown on terminal device 4a when the response data matches the correct answer data. Figure 11 shows an example of display screen G3 when the notification content display pattern of the master information registered from the corporate server 2 includes two elements, element ID "0" and element ID "3". Display screen G3 shows a display field G301 for displaying contract details, a string of characters based on the contract details, and an operation button G302 for transitioning to the payment site. Below the operation button G302, a display field G304 is shown containing explanations about payment and contact information. After the user confirms the contract details and other information described in display field G301, if they wish to make a payment, they can press the operation button G302 to proceed to the payment site screen G303 and complete the payment.

[0061] Figure 12 shows an example of the display screen for the first message shown on terminal device 4a when the response data matches the correct answer data. Figure 12 shows an example of display screen G4 when the notification content display pattern of the master information registered from the corporate server 2 includes three elements: element ID "0", element ID "3", and element ID "4". On display screen G4, a display field G401 shows the contract details, containing text based on the contract, and below that, an operation button G402 is displayed to transition to the payment site. Furthermore, below the operation button G402, an operation button G403 for generating PDF data and a display field G404 containing payment explanations and contact information are displayed. After reviewing the contract details and other information displayed in the G401 display area, users can proceed with payment by pressing the G402 operation button to go to the payment site screen G410. Furthermore, before (or after) making a payment, users can download the generated PDF data based on the information in the G401 table by pressing the G403 operation button, and then view the PDF display screen G420.

[0062] Figure 13 shows an example of the display screen for the first message shown on terminal device 4a when the response data matches the correct answer data. Figure 13 shows an example of display screen G5 when the notification content display pattern of the master information registered from the corporate server 2 includes three elements: element ID "0", element ID "1", and element ID "1". On display screen G5, a string of characters based on the contract is displayed in display field G501 for displaying the contract details, and below that, a link button G502 is displayed that leads to the homepage published by the company on corporate server 2. Furthermore, below link button G502, a link button G503 is displayed that leads to the FAQ site. After reviewing the contract details and other information displayed in display area G501, users can click the link button G502 to navigate to the company's homepage, which will then be displayed on screen G510. Additionally, users can click the link button G503 to access screen G520, which displays the FAQ content, if they wish to confirm information on the FAQ site.

[0063] Figure 14 shows an example of the display screen for the first message shown on terminal device 4a when the response data matches the correct answer data. Figure 14 shows an example of display screen G6 when the notification content display pattern of the master information registered from enterprise server 2 includes one element with element ID "4". On the display screen G6, an operation button G602 for generating PDF data is displayed between the standard text G601 and the contact information display field G604. The user can initiate the generation of PDF data by pressing the operation button G602, and then display the generated and downloaded PDF screen G610.

[0064] According to the embodiment described above, the way in which the content of the first message is displayed to a user whose identity has been confirmed by the authentication URL based on the second message can be switched on the message management system side according to the company's requirements. Furthermore, the way in which the content of the first message is displayed can be specified by the company server 2 using a combination that includes at least one element ID. Furthermore, according to the above-described embodiment, in the stage before connecting from the target message presented by the corporate server 2 to an external site (FAQ site, payment site, etc.), and after authentication of identity verification via an authentication URL, the message management system can be switched according to the company's request. This means that, normally, after identity verification is complete, the user is connected to each site via redirection, etc., but instead of immediately connecting to the external site after authentication is complete, the user is connected to the external site via a screen relayed by the message management system. This makes it possible to change the response in the message management system according to the destination from the time identity verification is completed until the transition to the external site. In addition, by having the user go through a screen relayed by the message management system, both the corporate server 2 and the company operating the message management system can understand which destinations users tend to transition to regarding message delivery, and can broaden the range of services.

[0065] In the embodiment described above, when generating PDF data, the authentication infrastructure server 12 sends a generation instruction to the report server 7 along with the data necessary to generate the PDF data, and the PDF data is generated. However, the authentication infrastructure server 12 may generate the PDF data itself. In the embodiment described above, PDF data is generated in response to the press of an operation button for generating PDF data on the terminal device 4. Here, it is also possible to generate the PDF data in advance and make it ready to send before sending the first message, but not all users will necessarily view the PDF data. For example, when a message containing a reminder notice is displayed, a user who wants to proceed with the payment process without reviewing the reminder notice in PDF data may skip reviewing the PDF data. In such cases, an on-demand method of generating the PDF data in response to a user request may be applied. This avoids the burden of performing the process of generating the PDF data in advance, and also eliminates the need to reserve memory space to store the generated PDF data. On the other hand, if a service is provided that requires users to review the PDF data, the PDF data may be generated in advance.

[0066] Furthermore, even when providing PDF data on demand, the PDF data can be provided by having the user press an operation button for generating the PDF data. Therefore, regardless of when the user requests the data to be generated, documents such as dunning notices can be quickly displayed and reviewed as PDF data.

[0067] The message management system 1 in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into the computer system and executed. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Moreover, "computer-readable recording medium" may also include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that hold programs for a certain period of time, such as volatile memory inside the computer system that acts as a server or client in such cases. Furthermore, the above-mentioned program may be for implementing a part of the above-mentioned function, or it may be a program that can implement the above-mentioned function in combination with a program already recorded in the computer system, or it may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0068] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments and includes designs and the like that do not depart from the spirit of this invention. [Explanation of Symbols]

[0069] 1. Message Management System 2,2a,2b Enterprise Server 3,3a,3b Telecommunications carrier server 4,4a,4b Terminal devices 5 Payment Server 6 Web Server 7. Report Server 10 Management Server 11 Distribution infrastructure server 12 Authentication infrastructure server 100 Storage section 101 Acquisition Department 102 Certification Department 103 Message generation unit 104 Message Sending Section 1011 First Acquisition Department 1012 Second Acquisition Department NW (Network Communication Network) S Message Distribution System

Claims

1. A first acquisition unit obtains a notification content display pattern from a requesting party that requests the sending of a message, which specifies which of several different elements the message should include. A second acquisition unit obtains from the requesting party the embedded data, which is the data to be embedded in the elements included in the notification content display pattern, and the recipient of the message. A second message transmission unit sends a confirmation message to the terminal device that is the destination to which the aforementioned message is to be sent, in order to verify the identity of the user. An authentication unit that determines whether or not the person is the person in question based on the data transmitted from the terminal device that received the aforementioned confirmation message, A first message transmission unit, when it is determined that the person is the person in question, transmits a message containing the embedded data embedded in the notification content display pattern to the destination terminal device in a viewable format. A message management system that has the following features.

2. The message concerns the contract for the services provided by the requesting party to the user. The first message transmission unit embeds embedded data indicating the content based on the contract into the notification content display pattern, and after it is determined that the user is the user, it transmits the data to the target terminal device that has been determined to be the user in a viewable format. The message management system according to claim 1.

3. A message management method performed by a computer, From the requesting party that requests the sending of a message, a notification content display pattern is obtained that specifies which of several different elements should be included in the message. The embedding data, which is the data to be embedded in the elements included in the notification content display pattern, and the recipient of the message are obtained from the requesting party. A confirmation message is sent to the terminal device that is the recipient of the aforementioned message to verify the user's identity, and a determination is made as to whether or not the user is the person in question based on the data transmitted from the terminal device. If it is determined that the person is the person in question, a message containing the embedded data embedded in the notification content display pattern is sent to the recipient's terminal device, making it viewable. A message management method that includes this.

4. A program executed by a computer, From the requesting party that requests the sending of a message, a notification content display pattern is obtained that specifies which of several different elements should be included in the message. The embedding data, which is the data to be embedded in the elements included in the notification content display pattern, and the recipient of the message are obtained from the requesting party. A confirmation message is sent to the terminal device that is the recipient of the aforementioned message to verify the user's identity, and a determination is made as to whether or not the user is the person in question based on the data transmitted from the terminal device. If it is determined that the person is the person in question, a message containing the embedded data embedded in the notification content display pattern is sent to the recipient's terminal device, making it viewable. A program that includes the following.

Images