Distribution management device, message distribution system, and message distribution method

Abstract

To provide a distribution management device, and a message distribution system and method for easily changing contents included in a message to be distributed on demand.SOLUTION: A delivery management server that transmits a message to a communication terminal in response to a delivery request from the communication terminal by using a telephone number as a destination, the delivery management server comprising: a storage unit that stores a scenario in which content included in the message is defined and a scenario key that identifies a combination of a plurality of scenarios different from a reference date and time to which a different date and time is assigned for each scenario in association with each other; And a selection unit that specifies a scenario associated with a reference date and time corresponding to the date and time information and selects a message corresponding to the specified scenario as a message to be distributed to the communication terminal.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a distribution management device, a message distribution system, and a message distribution method. [Background technology]

[0002] There is a service that delivers messages to consumers from delivery requesters such as companies and organizations (Patent Document 1). For example, when delivering messages, various messages are delivered using SMS (Short Message Service), RCS (Rich Communication Services), etc. In the case of distribution using SMS, for example, a one-time password (hereinafter also referred to as OTP) or the like may be distributed on demand in response to a distribution request from a consumer's communication terminal. In messages that are distributed on demand, the contents may be determined based on a scenario (template). When distributing a simple message such as an OTP, a scenario can be created in advance, and then a message with variable information such as a one-time password embedded in the scenario can be generated using this scenario and distributed to the consumer's communication device. Here, the content of the one-time password, the wording to be written in the message, the URL (Uniform Resource Locator), etc. can be specified by the distribution requester using text.

[0003] If the content to be delivered is a simple message with a predetermined content, such as an OTP, the desired message can be sent to the consumer's communication terminal by specifying the text corresponding to the wording to be written for a predetermined scenario. In other words, if you want to change the character string to be written in the message, you can specify the changed character string and send a message based on the changed character string. Currently, message delivery using SMS is the mainstream method, and messages can be delivered by describing variable information such as OTP according to a scenario that has already been decided on. [Prior art documents] [Patent documents]

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

[0005] However, if the content of the message to be delivered is not a simple message like an OTP, the message content may need to be revised. In recent years, message delivery using RCS has also become popular. Message delivery using RCS makes it possible to deliver not only messages containing text, but also messages containing images such as rich cards and carousels, so it is conceivable that various message revisions will occur. In such cases, the delivery requester can create a revised scenario, specify the revised scenario, and have the message delivered. When performing on-demand distribution using RCS, one possible method for replacing images in rich cards is to generate a different scenario in which new images are defined.

[0006] The above method requires the creation of a new scenario, and in this case, a new scenario ID is assigned in response to the creation of the new scenario. Therefore, the delivery requester must specify the new scenario ID as a request parameter to the server that delivers the message, which requires time and effort to make the change and the burden of having to accurately specify the request parameters.

[0007] The present invention has been made in view of the above circumstances, and its purpose is to provide a distribution management device, a message distribution system, and a message distribution method that can easily change the content included in a message to be distributed on demand while reducing the increase in the amount of work required by the distribution requester. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems, one aspect of the present invention is a distribution management device that sends a message to a communication terminal using a telephone number as a destination via a telecommunications carrier's server in response to a distribution request from the communication terminal, the distribution management device having a memory unit that stores scenarios that determine the content to be included in the message, a reference date and time to which a different date and time is assigned for each scenario, and a scenario key that identifies a combination of multiple different scenarios, an acquisition unit that acquires a scenario key and date and time information in response to a distribution request sent from a requesting device used by a source that requests the delivery of the message, and a selection unit that identifies a scenario that is associated with a reference date and time corresponding to the date and time information from among the multiple scenarios stored in the memory unit and that are associated with the scenario key sent from the requesting device, and selects a message corresponding to the identified scenario as a message to be delivered to the communication terminal.

[0009] Another aspect of the present invention is a message delivery system that sends a message to a communication terminal using a telephone number as a destination via a telecommunications carrier's server in response to a delivery request from the communication terminal, the message delivery system having a memory unit that stores scenarios that determine the content to be included in the message, a reference date and time to which a different date and time is assigned for each scenario, and a scenario key that identifies a combination of multiple different scenarios, an acquisition unit that acquires a scenario key and date and time information in response to a delivery request sent from a requesting device used by a source that requests delivery of the message, and a selection unit that identifies a scenario that is associated with a reference date and time corresponding to the date and time information from among the multiple scenarios stored in the memory unit and that are associated with the scenario key sent from the requesting device, and selects a message corresponding to the identified scenario as a message to be delivered to the communication terminal.

[0010] Another aspect of the present invention is a message delivery method executed by a computer that sends a message to a communication terminal using a telephone number as a destination via a telecommunications carrier's server in response to a delivery request from the communication terminal, the message delivery method including: storing in a memory unit a scenario that determines the content to be included in the message, a reference date and time to which a different date and time is assigned for each scenario, and a scenario key that identifies a combination of multiple different scenarios; acquiring a scenario key and date and time information corresponding to a delivery request sent from a requesting device used by a source that requests delivery of the message; identifying a scenario that is associated with a reference date and time corresponding to the date and time information from among the multiple scenarios stored in the memory unit and that are associated with the scenario key sent from the requesting device; and selecting a message corresponding to the identified scenario as a message to be delivered to the communication terminal. [Effects of the Invention]

[0011] As described above, according to the present invention, it is possible to easily change a message to be distributed on demand while reducing the increase in the amount of work required by the distribution requester. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a schematic block diagram showing the configuration of a message delivery system S according to an embodiment of the present invention. [Figure 2] 2 is a schematic functional block diagram illustrating the functions of the distribution management server 1. FIG. [Figure 3] FIG. 10 is a diagram showing an example of scenario data 1021. [Figure 4] 10 is a diagram showing an example of scenario group data 1022 stored in the storage unit 102. FIG. [Figure 5] 10 is a flowchart illustrating the operation of the distribution management server 1. [Figure 6] 10 is a conceptual diagram illustrating the relationship between date and time information, a reference date and time, and a message to be delivered. FIG. [Figure 7] FIG. 10 is a diagram showing an example of a case where a message is displayed on the communication terminal 4. DETAILED DESCRIPTION OF THE INVENTION

[0013] A message delivery system S according to an embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing the configuration of a message delivery system S according to an embodiment of the present invention. In the message delivery system S, a delivery management server 1, a company server 2, a carrier server 3, and communication terminals 4 (4a, 4b) are connected via a network NW.

[0014] The delivery management server 1 transmits a message to the communication terminal 4 via the communication carrier server 3. The delivery management server 1 is an information processing device managed by a business operator that provides a service of accepting message delivery requests from a company in the company server 2 and delivering messages in response to the delivery requests to communication terminals 4 via the telecommunications carrier server 3. The business operator that manages the delivery management server 1 may be the same as the company in the company server 2, or may be the same as the company in the telecommunications carrier server 3. The delivery management server 1 performs various controls for delivering messages requested for delivery by the company server 2. The delivery management server 1 communicates with the company server 2 and the telecommunications carrier server 3 wirelessly or via wired communication.

[0015] The corporate server 2 is a server device managed by a requester who requests the delivery management server 1 to deliver a message to a destination user. The requester is, for example, a company or organization (e.g., a bank, an insurance company, etc.) that provides information to the destination user. The corporate server 2 communicates with the delivery management server 1 wirelessly or via a wired connection. If there are multiple companies, a different company server 2 may be provided for each company. Furthermore, the company server 2 may be used not only by companies but also by organizations (such as local governments and administrative agencies).

[0016] The telecommunications carrier server 3 is a server device managed by a telecommunications carrier. The telecommunications carrier may be, for example, an MNO (Mobile Network Operator) that provides communication services using telephone numbers to the communication terminal 4, using communication lines that the carrier owns or operates. When there are multiple telecommunications carriers, a telecommunications carrier server 3 is provided for each telecommunications carrier.

[0017] The communication terminal 4 is, for example, any one of a smartphone, a tablet terminal, a personal computer, and the like. A consumer makes a contract with a telecommunications carrier of the telecommunications carrier server 3 to use a communication service using the communication terminal 4. The communication terminal 4 is capable of communicating using the communication service provided by the contracted telecommunications carrier. A mobile phone number (hereinafter simply referred to as a telephone number) is assigned to the communication terminal 4, and the communication terminal 4 has the function of communicating with this telephone number as the destination. The communication terminal 4 has a display unit such as a liquid crystal display that displays information, and an operation unit such as a touch panel that accepts user operations. The communication terminal 4 communicates with the telecommunications carrier server 3 via wireless or wired connections. The user may be, for example, a consumer. Furthermore, the user may not be a consumer, but may be an organization, group, or the like, as long as they can receive services provided by the company that operates the corporate server 2.

[0018] FIG. 2 is a schematic functional block diagram illustrating the functions of the distribution management server 1. As shown in FIG. The delivery management server 1 includes a communication unit 101, a storage unit 102, an acquisition unit 103, a selection unit 104, and a data processing unit 105. The delivery management server 1 delivers a message to a communication terminal 4 via a telecommunications carrier server 3, using the telephone number as the destination. The delivery management server 1 is a delivery management device that transmits a message to a communication terminal 4 via a communication carrier server 3, for example, using a telephone number as a destination in response to a delivery request from the communication terminal 4. The communication unit 101 communicates with the company server 2 , the carrier server 3 , and the communication terminal 4 .

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

[0020] The storage unit 102 stores scenario data 1021 and scenario group data 1022 . The scenario data 1021 includes a scenario ID and a scenario content. FIG. 3 is a diagram showing an example of the scenario data 1021. As shown in FIG. Scenario data associates a scenario ID with scenario content. The scenario ID is identification information that individually identifies a scenario. The scenario content represents content defined as a scenario that represents a template that constitutes a message. The scenario content can include a layout that represents the arrangement of text, images, etc. included in the message, content that represents a string of text predetermined for each type of message, information that indicates the position where variable text is to be placed in the message body, images included in the message, etc. Here, the scenario content may include at least images. The images included as scenario content may be still images or videos. Furthermore, the images may be displayed in a display format such as a rich card or a carousel. A rich card contains a set of content consisting of at least one of an image or text. A carousel arranges multiple rich cards in one direction, and as a consumer performs a sliding operation, the rich cards can be slid in a direction (for example, horizontally) corresponding to the sliding operation. Such scenario data 1021 is transmitted in advance from the device that has requested distribution (for example, the company server 2) and registered in the storage unit 102. In addition, the scenario data 1021 may be registered in the storage unit 102 by an operator performing various registration operations via an input device such as a keyboard or a mouse in response to a request from the device that has requested distribution.

[0021] The scenario group data 1022 is data that allows a scenario to be selected according to the timing at which a message delivery request is made. FIG. 4 is a diagram showing an example of the scenario group data 1022 stored in the storage unit 102. As shown in FIG. The scenario group data 1022 is data in which a scenario key, a reference date and time, and a scenario ID are associated with each other. The scenario key is identification information that identifies a combination of multiple different scenarios. The reference date and time is information to which a different date and time is assigned for each scenario. The scenario ID is registered as a scenario ID that belongs to a scenario key.

[0022] Here, three scenario IDs, "A1011," "A2321," and "A3403," belong to the scenario key "ABCDE." Furthermore, scenario ID "A1011" is associated with the reference date and time "2024 / 03 / 01 0:00:00," scenario ID "A2321" is associated with the reference date and time "2024 / 05 / 01 0:00:00," and scenario ID "A3403" is associated with the reference date and time "2024 / 07 / 01 0:00:00." Furthermore, three scenario IDs, "E1105," "E2056," and "E3811," belong to the scenario key "EFGHI." Furthermore, scenario ID "E1105" is associated with the reference date and time "2024 / 03 / 10 0:00:00," scenario ID "E2056" is associated with the reference date and time "2024 / 05 / 15 0:00:00," and scenario ID "E3811" is associated with the reference date and time "2024 / 07 / 22 0:00:00."

[0023] In this case, for messages in which the message body will not be changed, but some of the data contained in the message is expected to be replaced (changed) depending on the season or a specific date, scenario IDs that are candidates for the data to be replaced are associated with a scenario key. For example, if there is a plan to change part of a message, scenario IDs that are expected to be candidates for display can be registered so that they belong to scenario key "ABCDE," and scenario key "ABCDE" can be specified as the distribution target. In this case, it is possible to replace some of the elements that make up the message with one of the scenario IDs (A1011, A2321, A3403) that belong to scenario key "ABCDE," but replacement with scenario IDs that do not belong to scenario key "ABCDE" (E1105, E2056, E3811) will not be performed.

[0024] In the example shown in FIG. 4, the reference date and time includes the year, month, and date and time, but the time may be omitted and only the year, month, and date may be used. Such scenario group data 1022 may be sent in advance from the device that requested distribution (for example, the company server 2) and registered in the storage unit 102, or may be set by the company that manages the company server 2 by inputting the data into the management screen of the distribution management server 1 via an input device such as a keyboard or mouse. Alternatively, the company that manages the management server 1 may set the data instead.

[0025] The acquisition unit 103 acquires a scenario key and date and time information according to a delivery request sent from a requesting device (e.g., company server 2) used by the message delivery requester. In this embodiment, a case will be described in which a delivery request includes a scenario key and date and time information. The requesting device may be, for example, a physical server such as the corporate server 2, or may be a cloud server provided by a cloud computing service.

[0026] The selection unit 104 identifies a scenario that is associated with a reference date and time according to the date and time information from among a plurality of scenarios stored in the memory unit 102 and associated with a scenario key sent from the requesting device, and selects a message according to the identified scenario as a message to be delivered to the communication terminal.

[0027] The data processing unit 105 controls each unit of the distribution management server 1 . Furthermore, the data processing unit 105 transmits to the carrier server 3 a message delivery request in response to the delivery request acquired from the company server 2 .

[0028] In the above-described distribution management server 1, the communication unit 101, acquisition unit 103, selection unit 104, and data processing unit 105 may be configured by a processing unit such as a CPU (Central Processing Unit) or a dedicated electronic circuit. The delivery management server 1, the company server 2, and the carrier server 3 may each be a physical server or a cloud server provided by a cloud computing service. Some of the functions of the delivery management server 1 may be provided in the company server 2 and the carrier server 3.

[0029] FIG. 5 is a flowchart illustrating the operation of the distribution management server 1. Here, the storage unit 102 acquires and stores in advance scenario data 1021 and scenario group data 1022 transmitted from the company server 2. When changing some of the multiple elements that make up a message, the company server 2 sends a delivery request that allows the content of the change to be understood to the delivery management server 1. When changing some of the multiple elements included in a message, for example, changing (replacing) an image included in the message, the company server 2 sends a delivery request to the delivery management server 1 that includes the scenario key to which the scenario ID assigned to the scenario content that includes the changed element belongs, and date and time information. Here, the company server 2 may transmit the delivery request to the delivery management server 1 including the telephone number assigned to the communication terminal 4 to be delivered, and the character string to be written in the scenario (such as the expiration date, one-time password, character string to be displayed as a display item, and URL to be written in the message). The character string to be written in the scenario has content that varies for each message. This allows the communication terminal 4 to be delivered to be specified, and also allows the character string to be written in the message and the URL to be written to be different for each communication terminal 4 to be delivered to.

[0030] Furthermore, the company server 2 may use the date and time of the day the delivery request is made (current date and time) as the date and time information when sending the delivery request, or may use a date and time according to the deadline for changing the elements that make up the message. Such date and time information may be a date and time input as input data from a terminal device connected to the company server 2 and used by an operator belonging to the company that operates the company server 2. Furthermore, the company server 2 may transmit a distribution request without specifying date and time information. When date and time information is not specified, the company server 2 may use data indicating blank for the date and time information, or may transmit a distribution request that does not include date and time information.

[0031] The acquisition unit 103 of the delivery management server 1 acquires a delivery request from the company server 2 (step S101). Here, if the delivery request does not specify date and time information (if the date and time information is blank or if the date and time information is not included), the acquisition unit 103 may acquire a delivery request for which date and time information is not specified.

[0032] When a distribution request is acquired, the selection unit 104 performs an extraction process to extract the scenario key and date and time information contained in the distribution request acquired from the company server 2 by the acquisition unit 103 (step S102), and determines whether the date and time information has been acquired (step S103). If the date and time information has been acquired from the distribution request (step S103-YES), the selection unit 104 proceeds to step S104, and if the date and time information has not been acquired (step S103-NO), the selection unit 104 proceeds to step S110.

[0033] If date and time information is extracted from the distribution request (step S103-YES), the selection unit 104 refers to the storage unit 102 and identifies a reference date and time corresponding to the extracted date and time information from among the date and time information belonging to the extracted scenario key (step S104). Here, the selection unit 104 only needs to be able to identify a reference date and time according to the date and time information, and may, for example, identify the most recent reference date and time from among the reference dates and times that precede the date and time indicated by the date and time information, or may identify a reference date and time that is the same as the date and time indicated by the date and time information. As a specific example, when the scenario key "ABCDE" and date and time information "2024 / 05 / 10 0:00:00" included in the distribution request are extracted, the selection unit 104 identifies the scenario key "ABCDE" from the scenario group data 1022 stored in the memory unit 102, and identifies "2024 / 05 / 01 0:00:00" as the reference date and time before the date and time information "2024 / 05 / 10 0:00:00" and the most recent reference date and time from the reference dates and times "2024 / 03 / 01 0:00:00," "2024 / 05 / 01 0:00:00," and "2024 / 07 / 01 0:00:00" belonging to this scenario key "ABCDE."

[0034] Once the date and time information is identified, the selection unit 104 identifies a scenario ID corresponding to the identified reference date and time (step S105). For example, the selection unit 104 identifies, as the scenario ID, the scenario ID "A2321" corresponding to the reference date and time "2024 / 05 / 01 0:00:00" of the scenario key "ABCDE" from the scenario group data stored in the storage unit 102.

[0035] The selection unit 104 then selects the identified scenario ID as the scenario to be distributed (step S106). When delivering a message to the communication terminal 4 after a scenario has been selected, the data processing unit 105 delivers the message based on the selected scenario ID. For example, when a consumer operating communication terminal 4 inputs an instruction to request message delivery on a screen displayed when a message delivery application is executed on communication terminal 4, the message delivery request is sent to enterprise server 2, and in response to this request, enterprise server 2 sends the message delivery request together with the telephone number of communication terminal 4 to delivery management server 1. Here, if there are variable character strings to be written in a scenario defined as a template for character strings or URLs to be written in the message, enterprise server 2 can also include these character strings in the delivery request and send them.

[0036] Based on this message delivery request, the delivery management server 1 requests the telecommunications carrier server 3 to deliver the message to the specified telephone number as the destination. At this time, the delivery management server 1 requests the telecommunications carrier server 3 to deliver the message using the scenario ID selected in step S106. Furthermore, if the company server 2 specifies that there are character strings to be written in the message (such as the expiration date, one-time password, character strings to be displayed as display items, and URLs to be written in the message), the delivery management server 1 requests the communication carrier server 3 to deliver the message so that these are also written in. In this way, a scenario is generated in advance, and the company server 2 specifies, at the time of delivery, the character strings that will be variable elements to be changed at the time of delivery (such as the expiration date, one-time password, character strings to be displayed as display items, and URLs to be written in the message), while data previously stored as a scenario can be used for the rest. In this case, the company server 2 simply sends the character strings that will be variable elements and the telephone number assigned to the destination communication terminal 4 in addition to the delivery request. The telecommunications carrier server 3 delivers a message based on a delivery request from the delivery management server 1 to the communication terminal 4. This allows a message in which an image has been replaced in response to a request from the company server 2 to be delivered to the communication terminal 4.

[0037] On the other hand, if the date and time information cannot be extracted from the distribution request in step S103 (step S103-NO), the selection unit 104 acquires the current date and time as the date and time information (step S110). When acquiring the current date and time, the selection unit 104 may acquire the current time generated by a clocking function of the distribution management server 1, or may acquire it from a time server that distributes Japanese Standard Time. Here, even if the delivery request does not include date and time information, or if the date and time included in the delivery request is blank data, the delivery management server 1 uses the current date and time as date and time information. This eliminates the need for the company server 2 to include date and time information in the delivery request and send it to the delivery management server 1, thereby eliminating the need for the delivery request source (e.g., company server 2) to set date and time information. Furthermore, since the distribution management server 1 uses the current time when date and time information is not specified in the distribution request, it is possible to assign a reference date and time based on the timing at which the distribution request is received from the company server 2, and therefore it is possible to identify a scenario ID that corresponds to the timing at which the distribution request is received from the company server 2. Therefore, as long as the company server 2 can specify a scenario key, it does not need to consciously select which scenario ID corresponds to which reference date and time.

[0038] The selection unit 104 uses the current date and time as date and time information to identify the reference date and time corresponding to this date and time information from the reference dates and times belonging to the scenario key (step S104). The subsequent processing is the same as that from step S105 onwards described above.

[0039] FIG. 6 is a conceptual diagram illustrating the relationship between date and time information, a reference date and time, and a message to be delivered. At 00:00:00 on March 1, 2024, an image (symbol A1) based on scenario ID "A101" is being distributed to the communication terminal 4 as an image included in a message. If the image based on scenario ID "A101" is to be replaced with an image based on scenario ID "A2312" at 00:00:00 on May 10, 2024, the company server 2 sends the scenario key "ABCDE" and date and time information "2024 / 05 / 10 0:00:00" corresponding to the current date and time as a distribution request to the distribution management server 1. The distribution management server 1 then references the storage unit 102 and identifies the reference date and time "2024 / 05 / 01 0:00:00" corresponding to the date and time information included in the distribution request from among the reference dates and times belonging to the scenario key "ABCDE." The distribution management server 1 then selects the scenario ID "A2312" corresponding to this reference date and time as the image to be distributed. As a result, if a message delivery request is made from communication terminal 4 after the image is selected, the image that constitutes the message will be replaced with an image (symbol A2) corresponding to scenario ID "A2312" and delivered to communication terminal 4. In addition, if an image (symbol A2) based on scenario ID "A2312" is being distributed to communication terminal 4 as an image included in a message, and the image based on scenario ID "A2312" is to be replaced with an image based on scenario ID "A3403" at 00:00:00 on July 18, 2024, the company server 2 sends the scenario key "ABCDE" and date and time information "2024 / 07 / 18 0:00:00" corresponding to the current date and time as a distribution request to the distribution management server 1. As a result, the distribution management server 1 refers to the storage unit 102 and identifies the reference date and time "2024 / 07 / 01 0:00:00" corresponding to the date and time information included in the distribution request from among the reference dates and times belonging to scenario key "ABCDE." The distribution management server 1 then selects scenario ID "A3403" corresponding to this reference date and time as the image to be distributed. As a result, if a message delivery request is made from communication terminal 4 after the image is selected, the image (symbol A3) corresponding to scenario ID "A3403" will be delivered to communication terminal 4 as an image among the elements that make up the message. Here, when an image is replaced, elements that have not been replaced continue to be displayed in the message in the same way as before the change.

[0040] FIG. 7 is a diagram showing an example of a message displayed on the communication terminal 4. In FIG. Here, the display screen of the communication terminal 4 displays a display screen G1 on which a message delivery application of the communication terminal 4 has been launched by a consumer. When the consumer operates the communication terminal 4 and sends an inquiry from the communication terminal 4 to the company server 2, a message corresponding to the inquiry is sent from the company server 2 to the communication terminal 4 via the delivery management server 1 and the telecommunications carrier server 3. Here, as messages corresponding to the inquiry, a message (reference numeral 70) containing a URL and a message (reference numeral 71) related to the inquiry are displayed on the display screen G1. As described above, the message (reference numeral 71) displays content based on the scenario assigned the scenario ID selected by the selection unit 104. If an image has been replaced, the replaced image is displayed in the message (reference numeral 71).

[0041] According to the embodiment described above, when the delivery management server 1 receives a delivery request from the company server 2, it refers to the reference date and time, which allows the delivery system to identify and deliver a scenario that matches the reference date and time. This allows the company of the company server 2 to seamlessly switch scenarios after a specific date by sending a delivery request that already includes the current date and time as date and time information. Furthermore, even if the delivery request sent from the company server 2 to the delivery management server 1 does not include date and time information, the delivery management server 1 can supplement the current date and time as date and time information, allowing the delivery management server 1 to select a scenario appropriate for the day on which the delivery request is received.

[0042] Furthermore, according to the above-described embodiment, even when an image included in a message needs to be replaced, it is possible to flexibly respond and reduce the effort required for the distribution requester to change the scenario. This makes it easy to review the message, and therefore it becomes possible to update (reselect) the scenario more frequently than before.

[0043] Furthermore, according to the above-described embodiment, when a delivery requester such as the corporate server 2 or an administrator belonging to the company operating the server of the corporate server 2 changes an image included in a message, the delivery management server 1 can specify a scenario group by using a scenario key and also specify a date and time, and then issue a message delivery request to the telecommunications carrier server 3. As a result, when switching images to be sent as a message, the delivery requester only needs to specify a scenario key, and does not need to specify a scenario ID. As a result, even when changing the scenario, there is no need to be aware of the scenario IDs before and after the change, thereby reducing the effort required for the change. Furthermore, even if the delivery requester does not specify date and time information when changing an image included in a message, the delivery management server 1 will apply the current date and time as date and time information, so if the delivery requester specifies a scenario key at the required timing, the image included in the message can be changed. This makes it easier to change the image included in a message. After the scenario ID is changed, when the delivery management server 1 receives a message delivery request from the communication terminal 4, it can deliver a message based on the scenario ID corresponding to the reference date and time according to the date and time information, addressed to the telephone number assigned to the communication terminal 4 that made the delivery request.

[0044] Furthermore, in the above-described embodiment, a case has been described in which the distribution requester makes a distribution request with the mobile phone number assigned to the consumer's communication terminal 4 set as the destination. However, it is also possible to prepare a communication terminal to be used by the distribution requester, specify the scenario key as described above, and send a distribution request to the distribution management server 1 with the mobile phone number assigned to the distribution requester's communication terminal as the destination, and set the date and time information to a date and time slightly after the reference date and time associated with the scenario ID of the target to be tested. Here, for example, when performing on-demand distribution using RCS, one method for replacing the image on a rich card is to update it to the image included in the scenario to be distributed when the time for replacement arrives and then distribute it. With this method, the image is updated only when the desired replacement time arrives. Therefore, if a request is made from a consumer's communication device shortly after the image is updated, the replacement image will be delivered before verification has been performed to ensure that it is displayed correctly in the message at the intended size, making it impossible to perform advance verification. However, according to the above-described embodiment, a message set with a scenario ID belonging to the scenario key to be tested can be sent to the communication terminal used by the distribution requester. Therefore, the distribution requester can check the state in which the message including the replaced image is displayed on the communication terminal of the distribution requester. For example, by specifying a future date and time as the date and time information, a message corresponding to the scenario ID of the reference date and time can be sent to the communication terminal of the distribution requester according to the future date and time. This allows the distribution requester to check the message displayed on the display screen of the communication terminal and verify in advance whether the replaced image is displayed correctly in the message. For example, it can be verified whether the image is displayed at the expected size on the screen where the message is displayed. In addition, not only a future date and time but also a past date and time may be specified as the date and time information, which makes it possible to verify later whether an image included in a message delivered in the past was displayed correctly.

[0045] In the above embodiment, the message content associated with the scenario ID is an image, and the image is replaced among the elements constituting the message. However, the element to be replaced is not limited to an image, and may be a character string. For example, if the element to be replaced is a character string, the fixed phrase included in the message may be changed according to the season. Although predetermined items may be used as items to be written in the message, multiple scenario IDs may be prepared so that different items are used each time the year changes or when the service content to be provided changes. For example, scenarios to which different scenario IDs are assigned may be prepared depending on when the year changes or when the insurance content available changes for the items that need to be filled out on an insurance application form.

[0046] In the above-described embodiment, a reference date and time is stored for each scenario key, and an image is replaced by receiving a distribution request including the date and time information from the company server 2. However, other configurations are also possible. For example, instead of a reference date and time, different temperature ranges may be assigned to each scenario ID and stored. When the company server 2 transmits a distribution request to the distribution management server 1, the scenario may include temperature information based on the current temperature measurement results. This allows the scenario to be changed depending on the current temperature. More specifically, a first temperature range (0°C to 20°C), a second temperature range (21°C to 30°C), and a third temperature range (30°C to 35°C) are assigned to different scenario IDs, and the ranges are stored together with the scenario key as scenario group data. Then, when a certain temperature change occurs, the company server 2 transmits a distribution request including the current temperature (for example, the temperature in the area corresponding to the address registered by the consumer) to the distribution management server 1. The current temperature may be obtained from a weather server or the like. Based on the delivery request, the delivery management server 1 may identify the temperature range to which the current temperature falls, identify a scenario ID corresponding to the identified temperature range, and deliver a message including an image according to the identified scenario ID to the communication terminal 4. This allows the image to be replaced depending on the temperature in the resident's area.

[0047] The distribution management server 1 in the above-described embodiment may be implemented by a computer. In this case, a program for implementing this function may be recorded on a computer-readable recording medium, and the program may be loaded into a 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 a 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 a computer system serving as a server or client. The program may be designed to implement only a portion of the above-described functions, or may be capable of implementing the above-described 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).

[0048] 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]

[0049] 1. Distribution management server 2. Corporate Server 3. Telecommunications carrier server 4. Communication terminals 4a Communication terminal 4b Communication terminal 101 Communications Department 102 Storage section 103 Acquisition Department 104 Selection section 105 Data Processing Unit 1021 Scenario Data 1022 Scenario Group Data G1 display screen NW Network S Message Delivery System

Claims

1. A delivery management device that transmits a message to a communication terminal using a telephone number as a destination via a server of a communication carrier in response to a delivery request from the communication terminal, a storage unit that stores scenarios that determine the content to be included in the message, a reference date and time that is assigned to each of the scenarios, and a scenario key that identifies a combination of multiple different scenarios; an acquisition unit that acquires a scenario key and date and time information according to a distribution request transmitted from a request source device used by a source that requests distribution of the message; a selection unit that identifies a scenario associated with a reference date and time according to the date and time information from among a plurality of scenarios stored in the storage unit and associated with a scenario key transmitted from the request source device, and selects a message according to the identified scenario as a message to be delivered to the communication terminal; A distribution management device having the above configuration.

2. A message delivery system that sends a message to a communication terminal using a telephone number as a destination via a server of a communication carrier in response to a delivery request from the communication terminal, a storage unit that stores scenarios that determine the content to be included in the message, a reference date and time that is assigned to each of the scenarios, and a scenario key that identifies a combination of multiple different scenarios; an acquisition unit that acquires a scenario key and date and time information according to a distribution request transmitted from a request source device used by a source that requests distribution of the message; a selection unit that identifies a scenario associated with a reference date and time according to the date and time information from among a plurality of scenarios stored in the storage unit and associated with a scenario key transmitted from the request source device, and selects a message according to the identified scenario as a message to be delivered to the communication terminal; A message delivery system having:

3. A message delivery method executed by a computer, which sends a message to a communication terminal using a telephone number as a destination via a server of a communication carrier in response to a delivery request from the communication terminal, comprising: a storage unit storing a scenario for determining the content to be included in the message, a reference date and time to which a different date and time is assigned for each scenario, and a scenario key for identifying a combination of a plurality of different scenarios; acquires a scenario key and date and time information according to a distribution request transmitted from a requesting device used by a message distribution requester; Among the multiple scenarios stored in the storage unit and associated with the scenario key transmitted from the requesting device, a scenario associated with a reference date and time corresponding to the date and time information is identified, and a message corresponding to the identified scenario is selected as a message to be delivered to the communication terminal. A message delivery method including:

Images