CN107734012B - Message pushing method, system and computer readable storage medium - Google Patents

Message pushing method, system and computer readable storage medium Download PDF

Info

Publication number
CN107734012B
CN107734012B CN201710903448.8A CN201710903448A CN107734012B CN 107734012 B CN107734012 B CN 107734012B CN 201710903448 A CN201710903448 A CN 201710903448A CN 107734012 B CN107734012 B CN 107734012B
Authority
CN
China
Prior art keywords
push
push message
server
message
browser
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710903448.8A
Other languages
Chinese (zh)
Other versions
CN107734012A (en
Inventor
倪秉炬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nubia Technology Co Ltd
Original Assignee
Nubia Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nubia Technology Co Ltd filed Critical Nubia Technology Co Ltd
Priority to CN201710903448.8A priority Critical patent/CN107734012B/en
Publication of CN107734012A publication Critical patent/CN107734012A/en
Application granted granted Critical
Publication of CN107734012B publication Critical patent/CN107734012B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a message pushing method, which comprises the following steps: the browser sends a push message request to a server based on a push mechanism corresponding to a preset unified push packet so that the server can feed back corresponding push messages according to the push message request, wherein the unified push packet is suitable for various different browsers; and when the push message fed back by the server is received, transmitting the push message to a corresponding page so as to display the push message. The invention also discloses a system and a computer readable storage medium. The invention reduces the cost of pushing the push message.

Description

Message pushing method, system and computer readable storage medium
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method and a system for pushing a message, and a computer-readable storage medium.
Background
With the development of internet technology, push services have been widely applied to clients and browsers for users to obtain various push messages at any time. Currently, for browsers, different browsers correspond to different push mechanisms, and therefore, push packages corresponding to various browsers need to be developed and configured, which undoubtedly results in high development cost, that is, the cost for implementing message push is high. Moreover, due to different push mechanisms, in order to adapt to different browsers, a server generally needs to implement sending push messages to the browsers through corresponding third-party services, and the third-party services generally need to be charged. Therefore, it can be seen from the above that, currently, the cost for acquiring the push message is high.
Disclosure of Invention
The invention mainly aims to provide a message pushing method, a message pushing system and a computer readable storage medium, and aims to solve the technical problem that the cost for acquiring a pushed message is high in the prior art.
In order to achieve the above object, the present invention provides a message pushing method applied to a browser, where the message pushing method includes:
the browser sends a push message request to a server based on a push mechanism corresponding to a preset unified push packet so that the server can feed back corresponding push messages according to the push message request, wherein the unified push packet is suitable for various different browsers;
and when the push message fed back by the server is received, transmitting the push message to a corresponding page so as to display the push message.
Optionally, the step of sending a push message request to a server, so that the server feeds back a corresponding push message according to the push message request includes:
and merging the push message request and a static resource file request corresponding to the acquired page, and sending the merged push message request and the static resource file request to the server so that the server merges the push message and the corresponding static resource file and feeds the merged push message and the corresponding static resource file back to the browser.
Optionally, the step of sending a push message request to a server, so that the server feeds back a corresponding push message according to the push message request includes:
and merging the push message request and the server interface calling request, and sending the merged push message request and the server interface calling request to the server so that the server merges the push message and the corresponding interface return value and feeds the merged push message and the corresponding interface return value back to the browser.
Optionally, when receiving the push message fed back by the server, the step of transmitting the push message to a corresponding page to display the push message includes:
when the push message is a merged push message corresponding to a plurality of projects, analyzing the merged push message to obtain a push message corresponding to each project;
sequentially taking each project as a current project, and judging whether a page corresponding to the current project is opened or not;
and if so, transmitting the push message corresponding to the current project to the page to display the push message.
Optionally, before the step of sending the push message request to the server, the browser further includes, based on a push mechanism corresponding to a preset unified push packet:
monitoring page operation within the session validity period of the browser;
and if the page operation is not monitored in the session validity period, starting a preset timer, and executing the step of sending the push message request to the server at regular time.
In addition, to achieve the above object, the present invention further provides a message pushing method, which is applied to a server side, and the message pushing method includes:
the method comprises the steps that when a server receives a push message request sent by a browser based on a push mechanism corresponding to a preset unified push packet, the server obtains a corresponding push message according to the push message request;
feeding back the push message to the browser so that the browser can transmit the push message to a corresponding page when receiving the push message, and displaying the push message.
Optionally, the feeding back the push message to the browser so that the browser transmits the push message to a corresponding page when receiving the push message, and the step of displaying the push message includes:
if the push messages are multiple push messages corresponding to multiple projects, merging the multiple push messages;
feeding the combined push messages back to the browser so that the browser can analyze the combined push messages to obtain push messages corresponding to each item, sequentially using each item as a current item, judging whether a page corresponding to the current item is opened or not, and if so, transmitting the push messages corresponding to the current item to the page to display the push messages.
Optionally, when receiving a push message request sent by a browser based on a push mechanism corresponding to a preset unified push packet, the step of obtaining a corresponding push message according to the push message request by the server includes:
when receiving the push message request sent by the browser and a static resource file request corresponding to an acquisition page, acquiring the push message and a corresponding static resource file, wherein the browser combines the push message request and the static resource file request corresponding to the acquisition page and sends the combined push message request and the static resource file request to a server based on a push mechanism corresponding to the unified push packet;
the step of feeding back the push message to the browser comprises:
and combining the push message and the static resource file and feeding back the combined push message and static resource file to the browser.
Optionally, when receiving a push message request sent by a browser based on a push mechanism corresponding to a preset unified push packet, the step of obtaining a corresponding push message according to the push message request by the server includes:
when the push message request and the server interface calling request sent by the browser are received, the push message and a corresponding interface return value are obtained, wherein the browser combines the push message request and the server interface calling request and sends the combined push message request and the server interface calling request to a server based on a push mechanism corresponding to the unified push packet;
the step of feeding back the push message to the browser comprises:
and combining the push message and the interface return value and feeding back the combined push message and the interface return value to the browser.
In addition, to achieve the above object, the present invention further provides a message pushing system, including a browser and a server, wherein:
the browser is used for sending a push message request to the server based on a push mechanism corresponding to a preset unified push packet, wherein the unified push packet is suitable for various browsers; when the push message fed back by the server is received, displaying the push message on a page corresponding to the browser;
and the server is used for feeding back the corresponding push message according to the push message request when receiving the push message request sent by the browser.
Furthermore, to achieve the above object, the present invention also provides a computer-readable storage medium, on which a message pushing program is stored, which when executed by a processor implements the steps of the message pushing method as described above.
According to the scheme provided by the invention, the unified push package adaptive to various different browsers is preset, the browsers send push message requests to corresponding servers based on the push mechanisms corresponding to the unified push package, the servers acquire the corresponding push messages according to the push message requests and feed the push messages back to the browsers, and because all the browsers adopt the unified push mechanism, the servers do not need to adapt to different browsers and realize the purpose of sending the push messages to the browsers through corresponding third-party services, so that the corresponding third-party services do not need to be purchased, and the cost of message push is saved. Moreover, the unified push package is adapted to various browsers, so that corresponding push packages do not need to be configured for the various browsers, development cost is reduced, and push cost of push messages is further reduced. .
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present invention;
FIG. 2 is a diagram of a communication network system architecture in which various embodiments of the present invention may be implemented;
FIG. 3 is a flowchart illustrating a first embodiment of a message pushing method according to the present invention;
fig. 4 is a schematic flow chart illustrating a process of transmitting the push message to a corresponding page to display the push message when receiving the push message fed back by the server according to the second embodiment of the message push method of the present invention;
FIG. 5 is a flowchart illustrating a message pushing method according to a third embodiment of the present invention;
FIG. 6 is a flowchart illustrating a fourth embodiment of a message pushing method according to the present invention;
fig. 7 is a schematic flow diagram illustrating that the push message is fed back to the browser in the fifth embodiment of the message push method of the present invention, so that the browser transmits the push message to a corresponding page when receiving the push message, so as to display the push message;
fig. 8 is a schematic diagram of a framework of the message push system according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The solution of the embodiment of the invention is mainly as follows: the method comprises the steps that unified push packets which are adaptive to various different browsers are preset, the browsers send push message requests to corresponding servers based on push mechanisms corresponding to the unified push packets, the servers acquire corresponding push messages according to the push message requests and feed the push messages back to the browsers, and the browsers push the push messages to corresponding pages to display the push messages. By the technical scheme of the embodiment of the invention, the problem of higher cost for acquiring the push message is solved.
Referring to fig. 1, fig. 1 is a schematic diagram of a hardware structure of a terminal for implementing various embodiments of the present invention.
In the present invention, the terminal can be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), etc., and may also include a fixed type terminal such as a Digital TV, a desktop computer, etc.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a terminal for implementing various embodiments of the present invention, the terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an a/V (audio/video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, a power supply 111, and the like. Those skilled in the art will appreciate that the terminal configuration shown in fig. 1 is not intended to be limiting, and that the terminal may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes the various components of the terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
WiFi belongs to short-distance wireless transmission technology, and the terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The terminal 100 also includes at least one sensor 105, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 100 or may be used to transmit data between the terminal 100 and the external device.
The memory 109 may be used to store software programs as well as various data. In the present invention, the memory 109 of the terminal 100 stores a message pushing program. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The processor 110 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
In the present invention, the processor 110 executes the message pushing program stored in the memory 109 to perform the following operations:
sending a push message request to a server based on a push mechanism corresponding to a preset unified push packet so that the server can feed back corresponding push messages according to the push message request, wherein the unified push packet is adapted to various different browsers;
and when the push message fed back by the server is received, transmitting the push message to a corresponding page so as to display the push message.
Further, the processor 110 executes the message pushing program stored in the memory 109, and further performs the following operations:
and merging the push message request and a static resource file request corresponding to the acquired page, and sending the merged push message request and the static resource file request to the server so that the server merges the push message and the corresponding static resource file and feeds the merged push message and the corresponding static resource file back to the browser.
Further, the processor 110 executes the message pushing program stored in the memory 109, and further performs the following operations:
and merging the push message request and the server interface calling request, and sending the merged push message request and the server interface calling request to the server so that the server merges the push message and the corresponding interface return value and feeds the merged push message and the corresponding interface return value back to the browser.
Further, the processor 110 executes the message pushing program stored in the memory 109, and further performs the following operations:
when the push message is a merged push message corresponding to a plurality of projects, analyzing the merged push message to obtain a push message corresponding to each project;
sequentially taking each project as a current project, and judging whether a page corresponding to the current project is opened or not;
and if so, transmitting the push message corresponding to the current project to the page to display the push message.
Further, the processor 110 executes the message pushing program stored in the memory 109, and further performs the following operations:
monitoring page operation within the session validity period of the browser;
and if the page operation is not monitored in the session validity period, starting a preset timer, and sending a message pushing request to the server at regular time.
The terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system.
Although not shown in fig. 1, the terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the terminal of the present invention is based is described below.
Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present invention, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.
Specifically, the UE201 may be the terminal 100 described above, and is not described herein again.
The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Among them, the eNodeB2021 may be connected with other eNodeB2022 through backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.
The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. The MME2031 is a control node that handles signaling between the UE201 and the EPC203, and provides bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.
Although the LTE system is described as an example, it should be understood by those skilled in the art that the present invention is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Based on the above terminal hardware structure and communication network system, the present invention provides various embodiments of the message pushing method.
Referring to fig. 3, fig. 3 is a flowchart illustrating a message pushing method according to a first embodiment of the present invention.
In a first embodiment, the message pushing method is applied to a browser side and includes the following steps:
step S10, sending a push message request to a server based on a preset unified push packet, so that the server can feed back a corresponding push message according to the push message request, wherein the unified push packet is adapted to various different browsers;
step S20, when receiving the push message fed back by the server, transmitting the push message to a corresponding page to display the push message.
In the invention, in order to reduce the message pushing cost, a unified pushing package which can be adapted to various browsers of different types is configured in advance, and the unified pushing package refers to a program package, such as a JAR package. The unified push package comprises a push message acquisition method corresponding to a server side and a push message method in a return value of an analysis server corresponding to a client browser, wherein calling of the methods is realized based on java or js universal codes.
And when a user starts a corresponding browser and opens a page corresponding to a corresponding item, in order to obtain a push message corresponding to the page, the browser sends a push message request corresponding to the page to a corresponding server based on a push mechanism corresponding to a preset unified push packet.
For the server, when receiving a push message request sent by the browser, the server calls a method for obtaining the push message in the unified push packet to obtain the push message corresponding to the push message request, adds the obtained push message to a return value corresponding to the push message request, and feeds the return value back to the browser.
For the browser, after receiving a return value corresponding to a push message request fed back by a server, the browser calls a push message method for analyzing the return value in a unified push packet, analyzes the return value, acquires a corresponding push message, and transmits the push message to a corresponding page so as to display the push message on the page.
Because the method for acquiring the push message corresponding to the server side and the method for pushing the push message in the return value of the analysis server corresponding to the browser of the client side are realized based on java or js universal codes, and a universal HTTP protocol is used for data communication between the server and the browser, the methods are not required to be adapted to the browser and can be compatible with various browsers.
Therefore, the server does not need to send the push message to the browser through a corresponding third-party service, such as GoEasy, in order to adapt to different browsers, and therefore, the corresponding third-party service does not need to be purchased.
Alternatively, the browser may send the push message request to the server in a variety of different circumstances. Two ways for the browser to send a push message request to the server are listed below.
1) And in the first mode, when the browser acquires the static resource file corresponding to the page from the server, the browser sends the push message request to the server. Specifically, in this embodiment, the step S10 includes:
step a, combining the push message request and a static resource file request corresponding to the acquired page, and sending the combined push message request and the static resource file request to the server, so that the server combines the push message and the corresponding static resource file and feeds the combined push message and the corresponding static resource file back to the browser.
Generally, when a user opens a certain page based on a browser, the browser will go to a server to obtain a static resource file corresponding to the page. Based on this, in this manner, when the browser is to acquire the static resource file corresponding to the page from the server, the browser merges the static resource file request corresponding to the corresponding acquired page with the push message request and sends the merged request to the server.
When the server receives a push message request sent by the browser in a combined mode and a static resource file request corresponding to the acquired page, the server acquires the push message corresponding to the page according to the push message request and acquires the static resource file corresponding to the page according to the static resource file request corresponding to the acquired page. And then, the server combines the obtained push message and the static resource file corresponding to the page and feeds the combined push message and the static resource file back to the browser. For example, the server optionally merges the push message into the tail of the static resource file and feeds back to the browser.
2) And in the second mode, the browser sends the push message request to the server when calling the server interface. Specifically, in this embodiment, the step S10 includes:
and b, merging the push message request and the request for calling the server interface, and sending the merged push message request and the request for calling the server interface to the server so that the server merges the push message and the corresponding interface return value and feeds the merged push message and the corresponding interface return value back to the browser.
In general, each page opened by the browser includes an interface requesting from the server, such as an HTTP (HyperText Transfer Protocol) interface. Based on this, in this mode, when the browser calls an interface to the server, the browser combines the corresponding server interface calling request and the push message request and sends the combined request to the server.
When the server receives a server interface calling request and a server pushing message request which are sent by the browser in a combined mode, the server obtains pushing messages corresponding to the page according to the server pushing message request and obtains corresponding interface return values according to the server interface calling request. And then, the server combines the acquired push message and the interface return value and feeds the combined push message and the interface return value back to the browser. For example, the server optionally incorporates the push message into the interface return value for feedback to the browser.
The above listed pushing message request is sent to the server when the static resource file corresponding to the page is acquired from the server, and the pushing message request is sent to the server when the server interface is called, so that the browser does not need to send the pushing message request to the server separately; similarly, the server merges the obtained push message and the static resource file corresponding to the page and feeds the merged push message back to the browser, or merges the obtained push message and the interface return value and feeds the merged push message back to the browser without sending the push message to the browser separately, so that the interaction times between the browser and the server are reduced, and the message pushing efficiency is improved.
It should be noted that, the browser may send the push message request to the server through two ways, that is, the above-mentioned sending of the push message request to the server when the static resource file corresponding to the page is acquired from the server, or the sending of the push message request to the server when the server interface is called, and may also send the push message request to the server through other ways, and specifically, the way in which the browser sends the push message request to the server is not limited in this embodiment.
According to the scheme provided by the embodiment, the unified push package adaptive to various different browsers is preset, the browsers send push message requests to corresponding servers based on the push mechanisms corresponding to the unified push package, the servers acquire corresponding push messages according to the push message requests and feed the push messages back to the browsers, and due to the fact that all the browsers adopt the unified push mechanism, the servers do not need to adapt to different browsers any more, and the push messages are sent to the browsers through corresponding third-party services, so that the corresponding third-party services do not need to be purchased, and the cost of message push is saved. Moreover, the unified push package is adapted to various browsers, so that corresponding push packages do not need to be configured for various browsers in a complicated manner, development cost is reduced, and push cost of push messages is further reduced.
Further, as shown in fig. 4, a second embodiment of the message pushing method of the present invention is proposed. The second embodiment of the message pushing method differs from the first embodiment of the message pushing method in that, in the second embodiment of the message pushing method, the step S20 includes:
step S21, when the push message is a merged push message corresponding to a plurality of projects, analyzing the merged push message to obtain a push message corresponding to each project;
step S22, taking each item as the current item in turn, and judging whether the page corresponding to the current item is opened; if yes, go to step S23; if not, go to step S24;
step S23, transmitting a push message corresponding to the current item to the page, so as to display the push message;
and step S24, terminating the push of the push message corresponding to the current item.
In this embodiment, in order to improve the pushing efficiency of the push message, when the push message to be pushed to the user includes a plurality of push messages, where the plurality of push messages may be push messages corresponding to one item or may also be push messages corresponding to a plurality of items, the server merges the plurality of push messages, and then feeds back the merged plurality of push messages to the browser, so that the pushing times of the push messages are effectively reduced, and the pushing efficiency of the push messages is improved.
And when the browser receives the combined plurality of push messages fed back by the server, analyzing the combined plurality of push messages to obtain each corresponding push message. If the plurality of push messages are push messages corresponding to the same project, judging whether a page corresponding to the project is opened; if so, transmitting the push messages to a page corresponding to the project so as to display the push messages on the page; if not, the pushing of the push message is terminated, and no response processing is carried out.
If the push messages are push messages corresponding to a plurality of projects, sequentially taking each project as a current project, and judging whether a page corresponding to the current project is opened; if so, transmitting a push message corresponding to the current project to the page so as to display the push message on the page; if not, terminating the push of the push message corresponding to the current project and not performing response processing.
According to the scheme provided by the embodiment, when a plurality of push messages need to be pushed to the browser, the plurality of push messages are merged and pushed, and when the browser receives the merged push messages, the merged push messages are analyzed, so that each push message is obtained and displayed on the corresponding page, and the push of the push messages is completed. Due to the fact that the plurality of push messages are combined and pushed, the pushing times of the push messages are effectively reduced, and therefore the pushing efficiency of the push messages is improved.
Further, as shown in fig. 5, a third embodiment of the message pushing method of the present invention is proposed. The difference between the third embodiment of the message pushing method and the first embodiment of the message pushing method or the second embodiment of the message pushing method is that, in the third embodiment of the message pushing method, before the step S10, the method further includes:
step S30, monitoring page operation in the session validity period of the browser;
step S40, if no page operation is monitored in the session validity period, a preset timer is started, and the step S10 is executed at regular time.
Since data communication is generally performed between the browser and the server through a TCP (Transmission Control Protocol) long connection, some browsers may prevent the TCP long connection from being pushed, and the browser has a session invalidation mechanism and a corresponding session validity period, for example, half an hour. If the user does not perform any operation within the session validity period, the login state of the browser is invalid, and once the login state is invalid, the browser cannot receive the push message any more, so that the push message cannot be pushed in time, and the user may miss a useful push message.
Therefore, in this embodiment, in order to obtain the push message from the server in time, a corresponding timer is preset. Normally, the timer is not started. When a user opens a browser and the browser is in a login state, page operation corresponding to the browser is monitored within a session validity period of the browser, that is, whether the browser sends a push message request to a server or whether the browser sends a request for acquiring a static resource file to the server or whether the browser sends a request for calling a server interface to the server or the like is monitored within the session validity period. If the corresponding page operation is monitored in the session validity period, for example, the browser has to execute one of the above listed operations, the timer is continuously maintained not to be started. If the corresponding page operation is not monitored all the time within the session validity period, namely any one of the listed operations is not executed, a timer is started, a timing task is run, and a push message request is sent to the server at regular time.
Then, the server and the browser execute the corresponding operations in the first embodiment or the second embodiment to push the push message, and the specific operation process may refer to the first embodiment or the second embodiment, which is not described herein again. Therefore, in the embodiment, after the user opens the browser, whether the page operation is available or not within the session validity period, the push message can be ensured to be obtained in time.
According to the scheme provided by the embodiment, a timer is preset, after the browser is started, page operation within the session validity period of the browser is monitored, if the page operation is not monitored within the session validity period, the timer is started, and a push message request is sent to the server at regular time, so that push messages pushed by the server are obtained in time, and the push messages are ensured to be pushed in time.
Further, referring to fig. 6, fig. 6 is a flowchart illustrating a message pushing method according to a fourth embodiment of the present invention.
In a fourth embodiment, the message pushing method is applied to a server, and includes the following steps:
step S50, when receiving a push message request sent by a browser based on a push mechanism corresponding to a preset unified push package, a server acquires a corresponding push message according to the push message request;
step S60, feeding back the push message to the browser, so that when the browser receives the push message, the browser transmits the push message to a corresponding page to display the push message.
In the invention, a uniform pushing package which can be adapted to various browsers of different types is pre-configured, namely a uniform code package is provided, and the code package can realize that the browsers of different types can obtain pushing messages, so that various items operated based on the browsers are integrated in the code package for use, and various corresponding pushing mechanisms do not need to be realized respectively.
And when a user starts a corresponding browser and opens a page corresponding to a corresponding item, in order to obtain a push message corresponding to the page, the browser sends a push message request corresponding to the page to a corresponding server based on a push mechanism corresponding to a preset unified push packet.
For the server, because the browser sends the push message request to the server based on the push mechanism corresponding to the uniform push package, and the push mechanism corresponding to the uniform push package is applicable to various browsers of different types, the server does not need to send the push message to the browser through a corresponding third-party service, such as GoEasy, in order to adapt to different browsers, and therefore, the browser does not need to purchase the corresponding third-party service. In this embodiment, when the server receives a push message request sent by the browser, the server may directly obtain, according to the push message request, a push message corresponding to the push message request, that is, obtain a push message corresponding to the page. And then, the server feeds back the push message corresponding to the acquired page to the browser.
Optionally, in an embodiment, the step S50 includes:
step c, when receiving the push message request sent by the browser and a static resource file request corresponding to an acquisition page, acquiring the push message and a corresponding static resource file, wherein the browser combines the push message request and the static resource file request corresponding to the acquisition page and sends the combined push message request and the static resource file request to a server based on a push mechanism corresponding to the unified push package;
the step S60 includes:
and d, combining the push message and the static resource file and feeding back the combined push message and static resource file to the browser.
Generally, when a user opens a certain page based on a browser, the browser will go to a server to obtain a static resource file corresponding to the page. Based on this, in this manner, when the browser is to acquire the static resource file corresponding to the page from the server, the browser merges the corresponding static resource file request corresponding to the acquired page and the push message request based on the push mechanism corresponding to the unified push package, and sends the merged request to the server.
When the server receives a push message request sent by the browser in a combined mode and a static resource file request corresponding to the acquired page, the server acquires the push message corresponding to the page according to the push message request and acquires the static resource file corresponding to the page according to the static resource file request corresponding to the acquired page. And then, the server combines the obtained push message and the static resource file corresponding to the page and feeds the combined push message and the static resource file back to the browser. For example, the server optionally merges the push message into the tail of the static resource file and feeds back to the browser.
Optionally, in another embodiment, the step S50 includes:
step e, when receiving the push message request and the server interface calling request sent by the browser, acquiring the push message and a corresponding interface return value, wherein the browser combines the push message request and the server interface calling request and sends the combined push message request and the server interface calling request to a server based on a push mechanism corresponding to the unified push packet;
the step S60 includes:
and e, combining the push message and the interface return value and feeding back the combined push message and the interface return value to the browser.
In general, each page opened by the browser includes an interface, such as an HTTP interface, for requesting from the server. Based on the point, in the mode, when the browser calls the interface to the server, the browser combines the corresponding server interface calling request and the push message request and sends the combined request to the server based on the push mechanism corresponding to the uniform push packet.
When the server receives a server interface calling request and a server pushing message request which are sent by the browser in a combined mode, the server obtains pushing messages corresponding to the page according to the server pushing message request and obtains corresponding interface return values according to the server interface calling request. And then, the server combines the acquired push message and the interface return value and feeds the combined push message and the interface return value back to the browser. For example, the server optionally incorporates the push message into the interface return value for feedback to the browser.
The above listed pushing message request is sent to the server when the static resource file corresponding to the page is acquired from the server, and the pushing message request is sent to the server when the server interface is called, so that the browser does not need to send the pushing message request to the server separately; similarly, the server merges the obtained push message and the static resource file corresponding to the page and feeds the merged push message back to the browser, or merges the obtained push message and the interface return value and feeds the merged push message back to the browser without sending the push message to the browser separately, so that the interaction times between the browser and the server are reduced, and the message pushing efficiency is improved.
And the browser transmits the push message to a corresponding page based on a push mechanism corresponding to the uniform push package when receiving the push message fed back by the server so as to display the push message on the page.
According to the scheme provided by the embodiment, the unified push package adaptive to various different browsers is preset, the browsers send push message requests to corresponding servers based on the push mechanisms corresponding to the unified push package, the servers acquire corresponding push messages according to the push message requests and feed the push messages back to the browsers, and due to the fact that all the browsers adopt the unified push mechanism, the servers do not need to adapt to different browsers any more, and the push messages are sent to the browsers through corresponding third-party services, so that the corresponding third-party services do not need to be purchased, and the cost of message push is saved. Moreover, the unified push package is adapted to various browsers, so that corresponding push packages do not need to be configured for various browsers in a complicated manner, development cost is reduced, and push cost of push messages is further reduced.
Further, as shown in fig. 7, a fifth embodiment of the message pushing method of the present invention is proposed. The fifth embodiment of the message pushing method is different from the fourth embodiment of the message pushing method in that, in the fifth embodiment of the message pushing method, the step S60 includes:
step S61, if the push message is multiple push messages corresponding to multiple items, merging the multiple push messages;
step S22, feeding back the combined push messages to the browser, so that the browser parses the combined push messages to obtain a push message corresponding to each item, and sequentially using each item as a current item, determining whether a page corresponding to the current item is open, if so, transmitting the push message corresponding to the current item to the page, so as to display the push message.
In this embodiment, in order to improve the pushing efficiency of the push message, when the push message to be pushed to the user includes a plurality of push messages, where the plurality of push messages may be push messages corresponding to one item or may also be push messages corresponding to a plurality of items, the server merges the plurality of push messages, and then feeds back the merged plurality of push messages to the browser, so that the pushing times of the push messages are effectively reduced, and the pushing efficiency of the push messages is improved.
And when the browser receives the combined plurality of push messages fed back by the server, analyzing the combined plurality of push messages to obtain each corresponding push message. If the plurality of push messages are push messages corresponding to the same project, judging whether a page corresponding to the project is opened; if so, transmitting the push messages to a page corresponding to the project so as to display the push messages on the page; if not, the pushing of the push message is terminated, and no response processing is carried out.
If the push messages are push messages corresponding to a plurality of projects, sequentially taking each project as a current project, and judging whether a page corresponding to the current project is opened; if so, transmitting a push message corresponding to the current project to the page so as to display the push message on the page; if not, terminating the push of the push message corresponding to the current project and not performing response processing.
According to the scheme provided by the embodiment, when the server needs to push the plurality of push messages to the browser, the plurality of push messages are merged and pushed, and when the browser receives the merged plurality of push messages, the merged push messages are analyzed, so that each push message is obtained and displayed on the corresponding page, and the push of the push messages is completed. Due to the fact that the plurality of push messages are combined and pushed, the pushing times of the push messages are effectively reduced, and therefore the pushing efficiency of the push messages is improved.
In addition, the embodiment of the invention also provides a message pushing system.
Referring to fig. 8, fig. 8 is a schematic diagram of a framework of the message push system of the present invention. The message pushing system comprises a browser and a server, wherein:
the browser is used for sending a push message request to the server based on a push mechanism corresponding to a preset unified push packet, wherein the unified push packet is suitable for various browsers; when the push message fed back by the server is received, the push message is displayed on a corresponding page of the browser;
and the server is used for feeding back the corresponding push message according to the push message request when receiving the push message request sent by the browser.
In this embodiment, a message pushing system is composed of a server and a browser. In order to reduce the message pushing cost, a unified pushing package which can be adapted to various browsers of different types is configured in advance, and the unified pushing package refers to a program package such as a JAR package. The unified push package comprises a push message acquisition method corresponding to a server side and a push message method in a return value of an analysis server corresponding to a client browser, wherein calling of the methods is realized based on java or js universal codes.
And when a user starts a corresponding browser and opens a page corresponding to a corresponding item, in order to obtain a push message corresponding to the page, the browser sends a push message request corresponding to the page to a corresponding server based on a push mechanism corresponding to a preset unified push packet.
For the server, when receiving a push message request sent by the browser, the server calls a method for obtaining the push message in the unified push packet to obtain the push message corresponding to the push message request, adds the obtained push message to a return value corresponding to the push message request, and feeds the return value back to the browser.
For the browser, after receiving a return value corresponding to a push message request fed back by a server, the browser calls a push message method for analyzing the return value in a unified push packet, analyzes the return value, acquires a corresponding push message, and transmits the push message to a corresponding page so as to display the push message on the page.
Because the method for acquiring the push message corresponding to the server side and the method for pushing the push message in the return value of the analysis server corresponding to the browser of the client side are realized based on java or js universal codes, and a universal HTTP protocol is used for data communication between the server and the browser, the methods are not required to be adapted to the browser and can be compatible with various browsers.
Therefore, the server does not need to send the push message to the browser through a corresponding third-party service, such as GoEasy, in order to adapt to different browsers, and therefore, the corresponding third-party service does not need to be purchased.
According to the scheme provided by the embodiment, the unified push package adaptive to various different browsers is preset, the browsers send push message requests to corresponding servers based on the push mechanisms corresponding to the unified push package, the servers acquire corresponding push messages according to the push message requests and feed the push messages back to the browsers, and due to the fact that all the browsers adopt the unified push mechanism, the servers do not need to adapt to different browsers any more, and the push messages are sent to the browsers through corresponding third-party services, so that the corresponding third-party services do not need to be purchased, and the cost of message push is saved. Moreover, the unified push package is adapted to various browsers, so that corresponding push packages do not need to be configured for various browsers in a complicated manner, development cost is reduced, and push cost of push messages is further reduced.
Furthermore, an embodiment of the present invention further provides a computer-readable storage medium, where a message pushing program is stored on the computer-readable storage medium, and when executed by a processor, the message pushing program implements the following operations:
sending a push message request to a server based on a push mechanism corresponding to a preset unified push packet so that the server can feed back corresponding push messages according to the push message request, wherein the unified push packet is adapted to various different browsers;
and when the push message fed back by the server is received, transmitting the push message to a corresponding page so as to display the push message.
Further, the message pushing program when executed by the processor further implements the following operations:
and merging the push message request and a static resource file request corresponding to the acquired page, and sending the merged push message request and the static resource file request to the server so that the server merges the push message and the corresponding static resource file and feeds the merged push message and the corresponding static resource file back to the browser.
Further, the message pushing program when executed by the processor further implements the following operations:
and merging the push message request and the server interface calling request, and sending the merged push message request and the server interface calling request to the server so that the server merges the push message and the corresponding interface return value and feeds the merged push message and the corresponding interface return value back to the browser.
Further, the message pushing program when executed by the processor further implements the following operations:
when the push message is a merged push message corresponding to a plurality of projects, analyzing the merged push message to obtain a push message corresponding to each project;
sequentially taking each project as a current project, and judging whether a page corresponding to the current project is opened or not;
and if so, transmitting the push message corresponding to the current project to the page to display the push message.
Further, the message pushing program when executed by the processor further implements the following operations:
monitoring page operation within the session validity period of the browser;
and if the page operation is not monitored in the session validity period, starting a preset timer, and sending a message pushing request to the server at regular time.
According to the scheme provided by the embodiment, the unified push package adaptive to various different browsers is preset, the browsers send push message requests to corresponding servers based on the push mechanisms corresponding to the unified push package, the servers acquire corresponding push messages according to the push message requests and feed the push messages back to the browsers, and due to the fact that all the browsers adopt the unified push mechanism, the servers do not need to adapt to different browsers any more, and the push messages are sent to the browsers through corresponding third-party services, so that the corresponding third-party services do not need to be purchased, and the cost of message push is saved. Moreover, the unified push package is adapted to various browsers, so that corresponding push packages do not need to be configured for various browsers in a complicated manner, development cost is reduced, and push cost of push messages is further reduced.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims (9)

1. A message pushing method is applied to a browser end and is characterized by comprising the following steps:
the browser sends a push message request to a server based on a push mechanism corresponding to a preset unified push packet so that the server can feed back corresponding push messages according to the push message request, wherein the unified push packet is suitable for various different browsers;
when the push message fed back by the server is received, transmitting the push message to a corresponding page so as to display the push message;
the step of sending a push message request to a server so that the server feeds back a corresponding push message according to the push message request includes:
and merging the push message request and a static resource file request corresponding to the acquired page, and sending the merged push message request and the static resource file request to the server so that the server merges the push message and the corresponding static resource file and feeds the merged push message and the corresponding static resource file back to the browser.
2. The message pushing method according to claim 1, wherein the step of sending a push message request to a server for the server to feed back a corresponding push message according to the push message request comprises:
and merging the push message request and the server interface calling request, and sending the merged push message request and the server interface calling request to the server so that the server merges the push message and the corresponding interface return value and feeds the merged push message and the corresponding interface return value back to the browser.
3. The message pushing method according to claim 1, wherein the step of delivering the push message to a corresponding page to display the push message when receiving the push message fed back by the server comprises:
when the push message is a merged push message corresponding to a plurality of projects, analyzing the merged push message to obtain a push message corresponding to each project;
sequentially taking each project as a current project, and judging whether a page corresponding to the current project is opened or not;
and if so, transmitting the push message corresponding to the current project to the page to display the push message.
4. The message pushing method according to any one of claims 1 to 3, wherein before the step of sending the push message request to the server by the browser based on the pushing mechanism corresponding to the preset unified push package, the method further comprises:
monitoring page operation within the session validity period of the browser;
and if the page operation is not monitored in the session validity period, starting a preset timer, and executing the step of sending the push message request to the server at regular time.
5. A message pushing method is applied to a server side, and is characterized by comprising the following steps:
the method comprises the steps that when a server receives a push message request sent by a browser based on a push mechanism corresponding to a preset unified push packet, the server obtains a corresponding push message according to the push message request;
feeding the push message back to the browser so that the browser can transmit the push message to a corresponding page when receiving the push message, and displaying the push message;
when receiving a push message request sent by a browser based on a push mechanism corresponding to a preset unified push packet, the server acquires a corresponding push message according to the push message request, and the step includes:
when the push message request and the static resource file request corresponding to the acquired page sent by the browser are received, the push message and the corresponding static resource file are acquired, and the browser combines the push message request and the static resource file request corresponding to the acquired page and sends the combined push message request and the static resource file request to a server based on a push mechanism corresponding to the unified push package;
the step of feeding back the push message to the browser comprises:
and combining the push message and the static resource file and feeding back the combined push message and static resource file to the browser.
6. The message pushing method according to claim 5, wherein the step of feeding back the push message to the browser so that the browser can deliver the push message to a corresponding page when receiving the push message to display the push message comprises:
if the push messages are multiple push messages corresponding to multiple projects, merging the multiple push messages;
feeding the combined push messages back to the browser so that the browser can analyze the combined push messages to obtain push messages corresponding to each item, sequentially using each item as a current item, judging whether a page corresponding to the current item is opened or not, and if so, transmitting the push messages corresponding to the current item to the page to display the push messages.
7. The message pushing method according to claim 5, wherein the step of, when receiving the push message request sent by the browser based on the push mechanism corresponding to the preset unified push package, the server obtaining the corresponding push message according to the push message request includes:
when the push message request and the server interface calling request sent by the browser are received, the push message and a corresponding interface return value are obtained, wherein the browser combines the push message request and the server interface calling request and sends the combined push message request and the server interface calling request to a server based on a push mechanism corresponding to the unified push packet;
the step of feeding back the push message to the browser comprises:
and combining the push message and the interface return value and feeding back the combined push message and the interface return value to the browser.
8. A message push system, characterized in that the message push system comprises a browser and a server, wherein:
the browser is used for sending a push message request to the server based on a push mechanism corresponding to a preset unified push packet, wherein the unified push packet is suitable for various browsers; when the push message fed back by the server is received, displaying the push message on a page corresponding to the browser;
and the server is used for feeding back the push message and the corresponding static resource file according to the push message and the static resource file request when receiving the push message request and the static resource file request sent by the browser.
9. A computer-readable storage medium, on which a message pushing program is stored, which when executed by a processor implements the steps of the message pushing method according to any one of claims 1 to 4.
CN201710903448.8A 2017-09-27 2017-09-27 Message pushing method, system and computer readable storage medium Active CN107734012B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710903448.8A CN107734012B (en) 2017-09-27 2017-09-27 Message pushing method, system and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710903448.8A CN107734012B (en) 2017-09-27 2017-09-27 Message pushing method, system and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN107734012A CN107734012A (en) 2018-02-23
CN107734012B true CN107734012B (en) 2021-06-15

Family

ID=61208983

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710903448.8A Active CN107734012B (en) 2017-09-27 2017-09-27 Message pushing method, system and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN107734012B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110719145B (en) * 2018-07-13 2022-04-19 深圳兆日科技股份有限公司 Method and device for sending read receipt and computer readable storage medium
CN111294369B (en) * 2018-12-06 2022-06-03 阿里巴巴集团控股有限公司 Page request processing method and device and electronic equipment
CN111917811B (en) * 2019-05-10 2023-08-25 北京车和家信息技术有限公司 Message pushing method and system

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102333128A (en) * 2011-10-31 2012-01-25 河南省电力公司计量中心 Active transmission method for real-time Web data
CN102724324A (en) * 2012-06-28 2012-10-10 用友软件股份有限公司 Information pushing and integrating device and information pushing and integrating method
CN103902616A (en) * 2012-12-28 2014-07-02 腾讯科技（深圳）有限公司 Method, device and system for pushing webpage application messages
CN105897884A (en) * 2016-04-07 2016-08-24 四川大学 Android mobile phone push platform based on eXtensive messaging presence protocol (XMPP)
CN106412104A (en) * 2016-10-28 2017-02-15 努比亚技术有限公司 Application message pushing device and method
CN106453382A (en) * 2016-10-28 2017-02-22 努比亚技术有限公司 Message pushing method and device
CN106899641A (en) * 2015-12-21 2017-06-27 北京奇虎科技有限公司 The acquisition methods of data resource, server, control device and communication system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100894910B1 (en) * 2007-11-09 2009-04-30 한국전자통신연구원 Multiiple query processing apparatus and method for heterogeneous sensor networks
WO2015186248A1 (en) * 2014-06-06 2015-12-10 株式会社日立製作所 Storage system, computer system, and data migration method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102333128A (en) * 2011-10-31 2012-01-25 河南省电力公司计量中心 Active transmission method for real-time Web data
CN102724324A (en) * 2012-06-28 2012-10-10 用友软件股份有限公司 Information pushing and integrating device and information pushing and integrating method
CN103902616A (en) * 2012-12-28 2014-07-02 腾讯科技（深圳）有限公司 Method, device and system for pushing webpage application messages
CN106899641A (en) * 2015-12-21 2017-06-27 北京奇虎科技有限公司 The acquisition methods of data resource, server, control device and communication system
CN105897884A (en) * 2016-04-07 2016-08-24 四川大学 Android mobile phone push platform based on eXtensive messaging presence protocol (XMPP)
CN106412104A (en) * 2016-10-28 2017-02-15 努比亚技术有限公司 Application message pushing device and method
CN106453382A (en) * 2016-10-28 2017-02-22 努比亚技术有限公司 Message pushing method and device

Also Published As

Publication number Publication date
CN107734012A (en) 2018-02-23

Similar Documents

Publication Publication Date Title
CN108572764B (en) Character input control method and device and computer readable storage medium
CN108768775B (en) Information processing method, electronic device, and computer storage medium
CN107038245B (en) Page switching method, mobile terminal and storage medium
CN107040543B (en) Single sign-on method, terminal and storage medium
CN112799577B (en) Method, terminal and storage medium for projecting small window
CN107749919B (en) Application program page display method and device and computer readable storage medium
CN110784898A (en) Network switching method, mobile terminal and computer readable storage medium
CN108282405B (en) Application program interface cache management method, application server and storage medium
CN108600516B (en) Data acquisition method, mobile terminal and computer readable storage medium
CN107862217B (en) Position information acquisition method, mobile terminal and computer storage medium
CN110187808B (en) Dynamic wallpaper setting method and device and computer-readable storage medium
CN107734012B (en) Message pushing method, system and computer readable storage medium
CN110278481B (en) Picture-in-picture implementation method, terminal and computer readable storage medium
CN108306856B (en) Interface merging method, client, server and computer readable storage medium
CN108260009B (en) Video processing method, mobile terminal and computer readable storage medium
CN108040116B (en) Message pushing method, router and computer readable storage medium
CN107809527B (en) Method for presenting shortcut operation and electronic equipment
CN109669616B (en) Side screen interaction control method and device and computer readable storage medium
CN109818967B (en) Notification method, server, mobile terminal and computer readable storage medium
CN111970738A (en) Network switching control method, equipment and computer readable storage medium
CN111931155A (en) Verification code input method, verification code input equipment and storage medium
CN108183833B (en) Response processing method and device and computer readable storage medium
CN108040330B (en) WiFi directional transmission method, mobile terminal and readable storage medium
CN107623788B (en) Method and device for improving application starting speed and computer readable storage medium
CN107204977B (en) Interface security verification method and device and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant