JP2023111042A - Distribution server, distribution method, and program - Google Patents

Abstract

To prevent a log, which is generated using Webhook information, from being complicated by identifying a message to which a reply is performed based on the Webhook information.SOLUTION: A distribution server comprises: a message generation unit for generating a message using an RCS which makes post back data including identification information for identifying the message correspondent to a content included in the message; an acquisition unit for acquiring Web hook information including the post back data, the Webhook information being reported from a communication carrier when the content is operated; an identification unit for identifying the message corresponding to the operated content using the identification information included in the Webhook information; and a log generation unit which generates a log using the Webhook information and generates the log, in which the identification information is not included, in accordance with an output destination of the log.SELECTED DRAWING: Figure 3

Description

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

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

Among such electronic notification services, message services addressed to mobile phone numbers are widely used. Message services addressed to mobile phone numbers include, for example, RCS (Rich Communication Services). By using the mobile phone number as the destination, the message can be sent even if the e-mail address of the recipient of the notification is unknown.

In a message service with a mobile phone number as the destination, for example, a message is sent to the customer's communication terminal in response to a request from the requester of a company, etc., and the response obtained from the customer is sent as a log to the requester. It is carried out. When RCS is used, when an operation is performed to respond to a message, the details of the operation and the telephone number of the communication device on which the operation was performed are notified from the carrier as Webhook information. For example, a log can be generated based on this webhook information.

JP 2007-241732 A

By the way, the Webhook information does not show the association between the notified message and the action information, which is the response to the message. For example, with respect to responses made after the same message has been sent multiple times, there has been a problem that the Webhook information does not indicate to which message of the multiple transmissions the response has been made.

Postback data can be used for this task. Postback data is information that can be set to buttons indicating content used to respond to messages, for example, 'yes' and 'no', and is included in webhook information when an operation is performed on the content. This is the information notified by For example, a message is generated in which an identifier that can identify the message is set in the postback data for buttons such as "yes" and "no". When the button of the message generated in this manner is tapped, Webhook information including an identifier is notified corresponding to the operation. A message to which a response has been made can be identified based on the identifier extracted from the notified Webhook information.

However, when information such as an identifier is set in the postback data and a log is generated based on the Webhook information, the generated log includes information such as the identifier, resulting in a problem that the log becomes complicated.

The present invention has been made in view of such circumstances, and its object is to be able to identify a message to which a response has been made based on Webhook information, and to prevent the log generated using Webhook information from becoming complicated. To provide a distribution server, a distribution method, and a program capable of

In order to solve the above-described problems, a distribution server according to the present invention is a distribution server that transmits a message using RCS (Rich Communication Services) to a communication terminal via a telecommunications carrier, wherein: a message generation unit that generates the message in which postback data including identification information that identifies the message is associated with the content to be received; and Webhook information that is notified from the telecommunications carrier when the content is operated, , an acquisition unit for acquiring Webhook information including the postback data; an identification unit for identifying the message corresponding to the operated content using the identification information included in the Webhook information; and using the Webhook information. and a log generation unit that generates the log that does not include the identification information according to the output destination of the log.

Further, in order to solve the above-described problems, a delivery method according to the present invention provides a delivery method performed by a computer, which is a delivery server, for transmitting a message using RCS (Rich Communication Services) to a communication terminal via a telecommunications carrier. In the method, a message generation unit generates the message in which postback data including identification information for identifying the message is associated with content included in the message, and an acquisition unit performs the operation when the content is operated. is the Webhook information notified from the telecommunications carrier and includes the postback data, and the specifying unit uses the identification information included in the Webhook information to correspond to the operated content A log generation unit generates a log using the Webhook information, and generates the log that does not include the identification information according to the output destination of the log.

Further, in order to solve the above-described problems, the present invention provides a program for causing a computer to operate as the distribution server described above, the program for causing the computer to function as each unit provided in the distribution server. be.

According to the present invention, it is possible to determine whether or not a communication device that has accessed a website indicated by a link in a message is the communication device of the user to whom the message is to be sent.

1 is a schematic block diagram showing a configuration example of an information processing system 1 according to an embodiment; FIG. It is a figure which shows the example of the message based on embodiment. 2 is a block diagram showing a configuration example of distribution server 10 according to the embodiment; FIG. It is a figure which shows the example of the delivery information 120 which concerns on embodiment. It is a figure which shows the example of the response information 121 which concerns on embodiment. 4 is a sequence diagram showing the flow of processing performed by the information processing system 1 according to the embodiment; FIG.

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

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

The distribution server 10 is a server device managed by an operator who provides a service of sending messages to the communication terminal 40 . The distribution server 10 transmits (distributes) a message to the communication terminal 40 via the carrier server 30 . The distribution server 10 transmits a message using RCS (Rich Communication Services), which is a message service whose destination is a telephone number. The distribution server 10 performs wireless or wired communication with the company server 20 and the carrier server 30 .

The company server 20 is a server device managed by a requester who requests the information processing system 1 to deliver a message. The requester is, for example, a company or organization that provides information to the destination user, such as a bank or an insurance company. The company server 20 performs wireless or wired communication with the distribution server 10 .

The carrier server 30 is a server device managed by a carrier. The telecommunications carrier is, for example, an MNO (Mobile Network Operator) that provides the communication terminal 40 with a communication service using a telephone number using a communication line owned or operated by itself. Communication services include communication using RCS. The carrier server 30 performs wireless or wired communication with the distribution server 10 and the communication terminal 40 . The carrier server 30 transmits a message using RCS to the communication terminal 40 in response to the distribution request from the distribution server 10 .
In a communication service using RCS, Webhook information for a message sent to communication terminal 40 is sent to distribution server 10 . The Webhook information is information indicating the status of the message, for example, the status that the message has been received by the communication terminal 40, or that the message has been read or a response operation has been performed.

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

FIG. 2 is a diagram illustrating an example of a message according to the embodiment; FIG. 2 shows information displayed on the display screen of the communication terminal 40 when the respective messages of the text M1, the carousel C, the text M2, and the button B are notified to the communication terminal 40 in order. .

As shown in the example of this figure, the communication terminal 40 is notified of a plurality of messages. Multiple messages are sent, for example, according to predetermined scenarios. Here, the scenario is information that defines what messages are to be sent in what order according to the messages to be sent and the responses to the messages that have been sent.
Among the messages used in the scenario, messages for which response operations can be performed, such as carousel C and button B, include contents used for response operations. For example, the carousel C includes buttons CB1 and CB2 that accept tap operations. For example, Button B includes buttons labeled "Yes" and "No".
Postback data can be set by the distribution server 10, which is the distributor, in the contents used for these response operations. By setting postback data in the content, Webhook information including the postback data set in the content is notified from the carrier server 30 to the distribution server 10 when the content is operated.

FIG. 3 is a block diagram showing a configuration example of the distribution server 10 according to the embodiment. As shown in FIG. 2 , distribution server 10 includes communication unit 11 , storage unit 12 , and control unit 13 . The communication unit 11 communicates with the company server 20 and the carrier server 30 . The storage unit 12 stores various types of information such as distribution information 120 and response information 121 . The delivery information 120 is information about a message to be sent to the communication terminal 40. FIG. The response information 121 is information about responses to messages sent to the communication terminal 40 .

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

The control unit 13 includes an acquisition unit 130, a message generation unit 131, a specification unit 132, and a log generation unit 133, for example.
Acquisition unit 130 acquires various types of information. For example, the acquisition unit 130 acquires information about a message generated by a message generation unit 131, which will be described later, and causes the storage unit 12 to store the acquired information. By writing the information about the message to the storage unit 12 , it becomes possible to use the information about the message as the distribution information 120 . The acquisition unit 130 also acquires the webhook information received from the carrier server 30 and causes the storage unit 12 to store the acquired webhook information. By writing the webhook information to the storage unit 12 , it becomes possible to use this webhook information as the response information 121 .

Message generator 131 generates a message to be transmitted to communication terminal 40 . The message generator 131 generates messages that can be used in RCS, such as rich cards and tip lists. The message generation unit 131 generates a message in which postback data is associated with content that can be used in the message, such as the carousel C, for example. The message generator 131 generates a message such that the postback data includes identification information for identifying the message.

The specifying unit 132 specifies, when a response is made to a message, to which message the response is made based on the identification information included in the Webhook information.

For example, consider the case of sending a message regarding automobile insurance to the communication terminal 40 of the user. If the user owns multiple cars and has car insurance for each car, a message about each car insurance is notified. Therefore, the user's communication terminal 40 receives a plurality of messages showing similar contents. When the user operates the communication terminal 40 and presses a button for any message, Webhook information is notified corresponding to the operation. Since the Webhook information notified here includes the telephone number of the communication terminal 40 of the user, it can be understood that the user has responded to the message. However, since the Webhook information is given a message ID different from that of the message to which the response is made, a case may occur in which it is not possible to specify which of the plurality of messages has been responded to.
Also, for example, consider a case where a message regarding billing is sent to the user's communication terminal 40 every month. Messages about monthly billing have a uniform format, and follow the same scenario, for example, creating a message with a "confirm" button. For such billing messages, for example, October and November messages are created and sent to the communication terminal 40 of the user in sequence. After the messages for October and November are received by the communication terminal 40, when the user operates the "Confirm" button in the messages, Webhook information is notified in response to the operation. In this case as well, it is not possible to specify from the phone number or message ID in the Webhook information whether the "confirm" button in the message for October or November was operated.

As described above, even when a plurality of messages are transmitted to the same communication terminal 40, it is desirable to be able to specify which of the plurality of messages the response is to.

As a countermeasure against this, in the information processing system 1 of the present embodiment, information that can identify which message is set is set in the postback data associated with the button. That is, the webhook information notified when the button is operated and there is a reaction (action) from the communication terminal 40 of the user includes the postback data in which the information that can specify which message is set is included. to As a result, when there is an action from the communication terminal 40 of the user, it is possible to specify which message the response is to.

The log generator 133 generates logs. Logs are information about sent messages and status information and responses to those messages. is information indicating

The log generator 133 generates a log according to the output destination. For example, when generating a log to be notified to the client, the log generator 133 generates a log that does not include identification information. A plurality of messages indicating the same content addressed to the same telephone number, such as a message regarding insurance contracts for each of a plurality of automobiles owned by the user as described above, or a message regarding billing sent monthly, is sent to the same telephone number for a predetermined period of time. If a request is made to distribute the messages sequentially after the elapse of time, it is likely that the log will become complicated and difficult to understand if information that enables identification of which message has received a response from the user is included in the log. Therefore, the log generation unit 133 generates a log that does not include identification information according to the output destination.

FIG. 4 is a diagram showing an example of distribution information 120 according to the embodiment. Distribution information 120 is generated for each scenario.

The distribution information 120 includes, for example, a scenario ID and information corresponding to each of a plurality of messages (message 1, message 2, message 3, . . . ). A scenario ID is information that identifies a scenario. The message includes information corresponding to the scene ID and information corresponding to the type of message. The scene ID is information for identifying which message, that is, what order the message is in the scenario when a plurality of messages are notified in the scenario.
This figure shows an example of distribution information 120 corresponding to the scenario shown in FIG. 2, where message 1 corresponds to text M and message 2 corresponds to carousel C.
Message 1 has a scene ID and text data. The text data is text data indicating the content of the message notified in text.
Message 2 has a scene ID and postback data associated with the rich card. The postback data is postback data to be set in the rich card included in the carousel C. FIG.
In this embodiment, a scenario ID, a scene ID, a unique ID, and an arbitrary character string are set in this postback data. A unique ID is information that uniquely identifies a message. The arbitrary character string may be set arbitrarily, and is, for example, a character string that describes the content. In addition, here, a scenario ID, a scene ID, a unique ID, and an arbitrary character string are set in the postback data as an example, but the present invention is not limited to this. The postback data may be set with at least identification information that can identify the message, and information corresponding to a scenario ID, a scene ID, a unique ID, a part of an arbitrary character string, a combination thereof, or the like is set. may

FIG. 5 is a diagram showing an example of response information 121 according to the embodiment. The response information 121 is generated for each reaction obtained with respect to the message sent to the communication terminal 40 .

The response information 121 includes, for example, information corresponding to each item of telephone number, time stamp, and postback data. These pieces of information in the response information 121, that is, the information corresponding to the respective items of telephone number, time stamp, and postback data are included in the Webhook information.
The phone number is the phone number of the communication device on which the button operation was performed. The time stamp is information indicating the time when the button was operated. Postback data is postback data associated with an operated button.

Processing performed by the information processing system 1 will be described with reference to FIG. FIG. 6 is a sequence diagram showing the flow of processing performed by the information processing system 1 according to the embodiment.

The distribution server 10 transmits a distribution request to the carrier server 30 (step S1). The distribution server 10 generates a message in which postback data is set in the content of the message, and requests the carrier server 30 to distribute the generated message to the communication terminal 40 .

Upon receiving the distribution request from the distribution server 10, the carrier server 30 transmits a distribution response to the distribution server 10 (step S11). The communication carrier server 30 assigns an ID (message ID_1) to the message to be delivered indicated in the received delivery request, and transmits the assigned (message ID_1) to the delivery server 10, thereby responding to the delivery request. Give a response.
The carrier server 30 transmits the message to the communication terminal 40 in response to the distribution request (step S12). The carrier server 30 transmits to the communication terminal 40 the message corresponding to (message ID_1) assigned in step S11.
After transmitting the message to the communication terminal 40, the carrier server 30 notifies the distribution server 10 of the status (step S13). The carrier server 30 notifies the distribution server 10 of the status by sending (message ID_1) assigned in step S11 and the status (SENT) indicating that the message has been sent.

When receiving the message, the communication terminal 40 transmits a reception status (control information for notifying the communication carrier server 30 that the message has been received) (step S14).
Upon receiving the reception status from the communication terminal 40, the carrier server 30 notifies the distribution server 10 of the status (step S15). The carrier server 30 notifies the distribution server 10 of the status by transmitting (message ID_1) assigned in step S11 and the status (DELIVERED) indicating that the message has been received.
When the communication terminal 40 performs a read operation (message display) on the message, the message ID_1 and the status (DISPLAYED) indicating that the message has been displayed are sent via the communication carrier server 30. The distribution server 10 is notified.

When a response operation to the message is performed, the communication terminal 40 transmits control information indicating that the response operation has been performed to the communication carrier server 30 (step S16).
Upon receiving the control information indicating that the response operation has been performed from the communication terminal 40, the carrier server 30 notifies the distribution server 10 of the status of the message by notifying the webhook information (step S17). A message ID_2 is assigned to the Webhook information, but the message ID_2 is not associated with the message ID_1. The carrier server 30 notifies the delivery server 10 of the status by sending message ID_2 and a status indicating that the message has been responded to. The status notified here corresponds to (Webhook information). The status notified here includes the content of the response, the date and time when the response operation was performed, the telephone number of the communication terminal 40 where the response operation was performed, and the postback data set in the content for which the response operation was performed. is included.

As described above, the distribution server 10 of the embodiment is an information processing system that transmits a message using RCS to the communication terminal 40 via the communication carrier. The information processing system 1 includes a message generation unit 131 , an acquisition unit 130 , an identification unit 132 and a log generation unit 133 . The message generator 131 generates a message in which postback data including identification information is associated with button B (an example of content) included in the message. An identifier is identification information for identifying a message, and is, for example, a scenario ID, scene ID, unique ID, or arbitrary character string. Acquisition unit 130 acquires Webhook information. The Webhook information is information notified from the carrier server 30 when button B in the transmitted message is operated. The webhook information includes postback data associated with button B. FIG. The identification unit 132 identifies the message corresponding to the operated content using the identification information included in the webhook information. The log generation unit 133 uses Webhook information to generate a log that does not include identification information according to the output destination. As a result, the delivery server 10 of the embodiment can identify the message to which the response is made based on the Webhook information, and can prevent the log generated using the Webhook information from becoming complicated.

In the distribution server 10 of the present embodiment, the message generation unit 131 generates a message in which postback data including a scenario ID and a scene ID are associated with content included in the message. As a result, the distribution server 10 of the embodiment can acquire Webhook information including the scenario ID and the scene ID when an operation is performed on the content, and can specify the message based on the acquired Webhook information. Become.

At least if a unique ID is set as postback data, it is possible to identify the message by referring to the distribution information 120 using the unique ID included in the webhook information. However, processing including the step of referring to the distribution information 120 must be performed. In particular, when a large number of scenarios used in the information processing system 1 are stored in the distribution information 120, the processing load of referring to the distribution information 120 and specifying one message increases. On the other hand, by including the scenario ID and the scene ID in the postback data, the message can be specified without referring to the delivery information 120, and the message can be specified without increasing the processing load. becomes possible.

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

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

1... information processing system, 10... delivery server, 20... company server, 30... carrier server, 40... communication terminal 40, 11... communication unit, 12... storage unit, 120... delivery information, 121... response information 121 ( Webhook information), 13... control unit, 130... acquisition unit, 131... message generation unit, 132... identification unit, 133... log generation unit 133

Claims (4)

A distribution server that transmits a message using RCS (Rich Communication Services) to a communication terminal via a communication carrier,
a message generation unit that generates the message in which postback data including identification information for identifying the message is associated with content included in the message;
an acquisition unit configured to acquire Webhook information including the postback data, which is Webhook information notified by the telecommunications carrier when the content is operated;
a specifying unit that specifies the message corresponding to the operated content using the identification information included in the Webhook information;
A distribution server comprising: a log generation unit that generates a log using the Webhook information and generates the log that does not include the identification information according to an output destination of the log. said message is sent according to a scenario,
The message generation unit associates the content included in the message with postback data including a scenario ID that identifies the scenario and a scene ID that identifies in which scene in the scenario the message is transmitted. generating said message;
The distribution server according to claim 1. A delivery method performed by a computer serving as a delivery server for sending a message using RCS (Rich Communication Services) to a communication terminal via a telecommunications carrier,
A message generation unit generates the message in which postback data including identification information for identifying the message is associated with content included in the message;
an acquisition unit that acquires Webhook information that is notified from the telecommunications carrier when the content is operated and that includes the postback data;
an identifying unit identifying the message corresponding to the manipulated content using the identification information included in the Webhook information;
A distribution method, wherein a log generation unit generates a log using the Webhook information, and generates the log that does not include the identification information according to an output destination of the log. 3. A program for causing a computer to operate as the distribution server according to claim 1 or 2, the program for causing the computer to function as each unit included in the distribution server.

Images