JP2024048824A - Distribution server and distribution method - Google Patents

Abstract

To distribution server and a distribution method which distribute, without delay, the second and subsequent messages which are distributed in accordance with on-demand distribution or a status of a distributed message even if a large amount of distribution information to be distributed by batch is stored in a distribution queue.SOLUTION: In a distribution system 1, a distribution server 10 includes: a sorting processing unit 15 which stores messages to be distributed by batch in a standard distribution queue 13, and stores messages to be distributed on demand in accordance with a distribution request in a priority distribution queue 14; a distribution processing unit 17 which executes a process for distributing the messages stored in the standard distribution queue 13 if no message is stored in the priority distribution queue 14; and a reception processing unit 18 which generates third distribution information regarding the second and subsequent messages to be distributed based on status information indicating a status of a distributed message which has been distributed by the distribution processing unit, and stores the information in the priority distribution queue 14.SELECTED DRAWING: Figure 1

Description

The present invention relates to a distribution server and a distribution method.

There is a messaging service that notifies information online (for example, see Patent Document 1). In such a service, when a message is delivered, the delivery information is first queued (stored) in a delivery queue. Next, the delivery information stored in the delivery queue is retrieved one by one, and a delivery process is performed to deliver the retrieved delivery information. There are two delivery process methods: bulk delivery by batch processing, and on-demand delivery. The former is a process in which multiple messages are delivered together each time the batch processing timing arrives, for example, a process in which 10,000 messages are delivered at 10:00. In the latter on-demand delivery, delivery requests are accepted individually, and messages are delivered in real time in response to the delivery requests.

In addition, with the message service, subsequent messages are delivered depending on the status of the first message. For example, a message containing operation buttons marked "Yes" and "No" is delivered along with an instruction such as "Would you like to watch a video on how to use My Page in more detail?". If "Yes" is pressed in response to this message, a message containing the video is sent.

JP 2007-241732 A

However, when bulk delivery is performed, a large amount of delivery information is stored in the delivery queue through batch processing. If a delivery request for on-demand delivery is received when a large amount of delivery information is stored in the delivery queue, there is a possibility that the on-demand delivery will be delayed. In on-demand delivery, it is better for messages to be delivered without delay after the delivery request is accepted. In addition, it is also desirable for the second and subsequent messages, which are delivered depending on the status of messages that have already been delivered, to be delivered without delay so as to meet the expectations of users who are waiting for a reply.

The present invention has been made in consideration of the above circumstances, and its purpose is to provide a distribution server and distribution method that can deliver on-demand messages and second and subsequent messages that are delivered according to the status of already delivered messages without delay, even when a large amount of distribution information is stored in a distribution queue due to batch processing.

In order to solve the above-mentioned problems, the delivery server according to the present invention includes a distribution processing unit that stores first delivery information related to a message to be delivered by batch processing in a standard delivery queue and stores second delivery information related to a message to be delivered on demand in response to a delivery request in a priority delivery queue different from the standard delivery queue; a delivery processing unit that determines whether the second delivery information is stored in the priority delivery queue, executes processing to deliver a message corresponding to the second delivery information if the second delivery information is stored, and executes processing to deliver a message corresponding to the first delivery information stored in the standard delivery queue if the second delivery information is not stored in the priority delivery queue; and a reception processing unit that generates third delivery information related to the second and subsequent messages to be delivered according to the situation based on status information indicating the status of the delivered message delivered by the delivery processing unit, and stores the third delivery information in the priority delivery queue regardless of whether the delivered message corresponding to the generated third delivery information is a message delivered by the batch processing or a message delivered on demand.

The delivery method according to the present invention is a delivery method performed by a computer, in which a sorting processor stores first delivery information related to a message to be delivered by batch processing in a standard delivery queue, and stores second delivery information related to a message to be delivered on demand in response to a delivery request in a priority delivery queue different from the standard delivery queue, a delivery processor determines whether the second delivery information is stored in the priority delivery queue, and if the second delivery information is stored, executes a process to deliver a message corresponding to the second delivery information, and if the second delivery information is not stored in the priority delivery queue, executes a process to deliver a message corresponding to the first delivery information stored in the standard delivery queue, and a reception processor generates third delivery information related to the second or subsequent messages to be delivered according to the situation based on status information indicating the status of the delivered message delivered by the delivery processor, and stores the third delivery information in the priority delivery queue regardless of whether the delivered message corresponding to the generated third delivery information is a message delivered by the batch processing or a message delivered on demand.

According to the present invention, even if a large amount of delivery information is stored in a delivery queue due to batch processing, on-demand delivery and second and subsequent messages that are delivered according to the status of messages already delivered can be delivered without delay.

1 is a block diagram showing an example of a distribution system 1 according to an embodiment. FIG. 11 is a diagram showing an example of a message displayed on the communication terminal 40 according to the embodiment. 2 is a diagram showing an example of information stored in a distribution information storage unit 11 according to the embodiment; FIG. 4 is a diagram showing an example of information stored in a delivery message history information storage unit 12 according to the embodiment; FIG. 2 is a diagram showing a flow of processing performed by the distribution system 1 according to the embodiment. FIG. 2 is a diagram showing a flow of processing performed by the distribution system 1 according to the embodiment. FIG. 2 is a diagram showing a flow of processing performed by the distribution system 1 according to the embodiment. FIG. 2 is a diagram showing a flow of processing performed by the distribution system 1 according to the embodiment. FIG. 2 is a diagram showing a flow of processing performed by the distribution system 1 according to the embodiment. FIG. 2 is a diagram showing a flow of processing performed by the distribution system 1 according to the embodiment. FIG. 2 is a diagram showing an example of information stored in a distribution information storage unit 11 according to the embodiment; FIG. 2 is a diagram showing an example of information stored in a distribution information storage unit 11 according to the embodiment; FIG.

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

FIG. 1 is a block diagram showing an example of a distribution system 1 according to an embodiment. The distribution system 1 includes, for example, a distribution server 10, a company server 20, a telecommunications carrier server 30, and a communication terminal 40.

The distribution server 10 is an information processing device that distributes messages requested by a company corresponding to the company server 20. For example, a server device or a computer such as a personal computer (PC) can be used as the distribution server 10. The distribution server 10 communicates wirelessly or wired with the company server 20 and the telecommunications carrier server 30.

The distribution server 10 controls the distribution of messages requested by the enterprise server 20 to the communication terminal 40. For example, the distribution server 10 distributes RCS messages using RCS (Rich Communication Services), a message service addressed to a telephone number.

The distribution server 10 distributes messages according to the content of requests from companies corresponding to the corporate server 20. For example, the distribution server 10 distributes messages using two distribution methods: bulk distribution by batch processing and on-demand distribution, according to the content of requests from companies. Bulk distribution is a process in which multiple messages are distributed at once each time the batch processing timing arrives, for example, a process in which 10,000 messages are distributed at 10:00. On-demand distribution is a process in which messages are distributed in real time in response to a distribution request.

The distribution server 10 also transmits a series of messages according to a scenario in response to the content of a request from a company corresponding to the company server 20. The scenario here is information in which the second and subsequent messages to be distributed are set according to the status of the first message that has already been distributed, or the user's action (response) to the message.

For example, assume that a scenario is set to deliver, as the first message, a carousel (called a first message) showing a link to a specific page corresponding to "My Page" or the like.
In this case, the second message is delivered depending on the status of the first message that has already been delivered. Specifically, for example, when the first message is received by the communication terminal 40, a setting is made such that a message including operation buttons with "Yes" and "No" indicated (referred to as a second message) is delivered together with a guidance text such as "Would you like to watch a video on how to use My Page in detail?"
Furthermore, the third message is delivered in response to a user's action (response) to the second message. Specifically, for example, when the operation button indicating "Yes" is operated in response to the second message, a message including a video is set as the next message.
On the other hand, if the operation button indicating "No" is operated in response to the second message, a message containing content different from the above video, for example a URL corresponding to My Page, is set in the scenario as the third message.

The corporate server 20 is an information processing device managed by a company. For example, a server device, a computer such as a PC, etc. can be applied as the corporate server 20. Any company or organization, such as a bank, insurance company, travel agency, public organization, etc. can be applied as a company corresponding to the corporate server 20. The corporate server 20 communicates with the distribution server 10 wirelessly or via wired communication. The corporate server 20 requests the company that manages the distribution server 10 to distribute a message to the communication terminal 40.

The telecommunications carrier server 30 is a server device managed by a telecommunications carrier. The telecommunications carrier is, for example, an MNO (Mobile Network Operator) that provides communication services using telephone numbers to the communication terminal 40 using communication lines that the carrier owns or operates.

The communication service here includes communication using RCS. In communication using RCS, the communication carrier server 30 transmits a message corresponding to RCS to the communication terminal 40 in response to a distribution request from the distribution server 10. In a communication service using a message corresponding to RCS, Webhook information for the RCS message transmitted to the communication terminal 40 is transmitted to the distribution server 10 via the communication carrier server 30. The Webhook information includes the status of the RCS message distributed to the communication terminal 40, for example, information indicating that the RCS message has been received by the communication terminal 40. The Webhook information also includes the state of the content in the RCS message, for example, an operation button, etc., being operated. The communication carrier server 30 performs wireless or wired communication between the distribution server 10 and the communication terminal 40.

The communication terminal 40 is an information processing device used by a user or the like. For example, a smartphone, a mobile phone, a computer such as a PC, or the like can be used as the communication terminal 40. The communication terminal 40 has a display unit such as a liquid crystal display that displays information, and an operation unit such as a touch panel that accepts operations by the user. The communication terminal 40 receives messages from the company server 20 via the distribution server 10 and the communication carrier server 30.

A contract is made by a user or the like with a telecommunications carrier corresponding to the telecommunications carrier server 30 for using a communication service using the communication terminal 40. The communication terminal 40 is capable of communicating using a communication service provided by the contracted telecommunications carrier. A telephone number is assigned to the communication terminal 40, and the communication terminal 40 has a function for communicating with this telephone number as the destination, i.e., communicating using an RCS.

Figure 2 is a diagram showing an example of a message displayed on a communication terminal 40 according to an embodiment. As shown in Figure 2, for example, a series of messages in accordance with a scenario SR are delivered from a company "Cde Corporation" to a communication terminal 40 of a user who is a customer of the company. This figure shows an example in which scene SN1 is delivered as the first message, scene SN2 is delivered as the second message, and scene SN3 is delivered as the third message in accordance with the scenario SR.

In this case, for example, the scenario SR indicates that scene SN1 is to be delivered, that scene SN2 is to be delivered when scene SN1 is received by the communication terminal 40, and that scene SN3 is to be delivered when scene SN2 is received by the communication terminal 40. It also indicates that when a specific content included in scene SN3 (for example, an operation button labeled "Yes" or "No") is tapped, a message corresponding to the scene according to the operation is to be delivered.

For example, in the distribution system 1, distribution is performed according to the above scenario SR in the following steps.

In accordance with the scenario SR, the distribution server 10 first notifies the telecommunications carrier server 30 of a distribution request to distribute a message corresponding to scene SN1 to the communication terminal 40. In response to the distribution request, the telecommunications carrier server 30 distributes the message corresponding to scene SN1 to the communication terminal 40. When the distributed message is received by the communication terminal 40, the telecommunications carrier server 30 transmits Webhook information (arrival information) indicating that the message has been received by the communication terminal 40 to the distribution server 10.

When the distribution server 10 receives the arrival information from the telecommunications carrier server 30, it notifies the telecommunications carrier server 30 of a distribution request to distribute the next message corresponding to scene SN2 to the communication terminal 40 in accordance with the scenario SR. In response to the distribution request, the telecommunications carrier server 30 distributes the message corresponding to scene SN2 to the communication terminal 40. When the distributed message is received by the communication terminal 40, the telecommunications carrier server 30 transmits Webhook information (arrival information) indicating that the message has been received by the communication terminal 40 to the distribution server 10.
When the distribution server 10 receives the arrival information from the telecommunications carrier server 30, it notifies the telecommunications carrier server 30 of a distribution request to distribute the next message corresponding to scene SN3 to the communication terminal 40 in accordance with the scenario SR. In response to the distribution request, the telecommunications carrier server 30 distributes the message corresponding to scene SN3 to the communication terminal 40. When the distributed message is received by the communication terminal 40, the telecommunications carrier server 30 transmits Webhook information (arrival information) indicating that the message has been received by the communication terminal 40 to the distribution server 10.
In addition, when a specific content (e.g., an operation button indicating "Yes" or "No", etc.) in a message corresponding to scene SN3 is operated, the telecommunications carrier server 30 transmits to the distribution server 10 Webhook information (action information) indicating that the specific content has been operated.

When the distribution server 10 receives the action information from the telecommunications carrier server 30, it notifies the telecommunications carrier server 30 of a distribution request to distribute the next message corresponding to scene SN4 to the communication terminal 40 in accordance with the scenario SR. In response to the distribution request, the telecommunications carrier server 30 distributes the message corresponding to scene SN4 to the communication terminal 40.

Returning to FIG. 1, the distribution server 10 includes, for example, a distribution information storage unit 11, a distribution message history information storage unit 12, a standard distribution queue 13, a priority distribution queue 14, a distribution processing unit 15, a response determination unit 16, a distribution processing unit 17, and a reception processing unit 18.

The delivery information storage unit 11, the delivery message history information storage unit 12, the standard delivery queue 13, and the priority delivery queue 14 are provided, for example, in a storage unit (not shown) provided in the delivery server 10. The storage unit provided in the delivery server 10 is configured with a storage medium, for example, a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read/write memory (RAM), a read only memory (ROM), or any combination of these storage media. The storage unit provided in the delivery server 10 stores programs for executing various processes of the delivery server 10, and temporary data used when performing various processes.

The distribution information storage unit 11 stores distribution information. Distribution information is information about a series of messages to be distributed to users.

Fig. 3 is a diagram showing an example of information stored in the distribution information storage unit 11. As shown in Fig. 3, for example, the distribution information storage unit 11 stores distribution information. The distribution information includes information corresponding to items such as a case ID, a distribution pattern, a distribution unit ID, an individual management number, an original message ID, a scenario ID, and a scene ID.
In addition, in this figure, an example is shown in which the distribution information includes both information for identifying a scenario (such as a distribution pattern, a scenario ID, and a scene ID, which will be described later) and information for identifying a user to whom a message is to be notified (such as a distribution unit ID and an individual management number, which will be described later), but this is not limited to this example. The information for identifying a scenario in the distribution information and the information for identifying a user may be configured to be stored as separate information.

The case ID is identification information linked to the company account (customer account) corresponding to the requesting company server 20.

The distribution pattern is information indicating whether distribution is performed after a compatibility determination is made, or whether distribution is performed without making a compatibility determination. The compatibility determination here is to determine whether or not the communication terminal 40 to which the distribution is to be made supports RCS. If the result of the compatibility determination shows that the communication terminal 40 to which the distribution is to be made supports RCS, for example, the distribution server 10 makes a distribution request to distribute a message compatible with RCS to the communication terminal 40. On the other hand, if the result of the compatibility determination shows that the communication terminal 40 to which the distribution is to be made does not support RCS, a distribution request is made to distribute a message compatible with a message service other than RCS, for example, SMS (Short Message Service), to the communication terminal 40.

The delivery unit ID is identification information assigned to each processing unit of delivery. The delivery unit here is, for example, the unit of bulk delivery by batch processing. For example, when 10,000 messages are delivered in bulk at 10:00, a unique delivery unit ID is assigned to that bulk delivery.

The individual management number is identification information for individually identifying the message to be delivered. For example, by adding destination information such as the telephone number of the delivery destination to the delivery unit ID as the individual management number, a unique identification information is assigned to each message to be delivered.

The scenario ID is identification information for identifying a scenario. As the scenario ID, unique information consisting of numbers and letters, such as "6730...", is assigned to each scenario.

The scene ID is identification information for identifying the scene corresponding to the message included in the scenario. For example, the scene ID corresponding to the first (first) message to be notified in a scenario is set to "start", the scene ID corresponding to the next (second) message to be notified is set to "next", the scene ID corresponding to the next (third) message to be notified is set to "next_1", etc.

The original message ID is an ID that is assigned by the telecommunications carrier server 30 when a delivery request is notified to the telecommunications carrier server 30 to deliver a message, and is identification information for identifying the message delivered by the telecommunications carrier server 30. The message ID is, for example, included in the Webhook information and notified from the telecommunications carrier server 30 to the delivery server 10.

The delivery message history information storage unit 12 stores delivery message history information. Delivery message history information is information that indicates the history of messages delivered to users, for example, the history of messages being received, specific content being operated, etc.

Figure 4 is a diagram showing an example of information stored in the delivery message history information storage unit 12. As shown in Figure 4, for example, the delivery message history information storage unit 12 stores information corresponding to items such as arrival information and action information.

The arrival information is Webhook information notified by the telecommunications carrier server 30 in response to a delivery request from the delivery server 10, and is information indicating that the message has been received by the communication terminal 40. The arrival information stores information corresponding to items such as the message ID and status, for example. The message ID is an ID assigned by the telecommunications carrier server 30 in response to a message delivery request. The status is information indicating the status of the delivered message; for example, when a message is received by the communication terminal 40, information indicating "arrived" is set as the status.

The action information is Webhook information notified by the telecommunications carrier server 30 in response to a delivery request from the delivery server 10, and is information indicating that a specific content in a message has been operated. The action information stores information corresponding to items such as a message ID and postback data. The message ID is an ID given by the telecommunications carrier server 30 in response to a delivery request for a message. The postback data is information set in advance by the delivery server 10 for each content so that the content is notified when the content is operated. For example, the postback data stores information corresponding to items such as a scenario ID, a scene ID, and a scene ID of the next message. Alternatively, information indicating the division displayed in the content, such as "yes" or "no", may be set as the postback data. The scenario ID and scene ID here are the scenario ID and scene ID corresponding to the operated content. The scene ID of the next message is the scene ID corresponding to the message set to be sent next when the content is operated in the scenario.

Returning to FIG. 1, the standard delivery queue 13 is a queue in which delivery information for messages to be delivered by bulk delivery is stored.

For example, the standard delivery queue 13 includes a standard response determination queue 130, an RCS standard queue 131, and an SMS standard queue 132. The standard response determination queue 130 stores delivery information of messages for which a pattern for performing response determination is set as the delivery pattern for bulk delivery. The RCS standard queue 131 stores delivery information of messages to be notified to communication terminals 40 that have been determined to be RCS-compatible as a result of the response determination. The SMS standard queue 132 stores delivery information of messages to be notified to communication terminals 40 that have been determined to be RCS-incompatible as a result of the response determination, and delivery information of messages for which a pattern for not performing response determination is set as the delivery pattern for bulk delivery.

The priority delivery queue 14 is a queue (waiting queue) that stores messages to be delivered by on-demand delivery, as well as second and subsequent messages to be delivered depending on the status of already delivered messages and user actions (responses) to already delivered messages.

For example, the priority delivery queue 14 includes a response determination priority queue 140, a response determination RCS priority queue 141, a response determination SMS priority queue 142, an SMS priority queue 143, and an RCS priority queue 144. The response determination priority queue 140 stores delivery information of messages for which a pattern for performing response determination is set as a delivery pattern of on-demand delivery. The response determination RCS priority queue 141 stores delivery information of messages to be notified to communication terminals 40 that have been determined to be compatible with RCS as a result of the response determination. The response determination SMS priority queue 142 stores delivery information of messages to be notified to communication terminals 40 that have been determined to be incompatible with RCS as a result of the response determination. The SMS priority queue 143 stores delivery information of messages for which a pattern for not performing response determination is set as a delivery pattern of on-demand delivery. The RCS priority queue 144 stores delivery information of second and subsequent messages to be delivered depending on the status of the first message.

The distribution processing unit 15, the response determination unit 16, the distribution processing unit 17, and the reception processing unit 18 are functional units that perform signal processing. The functional units are realized by having a central processing unit (CPU) that the distribution server 10 has as hardware execute a program.

When distributing messages requested by companies, the distribution processing unit 15 distributes and stores the messages in either the standard distribution queue 13 or the priority distribution queue 14. When the time for bulk distribution arrives, the distribution processing unit 15 refers to the distribution information storage unit 11 to obtain distribution information for the group of messages to be distributed at that time. The distribution processing unit 15 stores the obtained distribution information in the standard distribution queue 13.

More specifically, the sorting processor 15 sorts messages according to the bulk delivery pattern. For example, the sorting processor 15 stores bulk delivery messages for which a pattern for which a response determination is performed is set as the delivery pattern in the standard response determination queue 130. In addition, the sorting processor 15 stores bulk delivery messages for which a pattern for which a response determination is not performed is set as the delivery pattern in the standard SMS queue 132.

When the distribution processing unit 15 receives a request for on-demand delivery from the corporate server 20, it refers to the delivery information storage unit 11 to obtain delivery information for the message corresponding to the on-demand delivery. The distribution processing unit 15 stores the obtained delivery information in the priority delivery queue 14.

The distribution processing unit 15 may distribute message delivery information according to the delivery pattern of on-demand delivery.

Specifically, the sorting processor 15 stores delivery information of messages for on-demand delivery, for which a delivery pattern is set so that a response determination is performed, in the response determination priority queue 140. On the other hand, it stores delivery information of messages for which a pattern is set so that a response determination is not performed, in the SMS priority queue 143.

The compatibility determination unit 16 performs compatibility determination. The compatibility determination is a process for determining whether the communication terminal 40 is compatible with RCS. Generally, most communication terminals 40 are compatible with SMS, but there are many cases where some communication terminals 40 are compatible with RCS and some are not. For example, if an RCS application is installed in the communication terminal 40 and activation including consent to the terms of use for communication using RCS has been performed, the communication terminal 40 is a terminal that supports RCS. On the other hand, if an RCS application is not installed in the communication terminal 40, or if an RCS application is installed but not activated, the communication terminal 40 is a terminal that does not support RCS.

The response determination unit 16 makes a response determination by requesting the telecommunications carrier server 30 to make a response determination. Specifically, the response determination unit 16 requests the response determination by notifying the telecommunications carrier server 30 of information including the telephone number to which the message is to be delivered. The telecommunications carrier server 30 makes a response determination in response to the request from the distribution server 10, and notifies the distribution server 10 of the result, that is, information indicating whether or not the communication terminal 40 corresponding to the telephone number to which the message is to be delivered supports RCS.

The response determination unit 16 requests a response determination for the telephone number that is the delivery destination of the message corresponding to the delivery information stored in the response determination standard queue 130. Based on the result of the response determination notified by the communication carrier server 30, the response determination unit 16 stores the delivery information stored in the response determination standard queue 130 in either the RCS standard queue 131 or the SMS standard queue 132. Specifically, the response determination unit 16 stores the delivery information of the message to be notified to the communication terminal 40 that supports RCS in the RCS standard queue 131. On the other hand, the response determination unit 16 stores the delivery information of the message to be notified to the communication terminal 40 that does not support RCS in the SMS standard queue 132.

The response determination unit 16 also requests a response determination for the telephone number that is the delivery destination of the message corresponding to the delivery information stored in the response determination priority queue 140. Based on the result of the response determination notified by the communication carrier server 30, the delivery information stored in the response determination priority queue 140 is stored in either the post-response determination RCS priority queue 141 or the post-response determination SMS priority queue 142. The response determination unit 16 stores the delivery information of the message to be notified to the communication terminal 40 that supports RCS in the post-response determination RCS priority queue 141. The response determination unit 16 stores the delivery information of the message to be notified to the communication terminal 40 that does not support RCS in the post-response determination SMS priority queue 142.

The distribution processing unit 17 performs processing for distributing a message. The distribution processing unit 17 notifies the telecommunications carrier server 30 of all or part of the distribution information, thereby making a distribution request to distribute a message corresponding to the distribution information to the destination communication terminal 40. In response to the distribution request, the telecommunications carrier server 30 issues a message ID for the message corresponding to the distribution request, and notifies the distribution server 10 of the issued message ID. The distribution processing unit 17 generates distribution message history information based on the message ID notified by the telecommunications carrier server 30, and stores the generated information in the distribution message history information storage unit 12.

When making a delivery request, the delivery processing unit 17 first executes processing to deliver a message corresponding to the delivery information stored in the priority delivery queue 14 if delivery information is stored in the priority delivery queue 14. Then, if no delivery information is stored in the priority delivery queue 14, the delivery processing unit 17 executes processing to deliver a message corresponding to the delivery information stored in the standard delivery queue 13.

This allows messages corresponding to delivery information stored in the priority delivery queue 14 to be sent with priority over messages corresponding to delivery information stored in the standard delivery queue 13. Therefore, even if a large amount of delivery information corresponding to messages related to bulk delivery is stored in the standard delivery queue 13, it is possible to prevent delays in the delivery of messages corresponding to delivery information stored in the priority delivery queue 14, such as messages related to on-demand delivery.

Specifically, the distribution processing unit 17 determines whether or not distribution information is stored in the priority distribution queue 14. If distribution information is stored in the priority distribution queue 14, the distribution processing unit 17 performs processing to distribute a message corresponding to the distribution information stored in the priority distribution queue 14.

More specifically, if there is delivery information stored in the RCS priority queue 141 after the response determination, the delivery processing unit 17 makes a delivery request to the telecommunications carrier server 30 for a message corresponding to the delivery information. Also, if there is delivery information stored in the SMS priority queue 142 after the response determination, the delivery processing unit 17 makes a delivery request to the telecommunications carrier server 30 for a message corresponding to the delivery information. Also, if there is delivery information stored in the SMS priority queue 143, the delivery processing unit 17 makes a delivery request to the telecommunications carrier server 30 for a message corresponding to the delivery information. If there is delivery information stored in the RCS priority queue 144, the delivery processing unit 17 makes a delivery request to the telecommunications carrier server 30 for a message corresponding to the delivery information.

In the process for delivering a message performed by the delivery processing unit 17, which of the multiple priority queues (e.g., post-response-determination RCS priority queue 141, post-response-determination SMS priority queue 142, SMS priority queue 143, and RCS priority queue 144, etc.) to respond to first may be arbitrarily determined. For example, a priority order may be assigned to each of the multiple priority queues, and delivery may be controlled to begin with the queue with the highest priority. Alternatively, the delivery processes for the multiple priority queues may be made independent, and if the respective priority queues are not looked at in each delivery process, the standard queue may be looked at.

On the other hand, if no delivery information is stored in the priority delivery queue 14, the delivery processing unit 17 performs processing to deliver a message corresponding to the delivery information stored in the standard delivery queue 13. More specifically, the delivery processing unit 17 makes a delivery request to the telecommunications carrier server 30 for a message corresponding to the delivery information stored in the RCS standard queue 131. The delivery processing unit 17 makes a delivery request to the telecommunications carrier server 30 for a message corresponding to the delivery information stored in the SMS standard queue 132.

Here, the distribution processing unit 17 distributes the message with the postback data set to the communication terminal 40 that supports RCS. The message with the postback data set is, for example, included in advance in the distribution information.

By distributing a message in which postback data is set, the distribution server 10 can receive Webhook information including the postback data from the telecommunications carrier server 30. In other words, after the message is distributed, if the content in the message is operated by the user of the communication terminal 40, the telecommunications carrier server 30 transmits to the distribution server 10 Webhook information including the information set in the postback data of the operated content.

The distribution server 10 sets information in the postback data that indicates, for example, the next message to be sent in response to an operation on the content. This makes it easy for the distribution server 10 to identify the next message to be delivered based on the Webhook information notified by the telecommunications carrier server 30.

The reception processing unit 18 receives Webhook information. When a message is delivered, the telecommunications carrier server 30 notifies the delivery message of information indicating the status of the delivered message, such as Webhook information indicating arrival information and action information, according to changes in the status of the delivered message. The reception processing unit 18 refers to the delivery message history information storage unit 12 based on the Webhook information notified by the telecommunications carrier server 30, and extracts the corresponding delivery message history information.

The reception processing unit 18 performs processing for delivering the second and subsequent messages based on the Webhook information notified from the communication carrier server 30 .
For example, when the Webhook information is arrival information and indicates that a message has been received by the communication terminal 40, the reception processing unit 18 refers to the delivery information storage unit 11 based on the message ID included in the Webhook information. The reception processing unit 18 acquires a scene ID of a message corresponding to the currently received arrival information from the referenced delivery information storage unit 11. The reception processing unit 18 increments the acquired scene ID and determines whether or not a message corresponding to the incremented scene ID exists in the delivery information. When a message corresponding to the incremented scene ID exists, the reception processing unit 18 queues (stores) the delivery information of the message corresponding to the incremented scene ID in the RCS priority queue 144.

Alternatively, when the Webhook information is action information, the reception processing unit 18 refers to the postback data in the Webhook information and determines whether or not the scene ID of the next message is set in the postback data. When a scenario ID and a scene ID are set in the postback data, and further, a scene ID of the next message is set, the reception processing unit 18 determines that the message corresponding to the scene ID will be delivered as the second or subsequent message. On the other hand, when a scenario ID or a scene ID is not set in the postback data, the reception processing unit 18 determines that the message will not be delivered as the second or subsequent message. Also, when a scenario ID and a scene ID are set in the postback data but a scene ID of the next message is not set, the reception processing unit 18 determines that the second or subsequent message will not be delivered.

When distributing the second or subsequent messages, the reception processing unit 18 refers to the distribution information storage unit 11 based on the scenario ID in the postback data, and extracts distribution information corresponding to the scenario ID. The response determination unit 16 increments and updates the scene ID in the extracted distribution information, and generates the updated distribution information as distribution information corresponding to the second or subsequent messages. The reception processing unit 18 stores the generated distribution information in the RCS priority queue 144.

As shown in FIG. 1, the telecommunications carrier server 30 includes, for example, a distribution API 31, a compatibility determination API 32, and a reception API 33. The distribution API 31 distributes a message in response to a distribution request from the distribution server 10 to the destination communication terminal 40. The compatibility determination API 32 determines whether the communication terminal 40 supports RCS in response to a request from the distribution server 10, and transmits the result to the distribution server 10. The reception API 33 transmits Webhook information according to the status of messages that have already been distributed to the distribution server 10.

The flow of processing performed by the distribution system 1 will now be described with reference to Figures 5 to 10. Figures 5 to 10 are sequence diagrams showing the flow of processing performed by the distribution system 1 according to the embodiment.

Figure 5 shows an overview of the flow of batch processing and on-demand processing (processing related to on-demand delivery).

As shown in FIG. 5, when the time to perform bulk delivery arrives, the distribution processing unit 15 of the delivery server 10 first refers to the delivery information storage unit 11 to obtain delivery information for the group of messages to be delivered at that time (step S1). The distribution processing unit 15 stores the obtained delivery information in the standard delivery queue 13 (step S2).

On the other hand, when the distribution processing unit 15 receives a request for on-demand delivery at any timing (step S3), it refers to the delivery information storage unit 11 to obtain delivery information for the message corresponding to the on-demand delivery, and stores the obtained delivery information in the priority delivery queue 14 (step S4).

Next, the distribution processing unit 17 determines whether or not distribution information is stored in the priority distribution queue 14. If distribution information is stored in the priority distribution queue 14, the distribution processing unit 17 acquires the distribution information stored in the priority distribution queue 14 (step S5) and makes a distribution request for the message corresponding to the acquired distribution information to the telecommunications carrier server 30 (step S7).

On the other hand, if no delivery information is stored in the priority delivery queue 14, the delivery processing unit 17 acquires the delivery information stored in the standard delivery queue 13 (step S6) and makes a delivery request for the message corresponding to the acquired delivery information to the telecommunications carrier server 30 (step S7).

When the delivery API 31 of the telecommunications carrier server 30 receives a delivery request from the delivery processing unit 17 of the delivery server 10, it delivers a message to the destination communication terminal 40 in response to the received delivery request (step S8). When the delivered message is received by the communication terminal 40, a control signal indicating that the communication terminal 40 has received the message is sent to the telecommunications carrier server 30 (step S9). When the reception API 33 receives a control signal from the communication terminal 40, it sends to the delivery server 10 Webhook information (arrival information) indicating that the message has been received by the communication terminal 40 (step S10).

The reception processing unit 18 of the distribution server 10 determines whether to distribute the second and subsequent messages based on the Webhook information notified by the telecommunications carrier server 30. If the reception processing unit 18 is to distribute the second and subsequent messages, it generates distribution information corresponding to the second and subsequent messages and stores the generated distribution information in the priority distribution queue 14 (the RCS priority queue 144) (step S11).

Figure 6 shows the flow of batch processing, particularly the process of delivering messages that have a delivery pattern set for which a response determination is performed.

As shown in FIG. 6, first, when the time to perform bulk delivery arrives (step S101), the distribution processing unit 15 refers to the delivery information storage unit 11 to acquire delivery information for a group of messages to be delivered at that time (step S102). Among the acquired delivery information, the distribution processing unit 15 stores the delivery information of messages for which a delivery pattern is set to perform a response determination in the response determination standard queue 130 (step S103).

The response determination unit 16 acquires the distribution information stored in the response determination standard queue 130 (step S104), and requests a response determination by notifying the telecommunications carrier server 30 of all or part of the acquired distribution information (step S105). The response determination API 32 of the telecommunications carrier server 30 performs a response determination in response to the request from the distribution server 10, and transmits the result to the distribution server 10 (step S106).

The response determination unit 16 acquires the response determination result notified to the distribution server 10 by the communication carrier server 30. Depending on the acquired result, the response determination unit 16 stores the distribution information stored in the response determination standard queue 130 in either the RCS standard queue 131 or the SMS standard queue 132 (steps S107A and S107B). Specifically, the distribution server 10 stores, among the distribution information stored in the response determination standard queue 130, the information for which the communication terminal 40, which is the destination of the message corresponding to the distribution information, supports RCS in the RCS standard queue 131 (step S107A). On the other hand, the distribution server 10 stores, among the distribution information stored in the response determination standard queue 130, the information for which the communication terminal 40, which is the destination of the message corresponding to the distribution information, does not support RCS in the SMS standard queue 132 (step S107B).

The distribution processing unit 17 acquires the distribution information stored in the RCS standard queue 131 and the SMS standard queue 132 (steps S108A, S108B). Specifically, the distribution processing unit 17 acquires the distribution information stored in the RCS standard queue 131 (step S108A) and refers to the distribution information storage unit 11 based on the acquired distribution information (step S109). The distribution processing unit 17 notifies the carrier server 30 of all or part of the distribution information, thereby making a distribution request for the message corresponding to the distribution information (step S110).

The delivery processing unit 17 also acquires the delivery information stored in the SMS standard queue 132 (step S108B), and generates a delivery request including the contents of the message to be delivered and the telephone number of the delivery destination by referring to the delivery information storage unit 11 based on the acquired delivery information (step S109). The delivery processing unit 17 notifies the communication carrier server 30 of the delivery request, requesting that the message corresponding to the delivery information be delivered (step S110).

When the delivery API 31 of the telecommunications carrier server 30 accepts the delivery request, it issues a message ID corresponding to the accepted message and notifies the delivery server 10 of the issued message ID (step S111). The delivery processing unit 17 of the delivery server 10 stores the message ID received from the telecommunications carrier server 30 in the delivery message history information storage unit 12 (step S112).

Figure 7 shows the flow of batch processing, particularly the process of delivering messages with a delivery pattern that does not perform response determination.

As shown in FIG. 7, when the time to perform bulk delivery arrives (step S201), the sorting processor 15 first refers to the delivery information storage unit 11 to acquire delivery information for a group of messages to be delivered at that time (step S202). Among the acquired delivery information, the sorting processor 15 stores the delivery information for messages for which a delivery pattern that does not perform response determination is set in the SMS standard queue 132 (step S203).

The delivery processing unit 17 acquires the delivery information stored in the SMS standard queue 132 (step S204) and generates a delivery request by referencing the delivery information storage unit 11 based on the acquired delivery information (step S205). The delivery processing unit 17 notifies the carrier server 30 of the delivery request, requesting that the message corresponding to the delivery information be delivered (step S206). When the delivery API 31 accepts the delivery request, it issues a message ID corresponding to the accepted message and notifies the delivery server 10 of the issued message ID (step S207). The delivery processing unit 17 stores the message ID received from the carrier server 30 in the delivery message history information storage unit 12 (step S208).

Figure 8 shows the flow of on-demand processing, particularly the process of delivering a message with a delivery pattern set for which a response determination is made.

As shown in FIG. 8, first, the distribution processing unit 15 receives an on-demand request requesting on-demand distribution (step S301), and acquires distribution information corresponding to the on-demand requested message by referring to the distribution information storage unit 11 (step S302). If the message corresponding to the acquired distribution information is a message for which a distribution pattern is set to perform a response determination, the distribution processing unit 15 stores the distribution information in the response determination priority queue 140 (step S303).

The response determination unit 16 acquires the distribution information stored in the response determination priority queue 140 (step S304), and requests a response determination by notifying the telecommunications carrier server 30 of all or part of the acquired distribution information (step S305). The response determination API 32 of the telecommunications carrier server 30 performs a response determination in response to the request from the distribution server 10, and transmits the result to the distribution server 10 (step S306).

The response determination unit 16 acquires the response determination result notified to the distribution server 10 by the communication carrier server 30. Depending on the acquired result, the response determination unit 16 stores the distribution information stored in the response determination priority queue 140 in either the response determination RCS priority queue 141 or the response determination SMS priority queue 142 (steps S307A and S307B). Specifically, the distribution server 10 stores, among the distribution information stored in the response determination priority queue 140, the information for which the communication terminal 40, which is the destination of the message corresponding to the distribution information, supports RCS in the response determination RCS priority queue 141 (step S307A). On the other hand, the distribution server 10 stores, among the distribution information stored in the response determination priority queue 140, the information for which the communication terminal 40, which is the destination of the message corresponding to the distribution information, does not support RCS in the response determination SMS priority queue 142 (step S307B).

The delivery processing unit 17 acquires the delivery information stored in the post-response-determination RCS priority queue 141 and the post-response-determination SMS priority queue 142 (steps S308A, S308B). Specifically, the delivery processing unit 17 acquires the delivery information stored in the post-response-determination RCS priority queue 141, and generates a delivery request including the contents of the message to be delivered and the telephone number of the delivery destination, etc., by referring to the delivery information storage unit 11 based on the acquired delivery information (step S309). The delivery processing unit 17 notifies the carrier server 30 of all or part of the delivery information, thereby making a delivery request for the message corresponding to the delivery information (step S310).

The delivery processing unit 17 also acquires the delivery information stored in the SMS priority queue 142 after determining whether to respond (step S308B), and generates a delivery request including the contents of the message to be delivered and the telephone number of the delivery destination by referring to the delivery information storage unit 11 based on the acquired delivery information (step S309). The delivery processing unit 17 notifies the communication carrier server 30 of the delivery request, requesting that the message corresponding to the delivery information be delivered (step S310).

When the delivery API 31 of the telecommunications carrier server 30 accepts the delivery request, it issues a message ID corresponding to the accepted message and notifies the delivery server 10 of the issued message ID (step S311). The delivery processing unit 17 of the delivery server 10 stores the message ID received from the telecommunications carrier server 30 in the delivery message history information storage unit 12 (step S312).

Figure 9 shows the flow of on-demand processing, particularly the process of delivering a message with a delivery pattern that does not perform response determination.

As shown in FIG. 9, first, the distribution processing unit 15 receives an on-demand request (step S401), and acquires distribution information corresponding to the on-demand requested message by referring to the distribution information storage unit 11 (step S402). If the message corresponding to the acquired distribution information is a message for which a distribution pattern that does not perform response determination is set, the distribution processing unit 15 stores the distribution information in the SMS priority queue 143 (step S403).

The delivery processing unit 17 acquires the delivery information stored in the SMS priority queue 143 (step S404) and generates a delivery request by referencing the delivery information storage unit 11 based on the acquired delivery information (step S405). The delivery processing unit 17 notifies the carrier server 30 of the delivery request, requesting that a message corresponding to the delivery information be delivered (step S406). When the delivery API 31 accepts the delivery request, it issues a message ID corresponding to the accepted message and notifies the delivery server 10 of the issued message ID (step S407). The delivery processing unit 17 stores the message ID received from the carrier server 30 in the delivery message history information storage unit 12 (step S408).

Figure 10 shows the process flow for delivering subsequent messages when a response to a delivered message is received.

As shown in FIG. 10, when a user of the communication terminal 40 operates on a delivered message, the communication carrier server 30 receives control information from the communication terminal 40 indicating that the operation has been performed (steps S501A and S501B). Specifically, when a message delivered to the communication terminal 40 (a carousel showing a title such as "My Page Login") is received, the reception API 33 receives control information indicating that the message has been received (step S501A). In addition, when an operation button (an operation button showing "Yes", "No", etc.) of a specific content included in the message delivered to the communication terminal 40 is tapped, the reception API 33 receives control information indicating that the operation button of the content has been operated (step S501B).

The reception API 33 generates Webhook information based on the control information received from the communication terminal 40, and transmits the generated Webhook information to the distribution server 10 (step S502). Specifically, when a message is received, the reception API 33 transmits Webhook information (arrival information) based on the control information received in step S501A to the distribution server 10. On the other hand, when content is operated, the reception API 33 transmits Webhook information (action information) based on the control information received in step S501B to the distribution server 10.

When the reception processing unit 18 of the delivery server 10 acquires the Webhook information received from the communication carrier server 30, it generates a message (second or subsequent message) to be delivered according to the contents notified in the Webhook information (step S503). Specifically, the reception processing unit 18 identifies a message corresponding to the acquired Webhook information, and extracts delivery message history information corresponding to the identified message from the delivery message history information storage unit 12. The reception processing unit 18 also refers to the postback data in the Webhook information and determines whether or not to deliver the second or subsequent message according to the operation. When delivering the second or subsequent message, the reception processing unit 18 refers to the delivery information storage unit 11 based on the postback data and extracts the corresponding delivery information. The reception processing unit 18 sets the message to be delivered from the second or subsequent message by incrementing the scene ID of the extracted delivery information. The algorithm for identifying the message to be delivered from the second or subsequent message may be determined arbitrarily. For example, the message to be delivered from the second onwards may be set based on an algorithm that automatically selects "02" after "01" based on a number shown at a specific position in the scene ID, such as the beginning or after a specific symbol, such as "01" or "02" in 01-XXX or 02-XXX.

The reception processing unit 18 stores the delivery information corresponding to the second and subsequent messages to be delivered in the RCS priority queue 144 (step S504).

The distribution processing unit 17 acquires the distribution information stored in the RCS priority queue 144 (step S505), and based on the acquired distribution information, references the distribution information storage unit 11 and the distribution message history information storage unit 12 (step S506) to generate a distribution request including the contents of the message to be distributed and the telephone number of the destination. The distribution processing unit 17 notifies the communication carrier server 30 of the distribution request, requesting that the message corresponding to the distribution information be distributed (step S507). When the distribution API 31 accepts the distribution request, it distributes the accepted message to the communication terminal 40 (step S508).

Here, Figs. 11 and 12 are diagrams showing examples of delivery information when delivering second and subsequent messages. Figs. 11 and 12 are diagrams showing examples of information stored in the delivery information storage unit 11 according to the embodiment.

Figure 11 shows an example of delivery information corresponding to the second and subsequent messages that are delivered in response to the reception of a message corresponding to the arrival information, based on the Webhook information (arrival information) notified when a message is received, as shown in step S501A of Figure 10.

As shown in FIG. 11, for example, in the delivery information corresponding to the second and subsequent messages, the message ID notified in the Webhook information is set as the original message ID. The scenario ID is set to the scenario ID of the scenario corresponding to the second and subsequent messages to be delivered. The scene ID is set to "next_k" (k is an integer equal to or greater than 1) corresponding to the scene ID of the second and subsequent messages to be delivered.

Figure 12 shows an example of delivery information corresponding to the second and subsequent messages that are delivered in response to an operation corresponding to the action information based on the Webhook information (action information) notified when an operation is performed on an operation button (here, the operation button showing "Yes") included in specific content as shown in step S501B of Figure 10.

As shown in FIG. 12, for example, in the delivery information corresponding to the second and subsequent messages, the message ID notified in the Webhook information is set as the original message ID. The scenario ID is set to the scenario ID of the scenario corresponding to the second and subsequent messages to be delivered. The scene ID is set to "yes", which corresponds to the scene ID of the second and subsequent messages to be delivered. This scene ID indicates the identification information of the message to be delivered when the operation button indicating "yes" is operated.

In the above, an example was given of storing the distribution information in a queue (standard distribution queue 13 or priority distribution queue 14), but this is not limited to this. It is sufficient that at least information capable of identifying a scenario corresponding to a message to be notified to the user is stored in the queue. For example, key information for identifying the distribution information may be stored in the queue, rather than the distribution information itself.

As described above, the distribution server 10 of the embodiment includes a distribution processing unit 15, a distribution processing unit 17, and a reception processing unit 18. The distribution processing unit 15 stores distribution information (first distribution information) related to a message to be distributed by batch processing in the standard distribution queue 13. The distribution processing unit 15 stores distribution information (second distribution information) related to a message to be distributed on demand in response to a distribution request in the priority distribution queue 14 (a queue different from the standard distribution queue 13). The distribution processing unit 17 determines whether the second distribution information is stored in the priority distribution queue 14, and if the second distribution information is stored in the priority distribution queue 14, executes a process to distribute a message corresponding to the second distribution information. If the second distribution information is not stored in the priority distribution queue 14, the distribution processing unit 17 executes a process to distribute a message corresponding to the first distribution information stored in the standard distribution queue 13. The reception processing unit 18 generates distribution information (third distribution information) related to the second and subsequent messages. The second and subsequent messages are messages that are delivered according to the status based on status information indicating the status of the delivered message delivered by the delivery processing unit 17. The reception processing unit 18 stores third delivery information corresponding to the second and subsequent messages in the priority delivery queue 14, regardless of whether the delivered message is a message delivered by batch processing or a message delivered on demand.

In this way, in the delivery server 10 of this embodiment, messages to be delivered on demand can be stored in a priority delivery queue different from messages to be delivered by batch processing, and messages to be delivered by batch processing can be delivered when messages to be delivered on demand are not stored in the queue. Therefore, even if a large number of messages to be delivered by batch processing are stored in the queue, messages to be delivered on demand can be delivered without delay. Moreover, when delivering the second or subsequent messages, the first message can be stored in the priority delivery queue regardless of whether it is a message delivered by batch processing or a message delivered on demand. Therefore, messages to be delivered according to the status of messages that have already been delivered can be delivered without delay even if a large number of messages to be delivered by batch processing are stored in the queue. Therefore, even if a large amount of delivery information by batch processing is stored in the delivery queue, messages to be delivered on demand and according to the status of messages after the first message can be delivered without delay. This meets the expectations of users who are waiting for the second or subsequent messages after receiving the first message, or users who are waiting for the next message by operating an operation button or the like on the received message.

The distribution server 10 of the embodiment distributes a message using RCS (Rich Communication Services) via the communication carrier server 30. The distribution processing unit 17 distributes the message via the communication carrier server 30. The reception processing unit 18 acquires, as status information, Webhook information notified from the communication carrier server 30 when a distributed message is received by the communication terminal 40 (distribution destination). The reception processing unit 18 generates distribution information (third distribution information) corresponding to the second and subsequent messages based on the acquired Webhook information. This enables the distribution server 10 of the embodiment to distribute a message using RCS and to grasp whether a message has been received using the Webhook information. Therefore, the next message can be distributed in response to the reception of a message.

The distribution server 10 of the embodiment distributes a message using RCS (Rich Communication Services) via the telecommunications carrier server 30. The distribution processing unit 17 sets postback data including information indicating a next message to be sent in response to the content being operated on the content (for example, an operation button indicating "yes" or "no") included in the message. The distribution processing unit 17 distributes the message in which the postback data including the next message is set to the content via the telecommunications carrier server 30. The reception processing unit 18 acquires, as status information, Webhook information notified from the telecommunications carrier server 30 in association with the content being operated. The reception processing unit 18 generates distribution information (third distribution information) corresponding to the second or subsequent message based on information indicating the next message indicated in the postback data included in the acquired Webhook information. This makes it possible for the distribution server 10 of the embodiment to distribute a message using RCS and to grasp whether the content has been operated using the Webhook information. Therefore, the next message can be distributed in response to the content being operated.

The distribution server 10 of the embodiment further includes a compatibility determination unit 16. The compatibility determination unit 16 performs processing to determine whether or not the communication terminal 40 (destination of the message) supports RCS. When it is determined that the communication terminal 40 supports RCS according to the result of the processing performed by the compatibility determination unit 16, the distribution processing unit 17 performs processing to distribute a message using RCS. This allows the distribution server 10 of the embodiment to determine whether or not the communication terminal 40, which is the destination of the message, supports RCS before distributing the message. Therefore, it is possible to distribute a message using RCS to a communication terminal 40 that supports RCS, and not to distribute a message using RCS to a communication terminal 40 that does not support RCS.

The distribution system 1 and the distribution server 10 in the above-mentioned embodiment may be realized in whole or in part by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into the computer system and executed to realize the function. Note that the term "computer system" here 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, and storage devices such as hard disks built into the computer system. Furthermore, the term "computer-readable recording medium" may include a medium that dynamically holds a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in such a case. Furthermore, the above-mentioned program may be a program for realizing a part of the above-mentioned function, or may be a program that can realize the above-mentioned function in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

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

1...Distribution system, 10...Distribution server, 11...Distribution information storage unit, 12...Distribution message history information storage unit, 13...Standard distribution queue, 14...Priority distribution queue, 15...Distribution processing unit, 16...Response determination unit, 17...Distribution processing unit, 18...Reception processing unit, 30...Telecommunications carrier server, 40...Communications terminal

Claims (5)

a distribution processing unit that stores first distribution information related to messages to be distributed by batch processing in a standard distribution queue, and stores second distribution information related to messages to be distributed on demand in response to a distribution request in a priority distribution queue different from the standard distribution queue;
a delivery processing unit that determines whether the second delivery information is stored in the priority delivery queue, and if the second delivery information is stored, executes a process for delivering a message corresponding to the second delivery information, and if the second delivery information is not stored in the priority delivery queue, executes a process for delivering a message corresponding to the first delivery information stored in the standard delivery queue;
a reception processing unit that generates third delivery information related to second and subsequent messages to be delivered according to the situation based on status information indicating the status of the delivered message delivered by the delivery processing unit, and stores the third delivery information in the priority delivery queue regardless of whether the delivered message corresponding to the generated third delivery information is a message delivered by the batch processing or an on-demand message;
A distribution server comprising: The delivery server delivers a message using Rich Communication Services (RCS) via a communication carrier server,
The delivery processing unit delivers a message via the communication carrier server,
The reception processing unit acquires, as the status information, Webhook information notified from the communication carrier server in association with the message distributed by the distribution processing unit being received by the distribution destination, and generates the third distribution information based on the acquired Webhook information.
The distribution server according to claim 1 . The delivery server delivers a message using Rich Communication Services (RCS) via a communication carrier server,
the delivery processing unit delivers, via the communication carrier server, a message in which postback data including information indicating a next message to be sent in response to the operation of the content is set in the content included in the message;
the reception processing unit acquires, as the status information, Webhook information notified from the communication carrier server in association with the operation of the content, and generates the third delivery information based on information indicating the next message indicated in the postback data included in the acquired Webhook information;
The distribution server according to claim 1 . The message delivery device further includes a determination processing unit that performs processing for determining whether or not a communication terminal to which the message is to be delivered supports the RCS,
the distribution processing unit, when it is determined that the communication terminal is compatible with the RCS according to a result of the process performed by the determination processing unit, performs a process for distributing a message using the RCS.
The distribution server according to claim 2 or 3. 1. A computer-implemented distribution method, comprising:
a distribution processing unit stores first delivery information relating to messages to be distributed by batch processing in a standard delivery queue, and stores second delivery information relating to messages to be distributed on demand in response to a delivery request in a priority delivery queue different from the standard delivery queue;
a delivery processing unit determines whether the second delivery information is stored in the priority delivery queue, and if the second delivery information is stored, executes a process for delivering a message corresponding to the second delivery information, and if the second delivery information is not stored in the priority delivery queue, executes a process for delivering a message corresponding to the first delivery information stored in the standard delivery queue,
a reception processing unit generates third delivery information related to a second or subsequent message to be delivered in accordance with the situation based on status information indicating the status of the delivered message delivered by the delivery processing unit, and stores the third delivery information in the priority delivery queue regardless of whether the delivered message corresponding to the generated third delivery information is a message delivered by the batch processing or an on-demand message.
Delivery method.

Images