WO2017128978A1

WO2017128978A1 - Push information monitoring device, push information monitoring method, and client

Info

Publication number: WO2017128978A1
Application number: PCT/CN2017/071271
Authority: WO
Inventors: 伍中联
Original assignee: 广州市动景计算机科技有限公司
Priority date: 2016-01-28
Filing date: 2017-01-16
Publication date: 2017-08-03
Also published as: CN105743774B; CN105743774A

Abstract

Provided in embodiments of the present application are a method and device for push information monitoring for detecting whether push information is displayed in an information pushing process. The embodiments of the present application, in a case when it is not possible to learn directly whether a notification display switch is enable on a client, by combining a state of the notification display switch and a display state comprising a message box having a viewable image, achieve indirect acquisition of the state of the notification display switch by detecting a state of the message box. A server is allowed to effectively learn the rate at which the push information is displayed, the provision of guidance to a user having disabled push notifications to enable same is facilitated, and the level of activeness of the user is effectively increased.

Description

Push information monitoring device, push information monitoring method and client

Technical field

The present application relates to the field of information push technology, and in particular, to a push information monitoring device, a push information monitoring method, and a client.

Background technique

Electronic devices such as smart phones, mobile Internet devices (MIDs), personal digital assistants (PDAs), and tablets have become indispensable communication and entertainment tools in people's daily work and life. Many electronic devices support user-defined installation of various applications (Application, App) to meet different user needs. After the electronic device installs the corresponding application, the background of the application can periodically provide the user with the push function of the information when new information or news is generated. However, when the notification information is pushed to the electronic device in the background, there is a case where the notification information is not displayed or lost, and the main reason for the occurrence of the notification is that the user turns off the notification display switch of the application. However, whether the user closes the notification display switch of the application, the server background is not known, and thus the corresponding measures cannot be taken to guide the user to turn on the notification display switch, so that the penetration rate and the display rate of the push message are low. Therefore, how to know the status of the notification display switch of the application when pushing the notification information is an urgent problem to be solved.

Summary of the invention

In view of this, the purpose of the embodiments of the present application is to provide a sending information monitoring apparatus, a push information monitoring method, and a client.

The push information monitoring device provided by the embodiment of the present application is applied to a client that is in communication with a server, and the push information monitoring device includes: a message box creating module, after receiving the push information sent by the server Creating a message box including a view, the message box being associated with a display state of the view and a display state of the push information; a callback information generating module for monitoring the view; and listening to the When the view is displayed by the message box, the callback information is generated. The status information sending module is configured to send, to the server, status information indicating whether the client uses the push information to display the notification display switch when the callback information is detected. And when the callback information is not detected, sending status information indicating that the notification display switch has been turned off to the server.

The method for monitoring the push information provided by the embodiment of the present application is applied to a client that is in communication with a server, and the method for monitoring the push information includes: after receiving the push information sent by the server, creating a message frame including a view And monitoring the view, the message box is associated with the display state of the view and the display state of the push information; if the callback information is detected, sending a message indicating that the display notification switch has been turned on to the server Status information, wherein the callback information is generated when the view is displayed by the message box, and the notification display switch is used to control display of push information in the client; if no callback information is detected, The server sends status information indicating that the notification display switch has been turned off.

A client provided by the embodiment of the present application, the client includes: a memory; a processor; and a push information monitoring device, where the push information monitoring device includes one or more stored in the memory and is processed by the processor The executed module, the information pushing device includes: a message box creating module, configured to: after receiving the push information sent by the server, create a message box including a view, where the message box displays the view state and the view The display status of the push information is associated; the callback information generating module is configured to monitor the view; and generate callback information when the view is displayed by the message box; the status information sending module is configured to When the callback information is detected, sending to the server indicates that the client is used to control whether the push information indicates that the notification display switch has been turned on. Status information, and when no callback information is detected, status information indicating that the notification display switch has been turned off is sent to the server.

A computer readable storage medium on which a program for executing the method of the embodiment of the present application is recorded is provided by an embodiment of the present application.

Compared with the prior art, the push information monitoring device, the push information monitoring method, and the client of the present application combine the state of the notification display switch with the message including the view when the client notification display switch is not directly accessible. The display state of the frame reaches the indirect acquisition of the state of the notification display switch by detecting the state of the message box. The server can effectively know the display rate of the push information, and facilitates opening and guiding the user who closes the push notification, thereby effectively improving the activity level of the user.

The above described objects, features, and advantages of the present invention will become more apparent from the following description.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. It should be understood that the following drawings show only certain embodiments of the present application, and therefore It should be seen as a limitation on the scope, and those skilled in the art can obtain other related drawings according to these drawings without any creative work.

FIG. 1 is a schematic diagram of interaction between a client and a server according to an embodiment of the present application;

2 is a schematic structural diagram of a client according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of another client according to an embodiment of the present application;

4 is a block diagram of a function module for pushing information monitoring according to an embodiment of the present application;

FIG. 5 is a block diagram of another function module for pushing information monitoring according to an embodiment of the present application;

FIG. 6 is a flowchart of a method for monitoring push information according to an embodiment of the present application;

FIG. 7 is a flowchart of another method for monitoring push information according to an embodiment of the present application.

Main component symbol description

服务器 server	100100
客户端 Client	200200
推送信息监控装置Push information monitoring device	1010
存储器 Memory	2020
处理器 processor	3030
推送信息检测模块Push information detection module	101101
消息框创建模块Message box creation module	102102
消息框状态控制模块Message box status control module	103103
回调信息生成模块Callback information generation module	104104
状态信息发送模块Status information sending module	105105

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the invention, which are set forth in the claims Selected embodiments of the present application are shown. All other embodiments obtained by a person skilled in the art based on the embodiments of the present application without creative efforts are within the scope of the present application.

It should be noted that similar reference numerals and letters indicate similar items in the following figures, and therefore, once an item is defined in a drawing, it is not necessary to further define and explain it in the subsequent drawings. Also, in the description of the present application, the terms "first", "second", and the like are used merely to distinguish a description, and are not to be construed as indicating or implying a relative importance.

As shown in FIG. 1 , it is a schematic diagram of the client 200 provided by the embodiment of the present application interacting with the server 100 . The server 100 is in communication with one or more clients 200 over a network for data communication or interaction. The server 100 can provide at least one installation package of an application (Application, APP) suitable for various operating systems for the client 200 to download. After the client 200 accesses the server 100 through the network, an installation package of an application suitable for the operating system of the client 200 can be downloaded from the server 100 through the network to install the application to the server. In the client 200. In this embodiment, after the client 200 installs the application, the client 200 may periodically receive the push information about the application that is pushed by the server 100. In the preferred embodiment, the client 200 is installed with an application program downloaded from the server 100 for the operating system of the client 200, and the operating system is an Android system. The application is preferably a browser, such as a UC browser.

The server 100 may be, but not limited to, a network (web) server 100, a ftp (file transfer protocol) server 100, a database server 100, and the like. The client 200 can be, but is not limited to, a desktop, a portable computer, a tablet, a smart phone, a personal data assistant (PDA), a smart wearable device, or other type of computer device. The operating system of the client 200 may be, but not limited to, an Android system, an IOS system, a Windows Phone system, and the like. Preferably, in this embodiment, the operating system of the client 200 is an Android system.

As shown in FIG. 2, it is a schematic structural diagram of a client in the embodiment of the present application. The client can include a processing module 210, a storage subsystem 220, an input device 230, a display 240, a network interface 250, and a bus 260.

The processing module 210 can be a multi-core processor or multiple processors. In some embodiments, processing module 210 can include a general purpose main processor and one or more special coprocessors, such as a graphics processing unit (GPU), a digital signal processor (DSP), and the like. In some embodiments, processor 100 can be implemented using custom circuitry, such as an application specific integrated circuit (ASIC) or field programmable gate arrays (FPGA). In some implementations, the processing module 210 can be a similar circuit that executes executable instructions stored on itself. In still other implementations, the processing module 210 can execute executable instructions stored on the storage subsystem 210.

Storage subsystem 220 can include various types of storage units, such as system memory, read only memory (ROM), and persistent storage. The ROM may store static data or instructions required by the processing module 210 or other modules of the client. The persistent storage device can be a readable and writable storage device. The persistent storage device may be a non-volatile storage device that does not lose stored instructions and data even after the client is powered off. In some embodiments, the persistent storage device employs a mass storage device (eg, magnetic or optical disk, flash memory) as the permanent storage device. In other embodiments, the persistent storage device can be a removable storage device (eg, a floppy disk, an optical drive). The system memory can be a readable and writable storage device or a volatile read/write storage device, such as dynamic random access memory. System memory can store instructions and data that some or all of the processors need at runtime. Moreover, storage subsystem 220 can include any combination of computer readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read only memory), and magnetic disks and/or optical disks can also be employed. In some embodiments, storage subsystem 220 can include removable storage devices that are readable and/or writable, such as a compact disc (CD), a read-only digital versatile disc (eg, a DVD-ROM, a dual layer DVD-ROM) ), read-only Blu-ray Disc, Ultra Density Disc, Flash Card (such as SD card, min SD card, Micro-SD card, etc.), magnetic soft Disk and so on. The computer readable storage medium does not include a carrier wave and an instantaneous electronic signal transmitted by wireless or wire. In some embodiments, the storage subsystem 220 can store one or more software programs that can be executed by the processing module 210 or resource files that need to be invoked. The resource files can include some third-party libraries, including but not limited to audio libraries, video libraries. , 2D graphics library, 3D graphics library.

The user interface can be provided by one or more user input devices 230, display 240, and/or one or more other user output devices. Input device 230 can include means for a user to input a signal to a client, and the client can interpret the signals containing particular user requests or information. In some embodiments, a web address may be input to the user interface through a keyboard to display webpage content corresponding to the input webpage. In some embodiments, input device 230 can include some or all of a keyboard button, touch screen, mouse or other pointing device, scroll wheel, click wheel, dial, button, switch, keypad, microphone, and the like.

The display 240 can display images generated by the client, and can include various types of image devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), a light emitting diode (LED) (including an organic light emitting diode (OLED)), and a projection. A collection of systems and the like with other supporting electronic devices (eg, DACs, ADCs, signal processors, etc.). In some embodiments, it is also possible to additionally provide other user output devices, or to replace display 240, such as a signal light, a speaker, a tactile sensor, a printer, and the like.

In some embodiments, the user interface can be provided through a graphical user interface. Certain areas of the display 240 define some visual graphical elements as interactive objects or control objects that the user selects through the input device 230. For example, the user can operate the user input device 230 to move the specified location input URL on the screen, and control the display of the webpage content corresponding to the webpage on the display 240. In some embodiments, a touch device that can recognize a user gesture can be used as an input device that can, but need not, be associated with an array on display 300.

Network interface 250 provides voice and/or data communication functionality to the client. In some embodiments, network interface 250 can include a radio frequency transceiver to communicate sound and/or data (eg, using cellular telephone technology, such as 3G, 4G or EDGE, WIFI data network technology), GPS accepting modules, and/or other Module. In some In an embodiment, network interface 250 may provide an additional wireless network connection or an alternative wireless interface. Network interface 250 may be a combination of hardware (eg, antennas, modems, codecs, and other analog and/or digital signal processing circuits) and software modules.

Bus 260 can include various systems, external devices, and chip buses that connect various components within the client. For example, bus 260 connects processing device 100 to storage subsystem 220, and may also connect input device 230 and display 240. Bus 260 may also cause the client to connect to the network via network interface 250. In this case, the client can be part of multiple networked computer devices. Any or all of the components of the client may be coordinated for use in embodiments of the present application.

Some embodiments include electronic components, such as a microprocessor, a memory that stores computer instructions and data in a computer readable storage medium. Many of the features described in the Detailed Description section can be implemented by the method steps of executing computer instructions stored on a computer readable storage medium. When these computer instructions are executed, the computer processing unit performs various functions of the instructions. The embodiment of the program instructions or computer code may be machine code, such as code compiled using a computer, electronic component or microprocessor of the object to be parsed to compile other high-level languages.

It should be understood that the client is schematic. The client may have other functions not specifically described (eg, mobile call, GPS, power management, one or more cameras, various connection ports or accessories for connecting external devices, etc.). Further, the specific functional modules involved in the client 100 are described herein, and the description of these functional modules is for convenience of description, and does not mean a specific physical configuration of the functional components. Moreover, these functional modules do not need to be in one-to-one correspondence with physical modules. The module can be configured to perform various operations, such as by programming or setting up appropriate control circuitry, and the module may be reconfigured according to initial settings. Embodiments of the present application can be implemented in various devices, including electronic devices, by using a combination of hardware and software.

The embodiment further provides a non-volatile readable storage medium, where the storage medium stores one or more programs, and when the one or more modules are applied to the computing device, the computing device can be The instructions of each step of the method described in the embodiment of the present application are executed.

FIG. 3 is a schematic structural diagram of an example of a client in the embodiment of the present application. The client 200 includes a push information monitoring device 10, a memory 20, and a processor 30.

The memory 20 and the processor 30 are electrically connected directly or indirectly to each other to implement data transmission or interaction. For example, electrical connections can be made to one another via one or more communication buses or signal lines.

An example of the foregoing storage subsystem 220 is that the memory 20 can be, but not limited to, a random access memory (RAM), a read only memory (ROM), and a programmable read only memory ( Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), and the like. The memory 20 is used to store a program, and the processor 30 executes the program after receiving an execution instruction.

An example of such a processing module 210 is the processor 30, which may be an integrated circuit chip with signal processing capabilities. The processor 30 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP processor, etc.), or a digital signal processor (DSP), an application specific integrated circuit. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general purpose processor may be a microprocessor or the processor 30 may be any conventional processor or the like.

The push information monitoring device 10 includes at least one or more software functions that can be stored in the memory 20 or in an operating system (OS) of the client 200 in the form of software or firmware. Module. The processor 30 is configured to execute an executable module stored in the memory 20, such as a software function module or a computer program included in the push information monitoring device 10. In this embodiment, the client 200 is installed with an application program downloaded from the server 100 and adapted to the operating system of the client 200, and the operating system is an Android system. The push information monitoring device 10 can be installed A separate application to the client 200, or a portion of the installed application (such as a functional module) is downloaded from the server 100.

Please refer to FIG. 4 , which is a functional block diagram of a push information monitoring apparatus of a client provided by an embodiment of the present application. The push information monitoring device includes a message box creating module 102, a callback information generating module 104, and a status information sending module 105.

The message box creating module 102 is configured to: after receiving the push information sent by the server, create a message box including a view, where the message box associates the display state of the view with the display state of the push information.

The callback information generating module 104 is configured to monitor the view; and generate callback information when the view is displayed by the message box.

The status information sending module 105 is configured to send status information indicating that the notification display switch has been opened to the server when the callback information is detected, and send the notification display switch to the server when the callback information is not detected. Status information that has been turned off, the notification display switch is used to control the display of push information in the client.

In the embodiment of the present application, the notification display switch is used to control whether to display the notification information, that is, the notification display switch can be used to control whether the push information in the client is displayed. In order to be able to know the on/off state of the notification display switch, when the client 200 receives the push information sent by the server 100, a message box corresponding to the push information is created, and a view is created on the message box for display. The display state of the message box is related to the display state of the push information. Therefore, after the message frame is established, the display state of the view is controlled according to the display state of the push information, so that the display state of the message frame can be The display state of the inter-ground reaction push information. For example, in the Android system, the method for implementing the message box to associate the display state of the view with the display state of the push information may be: setting a listener that listens to the display state of the push information, and then monitoring the result. Combined with the action of the message box.

On the basis that the message box associates the display state of the view with the display state of the push information, after receiving the push information sent by the server 100, the client 200, if the notification display switch is turned on, pushes the information at the location. Displayed in the information notification column of the client 200, thereby triggering the message box to perform display The operation of the view. If the notification display switch is in the off state, the message box does not perform any operation, so that the view is not displayed. Therefore, in this embodiment, the view of the message box is also monitored to determine whether the view is displayed. By monitoring whether the view of the message box is displayed, the status of the notification display switch can be indirectly known.

When the notification display switch is turned on, the push information is displayed in the notification bar, and the message box displays the view, and generates a corresponding callback information by monitoring; when the notification display switch is turned off, the push information is not displayed in the notification column. And the message box will not display the view, it will not monitor the view is displayed and will not generate callback information. Therefore, after receiving the push information sent by the server 100, detecting whether the callback information is generated, whether the push information is displayed or not, and determining the status of the notification display switch.

In this embodiment, the detection of the callback information may be performed from the moment when the push information sent by the server 100 is received. According to the above correspondence, if the callback information is detected, the display state of the message frame is the display view, and it can be known that the push information has been displayed, thereby determining that the notification display switch has been turned on. Conversely, if no callback information is detected, it can be determined that the notification display switch has been turned off. After the status of the notification display switch is obtained, the corresponding status information is transmitted to the server 100, so that the server 100 can know whether the notification display switch of the client 200 is turned off.

In summary, after receiving the push information, a message box including a view is created, and the message box associates the display state of the view with the display state of the push information, thereby being indirectly reflected by the display state of the message frame. Pushing the display state of the information, monitoring the view, and generating the callback information when the view is displayed by the message box, so that when the callback information is detected, the server is sent to indicate that the client is used to control the push information. Whether to display the status information that the notification display switch has been turned on, and when the callback information is not detected, send status information indicating that the notification display switch has been turned off to the server, by creating a message box and monitoring the view in the message box, Enables the server to effectively determine the status of the notification display switch.

Referring to FIG. 5, the push information monitoring apparatus 10 further includes a push information detecting module 101 and a message box state control module 103. among them:

The push information detecting module 101 is configured to detect whether the client 200 receives the push information sent by the server 100.

After the push information sent by the server 100 is received by the client 200, it is generally not directly displayed to the user, but the content of the push information is extracted by the operating system of the client 200, and then displayed in the corresponding information notification column. When the display switch for controlling whether or not to display the notification information is turned off, even if the client 200 receives the push information transmitted by the server 100, the client 200 does not display the push information. In this embodiment, the operating system of the client 200 is an Android system. In the Android system, the push information is displayed through the Push Notification function. When the user closes the notification status of the Push Notification, the client 200 receives the received information. Push information is not notified.

The message box creating module 102 is configured to: after receiving the push information sent by the server 100, create a message box including a view, where the message box associates the display state of the view with the display state of the push information.

In this embodiment, after receiving the push information sent by the server 100, the client 200 creates a message box corresponding to the push information, and creates a view on the message box for display. After the message frame is established, the display state of its view is controlled according to the display state of the push information. The display state of the push information is indirectly reflected by the display state of the message box. Specifically, in the Android system, the method for implementing the message box to associate the display state of the view with the display state of the push information may be: setting a listener that listens to the display state of the push information, and then monitoring The result is combined with the action of the message box.

In this embodiment, the message box may be a Toast message box in the Android system. Toast is a simple message box that won't get the focus, can't be clicked, and will automatically disappear after a period of time according to the preset length of time, without affecting the normal operation of the client 200. Toast is a standard control provided by Android. It is suitable for any version of Android system. It is more convenient to use and has a wider range of applications.

To further reduce the impact of the view of the message box on the user when displayed, the format of the view is set to be transparent and the area size is zero. Even if the operation of displaying the view is performed, the user does not see the view on the operation interface of the client 200. In this way, the user will not be aware of the extra message box, and the user experience will not be affected as a result.

The message box state control module 103 is configured to control the message box to perform an operation of displaying the view when the push information is displayed in the information notification column of the client 200.

On the basis that the message box associates the display state of the view with the display state of the push information, after receiving the push information sent by the server 100, the client 200, if the notification display switch is turned on, pushes the information at the location. The information notification column of the client 200 is displayed, and the message box is triggered to perform an operation of displaying the view. If the notification display switch is in the off state, the message box does not perform any operation, so that the view is not displayed. Therefore, by detecting whether the view of the message box is displayed, the state of the notification display switch can be indirectly known.

The callback information generating module 104 is configured to monitor the view, and generate callback information when the view is displayed by the message box.

In this embodiment, the client 200 can detect whether the view of the message box is displayed by monitoring the callback. Specifically, whether the view is displayed by the message box is monitored by adding an additional status event that can be monitored for callback to the view. When the view is displayed, the additional status event is triggered to generate a corresponding callback information. If the view is not displayed, no events will be fired. On the basis of this, it is only necessary to detect whether the callback information is generated after receiving the push information sent by the server 100, and whether the push information is displayed or not, and then determine the status of the notification display switch.

The status information sending module 105 is configured to, when the callback information generating module 104 generates the callback information, send, to the server 100, state information indicating whether the client 200 is used to control whether the push information is displayed, that the notification display switch has been turned on, and When the callback information generating module 104 does not generate the callback information, it transmits to the server 100 status information indicating that the notification display switch has been turned off.

In the present embodiment, the detection of the callback information is started from the time when the push information transmitted by the server 100 is received. According to the above correspondence, if there is callback information generated, the display state of the message box is a display view, and it can be known that the push information has been displayed, thereby determining that the notification display switch has been turned on. Conversely, if no callback information is generated, it can be determined that the notification display switch has been turned off. After the status of the notification display switch is obtained, the corresponding status information is transmitted to the server 100, so that the server 100 can know whether the notification display switch of the client 200 is turned off.

Further, in the case where the notification display switch has been turned off, since the push information is not displayed, no operation associated with it is triggered. In order to achieve accurate detection of the state, it is detected whether there is callback information generated within a preset period of time after receiving the push information sent by the server 100. Under normal conditions, if the notification display switch is turned on, the time required from receiving the push information to detecting the callback information is about 1 to 2 seconds. If the callback information is not detected during this time, the notification display can be indicated. The switch is off. Specifically, the length of the preset time period may be set to a value slightly longer than 2 seconds (for example, 5 seconds), and after receiving the push information sent by the server 100, the callback information is detected, if a callback is detected. The information immediately transmits status information indicating that the notification display switch has been turned on to the server 100. If no callback information is detected within the time period, status information indicating that the notification display switch has been turned off is transmitted to the server 100. Specifically, in the Android system, the operation is implemented by a Handler.

In summary, the embodiment of the present application may enable the server 100 to know whether the notification display switch of the client 200 is turned off, so that the server 100 takes corresponding measures as needed to guide the user to open the notification when the notification display switch is turned off. The notification display switch is used to enhance the penetration and display rate of the push information.

Please refer to FIG. 6 , which is a flowchart of a method for monitoring push information provided by an embodiment of the present application. The specific flow shown in FIG. 6 will be described in detail below.

Step S601, after receiving the push information sent by the server, create a message box including a view, and listen to the view.

In order to be able to know the on/off state of the notification display switch, after the client receives the push information sent by the server, a message box corresponding to the push information is created, and a view is created on the message box for display, the message box A display state of the view is associated with a display state of the push information. If the notification display switch is in an open state, the push information is displayed in the information notification column of the client, thereby triggering the message box to perform an operation of displaying the view. If the notification display switch is in the off state, the message box does not perform any operation, so that the view is not displayed. Therefore, in this embodiment, the view of the message box is also monitored to determine whether the view is displayed. By monitoring whether the view of the message box is displayed, the status of the notification display switch can be indirectly known.

Step S602, if the callback information is detected, send status information indicating that the display notification display switch has been opened to the server, wherein the callback information is generated when the view is displayed by the message box.

Step S603, if the callback information is not detected, send status information indicating that the notification display switch has been turned off to the server.

When the notification display switch is turned on, the push information is displayed in the notification bar, and the message box displays the view, and generates a corresponding callback information by monitoring; when the notification display switch is turned off, the push information is not displayed in the notification column. And the message box will not display the view, it will not monitor the view is displayed and will not generate callback information. Therefore, after receiving the push information sent by the server, detecting whether the callback information is generated, whether the push information is displayed or not, and determining the status of the notification display switch is determined.

Therefore, if the callback information is detected, the display state of the representation message box is the display view, and it can be known that the push information has been displayed, thereby determining that the notification display switch has been turned on. Conversely, if no callback information is detected, it can be determined that the notification display switch has been turned off. After the status of the notification display switch is obtained, the corresponding status information is sent to the server, so that the server can know whether the notification display switch of the client is closed.

In summary, after receiving the push information, a message box including a view is created, and the message box associates the display state of the view with the display state of the push information, thereby being indirectly reflected by the display state of the message frame. Push information Displaying a state, monitoring the view, and generating callback information when the view is displayed by the message box, so that when the callback information is detected, sending a message to the server indicating whether the client is used to control whether the push information is displayed Displaying status information that the switch has been turned on, and sending status information indicating that the notification display switch has been turned off to the server when the callback information is not detected, by creating a message box and monitoring the view in the message box, so that the server can enable the server to Effectively determines the status of the notification display switch.

Please refer to FIG. 7 , which is a flowchart of another method for monitoring push information provided by an embodiment of the present application. The specific flow shown in FIG. 7 will be described in detail below.

Step S701, detecting whether the client receives the push information sent by the server. If yes, step S402 is performed, and if not, the flow is ended.

In this embodiment, when the server has notified that it needs to be sent to the client, the corresponding push information is generated according to the content of the notification and then sent, and the client receives the push information sent by the server. The monitoring of the push information is performed on the basis that the push information is sent to the client.

Step S702, creating a message box including a view, and monitoring the view, the message box is associated with a display state of the view and a display state of the push information.

In this embodiment, the operating system of the client is an Android system, and the message box is a Toast message box in the Android system.

Step S703, if the notification display switch is in the on state, the push information is displayed in the information notification column of the client, and the message box is controlled to perform an operation of displaying the view.

In this embodiment, the view is a view that is transparent and has an area size equal to zero. The user is not affected by the display of the message box and does not know that the status of the notification display switch is being detected.

Step S704, listening to the view being displayed by the message box, generating callback information.

Whether the callback information is generated or not reflects indirectly whether the push information is displayed. By detecting the callback information, the status of the notification display switch can be indirectly obtained. In this reality In an embodiment, whether the view is displayed by the message box is monitored by adding to the view an additional status event that can be listened to for callback.

In step S705, it is detected whether there is callback information, if yes, step S706 is performed, and if no, step 707 is performed. If the notification display switch is on, the callback information can be detected, and if the notification display switch is off, the callback information cannot be detected.

Step S706, sending status information indicating that the notification display switch has been turned on to the server.

Step S707, sending status information indicating that the notification display switch has been turned off to the server.

In the present embodiment, the detection of the callback information is performed from the time of receiving the push information transmitted by the server. Whether or not callback information is generated is detected within a preset period of time after receiving the push information sent by the server.

The push information monitoring method provided by the present application is further described in detail below through a specific example.

For example, assume that there are multiple clients 200 in communication with the server 100. The client 200 downloads an application (such as a browser) from the server 100 and installs it. The push information monitoring device 10 may be a part of a function module downloaded and installed in a browser of the smartphone. When there is a new notification that needs to be pushed (such as the hot news that just happened), the server 100 sends the corresponding push information to each client 200. In each client 200, some notification display switches may have been turned off, and some notification display switches are turned on. After receiving the push information, the client 200 establishes a Toast message box corresponding to the operating system information notification display bar. The Toast includes a transparent View view with an area size of 0, and adds an Attach State event listener for the View view. Callback. If the client 200 notifies that the display switch is turned on, the push information is displayed in the information notification display bar, triggering Toast to display the View view. When the operation in which the View view is displayed is monitored, the corresponding client 200 further generates corresponding callback information, and then the client 200 feeds back to the server 100 the status information indicating that the display switch is turned on. If the client 200 notifies that the display switch is turned off and the push information is not displayed in the information notification display column, the above operation is not triggered. If the client 200 is collecting If there is no callback information detected within 5 seconds after the push information is transmitted, the server 100 is fed back with the status information indicating that the display switch is off. Through the above process, the server 100 can know the display status of the push information by the client 200 connected thereto according to the status information fed back by the client 200.

In summary, the push information monitoring device, the push information monitoring method, and the client 200 of the present application combine the state of the notification display switch with the message including the view if the client 200 is not directly notified whether the display switch is turned on. The display state of the frame reaches the indirect acquisition of the state of the notification display switch by detecting the state of the message box. The server 100 can effectively know the display rate of the push information, facilitate opening guidance for the user who closes the push notification, and effectively improve the user's activity level.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may also be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and functionality of possible implementations of apparatus, methods, and computer program products according to various embodiments of the present application. operating. In this regard, each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may also occur in a different order than those illustrated in the drawings. For example, two consecutive blocks may be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented in a dedicated hardware-based system that performs the specified function or function. Or it can be implemented by a combination of dedicated hardware and computer instructions.

In addition, each functional module in each embodiment of the present application may be integrated to form a separate part, or each module may exist separately, or two or more modules may be integrated to form a separate part.

The functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. . It should be noted that, in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply such entities or operations. There is any such actual relationship or order between them. Furthermore, the term "comprises" or "comprises" or "comprises" or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The above description is only the preferred embodiment of the present application, and is not intended to limit the present application, and various changes and modifications may be made to the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application are intended to be included within the scope of the present application. It should be noted that similar reference numerals and letters indicate similar items in the following figures, and therefore, once an item is defined in a drawing, it is not necessary to further define and explain it in the subsequent drawings.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A push information monitoring device is applied to a client that is in communication with a server, wherein the push information monitoring device comprises:

a message box creating module, configured to: after receiving the push information sent by the server, create a message box including a view, where the message box associates a display state of the view with a display state of the push information;

a callback information generating module, configured to monitor the view; and generate callback information when the view is displayed by the message box;

a status information sending module, configured to send status information indicating that the notification display switch has been opened to the server when the callback information is detected, and send, to the server, that the notification display switch has been sent when the callback information is not detected The closed status information, the notification display switch is used to control the display of the push information in the client.
The push information monitoring device according to claim 1, further comprising:

The message box state control module is configured to control the message box to perform an operation of displaying the view when the push information is displayed in an information notification column of the client.
A push information monitoring apparatus according to claim 1, wherein:

The status information sending module is configured to detect whether callback information is generated within a preset time period after receiving the push information sent by the server.
The push information monitoring apparatus according to claim 1, wherein the view is a view that is transparent and has an area size equal to zero.
A push information monitoring apparatus according to claim 1, wherein:

The callback information generating module is configured to monitor whether the view is displayed by the message box by adding an additional state event that can perform a listenback callback to the view.
The push information monitoring device according to claim 1, further comprising:

The push information detecting module is configured to detect whether the client receives the push information sent by the server.
The push information monitoring device according to claim 1, wherein the operating system of the client is an Android system, and the message box is a Toast message box in the Android system.
A push information monitoring method is applied to a client that is in communication with a server, and the push information monitoring method includes:

After receiving the push information sent by the server, creating a message box including a view, and monitoring the view, the message box is associated with a display state of the view and a display state of the push information;

If the callback information is detected, send status information indicating that the display notification display switch has been opened to the server, wherein the callback information is generated when the view is displayed by the message box, and the notification display switch is used. Displaying the push information in the control client;

If no callback information is detected, status information indicating that the notification display switch has been turned off is sent to the server.
The push information monitoring method according to claim 8, wherein before detecting the callback information, the method further comprises:

Controlling the message box to perform an operation of displaying the view when the push information is displayed in an information notification column of the client;

The listener determines that the view is displayed by the message box to generate callback information.
The method for monitoring push information according to claim 8, further comprising:

Whether or not callback information is generated is detected within a preset period of time after receiving the push information sent by the server.
The push information monitoring method according to claim 8, wherein the view is a view that is transparent and has an area size equal to zero.
The method for monitoring push information according to claim 8, wherein the monitoring of the view comprises:

Whether the view is monitored by the message box display by adding an additional state event that can be listened to for the view.
The method for monitoring push information according to claim 8, further comprising:

Detecting whether the client receives the push information sent by the server.
The push information monitoring method according to claim 8, wherein the operating system of the client is an Android system, and the message box is a Toast message box in the Android system.
A client, wherein the client includes:

Memory

Processor;

Pushing the information monitoring device, the push information monitoring device comprising one or more modules stored in the memory and executed by the processor, the information pushing device comprising:

a message box creating module, configured to: after receiving the push information sent by the server, create a message box including a view, where the message box associates a display state of the view with a display state of the push information;

a callback information generating module, configured to monitor the view; and generate callback information when the view is displayed by the message box;

a status information sending module, configured to send, to the server, state information indicating whether the client uses the push information to display the notification display switch has been turned on when the callback information is detected, and when the callback information is not detected, The server transmits status information indicating that the notification display switch has been turned off.
A computer readable storage medium having recorded thereon a program for performing the method of claims 8-14.