JP5736599B2 - Push notification management device, push notification management method, and push notification management program - Google Patents

Description

  The present invention relates to a technique for managing push notifications.

  Push notification actively notifies a user terminal of a message from the system side, and the user can acquire information in real time without performing any operation (for example, see Patent Document 1). reference.).

  Many smartphone OSs (Operating System) have built-in push notification functions, and push notifications are linked with cloud services (APNs: Apple Push Notification Service, GCM: Google Cloud Messaging for Android, etc.) It can be done. If the user has permitted to receive push notifications for a given app, the server pushes the user's terminal by requesting a push notification from a cloud service such as APNs by specifying a device token that identifies the user's terminal Notification is made.

JP 2013-11951 A

  As described above, the push notification is a very convenient function. However, when the push notification is frequently performed for a large number of users, it is necessary to increase the equipment on the server side, and an increase in cost is inevitable. Since not all users want push notifications, there is a need to optimize the facilities by narrowing down push notifications to effective users who can see them.

  Also, from the user's standpoint, frequent push notifications are annoying, and there is an adverse effect of overlooking important notifications.

  The present invention has been proposed in view of the above-described conventional problems, and an object of the present invention is to provide a mechanism that can be narrowed down to push notifications that the user is likely to see.

In order to solve the above-described problem, in the present invention, for a predetermined message, transmission request means for requesting the cloud service to transmit a push notification based on a user list, and a user responding to the push notification Response information registration means for receiving and registering response information including identification information of the user and message identification information of the message related to the push notification from the terminal, and a new message related to the message related to the push notification, And a related transmission request unit that requests the cloud service to transmit a new push notification to the user terminal from which the response information is obtained, and the related transmission request unit includes the response information at the start of processing. Requesting transmission of the new push notification for the terminal of the user who has obtained Register the message according to the PUSH notification, upon receiving the response information from the user's terminal to the processing after the start time for the terminal of the user, so as to request transmission of push notification message the registration ing.

  In the present invention, it is possible to narrow down to push notifications that are highly likely to be viewed by the user, and it is possible to optimize server facilities and improve user convenience.

It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the structural example of the information used for a process. It is a figure which shows the hardware structural example of a terminal device. It is a figure which shows the hardware structural examples, such as a game server. It is a sequence diagram (the 1) which shows the process example of embodiment. It is a sequence diagram (the 2) which shows the process example of embodiment. It is a sequence diagram (the 3) which shows the process example of embodiment. It is a figure which shows the example of a screen display of a push notification. It is a figure which shows the structural example of message relevant information. It is a sequence diagram (the 4) which shows the process example of embodiment. It is a sequence diagram (the 5) which shows the process example of embodiment.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 1, the system includes a terminal device 1 (1A, 1B,...) Such as a smartphone or a mobile phone operated by a user (player), a game server 3 that manages a game, and an operator of the game server 3. Mediates the request for push notification to the push notification execution server 5 and the push notification execution server 5 that performs the push notification provided as a cloud service, the management terminal device 4 that is instructed to transmit the push notification, etc. The push notification management server 6 is configured to be connected via a network 2 such as the Internet.

  An application (application program) X is installed in the terminal device 1, and by executing the application, a user registration request unit 11, a device token acquisition request unit 12, a device token registration request unit 13, a push notification request unit 14, response information The transmission unit 15 is realized.

  The user registration request unit 11 has a function of performing user registration with the game server 3 when the application X is activated for the first time.

  The device token acquisition request unit 12 has a function of making a device token acquisition request to the push notification execution server 5 every time the application X is activated. The device token is information for identifying the terminal device 1 that is a destination when a push notification transmission request is made to the push notification execution server 5. Since the device token is updated at a predetermined frequency, it is necessary to obtain the device token every time the application X is activated.

  The device token registration request unit 13 has a function of requesting registration of the device token acquired from the push notification execution server 5 to the push notification management server 6.

  The push notification request unit 14 has a function of making a push notification transmission request to the push notification management server 6.

  After receiving the push notification, the response information transmitting unit 15 starts a predetermined operation in response to the push notification (a predetermined screen of the app X in response to the push notification, a battle, a quest, a combination (a plurality of game items A function of transmitting response information to the push notification management server 6 when a predetermined action such as billing or the like is performed). .

  The game server 3 is provided with a user management database 31, a user registration unit 32, an information management unit 33, and a push notification request unit 34.

  As shown in FIG. 2, the user management database 31 has items (fields) such as “user ID”, “password”, “user attribute”, “language used”, “OS version”, “last activation date”, and “game history”. ing. “User ID” is information for identifying a user. “Password” is secret information used for authentication. “User attribute” is information such as the gender, age group, and residential area of the user. “Use language” is information for identifying the use language on the application X of the user. “OS version” is information indicating the version number of the OS executing the application X of the user. “Last activation date” is information on the date and time when the user last activated the application X. “Game history” is information on the history of the game by the application X by the user.

  Returning to FIG. 1, the user registration unit 32 of the game server 3 has a function of accepting a user registration request from the terminal device 1 and performing a user registration process.

  The information management unit 33 has a function of providing information managed in the game server 3 in response to a request from the management terminal device 4 or the like.

  The push notification request unit 34 has a function of making a push notification transmission request to the push notification management server 6.

  The management terminal device 4 is provided with a user list generation unit 41 and a push notification request unit 42.

  The user list generation unit 41 has a function of acquiring information from the game server 3 as necessary, and generating a list of user IDs that are transmission destinations of push notifications.

  The push notification request unit 42 has a function of making a push notification transmission request to the push notification management server 6. The push notification from the management terminal device 4 is a request for batch transmission based on the user list. This request includes a case where transmission is performed immediately and a case where reservation is made by specifying a transmission date and time (distribution date and time).

  The push notification management server 6 includes a device token management database 61, a message reservation management information 62, a message management database 63, a device token registration unit 64, a message management unit 65, a push notification request unit 66, and a response information reception unit 67. ing.

  As shown in FIG. 2, the device token management database 61 includes items such as “application ID”, “user ID”, and “device token”. “App ID” is information for identifying an application. “User ID” is information for identifying a user. The “device token” is a device token issued from the push notification execution server 5 to the user.

  As shown in FIG. 2, the message reservation management information 62 has items such as “message ID”, “message content”, “delivery reservation date / time”, and “not yet delivered”. “Message ID” is information for identifying a message to be notified of push. “Message content” is information on the content of the message. “Delivery reservation date” is information on the date and time when the push notification is performed. “Undelivered” is information indicating whether or not a push notification has already been performed.

  As shown in FIG. 2, the message management database 63 includes items such as “message ID”, “application ID”, “destination device token”, and “response status”. “Message ID” is information for identifying a message. “App ID” is information for identifying an application. The “destination device token” is a device token that is the destination of the push notification. A user ID may be held instead of the device token.

  “Response status” is information indicating whether or not there is a response to the push notification, the date and time of the response, the operation that caused the response, and the like. The response status is based on response information transmitted from the terminal device 1. In this embodiment, since the response status of the push notification requested and transmitted from the terminal device 1 or the game server 3 is not used, it is determined whether the push notification is requested and transmitted from the management terminal device 4. The message management database 63 is excluded from the management target.

  Returning to FIG. 1, the device token registration unit 64 of the push notification management server 6 has a function of registering in the device token management database 61 in response to a device token registration request from the terminal device 1.

  The message management unit 65 accepts a push notification request from the terminal device 1, the game server 3, and the management terminal device 4. The reservation from the management terminal device 4 is registered in the message reservation management information 62 and the push notification is received. It has a function of registering the situation in the message management database 63.

  The push notification request unit 66 has a function of requesting the push notification execution server 5 for a push notification requested from the terminal device 1, the game server 3, and the management terminal device 4.

  The response information receiving unit 67 has a function of receiving response information indicating that a predetermined operation has been performed on the push notification in the terminal device 1.

  FIG. 3 is a diagram illustrating a hardware configuration example of the terminal device 1.

  In FIG. 3, the terminal device 1 includes a power supply system 101, a main system 102 including a processor 103, a memory controller 104, and a peripheral interface 105, and a storage unit 106. The terminal device 1 includes an external port 107, a high frequency circuit 108, an antenna 109, an audio circuit 110, a speaker 111, a microphone 112, a proximity sensor 113, and a GPS (Global Positioning System) circuit 114. ing. The terminal device 1 also includes an input / output (I / O) subsystem 115 including a display controller 116, an optical sensor controller 117, and an input controller 118, a touch-responsive display system 119, an optical sensor 120, and an input unit 121. And.

  FIG. 4 is a diagram illustrating a hardware configuration example of the game server 3 and the like.

  In FIG. 4, the game server 3, the management terminal device 4, the push notification execution server 5, and the push notification management server 6 include a CPU (Central Processing Unit) 302, a ROM (Read Only Memory) 303 connected to the system bus 301, A RAM (Random Access Memory) 304 and an NVRAM (Non-Volatile Random Access Memory) 305 are provided. In addition, the game server 3 and the like include an I / F (Interface) 306, an I / O (Input / Output Device) 307, an HDD (Hard Disk Drive) 308, and a NIC (Network Interface Card) connected to the I / F 306. 309, a monitor 310 connected to the I / O 307, a keyboard 311, a mouse 312 and the like. A CD / DVD (Compact Disk / Digital Versatile Disk) drive or the like can be connected to the I / O 307.

<Operation>
FIG. 5 is a sequence diagram illustrating a processing example of the above-described embodiment, and illustrates a processing example of user registration and device token acquisition / registration by the application X of the terminal device 1 performed prior to push notification. .

  In FIG. 5, it is assumed that the application X is activated on the terminal device 1A (step S101), and then the user registration request unit 11 of the application X makes a user registration request to the game server 3 (step S102). Note that user registration can be performed only once for the application X in principle.

  Upon receiving the user registration request, the user registration unit 32 of the game server 3 issues a user ID, a password, and the like and registers them in the user management database 31 according to a predetermined procedure (step S103), and registers them in the application X of the terminal device 1A. Notification is made (step S104).

  The user registration process is similarly performed from the application X of the terminal device 1B.

  Next, when the application X of the terminal device 1 is activated (step S111), a device token acquisition request is sent from the device token acquisition request unit 12 of the application X to the push notification execution server 5 (step S112).

  Upon receiving the device token acquisition request, the push notification execution server 5 issues a device token and registers it internally (step S113), and notifies the application X of the terminal device 1A (step S114).

  Next, the device token registration request unit 13 of the application X of the terminal device 1A makes a device token registration request to the push notification management server 6 (step S115). This device token registration request is accompanied by an application ID and a user ID.

  When the device token registration unit 64 of the push notification management server 6 accepts the device token registration request, the device token registration unit 64 performs registration in the device token management database 61 (step S116). The application X is notified (step S117).

  A device token registration process is similarly performed from the application X of the terminal device 1B.

  Next, FIG. 6 shows a processing example regarding a push notification request from the terminal device 1 and a push notification request from the game server 3.

  Here, it is assumed that the user of the terminal device 1A sends a push notification from the app X to the user of the terminal device 1B that uses the same app X.

  The push notification request unit 14 of the application X of the terminal device 1A makes a push notification request to the push notification management server 6 (step S201). This push notification request is accompanied by the user ID of the transmission destination and the message content.

  When receiving the push notification request, the message management unit 65 of the push notification management server 6 acquires a corresponding destination device token from the device token management database 61 using the destination user ID as a key (step S202).

  Next, the push notification request unit 66 of the push notification management server 6 makes a push notification request to the push notification execution server 5 (step S203). This push notification request is accompanied by a destination device token and message contents.

  Upon receiving the push notification request, the push notification execution server 5 sends a push notification to the application X of the terminal device 1B indicated by the destination device token (step S204), and the terminal device 1B displays the incoming push notification. (Step S205).

  Next, it is assumed that a push notification is sent from the game server 3 to the user of the terminal device 1A using the application X as the game progresses.

  The push notification request unit 34 of the game server 3 makes a push notification request to the push notification management server 6 (step S211). This push notification request is accompanied by the user ID of the transmission destination and the message content.

  When receiving the push notification request, the message management unit 65 of the push notification management server 6 acquires a corresponding destination device token from the device token management database 61 using the destination user ID as a key (step S212).

  Next, the push notification request unit 66 of the push notification management server 6 makes a push notification request to the push notification execution server 5 (step S213). This push notification request is accompanied by a destination device token and message contents.

  Upon receiving the push notification request, the push notification execution server 5 sends a push notification to the application X of the terminal device 1A indicated by the destination device token (step S214), and the terminal device 1A displays an incoming push notification. (Step S215).

  Next, FIG. 7 shows a processing example for a push notification request from the management terminal device 4.

  The user list generation unit 41 of the management terminal device 4 requests user information satisfying a predetermined condition from the game server 3 (step S221), and the information management unit 33 of the game server 3 searches the user management database 31. Then, the user information of the search result is returned to the management terminal device 4 (step S222). For example, a user ID whose language is “Japanese” and whose last activation date is “5 days or more ago” is acquired.

  The user list generation unit 41 of the management terminal device 4 generates a user list listing the user IDs that are subject to push notification based on the acquired user information (step S223).

  Next, the push notification request unit 42 of the management terminal device 4 makes a push notification request to the push notification management server 6 (step S224). This push notification request is accompanied by a destination user list and message contents (the same contents for all users in the user list). In addition, this push notification request can be accompanied by a reservation of the delivery date and time if it is not immediate transmission.

  When receiving the push notification request, the message management unit 65 of the push notification management server 6 registers the reservation content in the message reservation management information 62 when the delivery date / time is reserved (step S225).

  Thereafter, when the message reservation management information 62 includes reservation information, the message management unit 65 of the push notification management server 6 determines the timing of whether or not the reserved delivery date has been reached (step S226).

  The message management unit 65 of the push notification management server 6 immediately starts the push notification request without a reservation, and if the push notification request with a reservation has reached the delivery date and time, the message management unit 65 from the device token management database 61 A corresponding destination device token is acquired using the destination user ID as a key (step S227).

  Next, the push notification request unit 66 of the push notification management server 6 makes a push notification request to the push notification execution server 5 (step S228). This push notification request is accompanied by a list of destination device tokens and message contents.

  When the push notification execution server 5 accepts the push notification request, the push notification execution server 5 sends a push notification to the application X such as the terminal device 1A, 1B,. ,..., Etc., push notifications are displayed (steps S231 and S232).

  FIG. 8 is a diagram showing a screen display example of a push notification. In this example, another application such as “XXXXX” (game title name) is installed in the center of the screen and the recovery drug GET! We are informing you that you will get benefits by installing. In addition, an event start notification such as “XXXXX (game title) New event start!” Can be performed.

  Returning to FIG. 7, when the user of the terminal device 1A performs a predetermined operation on the displayed push notification (step S233), the application X of the terminal device 1A performs a predetermined process (step S234). . For example, in the case of the push notification “recovered drug GET! By application installation name” shown in FIG. 8, slide the button at the bottom of the screen to the right to “display” When an operation is performed, the screen changes to a screen for installing another application. Further, in the case of a push notification “XXXXX (Game Title Name) New Event Start!”, The same operation is performed to shift to a screen for introducing a new event. It is also possible to start an application that has not been started by a predetermined operation for the push notification. These can be realized by a scheme such as a URL scheme.

  Returning to FIG. 7, the response information transmission unit 15 of the application X of the terminal device 1 </ b> A transmits the response information to the push notification management server 6 according to the operation performed by the user for the push notification (step S <b> 235). This response information includes an application ID, a user ID (or device token), and a message ID.

  The response information receiving unit 67 of the push notification management server 6 receives the response information from the terminal device 1A, and the message management unit 65 registers the response status in the message management database 63 (step S236).

  Thereafter, it is assumed that the management terminal device 4 performs a push notification request (step S224) first and performs a push notification for another new message related to a message for which a push notification has already been performed. Here, the other related new message is a message positioned as a sequel to the previous message.

  In this embodiment, as for other related messages, only the user who has received the response information indicating that a predetermined operation has been performed within the range of the user who has pushed the previous message. , Push notifications of other messages. A user who performs a predetermined operation for push notification is likely to want the push notification, and pushes other messages related only to such a user, leading to enlargement of facilities. And effective push notification can be performed.

  In FIG. 7, the push notification request unit 42 of the management terminal device 4 makes a new push notification request to the push notification management server 6 (step S241). This push notification request is accompanied by a destination user list and message contents (the same contents for all users in the user list) and associated destination message IDs. In addition, this push notification request can be accompanied by a reservation of the delivery date and time if it is not immediate transmission.

  When receiving the push notification request, the message management unit 65 of the push notification management server 6 registers the reservation content in the message reservation management information 62 when the delivery date / time is reserved (step S242).

  After that, when there is reservation information in the message reservation management information 62, the message management unit 65 of the push notification management server 6 determines the timing of whether or not the reserved delivery date / time has been reached (step S243).

  The message management unit 65 of the push notification management server 6 immediately updates the message when the push notification request is not accompanied by a reservation, and when the delivery date / time is reached when the push notification request is accompanied by a reservation, The device token of the transmission destination whose response status is a predetermined operation is selected as a target user using the message ID of the message to be transmitted as a key (step S244).

  Next, the push notification request unit 66 of the push notification management server 6 makes a push notification request to the push notification execution server 5 (step S245). This push notification request is accompanied by a list of destination device tokens and message contents.

  When the push notification execution server 5 accepts the push notification request, the push notification execution server 5 sends a push notification to the application X such as the terminal device 1A (excluded because the terminal device 1B did not perform a response operation) indicated by the destination device token (step S246). In the terminal device 1A or the like, an incoming push notification is displayed (step S247).

  Thereafter, when performing push notification of other related new messages, the same processing is repeated.

  Next, a modified example of the process described in FIG. 7 will be described. That is, in the process described in FIG. 7, when performing push notification for other related messages, push notification is performed in a batch process, and push notification is performed only to users who have obtained predetermined response information at that time. ing. However, if you do not immediately notice the push notification and respond to the push notification of the previous message after other related messages have already been pushed (not sent to users who do not notice the previous push notification) Is also possible.

  Therefore, in this modification, the push notification is performed for other messages that have already started the push notification after the predetermined response information is obtained from the user regarding the previous message. This is effective when the push notification message has an order or story and should be read continuously.

  FIG. 9 is a diagram showing an example of the structure of message-related information 68 newly added to the push notification management server 6, and has items such as “parent message ID”, “child message ID”, and “child message content”. . “Parent message ID” is the message ID of the previous message in the two related messages. The “child message ID” is a message ID of a later message in the two related messages. The “child message content” is information indicating the content of the child message. If the message content is held elsewhere, the “child message content” can be omitted.

  10 and 11 are sequence diagrams showing an example of processing in this case. 10, steps S301 to S316 are the same as steps S221 to S236 in FIG. 10 differs from steps S241 to S247 in FIG. 7 in that message-related information registration (step S323) is added immediately after reservation registration (step S222). That is, the message management unit 65 of the push notification management server 6 registers the relevance and the like of the other message with the previous message in the message related information 68 (step S323).

  Next, in FIG. 11, when the user of the terminal device 1B performs a predetermined operation on the already received push notification (step S331), the application X of the terminal device 1B performs predetermined processing such as screen transition. This is performed (step S332).

  Next, the response information transmission unit 15 of the application X of the terminal device 1B transmits the response information to the push notification management server 6 according to the operation performed on the push notification by the user (step S333). This response information includes an application ID, a user ID (or device token), and a message ID.

  The response information reception unit 67 of the push notification management server 6 receives the response information from the terminal device 1B, and the message management unit 65 registers the response status in the message management database 63 (step S334).

  Next, when the message ID of the received response information matches the parent message ID of the message related information 68, the message management unit 65 of the push notification management server 6 acquires the child message ID and the message content (step S335). ). The device token of the transmission destination can be acquired directly or indirectly from the response information.

  Then, the push notification request unit 66 of the push notification management server 6 makes a push notification request to the push notification execution server 5 (step S336). This push notification request is accompanied by a destination device token and message contents.

  Upon receiving the push notification request, the push notification execution server 5 sends a push notification to the application X of the terminal device 1B indicated by the destination device token (step S337), and the terminal device 1B displays the incoming push notification. (Step S338).

<Summary>
As described above, according to the present embodiment, it is possible to narrow down to push notifications that are highly likely to be viewed by the user, and it is possible to optimize server facilities and improve user convenience.

  In addition, although push notification was demonstrated, it is applicable similarly to an email, SMS (Short Message Service), etc.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

1, 1A, 1B terminal device X application 11 user registration request unit 12 device token acquisition request unit 13 device token registration request unit 14 push notification request unit 15 response information transmission unit 2 network 3 game server 31 user management database 32 user registration unit 33 Information management unit 34 Push notification request unit 4 Management terminal device 41 User list generation unit 42 Push notification request unit 5 Push notification execution server 6 Push notification management server 61 Device token management database 62 Message reservation management information 63 Message management database 64 Device token Registration unit 65 Message management unit 66 Push notification request unit 67 Response information reception unit 68 Message related information

Claims (4)

For a predetermined message, transmission request means for requesting the cloud service to transmit a push notification based on a user list;
Response information registration means for receiving and registering response information including identification information of the user and message identification information of the message related to the push notification from the terminal of the user who responded to the push notification;
About a new message related to the message related to the push notification, it is limited to the user terminal from which the response information is obtained, and includes related transmission requesting means for requesting the cloud service to transmit a new push notification. ,
The related transmission request means includes
Requesting the transmission of the new push notification for the terminal of the user whose response information has been obtained at the start of processing, and registering a message related to the push notification,
When the response information is received from the user's terminal after the processing start time point , the push notification management characterized in that the user's terminal is requested to transmit a push notification of the registered message. apparatus. In the push notification management device according to claim 1,
The related transmission request unit requests transmission of the new push notification for a user terminal for which the response information is obtained at the start of processing. A method executed by a push notification management device, comprising:
For a predetermined message, a transmission request step for requesting transmission of a push notification to the cloud service based on a user list;
A response information registration step of receiving and registering response information including the identification information of the user and the message identification information of the message related to the push notification from the terminal of the user who responded to the push notification;
A new message related to the message related to the push notification, the related transmission requesting step for limiting the transmission of the new push notification to the cloud service, limited to the user terminal from which the response information is obtained. ,
The related transmission request step includes:
Requesting the transmission of the new push notification for the terminal of the user whose response information has been obtained at the start of processing, and registering a message related to the push notification,
When the response information is received from the user's terminal after the processing start time point , the push notification management characterized in that the user's terminal is requested to transmit a push notification of the registered message. Method. The computers that make up the push notification management device
A transmission request means for requesting the cloud service to transmit a push notification based on a user list for a predetermined message;
Response information registration means for receiving and registering response information including identification information of the user and message identification information of the message related to the push notification from the terminal of the user who responded to the push notification,
The new message related to the message related to the push notification is limited to the terminal of the user from which the response information is obtained, and functions as a related transmission request means for requesting the cloud service to transmit a new push notification. ,
The related transmission request means includes
Requesting the transmission of the new push notification for the terminal of the user whose response information has been obtained at the start of processing, and registering a message related to the push notification,
A push notification management program that, when receiving the response information from a user's terminal after the processing start time, requests the user's terminal to transmit a push notification of the registered message .

Images