JP2017220720A - Communication monitoring device and communication monitoring method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve appeal of push notification used in mobile terminal.SOLUTION: A communication monitoring device 1 for monitoring communication of a user terminal receiving push notification from a distribution server includes a timing determination/sharing unit 13 for determining whether or not the user terminal is in use from the communication state of the user terminal, and when a determination is made that it is in use, notifying an instruction server for instructing push notification to the distribution server of the execution timing of push notification. In particular, the timing determination/sharing unit 13 can check communication including communication other than that using an application provided by a service provider possessing the instruction server, and when a determination is made that the user terminal is in use, notifies the instruction server of the execution timing of push notification.SELECTED DRAWING: Figure 2

Description

  The present invention relates to information distribution technology for mobile terminals such as smartphones (hereinafter sometimes referred to as “terminals” or “user terminals”).

  With the spread of mobile terminals such as smartphones, PUSH notification (push notification) using a smartphone application is used as an effective approach means to mass users.

  Non-patent document 1 is an example of a document disclosing a technology related to push notification.

“O2O technology summary commentary that can be used with Android (1): Basic knowledge of“ O2O ”(5/5) that is lost even if a smartphone engineer does not know” [online], [Search June 2, 2016], Internet <URL : http://www.atmarkit.co.jp/ait/articles/1209/07/news127_5.html>

  However, in the current situation where push notifications are used in many applications, it is very complicated for a user who has installed many applications on the terminal to check incoming information every time there is a push notification. As a result, the appeal of push notifications has declined at present, and push notifications received when the device is not in use (when not viewing the terminal screen: sleep state) can be overlooked (similar to emails) Is expensive.

  In view of such circumstances, an object of the present invention is to improve the appeal of push notifications used in user terminals.

  In order to solve the above-described problem, the invention according to claim 1 is a communication monitoring apparatus that monitors communication of a user terminal that receives a push notification from a distribution server, and the user terminal is configured based on a communication status of the user terminal. It is determined whether or not it is in use, and when it is determined that it is in use, the instruction server that instructs the push notification to the distribution server includes a determination unit that notifies the execution timing of the push notification. And

  The invention according to claim 3 is a communication monitoring method in a communication monitoring device that monitors communication of a user terminal that receives a push notification from a distribution server, wherein the communication monitoring device is based on a communication status of the user terminal. Determining whether or not the user terminal is in use; and when determining that the user terminal is in use, notifying an instruction server that instructs the push notification to the distribution server of the push notification; It is characterized by performing.

According to the first and third aspects of the present invention, the service provider can implement the push notification optimally by constructing a system in which the service provider can collaborate with the line operator having the communication monitoring device. It is possible to have the communication monitoring device notify the timing that the user terminal is in use.
Therefore, it is possible to improve the appeal power of the push notification used in the user terminal.

  The invention according to claim 2 is the communication monitoring apparatus according to claim 1, wherein the determination unit includes communication other than communication using an application provided by a service provider having the instruction server. When it is determined that the user terminal is in use by confirming communication, the instruction server is notified of the execution timing of the push notification.

According to the invention described in claim 2, the service monitoring device alone cannot directly grasp communication other than communication using the application provided by the service provider. Communication can be grasped indirectly. As a result, the service provider can more frequently notify the communication monitoring device of the timing when the user terminal is being used, which is the optimal timing for performing the push notification.
Therefore, it is possible to further improve the appealing power of push notifications used in the user terminal.

  ADVANTAGE OF THE INVENTION According to this invention, the appeal power of the push notification currently used with the user terminal can be improved.

It is a whole block diagram of the system which implement | achieves the push notification of this embodiment. It is a functional block diagram of the communication monitoring apparatus of this embodiment. It is a flowchart which shows the whole process performed with the communication monitoring apparatus of this embodiment. It is a flowchart which shows the operation example of a R_ID-ID_A tied part. It is a flowchart which shows the operation example of a cooperation target R_ID management part. It is a flowchart which shows the operation example of a timing judgment / sharing part.

  Embodiments of the present invention will be described in detail with reference to the drawings.

≪Configuration≫
As shown in FIG. 1, the system that realizes push notification according to the present embodiment includes a communication monitoring device 1, a user terminal 2, an instruction server 3, a company service server 3 </ b> A, and a distribution server 4. Further, the other server 5 in FIG. 1 is communicably connected to the system of the present embodiment.

The communication monitoring device 1 is a device that monitors communication performed at the user terminal 2. The communication monitoring device 1 is, for example, a packet counter or a DPI (Deep Packet Inspection) device. The communication monitoring device 1 is used by, for example, a line provider or ISP (Internet Service Provider) provider (hereinafter sometimes referred to as “line provider etc.”).
The communication monitoring apparatus 1 includes hardware such as a control unit, a storage unit, an input unit, and an output unit, and the control unit develops and executes a program stored in the storage unit in a storage area of the storage unit. Thus, the above-described functional unit can be realized and various processes can be executed. The communication monitoring apparatus 1 according to the present embodiment can realize such cooperation between software and hardware.

  The user terminal 2 is, for example, a smartphone or a tablet terminal. The user terminal 2 is a device used by a user who uses a predetermined service. The user terminal 2 has a web browser and a plurality of types of applications installed therein, and has a function of using push notification.

  The instruction server 3 is a server that instructs the distribution server 4 to perform push notification. The instruction server 3 is a device used by a service provider that provides a predetermined service to a user (sometimes referred to as “in-house service provider” for convenience of explanation).

  The in-house service server 3A is a server in which an in-house service provider provides an in-house service to users. It is assumed that an application developed by its own service provider is installed in the user terminal 2. This application has a function of using push notification.

  The distribution server 4 is a server that performs push notification to the user terminal 2 in accordance with an instruction from the instruction server 3. The distribution server 4 is a server used by an OS (Operating System) provider of the user terminal 2. The distribution server 4 publishes an API (Application Programming Interface) for push notification.

The other server 5 is, for example, a Web server or another company service server. The Web server can publish a Web page by Web browsing of the user terminal 2. The other company's service server is a service server other than its own service server 3A, and is used by another company's service provider other than its own service provider. Assume that an application developed by a service provider of another company is installed in the user terminal 2. This application may or may not have a function of using push notification.
The service provider of another company has an instruction server (not shown) having a function equivalent to that of the instruction server 3, and can instruct the push notification to the distribution server 4.

  As a pre-operation before the push notification, the processing of step a1 to step a3 in FIG. 1 is executed. That is, in step a1, the company application of the user terminal 2 (hereinafter simply referred to as “app”) registers the application of the user terminal 2 itself with the distribution server 4 and requests the distribution server 4 to issue an R_ID for push notification (R_ID Withdrawal request). R_ID is an identifier managed by the distribution server 4 or the instruction server 3 in order for the instruction server 3 to identify the application of the user terminal 2 regarding the implementation of the push notification.

  Next, the distribution server 4 gives R_ID to the application of the user terminal 2 in step a2. Next, in step a3, the application of the user terminal 2 transmits the R_ID of the application of the user terminal 2 itself to the instruction server 3 (via the communication monitoring device 1). At this time, as an application example of the service provider, the application of the user terminal 2 can transmit user attribute information such as the user's age and sex together with the R_ID to the instruction server 3.

  Moreover, the process of step b1-step b4 in FIG. 1 is performed as operation | movement at the time of push notification. That is, when information and timing suitable for the user are generated on the service provider side (in-house) in step b1, the instruction server 3 instructs the distribution server 4 to perform push notification in step b2, Request information distribution to the R_ID of the user. At this time, as an application example of the service provider, the application of the user terminal 2 transmits position information by GPS (Global Positioning System) or the like to the instruction server 3 in order to know the timing of performing the push notification. Can do.

  Next, in step b3, the distribution server 4 sends a push notification to the user terminal 2 and distributes the requested information. Next, in step b4, the user terminal 2 processes the distributed information.

  Line operators and the like give ID_A to users. ID_A is an identifier managed by the line operator (communication monitoring apparatus 1) on the side of the line operator (communication monitoring apparatus 1) in order to identify the user regarding the communication line used by the user. When R_ID is transmitted (step a3), the communication monitoring apparatus 1 can link R_ID and ID_A (details will be described later). As shown in step c1 in FIG. 1, the user terminal 2 communicates with the service server 3A of the company service server 3A or another server 5 in order to use the service, or communicates with the web server of the other server 5 by web browsing. You can do it. At this time, as shown in step c2 in FIG. 1, the communication monitoring device 1 makes an instruction to the instruction server 3 based on the communication status of communication from the user terminal 2 to the company service server 3A or the other server 5. It is possible to notify the optimum timing of the push notification (details will be described later).

  As already explained, in the current situation where many applications that use push notifications are installed in the user terminal 2, the appealing power of push notifications is reduced. For this reason, even if the push notification is performed when the user terminal 2 is not used, the delivered information is likely to be overlooked. Then, the idea that it is better to carry out push notifications at the timing when the user terminal 2 is in use is born. However, determination during use of the user terminal 2 is not easy. Note that “in use of the user terminal 2” (when the user terminal 2 is used: when using the terminal) means that the user is viewing the terminal screen, the terminal screen is being displayed, or the lock is being released. Say. Further, “when the user terminal 2 is not used” (when the terminal is not used) means when the user is not looking at the terminal screen, when the terminal screen is not displayed (sleep state), or when the lock is activated. . Note the following <1> to <4> regarding the push notification implementation timing.

  <1> First, there is a method of notifying whether or not the user terminal 2 is in use and performing a push notification immediately when information suitable for the user is generated. In this case, there is an advantage that push notification can be made fastest. However, it is considered that the possibility that the user is touching the user terminal 2 is the smallest, and the appeal power of the push notification is extremely small.

  <2> In addition, there is a method for designating a time zone for performing the push notification. For example, the push notification is performed in the commuting time zone in which it is expected that the user on the train is touching the user terminal 2. However, there are some users who do not touch the user terminal 2 even during the commuting time period, and the appealing power of the push notification is not so high.

  <3> In addition, specify a specific area to perform push notification, and use sensor information such as GPS, WiFi (registered trademark), BLE (Bluetooth (registered trademark) Low Energy) to enter, exit, and stay in the specified area There is a way to monitor. According to this method, there is an advantage that timely information distribution (for example, PR of a special product) linked to a specific area can be performed. However, since the user is moving, there is a possibility that the user terminal 2 is not touched, and the high appealing power of the push notification cannot be desired. In addition, since the use of various sensor information needs to be approved by the user, it can be an obstacle to installing the company application from the viewpoint of privacy. In addition, when collecting sensor information periodically or sending collected information to the company's service server, there is concern about battery consumption, but if the battery consumption is high during background operation, the app may be uninstalled. Get higher. That is, there is an inconvenient situation that is not directly related to the push notification.

  <4> In addition, there is a method of performing push notification when using the company's (service provider) application. The in-house service server 3A can acquire from the user terminal 2 that the user is using the in-house application when using the in-house application, and the user is surely touching the user terminal 2, and the optimal timing of the push notification is performed. Can be notified to the instruction server 3. However, for example, when the company application is not frequently used by the user, the service provider of the company has few opportunities to know the optimal timing of the push notification.

  In view of the above circumstances, it is possible to perform push notification when using other than the use of the company's application, for example, when another company's application is used, or when a standard Web browser is used, and the optimal push notification There is a desire to increase opportunities to know the right timing. Therefore, in the present embodiment, the service provider of the company cooperates with the line operator or ISP company that uses the communication monitoring device 1, and the user uses the user terminal 2, for example, the terminal screen is viewed. A configuration is realized in which the communication monitoring device 1 is notified of a highly likely timing, and a push notification is performed at that timing.

A configuration of the communication monitoring apparatus 1 will be described.
As illustrated in FIG. 2, the communication monitoring apparatus 1 includes an R_ID-ID_A association unit 11, a cooperation target R_ID management unit 12, a timing determination / sharing unit 13 (determination unit), a user authentication unit 14, and a relay unit 15. And a functional unit such as an ID correspondence table T1 and a communication confirmation target user registration table T2. Note that the user terminal 2 has a provider application 21 that is an application developed by a service provider of the company, a third party application 22 that is an application developed by a service provider of another company, and a Web browser 23 installed. The unit 24 can communicate with the instruction server 3, the company service server 3A, and the other server 5 (via the communication monitoring device 1).

  The R_ID-ID_A associating unit 11 pays out the R_ID acquired from the user terminal 2 and the line for the same user during the pre-operation before the push notification (see step a1 to step a3 in FIG. 1). The ID_A managed in advance on the business operator side (communication monitoring device 1 side) is linked. The R_ID-ID_A association unit 11 registers the association result in the ID correspondence table T1.

  The cooperation target R_ID management unit 12 receives and manages the R_ID of the user who wants to know the execution timing of the push notification from the instruction server 3. The collaboration target R_ID management unit 12 manages the R_ID received from the instruction server 3 as the collaboration target R_ID. The cooperation target R_ID management unit 12 can obtain a list of cooperation target R_IDs from the service provider online or can obtain them offline. Further, the cooperation target R_ID management unit 12 may convert the acquired R_ID into ID_A and manage it.

  The timing determination / sharing unit 13 determines whether the user terminal 2 is in use from the communication status of the user terminal 2. Further, when the timing determination / sharing unit 13 determines that the user terminal 2 is in use, the timing determination / sharing unit 13 notifies the instruction server 3 of the execution timing of the push notification, and between the line operator and the service provider, Share the timing of push notifications. The timing determination / sharing unit 13 specifies a user who is a target for determining whether or not the user terminal 2 is in use from the communication confirmation target user registration table T2.

The user authentication unit 14 authenticates a user who performs communication.
The relay unit 15 relays the exchange of information between the communication monitoring apparatus 1 and the instruction server 3, the company service server 3 </ b> A, and the other server 5.

The ID correspondence table T1 is a table that manages R_ID and ID_A in association with each user who uses the service by the system of the present embodiment.
The communication confirmation target user registration table T2 includes the R_ID and the R_ID for each communication confirmation target user who wants to know the execution timing of the push notification among the users who use the service by the system of the present embodiment. This is a table for managing ID_A and service providers in association with each other.

(Variation of timing judgment / sharing unit 13)
[1-1]: For example, the timing determination / sharing unit 13 confirms the communication amount of the user terminal 2 with a packet counter or the like for the communication confirmation target user, and the user terminal 2 uses the communication amount when the communication amount increases. It determines that it is in the middle and notifies the instruction server 3. Here, since the communication includes background communication at the user terminal 2, for example, the user terminal 2 is using the communication amount obtained by subtracting the background communication amount by measuring the normal background communication amount. It is good to determine whether or not.

  [1-2]: Also, for example, the timing determination / sharing unit 13 analyzes the packet header and payload of communication from the user terminal 2 by DPI, and performs communication that is not background-specific communication (for example, background communication) If communication with a server other than the specific server that is operating on is detected, the user terminal 2 may be determined to be in use and notified to the instruction server 3.

  [1-3]: Also, for example, the timing determination / sharing unit 13 obtains in advance list information of a pair of R_ID and a specific URI (Uniform Resource Identifier) from the service provider, and from the user terminal 2 using DPI. If the acquired specific URI is included in the packet header, it is determined that the user terminal 2 is in use, and the instruction server 3 is notified. Thereby, for example, when a push notification is to be sent to a user who is interested in a car, the user terminal 2 can make a push notice during access to a URI that handles car information. In the case of [1-3], the cooperation target R_ID management unit 12 may acquire and manage a specific URI together with the cooperation target R_ID from the service provider.

  [1-4]: For example, the timing determination / sharing unit 13 acquires in advance the list information of the pair of R_ID and the specific keyword from the service provider, and packet payload of communication from the user terminal 2 by DPI When the acquired specific keyword is included in the packet payload, it is determined that the user terminal 2 is in use, and the instruction server 3 is notified. Thereby, for example, when a push notification is to be made to a user who is interested in a car, the user terminal 2 can make a push notice while browsing a web page that handles car information. In the case of [1-4], the cooperation target R_ID management unit 12 may acquire and manage keywords together with the cooperation target R_ID from the service provider.

(Variation of R_ID-ID_A pegging part 11)
[2-1-1]: For example, the R_ID-ID_A association unit 11 detects the detected R_ID and the communication monitoring device when the R_ID is detected from communication between the provider application 21 and the service provider using DPI. The ID_A managed in advance on the one side may be managed online or linked in real time.

  [2-1-2]: In addition, for example, the R_ID-ID_A association unit 11 matches the communication log from the user terminal 2 or member information (eg, the user's name) with ID_A, or the user terminal 2 R_ID and ID_A may be linked and managed without using DPI by directly receiving (separately sending) R_ID from applications 21 and 22.

[2-2-1]: For example, when the R_ID-ID_A associating unit 11 functions as an accepting unit that accepts an R_ID associated with ID_A, the accepting unit may be installed for each service provider.
When taking the form of [2-2-1], for the variation of [2-1-1], filtering the destination address (service server address) of the communication packet with the IP address of each reception unit, R_ID can be extracted, and the association between the extracted R_ID and ID_A can be realized. As for the variation of [2-1-2], R_ID is extracted by matching the access log of each reception unit with the DHCP / NAT log etc. of the network operator etc., and the extracted R_ID and ID_A Can be realized.

[2-2-2]: For example, when the R_ID-ID_A associating unit 11 functions as a receiving unit that receives an R_ID associated with ID_A, the receiving unit is installed in a centralized manner by the line operator, The reception unit can primarily receive and relay communication separately sent from the application and communication to the service provider using the service provider identifier.
When taking the form of [2-2-2], for the variation of [2-1-1], the destination address (service server address) of the communication packet is set by the IP address of this receiving unit such as a line carrier. R_ID is extracted by filtering or the like, and the association between the extracted R_ID and ID_A can be realized. In addition, for the variation of [2-1-2], R_ID is extracted and extracted by matching the access log of this reception unit such as a line carrier with the DHCP / NAT log etc. of the line carrier or the like. R_ID and ID_A can be linked.

<< Process >>
Next, processing of the communication monitoring apparatus 1 will be described.
As shown in FIG. 3, the overall processing of the communication monitoring apparatus 1 is as follows.

  First, the R_ID-ID_A association unit 11 constantly updates the ID correspondence table T1 at a predetermined time interval (step S1). For example, when the communication monitoring device 1 acquires the corresponding R_ID for ID_A managed on the communication monitoring device 1 side and registered in the ID correspondence table T1, the acquired R_ID is associated with the ID correspondence table T1. Link to ID_A.

  Next, the collaboration target R_ID management unit 12 receives the collaboration target R_ID presented by the predetermined service provider (step S2).

Next, the timing determination / sharing unit 13 adds a user corresponding to the cooperation target R_ID as a communication confirmation target user to the communication confirmation target user registration table T2 (step S3). For example, when the ID_A of the user corresponding to the cooperation target R_ID exists in the ID correspondence table T1, the timing determination / sharing unit 13 registers this ID_A in the communication confirmation target user registration table T2 and selects the communication confirmation target user. to add.
If the ID_A of the user corresponding to the cooperation target R_ID does not exist in the ID correspondence table T1, the timing determination / sharing unit 13 first adds the R_ID as the cooperation target R_ID to the communication confirmation target user registration table T2. . When the ID_A corresponding to the cooperation target R_ID newly appears at the update timing in step S1, the timing determination / sharing unit 13 registers this ID_A in the communication confirmation target user registration table T2 to register the communication confirmation target user. Add

Next, the timing determination / sharing unit 13 confirms the communication of the communication confirmation target user registered in the communication confirmation target user registration table T2 (step S4).
Next, the timing determination / sharing unit 13 determines whether or not the user terminal 2 of the communication confirmation target user is in use, and if it is determined to be in use, notifies the instruction server 3 of the execution timing of the push notification. (Step S5). With this notification, the R_ID of the communication confirmation target user is shared between the line provider and the service provider.

  Thereafter, the instruction server 3 instructs the distribution server 4 (FIG. 1) to perform push notification, and the push notification by the distribution server 4 is performed. This push notification is made when the user terminal 2 is in use, for example, when the user is looking at the terminal screen. Therefore, the user reliably recognizes the push notification when the push notification is performed, and is distributed by the push notification. Information can be accessed immediately.

An operation example of the R_ID-ID_A association unit 11 for executing the entire process of FIG. 3 will be described.
As shown in FIG. 4, an operation example of the R_ID-ID_A association unit 11 is as follows.

  First, the R_ID-ID_A association unit 11 constantly monitors communication on the network (step A1). For example, the R_ID-ID_A association unit 11 monitors by periodically acquiring and analyzing a packet generated by communication of an unspecified user terminal 2.

  Next, the R_ID-ID_A association unit 11 determines whether or not R_ID is included in the acquired packet (step A2). If not included (step A2 / No), the process returns to step A1 and communication monitoring is continued.

  On the other hand, when the R_ID is included in the acquired packet (step A2 / Yes), the R_ID-ID_A association unit 11 and the ID_A of the user (communication person) of the user terminal 2 that communicated the acquired packet. Is added to the ID correspondence table T1 and registered (step A3).

  Next, the R_ID-ID_A associating unit 11 determines whether or not the R_ID is a monitoring target necessary for determining the execution timing of the push notification (Step A4). For example, before the addition in step A3, R_ID was in the ID correspondence table T1, but when ID_A corresponding to the R_ID is blank, R_ID becomes the monitoring target. If it is not the monitoring target (step A4 / No), the process returns to step A1 to continue monitoring the communication.

On the other hand, when R_ID is to be monitored (step A4 / Yes), the R_ID-ID_A association unit 11 adds ID_A added to the ID correspondence table T1 (see step A3) to the communication confirmation target user registration table T2, and adds The user corresponding to the ID_A thus selected is set as a communication confirmation target user (step A5).
According to the process of FIG. 4, it is possible to specify a user who confirms communication in order to notify the execution timing of push notification.

An operation example of the cooperation target R_ID management unit 12 for executing the entire process of FIG. 3 will be described.
As shown in FIG. 5, an operation example of the cooperation target R_ID management unit 12 is as follows.

  First, the cooperation target R_ID management unit 12 acquires one or a plurality of cooperation target R_IDs designated by the service provider from a specific service provider (such as the instruction server 3), and the service provider and the service provider. The R_ID to be linked is shared with (step B1).

Next, the loop processing of the following steps B3 to B5 is executed for the shared cooperation target R_ID (step B2).
The collaboration target R_ID management unit 12 determines whether or not ID_A corresponding to the collaboration target R_ID exists in the ID correspondence table T1 (step B3).

When ID_A exists (step B3 / Yes), the cooperation target R_ID management unit 12 adds the ID_A to the communication confirmation target user registration table T2, and sets the user corresponding to the added ID_A as the communication confirmation target user (step B4). ). As a result, in the communication confirmation target user registration table T2, R_ID as the shared cooperation target R_ID, ID_A, and the identifier of the service provider that specifies the cooperation target R_ID are associated and registered.
Thereafter, the loop process is advanced for another cooperation target R_ID, or if there is no other cooperation target R_ID, the process of FIG. 5 ends.

When there is no ID_A (step B3 / No), the collaboration target R_ID management unit 12 adds the R_ID as the shared collaboration target R_ID to the ID correspondence table T1 (step B5). ID_A corresponding to the added R_ID temporarily becomes blank, but is supplemented when the ID_A is discovered in connection with communication.
Thereafter, the loop process is advanced for another cooperation target R_ID, or if there is no other cooperation target R_ID, the process of FIG. 5 ends.
According to the processing in FIG. 5, one or more cooperation target R_IDs designated by the service provider can be managed on the side of the circuit provider or the like.

An example of the operation of the timing determination / sharing unit 13 for executing the entire process of FIG. 3 will be described.
As shown in FIG. 6, an example of the operation of the timing determination / sharing unit 13 is as follows.

  First, the timing determination / sharing unit 13 always executes the following loop processing of steps C2 to C4 for each of the communication confirmation target users (step C1).

The timing determination / sharing unit 13 monitors the communication of the user terminal 2 of the communication confirmation target user (step C2).
Next, the timing determination / sharing unit 13 determines whether or not the user terminal 2 of the communication confirmation target user is in use (step C3). If it is determined that it is not in use (step C3 / No), the process returns to step C1, and loop processing is executed for other communication confirmation target users.

On the other hand, if it is determined that it is in use (step C3 / Yes), the R_ID of the communication confirmation target user is notified to the service provider's instruction server 3, and the R_ID of the communication confirmation target user is provided to the service provider and the service provider. (Step C4).
Then, it returns to step C1 and performs a loop process about another communication confirmation object user. When the loop processing is completed for all the communication confirmation target users, the processing in FIG. 6 (one time of regular processing) is terminated.

  According to the process of FIG. 6, the user designated as the R_ID to be linked by the service provider is determined as a communication confirmation target user, the user terminal 2 is determined to be in use, and the push notification execution timing is notified from the network operator or the like. be able to.

≪Summary≫
According to the present embodiment, by constructing a system in which the service provider can collaborate with a line carrier having the communication monitoring device 1, the service provider can obtain the optimum execution timing of the push notification. The timing that the terminal 2 is in use can be notified from the communication monitoring apparatus 1.
Therefore, it is possible to improve the appeal power of the push notification used in the user terminal.
As a result, the unsealing rate of the push notification from the distribution server 4 is improved on the user terminal 2 side. Oversight of push notifications by users using the service is reduced. If the information distributed by the push notification is used, the profits of the service provider and the line provider are expected to be improved, and the possibility of the final profit return to the user is increased.
Further, if the judgment logic based on the variations [1-3] and [1-4] of the timing judgment / sharing unit 13 is adopted, push notification can be performed only for users who are interested in specific information. It is also possible to provide a user with more benefits than usual with the funds.

In addition, it is impossible for the service provider alone to directly grasp communication other than communication using the application provided by the service provider. However, the communication monitoring device 1 indirectly grasps such communication. Will be able to. As a result, the service provider can be notified more frequently from the communication monitoring device 1 of the timing when the user terminal 2 is in use, which is the optimal execution timing of the push notification.
Therefore, it is possible to further improve the appealing power of push notifications used in the user terminal.

The present invention is not limited to the above embodiment, and can be modified without departing from the spirit of the present invention.
For example, in the present embodiment, the service provider has been notified by the line operator of the communication monitoring apparatus 1 that the user terminal 2 is being used by communication with another company's application. However, each service provider push-notifies each other by notifying each other that the applications of each company are communicating and the user terminal 2 is in use between service servers owned by a plurality of service providers. It may be possible to obtain a number of optimal execution timings.

In addition, it is possible to realize a technique in which various techniques described in this embodiment are appropriately combined.
Further, the software described in the present embodiment can be realized as hardware, and the hardware can also be realized as software.
In addition, hardware, software, processing procedures, and the like can be changed as appropriate without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 1 Communication monitoring apparatus 2 User terminal 3 Instruction server 3A In-house service server 4 Distribution server 5 Other server 11 R_ID-ID_A association part 12 Cooperation target R_ID management part 13 Timing judgment and sharing part (determination part)

Claims (3)

A communication monitoring device that monitors communication of a user terminal that receives a push notification from a distribution server,
It is determined whether or not the user terminal is in use from the communication status of the user terminal, and when it is determined that the user terminal is in use, an instruction server that instructs the push notification to the distribution server indicates an execution timing of the push notification. A determination unit for notifying,
A communication monitoring device. The determination unit
When it is determined that the user terminal is in use by checking communication including communication other than using an application provided by the service provider having the instruction server, the push notification is performed on the instruction server. Notify the timing,
The communication monitoring apparatus according to claim 1. A communication monitoring method in a communication monitoring apparatus for monitoring communication of a user terminal that receives a push notification from a distribution server,
The communication monitoring device includes:
Determining whether the user terminal is in use from the communication status of the user terminal;
If it is determined that the push notification is in use, the instruction server that instructs the push notification to the delivery server is notified of the execution timing of the push notification.
And a communication monitoring method.

Images