JP7398928B2 - Notification management device, notification management method, and program - Google Patents

Description

The present invention relates to a notification management device, a notification management method, and a program.

In the business of reminding users about payment, an operator such as a call center in charge of the business may send a bill such as a transfer form after confirming the user's intention to pay. This allows the user to make a transfer using the sent transfer form.

By the way, with the development of computers and communication network technology such as the Internet, technology for notifying information using messaging services has been developed. The messaging service is a mechanism for transmitting and receiving messages using functions such as RCS (Rich Communication Services), SMS (Short Message Service), and MMS (Multimedia Messaging Service). RCS is a standard for implementing an instant messenger for mobile phones at the terminal level, and uses a telephone number as a user account for communication. Furthermore, in RCS, the upper limit of the number of characters that can be sent is set larger than in conventional SMS and MMS. It is conceivable that such a messaging service could be used to send an electronic invoice corresponding to a transfer form to perform a reminder service. Patent Document 1 discloses a technique for prompting a user to view notification contents (content) by changing a display area in which unviewed notifications are displayed. By using this technique, it becomes possible to make it easier for the user to recognize the message that sent the bill.

JP2017-91507A

However, if the scheduled payment date set on the invoice has passed, a late payment fee may be incurred. The transfer form is prepared with the assumption that payment will be made on the scheduled payment date, and the amount is listed before any late fees are incurred. Therefore, if a transfer is made using a transfer form after the scheduled payment date has passed, there is a problem in that the amount equivalent to the late payment fee cannot be collected. Alternatively, if a delay charge has already been incurred, the billed amount, including the incurred delay charge, is stated assuming that payment will be made on the scheduled payment date. For this reason, if a transfer is made using a transfer form after the scheduled payment date, there is a problem in that it is not possible to collect the amount equivalent to the additional delay damages incurred after the scheduled payment date. Ta.

The present invention has been made in view of this situation, and provides a notification management device, a notification management method, and a notification management method that can bill an appropriate billing amount even if the billing amount changes depending on the date of payment. Provide programs.

In order to solve the above-mentioned problems of the present invention, the present invention provides an explanation of the billed amount corresponding to the scheduled payment date based on the status of the response in the confirmation message that is notified to the user terminal and confirms the scheduled payment date. a message creation unit that creates a billing message for writing or issuing the assigned time-limited billing code; a communication unit that notifies the user terminal of the billing message created by the message creation unit; When notifying the user terminal of a predetermined notification message, it is determined whether or not to resend the request message together with notification of the notification message based on the status of the response to the request message that has already been notified to the user terminal. a determination unit that makes a determination, and when retransmitting the request message together with the notification message according to the determination result determined by the determination unit, the notification message and the request message are displayed in a carousel on the user terminal; This is a notification management device comprising: a notification control unit configured to perform a notification management process;
In order to solve the above-mentioned problems of the present invention, the present invention provides an explanation of the billed amount corresponding to the scheduled payment date based on the status of the response in the confirmation message that is notified to the user terminal and confirms the scheduled payment date. a message creation unit that creates a billing message for writing or issuing the assigned time-limited billing code; a communication unit that notifies the user terminal of the billing message created by the message creation unit; When notifying the user terminal of a predetermined notification message, it is determined whether or not to resend the confirmation message together with notification of the notification message, based on the status of the response to the confirmation message that has already been notified to the user terminal. When the confirmation message is retransmitted together with the notification message according to the determination unit that makes the determination and the determination result determined by the determination unit, the notification message and the confirmation message are displayed in a carousel on the user terminal. This is a notification management device comprising: a notification control unit configured to perform a notification control unit;

Further, the present invention provides a time limit in which an explanation of the billed amount corresponding to the scheduled payment date is attached, based on a response status in a confirmation message for confirming the scheduled payment date, which the message creation unit notifies the user terminal. A communication unit notifies the user terminal of the billing message created by the message creation unit, and a determination unit sends the billing message to the user terminal. , when notifying a predetermined notification message, determine whether or not to resend the request message together with notification of the notification message based on the status of the response to the request message that has already been notified to the user terminal; When the control unit resends the request message together with the notification message according to the determination result determined by the determination unit, the notification message and the request message are displayed in a carousel on the user terminal. This is a notification management method that allows you to :
Further, the present invention provides a time limit in which an explanation of the billed amount corresponding to the scheduled payment date is attached, based on a response status in a confirmation message for confirming the scheduled payment date, which the message creation unit notifies the user terminal. A communication unit notifies the user terminal of the request message created by the message creation unit, and a determination unit sends the request message to the user terminal. , when notifying a predetermined notification message, determine whether or not to resend the confirmation message together with notification of the notification message based on the status of the response to the confirmation message that has already been notified to the user terminal; When the control unit resends the confirmation message together with the notification message according to the determination result determined by the determination unit, the notification message and the confirmation message are displayed in a carousel on the user terminal. This is a notification management method.

Further, the present invention is a program for causing a computer to operate as the notification management device described above, and a program for causing the computer to function as each section included in the notification management device.

According to the present invention, even if the billed amount is changed after the bill is notified, the appropriate billed amount can be billed.

FIG. 1 is a block diagram showing an example of the configuration of a notification system 1 according to an embodiment. 1 is a block diagram illustrating an example of the configuration of a notification management device 10 according to an embodiment. FIG. 3 is a diagram illustrating an example of a configuration of notification information 120 according to an embodiment. FIG. It is a figure showing an example of composition of response information 121 concerning an embodiment. It is a figure showing an example of composition of response information 121 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a figure showing an example of a display of user terminal 30 concerning an embodiment. It is a flowchart showing the flow of processing performed by the notification management device 10 according to the embodiment. It is a flowchart showing the flow of processing performed by the notification management device 10 according to the embodiment.

Embodiments of the invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing an example of the configuration of a notification system 1 according to an embodiment. The notification system 1 includes, for example, a notification management device 10, a company server 20, and a plurality of user terminals 30 (user terminals 30-1, 30-2, . . . , 30-N). The notification management device 10, the company server 20, and the user terminal 30 are communicably connected via a communication network NW. Note that although the example in FIG. 1 shows an example in which the notification system 1 is configured with one notification management device 10, the notification system 1 may be configured including a plurality of notification management devices 10. . Further, the notification system 1 may be configured to include a plurality of company servers 20.

The notification system 1 is a system that notifies the user terminal 30 of messages in response to requests from the corporate server 20. The message in this embodiment includes content to be notified to the user terminal 30, and includes, for example, text, still images and moving images including figures such as illustrations and photographs, and sound.

The notification in this embodiment is a notification using a messaging service. The messaging service is a mechanism for sending and receiving messages using functions such as RCS, SMS, and MMS. In a messaging service, messages are displayed along a predetermined direction (timeline direction) according to the notified time series.

The notification management device 10 receives a notification request from the company server 20. The notification request here is a signal requesting the customer's user terminal 30 to send a notification. The notification request includes, for example, information regarding the requestor (company) requesting the notification, information regarding the notification destination (user) to whom the notification is to be made, and information indicating the content of the notification. The configuration of the notification management device 10 will be explained in detail later.

The company server 20 is a server device of a company or the like that uses the notification system 1 to notify customers (users). The company server 20 includes, for example, a communication section 21 and a control section 22. The communication unit 21 communicates with the notification management device 10 via the communication network NW, and transmits a notification request to the notification management device 10. The control unit 22 centrally controls the company server 20, and creates a notification request based on a customer database (not shown), for example. For example, the control unit 22 creates a notification request for a normal notification (hereinafter referred to as a normal message). The normal message is, for example, a notification indicating the contents of various contracts, details of various bills, and deadlines such as expiration dates. The control unit 22 also creates a notification request for a notification requesting payment (hereinafter referred to as a request message). The payment message is, for example, a notification in which a two-dimensional barcode in which billing details such as payment deadline and billing amount are embedded is described (see FIG. 8).

In this embodiment, when notifying a billing message, the user is asked in advance what the scheduled payment date for the bill in the billing message is, and if a response indicating the scheduled payment date is obtained from the user, , notify you of billing messages. In the following explanation, a notification that asks the user to confirm the scheduled payment date will be referred to as a confirmation message.

The user terminal 30 is a smartphone, a tablet terminal, a PC (Personal Computer), a mobile phone, a game console, a touch pad, an e-book reader, a wearable terminal, etc., and includes an application program (hereinafter also referred to as an application) that performs a messaging service. ) is installed on the device.

The user terminal 30 includes, for example, a communication section 31, a display section 32, and a control section 33. The communication unit 31 communicates with the notification management device 10 via the communication network NW, and receives notifications from the notification management device 10 using a messaging service. The display unit 32 displays the content of the notification received from the notification management device 10. The control unit 33 controls the user terminal 30 in an integrated manner, for example, causes the display unit 32 to display the content of the notification from the notification management device 10, and also makes a sound that allows the user to recognize that there is a notification. Performs output and display (for example, displaying a banner image, etc.).

The communication network NW is, for example, a communication network that includes some or all of the Internet, a WAN (Wide Area Network), a LAN (Local Area Network), a provider device, a wireless base station, a dedicated line, and the like.

FIG. 2 is a block diagram showing an example of the configuration of the notification management device 10 according to the embodiment. The notification management device 10 includes, for example, a communication section 11, a storage section 12, and a control section 13. The communication unit 11 communicates with the notification management device 10 and the user terminal 30 via the communication network NW.

The storage unit 12 is an HDD (Hard Disk Drive), a flash memory, a RAM (Random Access Memory), or the like. The storage unit 12 stores programs executed to enable the functional units included in the control unit 13 to perform their functions, and data used when the programs are executed. The storage unit 12 stores, for example, notification information 120 and response information 121.

FIG. 3 is a diagram illustrating an example of the configuration of notification information 120 according to the embodiment. The notification information 120 is information used to make a notification in response to a notification request notified from the company server 20. Notification information 120 is created, for example, for each message for which a user is requested to be notified. The notification information 120 includes, for example, message ID, request source, notification destination, notification procedure, and retransmission conditions.

The message ID indicates identification information that uniquely identifies the message to be notified.
Information regarding the request source is shown in the request source. For example, an ID, name, and account are shown for the requester. The ID is identification information that uniquely identifies the requesting company. The name is the name of the company etc. corresponding to the ID. The account is a messaging service account used for notifications from companies and the like corresponding to the ID.
For the notification destination, for example, an ID, a name, and an account are shown as information related to the notification destination. The ID is identification information that uniquely identifies the user to be notified. The name is the name of the user corresponding to the ID. The account is a messaging service account used to notify the user corresponding to the ID.

The notification attribute indicates information regarding the content to be notified to the user. The notification attributes include, for example, notification date and time, scenario ID, scenario name, and notification type. The notification date and time is the date and time of the notification requested by the requester. The scenario ID is identification information that uniquely identifies the scenario to be notified. The scenario here is information indicating a template of the content to be notified. The scenario name is the name of the scenario corresponding to the scenario ID. The notification procedure is information indicating a procedure for notifying, etc., and here, it is information indicating a procedure for notifying a billing message.
The retransmission conditions indicate information indicating conditions for retransmitting a message. The retransmission conditions include, for example, an upper limit on the number of times and a deadline. The upper limit number of times indicates the upper limit of the number of retransmissions. The deadline indicates the deadline for retransmission.

The example in FIG. 3 shows that the requester is company X, the company X's messaging service account is 03-1111-2222, and the notification destination is user C. Further, it is indicated that the notification from company X to user C will be made at 10:00 on DD day of month MM, year YY. It is shown that the content of the notification is related to a payment reminder (payment reminder), which is created based on the scenario ID (0101). In this notification, a two-step procedure is taken: first, the user is notified of a confirmation message confirming the scheduled payment date, and then a billing message is notified in response to the notified confirmation message. It is shown that while there is no response to the billing message (no payment is made), the billing message is retransmitted an unlimited number of times (no upper limit) only on the notification date. Furthermore, if there is no response to the confirmation message (the scheduled payment date is not notified), it is indicated that the confirmation message will be resent up to three times within three months from the first notification.

4 and 5 are diagrams illustrating an example of the structure of response information 121 according to the embodiment. The response information 121 is information regarding a response from the user who notified the message. FIG. 4 shows the response information 121 in the confirmation message. FIG. 5 shows the response information 121 in the request message. In this way, response information 121 is generated for each message notified to the user.

The response information 121 shown in FIG. 4 includes, for example, message ID, response status, and retransmission conditions.
The message ID indicates identification information that uniquely identifies the notified message.
The response status indicates the status of the user's response to the notified message. The response status includes, for example, whether there is a response or not and the number of retransmissions. The presence/absence of response indicates whether there is a response from the user. The number of retransmissions indicates the number of times the message was retransmitted to the user.
The retransmission condition indicates the retransmission condition of the notified message, for example, the retransmission condition of the notification information 120.
In the example of FIG. 4, the response status to the confirmation message corresponding to the message ID (0001-01) shows that there is no response yet and that the message has already been retransmitted twice. Furthermore, the retransmission conditions for this message indicate that the message should be retransmitted up to three times and only within three months from the first notification.

The response information 121 shown in FIG. 5 includes, for example, message ID, response status, and retransmission conditions.
The message ID indicates identification information that uniquely identifies the notified message.
The response status indicates the status of the user's response to the notified message. The response here means that the bill indicated in the bill message is fulfilled, and for example, payment is made using the two-dimensional barcode or the like indicated in the bill message. The response status includes, for example, whether there is a response or not and the number of retransmissions. The presence or absence of response indicates whether or not there is a response by the user. The number of retransmissions indicates the number of times the message was retransmitted to the user.
The retransmission condition indicates the retransmission condition of the notified message, for example, the retransmission condition of the notification information 120.
In the example of FIG. 5, the response status to the billing message corresponding to the message ID (0001-02) shows that the payment has not yet been made and has already been resent twice. Further, as a retransmission condition for this message, it is indicated that the message is to be retransmitted only on the notified date without any limit to the number of times.

Returning to FIG. 2, the control unit 13 includes, for example, a message creation unit 130, a determination unit 131, and a notification control unit 132.
The message creation unit 130 creates a message to notify the user based on the notification information 120. The message creation unit 130 refers to the notification type in the notification attribute of the notification information 120 and determines the notification procedure for the message to be created. The message creation unit 130 creates a confirmation message if the scheduled payment date has not been confirmed yet. On the other hand, if there is a response to the confirmation message and the scheduled payment date can be confirmed, a billing message is created to charge the amount according to the scheduled payment date.
Note that, if the message to be created does not require prior confirmation, the message creation unit 130 creates a message (hereinafter referred to as a normal message) that notifies the content corresponding to the scenario ID. The message creation unit 130 causes the storage unit 12 to store the created message.

When notifying the user terminal 30 of a predetermined notification message, the determining unit 131 determines whether or not to resend the notified message together with the notification message based on the status of the message that has already been notified to the user terminal 30. judge. The notified messages here include a confirmation message and a request message. The determination unit 131 determines to resend the confirmation message based on the status of the response to the confirmation message, for example, when there is no response. The determination unit 131 determines to resend the billing message based on the response status of the billing message, for example, when payment using the bill linked to the billing message has not been made. Further, the notification message here includes a confirmation message and a normal message. The notification message here may include not only a new notification message but also a retransmission message.

The determination unit 131 refers to the response information 121 and obtains the response status of the confirmation message that has been notified to the user terminal 30. The determination unit 131 determines to resend the confirmation message together with the message notification when the response status of the notified confirmation message satisfies a predetermined condition. The predetermined conditions may be set arbitrarily. For example, the predetermined condition is a retransmission condition indicated in the notification information 120, and is a condition specified in a notification request received from the corporate server 20.

For example, the determination unit 131 obtains whether there is a response in the confirmation message based on the presence or absence of a response in the response information 121. The determination unit 131 obtains the retransmission deadline in the confirmation message based on the retransmission deadline in the retransmission conditions of the response information 121. Then, if there is no response to the confirmation message that has been notified to the user terminal 30 and the predetermined retransmission deadline for the confirmation message that has been notified to the user terminal 30 has not been exceeded, the determination unit 131 determines that the confirmation message will be retransmitted. judge.

Alternatively, the determination unit 131 may determine whether or not to retransmit the confirmation message based on the number of retransmissions in the confirmation message that has been notified to the user terminal 30. In this case, the determination unit 131 obtains the number of times the confirmation message has already been retransmitted based on the number of retransmissions in the response status of the response information 121. The determination unit 131 obtains the upper limit of the number of retransmissions in the confirmation message based on the upper limit of the number of retransmissions in the retransmission conditions of the response information 121. Then, the determination unit 131 determines to retransmit the confirmation message if the number of retransmissions in the confirmation message that has been notified to the user terminal 30 does not exceed a predetermined upper limit. In this case, the determination unit 131 determines that the number of retransmissions in the confirmation message that has been notified to the user terminal 30 does not exceed a predetermined upper limit, and does not exceed the predetermined retransmission deadline for the confirmation message. In this case, the confirmation message may be determined to be retransmitted. When notifying the user terminal 30 of a notification message, the determination unit 131 outputs to the notification control unit 132 the determination result of determining whether or not to resend the confirmation message together with the notification message.

The determination unit 131 refers to the response information 121 and obtains the response status of the billing message that has been notified to the user terminal 30. The determining unit 131 determines to resend the request message together with the notification message when the response status of the notified request message satisfies a predetermined condition. The predetermined conditions may be set arbitrarily. For example, the predetermined condition is a retransmission condition indicated in the notification information 120, and is a condition specified in a notification request received from the corporate server 20.

For example, the determination unit 131 acquires the presence or absence of a response in the request message based on the presence or absence of a response in the response information 121. The determination unit 131 obtains the retransmission deadline in the request message based on the retransmission deadline in the retransmission conditions of the response information 121. Then, if there is no response to the request message that has been notified to the user terminal 30 and the predetermined retransmission deadline for the request message that has been notified to the user terminal 30 has not been exceeded, the determination unit 131 determines that the request message will be retransmitted. judge.

Alternatively, the determination unit 131 may determine whether or not to retransmit the request message based on the number of retransmissions in the request message that has been notified to the user terminal 30. In this case, the determining unit 131 obtains the number of times the request message has already been retransmitted based on the number of retransmissions in the response status of the response information 121. The determination unit 131 obtains the upper limit of the number of retransmissions in the request message based on the upper limit of the number of retransmissions in the retransmission conditions of the response information 121. Then, the determination unit 131 determines to retransmit the billing message when the number of retransmissions in the billing message that has been notified to the user terminal 30 does not exceed a predetermined upper limit. In this case, the determination unit 131 determines that the number of retransmissions in the request message that has been notified to the user terminal 30 does not exceed a predetermined upper limit, and does not exceed the predetermined retransmission deadline for the request message. In this case, the request message may be determined to be retransmitted. When notifying the user terminal 30 of a notification message, the determination unit 131 outputs to the notification control unit 132 the determination result of determining whether or not to resend the request message together with the notification message.

The notification control unit 132 performs notification according to the determination result determined by the determination unit 131. When the determination unit 131 determines that the confirmation message should be retransmitted, the notification control unit 132 causes the confirmation message to be retransmitted to be displayed in a carousel on the user terminal 30 together with the message to be notified to the user terminal 30. The carousel display is a display mode in which messages displayed on the screen are replaced by performing a slide operation or the like along a direction perpendicular to the timeline direction. Thereby, by notifying the notification message, it is possible to suppress a phenomenon in which the already notified confirmation message flows in the timeline direction, goes out of the display range, and is no longer visible to the user. In other words, even when a new notification message is sent, the confirmation message can be easily recognized by the user. Furthermore, since the confirmation message is resent at the same time as a new notification message is sent to the user terminal 30, the user is less bothered than when the confirmation message is resent alone. It is possible.

The notification control unit 132 performs notification according to the determination result determined by the determination unit 131. When the determination unit 131 determines that the request message should be retransmitted, the notification control unit 132 causes the request message to be retransmitted to be displayed in a carousel on the user terminal 30 together with the message to be notified to the user terminal 30. The carousel display is a display mode in which messages displayed on the screen are replaced by performing a slide operation or the like along a direction perpendicular to the timeline direction. As a result, it is possible to suppress a phenomenon in which a message that has already been notified flows in the timeline direction, moves out of the display range, and is no longer visible to the user by being notified of the notification message. In other words, even if a new notification message is sent, the billing message can be easily recognized by the user. Furthermore, since the billing message is resent at the same time as a new notification message is sent to the user terminal 30, the user is less bothered than when the billing message is resent alone. It is possible.

The device control unit 133 controls the notification management device 10 in an integrated manner. For example, when the device control unit 133 receives a notification request from the corporate server 20 via the communication unit 11, the device control unit 133 stores the contents as the notification information 120 in the storage unit 12. When the device control unit 133 receives a response to the message from the user terminal 30 via the communication unit 11, the device control unit 133 causes the storage unit 12 to store the contents as response information 121. The device control unit 133 notifies the user terminal 30 of the message created by the message creation unit 130 via the communication unit 11. When the communication unit 11 receives a response to the message from the user terminal 30, the device control unit 133 causes the control unit 13 to store the contents as response information 123.

Here, examples of display modes in which messages are displayed on the user terminal 30 will be explained using FIGS. 6 to 12. 6 to 12 are diagrams showing examples of displays on the user terminal 30 according to the embodiment.

FIG. 6 shows an example in which a confirmation message (numeral 320) is displayed on the display unit 32. In this example, when notifying the bill, a balloon F is displayed that says "Please select a payment date" for confirming the scheduled payment date in advance.

Further, in this example, buttons 321 to 323 used for responses are shown together with the speech bubble F. The button 321 is a button that says "Today (October 17th)", the button 322 is "Tomorrow (October 18th)", and the button 323 is a button that says "During x month". When the user who visually checks the screen of the user terminal 30 selects the button 321, 322, or 323, the notification management device 10 is notified of a response indicating the scheduled payment date according to the selected content. That is, when the user selects the "today" button 321, the user terminal 30 transmits a response to the notification management device 10 indicating that the scheduled payment date is today (October 17th). When the user selects the "by tomorrow" button 322, the user terminal 30 transmits a response to the notification management device 10 indicating that the scheduled payment date is tomorrow (October 18th). When the user selects and operates the button 322 for "0 month x day," a response is sent to the notification management device 10 to the effect that the scheduled payment date is 0 month x day. Note that in addition to the buttons 321 to 323 described above, buttons used for responding may be displayed. For example, if a button labeled "Specify" is displayed and the button is selected and operated, the user specifies any scheduled payment date within the settable range. The user terminal 30 transmits a response specifying the scheduled payment date set by the user's operation to the notification management device 10.

FIG. 7 shows an example in which a balloon F in response to the confirmation message is displayed on the display unit 32. For example, when a response to the confirmation message shown in FIG. 6 is made to specify a scheduled payment date, a response balloon F shown in FIG. 7 is displayed. This example shows a case where the notification management device 10 is notified of a response from the user terminal 30 to the effect that payment will be made today (October 17th).

FIG. 8 shows an example in which a request message (reference numeral 320) is displayed on the display unit 32. For example, after a response specifying the scheduled payment date is made in response to the confirmation message shown in FIG. 6, the notification management device 10 calculates the billed amount when payment is made on the scheduled payment date. Then, the notification management device 10 notifies the user terminal 30 of a balloon F with an explanation of the billed amount as shown in FIG. In this example, the content that explains the billing amount if payment is made today (October 17th) is "If you make payment today (October 17th), the billing amount will be ¥12, 500.'' is shown. Also shown is an example in which a caution regarding the billed amount is written. For example, a warning might include, ``Attention: The original billed amount is ○○○ yen.If you pay by today (October 17th), the billed amount will be ¥12,500.The payment will be delayed. Then, the billed amount will be multiplied by 1.XX% for every XX days.When you press the "Issue QR for payment" button, a QR code will be issued that reflects the billed amount for that day." Ru.

Further, in this example, the billing message (reference numeral 320) includes a speech bubble F with an explanation of the billed amount and a button 321 used for responding to the message. The button 321 is a button labeled "Issue QR for payment". When the user visually confirms the contents of the speech bubble F displayed on the screen of the user terminal 30 and selects the button 321, a request is made to issue a two-dimensional barcode for payment (described as payment QR). The response shown is notified to the notification management device 10. The two-dimensional barcode for payment will be described later. Here, the two-dimensional barcode for payment is an example of a "bill code."

FIG. 9 shows an example in which a notification (reference numeral 320) including a two-dimensional barcode CD for payment is displayed on the display unit 32. For example, when the button 321 is pressed in response to the billing message shown in FIG. 8 and a response is made to issue a payment QR, an external web browser will start up with a link in the app, and the By accessing a predetermined site that handles billing, a two-dimensional barcode CD for payment corresponding to the billed amount on the day the button 321 in FIG. 8 was pressed is issued and notified to the user terminal 30. Alternatively, if the app has a web browser function, you can transition from the company room to the web browser screen within the app, and then use the linked site to make a payment payment via the web browser you transitioned to. A dimensional barcode CD may also be issued. FIG. 9 shows an example of transitioning from a company room to a web browser within an application.

The two-dimensional barcode CD for payment is information according to a protocol exclusively for two-dimensional barcodes, and information regarding payment that is associated with the contents of the bill is embedded therein. Information regarding payment can be referenced by reading the two-dimensional barcode CD with a barcode reader. For example, when making a payment, a person in charge at a convenience store accepting payment, a financial institution, a company server 20, or the like reads a two-dimensional barcode CD using a reader such as a POS cash register, thereby completing a payment procedure. When a payment is made, it is stored in association with the two-dimensional barcode CD, and the notification management device 10 refers to the two-dimensional barcode CD to determine whether or not the payment has been made (that is, in response to the billing message). The presence or absence of a response can be determined.

Here, the two-dimensional barcode CD itself does not contain any information that can be visually read by the user. Therefore, as shown in the example in Figure 9, notes such as "Billed amount: ¥12,500" and "Valid only today (October 17th)" are written along with the two-dimensional barcode CD for payment. You can.

In this manner, in this embodiment, a two-dimensional barcode CD for time-limited payment is issued. The time-limited system here means that a deadline is set for payment using the two-dimensional barcode CD for payment, and the payment is scheduled without being made using the two-dimensional barcode CD for payment. When the date has passed, the two-dimensional barcode CD becomes invalid. Invalidating the two-dimensional barcode CD means changing the two-dimensional barcode CD to a state where the two-dimensional barcode CD and information regarding payment are not associated with each other. For example, if a two-dimensional barcode CD is read on a day different from the scheduled payment date, you will not be able to see the scheduled payment date or payment amount even if you access the URL linked to the two-dimensional barcode CD. , prevent payments from being accepted by the user. This prevents payments from being made on a date different from the scheduled payment date. Therefore, it is possible to prevent payment from being made at the amount before the change even though the payment amount has changed due to late payment charges being incurred due to the scheduled payment date passing. It is possible.

FIG. 10 shows an example in which a normal message is displayed on the display section 32. In this example, a normal message (reference numeral 320) is displayed with a speech bubble F notifying the details of the bill and a response button 321. When the user visually confirms the contents of the speech bubble F displayed on the screen of the user terminal 30 and selects the button 321, the notification management device 10 is notified of this. When the notification management device 10 receives a response requesting notification of specific content from the user terminal 30, it notifies the user terminal 30 of a message indicating the specific content.

Here, if a normal message as shown in FIG. 10 is notified while there is no response to the request message shown in FIG. The message falls outside the display range of the display unit 32. This makes it difficult for the user to recognize the billing message. In this case, even if the user wishes to fulfill the request, that is, pay, the payment will not be made because it will be difficult to find the request message.

As a countermeasure for this, in this embodiment, when a predetermined notification message is sent, the request message for which no response has been received is retransmitted along with the notification message. Further, in this case, the notification message and the request message are displayed in a carousel on the user terminal 30.

11 and 12 show an example in which a normal message and a billing message are displayed in a carousel on the user terminal 30. The normal message in this example is a normal message (reference numeral 320A) indicating the specific content of the request. Further, the billing message in this example is a billing message (reference numeral 320B) for issuing a time-limited billing code, which is given with an explanation of the billing amount according to the scheduled payment date.

In the carousel display, for example, as shown in FIG. 11, all or part of the newly notified regular message (320A) is displayed on the left side of the screen, and all or part of the retransmitted request message (320B) is displayed. section will be displayed on the right side of the screen. On the screen in the display state shown in FIG. 11, by performing a slide operation from left to right along the direction of symbol D (direction perpendicular to the timeline direction), retransmission is performed as shown in FIG. A billing message (reference numeral 320B) is displayed. Furthermore, by performing a slide operation from right to left along the direction of symbol D on the screen in the display state shown in FIG. 12, the normal message (reference symbol 320A) shown in FIG. 11 is displayed. Thereby, even if a new normal message is notified, the billing message can be easily recognized by the user. Furthermore, compared to the case where the billing message is resent alone, it is possible to make the user feel less bothered.

13 and 14 are flowcharts showing the flow of processing performed by the notification management device 10 according to the embodiment. FIG. 13 shows the flow of processing for notifying a request message. FIG. 14 shows the flow of processing for retransmitting a request message.
As shown in FIG. 13, first, the notification management device 10 notifies the user terminal 30 of a confirmation message (step S10). For example, the communication unit 11 notifies the user terminal 30 of the confirmation message created by the message creation unit 130.
Next, the notification management device 10 determines whether a response (response indicating the scheduled payment date) to the confirmation message notified in step S10 has been received (step S11). For example, the device control unit 133 determines, based on the content received via the communication unit 11, whether a response indicating the scheduled payment date has been received from the user terminal 30.
Next, when the notification management device 10 receives a response indicating the scheduled payment date from the user terminal 30, it notifies the user terminal 30 of a billing message showing a timed payment QR according to the scheduled payment date. (Step S12).

As shown in FIG. 14, the notification management device 10 creates a predetermined notification message (step S20). For example, when notifying the user terminal 30 of a new message, the message creation unit 130 refers to the notification information 120 based on instructions from the device control unit 133 and creates a predetermined notification message.
Next, the notification management device 10 determines whether to resend the notified request message (step S21). For example, the determination unit 131 refers to the response information 121 and determines whether there is a request message that has been notified to the user terminal 30, which is the destination of the notification message, but has not received a response. If there is a billing message that has been notified but has not received a response, the determining unit 131 determines that the billing message should be retransmitted.
Next, when the notification management device 10 determines to resend the notified billing message, the notified billing message is displayed in a carousel together with the notification message (step S22). On the other hand, if the notification management device 10 notifies only the notification message and does not resend the notified billing message, it notifies only the notification message to the user terminal 30 (step S23).

In the embodiment described above, the case where the billing message is retransmitted has been described as an example, but the present invention is not limited to this. When notifying a new notification message, the notification management device 10 may resend a confirmation message to which there is no response. The confirmation message to be retransmitted is, for example, a confirmation message as shown in FIG. 6 that confirms the scheduled payment date. Thereby, even if a new notification message is sent, the confirmation message can be easily recognized by the user without causing the user to feel bothered.

Further, in the above-described embodiment, the case where the retransmission conditions in the notification information 120 and the retransmission conditions in the response information 121 are the same has been described as an example, but the present invention is not limited to this. The notification management device 10 may set its own retransmission conditions after considering the notification request received from the corporate server 20. For example, the notification management device 10 may set retransmission conditions according to trends in past responses from user terminals 30 as notification destinations. In this case, the notification management device 10 increases the number of retransmission conditions for users who tend to respond to confirmation messages or request messages (hereinafter referred to as confirmation messages, etc.), for example. Alternatively, the notification management device 10 reduces the number of retransmission conditions for users who tend not to respond to confirmation messages and the like. By setting an appropriate number of retransmissions according to the user's tendency, it is possible to improve the probability that a response to a notified confirmation message or the like will be made.

Further, the notification management device 10 may set retransmission conditions according to the tendency of the company server 20 that is the notification source. For example, when a confirmation or request (hereinafter referred to as confirmation, etc.) is retransmitted from the company server 20, there is a relatively high probability that a response will be made if it is retransmitted up to 5 times, and if it is retransmitted more than 6 times, there is a relatively high probability that a response will be received. If the probability of a response tends to be relatively low, the upper limit of the number of retransmissions is set to five. Furthermore, the notification management device 10 may set retransmission conditions depending on the content of confirmation and the like. For example, an upper limit on the number of retransmissions may be set depending on the scheduled payment date or the billed amount.

Further, after the notification management device 10 receives a response specifying the scheduled payment date in response to the confirmation message shown in FIG. The user terminal 30 may be notified of a message including the above (without going through the web browser). In this case, for example, by reading the two-dimensional barcode CD, a URL etc. linked to the two-dimensional barcode CD is accessed, and a bill is displayed showing the scheduled payment date and the billed amount according to the scheduled payment date. , and that the bill is time-limited. In this case, the two-dimensional barcode CD shown in FIG. 9 is provided with an explanation of the billing amount according to the scheduled payment date and describes a time-limited billing code, and is an example of a "billing message."

In addition to the request message shown in FIG. 8, the retransmitted request message may be a message including the two-dimensional barcode for payment shown in FIG. 9 that does not go through the above-mentioned Web browser. In the case of a notification including a two-dimensional barcode for payment, a caution such as "Please use either the payment QR that has already been notified or the payment QR that has been resent this time" may be written. Thereby, the user can recognize that it is sufficient to make a payment using either the already notified two-dimensional barcode or the retransmitted two-dimensional barcode. Therefore, even if a plurality of two-dimensional barcodes for payment are notified, it is possible to make the payment without confusing the user.

As described above, the notification management device 10 of the embodiment includes the message creation section 130 and the communication section 11. The message creation unit 130 generates a time-limited invoice code, which is attached with an explanation of the billed amount corresponding to the scheduled payment date, based on the response status in the confirmation message for confirming the scheduled payment date, which is notified to the user terminal 30. Create a request message to describe or issue. The communication unit 11 notifies the user terminal 30 of the request message created by the message creation unit 130. As a result, the notification management device 10 of the embodiment can notify a bill requesting the payment amount on the scheduled payment date specified by the user, so even if the bill amount changes depending on the payment date, the It is possible to claim a reasonable amount. In addition, since time-limited invoices are notified, payments made using the invoice can be invalidated on a day different from the scheduled payment date, and if the billed amount changes after the scheduled payment date has passed. Even if the amount is changed, the amount before the change will not be erroneously collected. That is, even if the billing amount changes depending on the day of payment, it is possible to bill the appropriate billing amount.

Further, the notification management device 10 of the embodiment further includes a determination unit 131 and a notification control unit 132. When notifying the user terminal 30 of a predetermined notification message, the determining unit 131 determines whether to resend the request message together with the notification message based on the response status of the request message that has already been notified to the user terminal 30. Determine. When the notification control unit 132 resends the request message together with the notification message according to the determination result determined by the determination unit 131, the notification control unit 132 displays the notification message and the request message in a carousel on the user terminal 30. do. Thereby, the notification management device 10 of the embodiment can resend the request message at the timing of notifying the user terminal 30 of a new notification message. Therefore, compared to the case where only the request message is retransmitted unilaterally, the user does not feel troubled. Furthermore, by displaying the notification message and the billing message in a carousel on the user terminal 30, the billing message can be more easily recognized by the user compared to a case where the carousel is not displayed.

Furthermore, in the notification management device 10 of the embodiment, when notifying the user terminal 30 of a predetermined notification message, the determination unit 131 determines whether the notification message is correct based on the response status of the confirmation message that has already been notified to the user terminal 30. It is determined whether or not to resend the confirmation message along with the notification. The notification control unit 132 causes the notification message and the confirmation message to be displayed in a carousel on the user terminal 30 when resending the confirmation message together with the notification message according to the determination result determined by the determination unit 131. . Thereby, the notification management device 10 of the embodiment can resend the confirmation message at the timing of notifying the user terminal 30 of a new notification message. Therefore, compared to the case where only the confirmation message is retransmitted unilaterally, the user does not feel bothered. Furthermore, by displaying the notification message and the confirmation message in a carousel on the user terminal 30, the confirmation message can be more easily recognized by the user than in the case where the carousel is not displayed.

All or part of the notification management device 10 in the embodiment described above may be realized by a computer. In that case, a program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed. Note that the "computer system" herein includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into computer systems. Furthermore, a "computer-readable recording medium" refers to a storage medium that dynamically stores 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. It may also include a device that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in that case. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. It may also be realized using a programmable logic device such as an FPGA.

Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and includes designs within the scope of the gist of the present invention.

1...Notification system 10...Notification management device 11...Communication unit 12...Storage unit 120...Notification information 121...Response information 13...Control unit 130...Message creation unit 131...Determination unit 132...Notification control unit 133...Device control unit 20... Corporate server 30...User terminal

Claims (5)

Based on the status of the response to the confirmation message confirming the scheduled payment date notified to the user terminal, to write or issue a time-limited invoice code with an explanation of the billed amount corresponding to the scheduled payment date. a message creation unit that creates a billing message;
a communication unit that notifies the user terminal of the request message created by the message creation unit;
When notifying the user terminal of a predetermined notification message, it is determined whether or not to resend the request message together with notification of the notification message based on the status of the response to the request message that has already been notified to the user terminal. a determination unit that determines;
When the request message is retransmitted together with the notification message according to the determination result determined by the determination unit, the notification message and the request message are displayed in a carousel on the user terminal. a control unit;
A notification management device comprising: Based on the status of the response to the confirmation message confirming the scheduled payment date notified to the user terminal, to write or issue a time-limited invoice code with an explanation of the billed amount corresponding to the scheduled payment date. a message creation unit that creates a billing message;
a communication unit that notifies the user terminal of the request message created by the message creation unit;
When notifying the user terminal of a predetermined notification message, it is determined whether or not to resend the confirmation message together with notification of the notification message, based on the status of the response to the confirmation message that has already been notified to the user terminal. a determination unit that determines;
When retransmitting the confirmation message together with notification of the notification message according to the determination result determined by the determination unit, notification control causes the notification message and the confirmation message to be displayed in a carousel on the user terminal. Department and
A notification management device. The message creation unit generates a time-limited invoice code with an explanation of the billed amount corresponding to the scheduled payment date, based on the status of the response to the confirmation message that confirms the scheduled payment date, which is notified to the user terminal. Create a request message to write or issue,
a communication unit notifies the user terminal of the request message created by the message creation unit ,
When the determination unit notifies the user terminal of a predetermined notification message, the determining unit resends the request message together with the notification of the notification message based on the status of the response to the request message that has already been notified to the user terminal. Determine whether or not
When the notification control unit resends the request message together with the notification message according to the determination result determined by the determination unit, the notification message and the request message are displayed in a carousel on the user terminal. so that
How to manage notifications. The message creation unit generates a time-limited invoice code with an explanation of the billed amount corresponding to the scheduled payment date, based on the status of the response to the confirmation message that confirms the scheduled payment date, which is notified to the user terminal. Create a request message to write or issue,
a communication unit notifies the user terminal of the request message created by the message creation unit ,
When the determination unit notifies the user terminal of a predetermined notification message, the determination unit resends the confirmation message together with notification of the notification message based on the status of the response to the confirmation message that has already been notified to the user terminal. Determine whether or not
When the notification control unit resends the confirmation message together with the notification message according to the determination result determined by the determination unit, the notification message and the confirmation message are displayed in a carousel on the user terminal. to do so,
How to manage notifications. A program for causing a computer to operate as the notification management device according to claim 1 or 2 , the program for causing the computer to function as each section included in the notification management device.

Images